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

Redefine Mapper Level Milestones #3713

Open
russdeffner opened this issue Oct 13, 2020 · 3 comments
Open

Redefine Mapper Level Milestones #3713

russdeffner opened this issue Oct 13, 2020 · 3 comments
Labels
data-quality Issues related to data quality and validation workflow priority: medium

Comments

@russdeffner
Copy link

Currently Mapper Levels are defined as:

  • Beginner <250 changesets
  • Intermediate >=250<500 changesets
  • Advanced 500+ changesets

When vetting mappers requesting to become part of a validation team, we often find mappers with 500+ changesets that have mapped <1000 buildings and few of any other features. Obviously not what any experienced mapper would call "advanced". Therefore, I suggest we redefine these levels, if we cannot move towards a more sophisticated equation like X buildings, Y roads and Z 'other ways and POIs' then we should simply increase these numbers. I suggest doubling them to 500 and 1000 changeset milestones.

Moving towards the more sophisticated method of determining experience I think we could look towards the work done for the badges on the Missing Maps User Profiles http://www.missingmaps.org/users/#/ that has many different 'experience' types including things like participating in mapathons as a way to earn 'credit'/badges. Maybe we would need to simplify this to get us back to a 'beginner, intermediate, advanced' levels but as mentioned in #2907 - the current method is probably not good enough for our needs going forward.

@russdeffner
Copy link
Author

Another option discussed in the Activation Working Group was to leave intermediate at 250 and increase advanced to 750. This would have less disturbance on existing mappers (i.e. no one would 'return' to beginner).

@aawiseman
Copy link

aawiseman commented Nov 3, 2022

Hi all, the Quality Control Working Group would like to prioritize this one

@ramyaragupathy ramyaragupathy added the data-quality Issues related to data quality and validation workflow label Nov 8, 2022
@petya-kangalova
Copy link
Collaborator

Hi all. Linking to a research paper looking at The Role of Volunteer Experience on Performance on Online Volunteering Platforms and specifically HOTOSM Tasking Manager. It might be of interest and relevance specifically to redefining the mapper level milestones.

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
Projects
No open projects
Status: Needs discussion
Development

No branches or pull requests

6 participants