Aggregate to Aggregate publisher

[mitchellsundt]

Migrated to getodk/aggregate#39 by spacetelescope/github-issues-import

Originally reported on Google Code with ID 762

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.

Reported by yanokwa on 2013-02-06 20:37:53

[mitchellsundt]

Migrated to opendatakit/aggregate#39 (comment) by spacetelescope/github-issues-import

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.

Reported by mitchellsundt on 2013-02-06 22:19:29