- EpiData-list - University of Manitoba Mailing Lists

Bug in EpiData 3.1? (TYPE STATUSBAR)
by epidata-list＠lists.umanitoba.ca 01 Jul '05

01 Jul '05

I noticed some differences between EpiData 3.0 and 3.1 and a possible bug in version 3.1: 1) If I use the check command TYE STATUSBAR "CaseNum = " the value of the field (here: casenum) is only shown in the statusbar if the focus is on the field. If I move to other fields, the value is not visible anymore. This occurs in version 3.1 but not in 3.0. This seems to be an error of version 3.1. 2) Version 3.0 and 3.1 differ in the way they display values defined by RANGE, MISSINGVALUE, and/or COMMAND LEGAL (field). For example, I have a multiple response question and the first question is a filter (if checked, the following multiple response questions do not apply). Or there is no filter variable but I want that the coder first has to decide whether any of the multiple response questions are checked (this is what I use in the following example). If not, I want that all values are set to missing (9 - no answer) and the focus should be set to the next block of questions. On the other hand, if there is at least one answer checked, the focus should move to the first of the multiple response questions and the user has to enter one of the folling values: 0 (no checked), 1 (checked), or 7 (ambiguous answer). When all data are entered, I want that the value labels are defined as follows (because I want that the SPSS syntax attaches value labels to missing values, as well; 8 is necesseary because the whole block of questions may not be applicable): * --------------------------------------- LABEL notice 0 "somebody found out" 1 "nobody found out" 7 "ambiguous answer" 8 "not applicable" 9 "no answer" END * --------------------------------------- However, to help the coder I want that while entering the data he/she does not see these labels but the following: ----------------------------------------- 0 - (not checked) 1 - no 7 - (ambiguous answer) ----------------------------------------- With EpiData version 3.0 this is possible if I use the following check commands: * ======================================= beerdt MISSINGVALUE 9 8 7 * <- (1) BEFORE ENTRY HELP "MULTIPLE RESPONSE QUESTION\n\nQuestion 46.6: Anything checked? (y/n)" KEYS="YN" IF (RESULTVALUE=2) THEN beerdt=9 beerdtpa=9 beerdtpo=9 beerdtte=9 beerdtse=9 GOTO beerpun ENDIF COMMENT LEGAL SHOW * <- (2) 0 "(not checked)" 1 no 7 "(ambiguous answer)" END END COMMENT LEGAL USE notice * <- (3) MUSTENTER TYPE COMMENT RED JUMPS 1 beerpun 9 beerpun END AFTER ENTRY IF (beerdt=0) THEN clear beerdtpa clear beerdtpo clear beerdtte clear beerdtse ENDIF IF (beerdt=1) THEN beerdtpa=0 beerdtpo=0 beerdtte=0 beerdtse=0 ENDIF IF (beerdt = 7) THEN WRITENOTE "ambiguous answer" ENDIF IF (beerdt=9) THEN beerdtpa=9 beerdtpo=9 beerdtte=9 beerdtse=9 ENDIF END END * ======================================= However, with EpiData 3.1, I cannot use "MISSINGVALUE 9 8 7" (see: * <- (1)) _and_ "COMMAND LEGAL SHOW" (see: * <- (2)) or "COMMAND LEGAL notice" (see: * <- (3)) simultaneously. If I use (1) and (2), the user sees: ---------------------- 0 - (not checked) 1 - no 7 - (ambiguous answer) 9 - missing 8 - missing 7 - missing ---------------------- and is able to enter 9 (which should not be used) or 8 (which would be wrong). If I only use (2), the value (9) or (8) cannot be set by the "BEFORE ENTRY .. END" command or by an IF .. THEN condition in another field. To use (3) would also be no solution to this problem. Thus, only version 3.0 seems to allow a solution to this problem. My main question is: Are there any reasons why I should prefer version 3.1 to version 3.0? Or which check commands do I need to solve the problem in version 3.1? With respect to the missing values it would be extemely helpful if EpiData could create SPSS syntax that defines missing values according to the definitions in the EpiData check file. However, if (like in version 3.1) I cannot use MISSINGVALUE and "COMMAND LEGAL labelname" (because I want to label the missing values and to show the coder the meaning of the values entered) simultaneously , there are no missing value definitions that EpiData could use to create the SPSS syntax file. I think that there are two solutions to this problem: (1) If MISSINGVALUE and "COMMAND LEGAL labelname" are used simultaneously, in displaying the legal values the values defined in the LABEL block get priority (and values MISSINGVALUE are not duplicated in the display). This would solve the problem described above, as well. (2) Alternatively, if the MISSINGVALUE is commented out EpiData uses only the values defined by RANGE or COMMAND LEGAL, but uses the values defined by the MISSINGVALUE command that is preceded by "*" for creating the missing value definition in the SPSS syntax. For example: * ---------------------------------------- LABELBLOCK LABEL variable 1 no 2 yes 8 "not applicable" 9 "no answer" END END variable COMMENT LEGAL variable * MISSINGVALUE 9 8 END * ---------------------------------------- would create the following SPSS syntax: * ---------------------------------------- VALUE LABELS variable (1) 'no' (2) 'yes' (8) 'not applicable' (9) 'no answer'. MISSING VALUES variable (9,8). * ---------------------------------------- Regards, Dirk ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

Export to SPSS, Variable names
by epidata-list＠lists.umanitoba.ca 24 Jun '05

24 Jun '05

Hello, I have a suggestion for the Epidata-Help-File, section "Export to SPSS": In Epidata you can use variable names (or field names) with a maximum of 10 characters. In newer versions of SPSS (12 or 13) you can use long variable names (64 Byte = 64 characters), in older versions only 8 characters. Exporting Epidata-fields with 10 characters to SPSS leads to shortened field names with 8 characters (for SPSS before Version 12). That causes a lot of work (e.g. renaming variables), if you think that 10 characters are exported. A hint in the Epidata-Help, that if the Data will be analysed in SPSS, the field names should have max. 8 characters, will be usefull. Greetings Juergen Spiegel *********************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: (0761) 28 83 64 Fax: (0761) 29 27 493 Web: www.fifas.de e-mail: info(a)fifas.de

1 0

How to: Change id variable type from numerical to string
by epidata-list＠lists.umanitoba.ca 17 Jun '05

17 Jun '05

A question that came to epidata.dk: > In our EPI test.rec file we have made a 'clientnumber' field for a > maximum of 7 numbers entry (#######), for example to enter > clientnumber 3458. This test.rec file contains now several records. > But now we need to use the same field for entering a letters and > digits combination, f.e. P3467188. > I realise that we should have designed a string field <a >>. > > The clientnumber field not only needs to be longer than 7 numbers but > should be suitable for letters as well. > > Is it possible to change that in our current test.rec file? We prefer > that over making a new .qes file and an empty .rec file. > This is of general interest. the solution: 0. Make sure you have proper backup in case something goes wrong. 1. Either add a new field in the qes file with the letter part add a new field for combined letter + number add 2. or make qes and change to string field the same field update the rec file (just enter and epidata will ask ) 3. If you wish to add a certain letter to all previously added records add a recode block to the chk file or other file and run recode from the tools menu. See help file on recode e.g. if new string type id field is idNew and the old numerical one is id recodeblock idletter = "F" idnew = idletter + string(id) end plus to accomplish future records in same file: idnew noenter end idletter mustenter end id mustenter after entry idnew = idletter + string(id) end end -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

RE: selecting on string variables
by epidata-list＠lists.umanitoba.ca 08 Jun '05

08 Jun '05

>>> <epidata-list(a)lists.umanitoba.ca> 25-05-2005 16:59:11 >>> Why is this necessary? I see "LION", upper case and delineated with " ". Thanks, Kelly Because assigning this : if recnumber = 2 then animal = "LION" to a stringvariable of length 10 gets the value: "LION " not the value "LION" Computers are stupid and the designer makes the choices. My choice is that "LION " is different than "LION" Someone would argue that we should always use the trimmed value of string variables, such that "LION " is the same as "LION" but this would give the user a problem if he/she wanted to compare the full length string. The strategy of EpiData for as well data entry as the coming release of analysis is that we make as few decisions as possible and let the end user decide. This is in contrast to other software developers who often impose new and changed strategies and changed ways of doing things on the users (Who is then forced to keep upgrading and learning new ways of doing what they could do with the old principle). EpiData tries NOT to invent new ways of doing things, but stick to the well founded principles of Epi6 (with appropriate extensions for those who wish to use the new principles of further documentation). Regards Jens Lauritsen Initiator of EpiData Coordinator EpiData Association

1 1

RE: [EpiData-list] value labels
by epidata-list＠lists.umanitoba.ca 03 Jun '05

03 Jun '05

Hi. It's possible to store comment legal values up to 80 characters long (EpiInfo / EpiData limit for string length). To do so, refer to a lookup table (see 'Comment legal' help section for that.) ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : jeudi 2 juin 2005 15:03 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] value labels Hello to all! I have being using data entry software for my work and that of epi data is very interesting and smooth but my problem is that it can not take long value label with 256 characters. Is there anyone that can give me a suggestion of defining value labels for a variable with long characters. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 27 May 2005 12:02:51 -0500 (CDT) Subject: EpiData-list Digest, Vol 19, Issue 9 > 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..." ------- End of Original Message -------

1 0

RE: [EpiData-list] Relational database
by epidata-list＠lists.umanitoba.ca 03 Jun '05

03 Jun '05

In order to add only 1 related record (thus automatically go back to 'mother' datafile as soon 1 related record has been saved, just add '1' (without ') at the end of the RELATE command Example: RELATE IDENTFIELD DATAFILE2.REC 1 Best regards, ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mercredi 1 juin 2005 16:36 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] Relational database Hello! I have long questionnaire, so I divided it into two parts using through relational database. At the end of part 2, the EpiData is starting again part 2, taking it as new subrecord. How can I let EpiData start new record in part 1 (i.e. for a new person)? Thank you in advance! /Ziad

1 0

Topics in EpiData-List
by epidata-list＠lists.umanitoba.ca 02 Jun '05

02 Jun '05

The EpiData-list has been set up with two topics today: Analysis Data Entry A topic is a way to selectively receive only part of the mails from the discussion list. By default ALL mails are sent to all users. Even annoying ones, such as when I forgot to turn off an "out of office" message to the list last week (excuses) and all users received a message in Danish. How does topics work ? If a user is signed up to only "analysis", then only mails which contain the word "analysis" in the subject line or the first 15 lines of text in the body of the message will be sent to that user. If you wish to receive all mail: You do not have to do anything. If you wish to select only mails for one or the other topic: Go to this page in your browser http://lists.umanitoba.ca/mailman/options/epidata-list and edit your user profile. Further information is given on that page. For all users it is always good practice to choose wording of the subject such that other users can see what this mail is about. This is particularly true when topics are in effect. Regarding release of analysis I can inform you that we are progressing, but some errors in the basic handling of selecting data has postponed the release. The problem is related to a valid way of separating float values, such as e.g. 3.1 from 3.100000000001 and 3.097865491 Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

value labels
by epidata-list＠lists.umanitoba.ca 02 Jun '05

02 Jun '05

Hello to all! I have being using data entry software for my work and that of epi data is very interesting and smooth but my problem is that it can not take long value label with 256 characters. Is there anyone that can give me a suggestion of defining value labels for a variable with long characters. SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Fri, 27 May 2005 12:02:51 -0500 (CDT) Subject: EpiData-list Digest, Vol 19, Issue 9 > 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..." ------- End of Original Message -------

1 0

Relational database
by epidata-list＠lists.umanitoba.ca 01 Jun '05

01 Jun '05

Hello! I have long questionnaire, so I divided it into two parts using through relational database. At the end of part 2, the EpiData is starting again part 2, taking it as new subrecord. How can I let EpiData start new record in part 1 (i.e. for a new person)? Thank you in advance! /Ziad

1 0

(no subject)
by epidata-list＠lists.umanitoba.ca 31 May '05

31 May '05

Hi!everyone. I just obtain EPIDATA and I find it very useful. But I cann't analyze the data with Spss. Does Epidata have fountion to transform *.rec to *.sav? 　　　　　　　　致礼！　　　　　　　　stephen 　　　　　　　　stephen_ling(a)163.com 　　　　　　　　　　2005-05-31

1 2