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.
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
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
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
information off the phones for analysis.Mitch
On Thu, Mar 8, 2012 at 10:37 AM, Guillermo Perazzo gaperazzo@gmail.comwrote:
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
Yup. You have to modify Collect to do this.
We also need this feature. A button that allows the data collector to terminate the form and be able to send it to the server with a tag that says the respondent didn't want to continue anymore and the reason. And to be able to log the number of visits to complete an interview.
If anyone knows how to modify the Collect to be able to do this, please send me a message. Thank you!
You can detect the number of times a form was entered from the form audit log. When you export a zip from Central you get a single log from all submissions which you can process. I think you could answer your question with an Excel pivot table though I think currently most people who get automated insights from the audit log write scripts to do so.
What I've seen people do to allow partial submissions and still use constraints validated by the system is to start subsections with a yes/no question like "Are you ready to fill out section XYZ". If the answer is no, everything following that question is non-relevant. If you also need a reason for early submission, you can have a question at the very end with text something like "Were you able to complete all relevant sections?" (or you can compute this) and if not, you can ask for a reason (and make that question required).