I am currently working on migrating the ODK 2.0 documentation into Sphynx and bringing it in line with the rest of the ODK documentation. This includes bringing over all the existing ODK 2.0 documentation (both on the website and the wiki) as well as adding some more content to ease the learning curve for new users. Some example improvements include intro pages for the tools and for the suite as a whole, new tutorials, and documentation for the example apps.
On the most recent ODK 2.0 developer call I asked for feedback on the current documentation and for community requests going forward. I wanted to repeat that request here for anyone who couldn’t make the call. Please post any feelings you have about the current documentation: likes, dislikes, missing elements, inaccuracies, frustrations, cool ideas, etc. I want to hear about your experiences. And if you have any materials you want to share I’d love to include them.
This past summer we did a two-day training on ODK 2.0 and wanted to share the materials here. I am going to share them in two batches. This first batch is a series of slides for workflow and setup in ODK 2.0. We have a second batch of materials forthcoming of hands-on exercises (and excel “solutions”!) in programming the survey, but we gave the training in rev208 so the team is chipping away at updating those to rev218. Stay tuned!
One caveat:
We did this training with ODK rev208 tools. We tried to update to the current links for current downloads, but may have missed some, so please make sure you go to the latest versions of all of the directions/downloads.
Also, if you find any errors, please note them, or even better, if you want to do revised, improved versions, go for it!
Finished revising the second batch of ODK 2.0 materials from our training. This includes a series of hands on exercises in the slides with learning programming in ODK, so I am including here both the slides and the “solutions” to the exercises. These go AFTER the first set of slides in my earlier post.
The materials cover the basics of setting up your first form (08), the basics of workbook structure including different types of questions, skip patterns, grouping questions, etc. (09) and more advances aspects of workbook structure, such as calculations/assigning variables, calling on csvs for long/multi-level lists, adding sub-forms, preloading data, constraints, and language settings (10).
As mentioned previously, we did these initially in rev208 for the training, and just revised to rev218, so let me know if we missed any changes or if you find any bugs!
Thanks to everyone for all the great work getting the ODK"2" docs up and going!
We’ve been working away on some additions and edits to the docs. Alas, editing them directly was beyond our tech skills, but we followed a suggestion to copy existing docs and then track changes in Word. So hopefully someone with better tech skills than ours can review these and integrate into docs! We tried to follow the style guide, but please let us know if we made any errors so we can do better next time
Here are the three installments we’ve finished so far:
Thanks @elmps2018, Caitlyn, and Maddy! This is great! Your contributions to the docs have been and continue to be invaluable to the community.
I am currently trying to think of the best way to create tasks for this. I’ll probably create some Github issues and link to your post. I will take care of some of the transcription, and hopefully recruit some more volunteers. I’ll update this thread when they are complete.
thank you very much @elmps2018 for the tutorials…they are much more easier to understand than the official documentation.
One quick question, how would i make a follow up form, e.g i have registered farmers using one form and then i would like to create a form that tracks their attendance to trainings that are offered to them on a monthly basis?
@david_odongo, you can do this with sub-forms, or having another form that writes to the same table. Here’s an example that does this: Hope Demo — ODK-X Docs
Hopefully from this example you can see how to do follow up.
