Revision suggestion management workflow

People may suggest changes to our dataset. The instructions for this are here. Once someone has contacted us, we will assign an active coder to go through their suggestions, assess if it makes sense given our definitions and proceed to make changes and correspond with the expert as needed. This page outlines the workflow.

1. someone contacts us, via email or via GitHub issues
2. if the suggestion came in via email, a GitHub issue is started here regardless
3. a coder is assigned explicitly to the GitHub issue and in our to-do-lists (see tab "Revision from outside")
4. the assigned coder lets the submitter know we're on the case, either via GitHub issues or email
5. the assigned coder goes through all the suggestions, including checking if we have in fact already corrected the data-point
6. the assigned coder corresponds with the submitter, either via email or GitHub issues, as necessary
7. the assigned coder makes the final call on any changes to the data-points
8. if the submitter is correct, add them to the source column as "p.c." along with the published sources, and add their name to our acknowledgements
9. the assigned coder goes through our revision workflow for the changes
10. the assigned coder informs the submitter of the decisions and wraps up

For all coders in our project, keep in mind to be courteous and respectful of the time and effort of experts outside of our project, see more here.