maproulette / maproulette/maproulette-frontend

Tasks created with API cannot be rebuild (or at least error message fails to mention how)

Open
#2,392 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
167
Forks
39
Avg merge
16h 34m
Merged PRs (30d)
11

Description

Please Read First

  • If you are having issues creating your own Challenges, please make sure you carefully read the MapRoulette documentation, specifically the section about Creating and Managing Challenges. If that doesn't help you, please post to the OSM community forum with the hashtag #maproulette.
  • If you would like to report a Challenge you think is causing bad edits to OSM, please raise the issue with the Challenge owner first using the Get In Touch feature on the Challenge home page. If they fail to respond, please post to the OSM community forum with the hashtag #maproulette.
  • There is a separate repository for the MapRoulette back end. If your report pertains to the API / back end, please submit it there.

Thanks for helping us make MapRoulette great for everyone!

Describe the bug

My challenge created and edited via API got "This challenge was archived on January 26, 2024 because the tasks are more than 6 months old. You will need to rebuild the Tasks before you can unarchive the Challenge."

As it is not Overpass or Geojson based rebuilding challenge appears to be impossible.

Would it be possible to support unarchiving in such case? Or do I need to implement deletion/recreation of such challenges, to be performed every six months (would it kill ratings of people?).

Or maybe every six months I should dispose entire project, hide it and recreate tasks? With hope that no important "mark as false positive" were lost (I am actively monitoring those, but some would be lost on such resets)

Expected behavior
Please describe the expected behavior in clear language.

Message should explain what I should do in my case and instructions should be possible to follow.

To Reproduce
Steps to reproduce the behavior:

  1. Create challenge and populate it using API
  2. wait six months
  3. have challenge impossible to unarchive

Screenshots
If applicable, add screenshots to help explain your problem.

screen

https://maproulette.org/admin/project/53065/challenge/40102?filters.status=0%2C1%2C2%2C3%2C4%2C5%2C6%2C9&filters.reviewStatus=0%2C1%2C2%2C3%2C4%2C5%2C6%2C7%2C-1&filters.metaReviewStatus=0%2C1%2C2%2C3%2C5%2C6%2C7%2C-2&filters.priorities=0%2C1%2C2&sortCriteria.sortBy=name&sortCriteria.direction=DESC&pageSize=20&page=0&includeTags=false&boundingBox=-19.819335937500004%2C41.705728515237524%2C31.508789062500004%2C53.48804553605622

Desktop (please complete the following information):

  • OS: Lubuntu 20.04
  • Browser Firefox
  • Version 128

Additional context
Add any other context about the problem here.

Maybe I was not supposed to create challenge via API? And I was supposed to create geojson and import only that? In such case why API for task creation exists?

I checked https://github.com/maproulette/maproulette3/issues?q=is%3Aissue+This+challenge+was+archived

note to myself: once this is resolved, look again at https://codeberg.org/matkoniecz/improving_openstreetmap_using_alltheplaces_dataset/issues/8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the frontend entry point that renders the archived-challenge error message and trace how API-created challenges reach that state. Determine whether the frontend can support unarchiving or must explain an alternative; done means the reported case has a supported path or actionable instructions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.