- EpiData-list - University of Manitoba Mailing Lists

Changing Confidence Intervals on EpiData Analysis
by epidata-list＠lists.umanitoba.ca 29 Mar '07

29 Mar '07

Hi, I would like the stats I get when doing an epitable to to reflect a 90% CI, instead of the default 95%. Is it possible to do so, and if yes, how? Thanks! REgards Juanette John Natural Resources & the Environment - CSIR PO Box 395 Pretoria 0001 South Africa jjohn(a)csir.co.za Tel 27 12 841 4189 (mornings only) Cell 083 4100 444 Fax 27 12 841 4257/086 6180084 CSIR: "our future through Science" http://www.csir.co.za -- This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice. Views expressed herein do not necessarily represent the views of the CSIR. CSIR E-mail Legal Notice http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html CSIR Copyright, Terms and Conditions http://mail.csir.co.za/CSIR_Copyright.html For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice send a blank message with REQUEST LEGAL in the subject line to CallCentre(a)csir.co.za. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

Using Notes for long text fields
by epidata-list＠lists.umanitoba.ca 15 Mar '07

15 Mar '07

Hi Pedro, that's a good point. I'll try to figure that out. It seems to me that Epidata was not really developed for dealing with long text fields. Nevertheless, many questionnaires have such questions, e.g. a concluding question in which the respondent can comment on the contents of the questionnaire and this often leads to long and very interesting comments. It would ofcourse be nice if such and other long text answers could simply be processed with Epidatal. Maybe this will become more easy in a future release? Who knows. Bye and thanks, Ben.

1 1

long text fields
by epidata-list＠lists.umanitoba.ca 15 Mar '07

15 Mar '07

Hi Jamie, thanks a lot , I going to try that Notes screen, Ben.

1 0

Long texts in EpiData Entry
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Regarding Jamie 2nd option (see below), one thing we have to be aware is the problem of file size that the Epidat Editor can manage. If i am not wrong there is a limitation on that side. So check if that limitations is going to be a problem when entering your comments. > 2) Capture the text using the data notes capability. Just hit <F5> when > in a field and EpiData opens the Notes screen. You can type all you want > in here. EpiData puts in the record number, field name and current > field contents, so you may want to add to a BEFORE ENTRY block for this > field: > > BEFORE ENTRY > WRITENOTE "Notes for patient @patidnum, visit number @visitnum" > END > > This a very powerful feature of EpiData that is missing from most other > software. > You don't have any means of manipulating the data, but they are captured > and can be reviewed and edited in any text/word processor. > > Jamie Pedro Arias

1 0

Mapulation dates & Hour
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Thank you Charity I know this command and I have already used it when I even I drove the management of data since the beginning. But we are in front of this problem when someone give you this kind of data base. Then I would especially like to draw the attention of the designers of software so that this module can be introduced. Thank all ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 0

long text fields
by epidata-list＠lists.umanitoba.ca 14 Mar '07

14 Mar '07

Hi all, Is there a nice way in Epidata to deal with long text fields of 300 positions? I'm working with a questionnaire with open-end questions. The answers are not longer than about 300 characters. The qes files now has four text fields, each covering 80 positions which is the maximum. Though this works, it is e.g. not easy to make corrections in the text, since the four fields are handled separately by Epidata; inserting a word that I forgot to enter in the first field implies that all remaining fields have to be adjusted as well, since the text does not scroll over all five fields at the same time. Also, instead of showing 80 positions, only 64 are visible at a time, in each field. Does anyone have an idea or tip what I could do, staying with Epidata that is. (Of course, I could also type the text in notepad or whatever, but it's much nicer to keep all data together.) Thanks for any advice, Ben.

1 1

Manipulation of Date and hour
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

