Will there be some advanced skip and fill routines in future versions of epidatamanager.
For instance I work currently on a household survey where I ask about livestock.
V16a Number of cattle
V16b Number of goats
V16c Number of sheep
Etc.
V17a Number of productive female cattle
V17b Number of productive female goats
V17c Number of productive female sheep
Etc.
V18a Value of cattle
V18b Value of goats
V18c Value of sheep
Suppose V16a equals "0" or is "SYSMIS" V17a and V18a should be system missing.
I could not find it in the current version.
Regards,
Aiso
Aisa asked on skip and fill. With the current version you can do what you like by changing the sequence to:
V16a Number of cattle
(then set jumping to v17 if v16a is = 0) v16b Number of productive female cattle
v17a Number of goats
V17b Number of productive female goats
..... etc.
Regards Jens Lauritsen
On 05/28/2012 05:05 AM, epidata-list@lists.umanitoba.ca wrote:
Will there be some advanced skip and fill routines in future versions of epidatamanager.
V16a Number of cattle
V16b Number of goats
V16c Number of sheep
Etc.
V17a Number of productive female cattle
V17b Number of productive female goats
V17c Number of productive female sheep
Etc.
V18a Value of cattle
V18b Value of goats
V18c Value of sheep
Suppose V16a equals "0" or is "SYSMIS" V17a and V18a should be system missing.
I could not find it in the current version.
Regards,
Aiso
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Dear Jens,
Thank you for your reply. I asked this question since in days long gone (late eighties), this option was possible in SPSS/Data Entry for DOS.
Of course it depends on the design philosophy of a questionnaire. Mine is that the questionnaire is central and that the data entry should follow the questionnaire. Your philosophy is that the data entry is the crucial aspect and that the design of the questionnaire should follow the data entry form.
But perhaps you can think of introducing these options in future versions.
Regards,
Aiso
-----Oorspronkelijk bericht----- Van: epidata-list@lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Verzonden: dinsdag 29 mei 2012 20:16 Aan: epidata-list@lists.umanitoba.ca Onderwerp: Re: [EpiData-list] Skip and fill
Aisa asked on skip and fill. With the current version you can do what you like by changing the sequence to:
V16a Number of cattle
(then set jumping to v17 if v16a is = 0) v16b Number of productive female cattle
v17a Number of goats
V17b Number of productive female goats
..... etc.
Regards Jens Lauritsen
On 05/28/2012 05:05 AM, epidata-list@lists.umanitoba.ca wrote:
Will there be some advanced skip and fill routines in future versions of epidatamanager.
V16a Number of cattle
V16b Number of goats
V16c Number of sheep
Etc.
V17a Number of productive female cattle
V17b Number of productive female goats
V17c Number of productive female sheep
Etc.
V18a Value of cattle
V18b Value of goats
V18c Value of sheep
Suppose V16a equals "0" or is "SYSMIS" V17a and V18a should be system missing.
I could not find it in the current version.
Regards,
Aiso
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Dear Aiso,
I haven't familiarised myself with the latest version of EpiData Manager yet, but may have a solution to your problem using EpiData Entry (see attached database). In the CHK file you'll see that I hide and unhide the v17 and v18 fields depending on the value entered into the v16 fields. By hiding a field you are effectively skipping it during the entry process and the order in which the fields appear is irrelevant - provided hidden fields are after the "controlling" field. In my example I've used -1 as the code for missing. When I set up databases I use a value (such as -1) that is not a legitimate value for any of my fields. In Stata I then convert -1 to a Stata missing value.
v16a AFTER ENTRY IF v16a=0 THEN LET v17a=-1 LET v18a=-1 HIDE v17a HIDE v18a ENDIF IF v16a<>0 THEN LET v17a=. LET v18a=. UNHIDE v17a UNHIDE v18a ENDIF END END
Cheers,
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@mcri.edu.au www.mcri.edu.au
-----Original Message----- From: epidata-list-bounces@lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list@lists.umanitoba.ca Sent: Wednesday, 30 May 2012 12:55 PM To: epidata-list@lists.umanitoba.ca Subject: RE: [EpiData-list] Skip and fill
Dear Jens,
Thank you for your reply. I asked this question since in days long gone (late eighties), this option was possible in SPSS/Data Entry for DOS.
Of course it depends on the design philosophy of a questionnaire. Mine is that the questionnaire is central and that the data entry should follow the questionnaire. Your philosophy is that the data entry is the crucial aspect and that the design of the questionnaire should follow the data entry form.
But perhaps you can think of introducing these options in future versions.
Regards,
Aiso
-----Oorspronkelijk bericht----- Van: epidata-list@lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Verzonden: dinsdag 29 mei 2012 20:16 Aan: epidata-list@lists.umanitoba.ca Onderwerp: Re: [EpiData-list] Skip and fill
Aisa asked on skip and fill. With the current version you can do what you like by changing the sequence to:
V16a Number of cattle
(then set jumping to v17 if v16a is = 0) v16b Number of productive female cattle
v17a Number of goats
V17b Number of productive female goats
..... etc.
Regards Jens Lauritsen
On 05/28/2012 05:05 AM, epidata-list@lists.umanitoba.ca wrote:
Will there be some advanced skip and fill routines in future versions of epidatamanager.
V16a Number of cattle
V16b Number of goats
V16c Number of sheep
Etc.
V17a Number of productive female cattle
V17b Number of productive female goats
V17c Number of productive female sheep
Etc.
V18a Value of cattle
V18b Value of goats
V18c Value of sheep
Suppose V16a equals "0" or is "SYSMIS" V17a and V18a should be system missing.
I could not find it in the current version.
Regards,
Aiso
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
_______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com
If you have any question, please contact MCRI IT Helpdesk for further assistance. ______________________________________________________________________
______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
You also have to consider the price of the SPSS software.
We implement what is reasonable within the funding we have. For us just one copy of SPSS would be more than 1000 Euro or US dollars - unless you are in a University setting, where they set prices very low.
Anyone who can get some funding for development are welcome to do so, and we will do our best to implement such functionality.
regards
Jens Lauritsen
On 05/30/2012 04:55 AM, epidata-list@lists.umanitoba.ca wrote:
Dear Jens,
Thank you for your reply. I asked this question since in days long gone (late eighties), this option was possible in SPSS/Data Entry for DOS.
Of course it depends on the design philosophy of a questionnaire. Mine is that the questionnaire is central and that the data entry should follow the questionnaire. Your philosophy is that the data entry is the crucial aspect and that the design of the questionnaire should follow the data entry form.
But perhaps you can think of introducing these options in future versions.
Regards,
Aiso
Dear Jens,
Then again if you had opensourced your code there would not be such a discussion, because anyone who cared could implement the "skip and fill" functionality (or any functionality for that matter) and maybe contribute it back to epidata.
But obviously IMHO your business model is based on control (and one should respect that), so my point is moot...
Regards,
Theodore Lytras
2012/5/30 epidata-list@lists.umanitoba.ca:
You also have to consider the price of the SPSS software.
We implement what is reasonable within the funding we have. For us just one copy of SPSS would be more than 1000 Euro or US dollars - unless you are in a University setting, where they set prices very low.
Anyone who can get some funding for development are welcome to do so, and we will do our best to implement such functionality.
regards
Jens Lauritsen
On 05/30/2012 04:55 AM, epidata-list@lists.umanitoba.ca wrote:
Dear Jens,
Thank you for your reply. I asked this question since in days long gone (late eighties), this option was possible in SPSS/Data Entry for DOS.
Of course it depends on the design philosophy of a questionnaire. Mine is that the questionnaire is central and that the data entry should follow the questionnaire. Your philosophy is that the data entry is the crucial aspect and that the design of the questionnaire should follow the data entry form.
But perhaps you can think of introducing these options in future versions.
Regards,
Aiso
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Perhaps the list is not the place for an extended discussion of desired functionality, now that the request has been made. I would follow Jens' logic for this data because it seems to fit best with the way the questions should be asked. We readers don't have the full context of the questionnaire, however.
Since the creation of EpiData, a number of people like myself have encouraged, and occasionally found funding for, further development. I would like to think that I have had considerable influence on the development so far. The end goal is open source, but this is not practical until most of the design principles are established and coded. The volunteer effort required to maintain an open source model is far greater than is currently available for the work being done. But this will happen.
Jamie
On 2012-05-30, Theodore wrote:
Then again if you had opensourced your code there would not be such a discussion, because anyone who cared could implement the "skip and fill" functionality (or any functionality for that matter) and maybe contribute it back to epidata.
participants (1)
-
epidata-list@lists.umanitoba.ca