Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XLSForm questionaire should come after building validation questions #1697

Closed
spwoodcock opened this issue Jul 23, 2024 · 0 comments · Fixed by #1721
Closed

XLSForm questionaire should come after building validation questions #1697

spwoodcock opened this issue Jul 23, 2024 · 0 comments · Fixed by #1721
Labels
dependency:osm-fieldwork Requires updates in osm-fieldwork effort:low Likely a few hours enhancement New feature or request priority:high Should be addressed as a priority

Comments

@spwoodcock
Copy link
Member

Describe the issue

  • In the field we discovered that users would often go to a building, then speak to the owner first to ask for permission to collect data.
  • As the building validation questions come first, they would resort to noting down the owners answers on another app, before going back to ODK Collect!
  • The question order should be rethought to be most intuitive for the user.

Proposed solution

  • The validation / digitization_correct was placed at the top so the fields could easily be hidden, to allow the user to edit below.
  • This should be moved below the questions instead.
  • They should still be hidden.

Additional context

  • How do we best prevent the user overwriting the validation fields?
  • We need the validation section to carry out conflation.
  • The building selection will be handled by the custom ODK Collect version / load by intent feature, so this isn't an issue.

@ramyaragupathy as discussed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency:osm-fieldwork Requires updates in osm-fieldwork effort:low Likely a few hours enhancement New feature or request priority:high Should be addressed as a priority
Projects
Development

Successfully merging a pull request may close this issue.

1 participant