July 2009 - EpiData-list - University of Manitoba Mailing Lists

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

2 3

Limit on number of .rec files that can be RELATEd
by epidata-list＠lists.umanitoba.ca 17 Jul '09

17 Jul '09

Dear EpiData users, It appears as if there is a limit of 30 .rec files that can be linked together in a relational structure for data entry using the RELATE command. Am I mistaken or is there any work around for this? I have 29 files linked to a single "master" file and I need to be able to relate 2 more files to this first file for data entry to work well. Thank you in advance, Emilie

1 1

Re: Negative integer
by epidata-list＠lists.umanitoba.ca 15 Jul '09

15 Jul '09

Thak you guys, setting the field to ## worked fine! Best regards, Abraço forte e que a força esteja com você, Pedro Brasil

1 0

negative integers in epidata entry
by epidata-list＠lists.umanitoba.ca 15 Jul '09

15 Jul '09

Dear EpiData friends, I have a qes like this days NUMBER OF DAYS WITHOUT MEDICINE IN THE PERIOD ## However the ones who filled the CRFs filled this with -1 if there was no information about this question. Now Im testin the entrys to start feeding the datasets and just realize that -1 is not a legal integer for field # I thought that converting this field from # to <A > would work and later in the analysis to encode this variable to integer. WOuld this work? any more elegant workaround? Best regards, Abraço forte e que a força esteja com você, Pedro Emmanuel

1 3

creating an identifiant from various variables + double data entry
by epidata-list＠lists.umanitoba.ca 10 Jul '09

10 Jul '09

Dear Jens, Thanks for your helpful comment on creating an identifiant from various variables and double data entry (see below). I just wanted to clarify a few things: 1) Does this mean that when using the 'Double Entry Verification' option (immediate comparison), this will not work if you have added any new variables into the .rec, or changed the order of the variables from the existing .rec? 2) If you use the other method of data verification (entering data into two seperate files and then validating duplicate files afterwards), is it possible to compare the old and new .rec files, even if a new variable has been added, or the order of the variables has been changed? Will using the 'validate duplicate files' option work if the new .rec file has the variables in a different order? Thanks so much for all your help, Nicki Bailey One aspect of this about unique identifiers is when users want to do double entry. The only double entry option in this situation is to enter the data twice and then compare afterwards, since the "immediate comparison" double entry mode is not available for combined field unique entries unless the records are entered in EXACTLY the same sequence as the first time. The problem for the user is, that the system is NOT giving correct warnings in the immediate double entry if the unique index is created in contrast to entered directly. > I would like the identifier to be automatically created in the .rec > file after entering 4 variables and as an aggregation of these 4 > variables. > For instance my identifier is > ID=region number+village number+household number+member in the > household number regards Jens Lauritsen EpiData Association

1 6