formList?

Hi folks. In building my own aggregator, I'm trying to mimic the
output of something like: http://opendatakit.appspot.com/formList,
which replies with:

New Widgets Miramare Birds Geo Tagger v2

I've tried even echoing that back verbatim in my app, but Collect is
not reading it properly when I 'Get New Forms'. I get only the last
item in the list, and its ID is given as null.

What could be causing this?

I've looked at the response headers. They only difference seems to be
that appspot is gzipping its responses and I'm not. But not doing that
that shouldn't ruin everything!?

Ideas?

Thanks.

Hi Thomas,

You should look at https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI

The community is trying to standardize on a new set of APIs for the
interactions between the phone and the webserver.

These new APIs are built into Aggregate 1.0 Beta and Collect 1.1.7.
To be backward compatible with 1.1.5, Aggregate relies on the client
sending the X-OpenRosa-Version header ( see
https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest ) whenever the
client is using these new APIs. If that isn't present, Aggregate will fall
back to the older Collect 1.1.5 and earlier APIs (and send responses
appropriate for those).

Also, to see the current development tip for Aggregate 1.0 Beta, you will
want to look at the uiexperiment branch.
(
http://code.google.com/p/opendatakit/source/list?repo=aggregate&name=uiexperiment)
It has the beta release code.

Mitch

··· On Thu, Jun 30, 2011 at 11:57 AM, Thomas Smyth wrote:

Hi folks. In building my own aggregator, I'm trying to mimic the
output of something like: http://opendatakit.appspot.com/formList,
which replies with:

New Widgets Miramare Birds Geo Tagger v2

I've tried even echoing that back verbatim in my app, but Collect is
not reading it properly when I 'Get New Forms'. I get only the last
item in the list, and its ID is given as null.

What could be causing this?

I've looked at the response headers. They only difference seems to be
that appspot is gzipping its responses and I'm not. But not doing that
that shouldn't ruin everything!?

Ideas?

Thanks.

--
Mitch Sundt
Software Engineer


University of Washington
mitchellsundt@gmail.com

Thomas:

for the benefit of the community, could you also explain the system
design issues that are making you build a new aggregator? It would
just be good for everyone to know why certain things are happening -
you never know, there might be someone else with the same needs.

Thanks,
Gaetano

··· On Thu, Jun 30, 2011 at 12:07 PM, Mitch Sundt wrote: > Hi Thomas, > > You should look at https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI > > The community is trying to standardize on a new set of APIs for the > interactions between the phone and the webserver. > > These new APIs are built into Aggregate 1.0 Beta and Collect 1.1.7. > To be backward compatible with 1.1.5, Aggregate relies on the client > sending the X-OpenRosa-Version header ( see > https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest ) whenever the > client is using these new APIs. If that isn't present, Aggregate will fall > back to the older Collect 1.1.5 and earlier APIs (and send responses > appropriate for those). > > Also, to see the current development tip for Aggregate 1.0 Beta, you will > want to look at the uiexperiment branch. > ( > http://code.google.com/p/opendatakit/source/list?repo=aggregate&name=uiexperiment > ) > It has the beta release code. > > Mitch > > On Thu, Jun 30, 2011 at 11:57 AM, Thomas Smyth wrote: >> >> Hi folks. In building my own aggregator, I'm trying to mimic the >> output of something like: http://opendatakit.appspot.com/formList, >> which replies with: >> >> >> New >> Widgets >> > url="http://opendatakit.appspot.com/formXml?formId=Miramare">Miramare >> > url="http://opendatakit.appspot.com/formXml?formId=Birds">Birds >> > url="http://opendatakit.appspot.com/formXml?formId=geo_tagger_v2">Geo >> Tagger v2 >> >> >> I've tried even echoing that back verbatim in my app, but Collect is >> not reading it properly when I 'Get New Forms'. I get only the last >> item in the list, and its ID is given as null. >> >> What could be causing this? >> >> I've looked at the response headers. They only difference seems to be >> that appspot is gzipping its responses and I'm not. But not doing that >> that shouldn't ruin everything!? >> >> Ideas? >> >> Thanks. > > > > -- > Mitch Sundt > Software Engineer > http://www.OpenDataKit.org > University of Washington > mitchellsundt@gmail.com >

Thanks Mitch, that fixed everything.

··· On 30 June 2011 15:07, Mitch Sundt wrote: > Hi Thomas, > > You should look at https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI > > The community is trying to standardize on a new set of APIs for the > interactions between the phone and the webserver. > > These new APIs are built into Aggregate 1.0 Beta and Collect 1.1.7. > To be backward compatible with 1.1.5, Aggregate relies on the client > sending the X-OpenRosa-Version header ( see > https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest ) whenever the > client is using these new APIs. If that isn't present, Aggregate will fall > back to the older Collect 1.1.5 and earlier APIs (and send responses > appropriate for those). > > Also, to see the current development tip for Aggregate 1.0 Beta, you will > want to look at the uiexperiment branch. > ( > http://code.google.com/p/opendatakit/source/list?repo=aggregate&name=uiexperiment > ) > It has the beta release code. > > Mitch > > On Thu, Jun 30, 2011 at 11:57 AM, Thomas Smyth wrote: >> >> Hi folks. In building my own aggregator, I'm trying to mimic the >> output of something like: http://opendatakit.appspot.com/formList, >> which replies with: >> >> >> New >> Widgets >> > url="http://opendatakit.appspot.com/formXml?formId=Miramare">Miramare >> > url="http://opendatakit.appspot.com/formXml?formId=Birds">Birds >> > url="http://opendatakit.appspot.com/formXml?formId=geo_tagger_v2">Geo >> Tagger v2 >> >> >> I've tried even echoing that back verbatim in my app, but Collect is >> not reading it properly when I 'Get New Forms'. I get only the last >> item in the list, and its ID is given as null. >> >> What could be causing this? >> >> I've looked at the response headers. They only difference seems to be >> that appspot is gzipping its responses and I'm not. But not doing that >> that shouldn't ruin everything!? >> >> Ideas? >> >> Thanks. > > > > -- > Mitch Sundt > Software Engineer > http://www.OpenDataKit.org > University of Washington > mitchellsundt@gmail.com >

Sure. This work is for the Carter Center and is part of a larger
system for elections monitoring that involves other collection
modalities than just ODK (such as longer format reports composed
offline with a laptop, and maybe manually encoded sms reports using
cheapo phones). I wanted to bring things like authentication,
geocoding, and look/feel/user experience all under one roof and in one
database so that's why I'm doing a custom aggregator and form builder.

··· On 30 June 2011 16:37, Gaetano Borriello wrote: > Thomas: > > for the benefit of the community, could you also explain the system > design issues that are making you build a new aggregator? It would > just be good for everyone to know why certain things are happening - > you never know, there might be someone else with the same needs. > > Thanks, > Gaetano > > > > On Thu, Jun 30, 2011 at 12:07 PM, Mitch Sundt wrote: >> Hi Thomas, >> >> You should look at https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI >> >> The community is trying to standardize on a new set of APIs for the >> interactions between the phone and the webserver. >> >> These new APIs are built into Aggregate 1.0 Beta and Collect 1.1.7. >> To be backward compatible with 1.1.5, Aggregate relies on the client >> sending the X-OpenRosa-Version header ( see >> https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest ) whenever the >> client is using these new APIs. If that isn't present, Aggregate will fall >> back to the older Collect 1.1.5 and earlier APIs (and send responses >> appropriate for those). >> >> Also, to see the current development tip for Aggregate 1.0 Beta, you will >> want to look at the uiexperiment branch. >> ( >> http://code.google.com/p/opendatakit/source/list?repo=aggregate&name=uiexperiment >> ) >> It has the beta release code. >> >> Mitch >> >> On Thu, Jun 30, 2011 at 11:57 AM, Thomas Smyth wrote: >>> >>> Hi folks. In building my own aggregator, I'm trying to mimic the >>> output of something like: http://opendatakit.appspot.com/formList, >>> which replies with: >>> >>> >>> New >>> Widgets >>> >> url="http://opendatakit.appspot.com/formXml?formId=Miramare">Miramare >>> >> url="http://opendatakit.appspot.com/formXml?formId=Birds">Birds >>> >> url="http://opendatakit.appspot.com/formXml?formId=geo_tagger_v2">Geo >>> Tagger v2 >>> >>> >>> I've tried even echoing that back verbatim in my app, but Collect is >>> not reading it properly when I 'Get New Forms'. I get only the last >>> item in the list, and its ID is given as null. >>> >>> What could be causing this? >>> >>> I've looked at the response headers. They only difference seems to be >>> that appspot is gzipping its responses and I'm not. But not doing that >>> that shouldn't ruin everything!? >>> >>> Ideas? >>> >>> Thanks. >> >> >> >> -- >> Mitch Sundt >> Software Engineer >> http://www.OpenDataKit.org >> University of Washington >> mitchellsundt@gmail.com >> >

Hi Thomas,

If you're using Django there are a couple of projects that might help.


Andrew

··· On Thu, Jun 30, 2011 at 5:01 PM, Thomas Smyth wrote: > Sure. This work is for the Carter Center and is part of a larger > system for elections monitoring that involves other collection > modalities than just ODK (such as longer format reports composed > offline with a laptop, and maybe manually encoded sms reports using > cheapo phones). I wanted to bring things like authentication, > geocoding, and look/feel/user experience all under one roof and in one > database so that's why I'm doing a custom aggregator and form builder. > > > On 30 June 2011 16:37, Gaetano Borriello wrote: >> Thomas: >> >> for the benefit of the community, could you also explain the system >> design issues that are making you build a new aggregator? It would >> just be good for everyone to know why certain things are happening - >> you never know, there might be someone else with the same needs. >> >> Thanks, >> Gaetano >> >> >> >> On Thu, Jun 30, 2011 at 12:07 PM, Mitch Sundt wrote: >>> Hi Thomas, >>> >>> You should look at https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaAPI >>> >>> The community is trying to standardize on a new set of APIs for the >>> interactions between the phone and the webserver. >>> >>> These new APIs are built into Aggregate 1.0 Beta and Collect 1.1.7. >>> To be backward compatible with 1.1.5, Aggregate relies on the client >>> sending the X-OpenRosa-Version header ( see >>> https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaRequest ) whenever the >>> client is using these new APIs. If that isn't present, Aggregate will fall >>> back to the older Collect 1.1.5 and earlier APIs (and send responses >>> appropriate for those). >>> >>> Also, to see the current development tip for Aggregate 1.0 Beta, you will >>> want to look at the uiexperiment branch. >>> ( >>> http://code.google.com/p/opendatakit/source/list?repo=aggregate&name=uiexperiment >>> ) >>> It has the beta release code. >>> >>> Mitch >>> >>> On Thu, Jun 30, 2011 at 11:57 AM, Thomas Smyth wrote: >>>> >>>> Hi folks. In building my own aggregator, I'm trying to mimic the >>>> output of something like: http://opendatakit.appspot.com/formList, >>>> which replies with: >>>> >>>> >>>> New >>>> Widgets >>>> >>> url="http://opendatakit.appspot.com/formXml?formId=Miramare">Miramare >>>> >>> url="http://opendatakit.appspot.com/formXml?formId=Birds">Birds >>>> >>> url="http://opendatakit.appspot.com/formXml?formId=geo_tagger_v2">Geo >>>> Tagger v2 >>>> >>>> >>>> I've tried even echoing that back verbatim in my app, but Collect is >>>> not reading it properly when I 'Get New Forms'. I get only the last >>>> item in the list, and its ID is given as null. >>>> >>>> What could be causing this? >>>> >>>> I've looked at the response headers. They only difference seems to be >>>> that appspot is gzipping its responses and I'm not. But not doing that >>>> that shouldn't ruin everything!? >>>> >>>> Ideas? >>>> >>>> Thanks. >>> >>> >>> >>> -- >>> Mitch Sundt >>> Software Engineer >>> http://www.OpenDataKit.org >>> University of Washington >>> mitchellsundt@gmail.com >>> >> >