Publish to Github

I created a small node.js app to publish ODK submissions to Github. Thought
this might be useful for some people:

This is not fully tested yet, and I would welcome any comments/additions.

This is pretty cool, Gregor. Can you share a little bit about what
high level problem you are trying to solve with this approach?

Yaw

··· -- Need ODK services? http://nafundi.com provides form design, server setup, professional support, and software development for ODK.

On Mon, Jan 27, 2014 at 9:26 AM, Gregor MacLennan gmaclennan@digital-democracy.org wrote:

I created a small node.js app to publish ODK submissions to Github. Thought
this might be useful for some people:

https://github.com/digidem/odk-to-github/

This is not fully tested yet, and I would welcome any comments/additions.

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


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

I am building an offline web app for viewing and editing data from ODK.
Ultimately I'm moving towards the concept of static sites
(e.g. http://jekyllrb.com/) for data. I'm interested in git for data
because of its commit history. One piece will be another small server to
concat all the submissions into paged lists of submissions. Ultimately I'm
interested in cutting out the ODK backend tools altogether, and just
implementing a small server to receive submissions and post to Github. All
indexing would be done by servers running on Github webhooks creating
static data files. For my uses we are dealing with only hundreds or
possibly a few thousand submissions, and I like the idea of keeping all
data in static files rather than dealing with a database.

Gregor

··· On Monday, January 27, 2014 12:13:47 PM UTC-6, Yaw Anokwa wrote: > > This is pretty cool, Gregor. Can you share a little bit about what > high level problem you are trying to solve with this approach? > > Yaw > -- > Need ODK services? http://nafundi.com provides form design, server > setup, professional support, and software development for ODK. > > On Mon, Jan 27, 2014 at 9:26 AM, Gregor MacLennan <gmacl...@digital-democracy.org > wrote: > > I created a small node.js app to publish ODK submissions to Github. > Thought > > this might be useful for some people: > > > > https://github.com/digidem/odk-to-github/ > > > > This is not fully tested yet, and I would welcome any > comments/additions. > > > > -- > > -- > > Post: opend...@googlegroups.com > > Unsubscribe: opendatakit...@googlegroups.com > > Options: http://groups.google.com/group/opendatakit?hl=en > > > > --- > > You received this message because you are subscribed to the Google > Groups > > "ODK Community" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to opendatakit...@googlegroups.com . > > For more options, visit https://groups.google.com/groups/opt_out. >

Also: I'm looking to use a small Raspberry Pi (or any small server) for
offline submission of ODK forms. The idea is that the Pi would create an
adhoc wi-fi network for the phones to connect to, or have a card-reader to
pull the forms from. A small server on the Pi would just save the files as
json, then when the Pi can connect it can use git to sync - which is pretty
efficient over a slow connection such as GPRS or even less. I've found http
form submissions from OSK Collect to be very unreliable on slow
connections.

··· On Wednesday, February 12, 2014 7:19:32 AM UTC-6, Gregor MacLennan wrote: > > I am building an offline web app for viewing and editing data from ODK. > Ultimately I'm moving towards the concept of static sites (e.g. > http://jekyllrb.com/) for data. I'm interested in git for data because of > its commit history. One piece will be another small server to concat all > the submissions into paged lists of submissions. Ultimately I'm interested > in cutting out the ODK backend tools altogether, and just implementing a > small server to receive submissions and post to Github. All indexing would > be done by servers running on Github webhooks creating static data files. > For my uses we are dealing with only hundreds or possibly a few thousand > submissions, and I like the idea of keeping all data in static files rather > than dealing with a database. > > Gregor > > > On Monday, January 27, 2014 12:13:47 PM UTC-6, Yaw Anokwa wrote: >> >> This is pretty cool, Gregor. Can you share a little bit about what >> high level problem you are trying to solve with this approach? >> >> Yaw >> -- >> Need ODK services? http://nafundi.com provides form design, server >> setup, professional support, and software development for ODK. >> >> On Mon, Jan 27, 2014 at 9:26 AM, Gregor MacLennan wrote: >> > I created a small node.js app to publish ODK submissions to Github. >> Thought >> > this might be useful for some people: >> > >> > https://github.com/digidem/odk-to-github/ >> > >> > This is not fully tested yet, and I would welcome any >> comments/additions. >> > >> > -- >> > -- >> > Post: opend...@googlegroups.com >> > Unsubscribe: opendatakit...@googlegroups.com >> > Options: http://groups.google.com/group/opendatakit?hl=en >> > >> > --- >> > You received this message because you are subscribed to the Google >> Groups >> > "ODK Community" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to opendatakit...@googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >