- EpiData-list - University of Manitoba Mailing Lists

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