Manager Call 2019-05-22
- 1 Agenda
- 1.1 Priorities until next GOC meeting
- 1.2 Discussion points
- 1.3 Items carried over from previous meetings
- 2 Minutes
- Agenda: Pascale
- Minutes: Laurent-Philippe
Priorities until next GOC meeting
Everyone was to fill in their effort (number of days until the GO meeting) for each Priority 1 project.
- GO software projects at some stage of development or discussion: https://docs.google.com/document/d/11spRpUY6IQ_1QhY0_LZuBaLScyMBb-EsyYOYnpOm_68/edit
- Projects SOP
June USC Meeting
Helpdesk widget status
Seth <- nothing further here from Seth, other discussions?
GO annotation in Apollo
- EuPathDB is interested in using Apollo for functional annotation
- How does this fit into our overall plan for developing tools for GO curation and working with new groups?
- Currently, we have calls on the third and fourth Tuesdays of each month.
- Curators want to discuss modeling questions (and these discussions are generally very interesting), but many issues remain unresolved at the end of the calls
- Is there a better way to do this, e.g. a smaller working group that examines specific annotation issues and comes up with guidelines to present to everyone?
Following up on SGN/Tomato and consequences
- What should be the "default" state in cases like this? Filter goa, lose experimental, or have double namespaces?
How much do we want to work to "centralize" and take over this functionality now? Should this pause the next release?
Following up on Authoritative groups procedure
Managers: do we need to change the policy ? For example SynGO annotated mouse and rat; MGI submits the SynGO annotations but not RGD (and anyway GOC would prefer to do the integration itself).
- Documentation is here Authoritative_Database_Groups (date unknown; moved from the old GO website)
- Judy: we should contact RGD (Pascale: and all other impacted resources) and ask them whether they would be willing to have the SynGO data loaded directly
- Paul: Paul S mentioned that he (wormbase) would be OK to just be able to review the data (in Noctua); the data flow doesn't need to go through wormbase
- Proposed process:
- SynGO data would be loaded directly into the GO database
- SynGO data would be filtered out from the MOD/contributors files (like PAINT)
- Authoritative databases would keep control of the annotations; they could review/give feedback (?)/edit annotations
- Check whether doable (Seth?)
- MGI and other groups stop loading SynGO annotations directly - would load by the GO pipeline
- Paul T to contact SynGO and all impacted groups to explain the proposed process
Items carried over from previous meetings
Meeting with MOD developers to go over GO pipeline
Similar to Seth and Laurie (?) at MGI
- We need an SOP for how to handle annotation (or other?) files that have pipeline-blocking errors that can be fixed by GO
- Is it okay to fix these errors?
- If yes, then is it okay to point to a GO version of the file in the source URL in the datasets.yaml file until the source file is fixed?
Fate of "unmanaged" external2go files
- Ontology group would like to archived them since we don't have the resources to maintain them and no one is maintaining these (e.g. mips is deprecated).
Must list which projects are not maintained anymore, and at least simplify the list. Waiting from Paul review. It seems tigr will be maintained by NCBI.
external2go svn link: http://viewvc.geneontology.org/viewvc/GO-SVN/trunk/external2go/
Also looking at "Genome Properties" for GO mappings. Chris will put some slides on this for microbial annotations, possibly another grant to have sufficient resources.
Note that there has been a discussion of why the Reactome file hasn't been updated. https://github.com/geneontology/go-site/issues/1031
Present: Pascale, Judy, Chris, Seth, Kimberly, Suzy A