Updated experimental test version of relational datasets (Manager and EntryClient 2.0.0.0)
On Oct. 9th. we announced release of an experimental test version capable of creating relational structures. See: http://lists.umanitoba.ca/pipermail/epidata-list/2014q4/002546.html
The following major bugs have been fixed and new versions are available: Updated versions are placed for download on http://www.epidata.dk/testing.php
Manager: 1. Reports were not saved correctly as txt or html 2. Value labels could not be edited 3. Export had malfunction
EntryClient: Would not propagate correctly the key from one level to the next in some instances.
Please test and verify function in as well simple and complex situations.
Please notice that version is still - in this upload - 2.0.0.0, but creation date is Oct 22nd.,
It is a good idea to use a particular ini file and recent file saving, when you are testing. To do this you add parameters/options to the start.
To see the options you can run from a terminal, epidatamanager -h entryclient -h which will give the explanation, e.g. for configurations files: -i=mytest.cfg recent file list: -r=testfiles.txt
regards Torsten Bonde Christiansen and Jens Lauritsen EpiData Association
To verify correct version: "Copy version Info" found in the help menu and check: Manager: Program version: 2.0.0.0[RC2] r1010 EntryClient: Program version: 2.0.0.0[RC2] r411 Both of them: Core version: 2.0.0.0 r1080
Thanks:
I'll take a look on it.
Att.
El 22/10/14 a las 06:14, epidata-list@lists.umanitoba.ca escibió:
On Oct. 9th. we announced release of an experimental test version capable of creating relational structures. See: http://lists.umanitoba.ca/pipermail/epidata-list/2014q4/002546.html
The following major bugs have been fixed and new versions are available: Updated versions are placed for download on http://www.epidata.dk/testing.php
Manager:
- Reports were not saved correctly as txt or html
- Value labels could not be edited
- Export had malfunction
EntryClient: Would not propagate correctly the key from one level to the next in some instances.
Please test and verify function in as well simple and complex situations.
Please notice that version is still - in this upload - 2.0.0.0, but creation date is Oct 22nd.,
It is a good idea to use a particular ini file and recent file saving, when you are testing. To do this you add parameters/options to the start.
To see the options you can run from a terminal, epidatamanager -h entryclient -h which will give the explanation, e.g. for configurations files: -i=mytest.cfg recent file list: -r=testfiles.txt
regards Torsten Bonde Christiansen and Jens Lauritsen EpiData Association
To verify correct version: "Copy version Info" found in the help menu and check: Manager: Program version: 2.0.0.0[RC2] r1010 EntryClient: Program version: 2.0.0.0[RC2] r411 Both of them: Core version: 2.0.0.0 r1080
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
From today v2.0.0.1 of Manager capable of creating relational data sets is available on http://www.epidata.dk/testing.php
There was a bug in creating value labels in v2.0.0.0, which has been fixed. There is still a bug if you use external value labels. E.g. a separate project file with all ICD10 diagnoses.
Please test and report .
We are aware of the possible inconvenience of uploads every other day. So if you allocate time for testing then check if there was a new upload before you spent time.
You should be aware that the function "Check Version Online" in the help menu does NOT show the experimental test versions, but today shows "Latest test version 0.0.0.0", since there is no release candidate for test.
We will modify the only version control to a more informative one. Such that one also can see when there is something to test and if so if this is a release candidate or an experimental one.
The development will typically be that we first publish an experimental test version, where the xml file structure has some form. This form can change btw. experimental test versions, but when we get to the "release candidate" level usually the xml format of the epx project file is fixed. And before the public release version is ready will be documented in the required way. Which will then be supported from that point on. We will always support reading "old" epx public release formats, but not those working at the experimental level.
We are now working with more aspects of relational data sets on the passage to a public release version. for example full adaptation of handling projects with more than one dataform, wording of structures, backup principles.
To analyse data in a relational dataset you should export one dataform at a time. EpiData Analysis cannot read related data sets at this point.
regards
Jens Lauritsen EpiData Association
participants (1)
-
epidata-list＠lists.umanitoba.ca