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

HOT Global Validators Team added by default to new projects when validation restricted to teams #6628

Open
SColchester opened this issue Nov 12, 2024 · 4 comments
Assignees
Labels
data-quality Issues related to data quality and validation workflow type: feature request Adding functionality that currently does not exist

Comments

@SColchester
Copy link

SColchester commented Nov 12, 2024

Problem
There are lots of projects that make very slow progress / get stuck with validation because the project creator restricts validation to teams and then assigns only a small and inactive team of validators to validate the project. Project creators do not necessarily know that they can add any team to validate a project and they may also not be aware that the 'HOT Global Validators' team is an excellent group of very active validators.

Solution
To ensure that more projects are available to validate by the HOT Global Validators team --> For any project in Tasking Manager, under the 'Permissions' section of the edit project page, if the project editor switches 'Validation' permissions to 'Only team members' (from the default of 'Only users with intermediate or advanced level') automatically populate 'HOT Global Validators' as a validation team.

Only do this once, the first time that the project editor changes validation permissions to 'Only team members'. This way the project creator can add additional teams, or if they like, opt-out by manually removing the HOT Global Validator team.

2024-11-12 11_07_19-Edit project #17928 - HOT Tasking Manager — Mozilla Firefox

Alternatives
An alternative could be to add a fifth radio button under the 'Validation permissions' section which specifically calls out the HOT Global Validator Team, so could be an option for example stating: 'Only HOT validators'.

@ramyaragupathy ramyaragupathy added the data-quality Issues related to data quality and validation workflow label Nov 13, 2024
@ramyaragupathy
Copy link
Member

@SColchester - thanks for bringing this up. @manjitapandey and I will verify the existing behaviour before we lock in a workflow.

cc @royallsilwallz

@manjitapandey manjitapandey added the type: feature request Adding functionality that currently does not exist label Nov 14, 2024
@martien-176
Copy link

I support the idea.

I think it would be helpful if there is some additional description of what the Global Validator team is about. Project creators could not be aware of the value of the Globals. And "unkown, unloved" could cause them to skip the Globals if they can.

@ramyaragupathy
Copy link
Member

@SColchester @martien-176 - we should go with the existing options as such and populate HOT Global validators when project manager chooses to restrict validation to only team members. Maintaining design consistency will be useful, so let's not go with an additional radio button for validation permissions.

Should we apply the same behaviour to only intermediate and advanced team members?

The information about the team could pop up on hover or with an info icon like how we have stats source mentioned. What do you think @emi420 @royallsilwallz ?

cc @manjitapandey

@SColchester
Copy link
Author

SColchester commented Nov 20, 2024

@ramyaragupathy Agree, not adding a radio button will be better, and yes - well spotted, for completeness it should automatically populate the HOT Global Validators team if either only team members or only intermediate and advanced team members is selected.

I like the pop up on hover option for more info on the team, and would be ideal if this could be pulled directly from the team's description field. This is what that field looks like on the team 'manage' page.

Image

@royallsilwallz royallsilwallz self-assigned this Nov 25, 2024
royallsilwallz added a commit to naxa-developers/tasking-manager that referenced this issue Dec 18, 2024
…ermissions

- Validation Permissions includes `Only team members` & `Only intermediate and advanced team members`
- Related to hotosm#6628
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 type: feature request Adding functionality that currently does not exist
Projects
None yet
Development

No branches or pull requests

5 participants