Ontology meeting 2016-10-27: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Attendees: | Attendees: | ||
Minutes: | Minutes: David OS? | ||
Regrets: David H | Regrets: David H | ||
| Line 15: | Line 15: | ||
For background, see http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-06#Follow-up:_Modified_proteins | For background, see http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-06#Follow-up:_Modified_proteins | ||
FYI, Paola did some edits to the Google doc draft and passed it on to David H, who will look at it next week and prepare some slides for the GOC meeting. Link to the doc: https://docs.google.com/document/d/17U1TD3n_QI9coCycJcOUBDa2nRf3ggPR-tKjDMa_ff8/edit | FYI, Paola did some edits to the Google doc draft and passed it on to David H, who will look at it next week and prepare some slides for the GOC meeting. So, no work needed now. Link to the doc: https://docs.google.com/document/d/17U1TD3n_QI9coCycJcOUBDa2nRf3ggPR-tKjDMa_ff8/edit | ||
===ec2go mappings=== | ===ec2go mappings=== | ||
| Line 30: | Line 30: | ||
Background: http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-13#Update:_contacts_for_UniProt_annotations | Background: http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-13#Update:_contacts_for_UniProt_annotations | ||
We realised we could do with a single GH user - one for sending emails to help@uniprot.org, since they can triage UniProt annotations regardless of their provenance (SIB vs GOA). Melanie will contact Sylvain with our proposal, and we'll go from there. | We realised that we could do with a single GH user - one for sending emails to help@uniprot.org, since they can triage UniProt annotations regardless of their provenance (SIB vs GOA). Melanie will contact Sylvain with our proposal, and we'll go from there. | ||
===GitHub projects=== | ===GitHub projects=== | ||
Revision as of 05:31, 26 October 2016
Attendees:
Minutes: David OS?
Regrets: David H
GoToMeeting invite: https://global.gotomeeting.com/join/859015101
Items for discussion at GOC LA meeting
A reminder to add any items we'd like to discuss (or be discussed if we're not present in person) here: http://wiki.geneontology.org/index.php/2016_Los_Angeles_GOC_Meeting_Agenda
Update: proposal on modified protein terms
For background, see http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-06#Follow-up:_Modified_proteins
FYI, Paola did some edits to the Google doc draft and passed it on to David H, who will look at it next week and prepare some slides for the GOC meeting. So, no work needed now. Link to the doc: https://docs.google.com/document/d/17U1TD3n_QI9coCycJcOUBDa2nRf3ggPR-tKjDMa_ff8/edit
ec2go mappings
(If not resolved yet) Stemming from Doug's comment on the recent change: "So it sounds like this is a planned and good loss of annotation. Is an ~80% loss of ec2go-derived annotations similar to what MGI sees? I would think this might be similar for any group using the ec2go file? I guess if the ec dbxrefs were to higher level terms then including annotation to all the children could account for the vast majority of derived annotations. On a related note, I still did see three "-" containing EC numbers in ec2go: EC:4.2.1.-xref: > GO:scalarane-17alpha-19-diol synthase activity GO:0102643. Is that something that needs cleaning?"
Follow-up: Github Ontology Tracker Update - incomplete
See https://github.com/geneontology/go-site/issues/240.
Follow-up: contacts for UniProt annotations
Background: http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-13#Update:_contacts_for_UniProt_annotations
We realised that we could do with a single GH user - one for sending emails to help@uniprot.org, since they can triage UniProt annotations regardless of their provenance (SIB vs GOA). Melanie will contact Sylvain with our proposal, and we'll go from there.
GitHub projects
See background here: http://wiki.geneontology.org/index.php/Ontology_meeting_2016-10-06#GitHub_Projects
Plan is to look at https://github.com/geneontology/go-ontology/projects/1 and see how this works for us. Feel free to add there.