[open-data-kit] Sahana and ODK

i think this important thread belongs on the brand new
opendatakit-developers mailing list so i'm forwarding it there. as a
heads up for the sahana crew, we are also moving the repo to
http://code.google.com/p/opendatakit.

we don't have hard release dates set for aggregate-local, but i expect
it will be in a few months.

have you considered exposing an xforms api in sahana? doing so would
enable a number of j2me xforms clients...

··· On Mon, Apr 26, 2010 at 12:53, Stuart Moffatt wrote: > Sahana team (cc ODK team) > I am somewhat familiar with the ODK source (both ODK Collect on the device > and ODK Aggregate on the AppEngine server) as we used ODK for Person Finder > Mobile (person-finder-mobile.googlecode.com). > I suggest several possible approaches to pushing ODK-collected data to > Sahana: > 1) Use un-modified ODK Aggregate as intermediate data server > > Use ODK Collect on client with custom Sahana XForm pulled from ODK Aggregate > instance belonging to deployers of Sahana instance. > Push data from client to deployer-owned ODK Aggregate instance on AppEngine > and save data to Google Docs / Spreadsheets > Write a customized fetch client to pull data out of Google Docs and into > Sahana > > 2) Use modified ODK Aggregate as intermediate data server > > Use ODK Collect on client with custom Sahana XForm pulled from ODK Aggregate > instance belonging to deployers of Sahana instance. > Push data from client to deployer-owned ODK Aggregate instance on AppEngine > and save data to Google AppEngine datastore > Add a custom servlet to Aggregate to push data out of AppEngine and across > HTTP to a Sahana instance (assuming HTTP based Sahana API accepts data) > > 3) Wait for un-released ODK Aggregate "Local" as intermediate server > > Aggregate "Local" is un-released, but will provide an abstracted Aggregate > interface to allow deployments to have data in something other than Google > AppEngine's datastore > (http://code.google.com/p/open-data-kit/source/browse/branches/uw/aggregate-local/readme.pdf) > Use ODK Collect on client with custom Sahana XForm pulled from ODK Aggregate > Local instance belonging to deployers of Sahana instance. > Push data from client to deployer-owned ODK Aggregate Local instance on > Sahana-deployer-owned Tomcat + MySQL system > Add a custom servlet to Aggregate Local to push data into Sahana OR write a > customized fetch client to pull data out of Aggregate Local and into Sahana > OR otherwise try to synchronize data at the MySQL database level > > In all three cases, some work is required to push data from ODK Aggregate > into Sahana. Also, work will be required to develop custom XForms (examples > at http://code.google.com/p/open-data-kit/source/browse/#svn/resources/forms) > that collect the data Sahana expects for its various modules. > ODK Devs -- can you comment on release dates for Aggregate Local? > Sahana Devs -- likely the only client project you will need in Sahana-mobile > project root is for customized XForms. I don't think there is any ODK client > code you will need to modify. > Stuart > > On Mon, Apr 26, 2010 at 3:06 PM, Chamindra de Silva wrote: >> >> Paneeth would be great if you can lead the mobile effort moving forward, >> with the others. I would also like to see us creating a new project under >> the the Sahana project specifically for mobile branches. >> >> I suggest we simply call it Sahana-mobile and host all the J2ME versions, >> Android app and any further work we hope to do in mobile. >> >> Chamindra >> >> On Thu, Apr 22, 2010 at 4:34 PM, Gavin Treadgold wrote: >>> >>> On 2010-04-22, at 18:52 , Praneeth wrote: >>> > Open Data Kit (ODK) >>> >>> A big +1 from me towards moving towards ODK if we can. They already have >>> some good apps and services setup that should speed the integration of data >>> collection on Android phones. They seem like they have a good generalised >>> platform that could be integrated into ours. >>> >>> Cheers Gav >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "SahanaPy" group. >>> To post to this group, send email to sahanapy@googlegroups.com. >>> To unsubscribe from this group, send email to >>> sahanapy+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/sahanapy?hl=en. >>> >> >> >> >> -- >> Chamindra de Silva >> Home: http://chamindra-de-silva.blogspot.com >> Twitter: http://twitter.com/ChamindraS (note the last S!) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "SahanaPy" group. >> To post to this group, send email to sahanapy@googlegroups.com. >> To unsubscribe from this group, send email to >> sahanapy+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/sahanapy?hl=en. > > -- > Post: open-data-kit@googlegroups.com > Unsubscribe: open-data-kit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/open-data-kit?hl=en >

