Manager Call 2020-06-17: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
Line 11: Line 11:
https://github.com/geneontology/go-site/issues/1105
https://github.com/geneontology/go-site/issues/1105
Should they not be ?  
Should they not be ?  
==Evidence code for inferred annotations==
(Pascale, from an ontlogy ticket)
https://github.com/geneontology/go-ontology/issues/19461


==Bader gene sets==
==Bader gene sets==

Revision as of 13:01, 15 June 2020

Agenda

  • Agenda: Laurent-Philippe
  • Minutes: David
  • Present:
  • Regrets:


Isoforms NOT in AmiGO/products

(Pascale, from feedback from Ruth) https://github.com/geneontology/go-site/issues/1105 Should they not be ?

Evidence code for inferred annotations

(Pascale, from an ontlogy ticket) https://github.com/geneontology/go-ontology/issues/19461

Bader gene sets

Approach to handle gene sets redundancy.

They are deriving gene sets for GO, but are using EBI and MGI for human and mouse annotations: http://baderlab.org/GeneSets#Sources.

Proposals: 1) contact them to explain the benefits of fetching annotations from GOC instead of EBI/MGI instead of GOC 2) page on the go site to explain the above (differences & benefits from fetching annotations from GOC rather than a source; eg check, validations, etc) 3) some of Bader gene sets could be of interest for QC ?

Updated GO managers page to match the Project Org chart

(Pascale)