CulverLab / CulverLab/sparcd-requirements
US-009 — Retry a failed upload to the same destination
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 18h 56m
- Merged PRs (30d)
- 1
Description
## User story
> As a species identifier, I want to retry a failed upload to the same destination, so that I do not create duplicate or misplaced uploads.
| Project field | Value |
|---|---|
| Rank | 9 |
| MoSCoW | Must have |
| Persona | Species identifier |
| Wiki source | AL2 |
## Planning notes
Agreed; wiki says partial. A successful retry must leave one complete upload and no inaccessible partial copy.
## 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
Start with the US-009 user story and its linked SPARCd Personas & User Stories wiki source. Clarify the failed-upload and retry lifecycle, including the requirement for one complete upload and no inaccessible partial copy; done criteria are not yet defined beyond that planning note.
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
- 25/100