Build out an MVP for annotation review for batch submissions to ClinVar

[larrybabb]

As discussed at the 10/13/2023 clinvar-curation meeting...

We need a process for identifying the annotations that we will be submitting to clinvar at some frequency (likely monthly). For now we are considering using the CvCuration QC & Statistics v3 google sheet and adding a new "Submission" tab.

The MVP requirements are:

• A method for knowing what annotations have already been submitted.
• A method for identifying the latest annotations that have not been submitted and selecting them for the batch to be submitted.
• A method for identifying which annotations DO vs DO NOT require review by a trained curator.
• When an annotation requires review the reviewer will be responsible for 'Fixing' the annotation if necessary. Whether or not the reviewer needs to fix the annotation or not they should be able to capture a note regarding their review of the annotation.
• A way to remove the annotation from the batch
• A way to easily see when an annotation in the batch (in any of these cases we would want to warn or prevent the batch from being submitted).
  • is not the most recent for that SCV,
  • the VCV has been modified since the annotation was made,
  • the SCV is outdated,
  • the SCV is deleted,
  • the SCV has moved to a new VCV

[larrybabb]

Update. All pilot feedback review data from initial batch submission has been collected and reformatted into the new Submission tab of the CvCuration QC & Statistics v3 sheet to validate how the data will be collected.