Hi,
is it possible to configure ODK collect so if an option is not
available among the autocomplete list, it still accepts it as a valid
entry?
From what I have seen in New Widgets demo and the country list, it
isn't so. Any option for
so that would be allowed?
Cheers
Rok
Hi Rok,
I think this should be the default behavior, but you're correct that it is
not. What should happen is that an autocomplete should let you type in
anything, and if you want to only allow items in that list you should make a
constraint statement that checks for those answers.
The behavior right now is that it lets the user go forward, pops a toast
that says, "answer not recorded", which is easily missed, and no answer is
recorded. This doesn't conform well to the user's mental model.
I've filed a bug here to be fixed before the release:
http://code.google.com/p/opendatakit/issues/detail?id=289
-Carl
···
On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
Hi,
is it possible to configure ODK collect so if an option is not
available among the autocomplete list, it still accepts it as a valid
entry?
From what I have seen in New Widgets demo and the country list, it
isn't so. Any option for
so that would be allowed?
Cheers
Rok
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Hi Carl, thanks a lot for the clarification! So what setting should
exactly go into the Constraint box in order to enable strict
validation? I see it's a simple input box in ODK Build...
···
On Aug 4, 10:57 am, Carl Hartung wrote:
> Hi Rok,
>
> I think this should be the default behavior, but you're correct that it is
> not. What should happen is that an autocomplete should let you type in
> anything, and if you want to only allow items in that list you should make a
> constraint statement that checks for those answers.
>
> The behavior right now is that it lets the user go forward, pops a toast
> that says, "answer not recorded", which is easily missed, and no answer is
> recorded. This doesn't conform well to the user's mental model.
>
> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>
> -Carl
>
>
>
>
>
>
>
> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
> > Hi,
>
> > is it possible to configure ODK collect so if an option is not
> > available among the autocomplete list, it still accepts it as a valid
> > entry?
>
> > From what I have seen in New Widgets demo and the country list, it
> > isn't so. Any option for
> >
> > so that would be allowed?
>
> > Cheers
> > Rok
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en
can you offer more details on exactly what you want to constrain? or
examples of what data you think would be valid and what would be
invalid?
···
On Thu, Aug 4, 2011 at 10:14, rok wrote:
> Hi Carl, thanks a lot for the clarification! So what setting should
> exactly go into the Constraint box in order to enable strict
> validation? I see it's a simple input box in ODK Build...
>
> On Aug 4, 10:57 am, Carl Hartung wrote:
>> Hi Rok,
>>
>> I think this should be the default behavior, but you're correct that it is
>> not. What should happen is that an autocomplete should let you type in
>> anything, and if you want to only allow items in that list you should make a
>> constraint statement that checks for those answers.
>>
>> The behavior right now is that it lets the user go forward, pops a toast
>> that says, "answer not recorded", which is easily missed, and no answer is
>> recorded. This doesn't conform well to the user's mental model.
>>
>> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>>
>> -Carl
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
>> > Hi,
>>
>> > is it possible to configure ODK collect so if an option is not
>> > available among the autocomplete list, it still accepts it as a valid
>> > entry?
>>
>> > From what I have seen in New Widgets demo and the country list, it
>> > isn't so. Any option for
>> >
>> > so that would be allowed?
>>
>> > Cheers
>> > Rok
>>
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Hi Yaw, I was just referring to Carl's explanation:
"..., and if you want to only allow items in that list you should make
a
constraint statement that checks for those answers..."
so wondering about that. If I understand correctly, the current
default behaviour of the autocomplete widget only allows entering
items from the list and my tests showed that if anything else is
entered, it is automatically erased on swipe to next screen with a
tiny message (sth. like "answer not recorded").
The other behaviour would be to allow the user to enter anything, but
at the same time offering autocompletion for items that fit the
entered string.
Rok
···
On Aug 4, 7:51 pm, Yaw Anokwa wrote:
> can you offer more details on exactly what you want to constrain? or
> examples of what data you think would be valid and what would be
> invalid?
>
>
>
>
>
>
>
> On Thu, Aug 4, 2011 at 10:14, rok wrote:
> > Hi Carl, thanks a lot for the clarification! So what setting should
> > exactly go into the Constraint box in order to enable strict
> > validation? I see it's a simple input box in ODK Build...
>
> > On Aug 4, 10:57 am, Carl Hartung wrote:
> >> Hi Rok,
>
> >> I think this should be the default behavior, but you're correct that it is
> >> not. What should happen is that an autocomplete should let you type in
> >> anything, and if you want to only allow items in that list you should make a
> >> constraint statement that checks for those answers.
>
> >> The behavior right now is that it lets the user go forward, pops a toast
> >> that says, "answer not recorded", which is easily missed, and no answer is
> >> recorded. This doesn't conform well to the user's mental model.
>
> >> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>
> >> -Carl
>
> >> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
> >> > Hi,
>
> >> > is it possible to configure ODK collect so if an option is not
> >> > available among the autocomplete list, it still accepts it as a valid
> >> > entry?
>
> >> > From what I have seen in New Widgets demo and the country list, it
> >> > isn't so. Any option for
> >> >
> >> > so that would be allowed?
>
> >> > Cheers
> >> > Rok
>
> >> > --
> >> > Post: opendatakit@googlegroups.com
> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en
ok. i think the bottom line is that we need to fix widget to behave
more sensibly (as described at
http://code.google.com/p/opendatakit/issues/detail?id=289). and then
allow people to specify if they want it to accept values not in the
list. until that is fixed in collect, there isn't anything you can do
in build to get around it. hope that helps!
···
On Thu, Aug 4, 2011 at 11:08, rok wrote:
> Hi Yaw, I was just referring to Carl's explanation:
> "..., and if you want to only allow items in that list you should make
> a
> constraint statement that checks for those answers..."
>
> so wondering about that. If I understand correctly, the current
> default behaviour of the autocomplete widget only allows entering
> items from the list and my tests showed that if anything else is
> entered, it is automatically erased on swipe to next screen with a
> tiny message (sth. like "answer not recorded").
>
> The other behaviour would be to allow the user to enter anything, but
> at the same time offering autocompletion for items that fit the
> entered string.
>
> Rok
>
>
> On Aug 4, 7:51 pm, Yaw Anokwa wrote:
>> can you offer more details on exactly what you want to constrain? or
>> examples of what data you think would be valid and what would be
>> invalid?
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Aug 4, 2011 at 10:14, rok wrote:
>> > Hi Carl, thanks a lot for the clarification! So what setting should
>> > exactly go into the Constraint box in order to enable strict
>> > validation? I see it's a simple input box in ODK Build...
>>
>> > On Aug 4, 10:57 am, Carl Hartung wrote:
>> >> Hi Rok,
>>
>> >> I think this should be the default behavior, but you're correct that it is
>> >> not. What should happen is that an autocomplete should let you type in
>> >> anything, and if you want to only allow items in that list you should make a
>> >> constraint statement that checks for those answers.
>>
>> >> The behavior right now is that it lets the user go forward, pops a toast
>> >> that says, "answer not recorded", which is easily missed, and no answer is
>> >> recorded. This doesn't conform well to the user's mental model.
>>
>> >> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>>
>> >> -Carl
>>
>> >> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
>> >> > Hi,
>>
>> >> > is it possible to configure ODK collect so if an option is not
>> >> > available among the autocomplete list, it still accepts it as a valid
>> >> > entry?
>>
>> >> > From what I have seen in New Widgets demo and the country list, it
>> >> > isn't so. Any option for
>> >> >
>> >> > so that would be allowed?
>>
>> >> > Cheers
>> >> > Rok
>>
>> >> > --
>> >> > Post: opendatakit@googlegroups.com
>> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>>
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Understood. That brings me to the next question.
If I wanted to submit a patch for this particular fix, what is the
process?
And second, I am also interested in developing the autocomplete widget
further to support barcode scanner entry of items. Would that be best
done through a clone? is there a particular "channel" through which
such requests are made?
Cheers
Rok
···
On Aug 4, 8:13 pm, Yaw Anokwa wrote:
> ok. i think the bottom line is that we need to fix widget to behave
> more sensibly (as described athttp://code.google.com/p/opendatakit/issues/detail?id=289). and then
> allow people to specify if they want it to accept values not in the
> list. until that is fixed in collect, there isn't anything you can do
> in build to get around it. hope that helps!
>
>
>
>
>
>
>
> On Thu, Aug 4, 2011 at 11:08, rok wrote:
> > Hi Yaw, I was just referring to Carl's explanation:
> > "..., and if you want to only allow items in that list you should make
> > a
> > constraint statement that checks for those answers..."
>
> > so wondering about that. If I understand correctly, the current
> > default behaviour of the autocomplete widget only allows entering
> > items from the list and my tests showed that if anything else is
> > entered, it is automatically erased on swipe to next screen with a
> > tiny message (sth. like "answer not recorded").
>
> > The other behaviour would be to allow the user to enter anything, but
> > at the same time offering autocompletion for items that fit the
> > entered string.
>
> > Rok
>
> > On Aug 4, 7:51 pm, Yaw Anokwa wrote:
> >> can you offer more details on exactly what you want to constrain? or
> >> examples of what data you think would be valid and what would be
> >> invalid?
>
> >> On Thu, Aug 4, 2011 at 10:14, rok wrote:
> >> > Hi Carl, thanks a lot for the clarification! So what setting should
> >> > exactly go into the Constraint box in order to enable strict
> >> > validation? I see it's a simple input box in ODK Build...
>
> >> > On Aug 4, 10:57 am, Carl Hartung wrote:
> >> >> Hi Rok,
>
> >> >> I think this should be the default behavior, but you're correct that it is
> >> >> not. What should happen is that an autocomplete should let you type in
> >> >> anything, and if you want to only allow items in that list you should make a
> >> >> constraint statement that checks for those answers.
>
> >> >> The behavior right now is that it lets the user go forward, pops a toast
> >> >> that says, "answer not recorded", which is easily missed, and no answer is
> >> >> recorded. This doesn't conform well to the user's mental model.
>
> >> >> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>
> >> >> -Carl
>
> >> >> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
> >> >> > Hi,
>
> >> >> > is it possible to configure ODK collect so if an option is not
> >> >> > available among the autocomplete list, it still accepts it as a valid
> >> >> > entry?
>
> >> >> > From what I have seen in New Widgets demo and the country list, it
> >> >> > isn't so. Any option for
> >> >> >
> >> >> > so that would be allowed?
>
> >> >> > Cheers
> >> >> > Rok
>
> >> >> > --
> >> >> > Post: opendatakit@googlegroups.com
> >> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> >> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> >> > --
> >> > Post: opendatakit@googlegroups.com
> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en
the easiest thing to do is to make a server side clone and patch
things there. then file an issue where you ask for code review and we
can pull the diff as needed. if it's a small patch, then no real need
to make a server side clone -- just attach the patch to an issue in
the issue tracker.
as far as requests, you can file a feature request, but there is no
guarantee that we'll implement it. generally, the more people ask for
the feature, the more likely it is we'll add it as we get spare
cycles.
···
On Thu, Aug 4, 2011 at 11:31, rok wrote:
> Understood. That brings me to the next question.
> If I wanted to submit a patch for this particular fix, what is the
> process?
>
> And second, I am also interested in developing the autocomplete widget
> further to support barcode scanner entry of items. Would that be best
> done through a clone? is there a particular "channel" through which
> such requests are made?
>
> Cheers
> Rok
>
> On Aug 4, 8:13 pm, Yaw Anokwa wrote:
>> ok. i think the bottom line is that we need to fix widget to behave
>> more sensibly (as described athttp://code.google.com/p/opendatakit/issues/detail?id=289). and then
>> allow people to specify if they want it to accept values not in the
>> list. until that is fixed in collect, there isn't anything you can do
>> in build to get around it. hope that helps!
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Aug 4, 2011 at 11:08, rok wrote:
>> > Hi Yaw, I was just referring to Carl's explanation:
>> > "..., and if you want to only allow items in that list you should make
>> > a
>> > constraint statement that checks for those answers..."
>>
>> > so wondering about that. If I understand correctly, the current
>> > default behaviour of the autocomplete widget only allows entering
>> > items from the list and my tests showed that if anything else is
>> > entered, it is automatically erased on swipe to next screen with a
>> > tiny message (sth. like "answer not recorded").
>>
>> > The other behaviour would be to allow the user to enter anything, but
>> > at the same time offering autocompletion for items that fit the
>> > entered string.
>>
>> > Rok
>>
>> > On Aug 4, 7:51 pm, Yaw Anokwa wrote:
>> >> can you offer more details on exactly what you want to constrain? or
>> >> examples of what data you think would be valid and what would be
>> >> invalid?
>>
>> >> On Thu, Aug 4, 2011 at 10:14, rok wrote:
>> >> > Hi Carl, thanks a lot for the clarification! So what setting should
>> >> > exactly go into the Constraint box in order to enable strict
>> >> > validation? I see it's a simple input box in ODK Build...
>>
>> >> > On Aug 4, 10:57 am, Carl Hartung wrote:
>> >> >> Hi Rok,
>>
>> >> >> I think this should be the default behavior, but you're correct that it is
>> >> >> not. What should happen is that an autocomplete should let you type in
>> >> >> anything, and if you want to only allow items in that list you should make a
>> >> >> constraint statement that checks for those answers.
>>
>> >> >> The behavior right now is that it lets the user go forward, pops a toast
>> >> >> that says, "answer not recorded", which is easily missed, and no answer is
>> >> >> recorded. This doesn't conform well to the user's mental model.
>>
>> >> >> I've filed a bug here to be fixed before the release:http://code.google.com/p/opendatakit/issues/detail?id=289
>>
>> >> >> -Carl
>>
>> >> >> On Thu, Aug 4, 2011 at 1:33 PM, rok wrote:
>> >> >> > Hi,
>>
>> >> >> > is it possible to configure ODK collect so if an option is not
>> >> >> > available among the autocomplete list, it still accepts it as a valid
>> >> >> > entry?
>>
>> >> >> > From what I have seen in New Widgets demo and the country list, it
>> >> >> > isn't so. Any option for
>> >> >> >
>> >> >> > so that would be allowed?
>>
>> >> >> > Cheers
>> >> >> > Rok
>>
>> >> >> > --
>> >> >> > Post: opendatakit@googlegroups.com
>> >> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>>
>> >> > --
>> >> > Post: opendatakit@googlegroups.com
>> >> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >> > Options:http://groups.google.com/group/opendatakit?hl=en
>>
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>