Manager Call 2020-09-23: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 36: Line 36:


'''Next steps: '''
'''Next steps: '''
1. New MGI/WB files to be QC'ed (David & Kimberly)
# New MGI/WB files to be QC'ed (David & Kimberly)
2. Finalize history/annotation properties GPAD2.0 specs
# Finalize history/annotation properties GPAD2.0 specs
3. Spec out GPAD output from GO-CAM models
# Spec out GPAD output from GO-CAM models
<hr>
<hr>



Revision as of 05:04, 17 September 2020

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


Agenda

Announcement

  • Pascale will be making the agenda for those calls from now on.
  • The main purpose of the calls is to report to PIs on projects progress, expected deliverables and delivery dates, delays, changes in project scope (unexpected tasks that need to be resourced).
  • Projects are based on the current projects, chosen and prioritized at/around each GO meeting - https://docs.google.com/document/d/1URLkEQBewlzD-NVAjbPLWD5Gu-5xq0RysTrm1GMbuiM/edit#
  • 2020 is a little different with the grant due in Jan 2021 - the deliverables will go to the end of 2020/early 2021 WRT what we want to show in the grant/preliminary data we need to produce
  • Everyone is of course invited to contribute discussion topics - add directly or ask Pascale. Pascale will be reviewing the agenda before calls
  • Everyone is of course invited to edit/fix minutes or action items if something is not correct.

Blocking issues/delays/changes in project scope

Anyone has blocking issues/delays/changes in project scope they need to report to managers /PIs?

Projects updates

GAF 2.2 (#4h) and GPAD/GPI 2.0 (#4i) (Kimberly)

  • Review action items

Draft the announcement and provide a link to the test file: https://docs.google.com/document/d/1x-jyBQgb4MoCdtNwxftbHJueP0n43Uz0PC_bZkH8ajw/edit

    • where to announce ? go-friends, go-announcements, biostars and other forums (which ones)?, can we also make a list of likely impacted resources? David, VLAD, Panther, STRING, GeneMania/Gary Bader... etc
    • Mention we'll provide a 2.0 -> 2.2 converter (Pascale : I thought GO would convert upstream data to GAF2.2 and provide a 2-2 -> 2.0 converter for groups unable to consume 2.2)
    • Goal: December for consortium and March release for external users: can we re-consider January ?

Noctua Imports (#3a)

Action items: Kimberly and David:

  • finalize annotation properties specs GPAD2.0 (metadata/history)
  • produce examples of issues with GPAD output
  • draft an agenda for a working meeting (~2days) to defines the requirements for GPAD output
  • priorities those issues to have different milestones and a better vision on when we could work with those ? (eg when for a 80% or 90% solution)

Next steps:

  1.  New MGI/WB files to be QC'ed (David & Kimberly)
  2. Finalize history/annotation properties GPAD2.0 specs
  3. Spec out GPAD output from GO-CAM models

Legacy data (#6)

Update Laurent-Philippe


Noctua (#3e)

  • ui implementations
    • bug fixes
      • Ongoing; Tremayne is submitting some PRs to noctua-dev for testing
      • Adding: connect to existing nodes; re-use of fields in a given model
    • ART
      • Tremayne has a prototype that David and Kimberly can test. The prototype has much of the desired functionality but is not yet employing the necessary functionality from minerva which will be developed later when Ben is available to work on that.

https://github.com/geneontology/noctua-annotation-review/issues/21

  • testing and release framework

Minerva support for noctua


Pipeline (ongoing) (#4a)


Pathways2GO paper (#1bi)

AOB

Creating a static page for SPARQL endpoint

Mentioned in the NAR paper - this needs to be prioritized and resourced: https://github.com/geneontology/go-site/issues/1549