Does anyone know if for a single or multiple select question one can add different choices for example; So instead of just having the possibility of choosing from a value. The list would give the option to manually enter data, get a bar code, enter gps coordinate etc? Below is a sample question
Enter HouseHold number:
a. manually enter number
b. scan QR code
c. Enter gps
text
hh_number
Input household number.
numbers
selected(${select_hh_ident},‘c’})
choices
list_name name label
hh_ident
a
manually enter number
hh_ident
b
scan QR code
hh_ident
c
Enter gps
Is this what you meant?
/r
Nik
···
On Sunday, July 8, 2012, Nabil mansouri wrote:
Does anyone know if for a single or multiple select question one can add different choices for example; So instead of just having the possibility of choosing from a value. The list would give the option to manually enter data, get a bar code, enter gps coordinate etc? Below is a sample question
Enter HouseHold number:
a. manually enter number
b. scan QR code
c. Enter gps
-nabil
–
You received this message because you are subscribed to the Google Groups “Kobo Users” group.
In that case I would recommend you to collect time as shown in the post below where the enumerator will not know that the time is collected as the time should collect in the background. With this you could collect time either before the scan or after the scan (as per your wish).
There’s a trick you can use to capture a timestamp when you (first) answer any question, barcode or otherwise:
once(if(${barcode} != '', now(), ''))
Basically, once() is actually re-calculated continuously (!), but will only ever over-write its existing value if it is currently null. The if(...) condition inside captures the now() timestamp only when your barcode (or whatever result you are interested in) is non-null. Hence, the first time your result becomes non-null the timestamp is captured during the immediate recalc cycle, but then wont get overwritten again.
Caveat: this captures the first timestamp. So if the user re-scans the barcode it wont capture the new timestamp.