Open florianm opened 4 years ago
Related to this theme of cleaning, I've been wondering whether it might be possible/in scope to use the upcoming submission review features to automatically flag records with possible issues. I'm imagining something like defining data constraints and for any submission/row that violates them, calling home to Central to set the review status to "Has Issues" with the constraint violation text as the note. I describe this with surface understanding of ruODK
so please don't take the suggestion literally but hopefully it helps illustrate the concept! Broadly, I'm interested in ways that users can automatically flag suspicious submissions. Happy to move the conversation somewhere else more appropriate if this is not feeling like the right place!
Oh that's a great idea, thanks for the suggestion! I could imagine this as a worked example in a vignette. There could be an angle of "turn data validation errors into suggestions for form validation".
The use cases in which my users want to update records are:
In my own use case, all data from ODK are imported into a data warehouse (Django), where we audit all QA operations (edits - django-revision) and decisions (quality levels - django-fsm). That's of course the most heavyweight implementation.
For a light-weight implementation purely in ODK Central / R / ruODK, I could imagine:
This outsources all validation logic to pointblank, and focuses ruODK on the use case "mark this list of records as Has Issues".
That sounds really great, @florianm! Thanks for the outline. Would be amazing to make some of these a reality. I'll see if I can help make that happen.
Stu Norris suggested to use Microsoft 365 R package to notify enumerators via email on data quality issues.
Feature
From the ODK Forum vignette "u r ODK, now what"
Fun things to do with ODK data via ruODK downstream: