- EpiData-list - University of Manitoba Mailing Lists

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