EpiData-list July 2010

epidata-list@lists.umanitoba.ca

1 participants
17 discussions

Critical fix of lastes EpiData Manager test version.

by epidata-list＠lists.umanitoba.ca

Dear Epidata List. A new version of the EpiData Manager have been placed on the testings page: http://epidata.dk/testing.php A great thanks to Jamie Hockin who identified a critical bug in to program, where project files could no longer be opened again. The new version is called 0.5.2.1 (R169) and should no longer contain this bug. With kind regards, Torsten Bonde Christiansen. EpiData Association.

13 years, 10 months

Re: EpiData-list Digest, Vol 81, Issue 4

by epidata-list＠lists.umanitoba.ca

Thank you Rafael, Sorry I just managed to look at the URL attached file and used the Stat/Transfer to import it as SAS or Stata file and the output is in agreement of what you saw previously. However, I will try it again using EpiC and get back to you. Take care and get back to you on Tuesday or Wednesday when I can access the computer. Tieble On 3 July 2010 18:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > Send EpiData-list mailing list submissions to > epidata-list(a)lists.umanitoba.ca > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > or, via email, send a message with subject or body 'help' to > epidata-list-request(a)lists.umanitoba.ca > > You can reach the person managing the list at > epidata-list-owner(a)lists.umanitoba.ca > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of EpiData-list digest..." > > > EpiData-list mailing list > ___________________________________ > > Today's Topics: > > 1. Re: Re: EpiData-list Digest, Vol 81, Issue 2 > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Re: EpiData-list Digest, Vol 81, Issue 2 > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Jul 2010 14:21:47 -0400 (EDT) > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Re: EpiData-list Digest, Vol 81, Issue 2 > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <1973065110.949481278094907507.JavaMail.root(a)simcoe.cs.uoguelph.ca> > Content-Type: text/plain; charset=utf-8 > > Hi Tieble, > > Thanks a lot for your reply. I did use EpiData export tool to send the file > to SAS. I did try to export to Excel and I had no issues with it. What do > you mean by posting lines of real data? > > Thanks again, > > Rafael > ----- Original Message ----- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Sent: Friday, July 2, 2010 5:42:40 AM GMT -05:00 US/Canada Eastern > Subject: [EpiData-list] Re: EpiData-list Digest, Vol 81, Issue 2 > > Hi Rafael, > Did you try to export into another package such as Stata, or Excel, and so > on? How did you export your data into SAS (using EpiData export tool or > Stata Transfer)? Brief, I suggest that you reconsider another package > (such > as Stata). Assuming that you have already done this, then second > suggestion > is to post a chunk of few lines of fake or your real data then you may get > appropriate help. > > Thank you > Tieble, London, UK > > > On 2 July 2010 02:52, <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: new test release of EpiData Manager available (paste text > > as fields and read qes) (epidata-list(a)lists.umanitoba.ca) > > 2. Problem exporting data to SAS (epidata-list(a)lists.umanitoba.ca) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 01 Jul 2010 21:34:27 +0200 > > From: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] new test release of EpiData Manager > > available (paste text as fields and read qes) > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: <4C2CEDC3.6010808(a)epidata.dk> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > I am quite sure everyone can understand the amount of work involved in > > the current rewriting and the need to focus and set the scope for > > development at a realistic level. > > > > One of the aspects that I currently consider not needed is the > > development of an editor. > > Power users will each have their own preference for an editor and for > > the EpiData Manager we can optimise usage of the clipboard instead of > > developing a new editor. > > > > Another issue is the need for documentation tools. My current > > understanding is that we do need: > > - double entry verification (comparing two files and showing differences) > > - count by id function (show a list of how many times a given id is > > contained in a number of files) > > - data verification according to controls built into a given data file. > > e.g. whether all mustenter, range and value label definitions are > met > > - verification of keys (unique) and listing of observations not meeting > > the defined key > > > > And I also think these should be part of the Manager, whereas other > > functions such as: > > codebook, listing and viewing data > > should be part of analysis. > > > > Comments on these aspects and the announced development phase sequence > > are welcomed on this list. > > > > > The next development phases are: a. Prevent double naming of fields > > > on a dataform b. Develop first test release of a dedicated Entry > > > Client. c. Add timed backup and date named zip file copy to Entry > > > Client function. d. Add control of entry (mustenter, range, value > > > labels) to Entry Client. e. Add multilanguage capability to dataform > > > definition and entry client. > > > > regards > > Jens Lauritsen > > EpiData Association > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Thu, 1 Jul 2010 21:40:27 -0400 (EDT) > > From: epidata-list(a)lists.umanitoba.ca > > Subject: [EpiData-list] Problem exporting data to SAS > > To: epidata-list(a)lists.umanitoba.ca > > Message-ID: > > < > 1871457764.860511278034827330.JavaMail.root(a)simcoe.cs.uoguelph.ca> > > Content-Type: text/plain; charset="utf-8" > > > > Dear members, > > > > I am currently setting up my database and faced one problem that I can't > > figure out. I entered some real data and exported to SAS. However, most > > variables are coming as missing (.), but very few are coming with the > > labels. I am thinking that it's something related to the checks on > EpiData > > and not a SAS problem. If anyone could help me I would appreciate. > Following > > attached is the .rec file. > > > > Thanks in advance, > > > > Rafael > >

