Manager Call 2018-02-21

From GO Wiki
Revision as of 08:16, 16 February 2018 by Pascale (talk | contribs)
Jump to navigation Jump to search


Call in info

https://stanford.zoom.us/j/754529609

Agenda

GO outreach role

Agenda for GOC meeting and SAB meeting

Annotation transfer across species

https://github.com/geneontology/go-annotation/issues/1807

Can we come up with a plan for annotation propagation across species moving forward? We have 3 main pipelines at the moment, PAINT, interpro2go, Ensembl (plus various groups may be using their own). Are all using the same rules? Are these clear? Do we need extra rules for blocking certain branches across certain levels? Are we all implementing the do-not-annotate subsets consistently? Do these need expanded, better strategy for response-to terms? - Chris

---

For example, in addition to PAINT, MGI brings in rat and human experimental annotations via ISO using MGI orthology assertions.

We do not use InterPro2GO for cross-species annotations.

The task first is, as you say, to gather status of major groups in this regard. This comes under AGR thinking too.

- Judy

USC developers hackaton jamboree report

Feb 7-8

Noctua V1 status report

GH ontology ticket marathon report

Feb 12-16, Denver


Outstanding from the docathon: What is a GO contributor, GO collaborator, and a GO resource?

see also website http://geneontology.org/page/contributors (Pascale) I want to double check this correctly represents people working on the project.



Minutes

  • On call: