Hello everyone, My organization appears to be running into some dead ends when it comes to adding newer, more complex question flows for some upcoming 'modules' that we would like to include in some of our questionnaires. The particular pattern we're looking for is to account for the history of …

I never realized that ODK 2.0 even existed. Maybe this is something that we can consider, but it seems like adopting it is quite a rigorous undertaking. Is it possible to achieve what we need with 1.0?

I haven't yet went out to create a form in ODK 2.0's 'Survey', but I am not yet seeing a solution to this issue, though I could be missing something. I decided to post over in the JavaRosa group as well, with much more detail as to the specific kind of syntax / functionality we are looking for: h…

The key limitation of ODK 1.x is that it does not easily support updating of existing, already-collected, data. There are many work-arounds for this, but this is fundamental in its design. Others have written different servers that do support accepting revisions to existing submissions, and mec…

Hello Mitch, I'm really happy to see your reply! Thanks for taking the time to address my issue. We are actually quite keen at the idea of implementing ODK 2.0, for various reasons. However I am wondering if this does indeed address the use case that we are currently experiencing. Referencing e…

The big change with the ODK 2.0 tools is a switch to Javascript, abandoning XForms and the idiosyncrasies of the Javarosa library implementation of that standard. The ODK Survey tool uses a spreadsheet to define your survey, which is then compiled into a Javascript definition that is interpreted…

And it is possible to extend the javascript within ODK Survey (by adding your own prompt type) to save off a copy of your collected data at a given point within each loop of your survey. That would not requirewriting your own Javascript to extend the Javascript that handles all of the ODK Survey …

Hello Mitch, Thanks for all of your helpful feedback. It appears to me that in ODK 2.0, we may be able to achieve what we need by either (a) manipulating the javascript of the form client, or (b) having each instance of what would have been an ODK 1.0 repeat, be a different form instance which a…

Yes, this is how I would approach it, with a main survey about the respondent, then 3 tables for each of birth, termination and contraceptive histories, with the instanceID of the respondent survey stored as a pre-populated field (that you have defined) in each of those tables (so you can link t…

Thanks for that clarification, Mitch. That is interesting. That is so much different than ODK 1.0, I wasn't sure if I was on the right track. I'll discuss what I've learned with my organization. Hopefully ODK 2.0 can solve many of the difficult use cases we're experiencing. Thanks!

ODK Forum

ODK Collect: Updating other questions' variables, dynamic relevant/constraints, looping, etc

Development