I would like to make date field mandatory on one of my ODK forms, expected
date could be the present date or a date from the past. Now the problem is
if the user does not make any changes to the date picker, still it picks
the current date. How do I ensure that, user paid attention to the date
picker, the current date doesn't mean that the user forgot to enter a date
value? There are some alternative ways; however, input should be date
value, not text or integer.
I believe there must be some solution, I know I can use a constraint for
past dates, but there is no way to ensure that current date doesn't mean
that it is a mistake of the data collector.
What I commonly do is to ask if they know they date before showing the
date question. You can also add a select one question after the date
question which is relevant if the selected date matches today. In that
question, I ask the user to confirm yes/no if they actually wanted to
select today's date.
Other approaches I've seen is break up the date into day, month, year
and use numbers/selects. Or set the default column in XLSForm to
something unreasonable (e.g., 1900-01-01) and require the user change
that date.
Yaw
···
On Sun, Jan 29, 2017 at 1:14 PM, A.N.M AL-IMRAN wrote:
> Dear Friends,
>
> I would like to make date field mandatory on one of my ODK forms, expected
> date could be the present date or a date from the past. Now the problem is
> if the user does not make any changes to the date picker, still it picks the
> current date. How do I ensure that, user paid attention to the date picker,
> the current date doesn't mean that the user forgot to enter a date value?
> There are some alternative ways; however, input should be date value, not
> text or integer.
>
> I believe there must be some solution, I know I can use a constraint for
> past dates, but there is no way to ensure that current date doesn't mean
> that it is a mistake of the data collector.
>
> Thanks,
> Imran
>
> --
> --
> 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.
Excellent! I found the 1st one more useful and I have applied it to my form.
Thanks once again,
Imran
A N M AL IMRAN (Imran)
Brossard, QC
Canada
Cell: +1 (438) 501 3576
···
On 3 February 2017 at 00:32, Yaw Anokwa wrote:
Hi Imran,
What I commonly do is to ask if they know they date before showing the
date question. You can also add a select one question after the date
question which is relevant if the selected date matches today. In that
question, I ask the user to confirm yes/no if they actually wanted to
select today's date.
Other approaches I've seen is break up the date into day, month, year
and use numbers/selects. Or set the default column in XLSForm to
something unreasonable (e.g., 1900-01-01) and require the user change
that date.
I would like to make date field mandatory on one of my ODK forms,
expected
date could be the present date or a date from the past. Now the problem
is
if the user does not make any changes to the date picker, still it picks
the
current date. How do I ensure that, user paid attention to the date
picker,
the current date doesn't mean that the user forgot to enter a date value?
There are some alternative ways; however, input should be date value, not
text or integer.
I believe there must be some solution, I know I can use a constraint for
past dates, but there is no way to ensure that current date doesn't mean
that it is a mistake of the data collector.