Allow submitted forms to be marked as invalid and resubmitted

[GoogleCodeExporter]

We have a use case where we want to use ODK Collect/Aggregate to collect health 
information. That health information will be inserted into a third party health 
system. We anticipate that there will be validation and other errors that could 
occur during form entry. We would like to keep invalid forms in Collect until 
the field worker has corrected them. After they have corrected them we assume 
they will be resubmitted.

I believe this will require changes on both Aggregate and Collect if it is 
accepted. Ideally, Aggregate would communicate all invalid submissions, and a 
brief message as to why the form submission failed. All valid forms would be 
deleted from the Collect client.

Original issue reported on code.google.com by david.ro...@gmail.com on 16 Jun 2011 at 6:52

[GoogleCodeExporter]

I think this is a general issue for anyone wishing to integrate ODK with third 
party systems. I don't believe there is a way of doing this currently with ODK. 

I would be willing to work on this issue if the ODK team thinks it would fit 
into their main line of development.

Ideas or suggestions on this issue are welcome.

Original comment by david.ro...@gmail.com on 16 Jun 2011 at 6:54

[GoogleCodeExporter]

Hi, based on the timing this issue was created, I'm assuming you guys do not 
believe this is a priority or have not had time to review. Either way, I just 
wanted to say I've actually started working on this based on the v1.1.5 
release. I'm trying to keep the work general enough so that it may at some 
point later be integrated back to the main ODK development line if you wish.

At this point, we have defined what we call a 'validation' server that can be 
enabled/disabled and configured in the Server Preferences activity on ODK 
Collect. We have also defined a preliminary protocol that the client can use to 
talk with a validation server. Essentially, the client sends an array of all 
submitted form ids to the validation server, and it responds back with any 
validation errors for those forms (the elements that failed validation and the 
reason(s) for failure.) Also, we've added functionality to the UI that 
indicates forms that have failed validation on the InstanceChooserActivity, as 
well as indicating fields that are invalid on the FormHierarchyActivity.

There are still some issues that need to be sorted out, but we plan to continue 
iterating on this issue. Hopefully this paints a clear picture of our 
intentions if there were any questions from the previous comments. I'm going to 
consider this issue as rejected, but if anyone wants to talk more on this, or 
the ODK team wants to look at our solution, please contact me.

Thanks

Original comment by david.ro...@gmail.com on 5 Jul 2011 at 7:42

[GoogleCodeExporter]

Sorry about our silence we are just scrambling to get out Collect 1.1.7 and 
Aggregate 1.0. This is definitely going to be an enhancement. Once we start 
moving on to new features for the next set of releases we will start to 
consider this stuff. Right now we are trying to move the current stuff out of 
Beta.

Original comment by wbrune...@gmail.com on 5 Jul 2011 at 11:47

• Added labels: Aggregate, Collect, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by mitchellsundt@gmail.com on 11 Aug 2011 at 9:01

• Added labels: Future