Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be possible
to ask all the questions again.
Thanks,
Jon
Jon,
This is a feature that we've worked out over the years just because it has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become "save
as incomplete just in case" and then the list of incomplete forms
becomes unmanageably large).
It's not particularly difficult to work back in, however, if we want to make
a task order to get the feature. It would basically consist of
Saving periodically in case the application closes is much more tricky and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having it
open regularly can cause the storage to become corrupted, so we'll want to
be pretty careful and test it thoroughly.
-Clayton
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be possible
to ask all the questions again.Thanks,
Jon
Hi Clayton,
These are good points, especially the tendency to save as incomplete. I
think let's hold off and I'll bring it up again if it becomes an issue in
the field.
Thanks,
Jon
Jon,
This is a feature that we've worked out over the years just because it has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become "save
as incomplete just in case" and then the list of incomplete forms
becomes unmanageably large).It's not particularly difficult to work back in, however, if we want to
make a task order to get the feature. It would basically consist of
- Button in the XForm Player to Save as Incomplete and Exit
- Menu item on the home screen for "View Incomplete Forms"
- Restarting that form on the last unanswered question.
Saving periodically in case the application closes is much more tricky and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having it
open regularly can cause the storage to become corrupted, so we'll want to
be pretty careful and test it thoroughly.-Clayton
On Tue, Dec 14, 2010 at 3:15 AM, Jonathan Payne paynejd@gmail.com wrote:
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be possible
to ask all the questions again.Thanks,
Jon
This discussion is good, especially with long forms like IMCI especially the
community IMCI in Malawi where we expect to use CommCare. I agree with Jon
that let's hold off for now but how ready are we to support this in case it
is needed? Are we talking in terms of weeks or months to support this?
Gayo
Hi Clayton,
These are good points, especially the tendency to save as incomplete. I
think let's hold off and I'll bring it up again if it becomes an issue in
the field.
Thanks,
Jon
On Tue, Dec 14, 2010 at 11:48 AM, Clayton Sims csims@dimagi.com wrote:
Jon,
This is a feature that we've worked out over the years just because it has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become "save
as incomplete just in case" and then the list of incomplete forms becomes
unmanageably large).
It's not particularly difficult to work back in, however, if we want to make
a task order to get the feature. It would basically consist of
Button in the XForm Player to Save as Incomplete and Exit
Menu item on the home screen for "View Incomplete Forms"
Restarting that form on the last unanswered question.
Saving periodically in case the application closes is much more tricky and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having it
open regularly can cause the storage to become corrupted, so we'll want to
be pretty careful and test it thoroughly.
-Clayton
On Tue, Dec 14, 2010 at 3:15 AM, Jonathan Payne paynejd@gmail.com wrote:
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be possible
to ask all the questions again.
Thanks,
Jon
It's actually pretty quick to write up the UI, more of an issue of
determining the actual use Case. IMCI is a good example. What's the actual
use case for saving a form as incomplete? Would the nurse look up patients
from a few days ago? A week ago? How do you search for them to begin with?
Do you need to start collecting names just to be able to look up the form
later?
And if someone is coming back from a week ago, do you trust that the data
already collected hasn't changed?
Before we can really get into making a solid timeline, we'd need a good
perspective on these kinds of use case questions to make sure the feature is
truly useful.
-Clayton
This discussion is good, especially with long forms like IMCI especially
the
community IMCI in Malawi where we expect to use CommCare. I agree with Jon
that let's hold off for now but how ready are we to support this in case
it
is needed? Are we talking in terms of weeks or months to support this?Gayo
[mailto:commcare-users@googlegroups.com] On Behalf Of Jonathan Payne
Hi Clayton,
These are good points, especially the tendency to save as incomplete. I
think let's hold off and I'll bring it up again if it becomes an issue in
the field.Thanks,
Jon
Jon,
This is a feature that we've worked out over the years just because it has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become "save
as incomplete just in case" and then the list of incomplete forms becomes
unmanageably large).It's not particularly difficult to work back in, however, if we want to
make
a task order to get the feature. It would basically consist of
Button in the XForm Player to Save as Incomplete and Exit
Menu item on the home screen for "View Incomplete Forms"
Restarting that form on the last unanswered question.
Saving periodically in case the application closes is much more tricky and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having
it
open regularly can cause the storage to become corrupted, so we'll want to
be pretty careful and test it thoroughly.-Clayton
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be
possible
Clayton
Those are very good questions which we still don't know, I think that's why
Jon suggested we hold off until we find a use case before we implement.
Gayo
It's actually pretty quick to write up the UI, more of an issue of
determining the actual use Case. IMCI is a good example. What's the actual
use case for saving a form as incomplete? Would the nurse look up patients
from a few days ago? A week ago? How do you search for them to begin with?
Do you need to start collecting names just to be able to look up the form
later?
And if someone is coming back from a week ago, do you trust that the data
already collected hasn't changed?
Before we can really get into making a solid timeline, we'd need a good
perspective on these kinds of use case questions to make sure the feature is
truly useful.
-Clayton
On Dec 18, 2010 4:37 AM, "gayo" gayomhila@gmail.com wrote:
This discussion is good, especially with long forms like IMCI especially
the
community IMCI in Malawi where we expect to use CommCare. I agree with Jon
that let's hold off for now but how ready are we to support this in case
it
is needed? Are we talking in terms of weeks or months to support this?Gayo
From: commcare-users@googlegroups.com
[mailto:commcare-users@googlegroups.com] On Behalf Of Jonathan Payne
Sent: Thursday, December 16, 2010 5:19 AM
To: commcare-users
Subject: Re: Save progress on a form and continue later?Hi Clayton,
These are good points, especially the tendency to save as incomplete. I
think let's hold off and I'll bring it up again if it becomes an issue in
the field.Thanks,
Jon
On Tue, Dec 14, 2010 at 11:48 AM, Clayton Sims csims@dimagi.com wrote:
Jon,
This is a feature that we've worked out over the years just because it has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become "save
as incomplete just in case" and then the list of incomplete forms becomes
unmanageably large).It's not particularly difficult to work back in, however, if we want to
make
a task order to get the feature. It would basically consist of
Button in the XForm Player to Save as Incomplete and Exit
Menu item on the home screen for "View Incomplete Forms"
Restarting that form on the last unanswered question.
Saving periodically in case the application closes is much more tricky and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having
it
open regularly can cause the storage to become corrupted, so we'll want to
be pretty careful and test it thoroughly.-Clayton
On Tue, Dec 14, 2010 at 3:15 AM, Jonathan Payne paynejd@gmail.com wrote:
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This would
be important for long protocols, so that if the application closes (due to
error or user) or if a visit needs to be restarted later, the worker would
not have to ask all the questions again. In some cases, it won't be
possible
to ask all the questions again.Thanks,
Jon
Gayo,
Ah, for sure. I was mostly providing my perception of what questions we'll
want to start looking for from the tech side over the next few months as you
guys start formulating the use case. We're definitely all on the same page.
Cheers!
-Clayton
Clayton
Those are very good questions which we still don't know, I think that's why
Jon suggested we hold off until we find a use case before we implement.Gayo
From: commcare-users@googlegroups.com [mailto:
commcare-users@googlegroups.com] *On Behalf Of *Clayton Sims
Sent: Saturday, December 18, 2010 10:51 AM
To: commcare-users@googlegroups.com
Subject: Re: RE: Save progress on a form and continue later?It's actually pretty quick to write up the UI, more of an issue of
determining the actual use Case. IMCI is a good example. What's the actual
use case for saving a form as incomplete? Would the nurse look up patients
from a few days ago? A week ago? How do you search for them to begin with?
Do you need to start collecting names just to be able to look up the form
later?And if someone is coming back from a week ago, do you trust that the data
already collected hasn't changed?Before we can really get into making a solid timeline, we'd need a good
perspective on these kinds of use case questions to make sure the feature is
truly useful.-Clayton
On Dec 18, 2010 4:37 AM, "gayo" gayomhila@gmail.com wrote:
This discussion is good, especially with long forms like IMCI especially
the
community IMCI in Malawi where we expect to use CommCare. I agree with
Jon
that let's hold off for now but how ready are we to support this in case
it
is needed? Are we talking in terms of weeks or months to support this?Gayo
From: commcare-users@googlegroups.com
[mailto:commcare-users@googlegroups.com] On Behalf Of Jonathan Payne
Sent: Thursday, December 16, 2010 5:19 AM
To: commcare-users
Subject: Re: Save progress on a form and continue later?Hi Clayton,
These are good points, especially the tendency to save as incomplete. I
think let's hold off and I'll bring it up again if it becomes an issue in
the field.Thanks,
Jon
On Tue, Dec 14, 2010 at 11:48 AM, Clayton Sims csims@dimagi.com wrote:
Jon,
This is a feature that we've worked out over the years just because it
has
implications for the stability of the phone storage and some practicality
concerns (it's pretty common for people's default behavior to become
"save
as incomplete just in case" and then the list of incomplete forms becomes
unmanageably large).It's not particularly difficult to work back in, however, if we want to
make
a task order to get the feature. It would basically consist of
Button in the XForm Player to Save as Incomplete and Exit
Menu item on the home screen for "View Incomplete Forms"
Restarting that form on the last unanswered question.
Saving periodically in case the application closes is much more tricky
and
should be its own Task Order. There are a lot of edge cases involved
there, including the fact that the storage is pretty volatile and having
it
open regularly can cause the storage to become corrupted, so we'll want
to
be pretty careful and test it thoroughly.-Clayton
On Tue, Dec 14, 2010 at 3:15 AM, Jonathan Payne paynejd@gmail.com wrote:
Hi,
Is it possible to save progress while filling out a form in CommCare and
continuing later? I believe this is a feature supported by ODK. This
would
be important for long protocols, so that if the application closes (due
to
error or user) or if a visit needs to be restarted later, the worker
would
not have to ask all the questions again. In some cases, it won't be
possible
to ask all the questions again.Thanks,
Jon