May 2013 - 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

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

I'm studying the copydata example to learn how to extract several variables from a file identified in a COMMENT LEGAL statement. In A3.chk, the statement "TYPE COMMENT atransfer" appears. What is atransfer? I don't see where it has been defined as a variable and I don't find it as a system variable. Further, the program seems to be parsing the string in atransfer according to the position of punctuation. Where is the format of this string defined? Perhaps to be a bit more explicit: I have file with a list of CHWs: District, Village, CHW name and a survey conducted by the CHWs. As the data is entered for the survey, I'd like to present pick lists to facilitate entry. The data is quite strictly hierarchical: Villages occur within Districts, an CHWs live in villages. Thank you,

2 3

Re: EpiData-list Digest, Vol 115, Issue 9
by epidata-list＠lists.umanitoba.ca 29 May '13

29 May '13

Thank you! When can I expect to be able to compare values in second file with what was already entered in the first file directly at entry? Is there an older version that allows this? Best, Natalie On Wed, May 29, 2013 at 10: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. Issue with double entry verification > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Issue with double entry verification > (epidata-list(a)lists.umanitoba.ca) > 3. Aspects of function in updated public release of Manager and > EntryClient (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 May 2013 20:47:44 -0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Issue with double entry verification > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAON-6PbqL-Rb_x3Nd2tBhf-hrP1v7T6c8Ju8RBKXrWR8wEmMdw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello, > > I am having an issue with double entry verification. I am using v1.4 on a > 64 bit Windows 7 PC. I am able to create a double file, but I am missing > any options like the manual indicates: > > *"*Options can be changed now: choose if textfields are to be ignore during > double entry (only data in numeric fields will be compared with original > data). > > Choose if records are to be compare by recordnumber or by a keyfield. If > the option "Match records by field" is unchecked, then records are compared > by recordnumber. If the option is checked, the user will be asked to point > out which data field should act as the keyfield. The keyfield must contain > unique data, i.e. a ID-number. > > Click OK and read the message stating that double entry varification is now > prepared." > > It simply only creates the double data file. I am also not able to get into > any sort of double entry mode in the epidata entry program. > > Is this a bug or am I not using it correctly? Thanks very much. > > -- > Natalie Sadler > Doctoral Student > Human Development Graduate Group > University of California, Davis > nsadler(a)ucdavis.edu > natalie.sadler(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Wed, 29 May 2013 09:12:41 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Issue with double entry verification > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <51A5AA69.1050200(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi. > > The double entry verification is a two-step process, which works > by first creating a duplicate of the the original project, but without > data. This is done with the "Prepare Double Entry"feature. > > Then you re-enter data into the second file, often namedlike > <filename>.double.epx. > > The last step is using the documentation feature "Validate > Duplicate Files" to compare the two files. It is within this feature > that you find your requested options, such as: > comparing using key fields, ignore text fields, etc. > > I hope this helps. > > Regards, > Torsten Bonde Christiansen. > EpiData Association. > > On 2013-05-29 05:47, epidata-list(a)lists.umanitoba.ca wrote: > > Hello, > > > > I am having an issue with double entry verification. I am using v1.4 on a > > 64 bit Windows 7 PC. I am able to create a double file, but I am missing > > any options like the manual indicates: > > > > *"*Options can be changed now: choose if textfields are to be ignore > during > > double entry (only data in numeric fields will be compared with original > > data). > > > > Choose if records are to be compare by recordnumber or by a keyfield. If > > the option "Match records by field" is unchecked, then records are > compared > > by recordnumber. If the option is checked, the user will be asked to > point > > out which data field should act as the keyfield. The keyfield must > contain > > unique data, i.e. a ID-number. > > > > Click OK and read the message stating that double entry varification is > now > > prepared." > > > > It simply only creates the double data file. I am also not able to get > into > > any sort of double entry mode in the epidata entry program. > > > > Is this a bug or am I not using it correctly? Thanks very much. > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 29 May 2013 09:55:54 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Aspects of function in updated public release > of Manager and EntryClient > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <51A5B48A.6070202(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Regarding the new versions 1.4 of Manager and EntryClient. > > Many changes have been implemented since first public release last year: > > Common: > * Encrypted data in project files > * Expanded headings to support 5 sizes/types. > * Added printing of dataform > * Key Fields (Unique keys) - including display of status of key at > record level > > Entry: > * Implemented a "Copy Record to Clipboard" function, with variable > format string. > > Manager: > * New improved drag/drop implementation (multiselect, copy/paste, > alignment) > * Double Entry Preparation/Validation > * Improved Study Information form. > * New improved export form, with more export formats. (SPSS, SAS, CSV, > DTA, DDI) > * Expanded process toolbar > > Obviously this is a remarked update and despite efforts to find and fix > problems in the testing uploads some issues have arisen in latest days: > > 1 Double entry > a > In EpiData Entry (old software): > - two different double entry modes are implemented: > 1. Compare values in second file with what was already entered in first > file directly at entry > 2. Compare two individually entered files > > In EpiData Manager (New software): > - Only type two is implemented at this point. Therefore you must (as > explained by T.Christiansen just before this mail) first enter data in > one file, then independently in the second. Following that compare the two. > > b > Validation has been extended with a new option such that a new field > can be added at record level (each observation) with the result of the > validation. When this field is added it makes sense to write a new file, > e.g. bromar.1.doubleentry-verification.epx. You can then read that file > into analysis and see which records are not validated. The values for > the created variable are: > 0 = Validated > 1 = Record does not exist in duplicate file > 2 = Failed due to different text > 3 = Failed due to different values > 4 = Duplicate key exists > > But currently in v1.4.0.0 the file is always created following > validation, and there can be a problem with the creation. This will be > changed, such that only when the user indicates addition of the field > the new file will be written and obviously also with the correct value. > > 2 > Aspects in relation to export: > a. Export to SPSS or SAS: the user is not informed of writing the > csv file > b. Export to DDI: the created xml is not correct in certain situations. > > Exported DDI meta data must validate correctly against the > DDI-Alliance standard v3.1. - with an external tool such as documented > on http://www.ddialliance.org/node/855 - The validator is found on > http://snd.gu.se/ddi/validator > > 3 > A few other aspects, such as default naming of valuelabel sets, term for > dataforms in reports and missing mentioning of cycle number > > The problems mentioned (1b, 2 and 3) will be fixed and a new public > update will be available later this week. > > Regarding cycle number this is a new feature which the end user is not > changing. Every time the project file is saved and there has been a > change in either study information, structure or value label sets > (metadata) or entered/edited observations/records the file will be saved > with a new "cycle number". On export this is part of the name of the > file. e.g. /home/jens/data/bromar_new.5.dta > > We will gradually implement usage of the cycle number in documentation > and verification of data in relation to in particular the implementation > of Good Clinical Practice guideline demands of verification. The notion > of a cycle comes from the DDI-alliance data-life cycle concept. You can > read more about that on: http://www.ddialliance.org/ddi-at-work > > regards > Jens Lauritsen > Epidata Association > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 115, Issue 9 > ******************************************** > -- Natalie Sadler Doctoral Student Human Development Graduate Group University of California, Davis nsadler(a)ucdavis.edu natalie.sadler(a)gmail.com

1 1

Issue with double entry verification
by epidata-list＠lists.umanitoba.ca 29 May '13

29 May '13

Hello, I am having an issue with double entry verification. I am using v1.4 on a 64 bit Windows 7 PC. I am able to create a double file, but I am missing any options like the manual indicates: *"*Options can be changed now: choose if textfields are to be ignore during double entry (only data in numeric fields will be compared with original data). Choose if records are to be compare by recordnumber or by a keyfield. If the option "Match records by field" is unchecked, then records are compared by recordnumber. If the option is checked, the user will be asked to point out which data field should act as the keyfield. The keyfield must contain unique data, i.e. a ID-number. Click OK and read the message stating that double entry varification is now prepared." It simply only creates the double data file. I am also not able to get into any sort of double entry mode in the epidata entry program. Is this a bug or am I not using it correctly? Thanks very much. -- Natalie Sadler Doctoral Student Human Development Graduate Group University of California, Davis nsadler(a)ucdavis.edu natalie.sadler(a)gmail.com

1 2

Reply: Regarding exporting to SPSS
by epidata-list＠lists.umanitoba.ca 24 May '13

24 May '13

Dear Seng Aung, -You can directly export to SPSS. But the dataset gets saved as SYNTAX file with an extension of " .sps" - Then open this syntax file in SPSS (using open-syntax in menu bar) , you will get a list commands/syntax. Read the instructions at the top of that page. You have to go to the last command/syntax SAVE and remove the * mark to execute the SAVE command. After removing the * mark, just click the RUN in the menubar (RUN all) and your SPSS dataset (.sav file) is ready with labels and label values. -I checked with the EpiData manager and it is working. Dr. C. Palanivel, MD (Community Medicine) Assistant Professor, Indira Gandhi Medical College and Research Institute, (Government of Puducherry Institution) Kathirkamam, Puducherry-605009. Office: 0413-2277545 (Ex) 3123 Mobile: 9787825827 On Wed, May 1, 2013 at 10:31 PM, <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. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > 2. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > 3. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 May 2013 14:56:28 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <000ED2B2-B253-454F-B1D7-10EAFC19CB01(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > Message: 2 > Date: Wed, 1 May 2013 14:56:38 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <899870FA-492C-4554-90A9-1FC98482545E(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > Message: 3 > Date: Wed, 1 May 2013 14:34:46 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <364AD808-5412-4D08-8711-E537DA688E01(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 115, Issue 1 > ******************************************** >

1 2

Reply: Regarding exporting to SPSS
by epidata-list＠lists.umanitoba.ca 15 May '13

15 May '13

Dear Dr. C. Palanivel, I've just downloaded and installed the latest EpiData Manager (1.1.2), but I can't find the export to SPSS feature - can you please point me in the right direction? In the Tools menu I only find "Export to Stata". Save Project As does not offer a SPSS or SYNTAX file format. Thank you in advance, Knud Larsen, Lab.Engineer, MScEE Aalborg University

1 2

Reply: Export to SPSS in version 1.1.2
by epidata-list＠lists.umanitoba.ca 14 May '13

14 May '13

Dear Larsen, - Yes, I can't find 'export to SPSS' option in EpiData Manager version 1.1.2 - You can do it by installing new test versions 1.3.2 (My previous comment on export to SPSS was based on this version) and the latest test release version 1.3.2.1 (released on 14th May). - In the tools menu or Export process tool bar, the default option is export to stata. There is a drop down box in the right top and you can select CSV or SPSS or SAS. I tested with SPSS export and it is working. (Remove the * mark before last SAVE command before running the syntax file in SPSS) - For latest versions, in the epidata website, goto downloads page----test versions---EpiData manager - Test versions may have issues with other functions (test version!!!)...Have a back up of your data Regards, Dr. C. Palanivel, On Tue, May 14, 2013 at 10:30 PM, <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. Reply: Regarding exporting to SPSS > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Reply: Regarding exporting to SPSS > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 May 2013 19:05:39 +0000 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Reply: Regarding exporting to SPSS > To: "'epidata-list(a)lists.umanitoba.ca'" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <31E7023F6EA2104EB7735E7EE729465A343FD071(a)AD-EXCHMBX2-1.aau.dk> > Content-Type: text/plain; charset="us-ascii" > > Dear Dr. C. Palanivel, > > I've just downloaded and installed the latest EpiData Manager (1.1.2), but > I can't find the export to SPSS feature - can you please point me in the > right direction? > In the Tools menu I only find "Export to Stata". Save Project As does not > offer a SPSS or SYNTAX file format. > > Thank you in advance, > Knud Larsen, Lab.Engineer, MScEE > Aalborg University > > > ------------------------------ > > Message: 2 > Date: Mon, 13 May 2013 16:28:41 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Reply: Regarding exporting to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP6B5C8494423FA496EBE1EFDA00(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > You should be able to read STATA v9 files in SPSS. > Jamie > > On 2013-05-13, at 3:05 PM, epidata-list(a)lists.umanitoba.ca wrote: > > > I've just downloaded and installed the latest EpiData Manager (1.1.2), > but I can't find the export to SPSS feature - can you please point me in > the right direction? > > In the Tools menu I only find "Export to Stata". Save Project As does > not offer a SPSS or SYNTAX file format. > > > > Thank you in advance, > > Knud Larsen, Lab.Engineer, MScEE > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 115, Issue 6 > ******************************************** >

1 0

RE:
by epidata-list＠lists.umanitoba.ca 13 May '13

13 May '13

http://queensland.homedesignandliving.com.au/facebook_xml.php?pkgnlf782pi rtremeaud raphael tremeaud **************** Epperson's law: When a man says it's a silly, childish game, it's probably something his wife can beat him at. %

1 0

Types of table in Epidata analysis & normal distribute
by epidata-list＠lists.umanitoba.ca 13 May '13

13 May '13

I see that there are 3 types of table in Epidata analysis: standard, compact, first x all; however, I have not yet distinguished among them: How/when use them, especially compact type. Besides, If I want to know whether data is normal distribute then what command takes on in epidata analysis? I hope that everyone will help me as soon as possible. Thanks many. -- Đỗ Thị Thanh Tâm - 0945.554.880

1 1

Error Epidata Analysis
by epidata-list＠lists.umanitoba.ca 03 May '13

03 May '13

Hi everybody, I would like to format an xls file into .rec file. I save my xls file into csv file to open the latter in Epidata Analysis. It did not want to open my file. I found that there is some pb with string variables. I thought to fix all problems but now Windows close Epidata Analysis when I'm trying to open my .csv file. Can anybody help me? Thank you so much in advance. Candemum.

1 1