- EpiData-list - University of Manitoba Mailing Lists

New test version of Manager and Analysis
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

The release of September 2nd is a minor update for Manager and EpiData Analysis, in which a few bug have been found and fixed. Manager: * Fixed bug where exporting to STATA did not export valuelabels. * Added support for importing .rec files with password protection. * Fixed minor bug where importing .rec files with valuelabels under special circumstances were not imported correctly. * Fixed significant bug in importing structure of STATA files could render computer useless (HUGE memory usage). * Fixed significant bug where deleting a section, with fields/heading moved out of could also delete the fields/headings. * Added "space extender". A heading is placed a "page" down on the designer, to extend the working area for placing fields, sections and headings. Analysis: * Fixed a bug where importing project files .epx/.epz would create a buggy .chk file on saving data from within Analysis. ==================================== Regards Torsten Christiansen and Jens Lauritsen EpiData Association

1 0

Re: conditional value label look-up?
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

We can use the following for the conditional value label look-up, disease AFTER ENTRY IF (disease='A') THEN GOTO subtypeA EXIT ENDIF IF (disease='B') THEN GOTO subtypeB ENDIF END END subtypeA COMMENT LEGAL USE label_subtypea SHOW TYPE COMMENT END subtypeB COMMENT LEGAL USE label_subtypeb SHOW TYPE COMMENT END Bijay Adhikari On Fri, Sep 2, 2011 at 11:00 AM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > 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. Re: conditional value label look-up? > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 1 Sep 2011 20:29:35 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] conditional value label look-up? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP55572154E8DD723E0CAE91FD180(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > This is possible in the current version of EpiData. The syntax is shown in > the help file (.chk commands --> comment legal). It only works for comment > legal, not for legal. In my tests, it sometimes get confused. You can also > implement it, if your lists are short (as in your example), using nested if > ... then blocks. This may be better as the logic should be simple enough and > it will be bullet-proof. You can also provide error messages using the help > command. > > In the test version, there is not yet an equivalent way to do this, but > here is what I would do: > > create 4 fields: > > disease > sub1 > sub2 > subtype (string only will work) > > disease has jumps, to either sub1 or sub2, depending on its value > sub1 and sub2 have appropriate legal values, ranges or value labels > sub1 and sub2 have a calculation: subtype=sub1 in sub1 and subtype=sub2 in > sub2 > > subtype is NOENTER > > sub1 and sub2 have to jump to the field past subtype. I'm not sure whether > an unconditional jump is implemented yet. This may be problematic. > > Jamie > > On 2011-08-31, at 4:30 PM, epidata-list(a)lists.umanitoba.ca wrote: > > > Is there a way to do a conditional value label look up in either the > current or in the new test version of EpiData? > > > > For instance, if field disease equals A then field subtype has values > 1,2,3 for selection, if field disease equals B then field subtype has values > 4,5,6, etc. > > > > Thank-you, and well done to the development team for excellent progress. > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 2 > ******************************************* > -- Regards, ABJ "It is not the strongest of the species that survives, nor the most intelligent, but the one most responsive to change." Charles Darwin

1 0

Re: conditional value label look-up
by epidata-list＠lists.umanitoba.ca 03 Sep '11

03 Sep '11

Greetings. Is there a way to do a conditional value label look up in either the current or in the new test version of EpiData? For instance, if field disease equals A then field subtype has values 1,2,3 for selection, if field disease equals B then field subtype has values 4,5,6, etc. Thank-you, and well done to the development team for excellent progress. _______________________________________ Stephen Drew Health Data Analyst Region of Waterloo Public Health Waterloo, ON ======================================================================== Thanks Stephen, what about using the expression if: Example for disease A disease_A BEFORE ENTRY IF disease_A = 1 or "AFP" THEN Symptom = 1 GOTO admission ENDIF END END Next thing to be done is the following expression IF disease_B = 2 or "Yellow_Fever" THEN Symptom = 3 GOTO admission_tropic (i.e another subtype) ENDIF END END As you can see this can be very time consuming, however it could best done at the data management stage where you could create or generate new variable appropriately before cracking on with the analysis. However, if you really want to proceed with: "A then field subtype has values 1,2,3 for selection" then the other thing that you could do would be to assign a unique code; such as if field subtype has values 1,2,3, then coded it 1, for value 4-7 coded it 2; this will make it easy. I am struggling to understand why you need values 1, 2, 3 in the same field at the same time? Hope this helps Best wishes Tieble On 1 September 2011 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. conditional value label look-up? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2011 16:30:53 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] conditional value label look-up? > To: "'epidata-list(a)lists.umanitoba.ca'" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: > < > 51AB587E44A99647912C34562ECADA570AF45AFBA1(a)MAIL.region.waterloo.on.ca> > > Content-Type: text/plain; charset="us-ascii" > > Greetings. > > Is there a way to do a conditional value label look up in either the > current or in the new test version of EpiData? > > For instance, if field disease equals A then field subtype has values 1,2,3 > for selection, if field disease equals B then field subtype has values > 4,5,6, etc. > > Thank-you, and well done to the development team for excellent progress. > _______________________________________ > Stephen Drew > Health Data Analyst > Region of Waterloo Public Health > Waterloo, ON > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 95, Issue 1 > ******************************************* > -- <http://www.vet2011.org/calendrier3.php>http://vet2011.org Vet for health, Vet for food, Vet for the planet ! <http://www.mgavm.ru/>