13 years, 10 months

Re: EpiData-list Digest, Vol 81, Issue 2

by epidata-list＠lists.umanitoba.ca

Hi Rafael, Did you try to export into another package such as Stata, or Excel, and so on? How did you export your data into SAS (using EpiData export tool or Stata Transfer)? Brief, I suggest that you reconsider another package (such as Stata). Assuming that you have already done this, then second suggestion is to post a chunk of few lines of fake or your real data then you may get appropriate help. Thank you Tieble, London, UK On 2 July 2010 02:52, <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: new test release of EpiData Manager available (paste text > as fields and read qes) (epidata-list(a)lists.umanitoba.ca) > 2. Problem exporting data to SAS (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 01 Jul 2010 21:34:27 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] new test release of EpiData Manager > available (paste text as fields and read qes) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4C2CEDC3.6010808(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I am quite sure everyone can understand the amount of work involved in > the current rewriting and the need to focus and set the scope for > development at a realistic level. > > One of the aspects that I currently consider not needed is the > development of an editor. > Power users will each have their own preference for an editor and for > the EpiData Manager we can optimise usage of the clipboard instead of > developing a new editor. > > Another issue is the need for documentation tools. My current > understanding is that we do need: > - double entry verification (comparing two files and showing differences) > - count by id function (show a list of how many times a given id is > contained in a number of files) > - data verification according to controls built into a given data file. > e.g. whether all mustenter, range and value label definitions are met > - verification of keys (unique) and listing of observations not meeting > the defined key > > And I also think these should be part of the Manager, whereas other > functions such as: > codebook, listing and viewing data > should be part of analysis. > > Comments on these aspects and the announced development phase sequence > are welcomed on this list. > > > The next development phases are: a. Prevent double naming of fields > > on a dataform b. Develop first test release of a dedicated Entry > > Client. c. Add timed backup and date named zip file copy to Entry > > Client function. d. Add control of entry (mustenter, range, value > > labels) to Entry Client. e. Add multilanguage capability to dataform > > definition and entry client. > > regards > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > Message: 2 > Date: Thu, 1 Jul 2010 21:40:27 -0400 (EDT) > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Problem exporting data to SAS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <1871457764.860511278034827330.JavaMail.root(a)simcoe.cs.uoguelph.ca> > Content-Type: text/plain; charset="utf-8" > > Dear members, > > I am currently setting up my database and faced one problem that I can't > figure out. I entered some real data and exported to SAS. However, most > variables are coming as missing (.), but very few are coming with the > labels. I am thinking that it's something related to the checks on EpiData > and not a SAS problem. If anyone could help me I would appreciate. Following > attached is the .rec file. > > Thanks in advance, > > Rafael >

13 years, 10 months

Re: EpiData-list Digest, Vol 81, Issue 2

by epidata-list＠lists.umanitoba.ca

Hi Jens, Thank you for your hard work and message too. With regard to your suggestion below: " whereas other functions such as: codebook, listing and viewing data should be part of analysis". The codebook, listing, viewing were very helpful and in fact allowed me to convince a group of scientists to use EpiData Entry. It will be nice if one could use view data or codebook the data and so at both data entry and data analysis stages (as in EpiData Entry) using the new EpiData Manager. This could be useful for someone who want to see what data are entered and how the labels are displayed. Some experienced users of Stata/SAS may prefer to use EpiData Manager for data entry and even to codebook, view and list data prior taking it to Stata or other package. I think your suggestion will work well for someone who will use EpiData Manager for further analysis. It will be nice to be able to codebook, view and list data and values at the data entry stage as well as analysis. Hoping not to be too demanding. Kind regards Tieble London, UK On 2 July 2010 02:52, <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: new test release of EpiData Manager available (paste text > as fields and read qes) (epidata-list(a)lists.umanitoba.ca) > 2. Problem exporting data to SAS (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 01 Jul 2010 21:34:27 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] new test release of EpiData Manager > available (paste text as fields and read qes) > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <4C2CEDC3.6010808(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I am quite sure everyone can understand the amount of work involved in > the current rewriting and the need to focus and set the scope for > development at a realistic level. > > One of the aspects that I currently consider not needed is the > development of an editor. > Power users will each have their own preference for an editor and for > the EpiData Manager we can optimise usage of the clipboard instead of > developing a new editor. > > Another issue is the need for documentation tools. My current > understanding is that we do need: > - double entry verification (comparing two files and showing differences) > - count by id function (show a list of how many times a given id is > contained in a number of files) > - data verification according to controls built into a given data file. > e.g. whether all mustenter, range and value label definitions are met > - verification of keys (unique) and listing of observations not meeting > the defined key > > And I also think these should be part of the Manager, whereas other > functions such as: > codebook, listing and viewing data > should be part of analysis. > > Comments on these aspects and the announced development phase sequence > are welcomed on this list. > > > The next development phases are: a. Prevent double naming of fields > > on a dataform b. Develop first test release of a dedicated Entry > > Client. c. Add timed backup and date named zip file copy to Entry > > Client function. d. Add control of entry (mustenter, range, value > > labels) to Entry Client. e. Add multilanguage capability to dataform > > definition and entry client. > > regards > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > Message: 2 > Date: Thu, 1 Jul 2010 21:40:27 -0400 (EDT) > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Problem exporting data to SAS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > <1871457764.860511278034827330.JavaMail.root(a)simcoe.cs.uoguelph.ca> > Content-Type: text/plain; charset="utf-8" > > Dear members, > > I am currently setting up my database and faced one problem that I can't > figure out. I entered some real data and exported to SAS. However, most > variables are coming as missing (.), but very few are coming with the > labels. I am thinking that it's something related to the checks on EpiData > and not a SAS problem. If anyone could help me I would appreciate. Following > attached is the .rec file. > > Thanks in advance, > > Rafael >

13 years, 10 months

Long questionnaire

by epidata-list＠lists.umanitoba.ca

Dear members, I had a problem when make a new data entry form for a questionnaire which is very long (more than 80 pages), so 1 data entry form not enough for me because one data entry form have only 999 lines. So devided my form into 6 parts and I use the related command to links each part together, but I do not know the effective and the way to manage this issue, please help me. Thanks in advance, Best, Linh -- ================================== Nguyen Thi Linh Institute of Social and Medical Studies No 17, Residence of Cau Giay District Health Center. Alley 1, Nguyen Thi Dinh Street-Cau Giay-Ha Noi Phone: 84-4-35558288 ext. 105 Fax: 84-4-35558274 Website: www.isms.org.vn www.newcare.com.vn

13 years, 10 months

new test release of EpiData Manager available (paste text as fields and read qes)

by epidata-list＠lists.umanitoba.ca

Dear All Next test release of the EpiData Manager is now ready for testing. Added functionality is: 1. load datafiels and structure to a dataform. 2. open qes files as dataform files 3. write settings to an ini file 4. paste text from clipboard to a dataform as fields (or qes) Please discuss function in general on this list and report reproducible errors to the flyspray database The next development phases are: a. Prevent double naming of fields on a dataform b. Develop first test release of a dedicated Entry Client. c. Add timed backup and date named zip file copy to Entry Client function. d. Add control of entry (mustenter, range, value labels) to Entry Client. e. Add multilanguage capability to dataform definition and entry client. See http://www.epidata.dk/testing.php for the operating systems Linux, Mac and Windows. An updated introduction document has been placed on the testing page. ---------------------------------------------------------------------- When you first start the application you will see two sections, which can be moved, edited and deleted. these contain further definitions and guidance. Torsten Christiansen and Jens Lauritsen EpiData Association

13 years, 10 months

Problem exporting data to SAS

by epidata-list＠lists.umanitoba.ca

Dear members, I am currently setting up my database and faced one problem that I can't figure out. I entered some real data and exported to SAS. However, most variables are coming as missing (.), but very few are coming with the labels. I am thinking that it's something related to the checks on EpiData and not a SAS problem. If anyone could help me I would appreciate. Following attached is the .rec file. Thanks in advance, Rafael

13 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list July 2010