additional checklist types in the editor
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] ENA Experiment (stakeholder: Peter)
- [ ] MorPhiC Experiment (stakeholder: Anu)
- [ ] Hierarchical checklists (stakeholder: EGA)
The first checklist is flat, so show me easy.
The other two have hierarchy. so the edit/create screen is more challenging.
Things to consider:
- Access control: editing/access by checklist type
- different json-schema format per checklist type
- how do we handle multi-tenancy? same db or different?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how the editor currently represents and creates the existing flat checklist, then compare that flow with the ENA Experiment, MorPhiC Experiment, and Hierarchical checklist requirements in the issue. Define the access-control, per-type JSON-schema, and multi-tenancy decisions before implementation; done means all three types have an agreed edit/create flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100