maproulette / maproulette/maproulette-backend
Challenge identifier not used
Open
Nobody has claimed this yet.
admin
confirmed
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I had a challenge with lots of tasks and re-generated those tasks and uploaded again. Now I have them all twice. I would have expected Maproulette to understand the unique identifiers and do a de-duplication.
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
No files, tests, or entry points are named. Start by locating the challenge-task upload path and how challenge identifiers are handled, then reproduce uploading regenerated tasks. Done means repeated uploads recognize existing unique identifiers and do not create duplicate tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100