Manager Call 2019-08-21: Difference between revisions
mNo edit summary |
|||
Line 13: | Line 13: | ||
* Get your people to pay (used for badges, etc.--the true reg) | * Get your people to pay (used for badges, etc.--the true reg) | ||
* There is only "Yes" and "No", there is no "Maybe" | * There is only "Yes" and "No", there is no "Maybe" | ||
==Aims GO meeting== | |||
Status on Priority 1 Tasks that we decided on: | |||
# GO-CAM validation software [Jim, Ben, Eric, Laurent-Philippe] | |||
(which includes GO-CAM specifications [Kimberly, David, Pascale, Ben, Jim, Huaiyu, Chris, Paul] | |||
# Integrate line-by-line annotations into Noctua [Kimberly, David, Ben, Dustin] [depends on #1; can we integrate MF? ] | |||
# Release Noctua Form 2.0 + ART [Tremayne, Kimberly, Seth, David, (Jim) Laurent-Philippe] | |||
# Retire legacy infrastructure [Chris, Seth] | |||
# Implement stricter checks on end products for automatic halt of pipeline [Seth, Eric] | |||
# Quality Control: Create automated reports on pre-releases [Laurent-Philippe] | |||
# Quality control: Data release pipeline: add a freeze and QC step [Seth, Pascale] - DONE | |||
# Finalize GPAD/GPI 2.0 Specifications [Kimberly, Seth, Chris] | |||
# Ontology: Removal of ChEBI roles when they are not strict [Karen] | |||
# Ontology: Define guidelines for creating new complexes [Ben, David / Judy] | |||
Priority 2 tasks: | |||
# Stabilize data release pipeline [Seth] | |||
# Stabilize release date [Seth] | |||
# Quality Control: Rules [Pascale, Seth, Eric] | |||
# Allow GPAD/GPI 2.0 in pipeline [nobody assigned] | |||
# GPX support [Chris, Seth] | |||
# Improve Helpdesk [Suzi, Laurent-Phillippe] | |||
# Tools and APIs [Chris, Laurent-Phillippe] | |||
# Pathways2GO [David (+Paul), Ben] | |||
# AmiGO improvements [David, Seth] | |||
# AmiGO improvements: improve display of 'redundant' annotations [Kimberly ? ] | |||
# AmiGO: Ribbon display and Alliance slim [Kimberly, Laurent-Phillippe] | |||
# Ontology: Molecular function refactoring [Paul, Pascale] | |||
==Pipeline progress== | ==Pipeline progress== |
Revision as of 04:35, 20 August 2019
Agenda
- Agenda: Seth
- Minutes: Pascale
GO users meeting Berkeley 2019
- TODO: Finalize decision on topics/speakers/target audience.
Preliminary agenda is here: https://docs.google.com/document/d/1YBCEeSl1MKPvtRNAMGBGcOZqdZl3wlbwWC1nuDnccqE/edit
- Next: start announcing
GO Meeting general
- Get your people to sign up
- Get your people to pay (used for badges, etc.--the true reg)
- There is only "Yes" and "No", there is no "Maybe"
Aims GO meeting
Status on Priority 1 Tasks that we decided on:
- GO-CAM validation software [Jim, Ben, Eric, Laurent-Philippe]
(which includes GO-CAM specifications [Kimberly, David, Pascale, Ben, Jim, Huaiyu, Chris, Paul]
- Integrate line-by-line annotations into Noctua [Kimberly, David, Ben, Dustin] [depends on #1; can we integrate MF? ]
- Release Noctua Form 2.0 + ART [Tremayne, Kimberly, Seth, David, (Jim) Laurent-Philippe]
- Retire legacy infrastructure [Chris, Seth]
- Implement stricter checks on end products for automatic halt of pipeline [Seth, Eric]
- Quality Control: Create automated reports on pre-releases [Laurent-Philippe]
- Quality control: Data release pipeline: add a freeze and QC step [Seth, Pascale] - DONE
- Finalize GPAD/GPI 2.0 Specifications [Kimberly, Seth, Chris]
- Ontology: Removal of ChEBI roles when they are not strict [Karen]
- Ontology: Define guidelines for creating new complexes [Ben, David / Judy]
Priority 2 tasks:
- Stabilize data release pipeline [Seth]
- Stabilize release date [Seth]
- Quality Control: Rules [Pascale, Seth, Eric]
- Allow GPAD/GPI 2.0 in pipeline [nobody assigned]
- GPX support [Chris, Seth]
- Improve Helpdesk [Suzi, Laurent-Phillippe]
- Tools and APIs [Chris, Laurent-Phillippe]
- Pathways2GO [David (+Paul), Ben]
- AmiGO improvements [David, Seth]
- AmiGO improvements: improve display of 'redundant' annotations [Kimberly ? ]
- AmiGO: Ribbon display and Alliance slim [Kimberly, Laurent-Phillippe]
- Ontology: Molecular function refactoring [Paul, Pascale]
Pipeline progress
- release process started
Project for improving mappings?
...[L]et's discuss whether we should initiate a project for improving the mappings: documentation, workflow processes, quality control, staying up to date.
We are of course doing a good job in specific instances, whether it is ones we bring in (interpro/reactom) or ones we maintain (e.g rhea), but this project would be about a broader approach.
Cross references on GO website/AmiGO page
- Follow up on https://github.com/geneontology/amigo/issues/578
- Seth was to create documentation describing how that page is generated; where is that ?
Collaborators Webpage
We need to decide who we put as collaborators and as contributing groups. There is some redundancy. https://github.com/geneontology/geneontology.github.io/issues/130
GO stats
Status, remaining work and decision on computing or not the stats for previous releases original issue and recent issue
Notes on zenodo archives and solr 3.6.
GO API & GOLr: availability & comment
On August 17, several down time or freeze of both the GO API and GOLr: status.geneontology.org. Anything particular on that date ?
GO API logs indicate pics of 2000+ packets / mn (usually 100-500 packets / mn). Most queries seems to be slimmer/ribbon related.