Difference between revisions of "2017 Corvallis GOC Meeting Agenda"

From GO Wiki
Jump to: navigation, search
(Attendees)
(Attendees)
Line 94: Line 94:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| N
 
| N
 
| N
 
| N
Line 100: Line 101:
 
| FlyBase
 
| FlyBase
 
| Y
 
| Y
|  
+
|
 +
|
 
| N
 
| N
 
| N
 
| N
Line 108: Line 110:
 
| Y
 
| Y
 
| Y
 
| Y
 +
| Y-1
 
| N
 
| N
 
| N
 
| N
Line 115: Line 118:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 121: Line 125:
 
| SGD
 
| SGD
 
| Y
 
| Y
|  
+
|
 +
|
 
| N
 
| N
 
| N
 
| N
Line 129: Line 134:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 136: Line 142:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 143: Line 150:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| N
 
| N
 
| N
 
| N
Line 150: Line 158:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 157: Line 166:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 164: Line 174:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 171: Line 182:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 178: Line 190:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 185: Line 198:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 192: Line 206:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 199: Line 214:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 206: Line 222:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 213: Line 230:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 220: Line 238:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 227: Line 246:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 234: Line 254:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 241: Line 262:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| N
 
| N
 
| N
 
| N
Line 248: Line 270:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 255: Line 278:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 262: Line 286:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 269: Line 294:
 
| Y
 
| Y
 
|  
 
|  
 +
|
 
| Y
 
| Y
 
| N
 
| N
Line 276: Line 302:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| Y
 
| Y
 
| Y
 
| Y
Line 283: Line 310:
 
| Y
 
| Y
 
| Y
 
| Y
 +
|
 
| Y
 
| Y
 
| Y
 
| Y

Revision as of 20:52, 26 April 2017

Day 1

9am Welcome, schedule and logistics


Overview/Plan for Upcoming Year

  • GO PIs presentation
  • This year's goals

Pipeline Migration

Seth & Chris 20 mins

New APIs

Seth & Chris 20 mins

TermGenie replacement

Chris 20 mins

Graph Store update

Eric 10 mins

GO and AGR

  • What does GO need to do for AGR?
  • Is there anything that GO curators should do any differently for this?

Introduction to Ontology Editing (David, Chris)

  • How are new terms added?

MF refactoring (Paul, David)

ECO

Mapping to classic GO evidence codes. The official mapping of IMP to ECO is not sufficiently broad. Should cover non-genetic perturbations (e.g. pharmacological).

GAFs and GPADs from Noctua models

  • Where do we stand?
  • Challenges with complex models (evidence)
  • All of PRO IDS should be available in Noctua (ids for human, pombe, etc); can these be loaded from PRO directly?

The fate of simple processes

The distinction between cellular processes and processes, do we need it?


Annotation QC issues

HTP papers

Pascale & Sylvain See notes /list of papers:


Modified protein binding

Pascale & Sylvain https://github.com/geneontology/go-ontology/issues/12787

Enrichment Analysis

Val & Seth

  • by default have the enrichment tool run directly on the GO annotation dataset
  • by default enable loading a background
  • currently missing a substantial number of annotations (e.g. fission yeast)


Contacts for Curation Groups

Pascale & David Some annotation groups are now gone (no longer annotating), therefore, can't dispute annotations and have no mechanism to update or change them, if needed. We need to have a mechanism for tracking the status better github go-annotation tracker for annotation disputes can we have some GOC superuser status in Protein2GO that allows GO curators to update annotations Some groups like JCVI, PAMGO no longer annotate - can GOC take control of these experimental annotations?

Attendees

Please add your name to the table if you intend to attend the meeting, the dinner, the Noctua workshop, and the Reactome workshop so we can get a headcount estimate. Thank you!

Name Organization Are you planning to attend the GOC meeting Are you planning to attend the GOC dinner Are you bringing a poster? how many? Are you planning to attend the Noctua workshop the day after the meeting, Sunday, June 4th? Are you planning to attend the Reactome workshop on Monday, June 5th?
Giulia Antonazzo FlyBase Y Y N N
Helen Attrill FlyBase Y N N
Judy Blake MGI Y Y Y-1 N N
Seth Carbon Berkeley/LBL Y Y Y
Mike Cherry SGD Y N N
Paul Thomas USC Y Y Y Y
Laurel Cooper Jaiswal Group/Oregon State Y Y Y
Stacia Engel SGD Y N N
Priyanka Garg Y Y Y
Parul Gupta Jaiswal Group/Oregon State Y Y Y
Tom Hayman RGD Y Y Y
Emily Heald SGD Y Y N
David Hill MGI Y Y N
Doug Howe Zfin Y Y N
Pankaj Jaiswal Reactome/Oregon State Y Y Y
Stan Laulederkind RGD Y Y Y N
Suzi Lewis Berkeley/LBL Y Y Y
Ruth Lovering UCL Y Y Y
Austin Meier Jaiswal Group/Oregon State Y Y N
Moni Munoz-Torres Berkeley/LBL Y Y N
Sushma Naithani Jaiswal Group/Oregon State Y Y Y
Darren Natale PRO Y N N
Sabrina Toro Zfin Y Y Y
Kimberly Van Auken WB Y Y Y Y
Edith Wong SGD Y Y N
Huaiyu Mi USC Y Y N
Chris Mungall LBL Y Y Y Y
Peter D'Eustachio Reactome Y Y Y Y
  • NOT ATTENDING: