Set up a review process for new data with goal to have review pre-merge

[Lnaden]

A review process needs to be established for data.

One process, proposed at the onset of the project was to just merge all data as it came in, and give it a color coded system to indicate review. It has been pointed out that this will likely lead to chaos and be hard to maintain.

Another process suggested was to have data be reviewed before it ever gets merged and I think this is what should be done. The pipeline would be like this:

• Contributing person accumulates all data they wish to submit and open a PR with their own assessment of the quality of the data.
• That assessment is reviewed by the curation team for that type of data
• Adjustments are made / discussed in PR
• Quality is assessed and noted in the PR
• Merged

cc @Andrew-AbiMansour @sjayellis @jchodera

[sjayellis]

I second that a pre-merge review process would be a better strategy. This allows all discussion about the data and its quality to be tied to a PR. The PR can also be used as a reference point for issues made, which may be a possibility for further discussion about the data quality after it has been merged.