- EpiData-list - University of Manitoba Mailing Lists

combined numeric text variable
by epidata-list＠lists.umanitoba.ca 14 May '08

14 May '08

I want to create a variable that is numeric ## and text ___________________________ for a fill in response such as other. However, a combination of text and numeric within the same variable creates two variables. For statistical purposes I dont want to opt for text only. Suggestions? Susan Caplan, RN, MSN, FNP-BC Yale University PhD Student in Nursing

1 1

AW: EpiData-list Digest, Vol 55, Issue 6 - EpiData und Linux
by epidata-list＠lists.umanitoba.ca 13 May '08

13 May '08

Dear Mr. Lauritsen, i can test EpiData-Linux with GNU/Debian Linux 4.0r3. Yours sincerley, Dirk Cremer Stadt Bielefeld - Der Oberbürgermeister - Gesundheits-, Veterinär- & Lebensmittelüberwachungsamt Nikolaus-Dürkopp-Str. 5-9 33597 Bielefeld http://www.bielefeld.de (bitte Gesundheitsberichterstattung in die Suchfunktion eingeben) Auskunft gibt Ihnen: Dirk Cremer Gesundheitsberichterstattung Raum 217 Tel.: 0521 51-5022 Fax: 0521 51-3406 -----Ursprüngliche Nachricht----- Von: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] Im Auftrag von epidata-list-request(a)lists.umanitoba.ca Gesendet: Mittwoch, 7. Mai 2008 19:11 An: epidata-list(a)lists.umanitoba.ca Betreff: EpiData-list Digest, Vol 55, Issue 6 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: EpiData-list Digest, Vol 55, Issue 5 (epidata-list(a)lists.umanitoba.ca) 2. Date time combinations in epicurves (epidata-list(a)lists.umanitoba.ca) 3. Using attack rate table output in reports (epidata-list(a)lists.umanitoba.ca) 4. EpiData and linux (epidata-list(a)lists.umanitoba.ca) 5. Re: EpiData and linux (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 May 2008 20:29:14 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] RE: EpiData-list Digest, Vol 55, Issue 5 To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <30123C01C7D6EE46B6AAA1B1772331971E1447(a)491-mail.mrcad.mrc.ac.za> Content-Type: text/plain; charset="iso-8859-1" You are absolutely correct, once a duplicated number is entered, it will pop up "Number already exists, do you want to go to record????? As long as you type "key Unique 1" A Key Unique number can be altered if it was entered by mistake but if you select the ID as AUTO select, then that number which is generated by the computer can not be altered. Sandy MRC (South Africa) -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 06 May 2008 07:02 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 55, Issue 5 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: Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number (epidata-list(a)lists.umanitoba.ca) 2. Epidata with Ubuntu gusty (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 05 May 2008 19:16:22 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number To: epidata-list(a)lists.umanitoba.ca Message-ID: <481F40E6.4090109(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Pedro: Am I incorrect in opinionating that actually KEY UNIQUE gives you all answers as well, that an identifier value is already in existence and in which record it is and allowing you to go to precisely that previous record. Hans epidata-list(a)lists.umanitoba.ca wrote: > Gilles, > > All the anterior answers are correct. Hoewever I have a preference for > another command: > > idnumber > autosearch list > end > > This command does not exactly the same thing as key unique. I have > this preference because key unique does not allow U to enter a > previous entered number and does not warn you which record this number > is. Autoserach warns that this number is already in the dataset and > gives you the option to edit this one or to generate a new one. This > is handy when the mistake is in the first one. > For example... suppose you are entering data of questionnaire number > 12, but by mistake you enter 22 at the ID number. When you get on 22, > key unique only tells you U cant enter 22, becasue it is already in > the databank. Autosearch list will show you the record with ID 22 for > you to compare and see if this is the same you entering and allow you > to go to this > 22 and change it to 12 if necessary. > > Also, you may use them both at the same check if u like ... > > id > key unique > autosearch list > end > > Best regards, > Pedro Emmanuel > ------------------------------ Message: 2 Date: Mon, 5 May 2008 22:48:48 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Epidata with Ubuntu gusty To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0805051848m3464cc07x658fc4e4946d9157(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 5 ******************************************* ------------------------------ Message: 2 Date: Wed, 07 May 2008 08:20:35 +1200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Date time combinations in epicurves To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <001d01c8af63$0f2698f0$663b4979@acerc6bac00326> Content-Type: text/plain; charset=US-ASCII I saw an earlier thread on the list suggesting a date time variable in epi analysis or the option to show two variables such as day and hours in an epicurve. I would find this very helpful as for an outbreak I was asked to produce an epi curve, preferably grouped in 3 hourly lots, but certainly showing both date and hour of onset on one graph. The outbreak data was entered into Epidata and as Epidata doesn't have a datetime field information about when people first became sick was stored in two different fields - onsetday (a date field) and onsettime (a numeric field entered as a 24 hour clock). There are three different onset days and a range of onsettimes in each day. I couldn't think of a way of putting both pieces of information on one graph in either epidata analysis or epi info (though in epi info you can group the hours and it will make you a different graph for each day), so finally I exported the data to Excel, grouped the data manually and then graphed it that way. Does anyone have a better suggestion about how to make an epicurv that includes both date and time information? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ------------------------------ Message: 3 Date: Wed, 07 May 2008 08:19:05 +1200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Using attack rate table output in reports To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <001d01c8af63$0f2698f0$663b4979@acerc6bac00326> Content-Type: text/plain; charset=US-ASCII First to say how great the outbreak analysis option is in Epi analysis. Instead of slowly cutting and pasting or copying information from a whole series of 2 by 2 tables as in Epi Info as I used to, I can now quickly create an attack rate table with for all exposures of interest including not just attack rates in the exposed and unexposed, but relative risks, p values and confidence intervals though that one command. I am helping analyse an outbreak at the moment and it has saved me lots of time, thank you very much. I am still learning about working with the output though, so what I am interested to learn from others is if you are using epi analysis attack rate output table in reports written in microsoft word and if so how. I was asked to provide the table in a version that could be incorporated in a write up about the outbreak to be written in MS word . My method was to 1. open microsoft word 2. chose insert file (making sure all files option was selected) 3. Insert the epianalysis htm file containing the table 4. Use table/select table and autoformat/grid 5. Do a small amount of re-formating This resulted in a table that looked OK in an MS word document - but is there a better way to do it? Also how do you change the default filename and path from EAoutput.htm to something else? I have another question about the epicurv but will email separately thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ------------------------------ Message: 4 Date: Wed, 07 May 2008 17:07:54 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData and linux To: epidata-list(a)lists.umanitoba.ca Message-ID: <4821C5CA.2070107(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed It would be good to form a kind of "EpiData Linux group" - I have allocated some of the development funding for getting into "linux". This is expected to start mid 2008. If we are to be succesfull it is of utmost importance, that some key users in each operating system will take part of the testing etc. Therefore the question yesterday on experiences comes in very handy, since the experiences will be part of "how and what to consider", when converting EpiData Entry from a "windows only" to a "multiplatform software". regards Jens Lauritsen EpiData Association ------------------------------ Message: 5 Date: Wed, 07 May 2008 11:32:41 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] EpiData and linux To: epidata-list(a)lists.umanitoba.ca Message-ID: <4821D9A9.2040102(a)binghamton.edu> Content-Type: text/plain; charset=ISO-8859-1 I would love to test a version of EpiData on Linux. I use Kanotix, a Debian-based distro. Sadly, I have no coding skills to contribute. --Chris Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 40 Arch Street, Johnson City, NY 13790 cryanatbinghamtondotedu PGP public keys available at http://home.stny.rr.com/ryancw/ "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery] epidata-list(a)lists.umanitoba.ca wrote: > It would be good to form a kind of "EpiData Linux group" - > > I have allocated some of the development funding for getting into "linux". > > This is expected to start mid 2008. If we are to be succesfull it is of > utmost importance, that some key users in each operating system will > take part of the testing etc. > > Therefore the question yesterday on experiences comes in very handy, > since the experiences will be part of "how and what to consider", when > converting EpiData Entry from a "windows only" to a "multiplatform > software". > > regards > > 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 55, Issue 6 *******************************************

