- EpiData-list - University of Manitoba Mailing Lists

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