anupmishra20 / opendatakit

Automatically exported from code.google.com/p/opendatakit
0 stars 0 forks source link

Aggregate to Aggregate publisher #762

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
There are scenarios where you want to feed data from one Aggregate instance to 
another. For example, you can have a hierarchical data collection campaign 
where data is reviewed in each district before being forwarded on to the 
country level. In these scenarios, it'd be great to have a way to forward data 
from one instance to another. I suppose you could use Briefcase, but transfers 
would be a lot faster and easier if you go server to server.

Original issue reported on code.google.com by yanokwa on 6 Feb 2013 at 8:37

GoogleCodeExporter commented 9 years ago
Since any 'review' step is likely to involve updating or correcting of the 
records (just supporting delete would not be a viable offering), and since ODK 
Aggregate does not allow record updates by design, the best way to accomplish 
this is to not change ODK Aggregate at all:

(1) submit data into  form_id = 'incoming_submissions'
(2) write a site-specific webapp that uses the ODK Briefcase APIs to query for 
newly-completed forms, present these to the office staff for whatever 
approval/mark-up workflow they need,
(3) once that custom work-flow is complete, submit data into a different 
form_id = 'verified_submissions'
(4) establish publishers on this verified form to send the data upward.

Original comment by mitchellsundt@gmail.com on 6 Feb 2013 at 10:19