But if we manage to add this on a version of the collect. We could send the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
···
2012/3/8 Yaw Anokwa
Yup. You have to modify Collect to do this.
On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
i dont know what you mean wen you say you could add. You are talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
2012/3/8 Mitch S mitchellsundt@gmail.com
If you want to detect and capture the explicit cancelling-out of a form,
you could add to the quit dialog actions (the one that displays when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments. It would
be
easiest to log these events to your own, separately maintained, logging
file, perhaps including a copy of the incomplete submission). You would
then
need to add your own operational processes to periodically gather this
information off the phones for analysis.
Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo <gaperazzo@gmail.com wrote:
In one metting i had been asked about an exit button (or option)
avaiable
on every question for the ennumerator be able to save the survey and
upload
it despite the survey wasnt finished.
So my bosses will have the posibility to analize the dropout rate.
i dont know how to do it minimizing the disruption to the output of
the
data.
Any ideas? Im sorry about my english?
Thanks as always.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
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
Collect is designed so that only finalized forms are added to the list
of sendable forms. That's just a user interface thing. You can very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed all
the validation and constraint rules the form designer included, so you
may get bad data. If you choose to go that route, it might make sense
to force all saves to be finalized. These finalized forms will still
be editable, but the finalization process will ensure they only have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can then
see where people stopped filling out the forms.
···
On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo wrote:
> But if we manage to add this on a version of the collect. We could send the
> unfinished forms to aggregate? So they can analize the data?
>
> Guillermo A. Perazzo
>
>
>
> 2012/3/8 Yaw Anokwa
>>
>> Yup. You have to modify Collect to do this.
>>
>> On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo wrote:
>> > i dont know what you mean wen you say you could add. You are talking
>> > about
>> > modifiing collect?
>> > In sorry
>> > Guillermo A. Perazzo
>> >
>> >
>> >
>> >
>> >
>> >
>> > 2012/3/8 Mitch S
>> >>
>> >> If you want to detect and capture the explicit cancelling-out of a
>> >> form,
>> >> you could add to the quit dialog actions (the one that displays when
>> >> you hit
>> >> the back button - "Save Changes / Ignore Changes" -- see
>> >> FormEntryActivity.createQuitDialog()) to track abandonments. It would
>> >> be
>> >> easiest to log these events to your own, separately maintained, logging
>> >> file, perhaps including a copy of the incomplete submission). You would
>> >> then
>> >> need to add your own operational processes to periodically gather this
>> >> information off the phones for analysis.
>> >>
>> >> Mitch
>> >>
>> >> On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo wrote:
>> >>>
>> >>> In one metting i had been asked about an exit button (or option)
>> >>> avaiable
>> >>> on every question for the ennumerator be able to save the survey and
>> >>> upload
>> >>> it despite the survey wasnt finished.
>> >>> So my bosses will have the posibility to analize the dropout rate.
>> >>> i dont know how to do it minimizing the disruption to the output of
>> >>> the
>> >>> data.
>> >>>
>> >>> Any ideas? Im sorry about my english?
>> >>> Thanks as always.
>> >>>
>> >>>
>> >>> --
>> >>> Post: opendatakit@googlegroups.com
>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Mitch Sundt
>> >> Software Engineer
>> >> University of Washington
>> >> mitchellsundt@gmail.com
>> >>
>> >> --
>> >> 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
Thanls for tthe answer Yaw. You think its posible to make some work
arround of this. Maybe by adding a choice option "abbandoned survey". Do
you think this is ppossible?
Thanks
Collect is designed so that only finalized forms are added to the list
of sendable forms. That's just a user interface thing. You can very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed all
the validation and constraint rules the form designer included, so you
may get bad data. If you choose to go that route, it might make sense
to force all saves to be finalized. These finalized forms will still
be editable, but the finalization process will ensure they only have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can then
see where people stopped filling out the forms.
But if we manage to add this on a version of the collect. We could send
the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
Yup. You have to modify Collect to do this.
i dont know what you mean wen you say you could add. You are talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
If you want to detect and capture the explicit cancelling-out of a
form,
you could add to the quit dialog actions (the one that displays when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments. It
would
be
easiest to log these events to your own, separately maintained,
logging
file, perhaps including a copy of the incomplete submission). You
would
then
need to add your own operational processes to periodically gather
this
···
El jueves 8 de marzo de 2012, Yaw Anokwa escribió:
> On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo wrote:
>> 2012/3/8 Yaw Anokwa
>>> On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo wrote:
>>> > 2012/3/8 Mitch S
>>> >> information off the phones for analysis.
>>> >>
>>> >> Mitch
>>> >>
>>> >> On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo wrote:
>>> >>>
>>> >>> In one metting i had been asked about an exit button (or option)
>>> >>> avaiable
>>> >>> on every question for the ennumerator be able to save the survey and
>>> >>> upload
>>> >>> it despite the survey wasnt finished.
>>> >>> So my bosses will have the posibility to analize the dropout rate.
>>> >>> i dont know how to do it minimizing the disruption to the output of
>>> >>> the
>>> >>> data.
>>> >>>
>>> >>> Any ideas? Im sorry about my english?
>>> >>> Thanks as always.
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Post: opendatakit@googlegroups.com
>>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Mitch Sundt
>>> >> Software Engineer
>>> >> University of Washington
>>> >> mitchellsundt@gmail.com
>>> >>
>>> >> --
>>> >> Post: opendatakit@googlegroups.com
>>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >
>>> >
>>> > --
>>> > Post: opendatakit@googlegroups.com
>>> > Unsubscribe: opendataki
--
Guillermo A. Perazzo
Im sorry i meant adding some logic in the form to do that like a choice
in a select one question.
···
El 08/03/2012 23:55, "Guillermo Perazzo" escribió:
Thanls for tthe answer Yaw. You think its posible to make some work
arround of this. Maybe by adding a choice option "abbandoned survey". Do
you think this is ppossible?
Thanks
El jueves 8 de marzo de 2012, Yaw Anokwa yanokwa@gmail.com escribió:
Collect is designed so that only finalized forms are added to the list
of sendable forms. That's just a user interface thing. You can very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed all
the validation and constraint rules the form designer included, so you
may get bad data. If you choose to go that route, it might make sense
to force all saves to be finalized. These finalized forms will still
be editable, but the finalization process will ensure they only have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can then
see where people stopped filling out the forms.
On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo gaperazzo@gmail.com wrote:
But if we manage to add this on a version of the collect. We could send
the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
2012/3/8 Yaw Anokwa yanokwa@gmail.com
Yup. You have to modify Collect to do this.
On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
i dont know what you mean wen you say you could add. You are talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
2012/3/8 Mitch S mitchellsundt@gmail.com
If you want to detect and capture the explicit cancelling-out of a
form,
you could add to the quit dialog actions (the one that displays when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments. It
would
be
easiest to log these events to your own, separately maintained,
logging
file, perhaps including a copy of the incomplete submission). You
would
then
need to add your own operational processes to periodically gather
this
information off the phones for analysis.
Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo gaperazzo@gmail.com wrote:
In one metting i had been asked about an exit button (or option)
avaiable
on every question for the ennumerator be able to save the survey
and
upload
it despite the survey wasnt finished.
So my bosses will have the posibility to analize the dropout rate.
i dont know how to do it minimizing the disruption to the output
of
the
data.
Any ideas? Im sorry about my english?
Thanks as always.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendataki
--
Guillermo A. Perazzo
Yes. You can add an "abandoned survey" option that users can select
and then only show the next prompt if abandoned survey is not
selected.
You can use this interaction to skip a bunch of prompts and go to the
end of the survey.
···
On Thu, Mar 8, 2012 at 19:39, Guillermo Perazzo wrote:
> Im sorry i meant adding some logic in the form to do that like a choice in
> a select one question.
>
> El 08/03/2012 23:55, "Guillermo Perazzo" escribió:
>
>> Thanls for tthe answer Yaw. You think its posible to make some work
>> arround of this. Maybe by adding a choice option "abbandoned survey". Do
>> you think this is ppossible?
>> Thanks
>>
>> El jueves 8 de marzo de 2012, Yaw Anokwa escribió:
>> > Collect is designed so that only finalized forms are added to the list
>> > of sendable forms. That's just a user interface thing. You can very
>> > easily modify the code base so that unfinished forms get sent.
>> >
>> > The caveat is that unfinished forms have not necessarily passed all
>> > the validation and constraint rules the form designer included, so you
>> > may get bad data. If you choose to go that route, it might make sense
>> > to force all saves to be finalized. These finalized forms will still
>> > be editable, but the finalization process will ensure they only have
>> > valid data.
>> >
>> > Once the finalized but unfinished forms are on Aggregate, you can then
>> > see where people stopped filling out the forms.
>> >
>> > On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo wrote:
>> >> But if we manage to add this on a version of the collect. We could send
>> >> the
>> >> unfinished forms to aggregate? So they can analize the data?
>> >>
>> >> Guillermo A. Perazzo
>> >>
>> >>
>> >>
>> >> 2012/3/8 Yaw Anokwa
>> >>>
>> >>> Yup. You have to modify Collect to do this.
>> >>>
>> >>> On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo wrote:
>> >>> > i dont know what you mean wen you say you could add. You are talking
>> >>> > about
>> >>> > modifiing collect?
>> >>> > In sorry
>> >>> > Guillermo A. Perazzo
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > 2012/3/8 Mitch S
>> >>> >>
>> >>> >> If you want to detect and capture the explicit cancelling-out of a
>> >>> >> form,
>> >>> >> you could add to the quit dialog actions (the one that displays
>> >>> >> when
>> >>> >> you hit
>> >>> >> the back button - "Save Changes / Ignore Changes" -- see
>> >>> >> FormEntryActivity.createQuitDialog()) to track abandonments. It
>> >>> >> would
>> >>> >> be
>> >>> >> easiest to log these events to your own, separately maintained,
>> >>> >> logging
>> >>> >> file, perhaps including a copy of the incomplete submission). You
>> >>> >> would
>> >>> >> then
>> >>> >> need to add your own operational processes to periodically gather
>> >>> >> this
>> >>> >> information off the phones for analysis.
>> >>> >>
>> >>> >> Mitch
>> >>> >>
>> >>> >> On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo wrote:
>> >>> >>>
>> >>> >>> In one metting i had been asked about an exit button (or option)
>> >>> >>> avaiable
>> >>> >>> on every question for the ennumerator be able to save the survey
>> >>> >>> and
>> >>> >>> upload
>> >>> >>> it despite the survey wasnt finished.
>> >>> >>> So my bosses will have the posibility to analize the dropout rate.
>> >>> >>> i dont know how to do it minimizing the disruption to the output
>> >>> >>> of
>> >>> >>> the
>> >>> >>> data.
>> >>> >>>
>> >>> >>> Any ideas? Im sorry about my english?
>> >>> >>> Thanks as always.
>> >>> >>>
>> >>> >>>
>> >>> >>> --
>> >>> >>> Post: opendatakit@googlegroups.com
>> >>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> Mitch Sundt
>> >>> >> Software Engineer
>> >>> >> University of Washington
>> >>> >> mitchellsundt@gmail.com
>> >>> >>
>> >>> >> --
>> >>> >> Post: opendatakit@googlegroups.com
>> >>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Post: opendatakit@googlegroups.com
>> >>> > Unsubscribe: opendataki
>>
>> --
>> Guillermo A. Perazzo
>>
>>
>>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
And yes, ODK Aggregate does not perform any data validation, it just holds
the submitted data, so you could submit these abandoned forms to Aggregate.
Mitch
···
On Thu, Mar 8, 2012 at 8:16 PM, Yaw Anokwa wrote:
Yes. You can add an "abandoned survey" option that users can select
and then only show the next prompt if abandoned survey is not
selected.
You can use this interaction to skip a bunch of prompts and go to the
end of the survey.
On Thu, Mar 8, 2012 at 19:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
Im sorry i meant adding some logic in the form to do that like a
choice in
a select one question.
El 08/03/2012 23:55, "Guillermo Perazzo" gaperazzo@gmail.com escribió:
Thanls for tthe answer Yaw. You think its posible to make some work
arround of this. Maybe by adding a choice option "abbandoned survey".
Do
you think this is ppossible?
Thanks
El jueves 8 de marzo de 2012, Yaw Anokwa yanokwa@gmail.com escribió:
Collect is designed so that only finalized forms are added to the list
of sendable forms. That's just a user interface thing. You can very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed all
the validation and constraint rules the form designer included, so you
may get bad data. If you choose to go that route, it might make sense
to force all saves to be finalized. These finalized forms will still
be editable, but the finalization process will ensure they only have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can then
see where people stopped filling out the forms.
On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo gaperazzo@gmail.com wrote:
But if we manage to add this on a version of the collect. We could
send
the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
2012/3/8 Yaw Anokwa yanokwa@gmail.com
Yup. You have to modify Collect to do this.
On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo < gaperazzo@gmail.com> wrote:
i dont know what you mean wen you say you could add. You are
talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
2012/3/8 Mitch S mitchellsundt@gmail.com
If you want to detect and capture the explicit cancelling-out of
a
form,
you could add to the quit dialog actions (the one that displays
when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments. It
would
be
easiest to log these events to your own, separately maintained,
logging
file, perhaps including a copy of the incomplete submission). You
would
then
need to add your own operational processes to periodically gather
this
information off the phones for analysis.
Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo gaperazzo@gmail.com wrote:
In one metting i had been asked about an exit button (or option)
avaiable
on every question for the ennumerator be able to save the survey
and
upload
it despite the survey wasnt finished.
So my bosses will have the posibility to analize the dropout
rate.
i dont know how to do it minimizing the disruption to the
output
of
the
data.
Any ideas? Im sorry about my english?
Thanks as always.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendataki
--
Guillermo A. Perazzo
--
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
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
i think i have to modify this entry?
case 0: // save and exit
isInstanceComplete(false), null);*
Maybe create a:
case 2: // save and send
isInstanceComplete(true), null);*
This will work?
Guillermo A. Perazzo
···
2012/3/9 Mitch S
And yes, ODK Aggregate does not perform any data validation, it just holds
the submitted data, so you could submit these abandoned forms to Aggregate.
Mitch
On Thu, Mar 8, 2012 at 8:16 PM, Yaw Anokwa yanokwa@gmail.com wrote:
Yes. You can add an "abandoned survey" option that users can select
and then only show the next prompt if abandoned survey is not
selected.
You can use this interaction to skip a bunch of prompts and go to the
end of the survey.
On Thu, Mar 8, 2012 at 19:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
Im sorry i meant adding some logic in the form to do that like a
choice in
a select one question.
El 08/03/2012 23:55, "Guillermo Perazzo" gaperazzo@gmail.com escribió:
Thanls for tthe answer Yaw. You think its posible to make some work
arround of this. Maybe by adding a choice option "abbandoned survey".
Do
you think this is ppossible?
Thanks
El jueves 8 de marzo de 2012, Yaw Anokwa yanokwa@gmail.com escribió:
Collect is designed so that only finalized forms are added to the
list
of sendable forms. That's just a user interface thing. You can very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed all
the validation and constraint rules the form designer included, so
you
may get bad data. If you choose to go that route, it might make sense
to force all saves to be finalized. These finalized forms will still
be editable, but the finalization process will ensure they only have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can
then
see where people stopped filling out the forms.
On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo <gaperazzo@gmail.com wrote:
But if we manage to add this on a version of the collect. We could
send
the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
2012/3/8 Yaw Anokwa yanokwa@gmail.com
Yup. You have to modify Collect to do this.
On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo < gaperazzo@gmail.com> wrote:
i dont know what you mean wen you say you could add. You are
talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
2012/3/8 Mitch S mitchellsundt@gmail.com
If you want to detect and capture the explicit cancelling-out
of a
form,
you could add to the quit dialog actions (the one that displays
when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments. It
would
be
easiest to log these events to your own, separately maintained,
logging
file, perhaps including a copy of the incomplete submission).
You
would
then
need to add your own operational processes to periodically
gather
this
information off the phones for analysis.
Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo gaperazzo@gmail.com wrote:
In one metting i had been asked about an exit button (or
option)
avaiable
on every question for the ennumerator be able to save the
survey
and
upload
it despite the survey wasnt finished.
So my bosses will have the posibility to analize the dropout
rate.
i dont know how to do it minimizing the disruption to the
output
of
the
data.
Any ideas? Im sorry about my english?
Thanks as always.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendataki
--
Guillermo A. Perazzo
--
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
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
Hi Guillermo,
We can't really provide this level of support. If the changes you need
to make in the Java code aren't clear, you might want to hire help at
Yaw
···
On Sun, Mar 11, 2012 at 17:17, Guillermo Perazzo wrote:
> i think i have to modify this entry?
> case 0: // save and exit
> saveDataToDisk(EXIT,
> isInstanceComplete(false), null);
> break;
> Maybe create a:
> case 2: // save and send
> saveDataToDisk(EXIT,
> isInstanceComplete(true), null);
> break;
> This will work?
>
> Guillermo A. Perazzo
>
>
>
>
>
>
> 2012/3/9 Mitch S
>>
>> And yes, ODK Aggregate does not perform any data validation, it just holds
>> the submitted data, so you could submit these abandoned forms to Aggregate.
>>
>> Mitch
>>
>>
>> On Thu, Mar 8, 2012 at 8:16 PM, Yaw Anokwa wrote:
>>>
>>> Yes. You can add an "abandoned survey" option that users can select
>>> and then only show the next prompt if abandoned survey is not
>>> selected.
>>>
>>> You can use this interaction to skip a bunch of prompts and go to the
>>> end of the survey.
>>>
>>> On Thu, Mar 8, 2012 at 19:39, Guillermo Perazzo wrote:
>>> > Im sorry i meant adding some logic in the form to do that like a
>>> > choice in
>>> > a select one question.
>>> >
>>> > El 08/03/2012 23:55, "Guillermo Perazzo" escribió:
>>> >
>>> >> Thanls for tthe answer Yaw. You think its posible to make some work
>>> >> arround of this. Maybe by adding a choice option "abbandoned survey".
>>> >> Do
>>> >> you think this is ppossible?
>>> >> Thanks
>>> >>
>>> >> El jueves 8 de marzo de 2012, Yaw Anokwa escribió:
>>> >> > Collect is designed so that only finalized forms are added to the
>>> >> > list
>>> >> > of sendable forms. That's just a user interface thing. You can very
>>> >> > easily modify the code base so that unfinished forms get sent.
>>> >> >
>>> >> > The caveat is that unfinished forms have not necessarily passed all
>>> >> > the validation and constraint rules the form designer included, so
>>> >> > you
>>> >> > may get bad data. If you choose to go that route, it might make
>>> >> > sense
>>> >> > to force all saves to be finalized. These finalized forms will still
>>> >> > be editable, but the finalization process will ensure they only have
>>> >> > valid data.
>>> >> >
>>> >> > Once the finalized but unfinished forms are on Aggregate, you can
>>> >> > then
>>> >> > see where people stopped filling out the forms.
>>> >> >
>>> >> > On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo wrote:
>>> >> >> But if we manage to add this on a version of the collect. We could
>>> >> >> send
>>> >> >> the
>>> >> >> unfinished forms to aggregate? So they can analize the data?
>>> >> >>
>>> >> >> Guillermo A. Perazzo
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> 2012/3/8 Yaw Anokwa
>>> >> >>>
>>> >> >>> Yup. You have to modify Collect to do this.
>>> >> >>>
>>> >> >>> On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo wrote:
>>> >> >>> > i dont know what you mean wen you say you could add. You are
>>> >> >>> > talking
>>> >> >>> > about
>>> >> >>> > modifiing collect?
>>> >> >>> > In sorry
>>> >> >>> > Guillermo A. Perazzo
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > 2012/3/8 Mitch S
>>> >> >>> >>
>>> >> >>> >> If you want to detect and capture the explicit cancelling-out
>>> >> >>> >> of a
>>> >> >>> >> form,
>>> >> >>> >> you could add to the quit dialog actions (the one that displays
>>> >> >>> >> when
>>> >> >>> >> you hit
>>> >> >>> >> the back button - "Save Changes / Ignore Changes" -- see
>>> >> >>> >> FormEntryActivity.createQuitDialog()) to track abandonments.
>>> >> >>> >> It
>>> >> >>> >> would
>>> >> >>> >> be
>>> >> >>> >> easiest to log these events to your own, separately maintained,
>>> >> >>> >> logging
>>> >> >>> >> file, perhaps including a copy of the incomplete submission).
>>> >> >>> >> You
>>> >> >>> >> would
>>> >> >>> >> then
>>> >> >>> >> need to add your own operational processes to periodically
>>> >> >>> >> gather
>>> >> >>> >> this
>>> >> >>> >> information off the phones for analysis.
>>> >> >>> >>
>>> >> >>> >> Mitch
>>> >> >>> >>
>>> >> >>> >> On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo wrote:
>>> >> >>> >>>
>>> >> >>> >>> In one metting i had been asked about an exit button (or
>>> >> >>> >>> option)
>>> >> >>> >>> avaiable
>>> >> >>> >>> on every question for the ennumerator be able to save the
>>> >> >>> >>> survey
>>> >> >>> >>> and
>>> >> >>> >>> upload
>>> >> >>> >>> it despite the survey wasnt finished.
>>> >> >>> >>> So my bosses will have the posibility to analize the dropout
>>> >> >>> >>> rate.
>>> >> >>> >>> i dont know how to do it minimizing the disruption to the
>>> >> >>> >>> output
>>> >> >>> >>> of
>>> >> >>> >>> the
>>> >> >>> >>> data.
>>> >> >>> >>>
>>> >> >>> >>> Any ideas? Im sorry about my english?
>>> >> >>> >>> Thanks as always.
>>> >> >>> >>>
>>> >> >>> >>>
>>> >> >>> >>> --
>>> >> >>> >>> Post: opendatakit@googlegroups.com
>>> >> >>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> >> >>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>> >> --
>>> >> >>> >> Mitch Sundt
>>> >> >>> >> Software Engineer
>>> >> >>> >> University of Washington
>>> >> >>> >> mitchellsundt@gmail.com
>>> >> >>> >>
>>> >> >>> >> --
>>> >> >>> >> Post: opendatakit@googlegroups.com
>>> >> >>> >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> >> >>> >> Options: http://groups.google.com/group/opendatakit?hl=en
>>> >> >>> >
>>> >> >>> >
>>> >> >>> > --
>>> >> >>> > Post: opendatakit@googlegroups.com
>>> >> >>> > Unsubscribe: opendataki
>>> >>
>>> >> --
>>> >> Guillermo A. Perazzo
>>> >>
>>> >>
>>> >>
>>> > --
>>> > 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
>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitchellsundt@gmail.com
>>
>> --
>> 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
i understand that. Yaw but i didnt manage to get funding yet. So im trying
by myself by now. I have already managed to tell the aplication to mark the
form as finished, Now im trying to avoid to check the constraints so im
looking in the code. (its nice to learn two)
thanks as always and sorry.
Guillermo A. Perazzo
···
2012/3/11 Yaw Anokwa
Hi Guillermo,
We can't really provide this level of support. If the changes you need
to make in the Java code aren't clear, you might want to hire help at
http://opendatakit.org/help/help-for-hire/
Yaw
On Sun, Mar 11, 2012 at 17:17, Guillermo Perazzo gaperazzo@gmail.com wrote:
i think i have to modify this entry?
case 0: // save and exit
saveDataToDisk(EXIT,
isInstanceComplete(false), null);
break;
Maybe create a:
case 2: // save and send
saveDataToDisk(EXIT,
isInstanceComplete(true), null);
break;
This will work?
Guillermo A. Perazzo
2012/3/9 Mitch S mitchellsundt@gmail.com
And yes, ODK Aggregate does not perform any data validation, it just
holds
the submitted data, so you could submit these abandoned forms to
Aggregate.
Mitch
On Thu, Mar 8, 2012 at 8:16 PM, Yaw Anokwa yanokwa@gmail.com wrote:
Yes. You can add an "abandoned survey" option that users can select
and then only show the next prompt if abandoned survey is not
selected.
You can use this interaction to skip a bunch of prompts and go to the
end of the survey.
On Thu, Mar 8, 2012 at 19:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
Im sorry i meant adding some logic in the form to do that like a
choice in
a select one question.
El 08/03/2012 23:55, "Guillermo Perazzo" gaperazzo@gmail.com escribió:
Thanls for tthe answer Yaw. You think its posible to make some work
arround of this. Maybe by adding a choice option "abbandoned
survey".
Do
you think this is ppossible?
Thanks
El jueves 8 de marzo de 2012, Yaw Anokwa yanokwa@gmail.com escribió:
Collect is designed so that only finalized forms are added to the
list
of sendable forms. That's just a user interface thing. You can
very
easily modify the code base so that unfinished forms get sent.
The caveat is that unfinished forms have not necessarily passed
all
the validation and constraint rules the form designer included, so
you
may get bad data. If you choose to go that route, it might make
sense
to force all saves to be finalized. These finalized forms will
still
be editable, but the finalization process will ensure they only
have
valid data.
Once the finalized but unfinished forms are on Aggregate, you can
then
see where people stopped filling out the forms.
On Thu, Mar 8, 2012 at 18:03, Guillermo Perazzo gaperazzo@gmail.com wrote:
But if we manage to add this on a version of the collect. We
could
send
the
unfinished forms to aggregate? So they can analize the data?
Guillermo A. Perazzo
2012/3/8 Yaw Anokwa yanokwa@gmail.com
Yup. You have to modify Collect to do this.
On Thu, Mar 8, 2012 at 11:39, Guillermo Perazzo gaperazzo@gmail.com wrote:
i dont know what you mean wen you say you could add. You are
talking
about
modifiing collect?
In sorry
Guillermo A. Perazzo
2012/3/8 Mitch S mitchellsundt@gmail.com
If you want to detect and capture the explicit cancelling-out
of a
form,
you could add to the quit dialog actions (the one that
displays
when
you hit
the back button - "Save Changes / Ignore Changes" -- see
FormEntryActivity.createQuitDialog()) to track abandonments.
It
would
be
easiest to log these events to your own, separately
maintained,
logging
file, perhaps including a copy of the incomplete submission).
You
would
then
need to add your own operational processes to periodically
gather
this
information off the phones for analysis.
Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo gaperazzo@gmail.com wrote:
In one metting i had been asked about an exit button (or
option)
avaiable
on every question for the ennumerator be able to save the
survey
and
upload
it despite the survey wasnt finished.
So my bosses will have the posibility to analize the dropout
rate.
i dont know how to do it minimizing the disruption to the
output
of
the
data.
Any ideas? Im sorry about my english?
Thanks as always.
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendataki
--
Guillermo A. Perazzo
--
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
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
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