Add notes about "new entity list, old form" scenario

Open Beginner friendly
#2,112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start by reading the linked Collect discussion and locate the existing documentation for entity lists and forms. Add notes explaining the new-entity-list/old-form scenario and what users should consider; done when this behavior and its implications are clear in the relevant docs.

Written by the indexing model from the issue text.

Description

Central Collect

As mentioned here, it's possible to end up in a scenario where Collect has the latest existing version of the entity list but out of date forms. Entities are designed to work this way: the list only has one existing "version" and is not bound to any particular form's structure.

We should document this as something for user's to think about.

Dominant language
Python
Stars
58
Forks
161
Avg merge
20h 51m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/docs

All issues in getodk/docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.