- EpiData-list - University of Manitoba Mailing Lists

Updated Manager and EntryClient available for testing
by epidata-list＠lists.umanitoba.ca 06 May '11

06 May '11

Dear All. An update version of the Manager and EntryClient is available for download on http://www.epidata.dk/testing.php This release is mainly focus on adding new features for controlling field entry, but does also include some rare-case bugfixes. Dues to changes in the project file structure, loading .epx/.epz files from previous versions of Manager and EntryClient will not be possible. However, we do hope that with the added features of todays test releases, we are very close to a settled "version 1" of the project file structure. As always, an updated version of the sample file is included in the downloads. The major changes for both Manager and Entry client are: 1. Fields may have notes attached. These are written in the Manager and can be read in EntryClient using F12. 2. Write the label part of a ValueLabel to a string field. 3. Fields may have a default value. 4. Fields can repeat value from previous record. 5. Simple calcaulation may be performed on exiting fields. (In old epidata known as AFTER ENTRY). These calculations are limited to 3 different types: a) Calculate the difference in time between two dates and/or times. b) Create a date based on a day, month and year field (integers). c) Combine 1-3 fields into a string field. 6. Compare two fields and require entry to respect the comparison. Eg. DateField2 > DateField1. 7. Force EntryClient to show the list of valuelabels associated with a field (manually show by pressing F9/+). Changes related only to Manager: 1. Large rearrangement of the Field Properties form. We have tried to group most used properties and logically connected propertied together. 2. Added tool for packing dataset. Removes records marked for deletion (see below). 3. Added Study information to Project settings form. Changes related only to EntryClient: 1. Search functionality: Ctrl+Shift+F: Show search dialog. Ctrl+F: Show search dialog filled with current entry for record. Ctrl+L: Do NOT show search dialog, but search with current entry and display a list of matching records. F3: Repeat last search in forward direction. Shift+F3: Repeat last search in backwards direction. 2. Updated graphical interface of program settings (Alt+S). 3. Records may be marked for deletion. See buttons beside record number. Kind regards, Torsten Christiansen. EpiData Association.

1 1

Suggestion: To go forward relational database and complex jumps with Entry Client and Manager
by epidata-list＠lists.umanitoba.ca 03 May '11

03 May '11

Hello: Sometimes I find out a bug on the EpiData testing version of the EpiData Entry Client and the Manager, using GNU/Linux. We are having some days without a very difficult bug to appear on the version. So I suggest to the programming team to go forward other steps like: 1) Relational database function and interface 2) To a more complex way to make jumps and conditional entry. Regards, -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 0

Re: EpiData-list Digest, Vol 90, Issue 2
by epidata-list＠lists.umanitoba.ca 25 Apr '11

25 Apr '11

