Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically Archive Projects that are 100% mapped and validated #6365

Open
SColchester opened this issue Apr 29, 2024 · 4 comments
Open

Automatically Archive Projects that are 100% mapped and validated #6365

SColchester opened this issue Apr 29, 2024 · 4 comments
Labels
data-quality Issues related to data quality and validation workflow priority: medium scope: backend scope: frontend status: todo type: feature request Adding functionality that currently does not exist

Comments

@SColchester
Copy link

Problem
Project creators are instructed to archive projects once they are 100% mapped and validated but they often don't archive their completed projects. This clutters the Tasking Manager with 'Published' projects which cannot be contributed to. Tasking Manager admins sink a lot of time into manually archiving these projects and following up with the project creators.

Solution
Once a project reaches 100% mapped and validated, automatically trigger an immediate status change for that project to shift from 'Published' -> 'Archived' - ideally with a message to the project creator to notify them.

Additional context
There is really no reason to keep a project which is 100% mapped and validated active as a 'Published' project, once projects are archived they can still be found and searched for by the public.

There is a large backlog of 100% mapped and validated projects which are not archived. If this change could also work to change the status of those (as well as newer projects that reach the 100% mark) this would be very valuable and a big time-saver.

@ramyaragupathy ramyaragupathy added scope: frontend scope: backend type: feature request Adding functionality that currently does not exist data-quality Issues related to data quality and validation workflow status: todo priority: medium labels May 1, 2024
@ramyaragupathy
Copy link
Member

@RAytoun's input: message project creator to do a third pass check for data quality before automatically archiving

@SColchester
Copy link
Author

Added this issue to Tasking Manager Project Gardening 2024 Wiki mentioning that if this issue is solved it will contribte to making the manual Gardening process redundant in the future - which would be great!

@anthaas
Copy link

anthaas commented Nov 7, 2024

Hi, this is really a great idea. It came to my attention that even if some tasks are marked as bad imagery, it is not considered in the overall completeness. So basically I can end up with 100% mapped and 100% validated but lots of tasks can be marked as bad imagery. In my experience usually I had to undo the bad imagery state and request to map those tiles again.
Would be great to consider a certain time frame between finishing the project and automatic archiving. Because if the last mapped task is marked and it triggers the archiving process immediately, I won’t be able to change the state of the bad imagery tiles.
Hope it makes sense.

@SColchester
Copy link
Author

Yeah totally @anthaas! I think that a way around this would be for it to only target projects where the total number of tasks = total number of validated tasks. So it's not looking for total mapped = total validated, because that would always archive projects that were validated apart from the bad imagery tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-quality Issues related to data quality and validation workflow priority: medium scope: backend scope: frontend status: todo type: feature request Adding functionality that currently does not exist
Projects
None yet
Development

No branches or pull requests

3 participants