We already have one :slight_smile:

F

··· On 27 April 2010 03:04, Yaw Anokwa wrote: > have you considered exposing an xforms api in sahana? doing so would > enable a number of j2me xforms clients...

--
Subscription settings: http://groups.google.com/group/opendatakit-developers/subscribe?hl=en

which is fine. any thoughts on adding xforms to sahana as a plugin?

··· On Mon, Apr 26, 2010 at 23:38, Fran Boon wrote: > On 27 April 2010 03:04, Yaw Anokwa wrote: >> have you considered exposing an xforms api in sahana? doing so would >> enable a number of j2me xforms clients... > > We already have one :) > > F >

--
Subscription settings: http://groups.google.com/group/opendatakit-developers/subscribe?hl=en

which is fine. any thoughts on adding xforms to sahana as a plugin?

What do you mean by a 'plugin'?

We already have a Controller which automatically generates XForms from
the Models.
This only provides a basic 1st-level which needs manually tweaking for
advanced functionality, but can easily incorporate a GWT-based editor
to do this.

F

··· On 27 April 2010 15:35, Yaw Anokwa wrote:

On Mon, Apr 26, 2010 at 23:38, Fran Boon francisboon@googlemail.com wrote:

On 27 April 2010 03:04, Yaw Anokwa yanokwa@gmail.com wrote:

have you considered exposing an xforms api in sahana? doing so would
enable a number of j2me xforms clients...

We already have one :slight_smile:

F

--
Subscription settings: http://groups.google.com/group/opendatakit-developers/subscribe?hl=en

the openrosa community has an emerging standard for downloading xforms
and posting xform instance data back to servers. what i mean by a
plugin is something on the sahana server that implements that
standard.

··· On Tue, Apr 27, 2010 at 08:29, Fran Boon wrote: > On 27 April 2010 15:35, Yaw Anokwa wrote: >> which is fine. any thoughts on adding xforms to sahana as a plugin? > > What do you mean by a 'plugin'? > > We already have a Controller which automatically generates XForms from > the Models. > This only provides a basic 1st-level which needs manually tweaking for > advanced functionality, but can easily incorporate a GWT-based editor > to do this. > > F > >> On Mon, Apr 26, 2010 at 23:38, Fran Boon wrote: >>> On 27 April 2010 03:04, Yaw Anokwa wrote: >>>> have you considered exposing an xforms api in sahana? doing so would >>>> enable a number of j2me xforms clients... >>> >>> We already have one :) >>> >>> F >>> >> >

--
Subscription settings: http://groups.google.com/group/opendatakit-developers/subscribe?hl=en

The time line for Aggregate 1.0 (which will include local datastores) is
first dependent on when the new standards are set that Yaw is referring to.
We are trying to minimize non backward compatible changes so we are grouping
a whole bunch in one big move to 1.0. Once the standards are settled it
will then take a few weeks of coding to implement things.

Aggregate is setup to automatically push data on reception of uploads to
another service. What type of api does your server normally take? We have
not setup aggregate to be fault tolerant in the push though so something
might get lost.

Cheers,
Waylon

··· On Tue, Apr 27, 2010 at 8:34 AM, Yaw Anokwa wrote:

the openrosa community has an emerging standard for downloading xforms
and posting xform instance data back to servers. what i mean by a
plugin is something on the sahana server that implements that
standard.

On Tue, Apr 27, 2010 at 08:29, Fran Boon francisboon@googlemail.com wrote:

On 27 April 2010 15:35, Yaw Anokwa yanokwa@gmail.com wrote:

which is fine. any thoughts on adding xforms to sahana as a plugin?

What do you mean by a 'plugin'?

We already have a Controller which automatically generates XForms from
the Models.
This only provides a basic 1st-level which needs manually tweaking for
advanced functionality, but can easily incorporate a GWT-based editor
to do this.

F

On Mon, Apr 26, 2010 at 23:38, Fran Boon francisboon@googlemail.com wrote:

On 27 April 2010 03:04, Yaw Anokwa yanokwa@gmail.com wrote:

have you considered exposing an xforms api in sahana? doing so would
enable a number of j2me xforms clients...

We already have one :slight_smile:

F

--
Subscription settings:
http://groups.google.com/group/opendatakit-developers/subscribe?hl=en