Difference between revisions of "2017 Cambridge GOC Meeting Agenda"

From GO Wiki
Jump to: navigation, search
(WHY creating slims - Intro to slim philosophy (Val, Suzi))
(WHY creating slims - Intro to slim philosophy (Val, Suzi))
Line 149: Line 149:
====WHY creating slims - Intro to slim philosophy (Val, Suzi)====
====WHY creating slims - Intro to slim philosophy (Mary,Val, Suzi)====
Judy, Mary D (+ Suzi, Val, etc). For overviews, for particular taxa, for a particular area of biology
Judy, Mary D (+ Suzi, Val, etc). For overviews, for particular taxa, for a particular area of biology

Revision as of 11:02, 28 September 2017

GOC Meeting, Cambridge , October 2-4, 2017


To all speakers

Please add your slides to the google drive: https://drive.google.com/drive/folders/0B7bEr6HANSlGSHY3c2JqNEs2ZUk

Monday 2nd October

Welcome, overview, vision, introductions


GO handbook presentation

The Gene Ontology and the meaning of biological function (Paul T)

Translating research data into Gene Ontology annotations (Pascale)

(includes a discussion of the issue: background knowledge & protein domains https://github.com/geneontology/go-annotation/issues/1621)

Gene Ontology - annotation extensions (Ruth)

GO as a biological systems model (Suzi)

Suzi, or Paul T if Suzi is late

Ontology Issues and Updates

Update on MF refactoring (Pascale or Paul T)

Qualifiers/Relation issues (Kimberly and Chris)

Qualifiers/Relations in GPAD (Kimberly and Chris)

Contributes_to guidelines (Kimberly)

++ colocalizes with

CC component annotation guidelines (Kimberly)

CC component annotation: what does it mean ? Kimberly to do 1 proposal (out of 3 alternatives) 1. where the protein is active 2. two different meanings: enables or the right RO (part:of, ie just found there) 3. part_of (low information value!)

Multiple qualifiers for an annotation (Huaiyu)

Use of Qualifiers in Legacy Annotations (Pascale)

Proposal: We will apply the general qualifier to all legacy annotations. Each group can provide more specific qualifiers if they have a mechanism to distinguish.

Regulates relations (Kimberly)

Adding new qualifiers for the relation between a gene/gene product and a GO term.

  • Corvallis discussion:* What should the default relation be? How will we handle regulation? Use a relation, involved in regulation of, or use the precomposed regulation term?

Ruth: There are now 3 ways to say the same thing: - involved_in_regulation_of X - involved_in X regulation - involved_in BP regulates(X) For annotation purposes and for our users we want one. DOS: Good point. These are semantically identical, but I agree we need to find a way to only have one: by convention for classic GO annotation and by filtering the output of inference for noctua output. Proposal: If a named regulation class exists: involved_in X regulation ...if not: involved_in {some BP} regulates(X) NOTE: If there was an annotation in Noctua such as ‘regulation of’ ‘very specific term’ and there was no term as ‘regulation of very specific term’ the GOC pipeline would create the annotation to the parent term: ‘regulation of less specific term’. Q: Is this implemented ?

Annotation guidelines and issues (part one)

Signaling (Kimberly and David)

  • Report from signaling workshop: David /Kimberly
  • Signaling: First attempt at Annotation consistency 2.0 - Kimberly to report on the approach and the outcome.

Discussion points: Limited participation (self-selected to participate). One recommendation may be to ask all active curators to participate, even at some low level https://github.com/orgs/geneontology/projects/

Overview of GO annotations/Noctua (Kimberly & Chris)

Getting Noctua ready for production (Kimberly & Seth)

  • Kimberly & Seth Blocking issues list: TO BE COMPLETED
  • Action Item Corvallis 2017/06:
    • Provide ways for users to recover and digest GO-CAM units (Gene Ontology-based Causal Activity Model). Ideas include rule-based generations of text statements from model, cytoscape view of network described, etc.
    • ECO codes available for use in Noctua should show how they map up to a classic GO code, and there should be an alert for curators when they are using a code that does NOT map up to a classic code
    • PRO IDs for use in Noctua
    • Fix GPAD export from Noctua https://github.com/geneontology/noctua/issues/418
    • Add a SPARTA workbench https://github.com/geneontology/noctua/issues/465
    • Working group discussion of evidence on complex Noctua models (Kimberly?)

Noctua table view demo (Chris)

Project updates

  • Ontology WG update: David
  • AGR - report to GOC: PIs
  • SynGO meeting report: Paul T
  • Report of Reactome-GO connection: David H/Peter D
  • Report on transcription work/Noctua templates: Astrid GREEKC consortium=

Evening: Poster session

Tuesday 3rd October

Documentation (Kimberly/Seth)

Kimberly Action Items Corvallis 2017/06

  • Continue with the consolidation of all documentation for ontology editing, and remove all old documents.
  • Review annotation documentation and add to github and readthedocs.
  • Make sure to mark obsolete pages/doc as such and add a link to the new relevant doc
  • Solicit annotation documentation from participating groups for consolidation.
  • Make sure to mark docs with ‘Date last reviewed’ so it’s easy for users to know when the documentation was last touched.
  • Pascale: additional information associated with GO terms, see GitHub ticket?
  • Add and follow action items at https://github.com/orgs/geneontology/projects/3

GitHub tutorial (Seth & Pascale)

How GO now uses GitHub for project management and guidelines for contributors

  • Where is information relevant to everyone's need
  • Groups (Groups.yaml)
  • Members
  • Etc

Annotation guidelines and issues (part two)

Centralization of InterPro2GO annotations (Paul T)

Proposal (follow-up from Geneva 2016):

  • GO database pulls directly from InterPro2GO for UniProt Reference Proteomes
  • MOD identifier is used as primary gene identifier
  • Annotations are given "contributed by" InterPro
  • MODs pull from GO database, no need to maintain separate InterPro pipelines

HTP guidelines (Helen)

Helen - 15 minutes Report on progress from HTP working group

  • Provision of new evidence code
  • Implementation & developing guidelines

Transcription annotations decision tree

Ruth Action Items Corvallis 2017/06

  • David OS to create transcription regulator activity (proposed by Paul T)
  • Proposed changes to decision tree in Corvallis:
    • Simplified from previous version. Essentially a choice between ‘regulating transcription by RNA polymerase II’ or ‘regulating gene expression’
    • Annotation 5 = contributes_to sequence-specific DNA binding

David: when people do enrichment, they don’t drop contributes_to (ie., pay attention to qualifiers), so all those proteins will come down as ‘DNA binding’ Action item: replace ‘annotation 5’ with ISS annotation (if DNA binding domain) or contributes to annotation 5 with ISS annotation if no DNA binding domain and domains to suggest coactivator

    • Annotation 3 = nuclear chromatin

Not everyone comfortable with this (ex., Stacia, David) Shouldn’t it be ‘colocalizes_with’? It was previously agreed that the definition for nuclear chromatin: The ordered and organized complex of DNA, protein, and sometimes RNA, that forms the chromosome in the nucleus. Source:PMID:20404130 was to be applied. The proteins here include all associated proteins, not limited to just histones. With this statement the TFs are then contributing to chromatin, rather than binding to chromatin or colocalizing with it.

    • Decision tree to be put up on GOC website.
    • Should annotation 4 exist? (Ruth)

PAINT update (Huaiyu)

Huaiyu Action Items Corvallis 2017/06:

  • Encourage discussion between PAINT curators and other annotators about terms not used for propagation
  • Report how many annotations per species are used for annotation propagation; could even supply this number for propagation specifically to human genes
  • Ruth and Huaiyu (others?) will discuss making use of groups that have already annotated specific gene lists to annotate the corresponding PAINT families.
  • Smooth out the challenge mechanism to make it easier to do make and resolve

the challenges, identify terms that may be problematic and would benefit from consistency exercises and discussion.

  • Get a list of families where terms have not been propagated (?) - Please check this one for clarity.

(added to github project board) Develop mechanism to trigger review of annotated PAINT families.

Viral processes update (Pascale)

Action Items Corvallis 2017/06 Check whether the incorporated changes could affect the host proteins. Document the use cases.

Community Support

Citing GO (Paul T)

Enrichment (Paul T & Suzi)

  • Web page
  • Paul Pavlidis…
  • Data Commons work


WHY creating slims - Intro to slim philosophy (Mary,Val, Suzi)

Judy, Mary D (+ Suzi, Val, etc). For overviews, for particular taxa, for a particular area of biology

Creating a biologically useful slim (complete coverage by aspect, biologically useful terms i.e sufficient granularity, avoiding single step process terms (i.e functions), different slims for different purposes) : Specifications for slims from user's perspective (Val: 20 mins) slides

HOW to make slims (Chris)

Yaml format for creating slims/types of slims/target organisms

Use and maintenance of slims (Mary and Suzi)

Mary: algorithm - 15 minutes Suzi: GO ribbon

Wednesday 4th October

Ongoing work

AmiGO (Follow up with Seth)

  • In general, while several of the AmiGO issues are high-priority, there has been limited bandwidth to tackle them in the context of continuing work on Noctua and the replacement pipeline. Several fixes are queued up and will be available before the upcoming SAB meeting.
    • In response to: in base_statistics, plotly graph for "Experimental annotation publications by assigner" is confusing https://github.com/geneontology/amigo/issues/429
    • From Pascale's question: My understanding is that there are essentially no resources for AmiGO right now so any AmiGO issue is low priority. Is this correct?

The Fate of Simple Processes

  • analysis of gene products annotated to phosphorylation but not annotated to a kinase MF term. What did these annotations actually mean? Curators would need to review. Timeline? Deadline? Working group? One possibility would be to use part_of/involved_in relation to phosphorylation for genes also annotated to kinase MF, and causally_upstream_of_or_within for others until curators can re-evaluate.
  • Other considerations:
    • Helen: are there many the single-step processes?
    • Paul: user-oriented approach - is it a useful grouping for our users?
    • Ruth: we need to think about the meaning beyond just “phosphorylation”
    • Ruth: what are the consequences of removing “phosphorylation” and what happens to all its children?
    • Pascale Q: providing that we remove the processes, would it affect the term enrichment analysis?

BP refactoring

  • Defining “Cellular Process” and “Multi-Organism Process” terms
  • Action item: the comments/examples/notes should be captured, working group to discuss this.


Establish a working group for when and how to use proteoforms in annotation. (Kimberly with Harold and Li)

Usability issues

  • What do users want?
    • truth (summary/story/model)?
    • fishing expeditions?
    • api access?
    • appropriate licensing
  • Who are our users?
    • geneticists?
    • clinicians?
    • computational biologists?
      • aggregators
  • Use cases: https://github.com/geneontology/go-ontology/issues/13606
  • Perhaps discussion of examples of how the GOC members are engaging with the community and how we can do better in the future (suggested by Helen).

Action Item Review

Wednesday noon-ish Fin