- EpiData-list - University of Manitoba Mailing Lists

New data format for testing and comments - tests needed
by epidata-list＠lists.umanitoba.ca 02 Oct '09

02 Oct '09

An exiting phase of development is now ready for general comments and testing. In june/july of this year the first cross platform experiments were available published on the testing page http://www.epidata.dk/testing.php Crossplatform function must solve aspects such as: - many different local character sets - different standards for physical file formats - the user should not do anything special when sending or receiving files created on another operating system On top of this another issue is coming up soon - the development of a dedicated data entry module also allowing for GCP (Good Clinical Practice) rules of transaction logging. Therefore we have now experimented with development and specification of a file format which contains as well the data as the metadata needed for understanding the data. By doing so we are moving towards a new structure: a. Datafile containing datadefinition and data. (parts of current rec and chk file). Suggested extension: recxml b. Dataentry definition file containing control during entry (e.g. relate, range, mustenter etc). Suggested extension: chkxml - part b not developed yet The proposed new data format is described here: http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat_xml Just now users are encouraged to test the following: 1. Can the test application read your files ? 2. Can the test application write your files ? 3. In particular test - when possible - whether the data files can be read on another operating system. E.g. saved by a Linux or Mac and then read on a windows pc. Get the test application from: http://www.epidata.dk/testing.php And report to the epidata-list of failures and success. Data formats supported are: REC, RECXML, ODF, DBF, XLS A table of what can be imported and exported is shown here: http://www.epidata.org/dokuwiki/doku.php/documentation:importexport Operating systems supported are: Mac (OS X), Linux (32+64bit), Windows. Mac PowerPC expected soon. After a few weeks of comments on the format a new test application will be created. Which will collect some time estimates of reading and writing data with subsequent reporting to a central database. This method should allow for future user tests of core modules with documentation available on the central website. Regards Jens Lauritsen EpiData Association

1 0

V2.2.1 of EpiData Analysis uploaded
by epidata-list＠lists.umanitoba.ca 01 Oct '09

01 Oct '09

v2.2.1 (Build 171) of EpiData Analysis has been uploaded. The only changes are: Fixing mismatch of subfoot and estimates information on SPC charts. Extending information for RunCharts - telling the number of measurements and points omitted on median. regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 71, Issue 6
by epidata-list＠lists.umanitoba.ca 24 Sep '09

24 Sep '09

The best way is to create a new variable from the old var Then pursue with the analysis. Alternatively, you should work on the original file .rec then .che before moving on the analytical part. Best wishes Tieble 2009/9/24 <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. losing checks after inserting new variables and saving data > in Epidata Analysis (epidata-list(a)lists.umanitoba.ca) > 2. Re: losing checks after inserting new variables and saving > data in Epidata Analysis (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 Sep 2009 12:30:28 +0530 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] losing checks after inserting new variables > and saving data in Epidata Analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <367f37ad0909240000u631a3637i4dec713b968ce095(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I am losing all my checks in the rec file after I insert new variables > using > Epidata Analysis and saving the file using command savedata. Please advise > how to retail my file structure as well as checks after I insert some new > variables using Epidata Analysis. > > -- > Ajay Kumar Reddy > > > ------------------------------ > > Message: 2 > Date: Thu, 24 Sep 2009 07:34:09 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] losing checks after inserting new > variables and saving data in Epidata Analysis > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4ABB5931.2000905(a)sympatico.ca> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have not had that problem using the current release. You can check the > version of Analysis under the help menu. When you SAVEDATA, Analysis > does create the corresponding .chk along with any new label values you > created for the new variables. You should be saving to a different file > name. > > What you can do if you continue to have this problem is to manually copy > the .chk for the original file to a new .chk that matches the file > created with SAVEDATA. > > I am losing all my checks in the rec file after I insert new variables > using > > Epidata Analysis and saving the file using command savedata. Please > advise > > how to retail my file structure as well as checks after I insert some new > > variables using Epidata Analysis. > > > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 71, Issue 6 > ******************************************* >

1 0

losing checks after inserting new variables and saving data in Epidata Analysis
by epidata-list＠lists.umanitoba.ca 24 Sep '09

24 Sep '09

I am losing all my checks in the rec file after I insert new variables using Epidata Analysis and saving the file using command savedata. Please advise how to retail my file structure as well as checks after I insert some new variables using Epidata Analysis. -- Ajay Kumar Reddy

1 1

Automatic fill in
by epidata-list＠lists.umanitoba.ca 15 Sep '09

15 Sep '09

I was wondering if anybody have an easy description of how to autofill variables after an if statement Per Kjaer

1 1

RE: EpiData-list Digest, Vol 71, Issue 1
by epidata-list＠lists.umanitoba.ca 12 Sep '09

12 Sep '09

