Annotation Review Request

From GO Wiki
Jump to navigation Jump to search

Annotation Review

Purpose

GO editors, GO Central (Quality assurance team), or users may request that annotations be reviewed. The reasons for requesting review vary, but typical reasons are:

  • Changes in the ontology that impact annotations
  • Changes in annotation guidelines
  • Poorly defined terms that lead to inconsistent annotations
  • Inconsistencies in annotations for a specific gene product

Procedure for requesting an Annotation Review using GitHub and GO's Google Drive

  1. Create a ticket in the Annotation repo: https://github.com/geneontology/go-annotation describing the issue
  2. Open the 'Template Annotation Review' file in the GO Google drive
  3. Make a copy
  4. Name of the file: Ticket-[nnnn] - Review annotations to [GO ID] [TermLabel]
  5. Download load the default data from AmiGO paste in the new Google document you have created in Step 3
  6. Whenever possible, add a suggested action (ie what term to replace by, etc) in the first column (A) of the spreadsheet
  7.  Make sure that the pull down menu in Column B is available for all rows of the spreadsheet; if not, copy/paste on additional rows
  8. Go back to the GitHub ticket and paste the link to the Google spreadsheet
  9.  Assign one person from each impacted group to review annotations (GitHub handle of the GO members are here: https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv)
  10.  Members will get a notification
  11.  When everyone has addressed the issue, change the Google document file name by adding 'DONE' in front of the name
  12. Close the ticket.

For curators: Procedure for addressing an Annotation Review

  1.  When notified that you have annotations to review, go to the GitHub ticket.
  2.  Click the link to the Google spreadsheet and review annotations. You should go back to the original paper and make sure you agree with any suggestion before editing your annotations.
  3.  Edit annotations as appropriate, and fill Columns B and C of the spreadsheet:
    • Column B: Changed/Removed/Checked (and unchanged)
    • Column C: your Git handle
  4.  If there are questions/disagreements with the suggestion, add these as comments in the GitHub ticket.
  5. When done, remove your name from the assignees of the ticket.

Proposal for Author Feedback for annotations

  • This is a proposal from 2015 - archive ??

Annotations removed as a result of Annotation QCs

  • This is an old attempt at metrics for reviewed annotations. Archive??


Back to: Annotation