Manager Call 2017-07-19: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
(Created page with "= Joining the Call on Zoom = https://stanford.zoom.us/j/754529609 = Agenda = == From June 21st Call == === Annotation Qualifiers === *What are the next steps? **Add guidelin...")
 
mNo edit summary
Line 28: Line 28:




===Process to deal with stale annotations===
Draft message:
Dear GO contributors,


GO is now using GitHub as a tracking system for ontology changes and for annotation issues. The repository can be found here:
https://github.com/geneontology
'''UPDATE to ???'''
We need to have a contact person for each group, ideally registered to GitHub, or at least an email address where we can address queries. The list of current contacts is here:
https://github.com/geneontology/go-ontology/blob/master/curator_group_contacts.tsv
'''UPDATE to ???'''
The contact person(s) is (are) responsible for
(1) answering requests regarding the annotations provided by the group
(2) providing feedback on ontology if the ontology editors would like the expertise of that group
Right now we have no contacts persons for the following groups:
CACAO
DFLAT
EcoCyc
EcoliWiki
Ensembl
EnsemblFungi
EnsemblPlants
GDB
GOC
GR
HPA
JCVI
LIFEdb
MENGO
MTBBASE
NTNU_SB
PAMGO_GAT
PAMGO_MGG
PseudoCAP
Roslin_Institute
TIGR
UniProt
If you are part of any of these groups and would like to be the contact point, please email me so I can add you to the list.
For the groups who do not reply, GO consortium will add itself as an editor of these annotations and will made changes to the annotations as necessary to ensure that the annotation meet our guidelines.





Revision as of 04:37, 11 July 2017

Joining the Call on Zoom

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

Agenda

From June 21st Call

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?


Working groups management on GitHub

Pascale has created new ‘Projects’ from the action items that proposed working groups at the GOC meeting, see https://github.com/orgs/geneontology/projects It would be nice to have a project lead on each of these, and add any relevant ticket.

We need to prioritize and probably add additional working groups.


Process to deal with stale annotations

Draft message: Dear GO contributors,

GO is now using GitHub as a tracking system for ontology changes and for annotation issues. The repository can be found here: https://github.com/geneontology UPDATE to ???

We need to have a contact person for each group, ideally registered to GitHub, or at least an email address where we can address queries. The list of current contacts is here: https://github.com/geneontology/go-ontology/blob/master/curator_group_contacts.tsv

UPDATE to ???

The contact person(s) is (are) responsible for (1) answering requests regarding the annotations provided by the group (2) providing feedback on ontology if the ontology editors would like the expertise of that group


Right now we have no contacts persons for the following groups:

CACAO DFLAT EcoCyc EcoliWiki Ensembl EnsemblFungi EnsemblPlants GDB GOC GR HPA JCVI LIFEdb MENGO MTBBASE NTNU_SB PAMGO_GAT PAMGO_MGG PseudoCAP Roslin_Institute TIGR UniProt


If you are part of any of these groups and would like to be the contact point, please email me so I can add you to the list. For the groups who do not reply, GO consortium will add itself as an editor of these annotations and will made changes to the annotations as necessary to ensure that the annotation meet our guidelines.


Minutes

  • On call: