ODK Aggregate Data Transfer

Development
1

Hello,

I need to use the data collected using ODK Collect and Aggregate in web
applications to be build on Rails framework. I explored about data transfer
and looks like JSON publishing should be the way to go and the rails
application should have an API to receive the data published from aggregate.

I would like to know if this is the best approach or should any other
approach be considered?

Thanks,
Yeshasvi

2

It is probably the simplest, as it isolates your application from our
database schema.

Others have used triggers on our database tables to publish data into their
own tables, but this is very difficult to maintain if you have rapidly
changing forms.

You may find these tables in our database useful for automatically
interpreting the JSON publisher content based upon the source form
definition.

_form_info == all the forms in the system
_form_info_submission_association == association of form id to
URI_SUBMISSION_DATA_MODEL
_form_data_model == for a given URI_SUBMISSION_DATA_MODEL, a description of
the form structure.

If you host your own ODK Aggregate, you would be able to access these
configuration tables directly to perhaps help automatically process the
JSON data stream.

It would save you from having to parse the XML form definition yourself.

··· On Thu, Dec 24, 2015 at 9:14 AM, Yeshasvi Pachpore < yeshasvi.pachpore@gmail.com> wrote:

Hello,

I need to use the data collected using ODK Collect and Aggregate in web
applications to be build on Rails framework. I explored about data transfer
and looks like JSON publishing should be the way to go and the rails
application should have an API to receive the data published from aggregate.

I would like to know if this is the best approach or should any other
approach be considered?

Thanks,
Yeshasvi

--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

3

Thank you Mitch, this is very useful.

Yeshasvi

··· On Thursday, December 24, 2015 at 1:31:09 PM UTC-6, Mitch wrote: > > It is probably the simplest, as it isolates your application from our > database schema. > > Others have used triggers on our database tables to publish data into > their own tables, but this is very difficult to maintain if you have > rapidly changing forms. > > You may find these tables in our database useful for automatically > interpreting the JSON publisher content based upon the source form > definition. > > _form_info == all the forms in the system > _form_info_submission_association == association of form id to > URI_SUBMISSION_DATA_MODEL > _form_data_model == for a given URI_SUBMISSION_DATA_MODEL, a description > of the form structure. > > If you host your own ODK Aggregate, you would be able to access these > configuration tables directly to perhaps help automatically process the > JSON data stream. > > It would save you from having to parse the XML form definition yourself. > > > On Thu, Dec 24, 2015 at 9:14 AM, Yeshasvi Pachpore <yeshasvi...@gmail.com > wrote: > >> Hello, >> >> I need to use the data collected using ODK Collect and Aggregate in web >> applications to be build on Rails framework. I explored about data transfer >> and looks like JSON publishing should be the way to go and the rails >> application should have an API to receive the data published from aggregate. >> >> I would like to know if this is the best approach or should any other >> approach be considered? >> >> Thanks, >> Yeshasvi >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ODK Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to opendatakit-developers+unsubscribe@googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com >