Editing a sent form

Hi,

Any way to work around editing a finalized form that has already been sent.

Thanks.

Raul

Nope. The sent form still lives on the SD card, but we hide it from
view. Feel free to change that in your build of Collect, but this has
all sorts of implications on workflow. For example, if you change a
sent form and re-send it, should it update the old form on the server?
Should it make create a totally new form?

ยทยทยท On Mon, Dec 10, 2012 at 3:58 AM, Raul Maano wrote: > Hi, > > Any way to work around editing a finalized form that has already been sent. > > Thanks. > > Raul > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

And at least for Aggregate, if you have an instanceID in the form (
http://opendatakit.org/help/form-design/ ), Aggregate is designed to *reject

  • the follow-on submission.

Mitch

ยทยทยท On Mon, Dec 10, 2012 at 7:03 AM, Yaw Anokwa wrote:

Nope. The sent form still lives on the SD card, but we hide it from
view. Feel free to change that in your build of Collect, but this has
all sorts of implications on workflow. For example, if you change a
sent form and re-send it, should it update the old form on the server?
Should it make create a totally new form?

On Mon, Dec 10, 2012 at 3:58 AM, Raul Maano simplyraul@gmail.com wrote:

Hi,

Any way to work around editing a finalized form that has already been
sent.

Thanks.

Raul

--
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 am referring here on the ODK collect app.

Take a scenario of a person going to a camp site to gather information this
week.
He comes back next week to the same camp to gather information again. The
form on the ODK collect is long. So everytime he goes back to the camp
site, he will re-encode all the data on the blank form and save again
before sending.

Wouldn't it be more logical for him to just pull up or open a previously
sent form and edit some of the entries and then resend ?

This is pertaining to ODK collect and not the form on the Aggregate. This
refers rather to the instance that is created everytime you select, "Fill
blank form."

Thanks.

Raul

ยทยทยท On Mon, Dec 10, 2012 at 7:29 PM, Mitch S wrote:

And at least for Aggregate, if you have an instanceID in the form (
http://opendatakit.org/help/form-design/ ), Aggregate is designed to *
reject* the follow-on submission.

Mitch

On Mon, Dec 10, 2012 at 7:03 AM, Yaw Anokwa yanokwa@nafundi.com wrote:

Nope. The sent form still lives on the SD card, but we hide it from
view. Feel free to change that in your build of Collect, but this has
all sorts of implications on workflow. For example, if you change a
sent form and re-send it, should it update the old form on the server?
Should it make create a totally new form?

On Mon, Dec 10, 2012 at 3:58 AM, Raul Maano simplyraul@gmail.com wrote:

Hi,

Any way to work around editing a finalized form that has already been
sent.

Thanks.

Raul

--
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

1 Like

This workflow is something the next version of the tools will address.

Mitch

ยทยทยท On Mon, Dec 10, 2012 at 12:20 PM, Raul Maano wrote:

I am referring here on the ODK collect app.

Take a scenario of a person going to a camp site to gather information
this week.
He comes back next week to the same camp to gather information again. The
form on the ODK collect is long. So everytime he goes back to the camp
site, he will re-encode all the data on the blank form and save again
before sending.

Wouldn't it be more logical for him to just pull up or open a previously
sent form and edit some of the entries and then resend ?

This is pertaining to ODK collect and not the form on the Aggregate. This
refers rather to the instance that is created everytime you select, "Fill
blank form."

Thanks.

Raul

On Mon, Dec 10, 2012 at 7:29 PM, Mitch S mitchellsundt@gmail.com wrote:

And at least for Aggregate, if you have an instanceID in the form (
http://opendatakit.org/help/form-design/ ), Aggregate is designed to *
reject* the follow-on submission.

Mitch

On Mon, Dec 10, 2012 at 7:03 AM, Yaw Anokwa yanokwa@nafundi.com wrote:

Nope. The sent form still lives on the SD card, but we hide it from
view. Feel free to change that in your build of Collect, but this has
all sorts of implications on workflow. For example, if you change a
sent form and re-send it, should it update the old form on the server?
Should it make create a totally new form?

On Mon, Dec 10, 2012 at 3:58 AM, Raul Maano simplyraul@gmail.com wrote:

Hi,

Any way to work around editing a finalized form that has already been
sent.

Thanks.

Raul

--
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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Can't wait for the next version to come out... Thanks! :slight_smile:

ยทยทยท On Mon, Dec 10, 2012 at 9:53 PM, Mitch S wrote:

This workflow is something the next version of the tools will address.

Mitch

On Mon, Dec 10, 2012 at 12:20 PM, Raul Maano simplyraul@gmail.com wrote:

I am referring here on the ODK collect app.

Take a scenario of a person going to a camp site to gather information
this week.
He comes back next week to the same camp to gather information again. The
form on the ODK collect is long. So everytime he goes back to the camp
site, he will re-encode all the data on the blank form and save again
before sending.

Wouldn't it be more logical for him to just pull up or open a previously
sent form and edit some of the entries and then resend ?

This is pertaining to ODK collect and not the form on the Aggregate.
This refers rather to the instance that is created everytime you select,
"Fill blank form."

Thanks.

Raul

On Mon, Dec 10, 2012 at 7:29 PM, Mitch S mitchellsundt@gmail.com wrote:

And at least for Aggregate, if you have an instanceID in the form (
http://opendatakit.org/help/form-design/ ), Aggregate is designed to *
reject* the follow-on submission.

Mitch

On Mon, Dec 10, 2012 at 7:03 AM, Yaw Anokwa yanokwa@nafundi.com wrote:

Nope. The sent form still lives on the SD card, but we hide it from
view. Feel free to change that in your build of Collect, but this has
all sorts of implications on workflow. For example, if you change a
sent form and re-send it, should it update the old form on the server?
Should it make create a totally new form?

On Mon, Dec 10, 2012 at 3:58 AM, Raul Maano simplyraul@gmail.com wrote:

Hi,

Any way to work around editing a finalized form that has already been
sent.

Thanks.

Raul

--
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

--
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

Dear Raul and Team,

This my workaround:
The form status is stored in an SQLite DB file in the odk/metadata directory- instances.db.
Get SQLite editor either on your PC or from play store ( I prefer SQLite studio for mac) you can edit the form status here ( from 'submitted' to 'complete' and save.
Switch to ODK collect app ( restart the app if needed) and Done!!

Let me know how it goes.

Best,
Benson

I'm sorry.. I was interested in the initial doubt and I liked the solution you gave, could you be clearer, so that I can do the same procedure?
I'm a bit of a layman in the SQL part