Annotation Conf. Call 2018-03-27: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Agenda = == GOC Meeting, NYU, New York, NY, May 12-14th == *Reminder to register, and reserve your hotel room before April 6th if staying at the Shelburne NYC *[http://wiki...") |
No edit summary |
||
Line 8: | Line 8: | ||
*Dates set for Oct 17-20 | *Dates set for Oct 17-20 | ||
== | == HTP Annotation Guidelines == | ||
*Helen has added documentation on the use of HTP evidence codes to the wiki: | |||
**[http://wiki.geneontology.org/index.php/Guide_to_GO_Evidence_Codes Guide to GO Evidence Codes] | |||
== Annotation Review == | == Annotation Review == | ||
Line 35: | Line 38: | ||
*We'd like to assign these to groups | *We'd like to assign these to groups | ||
**[https://github.com/geneontology/go-annotation/issues/1326 Annotating yeast autophagy regulators in PMID:25660547 ?] | **[https://github.com/geneontology/go-annotation/issues/1326 Annotating yeast autophagy regulators in PMID:25660547 ?] | ||
= Minutes = | = Minutes = |
Revision as of 17:00, 12 March 2018
Agenda
GOC Meeting, NYU, New York, NY, May 12-14th
- Reminder to register, and reserve your hotel room before April 6th if staying at the Shelburne NYC
- Logistics
- Agenda
20th Anniversary GO Meeting, Montreal, CA
- Dates set for Oct 17-20
HTP Annotation Guidelines
- Helen has added documentation on the use of HTP evidence codes to the wiki:
Annotation Review
- Annotation review is being driven by annotation QC and ontology development
- Goal here is for correct and consistent annotation
- Prioritize by:
- Annotations that are incorrect
- Annotations to terms that are being made obsolete
- Annotations to high level terms that are not informative
- Annotations to grouping terms for which more granular, informative terms exist (maybe weren't found initially or were created after the annotation was made)
- Prioritize by:
- Tickets are created in the geneontology/go-annotation repo on github
- Currently, 55 open tickets labeled with Annotation Review in geneontology/go-annotation
- Tickets are assigned to representatives of the annotation groups that need to perform the review
- Once review is done, please remove yourself from the assignee list AND record the action in the accompanying Google spreadsheet linked from the github ticket
- Spreadsheet on GO Annotation Google drive with specific annotations, suggestions
- Need a re-review of palate development annotations.
- Tickets for discussion:
- HAMAP:MF_03064 mapping for Q9P6N6
- General issue here: when should we capture a causal relation?
- Review annotations to palate development
- HAMAP:MF_03064 mapping for Q9P6N6
- Some older tickets that still need to be addressed:
Annotation Requests
- There are some tickets in geneontology/go-annotation that are requesting annotation
- We'd like to assign these to groups
Minutes
- On call: