avniproject / avniproject/avni-server
Metadata upload cannot be used to updae the existing records
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 22
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Right now for the user, catchment, and location upload, we don't respect the UUIDs and this causes issues when someone later wants to update the name of the location.
It might not be relevant for the user upload because Cognito doesn't allow the change in username. But this should be fixed for the location upload. Also there should be easy way to find out the UUIDs of the locations
Contributor guide
No contributing guide indexed for this repository
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
Trace the user, catchment, and location metadata-upload paths, focusing on how UUIDs are read and matched to existing records. Done means location uploads respect UUIDs so existing names can be updated, and users have an easy way to find location UUIDs; also determine whether the same behavior applies to user uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100