1 0

Attachments on EpiDatalist - do not use.
by epidata-list＠lists.umanitoba.ca 09 May '08

09 May '08

The EpiData list is planned as a "list without attachments". The problem of attachments is that sometimes they work only if users have certain software. (Apart from EpiData software). In general all attachments will be stripped (deleted), but sometimes the filters for this are not sufficient. The advice for users is to: A. Send mail as TEXT only mail to the list B. Try to generalise the statements in standard text C. Keep volumen low, since with slow internet connections the contents gets to be a problem. There is a limit on size in the list. If we run into problems I might change the limit (up or down). In other words. Attachments gives different users problems. So please send your questions as ordinary text only. Extended documentation or files can be the user be uploaded to that users own website. And then in the posting to the list refer to that site, where the file is placed. regards Jens Lauritsen EpiData Association

1 0

value labels
by epidata-list＠lists.umanitoba.ca 09 May '08

09 May '08

Please see attachment.

1 1

How to: Time variables and Epicurves (grouping by hours)
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

Christine asked how to create efficient epicurves with an X axis grouping in time intervals. I think the efficient way would be to change your date/time variables into hours since observation or a given day. Then cut the x-axis and work a bit on labelling. That might sound easier than done (would take some time of experimentation). But for the development plan I think we should consider adding easier ways of doing that. E.g. to allow epicurve to scale the axis with different groupings, but also to find ways of managing time/date situations. Some hints to the solution could be along these lines - A test could be: variables: dateonset : date of first symptom timeonset: hour at which the symptom came on that date (say the observations start on 1st of May this year) case: at least one positive symptom * generate 50 test observations and an epicurve grouped by 3: Close generate 50 gen d dateonset=dmy(1,5,2008)+(recnumber mod 3) gen i timeonset = 24 mod recnumber gen i timevar = 24*(dateonset - dmy(1,5,2008)) + timeonset gen i case = recnumber mod 2 * epicurve by hour would then be epicurve timevar case * recode hours to grouped hours by 3: define time3 ### recode timevar to time3 by 3 tab time3 * show epicurve: epicurve time3 case /xinc=3 /ti="Epicurve for ..... cases in 3 hour groups since start" Notice that the time3 variable will have labels, but currently these are not added to the graph. But for just showing the graph the lines would work. regards Jens Lauritsen EpiData Association

