Hi to everyone I haven't met. I'm a developer with Lumana and I'm
working on a web app that will act as a simple alternative to ODK
Aggregate called ODK Route. I was wondering if there was a doc
written up describing the different POST and GET requests that Collect
uses to download and submit surveys.
Also, what kind of authentication is supported between the mobile app
and the server?
There is no standard written up because the current interaction is
temporary. As discussed on our previous mailing list ( open-data-kit@googlegroups.com, you may want to search the archieve for more
detailed information) we are waiting on a server standard to be devloped by
the OpenRosa/JavaRosa team. Currently there is no authentication in the
temporary standard. The Authorization proposed standard is http://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPI. Feel free to
get involved in the process of moving the standard forward.
Once that is finalized a new suite of tools will be released (ODK Aggregate
1.0 (a non backwards compatible revision), ODK Form Manager, ODK Briefcase).
Cheers,
Waylon
···
On Tue, May 4, 2010 at 5:42 PM, Chad wrote:
Hi to everyone I haven't met. I'm a developer with Lumana and I'm
working on a web app that will act as a simple alternative to ODK
Aggregate called ODK Route. I was wondering if there was a doc
written up describing the different POST and GET requests that Collect
uses to download and submit surveys.
Also, what kind of authentication is supported between the mobile app
and the server?
···
On Tue, May 4, 2010 at 21:01, W. Brunette wrote:
> Chad,
>
> There is no standard written up because the current interaction is
> temporary. As discussed on our previous mailing
> list (open-data-kit@googlegroups.com, you may want to search the archieve
> for more detailed information) we are waiting on a server standard to
> be devloped by the OpenRosa/JavaRosa team. Currently there is no
> authentication in the temporary standard. The Authorization proposed
> standard is http://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPI.
> Feel free to get involved in the process of moving the standard forward.
>
> Once that is finalized a new suite of tools will be released (ODK Aggregate
> 1.0 (a non backwards compatible revision), ODK Form Manager, ODK Briefcase).
> Cheers,
> Waylon
> On Tue, May 4, 2010 at 5:42 PM, Chad wrote:
>>
>> Hi to everyone I haven't met. I'm a developer with Lumana and I'm
>> working on a web app that will act as a simple alternative to ODK
>> Aggregate called ODK Route. I was wondering if there was a doc
>> written up describing the different POST and GET requests that Collect
>> uses to download and submit surveys.
>>
>> Also, what kind of authentication is supported between the mobile app
>> and the server?
>>
>> Thanks!
>> Chad
>
>
Can you share any details about ODK Form Manager or ODK Briefcase?
···
On May 4, 2010, at 11:01 PM, W. Brunette wrote:
Chad,
There is no standard written up because the current interaction is temporary. As discussed on our previous mailing list (open-data-kit@googlegroups.com, you may want to search the archieve for more detailed information) we are waiting on a server standard to be devloped by the OpenRosa/JavaRosa team. Currently there is no authentication in the temporary standard. The Authorization proposed standard is http://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPI. Feel free to get involved in the process of moving the standard forward.
Once that is finalized a new suite of tools will be released (ODK Aggregate 1.0 (a non backwards compatible revision), ODK Form Manager, ODK Briefcase).
Cheers,
Waylon
On Tue, May 4, 2010 at 5:42 PM, Chad chadskeers@gmail.com wrote:
Hi to everyone I haven't met. I'm a developer with Lumana and I'm
working on a web app that will act as a simple alternative to ODK
Aggregate called ODK Route. I was wondering if there was a doc
written up describing the different POST and GET requests that Collect
uses to download and submit surveys.
Also, what kind of authentication is supported between the mobile app
and the server?
ODK Aggregate is changing with the new non backwards compatible interfaces ,
it's new function is to provide a wrapper for databases using a Java web
container to handle web requests. Since people may want to have multiple
repositories in multiple locations; examples, on a local machine running
mySQL or PostGres or on web.
ODK Form Manager will handle uploading the forms and setting up the
distribution. Basically a central repository of forms will exist and you
will chose form a drop down menu where you want your data to end up. It may
be Aggregate, it may be a a third party server, etc. Form Manager generates
a URL for submission and collect then will submit the submissions directly
to the URL or Form Manager will route the submission if the URL is
different.
ODK Briefcase will allow you to pull all your data out of an ODK server tool
and save it in a zip. It will also upload all the information from the zip
to an ODK server. Basically it will allow you to get your data out or put
new data in. This tool will help you own your data.
Cheers,
Waylon
···
On Wed, May 5, 2010 at 12:01 PM, Joel Shafer wrote:
Can you share any details about ODK Form Manager or ODK Briefcase?
On May 4, 2010, at 11:01 PM, W. Brunette wrote:
Chad,
There is no standard written up because the current interaction is
temporary. As discussed on our previous mailing list ( open-data-kit@googlegroups.com, you may want to search the archieve
for more detailed information) we are waiting on a server standard to
be devloped by the OpenRosa/JavaRosa team. Currently there is no
authentication in the temporary standard. The Authorization proposed
standard is http://bitbucket.org/javarosa/javarosa/wiki/AuthorizationAPI.
Feel free to get involved in the process of moving the standard forward.
Once that is finalized a new suite of tools will be released (ODK Aggregate
1.0 (a non backwards compatible revision), ODK Form Manager, ODK Briefcase).
Hi to everyone I haven't met. I'm a developer with Lumana and I'm
working on a web app that will act as a simple alternative to ODK
Aggregate called ODK Route. I was wondering if there was a doc
written up describing the different POST and GET requests that Collect
uses to download and submit surveys.
Also, what kind of authentication is supported between the mobile app
and the server?