- EpiData-list - University of Manitoba Mailing Lists

Epidata Manager and Entry Client Parent child levels limits
by EpiData development and support 30 Apr '18

30 Apr '18

Dear Jens,We have a relaTional database  with 4 Parent child forms levels in theclassical Epidata as shown below. Family -- Eligible Couple -- Under5 Child-- Growth MonitoringWhen we import the database in EntryClient, Entry Client does not relate  beyond 3 forms. Is there any technical limitto number of child forms which can be related to parent form?Dr. Shavinder Singh

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 170, Issue 2
by EpiData development and support 15 Apr '18

15 Apr '18

Dear Jens and ream Thank you for the effort. I've got a request.. Could podcasts be made, so we can learn easily? I know it's a lot of work but it's a plea from novices including me Warm regards Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] on behalf of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Saturday, April 14, 2018 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 170, Issue 2 Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..." EpiData-list mailing list ___________________________________ Today's Topics: 1. Almost final pre-public Manager - EntryClient (and Analysis) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 14 Apr 2018 18:29:44 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Almost final pre-public Manager - EntryClient (and Analysis) Message-ID: <798374ea-56eb-e9b0-ea5e-36f51a19cf4e(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Since the announcement last week we have not received any comments on the list or direct by mail. Neither have we found any (new) bugs, such that in the coming week we will release the next versions of Manager and EntryClient for public use. A major news item is also that we now consider the re-written Analysis ready for public use in terms of: - reading project files - data management - combination of files (merge, append) - saving, exporting and archiving data files (epx, dta, csv, ddi-3.1) including metadata - frequencies, count, means - documenting content of logging during entry Although it is a major drawback that one cannot create graphs or cross tables yet - we do think that the functionality now developed is sufficiently mature for release. Function is verified with the validation pgm's, which tests about 500 different aspects Therefore You may now find the pre-release versions for all three parts on http://www.epidata.dk/testing.php And once we have written a proper introduction document for the new analysis a public release version will be made available. Best wishes Jens Lauritsen and Torsten Bonde Christiansen EpiData Association Denmark ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 170, Issue 2 ********************************************

1 0

Almost final pre-public Manager - EntryClient (and Analysis)
by EpiData development and support 14 Apr '18

14 Apr '18

Since the announcement last week we have not received any comments on the list or direct by mail. Neither have we found any (new) bugs, such that in the coming week we will release the next versions of Manager and EntryClient for public use. A major news item is also that we now consider the re-written Analysis ready for public use in terms of: - reading project files - data management - combination of files (merge, append) - saving, exporting and archiving data files (epx, dta, csv, ddi-3.1) including metadata - frequencies, count, means - documenting content of logging during entry Although it is a major drawback that one cannot create graphs or cross tables yet - we do think that the functionality now developed is sufficiently mature for release. Function is verified with the validation pgm's, which tests about 500 different aspects Therefore You may now find the pre-release versions for all three parts on http://www.epidata.dk/testing.php And once we have written a proper introduction document for the new analysis a public release version will be made available. Best wishes Jens Lauritsen and Torsten Bonde Christiansen EpiData Association Denmark

1 0

Status - EpiData Software
by EpiData development and support 06 Apr '18

06 Apr '18

A brief status is: Manager and EntryClient: We do not expect addition of more functionality than found in the pre-release versions available this week. It is therefore very important that you report and discuss on this list (or add to Flyspray): a. Bugs in current functionality b. Any feature of high importance lacking in Manager or EntryClient (We are aware that scripting is not implemented, e.g. "before entry ...... after entry" blocks. ) Analysis: The Classic EpiData Analysis v2.2 - build 187 is the latest for production use. This will not be developed further, but will gradually be replaced by the new Analysis - which is still at the "experimental level". Major remaining aspects are: graphs, tables, dialog menu's collapsing/aggregating data, html formulation. Installation: We have decided to change the installation principles to a bundled package principle. The user will then only need to download one file, at least for Windows. The size of that single file will be larger, but still quite small (20-30Mb), which we hope pose no problem. The advantage is that in controlled environments only one file needs to be provided, e.g. here in the health region a new principle will only allow installation from a common system. EpiData has been accepted as part of that due to the inclusion of logging capabilities and we only need to deliver one package file for the health region. Question: Are all Linux users capable of working in 64 bit mode ? (Or do you have Linux installed on 32 bit computers) Open-Source release We are also working on aspects of release as open-source. This includes for example documentation of aspects of design and principles for other users to install and extend aspects on their own computers. More news on this later. The first test went well in the understanding that a power user (Jamie Hockin) in Canada could install all software and development tools, compile and also add to the main source code. Best wishes to all from Torsten Bonde Christiansen and I. Jens Lauritsen Initiator and Coordinator EpiData Association Denmark

1 0

Pre-public test of EpiData Manager and EntryClient - please test
by EpiData development and support 06 Apr '18

06 Apr '18

This week we have provided new versions on http://www.epidata.dk/testing.php: EpiData Manager Version 4.3.2.120 (pre-release) EpiData EntryClient Version 4.3.0.7 (pre-release) EpiData Analysis Version 0.9.3.7 (experimental test ) Manager and EntryClient will be released for production/public use in about a week - unless we find more bugs. Analysis is still experimental. The new features since v4.2 were announced on March 15th (see below). Since then we have removed several bugs, including a major bug in reading of projects and added a tool "archive". Before public release an "unarchive" tool will be provided also. With this you may encrypt any file or folder for archiving or mailing. This version applies stronger (SHA512) encryption and other internal changes to the xml structure. Therefore we kindly ask everyone to make a copy of their projects and then OPEN THE COPY with the versions mentioned above. This applies also to other projects without encryption. Should you find problems let us know on this list or by mail to info (at) epidata.dk . Jens Lauritsen/Torsten Bonde Christiansen EpiData Association Denmark Manager: * Jumps to fields can now also be key fields * Moved key selection from own windows to dataset properties * Added tools: Export Securitylog * Fixed several bugs in exporting to Stata 13+ EntryClient: * Bugfixes related to jump * Bugfixes related to logging with Extended Access * Added posibility to mark a record as Verified - observations that are "Marked for Deletion" cannot be directly marked as verified, but MUST be unmarked from deletion first. (under Extended Access this requires READ rights on the dataset) * Added additional information to the email body if the project is setup to create an email on close. Common: * Added "Days between password change" to Extended Access projects (and enforcement thereof) * Extended logging capabilities when using Extended Access * Better handling of recent files across Manager/Entryclient/Analysis * Updated cryptography of both Single Password and Extended Access from SHA1 to SHA512 Analysis: Consequential changes of the above to ensure reading and writing files accordingly.

1 0

Key from Image
by EpiData development and support 29 Mar '18

29 Mar '18

Does anyone have any information on using EpiData to key from image? The idea being one side of the users screen shows data entry fields while the other side of the screen shows an image that holds the data to be keyed. Once a user completes the data entry for an image, the next image is presented for keying a new record. Thanks, Brian

1 0

Appending memo and text fields, and better display for high dpi screen
by EpiData development and support 27 Mar '18

27 Mar '18

Hi All, Could I ask a couple of questions, please? (1) I have two epx files with the same variables, except that file A has a memo field and the corresponding field in file B is a string (as I imported file B from a stata dataset). How can I append these two files to have a memo field in my final file? (2) Is there a setting for a better display of the user interface on a high dpi screen? The texts on the manager and entry client look blurred at the moment. I am using these: Epidata manager version: 4.2.0.0 Epidata entry client version: 4.2.0.0 Mac OS High Sierra version 10.13.3 Thank you! Best wishes, Zaw Singapore

1 1

New testversions for EpiData Manager, EntryClient and Analysis
by EpiData development and support 15 Mar '18

15 Mar '18

We have just uploaded new testversions on: http://www.epidata.dk/testing.php Analysis: 0.9.3.6- EpiData EntryClient: 4.3.0.6- EpiData Manager: 4.3.1.119 We are still approaching public releases, but still lack some aspects. Remember to ALWAYS work on copies of data. In particular with this release if you use encryption since we have updated the strength of encryption to a stricter (modernized) level - SHA512. The following changes has been made in particular in relation to securing that we meet new demands for encryption and logging in relation to the regulatory requirements. During the coming week our inhouse complete test will be applied. But please do report any aspects you find problematic or strange. In manager we have done a bit of re-arrangement of the menu's, such that defining a "key" is now part of the properties for the datasets (dataforms). On the route to open-source we have done a test of having all source code installed in Canada by Jamie Hockin, who provided an updated "means" calculation in analysis, such that this should now be more precise. This was a promising test. A list of all changes is shown below. Best wishes Jens Lauritsen & Torsten Bonde Christiansen EpiData Association, Denmark. Manager: * Jumps to fields can now also be key fields * Moved key selection from own windows to dataset properties * Added tools: Export Securitylog * Fixed several bug in exporting to Stata 13+ EntryClient: * Bugfixes related to jump * Bugfixes related to logging with Extended Access * Added posibility to mark a record as Verified - observations that are "Marked for Deletion" cannot be directly marked as verified, but MUST be unmarked from deletion first. (under Extended Access this requires READ rights on the dataset) * Added additional information to the email body if the project is setup to create an email on close. Common: * Added "Days between password change" to Extended Access projects (and enforcement thereof) * Extended logging capabilities when using Extended Access * Better handling of recent files across Manager/Entryclient/Analysis * Updated cryptography of both Single Password and Extended Access from SHA1 to SHA512 Analysis: Consequential changes of the above to ensure reading and writing files accordingly.

1 0

time variable without seconds
by EpiData development and support 14 Mar '18

14 Mar '18

Is there any way to create a time variable in a dataform that does not require the seconds to be entered (ie would accept 08:15 instead of 08:15:00) Thank you ... Ian Dohoo -- Ian R. Dohoo DVM, PhD, FCAHS Professor Emeritus - Epidemiology U. of Prince Edward Island Charlottetown, PEI C1A 4P3 CANADA dohoo(a)upei.ca

1 1

new experimental build of analysis 0.9.3.0 released today
by EpiData development and support 09 Feb '18

09 Feb '18

From today v0.9.3.0 is released at the bottom of : Http://www.epidata.dk/testing.php Notice that the commands.html and the "how to adapt your pgm" help files found in the help menu of the main window. Please test and report to this list or in case of severe problems send an email to info at epidata.dk. We do hope that there are no more bugs in the released test version. But we do also encourage you to report such errors here. More info below Best wishes Jens Lauritsen , Torsten Bonde Christiansen EpiData Association Denmark ------------------------------------------------------------------------------------------------------------------- Example: read a file change value in a variable and display a browser before and after: // ----example: read "myfile.epx"; new variable v12 s; v12:= "unknown"; browse age v12 !caption:="Data before change"; v12 := iif( age[_n] > 18, "adult", "young"); browse age v12 !caption:=("Data after change" + now()); // ... end Here it would be natural to ask, why do I need the [-n]. This is a consequence of the way the internal machinery (parser) works. We will think over and attempt to see whether it is possible to leave out this, but until further notice you need that part. We have made it easy to add the [_n] - if you press alt+n with focus in the command prompt or in the editor the sequence "[_n]" will be added. Please do remember to work on copies of data. Real data should only be used in production release versions for actual data-analysis or data management Changes from last experimental version are: Documentation * fixed errors and inconsistencies in commands.html * fixed calling error - which would not open the commands.html in IE browser Adapted syntax * valuelabels: edit vl name <type> ( value, text) ( value, text) etc. Added functionality * automatic variables and memo fields may be created * list project * funtion user(), returning defined users in a project with extended access * Altered shortcuts on MAC (Editor) Bug fixes: * merge had several issues - and should now be complete, including documentation - could overwrite mergevar * editing of !related parameters !childobs and !afterobs * errors in certain variable expansion aspects and special combinations, e.g. save a project without variables * report validate, report cby , check relate could fail. * check relate -> would indicate incorrectly that a 1-many relation was not correct. * createtime(...) will return sysmis with illegal time value

1 0