Dear all users
New versions were placed yesterday for general download on http://www.epidata.dk/download.php
Many bugs have been fixed during recent releases and we therefore encourage all to get the new versions and replace older ones. The new versions will work with all epx project files. But it is always good practice to have a backup copy if some unexpected problem shows up.
The two updated versions fixes several details of related file systems and export. Related file principles are now sufficiently developed for routine use, including handling of "mark for deletion", "count by id", "compare duplicate", export etc.
See the complete list of changes here: Http://epidata.dk/epidatamanager.changelog.txt Http://epidata.dk/epidataentryclient.changelog.txt
Conversion from flat file systems to related structure is rather simple, provided you define the keys correctly. A step by step recipe for this will be published here later and added to the wiki system at http://epidata.info/dokuwiki/doku.php?id=start
Regards
Jens Lauritsen EpiData Association, Denmark
Unfortunately we found a bug today in relation to key expression on dataforms if a time field is part of the key.
A replacement file will be uploaded as soon as we have a "cure" for it.
We have tested four other relational setup projects which worked without any problem. These had other field types in the key.
Regards Jens Lauritsen EpiData Association
On 05/11/15 11:54, EpiData development and support wrote:
Dear all users
New versions were placed yesterday for general download on http://www.epidata.dk/download.php
Many bugs have been fixed during recent releases and we therefore encourage all to get the new versions and replace older ones. The new versions will work with all epx project files. But it is always good practice to have a backup copy if some unexpected problem shows up.
The two updated versions fixes several details of related file systems and export. Related file principles are now sufficiently developed for routine use, including handling of "mark for deletion", "count by id", "compare duplicate", export etc.
See the complete list of changes here: Http://epidata.dk/epidatamanager.changelog.txt Http://epidata.dk/epidataentryclient.changelog.txt
Conversion from flat file systems to related structure is rather simple, provided you define the keys correctly. A step by step recipe for this will be published here later and added to the wiki system at http://epidata.info/dokuwiki/doku.php?id=start
Regards
Jens Lauritsen EpiData Association, Denmark
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
On 05/11/15 17:36, EpiData development and support wrote:
Unfortunately we found a bug today in relation to key expression on dataforms if a time field is part of the key.
A replacement version - EntryClient 2.0.6.22 - has been uploaded. Please do not use any interim version for real projects.
We apologize for the inconvenience of several builds within a few days. It would be optimal if we could have a batch testing programme for defining and entering data. But until now we have found no viable solution for that. In contrast to EpiData Analysis for which we have almost 2000 tests in a batch procedure.
Allow me to mention that continued development is only possible due to funds from various sources, which also includes projects which I am responsible for here in Denmark. In particular I would like to acknowledge repeated donations from The Union (http://www.theunion.org/) since 2003. A complete list of contributors is available at: http://epidata.dk/funding.htm
In addition to substantial economic support the demands for functionality from The Union has been crucial. The teaching materials published at http://tbrieder.org/epidata/epidata.html is an important source for dissemination of proper principles in field work with EpiData software.
It should also be noted that without the skilled and consistent implementation of principles and functionality by T.Christiansen and the well functioning collaboration he and I have in the design of the software it would also not be possible to disseminate this software suite with focus on data documentation and sound field epidemiology principles. (- said in all modesty -)
The scheduled development path contains all the aspects of securing data regulation principles (user control and logging) (next months), scripting as part of data entry (mid 2016) and rewriting of analysis (follows). Source code will be released as open-source when we are through all aspects.
If problems or questions arise in relation to the new version please notify the list.
Regards Jens Lauritsen EpiData Association, Denmark Initiator and coordinator.
epidata-list@lists.umanitoba.ca
-
EpiData development and support