1 0

conditional value label look-up?
by epidata-list＠lists.umanitoba.ca 01 Sep '11

01 Sep '11

Greetings. Is there a way to do a conditional value label look up in either the current or in the new test version of EpiData? For instance, if field disease equals A then field subtype has values 1,2,3 for selection, if field disease equals B then field subtype has values 4,5,6, etc. Thank-you, and well done to the development team for excellent progress. _______________________________________ Stephen Drew Health Data Analyst Region of Waterloo Public Health Waterloo, ON

1 1

IF... THEN LEGAL
by epidata-list＠lists.umanitoba.ca 30 Aug '11

30 Aug '11

Hi all, I'm trying to combine IF... THEN with LEGAL but somehow I'm having problems with it. Basically, what I want to do is to determine valid values for one variable based on the answer given to another variable. In the example below, the two vars are stateid and countyid: If stateid = 1 then countyid could be 01 or 04; if stateid = 2 then countyid could be 02, 03 or 05. Example: countyid IF stateid = 1 THEN LEGAL 01 04 END ENDIF IF stateid = 2 THEN LEGAL 02 03 05 END ENDIF MUSTENTER END -- Thomaz A.

1 2

I can't normally export value labels to Stata 11
by epidata-list＠lists.umanitoba.ca 27 Aug '11

27 Aug '11

Dear friends, I can't normally export value labels to Stata 11 data file even using the newest sample.epx. Why? RegardsRichard Zhou > Date: Fri, 26 Aug 2011 12:00:29 -0500 > From: epidata-list-request(a)lists.umanitoba.ca > Subject: EpiData-list Digest, Vol 94, Issue 13 > To: epidata-list(a)lists.umanitoba.ca > > 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. Re: New test versions (manager, entryclient, template cmd > tool) (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Aug 2011 13:25:02 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] New test versions (manager, entryclient, > template cmd tool) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4E57828E.2030904(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear All. > > As promised in our previous mail, we have released a new test version of > EpiData Analysis on our website today. > > This test release have been modified to support the new XML structure > used by the most recent versions of EpiData Manager and EpiData EntryClient. > > Along with this change, EpiData Analysis is now also capable of reading > the zipped versions of the project files. That is, it is now possible to > read the .epz files. > > With kind regards, > Torsten Bonde Christiansen. > EpiData Association. > > > On 2011-08-24 16:38, epidata-list(a)lists.umanitoba.ca wrote: > > > > Dear All > > > > As previously announced the programs released today have had a > > significant change to the underlying structure of the project file > > (the .epx/.epz XML structure). > > > > The reason for this is that the previous structure could not be > > described by a XML Schema file. A schema file is a standardised way of > > describing the structure and internal logic of an XML file. Some of > > the logical properties of the structure were inconsistent and > > therefore changed. This has as a positive "side effect" that the > > overall loading and saving time for a project file has improved quite > > a bit. > > > > The changes will - as warned two times on this list - break > > compatibility with > > previously created files. An updated version of the sample.epx file is > > provided with the downloads and additionally the EpiData Commandline > > Tool has been updated (and release for all platforms) to support the > > new XML structure. > > > > Please read previous mails on the list to see further explanation and > > how you can avoid problems in relation to the changed XML structure. > > > > The currently available test version of EpiData Analysis does NOT > > support the new XML structure. An updated version will be released in > > a few days. > > > > Common fixes/changes: > > * Updated XML structure > > * Import from STATA 12 now supported. > > * New saving algorithm, for improved speed. > > > > Manager: > > * Fixed a bug where removing a control marked for copy would cause > > breakdown if copy/paste was later invoked. > > * Fixed shortcuts for MAC. > > * Added boolean field to "other fields" > > * Fixed bug with "delete all" > > * Speed improvements for copy/paste and placing new controls (mainly > > visible with very many controls). > > > > EntryClient: > > * Fixed shortcut overlap in MAC > > * Speed improvements with loading project files. > > * Speed improvements when browsing records. > > > > EpiC: > > * Updated to support new XML structure. > > > > Regards > > > > Torsten Christiansen and Jens Lauritsen > > EpiData Association > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 94, Issue 13 > ********************************************

1 0

New test versions (manager, entryclient, template cmd tool)
by epidata-list＠lists.umanitoba.ca 26 Aug '11

26 Aug '11

Dear All As previously announced the programs released today have had a significant change to the underlying structure of the project file (the .epx/.epz XML structure). The reason for this is that the previous structure could not be described by a XML Schema file. A schema file is a standardised way of describing the structure and internal logic of an XML file. Some of the logical properties of the structure were inconsistent and therefore changed. This has as a positive "side effect" that the overall loading and saving time for a project file has improved quite a bit. The changes will - as warned two times on this list - break compatibility with previously created files. An updated version of the sample.epx file is provided with the downloads and additionally the EpiData Commandline Tool has been updated (and release for all platforms) to support the new XML structure. Please read previous mails on the list to see further explanation and how you can avoid problems in relation to the changed XML structure. The currently available test version of EpiData Analysis does NOT support the new XML structure. An updated version will be released in a few days. Common fixes/changes: * Updated XML structure * Import from STATA 12 now supported. * New saving algorithm, for improved speed. Manager: * Fixed a bug where removing a control marked for copy would cause breakdown if copy/paste was later invoked. * Fixed shortcuts for MAC. * Added boolean field to "other fields" * Fixed bug with "delete all" * Speed improvements for copy/paste and placing new controls (mainly visible with very many controls). EntryClient: * Fixed shortcut overlap in MAC * Speed improvements with loading project files. * Speed improvements when browsing records. EpiC: * Updated to support new XML structure. Regards Torsten Christiansen and Jens Lauritsen EpiData Association

1 2

Warning: Changes in XML structur in the next test release of Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 22 Aug '11

22 Aug '11

Dear all As I already informed on August 17th the next test release for Manager and EntryClient will require ALL current EPX and EPZ files to be recreated. The next test release will be available within the next few days. Obviously this can be annoying, but as previously announced we do need to have the flexibility of changes all the way to release of version 1. If you are preparing projects for future use I recommend that you either: a. - Export your data with current test version into stata format - import again with the new test version (when this is ready) - add jumps, calculations etc after the import. (Labels will be imported correctly) or b look at the template principles explained in http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat and then use the template command tool to create the epx files. A revised template tool will be released at the same time as the next test release. In other words: Do not spend too much time on fine tuning epx files at this point. Datastructures are fine, but details must be expected to change, e.g. specifications of jumps, range, notes etc. The XML structure used in v1.0 will be supported for all future releases after that. regards Jens Lauritsen EpiData Association

1 1

key unique code not working fully
by epidata-list＠lists.umanitoba.ca 17 Aug '11

17 Aug '11

I have a database with 2 unique keys: stickno and randid. The CHK file contains the following code for these fields: stickno KEY UNIQUE 1 RANGE 1 500 MUSTENTER END randid KEY UNIQUE 2 RANGE 100 1699 MUSTENTER AFTER ENTRY IF (randid>899) and (randid<1300) THEN HELP "randid must be 100-899 or 1300-1699" TYPE=WARNING ENDIF END END Despite the KEY UNIQUE commands, I found 2 records with stickno=290 and randid==227. I believe KEY UNIQUE was present in the CHK file prior to beginning data entry, but even if not, when attempting to open the REC file I should receive a warning alerting me to the duplicates. This doesn't happen when I keep the EIX file in the same directory as the database. After deleting the EIX file from the directory, when attempting to open the REC file I do get a warning alerting me to the duplicates. What information does the EIX file store? I've attached it in case you're able to determine where the error lies. I haven't attached the database because it contains data on real patients and I can't edit it without changing the EIX file. Any insights would be much appreciated. Cheers, Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar(a)mcri.edu.au www.mcri.edu.au <http://www.mcri.edu.au/> ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

1 0

Revision of XML structure and changes in next test release of Manager and EntryClient
by epidata-list＠lists.umanitoba.ca 17 Aug '11

17 Aug '11

Dear all Since last test release of July 15th summer vacation is now over and the following has been fixed or worked on: a. copy-paste bugs b. other minor issues c. develop a scripting tool to validate function (simulate user performance) d. WIKI documentation updated - e.g. see: http://www.epidata.org/dokuwiki/doku.php/documentation:program_keys e. Critical external review of the XML structure The next test release will follow when these aspects are all covered. More comments below. Comments: Yesterday a critical review of the current XML structure for the data files was performed with the Danish Data Archive. It turns out that a few issues requires some changes to the XML structure (tag-attribute), to ensure consistence and possibility of developing a schema file for the XML. Schema files are content describing files, which will enable other software to read the epx files and validate contents against the formal specification. While this is rather technical - and of no interest - to most users, it means that with the next test release the XML structure will change (again). If you are preparing projects for future use I recommend that you either: a. - plan to export your data with current test version into stata format - import again with the new test version (when this is ready) or b look at the template principles explained in http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat and then use the template command tool to create the epx files. A revised template tool will be released at the same time as the next test release. In other words: Do not spend too much time on fine tuning epx files at this point. Datastructures are fine, but details must be expected to change, e.g. specifications of jumps, range, notes etc. The XML structure used in v1.0 will be supported for all future releases after that. regards Jens Lauritsen EpiData Association

1 0