I would like to know how to manipulate dates and hours at the same time. I have a data base which I seized under Epidata Entry and who understand variables dates and the hour of entrance for the delivery and date and the hour for the delivery. The hour I made two numeric variables, the hour and minutes. Now how to make to have the difference in the hour or in minutes? The problem does not settlewhen the delivery with place the same day. But the problem when there is gap For example: DAR Date of arrival <10/01/2007> HAR Arrival time 13 MAR Minute of arrival 45 DAC Dates delivery <12/01/2007> HAC Hour of delivery 02 MAC Minutes of delivery 34 Under SPSS, the manipulation is easy, I would like to know if under Epidata Analysis we can do the same with these temporal data. Should the opposite occur it would be necessary to think of introducing this module into the final version of this magnificent software. ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 13 Mars 2007, 18h10mn 43s Objet : EpiData-list Digest, Vol 41, Issue 7 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. deleted and excluded records (epidata-list(a)lists.umanitoba.ca) 2. Re: deleted and excluded records (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Mar 2007 08:16:27 +0100 (CET) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] deleted and excluded records To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <52289.130.226.78.129.1173770187.squirrel(a)webmail.webhosting.dk> Content-Type: text/plain; charset=iso-8859-1 Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen ------------------------------ Message: 2 Date: Tue, 13 Mar 2007 09:43:23 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] deleted and excluded records To: epidata-list(a)lists.umanitoba.ca Message-ID: <44e66f9b0703130043t1911363ev728eaea2e245ef85(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Thanks for the quick response to my email. I would just like to clarify my suggestion re "excluded" and "deleted" records. The issue is not about whether one can control reading deleted records or not (as Jens' response implies). My point was that if one is not aware that records have been deleted, it would be more informative on reading the dataset in Analysis if the message specifically states that x records have been deleted (and are therefore excluded). Using the word "excluded" suggests that Analysis has a problem with some values and therefore has excluded the records. One could spend quite some time trying to identify the problem before realising that these are merely records that have been deleted. On the point of deleted records, is there some way in Analysis of identifying records which had been deleted (but which one has chosen to include in the analysis). In EpiInfo, there was a system variable RECDELETED. Also, in browse/update mode, deleted records were identifiable by an asterisk. This was very useful in trying to sort out why records had been deleted. Thanks again, Annemieke van Middelkoop ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 7 ******************************************* ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 1

Manipulation of Date end hour
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

I would like to know how to treat(manipulate) dates and hours at the same time. I have a data base which I seized under Epidata Entry and who understand variables dates and the hour of entrance for the delivery and date and the hour for the delivery. The hour I made two numeric variables, the hour and minutes. Now how to make to have the difference in the hour or in minutes? The problem does not settlewhen the delivery with place the same day. But the problem when there is gap For example: DAR Date of arrival <10/01/2007> HAR Arrival time 13 MAR Minute of arrival 45 DAC Dates delivery <12/01/2007> HAC Hour of delivery 02 MAC Minutes of delivery 34 Under SPSS, the manipulation is easy, I would like to know if under Epidata Analysis we can do the same with these temporal data. Should the opposite occur it would be necessary to think of introducing this module into the final version of this magnificent software. ___________________________________________ Dr Jean-Paul DIBY-KONAN Médecin Santé Publique MCM Santé de la Reproduction Institut Médecine Tropicale Kapucinessenstraat 8 B-2000 Anvers Belgique ----- Message d'origine ---- De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> À : epidata-list(a)lists.umanitoba.ca Envoyé le : Mardi, 13 Mars 2007, 18h10mn 43s Objet : EpiData-list Digest, Vol 41, Issue 7 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. deleted and excluded records (epidata-list(a)lists.umanitoba.ca) 2. Re: deleted and excluded records (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Tue, 13 Mar 2007 08:16:27 +0100 (CET) From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] deleted and excluded records To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <52289.130.226.78.129.1173770187.squirrel(a)webmail.webhosting.dk> Content-Type: text/plain; charset=iso-8859-1 Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen ------------------------------ Message: 2 Date: Tue, 13 Mar 2007 09:43:23 +0200 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] deleted and excluded records To: epidata-list(a)lists.umanitoba.ca Message-ID: <44e66f9b0703130043t1911363ev728eaea2e245ef85(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Thanks for the quick response to my email. I would just like to clarify my suggestion re "excluded" and "deleted" records. The issue is not about whether one can control reading deleted records or not (as Jens' response implies). My point was that if one is not aware that records have been deleted, it would be more informative on reading the dataset in Analysis if the message specifically states that x records have been deleted (and are therefore excluded). Using the word "excluded" suggests that Analysis has a problem with some values and therefore has excluded the records. One could spend quite some time trying to identify the problem before realising that these are merely records that have been deleted. On the point of deleted records, is there some way in Analysis of identifying records which had been deleted (but which one has chosen to include in the analysis). In EpiInfo, there was a system variable RECDELETED. Also, in browse/update mode, deleted records were identifiable by an asterisk. This was very useful in trying to sort out why records had been deleted. Thanks again, Annemieke van Middelkoop ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 41, Issue 7 ******************************************* ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

1 1

deleted and excluded records and dates
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

Hi all, Interesting disccussion here. > 2. The suggestion: > "SUGGESTION: Would it not be possible for Analysis to assign a standard > valid value (e.g. 01/01/1900) to any invalid dates it comes across > during the read process. " > > Will be used in the next build of analysis, since it is very easy to > implement. Obviously with a message to the user. I think this can be > done in 5 minutes of work time in the programming, whereas the optimal > solution of showing variable/field name and record is a large job - > could be 1-2 days of work, since the function controlling the date value > is not knowing neither the name of the field nor the record. But I will > add the issue to the work plan for a solution at some point. In my view the problem with that solution is that if Analysis automatically changes all "invalid" dates to any standard missing value, it can be a problem if the user saves the changes in a new data file and deletes the old one. The message for the users should be VERY CLEAR. > I would just like to clarify my suggestion re "excluded" and "deleted" > records. The issue is not about whether one can control reading > deleted records or not (as Jens' response implies). My point was that > if one is not aware that records have been deleted, it would be more > informative on reading the dataset in Analysis if the message > specifically states that x records have been deleted (and are > therefore excluded). Using the word "excluded" suggests that Analysis > has a problem with some values and therefore has excluded the records. > One could spend quite some time trying to identify the problem before > realising that these are merely records that have been deleted. Maybe we can use a text similar to the one used by EpiInfo for Windows: "#### records loaded (deleted records excluded/included)" Still it makes no senese to display 100 times the same message saying that a record was excluded because of an invalide date if the user can not do anything. In my view one solution can be display, in adition to the previous message, another message saying: "#### records excluded because of quality checking with dates(or other reasons). TIP: sort ascending your data in any date variable and browse them to detect the problems" Pedro Arias

1 0

deleted and excluded records
by epidata-list＠lists.umanitoba.ca 13 Mar '07

13 Mar '07

Continued discussion on this topic: The suggested solution I gave could be clarified: 1. Dates before year approx. 1700-1800 give problems in Analysis now, but obviously should not. Although as everyone probably know there is a shift around 15xx (I do not remember the exact year). 2. The suggestion: "SUGGESTION: Would it not be possible for Analysis to assign a standard valid value (e.g. 01/01/1900) to any invalid dates it comes across during the read process. " Will be used in the next build of analysis, since it is very easy to implement. Obviously with a message to the user. I think this can be done in 5 minutes of work time in the programming, whereas the optimal solution of showing variable/field name and record is a large job - could be 1-2 days of work, since the function controlling the date value is not knowing neither the name of the field nor the record. But I will add the issue to the work plan for a solution at some point. Regarding the "excluded" versus "deleted" is also easy. The user can control whether records deleted are read or not by: set read deleted=on set read deleted=off The change works only when reading the file, so if you change re-read the file again. e.g. set read deleted = off read myfile describe age set read deleted = on read myfile /close describe age // here records marked for deletion are included. off is default. There is an error in v1 b68 in relation to this setting, such that if you read the file with "set read deleted=off" and then do an "update", you will see the records marked for deletion. The error has been found and a solution will be shown in next test release. regards Jens Lauritsen

1 1