Hi,
[The first of several questions]
I need some help with scripting something in XLSForm. Is there a way to count the number of times a piece of information is entered incorrectly?
We are trying to see if double confirmation leads to lower error rates when entering data, specifically when entering immunization dates.
Q1. On what date did the child receive the Oral Polio Vaccine (OPV), dose 1?
Q2. Please confirm: on what date did the child receive the Oral Polio Vaccine (OPV), dose 1?
This data is captured using the "date" format.
Right now, I have a constraint where the date from Q2 must equal the date from Q1 or else the enumerator can't go on to the next question. I could hard code by assuming that the enumerator won't take more than 10 attempts to find a matching date (if Q2 doesn't equal Q1, then ask Q3. If Q3 doesn't equal Q1, then ask Q4, etc.).
Is there an easier way to do this using some type of repeat counter so that I can determine the number of attempts the enumerator makes before entering a matching date?
Cheers,
I suspect this is not possible to do in an XLSForm.
The ODK 2.0 tools have more flexibility and could do this sort of counting
but we have not thought about dynamically controlling whether or not a
field is modifiable. I think you could do that with some customization of
the javascript layers, but it isn't there out-of-the-box.
ยทยทยท
On Mon, Jul 20, 2015 at 5:04 AM, wrote:
Hi,
[The first of several questions]
I need some help with scripting something in XLSForm. Is there a way to
count the number of times a piece of information is entered incorrectly?
We are trying to see if double confirmation leads to lower error rates
when entering data, specifically when entering immunization dates.
Q1. On what date did the child receive the Oral Polio Vaccine (OPV), dose
1?
Q2. Please confirm: on what date did the child receive the Oral Polio
Vaccine (OPV), dose 1?
This data is captured using the "date" format.
Right now, I have a constraint where the date from Q2 must equal the date
from Q1 or else the enumerator can't go on to the next question. I could
hard code by assuming that the enumerator won't take more than 10 attempts
to find a matching date (if Q2 doesn't equal Q1, then ask Q3. If Q3 doesn't
equal Q1, then ask Q4, etc.).
Is there an easier way to do this using some type of repeat counter so
that I can determine the number of attempts the enumerator makes before
entering a matching date?
Cheers,
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com