Collect and Google Drive, etc

Are there any plans to use Google drive to both access form definition with supplemental files and upload completed forms such that Briefcase can process the data and totally bypass Aggregate?

Aggregate was not designed to pass Gigabytes of media added to a survey so hooking up to the cloud seems the way to go for our project.

If I implemented this cloud back-end for Collect how do you recommend this feature should coexist with the current implementation of Google Drive that publishes strictly to Google maps? It would be nice to share the resulting code back into the community.

I would also like to add Box cloud support as an alternative to Google Drive as well since China blocks Google Drive and we plan for many enumerators there.

Any one else need looking for this feature?

What are your needs?

Bob

Hi Bob,

There are no plans to host submissions on Google Drive. Nafundi is
aware of this feature request and we are working on an alternative
that would publish to other Google products (e.g. Maps).

Yaw

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

On Fri, Jan 30, 2015 at 9:09 AM, bobachgill@hishandsreader.org wrote:

Are there any plans to use Google drive to both access form definition with supplemental files and upload completed forms such that Briefcase can process the data and totally bypass Aggregate?

Aggregate was not designed to pass Gigabytes of media added to a survey so hooking up to the cloud seems the way to go for our project.

If I implemented this cloud back-end for Collect how do you recommend this feature should coexist with the current implementation of Google Drive that publishes strictly to Google maps? It would be nice to share the resulting code back into the community.

I would also like to add Box cloud support as an alternative to Google Drive as well since China blocks Google Drive and we plan for many enumerators there.

Any one else need looking for this feature?

What are your needs?

Bob

--
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.

Whatever you develop would be a different "Server Protocol".

I assume you want a simple file-based PUT/GET API for accessing form
definitions (including media) on the server and also storing the submission
XML and media on the server.

You might consider S3 with encrypted forms, and whether to require
encrypted forms to provide greater security.

I would see each of these (S3, Box, Drive) being a different "Server
Protocol" that the user chooses, and then supplies a bucket/URL and
authentication credentials.

They might share some common implementation code.

Each would be a different Pull option in ODK Briefcase.

··· --------------

Note that the Google Maps protocol stores submission media in Picasa, not
on Google Drive.

I have an e-mail out to Yaw to add documentation to the opendatakit.org
site for this functionality ( Nafundi added it for Google Earth Outreach ) .

On Fri, Jan 30, 2015 at 9:14 AM, Yaw Anokwa yanokwa@nafundi.com wrote:

Hi Bob,

There are no plans to host submissions on Google Drive. Nafundi is
aware of this feature request and we are working on an alternative
that would publish to other Google products (e.g. Maps).

Yaw

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

On Fri, Jan 30, 2015 at 9:09 AM, bobachgill@hishandsreader.org wrote:

Are there any plans to use Google drive to both access form definition
with supplemental files and upload completed forms such that Briefcase can
process the data and totally bypass Aggregate?

Aggregate was not designed to pass Gigabytes of media added to a survey
so hooking up to the cloud seems the way to go for our project.

If I implemented this cloud back-end for Collect how do you recommend
this feature should coexist with the current implementation of Google Drive
that publishes strictly to Google maps? It would be nice to share the
resulting code back into the community.

I would also like to add Box cloud support as an alternative to Google
Drive as well since China blocks Google Drive and we plan for many
enumerators there.

Any one else need looking for this feature?

What are your needs?

Bob

--
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.

--
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

Thanks Mitch.

You talked me in to it. Yes, the S3 sounds like the best approach.

Probably want to separate out, forms definitions (including media) FROM submission XML (including media) into two separate buckets and authentication credentials. This way people can choose to get their forms from a shared forms repository, yet "Send" their completed forms somewhere else.

Other features??:

  1. The forms bucket could support browsing to choose forms by category (e.g. Forestry, Water, Medical, Education, Travel.) Categories can be delineated by folders in the forms bucket. Maybe even put in a selection list to choose from a growing list of registered forms provider bulletin board sites.

  2. Add support for a "Form owner tag Id". This tag in a form could auto direct which S3 bucket to "Send" the form to.
    e.g. Multi-lingual education survey from the University of Wisconsin is automatically directed to the University's S3 form collector bucket for aggregation
    e.g. My travel blog form containing my pics/videos with annotations from my latest trip is automatically directed to XYZ Travel Blog site S3 form collector for posting under my travel blog account with GPS coordinates and all.

Once the barrier of data size is broken by using the cloud to catch big data coming from a survey... ODK can begin to serve the generation that likes to take photos and videos with their smart phone. :slight_smile:

Bob