Skip to content

Modify the Standard Validation Email Message to Empower Contributors to Obtain Feedback #7097

@Pseudorandom-Pseudonym

Description

@Pseudorandom-Pseudonym

Is your feature request related to a problem? Please describe.

Seldom do I see that validators provide feedback to mappers. This doesn't mean it does not happen, just that I rarely see it. Maybe only one general comment is provided but not on each task. Many validaotrs also just 'fix up' tasks themselves if they do not believe they'll be mapped better following invalidation.

It is time consuming and effortful to provide good feedack, but this has a big impact on user retention and actually educating/training contributors.

Currently the standard email you recieve when a task you marked as mapped was validated states the following "This is an automated message, the person who validated it hopefully shared some feedback with you." Yeah, hopefully they did, but if they didn't, what then?

A mapper may not recieve feedback on the tasks they submit, and perhaps the validator is unable to provide it. The mapper should be shown how to obtain feedback for themselves

Describe the solution you'd like

  • Alter the automated email to include instructions for how a contributor can obtain feedback for themselves.

This will teach contributors how they can potentially obtain feedback on any task of theirs which has been (in)validated, by viewing the contributions of others. If they use tools like OSMCha they can see a before and after of data, and they'll begin to understand changesets.

Describe alternatives you've considered

Adding such insrtructions in context buttons on the task history page. Perhaps if there were a TM tutorial this could be included.

Additional context

This may give some inspiration for how such a message may look

for feedback:

Sharing links to tasks in the HOT slack

etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions