Manager Call 2020-02-12: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 25: Line 25:
==Status of 'high priority' Projects==
==Status of 'high priority' Projects==
Google spreadsheet of the projects: https://docs.google.com/spreadsheets/d/1lZO0cf64_eufimUhEdcpiZMGEmvF6_7BW-GQWBXR3Mw/edit#gid=199463565
Google spreadsheet of the projects: https://docs.google.com/spreadsheets/d/1lZO0cf64_eufimUhEdcpiZMGEmvF6_7BW-GQWBXR3Mw/edit#gid=199463565
* We need to know which of those projects are being worked on.
* Also, are there other projects not in this list ? to be sure the priorities are aligned with the specification documents and vice versa.




Line 30: Line 33:
Not yet prioritized but the PIs asked to evaluate work to decide whether this will be prioritized
Not yet prioritized but the PIs asked to evaluate work to decide whether this will be prioritized
Seth/Chris: evaluation of time - prioritization - resources
Seth/Chris: evaluation of time - prioritization - resources


===2.2 Aggregate Statistics for releases===
===2.2 Aggregate Statistics for releases===


===2.3 Legacy infrastructure ===
===2.3 Legacy infrastructure ===
Seth/Chris: next step?


===3.1 Migration of MGI and WormBase annotations to Noctua===
===3.1 Migration of MGI and WormBase annotations to Noctua===
Week of Feb 24 hackaton will address that:  
Week of Feb 24 hackaton will address that:  
Aims meeting:
* The primary product of this meeting will be a gantt chart (see David’s from MGI’s perspective) that fully describes input and output switchover dependencies at the three sites (although not necessarily times, as some of this will be dictated by other resource limitations). The document will define future work on this project.
* A secondary product will be to have a plan for annotation history. (TASK 4.5 in Priorities doc)
* A secondary product will be to have a base validation format that is usable for both batch rules and minerva UI signals. (TASK #?? Priority? )
* A secondary product will be continued work on merging the GPAD codebase and RDF emitters into the ontobio library. (TASK #?? Priority? )


===4.1 GO-CAM ShEx specification v1.0 completion===
===4.1 GO-CAM ShEx specification v1.0 completion===

Revision as of 09:56, 12 February 2020

Agenda

  • Agenda: Suzi
  • Minutes: Seth
  • Present:
  • Regrets:

Discussion points

Upcoming Meetings

Caltech f2f, 24-28 Feb

GO meeting Paris, 11 (Users), 12-14 (Main), 15(SAB) May

GO meeting Baltimore, week of 5th Oct

Discussion

Release delays

Is there anything we can do to help make releases easier ?

Status of 'high priority' Projects

Google spreadsheet of the projects: https://docs.google.com/spreadsheets/d/1lZO0cf64_eufimUhEdcpiZMGEmvF6_7BW-GQWBXR3Mw/edit#gid=199463565

  • We need to know which of those projects are being worked on.
  • Also, are there other projects not in this list ? to be sure the priorities are aligned with the specification documents and vice versa.


AmiGO search fixes

Not yet prioritized but the PIs asked to evaluate work to decide whether this will be prioritized Seth/Chris: evaluation of time - prioritization - resources

2.2 Aggregate Statistics for releases

2.3 Legacy infrastructure

3.1 Migration of MGI and WormBase annotations to Noctua

Week of Feb 24 hackaton will address that: Aims meeting:

  • The primary product of this meeting will be a gantt chart (see David’s from MGI’s perspective) that fully describes input and output switchover dependencies at the three sites (although not necessarily times, as some of this will be dictated by other resource limitations). The document will define future work on this project.
  • A secondary product will be to have a plan for annotation history. (TASK 4.5 in Priorities doc)
  • A secondary product will be to have a base validation format that is usable for both batch rules and minerva UI signals. (TASK #?? Priority? )
  • A secondary product will be continued work on merging the GPAD codebase and RDF emitters into the ontobio library. (TASK #?? Priority? )


4.1 GO-CAM ShEx specification v1.0 completion

4.2 Integrating validation (AKA GO rules) into Minerva

4.3 Noctua/GO-CAM Curator Documentation: curation philosophy

  • Done ? Do we need to add links to this ?

4.4: Documentation: curation how-to

  • which relations to choose when - this is the main thing curators ask about

-> Kimberly in progress


4.8 Pathways2GO, including making models *activity-centric*

5.1 Deploy Noctua Search (as landing page)

5.3 Noctua onto "production" footing

8.7 Improve GO API & support the GO-CAM + documentation

Other discussion points

Loading viral and bacterial entries in NEO

https://github.com/geneontology/neo/issues/49 Prioritize + assign someone


Isoforms not loaded in AmiGO

Was there a decision NOT to include UniProt isoforms in AmiGO ? https://github.com/geneontology/go-site/issues/1105

Also - should we provide single files for each organism, rather than splitting by entity type ? http://current.geneontology.org/products/pages/downloads.html


Minutes:

Retrieved from "https://wiki.geneontology.org/index.php?title=Manager_Call_2020-02-12&oldid=77512"