Manager Call 2019-10-30

From GO Wiki
Revision as of 11:51, 30 October 2019 by Lpalbou (talk | contribs) (→‎Projects Specification guidelines)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


  • Agenda: David
  • Minutes: Laurent-Philippe
  • Present: David, Chris, Judy, Pascale, Huaiyu, Seth, Paul, Chris, Laurent-Philippe, Suzi, Kimberly

Projects Specification guidelines

  • Start to spec out projects. Right now there are too many high-priority things. We modified the template document on the Google drive.
  • There is no longer a need to make a GH project for a project that is not yet active.

First pass at project priorities and PIs will assign the Product Owners / Tech Leads, especially green tasks (there are 42 high tasks). Meanwhile, reviewing all high / green tasks and assigning very high categories for anything related to the Noctua 2.0 / GO-CAM main delivery.

Note: annotation history set to high priority as required for MOD imports, hence for the main delivery.

David presents a spreadsheet on the different steps to achieve the MOD imports. Pascale expresses some concerns about QC.

SAB report

The SAB report was emailed today to go-managers.


In some cases, AmiGO-loaded ontologies seem sub-optimal, as it returns no-GO terms (often more than GO terms)

  • Suggestions:
    • Non-GO terms should NOT be returned in the search results
    • Obsolete terms should be weighted down (or an option to not get obsolete terms in the search results)
  • What is the priority on this task ? Considering people write that they are using QuickGO because of this (and other usability issues)

PRO gpi file

  • Harold reports from the PRO meeting (week of October 21st) that PRO is now providing a production gpi file released every 3-4 months.
  • PRO is also providing a 'development' file with more up-to-date additions to accommodate the needs of MODs that use PRO for their curation and want to include PRO ids in their respective gpi files.
  • We need to establish an SOP for id/accession dataflow between PRO and GO annotation groups.
    • We don't want duplicate ids in gpi files from PRO, MODs, and UniProt.
    • How do we make annotations that curators make with PRO ids available?
  • Note that there is a more general issue wrt allowed entity identifiers as primary annotation objects, With/From entries, and annotation extensions.
    • We need to deal with this issue, too, since it is creating problems downstream for consuming groups and may have implications for what we put into NEO.

GO Out-of-Office Calendar

Pascale: I’ve added people in the managers team in my ‘GO people away’ Google calendar. Let me know if you haven’t received the invite or if you want another email address to be associated.