Annotation Review Request: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Purpose) |
||
Line 1: | Line 1: | ||
= Annotation Review = | = Annotation Review = | ||
== Purpose== | == Purpose== | ||
GO editors, GO Central (Quality assurance team), or users may request that annotations be reviewed. The reasons for requesting review vary, but | GO editors, GO Central (Quality assurance team), or users may request that annotations be reviewed. The reasons for requesting review vary, but include: | ||
* Changes in the ontology that impact annotations | * Changes in the ontology that impact annotations | ||
* Changes in annotation guidelines | * Changes in annotation guidelines | ||
* Poorly defined terms that lead to inconsistent annotations | * Poorly defined terms that lead to inconsistent annotations | ||
* Inconsistencies in annotations for a specific gene product | * Inconsistencies in annotations for a specific gene product | ||
== Procedure for requesting an Annotation Review using GitHub and GO's Google Drive == | == Procedure for requesting an Annotation Review using GitHub and GO's Google Drive == |
Revision as of 08:48, 10 August 2018
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 include:
- 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
- Create a ticket in the Annotation repo: https://github.com/geneontology/go-annotation describing the issue
- Open the 'Template Annotation Review' file in the GO Google drive
- Make a copy
- Name of the file: Ticket-[nnnn] - Review annotations to [GO ID] [TermLabel]
- Download load the default data from AmiGO paste in the new Google document you have created in Step 3
- Whenever possible, add a suggested action (ie what term to replace by, etc) in the first column (A) of the spreadsheet
- 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
- Go back to the GitHub ticket and paste the link to the Google spreadsheet
- 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)
- Members will get a notification
- When everyone has addressed the issue, change the Google document file name by adding 'DONE' in front of the name
- Close the ticket.
For curators: Procedure for addressing an Annotation Review
- When notified that you have annotations to review, go to the GitHub ticket.
- 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.
- 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
- If there are questions/disagreements with the suggestion, add these as comments in the GitHub ticket.
- When done, remove your name from the assignees of the ticket.
Back to: Annotation