My English is bad and I apologize for that. My research instrument contains 21 questions to be answered for 12 disciplines in a course. The number of respondents is approximately 100 people. Each question will be answered for all disciplines. I am attaching an example with three questions (one question for each file.) When finished entering the data of 12 disciplines in question 3, I want go to the file Quest which is the first issue, data entry of a new student. Note that I used the RELATE command in questions 1 and 2. FQ2 AFTER ENTRY IF fq2=1 THEN RELATE QUEST q3 ENDIF END END -------------------------------------- Silvano Cesar da Costa Departamento de Estatística Universidade Estadual de Londrina Fone: 3371-4346 -------------------------------------- ----- Original Message ----- From: <epidata-list-request(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Sent: Thursday, April 21, 2011 2:00 PM Subject: EpiData-list Digest, Vol 90, Issue 2 > 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: Multiple files (epidata-list(a)lists.umanitoba.ca) > 2. Re: Multiple files (epidata-list(a)lists.umanitoba.ca) > 3. Re: Multiple files (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Apr 2011 20:11:32 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Multiple files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4DAF21D4.9080203(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > You should look at the command "relate" in the help file. > > To see a specific implementation I suggest you download > these three and > look at the check files: > *1 Relate example - Clinical Study with four forms > **2 Relate example - Multilevel, Village, Family, Person - > Nutritional > survey of region in Burkina Faso > **3 Relate example - hospital infections - 3 examples* > > You find it all at http://www.epidata.dk/examples.php > > Let us know how it works at the end - your example could > be added to the > examples page. > (without proper data obviously) > > regards > Jens Lauritsen > EpiData Association > > On 2011-04-20 16:26, epidata-list(a)lists.umanitoba.ca > wrote: >> Hi, >> >> I have a main file (Quest) and 21 related files. >> >> At the end of the input data file 21 that want to go back >> to >> the file Quest for new entry. >> How? >> >> I tried: >> >> FQ21 >> AFTER ENTRY >> IF FQ21=1 THEN >> GOTO WRITE >> ENDIF >> END >> END >> >> and >> >> FQ21 >> AFTER ENTRY >> IF FQ21=1 THEN >> GOTO QUEST >> ENDIF >> END >> END >> >> >> >> -------------------------------------- >> Silvano Cesar da Costa >> Departamento de Estatística >> Universidade Estadual de Londrina >> Fone: 3371-4346 >> -------------------------------------- >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> > > > > ------------------------------ > > Message: 2 > Date: Wed, 20 Apr 2011 19:52:08 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Multiple files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4DAF1D48.7010801(a)tbrieder.org> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > You probably mean "records" rather than files? > > If so, it is simple, no commands are needed in the CHK > file of the > related file, just press F10 to return to the parent file, > whenever you > have entered the last of the child records belonging to > one given parent. > > Hans > > > On 20:59, epidata-list(a)lists.umanitoba.ca wrote: >> Hi, >> >> I have a main file (Quest) and 21 related files. >> >> At the end of the input data file 21 that want to go back >> to >> the file Quest for new entry. >> How? >> >> I tried: >> >> FQ21 >> AFTER ENTRY >> IF FQ21=THEN >> GOTO WRITE >> ENDIF >> END >> END >> >> and >> >> FQ21 >> AFTER ENTRY >> IF FQ21=THEN >> GOTO QUEST >> ENDIF >> END >> END >> >> >> >> -------------------------------------- >> Silvano Cesar da Costa >> Departamento de Estatística >> Universidade Estadual de Londrina >> Fone: 3371-4346 >> -------------------------------------- >> > > -- > Hans L Rieder, MD, MPH > Jetzikofenstr 12 > 3038 Kirchlindach > Switzerland > > Tel: +41 31 829 4577 > Mob: +41 79 321 9122 > Web: http://www.tbrieder.org > > > > > ------------------------------ > > Message: 3 > Date: Thu, 21 Apr 2011 07:54:51 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Re: Multiple files > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <BANLkTimQxHVydfC2buhj=We2vtM4MiXSjw(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear Silvano Cesar da Costa, > One reliable way to approach this is to close the files in > reverse order > until the edit pencil is pointed to the start(in your case > may be file 1). > *As general rule*: To enter data in relational database > you must either move > down the tree through the field that contains the Relate > command, or move up > the tree by closing the rec.files. On closing file21.rec > the cursor should > go back to file20.rec so on. > Pressing F10 or CTRL+R ( return key) closes the file and > moves the > cursor/edit pencil back one level to the data files that > called RELATE. > > Hope this would help. > > Tieble > > On 20 April 2011 18:13, > <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. Multiple files (epidata-list(a)lists.umanitoba.ca) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Wed, 20 Apr 2011 11:26:20 -0300 >> From: epidata-list(a)lists.umanitoba.ca >> Subject: [EpiData-list] Multiple files >> To: <epidata-list(a)lists.umanitoba.ca> >> Message-ID: <77996779913E437DA44EEBB3B0E9F6FA@ccePC> >> Content-Type: text/plain; format=flowed; >> charset="iso-8859-1"; >> reply-type=response >> >> Hi, >> >> I have a main file (Quest) and 21 related files. >> >> At the end of the input data file 21 that want to go >> back >> to >> the file Quest for new entry. >> How? >> >> I tried: >> >> FQ21 >> AFTER ENTRY >> IF FQ21=1 THEN >> GOTO WRITE >> ENDIF >> END >> END >> >> and >> >> FQ21 >> AFTER ENTRY >> IF FQ21=1 THEN >> GOTO QUEST >> ENDIF >> END >> END >> >> >> >> -------------------------------------- >> Silvano Cesar da Costa >> Departamento de Estatística >> Universidade Estadual de Londrina >> Fone: 3371-4346 >> -------------------------------------- >> >> >> >> ------------------------------ >> >> ________________________________________ >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list >> >> >> End of EpiData-list Digest, Vol 90, 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/> > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 90, Issue 2 > ******************************************* >

1 1

Re: Multiple files
by epidata-list＠lists.umanitoba.ca 21 Apr '11

21 Apr '11

Dear Silvano Cesar da Costa, One reliable way to approach this is to close the files in reverse order until the edit pencil is pointed to the start(in your case may be file 1). *As general rule*: To enter data in relational database you must either move down the tree through the field that contains the Relate command, or move up the tree by closing the rec.files. On closing file21.rec the cursor should go back to file20.rec so on. Pressing F10 or CTRL+R ( return key) closes the file and moves the cursor/edit pencil back one level to the data files that called RELATE. Hope this would help. Tieble On 20 April 2011 18:13, <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. Multiple files (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Apr 2011 11:26:20 -0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Multiple files > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <77996779913E437DA44EEBB3B0E9F6FA@ccePC> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=response > > Hi, > > I have a main file (Quest) and 21 related files. > > At the end of the input data file 21 that want to go back > to > the file Quest for new entry. > How? > > I tried: > > FQ21 > AFTER ENTRY > IF FQ21=1 THEN > GOTO WRITE > ENDIF > END > END > > and > > FQ21 > AFTER ENTRY > IF FQ21=1 THEN > GOTO QUEST > ENDIF > END > END > > > > -------------------------------------- > Silvano Cesar da Costa > Departamento de Estatística > Universidade Estadual de Londrina > Fone: 3371-4346 > -------------------------------------- > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 90, 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

Multiple files
by epidata-list＠lists.umanitoba.ca 20 Apr '11

20 Apr '11

Hi, I have a main file (Quest) and 21 related files. At the end of the input data file 21 that want to go back to the file Quest for new entry. How? I tried: FQ21 AFTER ENTRY IF FQ21=1 THEN GOTO WRITE ENDIF END END and FQ21 AFTER ENTRY IF FQ21=1 THEN GOTO QUEST ENDIF END END -------------------------------------- Silvano Cesar da Costa Departamento de Estatística Universidade Estadual de Londrina Fone: 3371-4346 --------------------------------------

1 2

Analysis: graph creating GUI bug?
by epidata-list＠lists.umanitoba.ca 30 Mar '11

30 Mar '11

Hello all, I noticed that the GUI which allows you to create histograms (Graph -> Histogram) does not let you specify a boolean variable as "by" variable. Example: . read C:\EpiData\TestData\bromar.rec . select dectime<>. . gen b fast=(dectime<3.87) it is possible to do the following: . his age /by=fast but the GUI form does not list "fast" as a "by" variable. Kind regards, Simon PS: I tried to report this on flyspray, but I get a "Error #23: User or group not enabled for login." when I try to log in.

1 2

New EpiData EntryClient version release for test
by epidata-list＠lists.umanitoba.ca 29 Mar '11

29 Mar '11

Dear List A new version of the EpiData EntryClient program have been release for testing today. Due to a significant bug in jumps, where the program would end up in an infinite loop, we have decided to release a new version where this problem is no longer present. Since the sample file contains a contruct that could activate this bug, we strongly recommend all using the old version of EpiData EntryClient (0.3.2.0) to update to the new version. With kind regards, Torsten Bonde Christiansen EpiData Association.

1 1

Clarification of how to work from now on
by epidata-list＠lists.umanitoba.ca 23 Mar '11

23 Mar '11

Dear all Many of the messages I have added to the list recently are rather technical in nature. This is just a short notice on how mode of work will be from now on: Until now - since 1999 and 2003/4 we have: Data definition, docuemtation and Entry: Epidata Entry Analysis: EpiData Analysis From now on: The manager: The project manager creates data entry forms and structures data collection using the software "EpiData (data) Manager". This can be used in a "point and click" manner visually including adding checks, jumps and ranges. Once the database is structured and ready. The file, e.g. outbreak.epx can be given to those entering data. The one "physical" file contains all information including definition of fields, range, value labels, jumps etc. The data entry person would then acquire the "EpiData EntryClient", which can be used to enter actual data into the file. Adding records just as in the current EpiData Entry software. In other words we separated current functionality into: Project management, data definition and documentation: EpiData Manager Data Entry: Epidata EntryClient Analysis: EpiData Analysis All of these are available from the testing page: Http://www.epidata.dk/testing.php We are now (struggling) to implement all decided functionality, such that a public release will be available as soon as possible. There is still some adaptations and developments to do, but we are approaching the public release. It is therefore welcomed that you look at the new software and join the commenting on the EpiData List - just as many of you have already done. Regards Jens Lauritsen EpiData Association

1 3

BoxPlot with 3 variables
by epidata-list＠lists.umanitoba.ca 23 Mar '11

23 Mar '11

Dear EpiData users, How to make a Boxplot when I have one quantitative variable and two qualitatives variablesThanks __________________________________ Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Info. Médicale UFR Sciences Médicale, U. Abidjan-Cocody 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 493 334 GSM: (+225) 08 167 578 / 02 724 162 skype's: dibykonanjp

1 1

Updated EpiData Manager
by epidata-list＠lists.umanitoba.ca 21 Mar '11

21 Mar '11

Dear EpiData users. Due to a significant bug in the previous version (0.7.1) of EpiData Manager, posted on the testing page last week, a new version has been upload today already. The bug impacted the use of "Import Structure" which could cause problem with saving the project, fields could be missing the field name and other strange problems could follow. Please be advised to download the new version uploaded today to avoid any of these problems. With kind regards, Torsten Bonde Christiansen EpiData Association.

1 1

WRITENOTE command
by epidata-list＠lists.umanitoba.ca 21 Mar '11

21 Mar '11

When writing a comment into a .NOT file, I can display the ID number by @<field name>, e.g. where the field name is babyid: * WRITENOTE "Comments or additional information for baby ID @babyid" SHOW I tried doing this with 2 fields (the combination of babyid and wksdate is unique): * WRITENOTE "Comments or additional information for baby ID @babyid and Week Starting date @wksdate" SHOW However only the value of wksdate is displayed. How can I display the values of both fields? My work around is to create a variable that's a combination of babyid and wksdate, but I'm wondering if there's a more straightforward way to do it. 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

Can I start translating the spanish wiki?
by epidata-list＠lists.umanitoba.ca 20 Mar '11

20 Mar '11

Hello: Maybe is very soon to do this but I offer my help editing the spanish version of the wiki on my free time. Regards, -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 0

epx versus EPX , analysis and problems in test release
by epidata-list＠lists.umanitoba.ca 19 Mar '11

19 Mar '11

When working with files in windows there is no difference btw. "chk" and "CHK" as extension for a file, however in Linux (possibly also in MAC) there is a difference. This is also relevant for EPX versus epx. It turns out that apparently the new batch processor "epidatacmd" can give problems when creating files due to problems of "EPX" versus "epx" extensions. WHen using these files on a Linux pc a file with the name myfile.EPX will not show up on the "supported files", list in manager or client. Other issues when working with the latest released Manager and EntryClient I have found are: a. Sometimes "access violation" occurs when I change the setting in Manager of "showing variable names" or not. b. Sometimes single files created from templates with the epidatacmd processor and subsequently combined in the Manager with "import structure" cannot be read by EpiDataClient. These errors will be fixed - these are examples of why testing is important on the path to the first public release. An updated Analysis (build 175) has been placed on the http://epidata.dk/testing.php. The only change is adaptation of reading epx files with the most recent changes to the epx structure. regards Jens Lauritsen EpiData Association .....................................................................................

1 0

RE: [EpiData-list] Re: EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 17 Mar '11

17 Mar '11

Dear Sam: You have your unique identifier for the parent file that is "inherited" by the child file. In the child file your create a unique identifier for that (simple is a construct of the parent identifier plus the date, if each child event happens on a different date). For validation, you compare the two parent files and the two child files, and that's it. Best regards, Hans Hi, The only problem with this solution is that I then cannot use the double entry method that compares responses as they are keyed in. As far as I know, it is not possible to do that with relational files. Thanks, Sam -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re: EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 17 Mar '11

17 Mar '11

Hi Sam, To add on Jens's suggestion, you could also give very short name to your variables without much description and fit all within required lines. Otherwise I would recommend relational rec.files (with full description of each var to avoid suffering at the data cleaning stage) and merge them at the end. Best wishes Tieble <http://www.mgavm.ru/>

1 2

Updated Manager and EntryClient for testing
by epidata-list＠lists.umanitoba.ca 17 Mar '11

17 Mar '11

Dear All We are (rapidly) approaching the first public release (not being a test version) of the updated software, which shifts to an XML based data structure. An updated version of the Manager and EntryClient has been placed for download on http://www.epidata.dk/testing.php Apart from several bug-fixes these are the main aspects: 1. We have created a new command line tool which can create dataforms, including setting of value labels, range and jumps (as announced yesterday), from a text file. 2. We have chosen - as previously announced - to discontinue "paste as qes" in Manager as a consequence of point 1. 3. The Manager can now add structure from several files to a dataform. e.g. for outbreak analysis one could have dataforms (epx files) for: diary fish meat vegetable drinks dessert etc. To create a data collection form for a specific outbreak: 1. Start manager and create a new project 2. Point at all relevant files E.g.: drinks, fish, vegetable 3. Change sequence of files in the grid showing the files chosen 4. The manager will then add the files. 5. Finetune the created combined file - e.g. add more jumps or specifications. The focus on ability to create a database in batch with Epidatacmd is part of an ECDC (European Union) funded project, which will be announced in detail later. The project is part of collaboration with Statens Serum Institut in Denmark (ssi.dk) and the similar Norwegian institute. The funding is currently coming from the ECDC project, plus donations and collaborations as shown on the http://epidata.dk/funding.htm page, including APHEO and MSF. But I do see the need for more funding to conclude the rewriting of Analysis plus remaining aspects of Manager plus EntryClient. I will actively seek this in the coming time. (Ideas welcomed). The development of the Manager and EntryCLient will focus on remaining issues before final public release. These include: size of font, printing, searching, key unique, repeat, validate dublicate files etc. All programming done by Torsten Christiansen. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 89, Issue 2
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Dear Jamie, I managed to download wine bottler.dmg but failed to open it saying it cannot be recognized. Is there any additional things I need to do before opening it Rgds Al > > > ------------------------------ > > Message: 2 > Date: Tue, 15 Mar 2011 09:53:04 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData for Mac > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP51DE60B63BA698DF05BEF1FDCF0(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > Hi Aloysius, > > I've been using EpiData on my MacBook for the past year with no real problem. > > The old version (Entry, Analysis) run well under the Wine emulator. I > installed Winebottler (http://winebottler.kronenberg.org/) and then just > launch windows .exe files as if they were MAC applications. You can safely > install Winebottler and then forget about it. > > All of the EpiData documentation applies. Winebottler provides you with a > folder that acts like your C: drive and the rest of your MAC hard drive looks > like a Z: drive. > > The only problem I have had is using help for Entry, where you cannot see some > help pages. I'm not sure why. Analysis works with no problem. > > Your other approach would be to use Bootcamp to run Windows/XP. I didn't want > to do that. > > Jamie > > On 2011-03-15, Aloysius wrote: > >> I have just started using Epidata and I own a mac. There seem to be no >> detailed help guides to help follow and use the Mac version. Is it that its >> still under development? Is there anyone with access to this document > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 89, Issue 2 > *******************************************

1 1

new test release of EpiDataCmd batch processor (template tool)
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Dear All Today a new software release for testing has been placed on Http://www.epidata.dk/testing.php Current test release is for Linux and Windows only. Mac version follows. The intention of this tool is that the user can produce standard epx files based on a template defining dataforms. Full documentation of the format is found at: http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat The epidatacmd command line tool will create EpiData xml files based on template files.: Template files should be using UTF-8 To see options: epidatacmd -h Example file included: templatesample.tmpl to execute this: linux: ./epidatacmd template -i templatesample.tmpl -o diary.epx windows: epidatacmd template -i templatesample.tmpl -o diary.epx EpiData Association, Denmark, 2011-March Programming: Torsten Christiansen (TC) Design: Jens Lauritsen and TC

1 0

Re: EpiData-list Digest, Vol 89, Issue 2
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Hi All, I do not know how to design data entry form for pre and post test training course to we can compare how to improve of each person before and after training coures. Wish help of all. Best, Linh On Wed, Mar 16, 2011 at 12:18 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. EpiData for Mac (epidata-list(a)lists.umanitoba.ca) > 2. Re: EpiData for Mac (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Mar 2011 15:40:33 +0300 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] EpiData for Mac > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <C9A538F1.5AC1%ASSEMAGANDA(a)IAVI.OR.UG> > Content-Type: text/plain; charset="iso-8859-1" > > Dear EpiData colleagues, > I have just started using Epidata and I own a mac. There seem to be no > detailed help guides to help follow and use the Mac version. Is it that its > still under development? Is there anyone with access to this document > > Kind Regards > Aloysius Ssemaganda > UVRI/IAVI HIV Vaccine Program > Uganda Virus Research Institute > P.O.Box 49 Entebbe,Uganda. > Tel: +256 414 322 377/8,+256 414 321 094 > Cell: +256 782 334 633 > Fax: + 256 414 321 124 > Email: assemaganda(a)iavi.or.ug or assemaganda(a)gmail.com > > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 15 Mar 2011 09:53:04 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] EpiData for Mac > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP51DE60B63BA698DF05BEF1FDCF0(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > Hi Aloysius, > > I've been using EpiData on my MacBook for the past year with no real > problem. > > The old version (Entry, Analysis) run well under the Wine emulator. I > installed Winebottler (http://winebottler.kronenberg.org/) and then just > launch windows .exe files as if they were MAC applications. You can safely > install Winebottler and then forget about it. > > All of the EpiData documentation applies. Winebottler provides you with a > folder that acts like your C: drive and the rest of your MAC hard drive > looks like a Z: drive. > > The only problem I have had is using help for Entry, where you cannot see > some help pages. I'm not sure why. Analysis works with no problem. > > Your other approach would be to use Bootcamp to run Windows/XP. I didn't > want to do that. > > Jamie > > On 2011-03-15, Aloysius wrote: > > > I have just started using Epidata and I own a mac. There seem to be no > > detailed help guides to help follow and use the Mac version. Is it that > its > > still under development? Is there anyone with access to this document > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 89, Issue 2 > ******************************************* > -- ================================== Nguyen Thi Linh Institute of Social and Medical Studies No 17, Residence of Cau Giay District Health Center. Alley 1, Nguyen Thi Dinh Street-Cau Giay-Ha Noi Phone: 84-4-35558288 ext. 105 Cell: 0977.999.087 Fax: 84-4-35558274 Website: www.isms.org.vn www.newcare.com.vn

1 0

Re: EpiData-list Digest, Vol 89, Issue 1
by epidata-list＠lists.umanitoba.ca 16 Mar '11

16 Mar '11

Thank you Jens for suggestion. It was helpful. I was trying to automate at entry, so did the following and it works, MSM RANGE 0 9 AFTER ENTRY IF (a = 1) and (b=0) THEN MSM=0 ENDIF IF (a = 1) and (b= 1) THEN MSM=1 ENDIF IF (a = 1) and (b= 1) and (c= 0) THEN MSM=2 ENDIF IF (a = 1) and (b= 1) and (c= 1) THEN MSM=3 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 0) THEN MSM=0 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 1) THEN MSM=4 ENDIF IF (a = 1) and (b= 1) and (c= 1) and (d = 1) and (e=0) THEN MSM=9 ENDIF END END *Bijay Adhikari*, PhD, MPH, DVM Prov. Communicable Disease Epidemiologist Population Health Branch Saskatchewan Ministry of Health Regina, SK Canada On Sat, Mar 12, 2011 at 12:00 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. Conditional formula (epidata-list(a)lists.umanitoba.ca) > 2. Re: Conditional formula (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 11 Mar 2011 18:43:02 -0600 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Conditional formula > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <AANLkTik4syh1ti3z-sqV=SA+ULthRgmLrfYYxjpj_H-m(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello Epidata users, I am having problem to code conditional formula in > epidata as described below, can anyone suggest how to code to the following > condition, > > If a= 1 and b = 1 then exposure= K > > If a= 1 and b = 0 then exposure= K > > If a= 1 and b = 1 and c= 1 then exposure= K > > If a= 1 and b = 1 and c= 1 and d=0 then exposure= K > > If a= 1 and b = 1 and c= 1 and d=1 then exposure= K > > else exposure= K1 > > Thanks > > > -- > *Dr. Bijay Adhikari*, PhD, MPH, DVM* > Prov. Communicable Disease Epidemiologist > Population Health Branch > Saskatchewan Ministry of Health > Regina, SK Canada > > > ------------------------------ > > Message: 2 > Date: Sat, 12 Mar 2011 10:45:12 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Conditional formula > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4D7B40A8.8080601(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello Epidata users, I am having problem to code conditional formula in > > epidata as described below, can anyone suggest how to code to the > following > > condition, > I think the problem is that you should use more parenthesis. Is this in > analysis or in entry ? > > I assume analysis: > > * first create the integer variable k: > define k # > * or you could use the gen statement: "i" makes this an integer variable > gen i k = 0 > > * give labels > labelvalue k /0="No" /1="Yes" /9="Missing" /8="Not recoded" > > * now for certain conditions change exposure to "no" or yes: > * I just give different examples > * first I give all the value 8 to make sure I am in control of the > recoding: > k = 8 > If ( (a= 1) and (b = 1)) then exposure= 0 > If ( (f = 1) ) then exposure= 9 > If ( (a= 1) and (b = 1) and (c = 1) and (d = 1) ) then exposure= 1 > tab k > * if any records are stille with the value 8, then you would know there > is a problem. > > 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 89, Issue 1 > ******************************************* >

1 0

EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 15 Mar '11

15 Mar '11

Hello, I am working on a project with a data entry program that exceeds 999 lines and I would like to avoid breaking the entry into sections (we would need at least 4 sections for our data entry program). Are there any tricks to work around this situation besides breaking up the program into several parts? If not, does anyone have suggestions for alternative programs to use for data entry on long surveys like this? I have heard that CSPro may work, but I have no experience with it. If you have any experience with CSPro or other data entry programs that might work, please email me directly ( Haddaway-sam(a)norc.org). Thanks, Sam Sam Haddaway | Research Analyst, International Projects NORC at the University of Chicago 4350 East-West Highway, 8th Floor, Bethesda MD 20814 haddaway-sam(a)norc.org <mailto:haddaway-sam@norc.org> | office +1 (301) 634-9423

1 1

EpiData for Mac
by epidata-list＠lists.umanitoba.ca 15 Mar '11

15 Mar '11

Dear EpiData colleagues, I have just started using Epidata and I own a mac. There seem to be no detailed help guides to help follow and use the Mac version. Is it that its still under development? Is there anyone with access to this document Kind Regards Aloysius Ssemaganda UVRI/IAVI HIV Vaccine Program Uganda Virus Research Institute P.O.Box 49 Entebbe,Uganda. Tel: +256 414 322 377/8,+256 414 321 094 Cell: +256 782 334 633 Fax: + 256 414 321 124 Email: assemaganda(a)iavi.or.ug or assemaganda(a)gmail.com

1 1

Conditional formula
by epidata-list＠lists.umanitoba.ca 12 Mar '11

12 Mar '11

Hello Epidata users, I am having problem to code conditional formula in epidata as described below, can anyone suggest how to code to the following condition, If a= 1 and b = 1 then exposure= K If a= 1 and b = 0 then exposure= K If a= 1 and b = 1 and c= 1 then exposure= K If a= 1 and b = 1 and c= 1 and d=0 then exposure= K If a= 1 and b = 1 and c= 1 and d=1 then exposure= K else exposure= K1 Thanks -- *Dr. Bijay Adhikari*, PhD, MPH, DVM* Prov. Communicable Disease Epidemiologist Population Health Branch Saskatchewan Ministry of Health Regina, SK Canada

1 1

Thankyou
by epidata-list＠lists.umanitoba.ca 25 Feb '11

25 Feb '11

Hi Everyone, I would like to thank you for all your help answering my query with Epidata. All your help is much appreciated. Kind Regards, Niamh

1 0

Query about Epidata and Exporting to SPSS
by epidata-list＠lists.umanitoba.ca 24 Feb '11

24 Feb '11

Hi all, I have a quick question. I used Epidata to put all my data from a survey I conducted. I did not export all my inputted data in SPSS but I am using SPSS for analysis. I was wondering is it possible to export all of my data in Epidata into SPSS. Or is it better to manually put it into SPSS. Also, I am new to research and statistics and was advised to use Epidata first and then analyse using SPSS. I was wondering why people use Epidata first and then export to SPSS. I mean, what are the advantages of doing this? Is it better to do this first and then export to SPSS? Any advise would be greatly appreciated, Kind Regards, Niamh

1 4

Check commands and field naming
by epidata-list＠lists.umanitoba.ca 18 Feb '11

18 Feb '11

Well done to Jens and Torsten on the progress of the manager and entry client. I have a few questions. I see that there is a confirm field check in the manager, but appears to be applied to the field in question only. So if one wishes to make every field a confirm field, then such an edit would need to be made for every field. I wondered if there were plans to enable the user to set such a thing for the whole database by having it as a global setting. Similarly for a missing value (9999 might always be a missing value code). Another question is whether there any plans to enable chk files created in EpiData Entry to be imported into the manager and/or rec files containing such checks to be brought into the manager with the checks preserved (at present they are ignored). A final question concerns the pasting of a qes file into the manager which uses EpiData Entry automatic field naming (i.e. the curly brackets to define filed names) and whether this will be supported in the manager. At present, the brackets are ignored by the program. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Updated entry client fixing a backup problem uploaded
by epidata-list＠lists.umanitoba.ca 16 Feb '11

16 Feb '11

Unfortunately the backup at closure of a project was not working in the EntryClient uploaded last friday. This has been fixed in the version which has just been uploaded. An article on data quality describing the principles we are working under is available now as a free pdf from: http://www.ingentaconnect.com/search/download?pub=infobike%3a%2f%2fiuatld%2… the reference is: Quality assurance of data: ensuring that numbers reflect operational definitions and contain real measurements Authors: Rieder, H.L.1; Lauritsen, J.M.2 Source: The International Journal of Tuberculosis and Lung Disease, Volume 15, Number 3, March 2011 , pp. 296-304(9) regards to all Jens Lauritsen EpiData Association regards to all Jens Lauritsen EpiData Association

1 0

Asymmetric limbs of Confidence Interval - clarification
by epidata-list＠lists.umanitoba.ca 16 Feb '11

16 Feb '11

Please see below the table generated in Epidata analysis and note the confidence interval in the first row HIV results Total 1539 108 7.0 (5.8-8.4) This is the proportion of HIV infected among a group of TB suspects which is 7% with 95% CI being 5.8 - 8.4. It can be deduced that the upper limb of confidence interval(which is 1.96 times Standard error) is 8.4 minus 7 = 1.4 Similarly, it can be deduced that the lower limb of confidence interval(which is 1.96 times Standard error) is 7 minus 5.8 = 1.2 *Query - why are the two limbs of the confidence interval different?* the same observation can be noted in all CIs noted above in the table. The asymmetry of limbs of CI are expected in case of non-linear measures like Odds Ratio, Relative risk, Hazard Ratio etc, but not in case of simple proportions. I am given to understand (from Dr Hans Reider, from whom I learnt Epidata) that EpiData Analysis is purported to follow the recommendations by the BMJ in the calculation of most confidence intervals and this would indeed suggest that the CI around a proportion should be symmetric on a linear scale. Would be grateful if you could clarify. Regards, Ajay -- ****************** Dr. M. V. Ajay Kumar WHO National Consultant - RNTCP Central TB Division, MOHFW 523'C' Wing, Nirman Bhavan, Maulana Azad Road, New Delhi - 110108 Mail - No. 353-C, J&K Pocket, Dilshad Garden, Delhi - 110095 Phone : +91-9311384574 Email : Kumaramv(a)rntcp.org;

1 2

Technical details of test release
by epidata-list＠lists.umanitoba.ca 15 Feb '11

15 Feb '11

Dear All Today we have released new test versions of EpiData EntryClient and EpiData Manager. This email is mainly technical and will give broad view of changes and additions to the two programs. Important aspect: flow of entry. On a normal entry of fields, the flow is defined as moving from field to field in a left-to-right, then down, manner – but at the same time following sections. Once inside a section this section will be completed before exiting. This should simulate a normal work flow working with schemes/registration forms. The flow of entry is followed if you leave the field in a "standard" way. Standard ways are: "The entire length of the field is filled" or by using one of the following keys: ”Arrow down”, ”Enter” or ”Tab”. These keys are "flow of entry keys" and should be used during data entry. To break the flow of entry (not recommended) : Either use "Arrow Up" key, the mouse or enter a legal value and then avoid saving the record. We note "not recommended" since a field could have some attributes set that defines another flow of entry, e.g. a jump. The programming is handled in three "parts": A common core, EntryClient and Manager. Any change to the Core module will affect the two other parts: *Changes for Core*: * Define jumpsfor a field. Changes the flow of entry (see above) and rules for resetting field data. (leave as is, blank, add defined missing) * Define Entry Mode for a field. The possible (mutually exclusive) attributes are: Default Entry, Must Enter or No Enter. * Define Confirm Entry. This will force a user to confirm the entry using a key (see below). * Define Show Value Label. Show category text for a given entered value next to the field (right side) (formerly known as comment legal show). * Various bug fixes, including incorrect import of dates from Stata files and definitions of "missing" status of a Value Label. Changes for both programs: * Added a check such that programs can only be started once (single instance). * The programs now check that the active project file has not been modified between saves. * Added short-cuts to the 9 most recent files: Ctrl + Shift + <number> * Shortcuts for Mac OS X have been changed to follow the native style of the OS. * Adapted setup and properties for the new options Changes for Manager: * Hides Work Process Toolbar when a project is active. * Assign jumpsto field. One or more jumps may be assigned to a field. * Added the ability to "copy & paste" field/heading/sections on the designer. - A section can be copied to the main section. - Copying a section will also copy fields/headings within that section. - Fields/Headings can be copied to/from sections (including main section). - Field attributes can be copied from one field to another of same type. * "Tab" key should now work as "change cell" key on the Value Label Editor. * Value Label Editor modified. * Flyspray bugfixes: 71, 72, 73 Changes for Entry: * AutoIncrement (Formerly IDNUM) fields can start at a defined value * User specified Colour for errors * Enhanced control of focus for active field. * Fixed several bugs - including loading of corrupt/invalid files Kind regards, Torsten Bonde Christiansen Jens Lauritsen EpiData Association.

1 1

re: Double Entry failed when AutoSearch is enabled, Does this bug fixed?
by epidata-list＠lists.umanitoba.ca 13 Feb '11

13 Feb '11

> On 2011-02-13 08:55,epidata-list at lists.umanitoba.ca <http://lists.umanitoba.ca/mailman/listinfo/epidata-list> wrote: > >/ Hi, I have struggled with a problem that: > />/ When I use the double entry real time verification, I can only do the > />/ verification on the first record, When I entering a second record, the > />/ verification is Disabled. > /Obviously this was not a pleasant experience for you. But the struggling > tells that you tried various ways - which is always a good thing. > Unfortunately there are not many things in project work and research > which works in a simple way - at least not the first time one tries. Thanks for your reply and a warn encouragement. > Only for files with a unique identifier that you YOURSELF enter during > the entry - and provided this field have the "Key unique" setup will the > verify during entry work. It is obvious that if there is no unique key - > then the software will have no way of knowing which record from the > first entry to compare with. Your logic of using "autosearch" is fine in > general, but is too complex in the double entry situation. Here are my considerations (sorry if I not fully understand your statement as my English is not quite good:-) ) Generally, there are two kind of "double check": 1, we entered two rec files separately and independently, then use the Menu->document->Validate duplicate files, this checking is "off-line mode". 2, I entered one rec file, and cread a _dbl.rec file by Menu->Tools->Prepare double entry verification. Then just opened the _dbl.rec file, and entering records, so this is "double entry verification in real time mode". So, when I want to do "double entry in real time", I must: 1, use Key unique feature on some/one field 2, do not use "autosearch" right? > As such I do not know of any bugs in relation to double entry and > verification, but some requirements/limitations (possibly not well > documented) are needed: > > A. If you use<idnum> fields in your system then: > make a copy (copy structure in tools menu) of your system and > INDEPENDENTLY enter data the second time. Following the second entry do > the validation in the documentation menu. > B. If you use a combined key for your "unique identifier": > e.g. mykey = idnum+var1+var2 > or mykey = string(idnum) + string(var1) + string(var2) > then do as in point A > C. If you are using a related file system > then do as in point A > D. based on your experience we can add : If using autosearch > then do as in point A The method A,B,C,D you give is all about the way in "off-line mode", right? I'd like to say that: I prefer "double entry in real time mode", as I think it is much convenient to do the verification while entering. Zhang Yuanhui China

1 0

Double Entry failed when AutoSearch is enabled, Does this bug fixed?
by epidata-list＠lists.umanitoba.ca 13 Feb '11

13 Feb '11

Hi, I have struggled with a problem that: When I use the double entry real time verification, I can only do the verification on the first record, When I entering a second record, the verification is Disabled. I have struggled this problems for nearly two days by trying to narrow the problem, then finally I found that if I remove the "autosearch" function on my ID field (which is the matching key on the double entry verification), then everything works fine. Finally, I search by keywords "autosearch double entry" on this maillist, and found there is an announcement by the official author in this post: (it was in year 2006) http://lists.umanitoba.ca/pipermail/epidata-list/2006q2/000430.html They said: ------------------------- Double Entry and Autosearch: Danger!....... ------------------------- Now, I'm using the latest official release version, which is v3.1 (28jan2008). I also check the mantis system, I don't find anything related to this bug. http://www.epidata.dk/php/mantis/view_all_bug_page.php So, Still, my question is: Does this bug fixed? It seems this bug still exists in the v3.1 (28jan2008). Thanks Zhang Yuanhui China

1 1

next test version ready
by epidata-list＠lists.umanitoba.ca 11 Feb '11

11 Feb '11

Dear all As announced previously a new test release will be available today. A follow-up mail on the technical issues of the new versions will come when upload of the new software has taken place. Address will as usual be http://www.epidata.dk/testing.php The main new as pects are implementation of jumps, mustenter and a revision of the interface, plus handling of a number of reported bugs and those found in our own testing. Questions in relation to this or comments can be given: a. general ones to this list b. bug reporting to flyspray or this list as usual. c. specific questions or information on further funding possibilities to info at epidata.dk. The mails will be read, but you receive an automail telling of "do not expect a response". The following week Torsten Christiansen and I will attend to an APHEO seminar in Canada. The use of the software in field settings is the prime driver for developments. Torsten Christiansen is responsible for the software architecture, design and programming in collaboration with me. Further information on the seminar, see: http://www.apheo.ca/index.php?pid=47#2011 regards Jens Lauritsen Initiator and Coordinator EpiData Assocation, Denmark

1 0

Can't enter to flyspray bug tracking
by epidata-list＠lists.umanitoba.ca 10 Feb '11

10 Feb '11

Hello: If someone can help me with this, I would appreciate it. Read below. ---------- Mensaje reenviado ---------- De: Omar Bautista González <omarbautistag(a)gmail.com> Fecha: 28 de enero de 2011 18:56 Asunto: Can't enter to flyspray bug tracking Para: info(a)epidata.dk, Manager <flyspray(a)epidata.dk> Hello: I'm testing the GNU/Linux of EpiData Manager and Entry. There are some things that I want to report and the mailing list is not the best instrument to do that. I tried to suscribe to http://www.epidata.info/flyspray/ at the 17 of january (2011). I also tried today without success. Maybe is because the project admin must approve my account. I'm not the best English speaker, but I'm learning to help and other reasons. I speak spanish. My user account is RadicalLibre. Regards, -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 2

Epidata Analysis and cluster sampling
by epidata-list＠lists.umanitoba.ca 08 Feb '11

08 Feb '11

Hello, I would like to know if there is a way to analyze our data from a vaccination coverage study, in which we used *cluster sampling*, using Epidata Analysis. As far as I know, Epidata Analysis by default gives proportions and confidence intervals assuming for simple random sampling. Thank you in advance, Dimitris Papamichail National School of Public Health, Greece -- ------------------------------------------------------------------------------ Δημήτρης Παπαμιχαήλ Dimitris Papamichail 213 2010 153 dpapamnos(a)gmail.com ------------------------------------------------------------------------------

1 1

next test version - and a question on principles of updating auto-date and auto-time fields
by epidata-list＠lists.umanitoba.ca 08 Feb '11

08 Feb '11

Dear all Developments are continuing and many new aspects will be available in the next test release of the Manager and EntryClient software, e.g.: - revised value label definitions - range - mustenter, confirm, noenter - show value labels after entry (formerly known as : type comment) - jumps which can be to: "skipnextfield", "end of section", "save record" and to a named field the fields bypassed can be reset to: "no change", "system missing", "highest defined missing value", "next to highest defined missing value". Release of the next test version is expected within a few days. More information will be shown at the time of release. With this implementation we are very close to the functionality needed by most users in terms of data-entry. On top of that functions for searching in data and documentation will come. One aspect which we would like some input on, is the following: In the current EpiData Entry for windows we have: auto-id (<idnum>) and today fields which are updated at the time of SAVING data. In the current Manager and EntryClient the Auto-data, and auto-time fields are getting a value upon creation of the record. Not at the time of saving first time or editing the record. Please indicate preference: a. We only need auto.date and auto-time fields having value at saving records b. We only need auto.date and auto-time fields having value at creation time c. It is preferable to have a combination of a and b, where the user specifies for a given field which of the two properties these fields should have. regards Jens Lauritsen EpiData Assocation

1 2

EpiData in Vietnam
by epidata-list＠lists.umanitoba.ca 26 Jan '11

26 Jan '11

I'll be running a course in Vietnam on questionnaire design and data management. As part of the course I'm thinking of adding a session on EpiData. Can anyone answer the following question: How do people in non-English speaking countries manage with EpiData? I don't mind the menus being in English because a translation of the menus into Vietnamese can be handed out to participants. What may be an issue is entering Vietnamese characters into the QES file and text fields. If Vietnamese characters are entered into the QES file, will they be displayed in the REC file? Also can field names contain Vietnamese characters or must these be English letters? Also, what is the forecast for the release of EpiData Manager and EpiData EntryClient in the completed stage, i.e. with checks and GCP in place? Regards, 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/>

1 9

Testing GNU/Linux version
by epidata-list＠lists.umanitoba.ca 17 Jan '11

17 Jan '11

Hello: I'm now testing the linux version of EpiData Manager and EpiData Entry. The following suggestions would be useful: 1) When copy/paste of a text from an UPPERCASE field to a lowercase field it would be nice to automatically convert the text case on the destination corresponding field. 2) When importing from rec files the conversion don't reflect the rec created before on the stable version of EpiData. There are some differences between the names of the fields. Only a few labels appears and the ranges of inputs doesn't appears. 3) It would be great to finish the interface of the check commands and later the RELATE function for relational databases. 4) For future translations it would be good to build an interface, as stable EpiData has. Just with a file containing the translation in cuestion would be an easy alternative. Although, when EpiData will be released under Open or Free philosophy of source code, the translations can be done directly. I can help on a Spanish version on both scenarios. 5) As someone told on other moment an interface with other statistical analysis package would be great, as the R Statistical Computing. Also the new GPX or GPZ files will need interfaces to communicate with R, with the "foreign" package under R. Great job! Att. -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 0

Multiple users entering data the same time?
by epidata-list＠lists.umanitoba.ca 17 Jan '11

17 Jan '11

Hi, Can epidata safely handle multiple users entering data into a single recfile at the same time? Thanks. David -- David Whiting, PhD | Senior Epidemiology & Public Health Specialist tel +32-2-6437945 | mob +32-496-266436 | David.Whiting(a)idf.org International Diabetes Federation 166 Chaussée de la Hulpe, B-1170 Brussels, Belgium tel +32-2-5385511 | fax +32-2-5385114 info(a)idf.org | www.idf.org | VAT BE 0433.674.528 IDF | Promoting diabetes care, prevention and a cure worldwide

1 2

EpiData manager test
by epidata-list＠lists.umanitoba.ca 14 Jan '11

14 Jan '11

Hi, I have tested EpiData manager and EpiData entry client. First : congratulations for this great job! It will be hard to forget the .qes .chk .rec system, but xml is a good choice for the future! Bug report and suggestions (I work on a PC with windows 7) : 1/ Entry client : - when entering a date without "/", the first slash is automatically inserted (like in EpiData entry), but not the second one, and a blank grey screen appears after pressing tab or enter. This screen disappears when pressing ESC -is a search function planned ? 2/ Manager - Moving fields or headings does not seem easy once they are created. Actually I can't find how to do it ! - A double click on an item should open the properties window - edition of the value labels is not intuitive. For example, it took me a long time to understand that I had to press enter to insert a new line - in value label edition : the image of the edited value label disappears when it is selected (first column on the left) - I created a new project and tried to enter new value labels : I could insert new lines but could not fill the "value" and "label" columns : they became blank after entering text and pressing enter That's all for now! Pascal THIBON, MD CHU Caen, Normandie France

1 2

new test release for EpiData Manager and Epidata EntryClient
by epidata-list＠lists.umanitoba.ca 11 Jan '11

11 Jan '11

Dear all As you all know we are approaching the change from the EpiData Entry released first time in 1999 to the updated and modernised EpiData Manager and EpiData EntryClient The main reasons for change have been published previously here on the list. Among these are needs for adaptation to modern data quality standards and in medical research projects the increasing demands for documentation in the form of so called Good Clinical Practice principles. More on this later. Today we have released major revisions the EpiData Manager and EpiData EntryClient programs. _*Major changes for both programs:*_ * Define *valuelabels* for a project. This includes definition and changes at file and field level. * Implementation of *range* for a field, which may also be combined with value labels * Users can save pdf files with instructions in a specified folder. Those present in that folder will be shown in the help menu "tutorials". This means that without programming you can create your own set of instruction materials. * Automatic timed back-up features during design and entry * Modernised design, e.g. showing recently used files. Manager: * Independent Value Label editor. * "Show Structure" form informing about contents and definitions in the project. * Statusbar more informative. dded possibility to store the positions of open forms. EntryClient: * Use "+" or F9 to show defined value labels. Based on input a guess is made within the list. * Auto ID (IDnum) fields work and can have specified initial value. * Floating fields now show full number of defined decimals. Please test the released software. With the software introduction documents are included and updated versions will be placed on the testing page of EpiData. Find all of this at: Http://www.epidata.dk/testing.php Please do report on this list of how you find the new versions. We are approaching first release and I am aware that many courses in the coming months rely on good and stable function of the new versions. All programming done by full time employed Torsten Christiansen. Possible due to donations as indicated on http://www.epidata.dk/funding.htm (donations are required for continued development) Regards Jens Lauritsen EpiData Association

1 2

RE: EpiData-list Digest, Vol 86, Issue 4
by epidata-list＠lists.umanitoba.ca 01 Jan '11

01 Jan '11

Thank you Jamie for your solution. I didn't know "iif" command in Analysis. Bernard BRANGER, Nantes, France -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list-request(a)lists.umanitoba.ca Envoyé : lundi 27 décembre 2010 19:00 À : epidata-list(a)lists.umanitoba.ca Objet : EpiData-list Digest, Vol 86, Issue 4 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. EpiData-list Digest, Vol 86, Issue 3 (epidata-list(a)lists.umanitoba.ca) 2. Re: EpiData-list Digest, Vol 86, Issue 3 (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Dec 2010 11:38:50 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData-list Digest, Vol 86, Issue 3 To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <4738E210DAFB460CBD3010042CD0F657@Ordinateurfixe> Content-Type: text/plain; charset="Windows-1252" Hello, Thank you for your reply, but I specify my problem: - Variables in the questionnaire Var1 ## Var2 ## Var3 ## Var4 ## Mean4 ##.## - In CHECK file (or ANALYSIS) mean4 mean4 = (var1+var2+var3+var4)/4 end - But sometimes, var2, for example, can fail (blank): in this case, "mean4" is the sum (Var1 to var4) divided by 3! - My question is, how to count automatically (CHECK or ANALYSIS) the number of variables (var1 to var4) not missing? Thank you for your help. B. BRANGER, Nantes, France

1 0

EpiData-list Digest, Vol 86, Issue 3
by epidata-list＠lists.umanitoba.ca 27 Dec '10

27 Dec '10

Hello, Thank you for your reply, but I specify my problem: - Variables in the questionnaire Var1 ## Var2 ## Var3 ## Var4 ## Mean4 ##.## - In CHECK file (or ANALYSIS) mean4 mean4 = (var1+var2+var3+var4)/4 end - But sometimes, var2, for example, can fail (blank): in this case, "mean4" is the sum (Var1 to var4) divided by 3! - My question is, how to count automatically (CHECK or ANALYSIS) the number of variables (var1 to var4) not missing? Thank you for your help. B. BRANGER, Nantes, France -----Message d'origine----- De : epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] De la part de epidata-list-request(a)lists.umanitoba.ca Envoyé : dimanche 19 décembre 2010 19:00 À : epidata-list(a)lists.umanitoba.ca Objet : EpiData-list Digest, Vol 86, Issue 3 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: Number of variables not missing (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sat, 18 Dec 2010 20:52:21 +0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: Number of variables not missing To: epidata-list(a)lists.umanitoba.ca Message-ID: <AANLkTimm_vdw-KBwy03VcuDX5aXgUyZAB5k=JQbdzCU=(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear Bernard, What do you think about count if [logical statement]. For example: count if km=. will return the number of km that are missing in the data set. Additionally you can list such list id if km=. Please let me know if this helps. Tieble On 18 December 2010 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. Number of variables not missing (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Dec 2010 18:02:36 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Number of variables not missing > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <6B03D7CCC9B74325BC1D373EEBCD70CF@Ordinateurfixe> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > In EPIDATA ENTRY or ANALYSIS, to calculate an mean, it is easy to calculate > a sum of several variables (the numerator)(even if some are missing), but I > don't know calculate the number of non-missing variables (the denominator) > as the command "NBVAL" in EXCEL. Thank you for helping me. > > Bernard BRANGER, Nantes, France > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 86, Issue 2 > ******************************************* > -- http://www.vet2011.org/calendrier3.php ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 86, Issue 3 *******************************************

1 1

Re: Number of variables not missing
by epidata-list＠lists.umanitoba.ca 18 Dec '10

18 Dec '10

Dear Bernard, What do you think about count if [logical statement]. For example: count if km=. will return the number of km that are missing in the data set. Additionally you can list such list id if km=. Please let me know if this helps. Tieble On 18 December 2010 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. Number of variables not missing (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Dec 2010 18:02:36 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Number of variables not missing > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <6B03D7CCC9B74325BC1D373EEBCD70CF@Ordinateurfixe> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > In EPIDATA ENTRY or ANALYSIS, to calculate an mean, it is easy to calculate > a sum of several variables (the numerator)(even if some are missing), but I > don't know calculate the number of non-missing variables (the denominator) > as the command "NBVAL" in EXCEL. Thank you for helping me. > > Bernard BRANGER, Nantes, France > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 86, Issue 2 > ******************************************* > -- http://www.vet2011.org/calendrier3.php

1 0

Number of variables not missing
by epidata-list＠lists.umanitoba.ca 18 Dec '10

18 Dec '10

Hello, In EPIDATA ENTRY or ANALYSIS, to calculate an mean, it is easy to calculate a sum of several variables (the numerator)(even if some are missing), but I don't know calculate the number of non-missing variables (the denominator) as the command "NBVAL" in EXCEL. Thank you for helping me. Bernard BRANGER, Nantes, France

1 0

bugs in stattables command?
by epidata-list＠lists.umanitoba.ca 08 Dec '10

08 Dec '10

Hello all, I am trying to adapt a program written for an earlier version of EpiData to version 2.2.1.171. The command for the old version was . stab sex /mean="age" /des="age" which printed the following columns: sex, N, Nage, MEAage, MINage, MEDage, MAXage If I understand things correctly, I should be able to get the same table using the following command in the new version: . stab age /by=sex /stat="n mean des" However, I get a "Unknown aggregate function: N" when I try to execute the above command, even though the documentation mentions the parameter: * n Number of observations Also, interestingly, if I execute . stab age /by=sex /mean I get no error but just the table Sex | N ---------- M | 490 F | 3537 Instead of the mean. Are these bugs in EpiData or do I misunderstand the documentation? Kind regards, Simon

1 2

Re: Putting the content from several entry fields
by epidata-list＠lists.umanitoba.ca 26 Nov '10

26 Nov '10

Perhaps, you may want to create a field doctor_id (provided you have only few or up to 10). Then add label: 1 "Dr TH" 2 "Dr VM" 3 "DR HT" so on Then edit type comment Now you should be able to choose from the doctor_id, but you need to have doctor_id on each rec field. I would suggest that you try to do this in a simple way as two or more patients can be seen by the same and/ or different doctors. I don't know your research question but I have seen a case where patient A has been seen by Dr Smith then by Dr Brown too? Best wishes Tieble On 25 November 2010 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. Putting the content from several entry fileds into a value > label. (epidata-list(a)lists.umanitoba.ca) > 2. Re: Putting the content from several entry fileds into a > value label. (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 24 Nov 2010 23:54:40 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Putting the content from several entry fileds > into a value label. > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <FF3F33C7E13129439AFE23E87BD331F7C5B703BAD8(a)HORMXB102VM1.onerm.dk> > Content-Type: text/plain; charset="iso-8859-1" > > Hey > > I need help to find out if it is possible to have the content of several > data entry fields listed in a value label. > > I am doing a registration of data from patients files and need for > statistical purposes (cluster effect) to register the specific doctor that > has observed a given event, x-ray, bloodsample etc. > > I therefore thought of a way where you have one data entry field for each > doctor involved with patient and then everytime you need to assign a doctor > to a specific information a complete list (value label) defined by the > doctors you previously typed will show and you can then those instead of > typing it every time. > > How do I do that? Is there some way to write within the value label file > that allows a variable value to show? > > Thomas > > > ------------------------------ > > Message: 2 > Date: Wed, 24 Nov 2010 22:29:35 -0500 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Putting the content from several entry > fileds into a value label. > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP51B6C094BB2891B9A04854FD200(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > There is probably a way to do this, using EPIC via the EXEC command to > create a small .rec on the fly that can be used as input to a conditional > COMMENT LEGAL. Analysis could also create the required .rec of legal values > for a patient, but I've never tried to use the EXEC command in a .chk file > to run Analysis. The kind of solution MIGHT work - I haven't tried it. > However, if none of the first sentence makes sense to you, it is probably > not worth trying it out. > > Why not just have a list of all of the doctors and pick from that list > every time a record is created. This ensures accurate entry of doctors, if > you know them all to begin with. Even if you have a few hundred doctors, an > alphabetic list is easy to present to the user via COMMENT LEGAL. > > EpiData does not have lookup feature that will let you type part of the > doctor's name and then see a partial list (except via conditional comment > legal). > The problem you state is handled "easily" (for an experienced user) by > relational databases that can create queries on the fly (ACCESS, etc). > > EpiData Entry does have a provision for running small programs to do this > sort of thing, but creating those small programs is a task for an > experienced programmer. If you have a mission critical requirement and this > function will be used every day by many people, it would be worth > programming it. > > In the long term, this could be an interesting feature to request to have > in the Entry Client - essentially the ability to recall from all existing > records, the unique values of one field, based on a filter - to be used as a > lookup table; plus the ability to add new values. This could be used very > frequently in many data entry applications. > > Jamie > > On 2010-11-24, Thomas wrote: > > > I need help to find out if it is possible to have the content of several > data entry fields listed in a value label. > > > > I am doing a registration of data from patients files and need for > statistical purposes (cluster effect) to register the specific doctor that > has observed a given event, x-ray, bloodsample etc. > > > > I therefore thought of a way where you have one data entry field for each > doctor involved with patient and then everytime you need to assign a doctor > to a specific information a complete list (value label) defined by the > doctors you previously typed will show and you can then those instead of > typing it every time. > > > > How do I do that? Is there some way to write within the value label file > that allows a variable value to show? > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 85, Issue 12 > ******************************************** > -- http://www.vet2011.org/calendrier3.php

1 0

Putting the content from several entry fileds into a value label.
by epidata-list＠lists.umanitoba.ca 24 Nov '10

24 Nov '10

Hey I need help to find out if it is possible to have the content of several data entry fields listed in a value label. I am doing a registration of data from patients files and need for statistical purposes (cluster effect) to register the specific doctor that has observed a given event, x-ray, bloodsample etc. I therefore thought of a way where you have one data entry field for each doctor involved with patient and then everytime you need to assign a doctor to a specific information a complete list (value label) defined by the doctors you previously typed will show and you can then those instead of typing it every time. How do I do that? Is there some way to write within the value label file that allows a variable value to show? Thomas

1 1

substring in data entry check file
by epidata-list＠lists.umanitoba.ca 22 Nov '10

22 Nov '10

Hi, In epi info 6.04d for DOS it is possible to take a substring using square brackets to index the characters wanted, e.g. firstname[1,1] gives the first letter of the firstname field. Is there anyway to do this in epidata? Using [1,1] like this does not seem to work. It does not throw an error, it just does not do what I want it to do (fill in another field). Thanks. David -- David Whiting, PhD | Senior Epidemiology & Public Health Specialist tel +32-2-6437945 | mob +32-496-266436 | David.Whiting(a)idf.org International Diabetes Federation 166 Chaussée de la Hulpe, B-1170 Brussels, Belgium tel +32-2-5385511 | fax +32-2-5385114 info(a)idf.org | www.idf.org | VAT BE 0433.674.528 IDF | Promoting diabetes care, prevention and a cure worldwide

1 4

Re: [EpiData-list] Roster for household questionnaire
by epidata-list＠lists.umanitoba.ca 13 Nov '10

13 Nov '10

I agree that related files would work better in this case. In the current public release, however, related files are not fully integrated. For example, it is (as far as I can tell) impossible to do double entry on a record that has related files. I think the best solution would be to work on fully integrating related files into the program. If this is not possible, then the function for roster variables described by Mensah would be second best. -Sam -----Original Message----- Date: Thu, 11 Nov 2010 23:05:26 -0500 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Roster for household questionnaire To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP51E700F7DE8AA4536619A2FD330(a)phx.gbl> Content-Type: text/plain; charset="us-ascii" This is something I would use related files for, especially when you don't know how many household members there will be. We'll have to wait to see how they work in Manager/Entry. If you have parts of questionnaires you will use often, including more than once in the same project (questionnaire), simply create a short .qes for them and import that .qes structure multiple times into Manager. This works very well. You can then alter the Vnn field names yourself. Jamie On 2010-11-11, Mensah wrote: > Is it possible to have the function for a roster variables instead of > doing it manual. > for instance in CSpro, there is a roster function of designing a household > data that repeat several * *times, but in epidata you have to do it manual.

1 1

RE: EpiData-list Digest, Vol 85, Issue 6
by epidata-list＠lists.umanitoba.ca 12 Nov '10

12 Nov '10

I am using EpiData Verion 3.1. I did send a screenshot, but apparently only text is allowed by the list. Many thanks, Shakeel -----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: 11 November 2010 18:01 To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 85, 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. Overlapping text/ answer box (epidata-list(a)lists.umanitoba.ca) 2. Re: Overlapping text/ answer box (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Nov 2010 08:52:33 -0000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Overlapping text/ answer box To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <6FB4A65524882E48B6BEA9636B2628323693D3(a)colhpaexc015.HPA.org.uk> Content-Type: text/plain; charset="us-ascii" I don't use epidata very often, so this is probably a very basic question. I have created a form, but when I preview it, there are a few questions where the questions and answer boxes overlap (as shown in the attached). There is no overlap in design view and I am struggling to work out why this is happening. Any suggestions would be most welcome. Thanks, Shakeel Suleman ----------------------------------------- ************************************************************************ ** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk ************************************************************************ ** ------------------------------ Message: 2 Date: Thu, 11 Nov 2010 10:07:22 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Overlapping text/ answer box To: epidata-list(a)lists.umanitoba.ca Message-ID: <4CDBB24A.2090105(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 2010-11-11 09:52, epidata-list(a)lists.umanitoba.ca wrote: > I don't use epidata very often, so this is probably a very basic > question. I have created a form, but when I preview it, there are a few > questions where the questions and answer boxes overlap (as shown in the > attached). There is no overlap in design view and I am struggling to > work out why this is happening. Any suggestions would be most welcome. > > > > Thanks, > > > > Shakeel Suleman Dear Shakeel I think you forgot to attach the screenshot you mention. Also please tell which program that you refer to, the "old" Entry program or the test version the "new" EpiData EntryClient program. Kind regards, Torsten Bonde Christiansen. EpiData Association. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 85, Issue 6 ******************************************* ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 4

Roster for household questionnaire
by epidata-list＠lists.umanitoba.ca 11 Nov '10

11 Nov '10

Hello Jen and Team, Nice work on the new epidata software manager and client, which is under test. Is it possible to have the function for a roster variables instead of doing it manual. for instance in CSpro, there is a roster function of designing a household data that repeat several * *times, but in epidata you have to do it manual. illustration: Household Member 1 Age Sex Gender 2 3 4 -- ............ MENSAH KOJO SEDZRO P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-3033-300789 MOBILE : +233-244-458788 -------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 1

Overlapping text/ answer box
by epidata-list＠lists.umanitoba.ca 11 Nov '10

11 Nov '10

I don't use epidata very often, so this is probably a very basic question. I have created a form, but when I preview it, there are a few questions where the questions and answer boxes overlap (as shown in the attached). There is no overlap in design view and I am struggling to work out why this is happening. Any suggestions would be most welcome. Thanks, Shakeel Suleman ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

test version of analysis ready (read epx file - new Odds Ratio calculation)
by epidata-list＠lists.umanitoba.ca 07 Nov '10

07 Nov '10

A new test release of EpiData Analysis has been placed for download on the testing page. http://epidata.dk/testing.php The zip file contains a complete working copy, including updated help file. When you unzip please maintain folder structure. An EPX formatted version of bromar data is included in the zip file. Changes from previous releases are: A. Ability to read xml formatted files created by EpiData Manager (EPX) files (NOT EPZ zipped files) B. The default principle of Odds Ratio calculation has been changed from: MLE based to: Standard simple with Robins, Greenland, Breslow 95% CI to get the new default Odds Ratios use: /o , to use the same as previously: /oex Output is slightly changed, example: . tab runok sex /o /oex Outcome:Marathon race completed ? Sex of runner 1 0 Total 2 3119 418 3537 1 437 53 490 Total 3556 471 4027 Exposure: Sex of runner = 2Outcome: Marathon race completed ? = 1 Odds Ratio = 0.90 (95% CI: 0.67-1.23) (Robins,Greenland,Breslow CI) Exact (MLE) Odds Ratio = 0.90 (95% CI: 0.66-1.23) pORex<=1.0 = 0.2872 With this test release users are more than welcome to challenge the whole cycle of creating files in Manager (including import fra Stata, Rec, QES files, pasting via clipboard or editor etc), entering data with the EntryClient and analysing the data in Analysis. You may use the Manager to export data to Stata for comparisons of results. Anything not working - or comments to the way we have implemented aspects - please report to this list or if you find reproducible errors it is easier for us, if you can report to the flyspray system - see link on the testing page. regards Jens Lauritsen

1 2

EpiData-list Digest
by epidata-list＠lists.umanitoba.ca 06 Nov '10

06 Nov '10

Hello, Thank you for your response about police and presentation in future Epidata Manager, I understand the problem. But is it possible only for the size of the police for the titles for example..... ??? Also, in Epidata Analysis, there are two things that cause problems for teachers and users: - Following the command "freq", numbers order is not exactly descending in case of negative numbers. - Following the command "lifetable", P50 is sometimes wrong (if small population). .... and another thing that would make life easier: - Following the command "scatter", a regression line, like in EPI-INFO DOS with "/r", would be interesting . I have a method but is longer (with creation of new variable with equation of the line through "var result", and scatter with three variables). Thanks for EPIDATA. Bernard Branger, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 2261 courriels spam. Nous avons en ce moment 7 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

font selection and text appearence in data forms
by epidata-list＠lists.umanitoba.ca 04 Nov '10

04 Nov '10

Dear all A question was raised regarding specification of underline, bold etc and specification of fonts in data forms created by the Manager and used for entry with the EntryClient. I think what could be realistic to aim for is something like: at section level: choose background colours for data fields: show field border (implemented) choose font, size and colour for all fields (question text) for heading "lines" choose font, size and text colour for all heading lines However I doubt if we will get to the point of applying underline, bold or italics for single words . The amount of work is still immense for all the data management, documentation, rewriting analysis etc. So do not expect any developments in this text fomatting area before all the core functionality has been attained. regards Jens Lauritsen EpiData Association

1 2

EpiData course material
by epidata-list＠lists.umanitoba.ca 04 Nov '10

04 Nov '10

A friend suggested that I may post this information: The 27th course of the International Union Against Tuberculosis and Lung Disease (The Union) in collaboration with the EpiData Association and a group called "EpiData Promoters" was given in Paris in the last week of October to 12 operations research fellows of a training program of The Union from 10 countries. The updated course material is available at www.tbrieder.org (click "EpiData course" in the navigation panel). The entire course exists of four parts. In Part A, the use of EpiData Entry is taught, in Part B, EpiData Analysis is introduced, in Part C, EpiData software is applied to operations research, and in Part D more sophistication in the use of EpiData software is taught. In the one-week course, only Parts A and B were taught. Parts C and D will be given to three exceptional performers in a supplementary course. The course is taught sequentially as one exercise builds on the previous one. For those interesting in only perusing quickly, you might look at the end of each Part for the solution PDF, or at the very bottom for the PDF file of the entire course (220 pages). The zip files in the solutions contain the EpiData files that are produced in each exercises. Regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

RE: EpiData-list Digest, Vol 84, Issue 17
by epidata-list＠lists.umanitoba.ca 01 Nov '10

01 Nov '10

Hello, Are there plans in future EPIDATA MANAGER : - To change the font for a word or phrase without changing police from the another parts of a questionary? - To open multiple pages in a questionary? Thank you Bernard Branger, Nantes, France PS The link to "Course materials in French" in EPIDATA ENTRY / FRENCH is : http://www.reseau-naissance.com/joomla/index.php?option=com_content&task=vi… -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 2235 courriels spam. Nous avons en ce moment 7 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

An error message while executing the command in Epidata analysis
by epidata-list＠lists.umanitoba.ca 29 Oct '10

29 Oct '10

Dear all, I got an error message while executing commands of Epidata analysis on a new machine with Windows 7. Please see the message within the quotation marks. " Cannot open file "C:\Users\Gateway\AppData\Local\Temp\TMPCC04.Tmp". The process cannot access the file because it is being used by another process " This happened when I hit F8 or F9 and the command was not executed. But it did work when I hit F8 for several times. Could anybody tell me why it happened and how to solve this problem? Thank you for your support. Zaw Myanmar

1 1

Datetime conversion resource
by epidata-list＠lists.umanitoba.ca 27 Oct '10

27 Oct '10

Hi list members From time to time on the list we have discussed the value of having a datetime variable in Epidata. This is something I would find like, as the 'epidemic curve' is something that is an important part of any outbreak investigation. For short outbreaks that carry on over more than one day both the time and date are useful so youcan show numbers becoming ill every 6 hours for example over two or three days. The ability to map by datetime is one reason I often use EpiInfo for outbreak analysis, although I enter data in Epidata. I wanted to let any interested members know that a colleague has developed a simple text file that can be run as a programme in EpiINfo that coverts data entered in EPidata to a single datetime for use in EPiInfo. If you have entered an onset date as a date and onset time as a number with a decimal (e.g. 15.30) the programme converts the information into a single datetime variable - it can then be mapped using the EpiInfo histogram graph. Jens if you think this is useful at all would you like me to post this somewhere? Also is there any thought of creating a time field in Epidata? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Input for decision of sequence in development of new functionality, please comment
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Priority of developments The current sequence of developments until the first production release contains these elements. 1. Release of test version of EpiData Analysis, which can read EXP files (possibly EXZ) - expected this week. 2. "show structure" form to Manager 3. Control structures level 1 (value labels, range) --- test release 4. Multi language in forms and labels 5. Control structures level 2 (mustenter, jumps, "type comment") 6. Control structures level 3 (define unique key and search in data) --- test release 7. Solve known deficiences (from Flyspray and list) - e.g. idnum fields 8. Printing of dataforms in EntryClient --- test release 9. Enhancements for production of fast datasets, e.g. copy from question banks 10. Further developments, e.g. GCP (Good Clinical Practice Principles). Please discuss on this list at what level of function You find first release should be made - provided obviously at that level the function as such is stable. My current decision is after point 8. It would also be good to get statements during the coming months of which decisions you make locally on the conversion to the new principles - e.g. you are ready to use it at that moment, or you find the current EpiData Entry better for your purpose, or you decided to start using other software and the reasons for that. Regards Jens Lauritsen EpiData Association Denmark

1 1

Re: [EpiData-list] New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Hi Jens and the Epidata team thank you for all the work you are doing on the new development. In terms of the timeline I am wondering about when the new build might be stable enough to be used for training courses? At the moment I teach one or two courses a year to public health staff on using Epidata and EpiInfo to investigate disease outbreaks. They use the current version of Epidata and I am wondering about when I should try and change to the new version. thank you Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Re: [EpiData-list] New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 22 Oct '10

22 Oct '10

For all users. A critical bug had sneaked into the builds of Mac versions of EpiData EntryClient (thanks to Jamie Hockin for fast feedback). The Intel and PowerPC version have both been fixed and new versions (though with the same version no.) have been placed on the testing website. Regards, Torsten Bonde Christiansen. EpiData Association. On 2010-10-22 14:35, Jamie Hockin wrote: > Hi Torsten, > > The Mac (Intel) version of the Client is corrupted - the .app is not > executable (error that the .app file is damaged or incomplete). It is > the same size/date as the previous version. File date is Friday, > September 10, 2010 8:31 AM > > Jamie >

1 0

New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 22 Oct '10

22 Oct '10

For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association

1 0

NIH requirements for Data management
by epidata-list＠lists.umanitoba.ca 20 Oct '10

20 Oct '10

Dear EpiData friends, Recently I was talking to a friend about the professionalism of research x professor-student structure in research and then he showed me a past call of NIH grant wich in part I pasted here. I was somehow surprised, because I didnt know that all these should be in a project. Data and Biostatistics Core: Required. Each application must include a The Data and Biostatistics Core is a resource to the multi-project application, providing for the data management and statistical support of the overall Center and individual research projects. The Data and Biostatistics Core has several components: an electronic data management system, a data management implementation plan, and biostatistics support. A full-time Data Manager must be present onsite at the Center or at the place where the electronic data management system is hosted and statistical expert(s) should be available as needed. Applications must provide a detailed description of the existing or planned data management system. The data management system must be capable of collecting and managing data from the participating study sites in order to ensure uniformity of procedures and high quality data. The data management system should reside at the endemic area site(s) and data management staff will be responsible for the design, development and testing of databases and data management software, validation of the data system, training of data management and field personnel on data collection procedures and activities, maintenance of the database and software systems, documentation of changes, and preparation of data dictionaries and standard operating procedures for all aspects of data management. Each TMRC and related field sites should have computers, connectivity to the internet and communications capabilities. For sites without such capabilities, funding for such infrastructure should be budgeted in this core and the infrastructure should be in place before the end of the first year of the grant. The data management system should include, but is not limited to: • security features for controlled access to all project data; • a tracking system for data forms, activities, and study samples; • date and time stamping of all data records; • audit trails to track all changes made to data records; and • a reporting system that generates error reports and summary information reports. If applicants do not have the capability for the data management system at the time of application submission, the applicant should describe a plan for designing and implementing a fully operational data management system based on the system requirements, including provisions for the time frame for design, development, testing, validation, and training activities. Plans and procedures must be in place to provide security against anticipated risks, including loss of confidentiality of subject electronic records and data summaries. Each TMRC should have staff with data management (Data Manager) expertise at each site. The Center should have access to dedicated statistical expertise that informs the research study design and provides the ability to conduct statistical data analysis. They should provide for activities such as study design and protocol development and where appropriate, generating interim tables, preliminary statistical analyses for progress reports, and assisting with statistical issues related to laboratory testing and results. Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 1

Exporting problems
by epidata-list＠lists.umanitoba.ca 20 Oct '10

20 Oct '10

Dear all, When I try to export my data into SAS, all my variables appear into a single column (in SAS). What could be happening? When I export the data into Excel and then to SAS it does work perfect. Is there any difference from exporting a data file directly from EpiData into SAS other than EpiData into Excel and then SAS? Thanks in advance for your help. Rafael

1 11

BMI Calculation
by epidata-list＠lists.umanitoba.ca 14 Oct '10

14 Oct '10

I am having trouble calculating BMI in Epidata. Height is measured in feet (separate) and inches (separate). I tried to create a new variable (BMI), which it did, but it is labelled as "Float," and unusable. Please help! Ali Ali B. Mansaray, MPH, PhD.c OMH, SCDHEC (803) 898-0263 (Days) *MANSA CS* [(803) 446-6958 (On Call) *"To be or not to be: that is the question...?" (Shakespeare),* especially in public health, minority health and health disparities in these United States.

1 0

Re: EpiData-list Digest, Vol 84, Issue 7
by epidata-list＠lists.umanitoba.ca 13 Oct '10

13 Oct '10

I am having trouble calculating BMI in Epidata. Height is measured in feet (separate) and inches (separate). I tried to create a new variable (BMI), which it did, but it is labelled as "Float," and unusable. Please help! Ali Ali B. Mansaray, MPH, PhD.c OMH, SCDHEC (803) 898-0263 (Days) *MANSA CS* [(803) 446-6958 (On Call) *"To be or not to be: that is the question...?" (Shakespeare),* especially in public health, minority health and health disparities in these United States. On Sun, Oct 10, 2010 at 1:00 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. EpiData Manager integer vs float (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 09 Oct 2010 20:37:30 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] EpiData Manager integer vs float > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4CB0B66A.7000901(a)tbrieder.org> > Content-Type: text/plain; charset="ISO-8859-1" > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 84, Issue 7 > ******************************************* >

1 2

Order of how yes no settings appear in tables
by epidata-list＠lists.umanitoba.ca 13 Oct '10

13 Oct '10

Hi Jamie A little while ago when you answered my question about changing the Boolean fields to 0-1, you mentioned there was a way in both EpiData Analysis and EpiInfo to reverse the order that two by two tables were shown, that would help in a situation where 0 was no and yes was 1 (so the 1 or yes answers appeared first in the table). I have looked around Epi Info but couldn't find a setting like this. Could you let me know how to do it? And also how to do it in Epidata analysis? I Many thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> Christine Roseveare 20/09/2010 5:21 p.m. >>> Hi Jamie Could you please explain why you changed the booleans to 0-1 before loading it into manager? Sorry if this is a silly question. I am asking because someone recently gave me an outbreak file where they had used 0 and 1 (created in Excel 0 = no and 1 = yes). The problem was that when I came to analyse it (in this case using Epi Info) it meant that the two by two tables were in the wrong order. Because no was 0 it came out first in the table. I have always used the boolean field in epidata for our outbreak questionnaires and it has worked very well. They come out in the right order in both Epidata Analysis and Epin Info, and also make intuitive sense to the data entry person. thank you Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 13/09/2010 2:34 p.m. >>> I successfully loaded a moderately-sized .rec file (changing all booleans to 0-1 before loading into Manager--it should prompt to do that for us). Entry handled the existing and new data as expected. I would like to have the autojump to next field when all digits are filled. I assume that this is coming. I successfully loaded a fictitious file with just under 500,000 records and 12 fields (41.8 MB .epx from an 8 MB .rec). Given the capacity of removable memory today, size really isn't a problem. I cannot imagine ever having a real file that large. On my old Windows laptop, this file loaded/saved in 20-30 seconds, but GO TO any record in the file was instantaneous. Jamie -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

adding variables to existing rec
by epidata-list＠lists.umanitoba.ca 12 Oct '10

12 Oct '10

To add a variable to an existing REC file, I tried what was discussed on: http://lists.umanitoba.ca/mailman/htdig/epidata-list/2010q2/001427.html But I didn't have it very clear. I finally made it doing the following steps (using EpiData 3.1, under Microsoft Windows): 1) Editing the QES adding a variable with a temporally name as "new". 2) Then, Tools -> Revise Data File 3) Tools -> Rename Fields 4) I go to the new variable and then edited the subsecuent variables with a temporally name also. The added variable should finally have the name 'P1103e' and the subsecuent variables must be "moved". In that sense the new variable would be called 'newe' and the subsecuents of the same block of questions can be called 'newf', 'newg', 'newh', 'newi', 'newj', and so on. 5) Then, I just go again to Tools -> Rename Fields 6) I then rename the variables with the appropiate names as: 'P1103e', 'P1103f', 'P1103g', 'P1103h', 'P1103i', 'P1103j'. 7) Finally, I changed the QES file with the appropiate names and then Tools -> Revise Data File. This steps worked fine for me. Regards, -- Omar Bautista González - Coordinador de Investigación para el Desarrollo, Diseño, Monitoreo y Evaluación Visión Mundial República Dominicana - Colaborador en investigación social del movimiento del software libre en República Dominicana

1 0

EpiData Manager integer vs float
by epidata-list＠lists.umanitoba.ca 09 Oct '10

09 Oct '10

1 0

Re: EpiData-list Digest, Vol 84, Issue 5
by epidata-list＠lists.umanitoba.ca 09 Oct '10

09 Oct '10

Alternatively you can ask each site to create an updated folder containing the updated rec.file then zip the folder before emailing it. Hope this will help too. Tieble On 8 October 2010 18:01, <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. how to share epidata files? (epidata-list(a)lists.umanitoba.ca) > 2. Re: how to share epidata files? (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 08 Oct 2010 10:29:56 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] how to share epidata files? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4CAED684.8050907(a)burlo.trieste.it> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Dear epidata-list members, > > I'm a new member and I'm quite new also in the use of Epidata. I need > some support. > > My team is coordinating a multicentre study. At the beginning of the > study we prepared a database (files .qes, .chk and .rec) and sent it to > all centres; during the study they send back to us regularly the > updated .rec files with the records. We have problems in receiving via > e-mail, as attached documents, epidata files (especially files .rec with > records, but also without records). We sometimes are not able to open > the files, or sometimes we manage to open the files but the records are > not there. We realised it depends also on the e-mail server used by > every centre, and on other variables too. > > I wonder which would be the best way to share epidata databases. > > Many thanks > > Alessandro > > > > ------------------------------ > > Message: 2 > Date: Fri, 08 Oct 2010 11:38:03 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] how to share epidata files? > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4CAEE67B.4090505(a)fifas.de> > Content-Type: text/plain; charset="iso-8859-15" > > Am 08.10.2010 10:29, schrieb epidata-list(a)lists.umanitoba.ca: > > Dear epidata-list members, > > > > I'm a new member and I'm quite new also in the use of Epidata. I need > > some support. > > > > My team is coordinating a multicentre study. At the beginning of the > > study we prepared a database (files .qes, .chk and .rec) and sent it to > > all centres; during the study they send back to us regularly the updated > > .rec files with the records. We have problems in receiving via e-mail, > > as attached documents, epidata files (especially files .rec with > > records, but also without records). We sometimes are not able to open > > the files, or sometimes we manage to open the files but the records are > > not there. We realised it depends also on the e-mail server used by > > every centre, and on other variables too. > > > > I wonder which would be the best way to share epidata databases. > > > > Many thanks > > > > Alessandro > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > You can solve the problem when you zip the rec-files before you send > them as a email-attachment. > > Juergen > > -- > *********************************************************** > Freiburger Institut fuer angewandte Sozialwissenschaft e.V. > FIFAS > Erasmusstr. 16, D-79098 Freiburg > > Telefon: 0049 (0)761 28 83 64 > Fax: 0049 (0)761 29 27 493 > Web: http://www.fifas.de > E-Mail: info(a)fifas.de >

1 0

how to share epidata files?
by epidata-list＠lists.umanitoba.ca 08 Oct '10

08 Oct '10

Dear epidata-list members, I'm a new member and I'm quite new also in the use of Epidata. I need some support. My team is coordinating a multicentre study. At the beginning of the study we prepared a database (files .qes, .chk and .rec) and sent it to all centres; during the study they send back to us regularly the updated .rec files with the records. We have problems in receiving via e-mail, as attached documents, epidata files (especially files .rec with records, but also without records). We sometimes are not able to open the files, or sometimes we manage to open the files but the records are not there. We realised it depends also on the e-mail server used by every centre, and on other variables too. I wonder which would be the best way to share epidata databases. Many thanks Alessandro

1 2

New Sample file available
by epidata-list＠lists.umanitoba.ca 07 Oct '10

07 Oct '10

Dear EpiData list. With the latest release of the EpiData Manager and EntryClient some changes were made to the format of datafile. Therefore the test files from today contains an updated sample file. Please delete older versions. During the development phase of Manager and EntryClient changes to the XML structure should be expected, e.g. the latest extension specifying timed recovery backup. As soon as the first public release is available for routine usage we will make sure that coming versions can read all older files. But during the developments this will not be the case. In the meantime we will provide a working sample file for each new test version such that it is possible to see the capabilities of the program. The exe files uploaded today are the same as yesterday, except that the sample file is contained. Kind regards, Torsten Bonde Christiansen.

1 0

New Manager and EntryClient test version released.
by epidata-list＠lists.umanitoba.ca 06 Oct '10

06 Oct '10

Dear EpiData list. As of this morning (danish time) new test versions of both EpiData Manager and EpiData EntryClient have been released on our testing website: http://epidata.dk/testing.php Please be aware that the back-end code for the testing website have been changed, so if you experience any problems with downloading the files please report directly to me on: tc "at" epidata.dk The major changes for these version are: * A "timed recovery backup" system has been implemented in the EntryClient. At a given interval (this is set in EpiData Manager within "Project->Settings->General") a recovery backup is save to disk with the same filename as the project file but with an additional extension ".bak". On a clean close of the program this file is deleted, hence a regular user should not notice the existence of this file, but if the program crashes unexpectedly the file will remain an upon trying to load the original file, the user is informed that a recovery file exist and advised to load the recovery file. * In addition to the "timed recovery backup" system, it is no also possible to specify that a complete backup of the project file is taken on close/shutdown (again, this is specified in EpiData Manager). The backup is NOT used as part of the timed recovery system, hence the used is not noted of the existence upon loading the original file. This is merely meant as a "daily backup" feature, that gives the user the possibility of storing backups of the daily work. In the future this option is probably going to be a lot more configurable by the manager, but for now the original file is "just" stored with the same filename, but containing the date of saving. * Both Manager and EntryClient now has a feature that allow for checking on-line if a new version of the program exists. This naturally requires an active Internet connection, but if no such exists a non-fatal warning is given. * In addition to the above a small number of bug-fixes and speed improvements have also been implemented. Kind regards, Torsten Bonde Christiansen. EpiData Association.

1 3

Re: R, EpiInfo and opensource software
by epidata-list＠lists.umanitoba.ca 30 Sep '10

30 Sep '10

Jens, Im not exactly sure what you meant by "principles of calling batch procedures from other software into R" !?! Would you like to know how R import data from ohter software formats? How other sotwares export into R format? Access these codes? Is that it? R has a lot of different functions to import data from different formats, including, Stata, SAS, SPSS, SQL, MySQL, xls, xlsx, ols (this last a think is available only for UNIX), csv, dbf, revman, and others! I never heard that other software could export to R workspace! However, I have a Stat/Transfer (2007) that has an option to export to R workspace format! Im not sure it work properly though! Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional 2010/9/30 <epidata-list-request(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. Help - Auto Member Id & Checks (epidata-list(a)lists.umanitoba.ca) > 2. Re: Help - Auto Member Id & Checks > (epidata-list(a)lists.umanitoba.ca) > 3. Re: R, EpiInfo and opensource software > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 29 Sep 2010 19:06:18 +0000 (GMT) > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Help - Auto Member Id & Checks > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <996295.1834.qm(a)web29709.mail.ird.yahoo.com> > Content-Type: text/plain; charset=iso-8859-1 > > Hi All, > > I am setting up a parent-child project. At the child level, I need to > capture sets of data for every member of household. I have a variable at the > beginning which captures Number of people in the household. The problem is I > want the Household Member Id to be automated, secondly I want to ensure all > members data are captured and equals the total number in the household > initially specified. > > Kindly help with statements to use to achieve these two things. > > Thank you. > > Bola Adedoyin > DCConsult, Lagos, Nigeria > > > > > > > > > ------------------------------ > > Message: 2 > Date: Wed, 29 Sep 2010 16:08:15 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Help - Auto Member Id & Checks > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP6343273FFEFF345AE345B0FD670(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > Do you want to check that the number of family members captured equals the > number of people recorded on the household at the time of data entry? This > is harder than doing it in Analysis. There should be an example of > numbering household members automatically in the listserve archive. > > Jamie > > On 2010-09-29, Bola wrote: > > > am setting up a parent-child project. At the child level, I need to > capture sets of data for every member of household. I have a variable at the > beginning which captures Number of people in the household. The problem is I > want the Household Member Id to be automated, secondly I want to ensure all > members data are captured and equals the total number in the household > initially specified. > > > > Kindly help with statements to use to achieve these two things. > > > > ------------------------------ > > Message: 3 > Date: Wed, 29 Sep 2010 22:19:55 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] R, EpiInfo and opensource software > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4CA39F6B.50104(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Dear colleagues > > In response to the mails of last week regarding R and combination to > EpiData software I would like to state the following: > > The way I see EpiData software playing a role in the coming 10 years is > like this: > > a. Ensure full compliance with proper data documentation procedures and > compliance with GCP guide lines (Good Clinical Practice) for medical > studies, where certain requirements are imposed on the data management. > These are explained in the paper: GCP-compliant data management in > multinational clinical trials. ECRIN-2, Deliverable D10, Version 1, 15 > September 2008.Ohmann C (chair) and the Transnational Working Group on > Data Management. I participated in the workgroup. The paper can be > downloaded from: http://www.ecrin.org/index.php?id=274 > > b. Fulfill data entry needs at the basic level in local levels giving > full control over the process by the persons running projects or routine > systems at that level > > c. Perform analysis of quantitative data at the basic and extended > levels within principles of univariate, bivariate levels and further > levels in respect to stratified epidemiological analysis (M-H > techniques), controlled analysis in survival (log rank and k-m plots) etc. > > d. Bridge to other software for extending this analysis to current > expected levels of regression or survival analysis, e.g. repeated > measures models or logistic regression. > > e. The software should be easy to use for all users. Beginners as well > as support the needs for advanced usage based on more complex principles. > > For point d I think an optimal strategy would be to bridge into R as the > tool. (and to export documented data into commercial software such as > user community supportive products such as Stata). Such that the steep > learning curve for R is bypassed for standard analysis. This also allows > for simplification of the programming for EpiData. > > In other words - I see definetely - a path as suggested of a combination > of R and EpiData. If someone have or could prepare a document of > principles of calling batch procedures from other software into R please > let us know on this list. We will need this sometime in spring next > year, when other aspects of this are in place. > > 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 83, Issue 5 > ******************************************* >

1 0

R, EpiInfo and opensource software
by epidata-list＠lists.umanitoba.ca 29 Sep '10

29 Sep '10

Hello EpiData Friends, Im just writing a few lines to you at the end of my working day to share some toughts that I have recently. In the last four years I invested a lot of effort and time tring to learn R due to my PhD object. Right now I feel confrtable with R, but in the biginning I felt like banging my head in many places to make stuff work. For the same reason I signed some R mail lists around to trade some doubts and solutions. About three weeks ago, a EpiInfo developer posted a message in epidemiologic issues for R users and it seems that he wanted to go for a EPiInfo - R interface. I was curious and found out that the latest version of EpiInfo available at CDC is 2 years old. My guess is that it is too old for a software. Clearly it was not a oficial CDC contact. Wondering why and how this could be done I realize that most likely R cand do every analysis EpiInfo can and much more. The disadvantageous are: R is is not friedly for the uninitiated, and has no default and complete GUI, although there are several GUIs available. A EPI extesion could be developed in R, while there is already four of them, that I know of. But there some sntroger point to consider in developing stuff in R: (1) opensource software is growing (2) R is opensource (3) R is multi OS (4) R language is reasonbly stable; thus something developed today may last for many many years indently of OS updates or Software updates (5) R has a core team that develop the software itself thus contributers may concentrate efforts in the extension codes and not in the software core, and OS integration. (6) There hundreds of maintainers and contributers thus it is a solid development that even has a early congress for users (7) It is possible, and there is many examples, to create a friendly graphical interface for epidemiologic users (8) There is already many functions directed to epidemiologic users such as epidemic curves, tables in stack form etc Thus I would not be surprised if one day EpiData friends also start an integration with R, as already has been done for SAS, SPSS, WinBugs, SQL, MySQL etc etc and more recently it seems that epiinfo too. Best regards to all, Abraço forte e que a força esteja com você, Dr. Pedro Emmanuel A. A. do Brasil Instituto de Pesquisa Clínica Evandro Chagas Fundação Oswaldo Cruz Rio de Janeiro - Brasil Av. Brasil 4365 Tel 55 21 3865-9648 email: pedro.brasil(a)ipec.fiocruz.br email: emmanuel.brasil(a)gmail.com ---Apoio aos softwares livres www.zotero.org - gerenciamento de referências bibliográficas. www.broffice.org ou www.openoffice.org - textos, planilhas ou apresentações. www.epidata.dk - entrada de dados. www.r-project.org - análise de dados. www.ubuntu.com - sistema operacional

1 4

Help - Auto Member Id & Checks
by epidata-list＠lists.umanitoba.ca 29 Sep '10

29 Sep '10

Hi All, I am setting up a parent-child project. At the child level, I need to capture sets of data for every member of household. I have a variable at the beginning which captures Number of people in the household. The problem is I want the Household Member Id to be automated, secondly I want to ensure all members data are captured and equals the total number in the household initially specified. Kindly help with statements to use to achieve these two things. Thank you. Bola Adedoyin DCConsult, Lagos, Nigeria

1 1

Re: [EpiData-list] Entry/Manager test
by epidata-list＠lists.umanitoba.ca 20 Sep '10

20 Sep '10

Hi Jamie Could you please explain why you changed the booleans to 0-1 before loading it into manager? Sorry if this is a silly question. I am asking because someone recently gave me an outbreak file where they had used 0 and 1 (created in Excel 0 = no and 1 = yes). The problem was that when I came to analyse it (in this case using Epi Info) it meant that the two by two tables were in the wrong order. Because no was 0 it came out first in the table. I have always used the boolean field in epidata for our outbreak questionnaires and it has worked very well. They come out in the right order in both Epidata Analysis and Epin Info, and also make intuitive sense to the data entry person. thank you Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 13/09/2010 2:34 p.m. >>> I successfully loaded a moderately-sized .rec file (changing all booleans to 0-1 before loading into Manager--it should prompt to do that for us). Entry handled the existing and new data as expected. I would like to have the autojump to next field when all digits are filled. I assume that this is coming. I successfully loaded a fictitious file with just under 500,000 records and 12 fields (41.8 MB .epx from an 8 MB .rec). Given the capacity of removable memory today, size really isn't a problem. I cannot imagine ever having a real file that large. On my old Windows laptop, this file loaded/saved in 20-30 seconds, but GO TO any record in the file was instantaneous. Jamie -- 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 ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Re: EpiData-list Digest, Vol 83, Issue 2
by epidata-list＠lists.umanitoba.ca 16 Sep '10

16 Sep '10

Dear Suzanna, Many thanks for your help. The survey questions in which participants have entered more that one tick is like a multiple choice question, however, there is only one right answer. In many of the instances, participants have answered the right answer and also a wrong answer? I was wondering, what you would usually do in this instance? Thank you very much, Kind regards, Niamh On 16 Sep 2010, at 08:24, 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: First public test of new Entry Client (xml file > structure) - please test and comment (epidata-list(a)lists.umanitoba.ca) > 2. Re: First public test of new Entry Client (xml file > structure) - date and keyboard entry (epidata-list(a)lists.umanitoba.ca) > 3. Re: First public test of new Entry Client (xml file > structure) - date and keyboard entry (epidata-list(a)lists.umanitoba.ca) > 4. Entry/Manager test (epidata-list(a)lists.umanitoba.ca) > 5. Further on first public test of new Entry Client (xml file > structure) - please test and comment (epidata-list(a)lists.umanitoba.ca) > 6. Sample file in Entry and how to handle date formulations in > entry (epidata-list(a)lists.umanitoba.ca) > 7. RE: Command that Can affect Two diffrent Records > (epidata-list(a)lists.umanitoba.ca) > 8. (no subject) (epidata-list(a)lists.umanitoba.ca) > 9. RE: (no subject) (epidata-list(a)lists.umanitoba.ca) > 10. Updated version of Manager and Entry Client > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 11 Sep 2010 10:33:00 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] First public test of new Entry Client (xml > file structure) - please test and comment > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP857172775F5E4170435E14FD750(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > Manager and Client behave pretty well on my Mac (Intel) and in Windows Vista. > > Field entry is as expected, ignoring invalid keys and limiting lengths. Dates seem to go in properly, with short dates being assigned to the first fields. I would prefer that a single number entered in a date field be assigned to DAY, but realize this is a design issue that all of us can deal with. > > It will be good when the cursor changes without a mouse click, but that's not a problem in a test version. > > Congratulations on getting to this step! > > Jamie Hockin > > > > On 2010-09-10, at 5:38 AM, epidata-list(a)lists.umanitoba.ca wrote: > >> Therefore it is a crucial step in the development that users having either Linux, Macintosh or Windows operating systems can now test the new software released in as well 32 and 64bit versions for as well Manager and Data Entry Client (a+b). > > > > ------------------------------ > > Message: 2 > Date: Sat, 11 Sep 2010 17:10:44 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] First public test of new Entry Client (xml > file structure) - date and keyboard entry > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4C8B9BF4.20908(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Jamie comments on keyboard and movements. > > The strategy for moving after a key press or mouse in Entry Client is this: > a. tab, "arrow down" or enter : move to next field > b. shift+tab, "arrow up": move to previous field > c. when clicking with the mouse: move to that field > d. arrow down in last field: move to first field > e. arrow up in first field: move to last field > > The date rule now is: > One number: entered as first of dmy/mdy/ymd type, e.g. year for ymd > Two numbers: entered as first of dmy/mdy/ymd type, e.g. year for ymd > if more than 12 in a mdy field, then reject entering > > More than two numbers: depends in the same manner on field type > (dmy/mdy/ymd) > > Jamie Hockin suggests to always use a single (or two) digits as day, and > I suppose up to four digits always as day + month. > > Please discuss here on the list which logic you would like to see. > > regards > Jens Lauritsen > EpiData Association > > > ------------------------------ > > Message: 3 > Date: Sat, 11 Sep 2010 13:42:39 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] First public test of new Entry Client (xml > file structure) - date and keyboard entry > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP80F8E72A0DA6063F8B2023FD750(a)phx.gbl> > Content-Type: text/plain; charset=us-ascii > > I think it is trickier if 2 numbers (or 4 digits) are entered for a date. I would propose that anything other than a single number follow the day and month scheme established for the field. So entering 1011 for a <dd/mm/yyyy> field yields 10 November, but 11 October for a <mm/dd/yyyy> field or <yyyy/mm/dd> field. It's a bit of backwards logic, but would be easily explained to anyone doing data entry. But I have no strong feeling about that. > > Jamie > > > > On 2010-09-11, at 11:10 AM, epidata-list(a)lists.umanitoba.ca wrote: > >> The date rule now is: >> One number: entered as first of dmy/mdy/ymd type, e.g. year for ymd >> Two numbers: entered as first of dmy/mdy/ymd type, e.g. year for ymd >> if more than 12 in a mdy field, then reject entering >> >> More than two numbers: depends in the same manner on field type (dmy/mdy/ymd) >> >> Jamie Hockin suggests to always use a single (or two) digits as day, and I suppose up to four digits always as day + month. >> >> Please discuss here on the list which logic you would like to see. > > > > ------------------------------ > > Message: 4 > Date: Sun, 12 Sep 2010 22:34:46 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Entry/Manager test > To: epidata-list <EpiData-list(a)lists.umanitoba.ca> > Message-ID: > <AANLkTinqB2oSGV46s83VOZ6xCNiK-HRnt9Eau_gLvNs3(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I successfully loaded a moderately-sized .rec file (changing all booleans to > 0-1 before loading into Manager--it should prompt to do that for us). Entry > handled the existing and new data as expected. > > I would like to have the autojump to next field when all digits are filled. > I assume that this is coming. > > I successfully loaded a fictitious file with just under 500,000 records and > 12 fields (41.8 MB .epx from an 8 MB .rec). Given the capacity of removable > memory today, size really isn't a problem. I cannot imagine ever having a > real file that large. On my old Windows laptop, this file loaded/saved in > 20-30 seconds, but GO TO any record in the file was instantaneous. > > Jamie > > > ------------------------------ > > Message: 5 > Date: Mon, 13 Sep 2010 10:21:39 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Further on first public test of new Entry > Client (xml file structure) - please test and comment > To: EpiData-list(a)lists.umanitoba.ca > Message-ID: <4C8DDF13.1030803(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Users are urged to test as well data definition, change in definitions > and entry in files. Also please comment the development on this list. > > You can see more about the testing in the announcement mail sent a few > days ago. > > The following aspects will be fixed first: > a. Handling of decimal point, date and time visually > b. Autojump of a field in entry. E.g. in a one digit field > move to next field after entry of one digit. > c. Add to the help menu a "copy system & version to clipboard" > d. Handling issues of varying size of length of texts in Linux > versus Windows. To ensure cross-platform of files. > > further comments: > > re a: > We attempt this strategy: The user will see according to local standard > (. or , for numbers, /- for dates etc.). The physical epx file will > contain a given specified standard. We never use thousands separator. > > re c: we need this since versions will change often, and a given problem > might have been fixed. But the user have currently no way of easily > copying this information. > > > Regards to all > > Jens Lauritsen > Initiator and coordinator of EpiData Software > Denmark > > > > > ------------------------------ > > Message: 6 > Date: Mon, 13 Sep 2010 10:42:11 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Sample file in Entry and how to handle date > formulations in entry > To: EpiData-list(a)lists.umanitoba.ca > Message-ID: <4C8DE3E3.4020403(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Notice that when you open the Entry Client, the file sample.epx is > automatically loaded if the file is in the same folder as the exe files. > The file contains 12 records with examples of local font texts. If you > prefer NOT to have this file loaded every time, then just rename or move > the sample.epx to another folder. > > ...................................................................................................................................................... > > Specification of entry of dates. > > Please comment on which strategy you find most attractive: > > A: The date rule depends on (dmy/mdy/ymd) (current implementation) > B. The date rule is independent of type of field (dmy/mdy/ymd): > C: Combination of A and B > > A: > Enter digits to the field type first part (YMD/DMY/MDY) and fill in > current (day month or year) from "today" for the parts not entered. E.g. > one number is day in a DMY field, but year (+2000) in a YMD field. Try > this strategy in current sample file. > > B: > one digit: always day - automatically add current month + year > two digits: always day - automatically add current month + year > three digits: the first two are handled as a day, the third as month > four digits: the first two are handled as a day, the third+fourth as month > five or more up to 8 digits: the first two as a day, the third+fourth > as month, > 5 and up as year (+ centenary) > > C1: > one digit: always day - automatically add current month + year > two digits: always day - automatically add current month + year > if more than two follow same principle as A. > > C2: > one digit: always day - automatically add current month + year > two digits: always day - automatically add current month + year > three digits: the first two are handled as a day, the third as month > four digits: the first two are handled as a day, the third+fourth as month > if more than four follow same principle as A. > > The rule should be simple to explain or else wrong data will be entered. > > Possibly principle C1 is the simplest to explain. > > Please comment > > regards > Jens Lauritsen > EpiData Association > > > ------------------------------ > > Message: 7 > Date: Mon, 13 Sep 2010 01:56:29 -0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] RE: Command that Can affect Two diffrent > Records > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <AANLkTinTJV59NW_r+mseHvSpj0CoasGpRo+g0SyYZ5h5(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello Louk Meertens, > Thank you for trying to help me, but i have not received the Zip file you > said you attached. I will real appreciate if you send me those files because > its seems they will be a perfect example to the solution of my problem. > Thank you (If you don't mind you can send them direct to "edson.bk(a)live.com > ") > Regards > Edson B > > > ------------------------------ > > Message: 8 > Date: Mon, 13 Sep 2010 22:12:48 +0100 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] (no subject) > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Message-ID: <5CF6643E-208F-4842-9238-ECFED5623F7C(a)mail.dcu.ie> > Content-Type: text/plain; charset=us-ascii > > Hi all, > > I am new to using epidata and I was wondering if some one could be of help to me. I have put my quantitative questionnaire into epidata & have did the rec & chk forms also. I have assigned variables such as 88-for a question/tick box which any participant has missed or left un-ticked, and 99-for a question/tick box which the answer is unknown- ie If the participant ticks for example both a true & false answer. > > I am wondering for in the multiple choice aspect of my questionairre, some participants have ticked two boxes and I was wondering how do I deal with this during data entry Into epidata? Or do I need to go back & edit my ques & rec to facilitate this, > > Thanks in advance for the help, > > Niamh > > > > > ------------------------------ > > Message: 9 > Date: Tue, 14 Sep 2010 09:59:09 +1000 > From: epidata-list(a)lists.umanitoba.ca > Subject: RE: [EpiData-list] (no subject) > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: > <FB907A0DE4BDA84683C41C66CF81684001178271(a)murmx.mcri.edu.au> > Content-Type: text/plain; charset="us-ascii" > > Hi Niamh, > > Are the questions where participants have ticked 2 boxes "tick as many > as apply" type of questions, > > e.g. Which health practitioners are involved in managing your diabetes? > (tick as many as apply) > - Endocronoligist > - GP > - Nurse > - Dietician > - Other > > For such questions I set up a separate field for each option, then 1 is > entered if the box is ticked and 0 if it's not ticked. If on the other > hand participants are ticking multiple boxes where they should only be > ticking one, what should be entered would be up to the project manager. > The decision needs to be consistent and documented. If the responses are > a likert scale, e.g. strongly agree, agree, neither agree nor disagree, > disagree, strongly disagree, they may chose to take the more > conservative response - or a response in the middle if the 2 boxes > ticked aren't next to each other. There's no easy answer to this. It > depends on the research question the study is designed to answer and > needs to be considered separately for each question on the survey where > this has happened. > > Regards, > > 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 > -----Original Message----- > From: epidata-list-bounces(a)lists.umanitoba.ca > [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of > epidata-list(a)lists.umanitoba.ca > Sent: Tuesday, 14 September 2010 7:13 AM > To: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] (no subject) > > Hi all, > > I am new to using epidata and I was wondering if some one could be of > help to me. I have put my quantitative questionnaire into epidata & have > did the rec & chk forms also. I have assigned variables such as 88-for a > question/tick box which any participant has missed or left un-ticked, > and 99-for a question/tick box which the answer is unknown- ie If the > participant ticks for example both a true & false answer. > > I am wondering for in the multiple choice aspect of my questionairre, > some participants have ticked two boxes and I was wondering how do I > deal with this during data entry Into epidata? Or do I need to go back & > edit my ques & rec to facilitate this, > > Thanks in advance for the help, > > Niamh > > > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > ------------------------------ > > Message: 10 > Date: Thu, 16 Sep 2010 09:02:03 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Updated version of Manager and Entry Client > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4C91C0EB.9090907(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Dear EpiData list. > > A new version of the programs EpiData Manager and EpiData Entry Client > have been release for public testing. > > The program can be found in a bundled package on the testing page of > EpiData website: http://epidata.dk/testing.php > > Changes with the new version: > > * On certain OS's and regional settings, the program could create > datafiles (*.epx) that could not be read again. This has been > fixed such programs should support local settings for decimal-, > date- and time separators, while still being able to work > cross-platform. > * In the Entry Client "autojump on filled field" has been implemented. > * Both Entry Client and Manager have a "Copy Version Info" menu > item, that will copy the most needed details about program version > and possibly open project to the clipboard. This information is > very often vital for locating problems within a program and should > be sent with when reporting error to us. > > > Kind regards > Torsten Bonde Christiansen > EpiData Association. > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 83, Issue 2 > *******************************************

1 1

Updated version of Manager and Entry Client
by epidata-list＠lists.umanitoba.ca 16 Sep '10

16 Sep '10

Dear EpiData list. A new version of the programs EpiData Manager and EpiData Entry Client have been release for public testing. The program can be found in a bundled package on the testing page of EpiData website: http://epidata.dk/testing.php Changes with the new version: * On certain OS's and regional settings, the program could create datafiles (*.epx) that could not be read again. This has been fixed such programs should support local settings for decimal-, date- and time separators, while still being able to work cross-platform. * In the Entry Client "autojump on filled field" has been implemented. * Both Entry Client and Manager have a "Copy Version Info" menu item, that will copy the most needed details about program version and possibly open project to the clipboard. This information is very often vital for locating problems within a program and should be sent with when reporting error to us. Kind regards Torsten Bonde Christiansen EpiData Association.

1 1

EpiData Manager and EpiData Entry test versions
by epidata-list＠lists.umanitoba.ca 16 Sep '10

16 Sep '10

Comments on versions of 16 Sep 2010: EpiData Manager: epidatamanager.0.5.5.0.i386-win32.exe EpiData Entry: epidataentry.0.1.1.0.i386-win32.exe Test with existing REC file, 130,000 real records, 9 fields First approach: In EpiData Manager: Add structure from File: Existing field names are not respected as new field names but given V1, V2, ...: v1 country Study country Original: country Study country # After editing, so that "v1" becomes "country", etc: Opening epidataentry and importing original REC file: Corruption: In 'stream': (line 1 positiong 1): illegal at document level View line 1: 13 1 VLAB Deleting first line creates another error Second approach: Open EpiData Manager Load datafile, using existing REC file, REC file is loaded The last 3 fields in the REC file (QES file shown) are: result1 Result of first examination #.# result2 Result of second examination #.# result3 Result of third examination #.# In EpiData Manager correctly: length 1 decimal 1 Open epidataentry and REC file: The three above fields are truncated to become integers, in text editor: <Record f0="1" f1="101" f3="2003" f4="57" f5="2" f6="0" f7="0" f8="9" f9="9" st="0"/> Regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

(no subject)
by epidata-list＠lists.umanitoba.ca 13 Sep '10

13 Sep '10

Hi all, I am new to using epidata and I was wondering if some one could be of help to me. I have put my quantitative questionnaire into epidata & have did the rec & chk forms also. I have assigned variables such as 88-for a question/tick box which any participant has missed or left un-ticked, and 99-for a question/tick box which the answer is unknown- ie If the participant ticks for example both a true & false answer. I am wondering for in the multiple choice aspect of my questionairre, some participants have ticked two boxes and I was wondering how do I deal with this during data entry Into epidata? Or do I need to go back & edit my ques & rec to facilitate this, Thanks in advance for the help, Niamh

1 1

RE: Command that Can affect Two diffrent Records
by epidata-list＠lists.umanitoba.ca 13 Sep '10

13 Sep '10

Hello Louk Meertens, Thank you for trying to help me, but i have not received the Zip file you said you attached. I will real appreciate if you send me those files because its seems they will be a perfect example to the solution of my problem. Thank you (If you don't mind you can send them direct to "edson.bk(a)live.com ") Regards Edson B

1 0

Sample file in Entry and how to handle date formulations in entry
by epidata-list＠lists.umanitoba.ca 13 Sep '10

13 Sep '10

Notice that when you open the Entry Client, the file sample.epx is automatically loaded if the file is in the same folder as the exe files. The file contains 12 records with examples of local font texts. If you prefer NOT to have this file loaded every time, then just rename or move the sample.epx to another folder. ...................................................................................................................................................... Specification of entry of dates. Please comment on which strategy you find most attractive: A: The date rule depends on (dmy/mdy/ymd) (current implementation) B. The date rule is independent of type of field (dmy/mdy/ymd): C: Combination of A and B A: Enter digits to the field type first part (YMD/DMY/MDY) and fill in current (day month or year) from "today" for the parts not entered. E.g. one number is day in a DMY field, but year (+2000) in a YMD field. Try this strategy in current sample file. B: one digit: always day - automatically add current month + year two digits: always day - automatically add current month + year three digits: the first two are handled as a day, the third as month four digits: the first two are handled as a day, the third+fourth as month five or more up to 8 digits: the first two as a day, the third+fourth as month, 5 and up as year (+ centenary) C1: one digit: always day - automatically add current month + year two digits: always day - automatically add current month + year if more than two follow same principle as A. C2: one digit: always day - automatically add current month + year two digits: always day - automatically add current month + year three digits: the first two are handled as a day, the third as month four digits: the first two are handled as a day, the third+fourth as month if more than four follow same principle as A. The rule should be simple to explain or else wrong data will be entered. Possibly principle C1 is the simplest to explain. Please comment regards Jens Lauritsen EpiData Association

1 0

Further on first public test of new Entry Client (xml file structure) - please test and comment
by epidata-list＠lists.umanitoba.ca 13 Sep '10

13 Sep '10

Users are urged to test as well data definition, change in definitions and entry in files. Also please comment the development on this list. You can see more about the testing in the announcement mail sent a few days ago. The following aspects will be fixed first: a. Handling of decimal point, date and time visually b. Autojump of a field in entry. E.g. in a one digit field move to next field after entry of one digit. c. Add to the help menu a "copy system & version to clipboard" d. Handling issues of varying size of length of texts in Linux versus Windows. To ensure cross-platform of files. further comments: re a: We attempt this strategy: The user will see according to local standard (. or , for numbers, /- for dates etc.). The physical epx file will contain a given specified standard. We never use thousands separator. re c: we need this since versions will change often, and a given problem might have been fixed. But the user have currently no way of easily copying this information. Regards to all Jens Lauritsen Initiator and coordinator of EpiData Software Denmark

1 0

Entry/Manager test
by epidata-list＠lists.umanitoba.ca 12 Sep '10

12 Sep '10

I successfully loaded a moderately-sized .rec file (changing all booleans to 0-1 before loading into Manager--it should prompt to do that for us). Entry handled the existing and new data as expected. I would like to have the autojump to next field when all digits are filled. I assume that this is coming. I successfully loaded a fictitious file with just under 500,000 records and 12 fields (41.8 MB .epx from an 8 MB .rec). Given the capacity of removable memory today, size really isn't a problem. I cannot imagine ever having a real file that large. On my old Windows laptop, this file loaded/saved in 20-30 seconds, but GO TO any record in the file was instantaneous. Jamie

1 0

First public test of new Entry Client (xml file structure) - please test and comment
by epidata-list＠lists.umanitoba.ca 11 Sep '10

11 Sep '10

Announcement: An important development step has been reached: The first public test release of the new EpiData Data Entry Client. Since the first release of EpiData software in 1999 focus has been on data quality, stability and simplicity seen from the end users point of view. This strategy has been extended with more functionality and release of Analysis some years ago. Following the large user base resulting in download counts in several thousands as documented on the download pages - and unknown dissemination of copies to other users - an important decision was made a few years back to rewrite the whole software for the next decade. This has resulted in change to a new development environment (freepascal and Lazarus - see lazarus.org), which allows for crossplatform development based on the same source code, but also a new file structure. The EpiData XML file format "EPX" combines and replaces the current qes, chk and rec files into on physical file. It will also allow for more extensive access control at section level and compliance with so-called GCP (Good Clinical Practice) principles. The specification of the EPX format takes place in discussions with The Danish Data Archives (http://samfund.dda.dk/default-en.asp) in relation to securing compatibility with the DDI formats (see http://www.ddialliance.org/) The file structure will be fully documented. Currently you can see the principles in http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat:xml_v0 The re-written software will consist of three parts - and possibly batch processors for repetitive tasks. a. EpiData Data Manager b. EpiData DataEntry Client c. EpiData Analysis Therefore it is a crucial step in the development that users having either Linux, Macintosh or Windows operating systems can now test the new software released in as well 32 and 64bit versions for as well Manager and Data Entry Client (a+b). Users are urged to test as well data definition, change in definitions and entry for files. Also please comment the development on this list. In particular test and discuss these aspects: a. can we define all structures we would like ? - notice that in definition of data paste of text and qes like structures is possible b. is the naming of structures and aspects correct ? c. is the "feel of the software" easy to adapt to from earlier versions ? d. Also test local language formulations of data forms and entered data. In particular point c is important. We have to renew the system and principles. but would not like to loose a large number of users. Notice that the current release is NOT containing the controls in check files, but this will come later. We have a detailed development plan, which has been discussed in previous mails on this list. In the sample data base we have included 12 different local language fonts, which we can see on our monitors here, including Danish, Asian and right-left such as Arabic. The text included should say "Sample text", which we translated with an automatic translator on the web. On linux the right-left or left-right is shown correctly, but in windows all local fonts are aligned to the left border of the text field. The current test release is not for production, but only for test. But we proceed to add further functionality and more introduction documents until most of what was contained previously is available. Programming is done by Torsten Christiansen here in Denmark and specification via current functionality in EpiData Entry and Analysis, plus the discussions on this list and with the "Friends of EpiData Group", see the credit page on epidata.dk. The test version is released as a combined package of Manager plus Entry Client, but also includes the "sample.epx" file and is found on: http://www.epidata.dk/testing.php As soon as stability has been secured via your tests we will change the status from test to release with limited functionality. The time for this is not defined, but some aspects are crucial before turning to first actual release, e.g. secured timed back-up or reading of EPX files into analysis. One major change for entry is that now all data resides in memory until saved, therefore the user is asked to save project when closing. This will result in longer load times at the initiation of entry, but allows for quicker search and moves between records. Regards to all Jens Lauritsen Initiator and coordinator of EpiData Software Denmark

1 3

When do we have open source of EpiData?
by epidata-list＠lists.umanitoba.ca 09 Sep '10

09 Sep '10

Hello: I want to know when we have released for the public the source code of EpiData? I see on the web page of EpiData that this initiative is part of the interesting strategy. By the way I'm using EpiData because of that, along with other reasons like the low resources of hardware demanding to execute it. Regards, -- Omar Bautista González - Coordinador de Investigación para el Desarrollo, Diseño, Monitoreo y Evaluación Visión Mundial República Dominicana - Colaborador en investigación social del movimiento del software libre en República Dominicana

1 2

Command that Can affect Two diffrent Records
by epidata-list＠lists.umanitoba.ca 08 Sep '10

08 Sep '10

Hello, I have a questionnaire that i got from interviewing household members. However i was making sure that from each household i interview a male and a female respondent. You realize that some of the questions here for a household have got have the same answers eg Number of persons in the household, number of mosquito nets in the household etc. So, am inquiring to know whether there is any command i can include in my chk file to identify error between two records. I badly need your help, otherwise its so tiresome to check over 1500 records pair by pair. Thank you and regards Edson B Statistician River Blindness Elimination Program, Uganda

1 2

sf36 scoring file for EpiData - as pgm file ?
by epidata-list＠lists.umanitoba.ca 27 Aug '10

27 Aug '10

Does anyone have a scoring algorithm for SF36 - in the free version - not the licensed one, where one has to pay to Qualimetrics for usage. ? regards Jens Lauritsen Epidata Association Denmark

1 0

Double entry and validation
by epidata-list＠lists.umanitoba.ca 17 Aug '10

17 Aug '10

We have troubles with 'Double entry and validation'. We have chosen Tools - Prepare Double Entry Verification, chosen a key field to match records and 'Ignore text fields'. The first time it functioned OK - Epidata stopped, when the control entry differed from the original one, and you could chose between the original entry or the new one. But when a collegue started the following day, Epidata did not react, when the control entry differed from the original one. What are we doing wrong? Yours Søren Skadhede Computer Programmer Enheden for Psykiatrisk Forskning Aalborg Psykiatriske Sygehus +45 721 37229 / +45 2244 3951 e-mail: sosk(a)rn.dk<mailto:sosk@rn.dk>

1 0

Re EpiData notes file
by epidata-list＠lists.umanitoba.ca 16 Aug '10

16 Aug '10

Thanks to everyone who responded to my plea for help. 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/>

1 0

EpiData Notes file
by epidata-list＠lists.umanitoba.ca 16 Aug '10

16 Aug '10

Can anyone help with this? We set up an EpiData database with a notes file <filename>.not. The notes file appears to have corrupted and has taken the qualitative data from over 40 surveys with it. I was wondering if there was any way I could recover this or if I'll need to re-enter all the data manually into a word document. To help work out what/where/if something went wrong with EpiData the breakdown of events is as follows: * First ~45 surveys are entered without issue. * From ~survey 45 when the notes file opened up it would not allow me to type unless I pressed enter a few times and then backspace (pressing enter once and backspace once would create space for two characters to be typed). It was cumbersome but the data was still going in alright. * On closing the notes file whilst entering survey 60 the computer froze for a moment and EpiData was 'not responding' for about 20-30 seconds and then went back to normal functioning. * The next time the notes file was opened the cursor appeared about halfway through the qualitative data for survey 19 and all data after there had been wiped. I opened the notes file in notepad to confirm this was the case. Do you know of some recovery technique for this kind of problem? Thanks, 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/>

1 3

How to define Jumps at a variable using another variable
by epidata-list＠lists.umanitoba.ca 12 Aug '10

12 Aug '10

Hi all, Please help me on how I can define this jumps. Variable a04 is exact age of respondent while variable a06 is another question. Variable a06 is only applicable to respondents whose age range is 0-18 otherwise a jump is required to variable a08. This is what I have done below but I keep getting error message. Kindly help on how I can achieve the jumps. Thank you. Bola Adedoyin (Mrs) DC Pro-Data Consult Lagos, Nigeria a06 BEFORE ENTRY define tempv # IF a04 RANGE 0 18 THEN tempv=1 ELSE tempv=2 ENDIF tempv JUMPS 2 a08 END END END END

1 9

Help - Merging parent and child file into a single file
by epidata-list＠lists.umanitoba.ca 10 Aug '10

10 Aug '10

Hi all, Please how can I make parent and child datafile merge into one single file when converting the data to SPSS. Thank you. Bola Nigeria

1 1

Design decision for Data Entry Client
by epidata-list＠lists.umanitoba.ca 10 Aug '10

10 Aug '10

Development of the stand alone Data Entry Client is progressing and we need to take some decisions. In short the revised setup will be such that a project manager person will use the EpiData Data Manager to define data files, to document file contents etc. whereas the actual data entry will be done with a dedicated Entry Client, which can only do entry. On the list it was suggested earlier that it is important that the entry persons can get a quick overview, e.g. by data lists, spreadsheet view of the data or a codebook. We will look at this later. I invite you all to discuss and comment on the following aspects: a. Show field names on entry form. Could be either: A1 Be part of the data file definition (sort of built into the datafile) A2: Defined via an ini file for the client I tend to think that this is part of the project managers decision, and therefore it should be A1, but I am not sure. Currently this is NOT part of the data file definition, but part of the ini file for the Manager . . b. When the Entry Client opens a data file, which record should be shown ? b1. The first one b2. The last one b3. An empty "new" record - ready for entry (as in current EpiData Entry) Would depend on the project. I suggest we decide on b2. This shows how far entry is and the user can then issue a specific action to continue adding (e.g. ctrl+N). We can always discuss later if some of this could be controlled by commands or specifications, but a default must be defined now. Regards Jens Lauritsen EpiData Association

1 3

Re: EpiData-list Digest, Vol 82, Issue 6
by epidata-list＠lists.umanitoba.ca 10 Aug '10

10 Aug '10

Thanks Hans and Jamie. Your suggestion worked for me. Regards, Bola --- On Mon, 9/8/10, epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> wrote: From: epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Subject: EpiData-list Digest, Vol 82, Issue 6 To: epidata-list(a)lists.umanitoba.ca Date: Monday, 9 August, 2010, 10:00 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: How to define Jumps at a variable using another variable (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Sun, 8 Aug 2010 13:21:13 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How to define Jumps at a variable using another variable To: epidata-list(a)lists.umanitoba.ca Message-ID: <BLU0-SMTP69AE1A89EB290445795DDAFD930(a)phx.gbl> Content-Type: text/plain; charset=us-ascii You should do this with GOTO as Hans suggests: a06 before entry if (a04 >=0 and a04 <=18) then goto a08 endif end end blocks that begin with a variable name cannot appear within the block for another variable. If you need to use the variable tempv elsewhere, then include this at the top of your check file before file define tempv # global end Jamie On 2010-08-05, at 7:25 AM, epidata-list(a)lists.umanitoba.ca wrote: > Variable a04 is exact age of respondent while variable a06 is another question. Variable a06 is only applicable to respondents whose age range is 0-18 otherwise a jump is required to variable a08. This is what I have done below but I keep getting error message. > > Kindly help on how I can achieve the jumps. > > Thank you. > > Bola Adedoyin (Mrs) > DC Pro-Data Consult > Lagos, Nigeria > > a06 > BEFORE ENTRY > define tempv # > IF a04 RANGE 0 18 THEN tempv=1 > ELSE tempv=2 > ENDIF > tempv > JUMPS > 2 a08 > END > END > END > END ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 82, Issue 6 *******************************************

1 0

Help: How to define Jumps at a variable using another variable
by epidata-list＠lists.umanitoba.ca 05 Aug '10

05 Aug '10

--- On Thu, 5/8/10, Bola Adedoyin <madedoyinng(a)yahoo.com> wrote: From: Bola Adedoyin <madedoyinng(a)yahoo.com> Subject: How to define Jumps at a variable using another variable To: epidata-list(a)lists.umanitoba.ca Date: Thursday, 5 August, 2010, 4:25 Hi all, Please help me on how I can define this jumps. Variable a04 is exact age of respondent while variable a06 is another question. Variable a06 is only applicable to respondents whose age range is 0-18 otherwise a jump is required to variable a08. This is what I have done below but I keep getting error message. Kindly help on how I can achieve the jumps. Thank you. Bola Adedoyin (Mrs) DC Pro-Data Consult Lagos, Nigeria a06 BEFORE ENTRY define tempv # IF a04 RANGE 0 18 THEN tempv=1 ELSE tempv=2 ENDIF tempv JUMPS 2 a08 END END END END

1 0

help
by epidata-list＠lists.umanitoba.ca 03 Aug '10

03 Aug '10

Hello, I'm in the process of learning how to use EpiData Analysis. I'm going through the instructions in the Tiramisu example. I've run into a problem. I'm trying to create the epicruve/histogram. The graph window (Editing Chart) is not showing up. I looked through comments on the [EpiData-list] and found a recommendation: insert (set graph edit=on) in the command line. I tried this but received this message (graph edit not supported). How do I turn on the (editing chart) window? Thanks, Sandy

1 4

Extending command over multiple lines
by epidata-list＠lists.umanitoba.ca 02 Aug '10

02 Aug '10

Is there a way of extending a command in the EpiData Entry CHK file beyond a single line? In my example below I've got around the problem by using nested IF... THENs but there may be another way. For instance in Stata a command can be extended over multiple lines by ending each line with ///. admit1mon AFTER ENTRY IF (admit1mon<>"JAN") AND (admit1mon<>"FEB") AND (admit1mon<>"MAR") AND (admit1mon<>"APR") AND (admit1mon<>"MAY") AND admit1mon<>"JUN") THEN IF (admit1mon<>"JUL") AND (admit1mon<>"AUG") AND (admit1mon<>"SEP") AND (admit1mon<>"OCT") AND (admit1mon<>"NOV") AND (admit1mon<>"DEC") THEN HELP "Month is a 3 character field, e.g. JAN, FEB, etc" TYPE=ERROR GOTO admit1mon CLEAR admit1mon ENDIF ENDIF END END 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/>

1 5