Improve section on changing form structure
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the linked forum conversation to understand the backend consequences of changing ODK Collect forms, then locate the existing documentation section covering form changes. Done means clearly explaining field renames and group/repeat structure changes, potentially in an FAQ format.
Written by the indexing model from the issue text.
Description
Some good ideas from this conversation: https://forum.getodk.org/t/backend-consequences-of-modifying-odk-collect-forms/56772
- Explicitly say that renaming a field is like deleting it and adding a new one
- Be explicit about changing group/repeat structure
Could be structured as a FAQ?
- Dominant language
- Python
- Stars
- 58
- Forks
- 161
- Avg merge
- 20h 51m
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getodk/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Central Collect
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Make it explicit that an S3 bucket configured for use with Central must accept abitrary connectionsOpenCentral
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
area:cli area:security enhancement priority:medium size:small
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RonaldHensbergen/composable-data-stack#1338 ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
almanac-data/climate-almanac#139 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UKGovernmentBEIS/inspect_ai#6695 · 1 comment ·
Maintainers usually reply within 1 day