Hello, Two questions : - Is "P50 lifetable" validity in progress ? - In scatter graph, is a linear regression line planned ? Congratulations for all the progress with last versions; Bernard BRANGER, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 922 courriels spam. Nous avons en ce moment 6 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

New Core Module uploaded.
by epidata-list＠lists.umanitoba.ca 09 Sep '09

09 Sep '09

Dear EpiData users. I have posted a new version of the Core Module for testing on the EpiData website: http://epidata.dk/testing.php With the latest version it is now possible to import and export Open Office spreadsheets (Open Document Standard) although with limited support for exporting dates. Please see the wiki for information on what formats are supported: http://www.epidata.org/dokuwiki/doku.php/documentation:importexport Additionally it is also possible to export to Excel spreadsheet. Importing is yet no possible. With kind regards, Torsten Bonde Christiansen. Software Developer, Epidata.

1 2

possible strategy discussion meeting in Baltimore (sept. 12th.-18th)
by epidata-list＠lists.umanitoba.ca 02 Sep '09

02 Sep '09

Dear all During the current development phase some strategic decisions need to be taken. E.g. on data file format, data formats to support for import/export. How to handle support issues etc. What types of analysis should be supported and developed etc. I would like users to arrange locally such strategic meetings and let us know on the list of the viewpoints. If anyone in the Baltimore region in USA have interest in a strategic discussion meeting during the time from Sept. 13th. to Sept. 18th. let me know (off list). I could arrange such a meeting in late afternoons or early evening on campus at Johns Hopkins University, where I will attend a course on quality assurance . Another option is in New York on Sept. 11th. Regards Jens Lauritsen in case of interest email directly to: info at epidata.dk (disregard the return message I will contact you directly).

1 0

New EpiData Analysis b170 uploaded
by epidata-list＠lists.umanitoba.ca 23 Aug '09

23 Aug '09

Public Release Version *2.2.1* build 170 - Aug 23th 2009 * Extended o Histogram Now groups data into bins. o /CLOSE added to Generate command. o Added: /FONTSIZE and /SUBFOOT added to graph commands. * Bugs fixed o Removed Sigma3 from legend in runchart command. o Freq sorted incorrectly by default, and using /SA or /SD. o Variable name with "if" in, cause pre-processor to incorrectly insert "set option" text the wrong place. o Labelvalue command gave no error with incorrect construction. o Use of /W in tables command deleted wrong variable in some instances regards Jens Lauritsen EpiData Association

1 0

Emulating check boxes in Epidata Entry
by epidata-list＠lists.umanitoba.ca 20 Aug '09

20 Aug '09

I have been working on a data entry form that was previously in Access. It has a lot of check box fields in Access (boolean fields that are represented on the screen by a box that alternates between being checked (true) and empty (false) when clicked. There is a way to do this in Epidata, which can be useful when presenting a long list of symptoms/signs or exposures to be completed. The trick to doing this is to create Yes/No fields that cannot be entered using the tab or cursor keys. They can, however, be entered using the mouse. In this example, clicking in one of these fields will toggle the value of the field between "Y" and missing. Perhaps others will find this useful. Jamie Hockin 11 1 VLAB _label1 1 1 30 0 0 0 0 112 Emulate check boxes #id 1 3 30 4 3 12 5 112 id #age 1 5 30 5 5 0 2 112 age _sex 1 6 30 5 6 3 1 112 sex _label2 1 8 30 0 0 0 0 112 Check as many boxes as you want _a 1 10 30 3 10 5 1 112 a _b 6 10 30 9 10 5 1 112 b _c 12 10 30 15 10 5 1 112 c #xnotused 1 12 30 10 12 0 1 112 xnotused #action 1 14 30 8 14 0 1 112 action _label3 9 14 30 0 0 0 0 112 Anything to finish up 1 12M Y ! 2 11FY Y ! 3 10MYY ! * Emulate check boxes age range 0 99 end sex comment legal M Male F Female end * this is the last field before the check boxes * jump to the field beyond the check boxes goto action end * this is a checkbox field that can only be entered * by clicking the cursor * If Epidata gets to this field, it must be that the * user has clicked in the field. This means that the * value of the field is toggled between Y and missing. * Note that any other cycle of changes is possible * Y to N to Y, Y to N to blank to Y, etc * Just program the nested if ... then ... endif blocks * These blocks MUST be NESTED and not sequential. a before entry if a = "Y" then a = . else if a = . then a = "Y" endif endif goto action end end b before entry if b = "Y" then b = . else if b = . then b = "Y" endif endif goto action end end c before entry if c = "Y" then c = . else if c = . then c = "Y" endif endif goto action end end * This field is used to block going to field c * with the cursor. Cursor UP from field ACTION will * come here and immediately go back to field ACTION xnotused before entry goto action end end Emulate check boxes id <idnum> age ## sex <A> Check as many boxes as you want a <Y> b <Y> c <Y> xnotused # action # Anything to finish up

1 0