I have a need to persist data collected via ODK Collect in a permanent searchable repository. Searchable = categorizing and tagging the data and later allowing for filtering, sorting etc. on a front-end. I've been considering Drupal (since we use Drupal for other content in the organization already). I understand I can do this custom with the Central and Drupal APIs and Drupal modules. Wondering if there's anyone with experience, learnings with this integration that they can share or point me to.
I've seen this old post (10+ years) already.
Thank you!
For everyone's benefit, here is the complete workflow we are attempting to do. Given the complexity of the forms and the usage environment, this is a challenging project; I will of course share how this went when we are done!
- ODK Collect users from the field submit data to Central
- With pyODK, export the data from Central and push into Drupal content types via Drupal's APIs. This will be a scheduled automated backend job.
- ODK collect user logs in to Drupal and updates certain open-ended questions with long text on a Desktop computer (these are questions with descriptive responses that are hard to type in to the ODK Collect mobile form screen, the users instead note their detailed observations as audio in Collect, and manually input the long form response using the audio recording for input). Then submits the data in Drupal. This and the rest of the below workflow happens within Drupal.
- Backend team reviews the data and "sends" the data back to the submitter for corrections if any with suitable comments.
- Submitter logs in to Drupal, corrects/updates the data in Drupal, and resubmits
- Summary reports, content discovery, drilldown etc happens within Drupal by Backoffice users.
Note: We cannot auto-transcribe the user's voice because Google transcribe or any other are quite poor with semi-urban, rural accents. This is in India, multiple Indian languages.
