rdmorganiser / rdmorganiser/rdmo
Changes of Catalog in a project
Open
Nobody has claimed this yet.
effort:minor
priority:high
type:feature-request
- Dominant language
- Python
- Stars
- 133
- Forks
- 60
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 21
Description
If the questionnaire is changed for an active project, the stored information is presented with the new questionnaire
- in snapshots
- in xml exports
If one wants to preserve both together, this should be offered as an option (e.g.: as a complete export)
Contributor 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.
Research direction
Start by tracing how active projects produce snapshots and XML exports, as identified in the issue. Determine how questionnaire changes affect stored information and define what a complete export must preserve; done when an option can retain both the previous and current questionnaire data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100