maproulette / maproulette/maproulette-backend
Challenge maintainance workflow
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 53
- Forks
- 39
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
I have been looking throught the UI and the API docs, but can't figure out how I am supposed to manage challenges. I have created a challenge and add tasks to it. Now I have to update this regularly to add new tasks when new problems in OSM appear. The easiest way would be to remove all tasks of this challenge from maproulette, re-create the whole task list excluding those tasks that were skipped by users. But I don't know how to get this information out of the API. Do I have to download all tasks through the API and look at the status field? Is that what the status field is used for. It contains a number, not a string or so, so I am not sure, what it means. (btw: I created unique identifiers, so I could do all that.) Or do I have to only upload any new tasks and leave the existing tasks in place?
How do other people manage this workflow?
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
Start with the UI and API documentation mentioned in the issue, then determine what the numeric task status values mean and which workflow preserves skipped tasks. Done means documenting whether existing tasks should be replaced or retained and how to retrieve the necessary task information through the API.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100