CulverLab / CulverLab/sparcd-requirements
US-004 — Create collections and assign or change their owners
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 18h 56m
- Merged PRs (30d)
- 1
Description
## User story
> As an administrator, I want to create collections and assign or change their owners, so that responsibility remains accurate as people move in and out.
| Project field | Value |
|---|---|
| Rank | 4 |
| MoSCoW | Must have |
| Persona | Administrator |
| Wiki source | J2 |
## Planning notes
Agreed; a collection must never be left without a valid owner.
## Source
[SPARCd Personas & User Stories](https://github.com/CulverLab/sparcd-requirements/wiki/User-Stories)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no implementation files, tests, or entry points. Start by reading the linked SPARCd Personas & User Stories wiki page and the planning notes to clarify the collection and ownership requirements. Done is not defined beyond ensuring collections have valid owners, so the implementation scope and acceptance checks need to be established first.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100