Manager Call 2017-07-05: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
*Project strategy | *Project strategy | ||
**We have an annotation call on next Tuesday, July 11th and we should have a (proposed) strategy in place for that call | **We have an annotation call on next Tuesday, July 11th and we should have a (proposed) strategy in place for that call | ||
** | **Make sure we strike the right balance between: | ||
***theoretical (relations between MFs, BPs; representation in the ontology) | |||
***practical (consistent annotations; annotation guidelines that reflect experiments reported in the literature) | |||
**Review and flag all existing github tickets in ontology and annotation repositories | |||
***Need a signaling label | |||
*Cambridge meeting, Sunday, October 1st | *Cambridge meeting, Sunday, October 1st | ||
**Any funding available for non GO-funded groups? | **Any funding available for non GO-funded groups? | ||
=== GO AGR Slim === | === GO AGR Slim === | ||
*[https://github.com/geneontology/go-ontology/issues/13791 Modification to AGR slim] | *[https://github.com/geneontology/go-ontology/issues/13791 Modification to AGR slim] |
Revision as of 09:55, 5 July 2017
Joining the Call on Zoom
https://stanford.zoom.us/j/754529609
Agenda
From June 21st Call
Licensing
- The DO has recently gone to a CC0 license. http://disease-ontology.org/
Attributes in Noctua Annotations
New Issues
Signaling Project and Cambridge Meeting
- Project strategy
- We have an annotation call on next Tuesday, July 11th and we should have a (proposed) strategy in place for that call
- Make sure we strike the right balance between:
- theoretical (relations between MFs, BPs; representation in the ontology)
- practical (consistent annotations; annotation guidelines that reflect experiments reported in the literature)
- Review and flag all existing github tickets in ontology and annotation repositories
- Need a signaling label
- Cambridge meeting, Sunday, October 1st
- Any funding available for non GO-funded groups?
GO AGR Slim
- Modification to AGR slim
- What should AGR/MOD GO curators be doing for this?
Annotation Qualifiers
- What are the next steps?
- Add guidelines to github documentation with examples for use of each BP qualifier (include positive and negative directionality)
- Propose a half-day online working group meeting for this
- acts_upstream_of_or_within
- acts_upstream_of
- involved_in
- regulates
- Decide on SOP for legacy annotations
- This may be different for different annotation groups.
- What would be involved in providing computational approaches to help curators?
Minutes
- On call: