Manager Call 2018-04-19: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[Category:GO Managers Meetings]] | [[Category:GO Managers Meetings]] | ||
= Call in info= | |||
https://stanford.zoom.us/j/754529609 | |||
= Agenda = | = Agenda = |
Revision as of 10:49, 18 April 2018
Call in info
https://stanford.zoom.us/j/754529609
Agenda
NYC Meeting Agenda
- Start working on the agenda in more details
- SAB agenda, plans
ACTION POINT Please everyone make slides for your part by Friday April 27 Slides should be added here: https://drive.google.com/drive/u/0/folders/1iOGHjKc9FN_ShrlNEW0CvOmJANzXqep-
External Groups
- At least three new groups are interested in submitting GO annotations
- What's our plan for handling this:
- Is there an SOP for bringing a new dedicated annotation group on board (as opposed to drive-by contributions)?
- Minimally:
- GOC-approved curator docs
- joining appropriate mail lists (to hear of obsoletion announces etc)
- A new yaml file in datasets/
- Some kind of QC of the annotations so we can trust them
- Minimally:
Documentation
GO Site- Can we explicitly identify which tools/file formats are compatible with which relations/extensions (curator facing)
- SGD wants list of Noctua relations via category- BP to MF, to BP, to CC, MF to BP...
Protein2GO- GO RELS are not in RO. Eliminate some?
- Long term plans? including identifying/removing least common annotation extensions after re-annotation
Which annotation validation rules are currently implemented? https://github.com/geneontology/go-annotation/issues/1928
Working Group Meetings
- Quarterly?
- Rotate between ontology and annotation (small, focused groups)
- Test virtual meetings, but still focused on the task
Noctua
1.0 Rollout
- Merge Tremayne's fork with Noctua-dev for further testing
- Some outstanding issues on SAE
- Single source file for MODs to consume
Reactome Imports
- David, Kimberly have looked at some imports/translations
- Ben's work looks to be potentially very useful and promising for seeding templates, models
- Will probably require significant manual input, refinement, testing
End User Tools
- What plans do we have for implementing consumption and display of GO-CAM models?
- How does the AGR GO working group fit into this task?
- https://github.com/geneontology/noctua/issues/519
GO Helpdesk
Discuss this ticket: https://github.com/geneontology/go-site/issues/584
This is up for discussion at next Manager meeting. Seems like an outreach task. There is some documentation on GO for curators- 1st step is to contact GO. No guidelines on what GO should do (how to train, submit, who is responsible for maintaining...)
Email forwarded to Suzi A.
Ontology
Announcing changes to the wider user community
- This was brought up by Birgit in the protein complex merge ticket - she was suggesting we make an announcement. However we never made annoucements before (except for obsoletions); should we start? What would be the guidelines? For example when a merge affects more than 100, 1000 annotations ? EXP only ?
- Pascale: changes to definitions of root terms: https://github.com/geneontology/go-ontology/issues/14899; isn't this a big change ? How should we notify people?
- Should we create a label in GH 'Major change', so we can easily pull out the tickets and show them at Ontology and Annotation calls ? (perhaps in annual reports as well)
- Pascale: suggestion: create a new label 'major change' and announce them either on twitter and/or on the website as user stories (or whatever it's called).