1 0

Copying tables and graphs from analysis to a report
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

1. manipulating file names and positions. The output saved by command "openlog" can be placed anywhere, include the path you like, e.g.: logclose logopen "f:\australia\outbreak\first attempt\logfile 1.htm" 2. Copying graphs from output: To get graphs from output can be done in several ways: a1. produce a single graph. b1 switch to an open "other application", e.g. textprocessing. press ctrl+v (and the graph as added as a wmf editable file) a2. point at a graph in output with the mouse. b2. right click on that graph and "copy to clipboard" c2. switch to the other application and press : Ctrl+V the graph is added as a bmp file (non-editable) a3. produce the graph and add the /save="Myfile" option You can specify graph format with a set command. 3. Copy tables: a. produce a table in output. b. add en empty line at the bottom of the screen by putting a period "." in the command prompt and pressing enter c. mark the table from the command to the line after the table as a block d. right click within the block. e. Choose either "copy as text" or "copy as html". f. Switch to other application and press ctrl+V (or insert special). with text you get tab delimited text copied, with html a formatted table (if the recipient can take in such a table) regards Jens Lauritsen EpiData Association

1 0

EpiData and linux
by epidata-list＠lists.umanitoba.ca 07 May '08

07 May '08

It would be good to form a kind of "EpiData Linux group" - I have allocated some of the development funding for getting into "linux". This is expected to start mid 2008. If we are to be succesfull it is of utmost importance, that some key users in each operating system will take part of the testing etc. Therefore the question yesterday on experiences comes in very handy, since the experiences will be part of "how and what to consider", when converting EpiData Entry from a "windows only" to a "multiplatform software". regards Jens Lauritsen EpiData Association

1 1

Date time combinations in epicurves
by epidata-list＠lists.umanitoba.ca 06 May '08

06 May '08

I saw an earlier thread on the list suggesting a date time variable in epi analysis or the option to show two variables such as day and hours in an epicurve. I would find this very helpful as for an outbreak I was asked to produce an epi curve, preferably grouped in 3 hourly lots, but certainly showing both date and hour of onset on one graph. The outbreak data was entered into Epidata and as Epidata doesn't have a datetime field information about when people first became sick was stored in two different fields - onsetday (a date field) and onsettime (a numeric field entered as a 24 hour clock). There are three different onset days and a range of onsettimes in each day. I couldn't think of a way of putting both pieces of information on one graph in either epidata analysis or epi info (though in epi info you can group the hours and it will make you a different graph for each day), so finally I exported the data to Excel, grouped the data manually and then graphed it that way. Does anyone have a better suggestion about how to make an epicurv that includes both date and time information? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 0

RE: EpiData-list Digest, Vol 55, Issue 5
by epidata-list＠lists.umanitoba.ca 06 May '08

06 May '08

You are absolutely correct, once a duplicated number is entered, it will pop up "Number already exists, do you want to go to record????? As long as you type "key Unique 1" A Key Unique number can be altered if it was entered by mistake but if you select the ID as AUTO select, then that number which is generated by the computer can not be altered. Sandy MRC (South Africa) -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: 06 May 2008 07:02 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 55, Issue 5 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: Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number (epidata-list(a)lists.umanitoba.ca) 2. Epidata with Ubuntu gusty (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 05 May 2008 19:16:22 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 55, Issue 3 Unique ID number To: epidata-list(a)lists.umanitoba.ca Message-ID: <481F40E6.4090109(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Pedro: Am I incorrect in opinionating that actually KEY UNIQUE gives you all answers as well, that an identifier value is already in existence and in which record it is and allowing you to go to precisely that previous record. Hans epidata-list(a)lists.umanitoba.ca wrote: > Gilles, > > All the anterior answers are correct. Hoewever I have a preference for > another command: > > idnumber > autosearch list > end > > This command does not exactly the same thing as key unique. I have this > preference because key unique does not allow U to enter a previous entered > number and does not warn you which record this number is. Autoserach warns > that this number is already in the dataset and gives you the option to edit > this one or to generate a new one. This is handy when the mistake is in the > first one. > For example... suppose you are entering data of questionnaire number 12, > but by mistake you enter 22 at the ID number. When you get on 22, key > unique only tells you U cant enter 22, becasue it is already in the > databank. Autosearch list will show you the record with ID 22 for you to > compare and see if this is the same you entering and allow you to go to this > 22 and change it to 12 if necessary. > > Also, you may use them both at the same check if u like ... > > id > key unique > autosearch list > end > > Best regards, > Pedro Emmanuel > ------------------------------ Message: 2 Date: Mon, 5 May 2008 22:48:48 -0300 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Epidata with Ubuntu gusty To: epidata-list(a)lists.umanitoba.ca Message-ID: <a37cfb5a0805051848m3464cc07x658fc4e4946d9157(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 55, Issue 5 *******************************************

1 0

Epidata with Ubuntu gusty
by epidata-list＠lists.umanitoba.ca 05 May '08

05 May '08

Hello all, I tryed to install Epidata in Ubuntu today and it seems to work fine at first. I looked at the web page and old messages at the list but latest one were from 2004. The installation looked pretty simlpe with wine already installed. Just click on it and wine seems to do the rest. Choose the directory as in windows .... press continue... At first it seems a little weird ... the installation and the program were not in portuguese but in english. There is a lot of violations errors when opening and closing files and sometimes epidata just dont open the files. Some simple commands in windows such as Ctrl+Z dont work. I try to import a simple dataset from a csv file with 6 variables and 45 observations and the same error did not allow me to complete the import.... the ID variable is not compatible. The ID variable was a number from 1 to 45. I try even to delete some variables eand most of observations to make it simple but it didnt work out. Does anyone have recent experiences with Epidata in Linux? Good or bad? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0