Manager Call 2020-09-02: Difference between revisions
Line 53: | Line 53: | ||
** '''GPAD/GPI 2.0''' | ** '''GPAD/GPI 2.0''' | ||
** '''Minerva/gpad output''' | ** '''Minerva/gpad output''' | ||
*** I think we need to schedule a 1/2 or full day working meeting to focus on the GO-CAM GPAD output. Propose that David and I create an agenda so we know who needs to be at the meeting and then find a good time for everyone. (Kimberly) | |||
* '''Legacy data''' (#6) | * '''Legacy data''' (#6) | ||
Pascale, Laurent-Philippe | Pascale, Laurent-Philippe |
Revision as of 20:15, 1 September 2020
Agenda
- Agenda: Suzi
- Minutes: Huaiyu
- Present:
- Regrets: DavidH
NAR paper update
Everyone should have sent their section(s)
15 Sep deadline for update article
GOC Meeting Baltimore
Draft agenda based on priorities: https://docs.google.com/document/d/17Jo2qdNfbF58rIYI2K1dkrEWk4-JqT-2aVAb1_vgAHI/edit?usp=drive_web&ouid=116162935390241629304
Noctua capacities and expectations
https://docs.google.com/document/d/1op_gvlN3c1wqA0ii7asSQyg0ft-NpiuAb1jErcF8ZuA/edit
Time ran out on last meeting- any last thoughts?
New group: PHI-Base
https://github.com/geneontology/go-site/pull/1543
Regulates closure
- Amigo regulates closure: The current behavior is probably not the best one - regulates closure should NOT be applied by default
https://github.com/geneontology/amigo/issues/602
Summary from Software call
- Request to include regulates closure in GO enrichment tool and results from the tests.
Process to follow for a project
The different phases, the responsibility of product owner, technical lead and architect for each phase
- requirement phase
- implementation plan
- project validation
- tickets and assignment
Ongoing projects
Anyone has blocking issues/delays/changes in project scope they need to report to managers /PIs?
Ongoing projects updates
- Noctua Imports (#3a)
- MGI/wormbase imports
- GPAD/GPI 2.0
- Minerva/gpad output
- I think we need to schedule a 1/2 or full day working meeting to focus on the GO-CAM GPAD output. Propose that David and I create an agenda so we know who needs to be at the meeting and then find a good time for everyone. (Kimberly)
- Legacy data (#6)
Pascale, Laurent-Philippe
- 1. gp2protein, gp2RNA files, gpi files: Any preferences for keeping/dropping them ?
- 2. File names: what about users citing old filenames ? see https://github.com/geneontology/archive-reconstruction/issues/1#issuecomment-680121448
- 3. Folder structure: can we avoid repetition in folder names ? see https://github.com/geneontology/archive-reconstruction/issues/1#issuecomment-680122454 . How do we plan for future changes ? For instance if annotation files are created for species rather than groups (this would also be a breaking change for Zenodo).
- 4. File browser: use the AWS S3 of the archive (https://geneontology-tmp.s3.amazonaws.com/index.html) for both current & release.geneontology.org ?
- 5. Do we store this archive only on release.geneontology.org or do we store it also on Zenodo *now* ? Pros: Zenodo is here for "always" and free, AWS S3 could be turned off (eg if cost not paid); Cons: everything in Zenodo would have a DOI and it could easily discourage any changes to the archive folder hierarchy / file names (situation we are in)
- Noctua (#3e)
- ui implementations
- bug fixes
- ART
- ui implementations
https://github.com/geneontology/noctua-annotation-review/issues/21
- testing and release framework
- Minerva support for noctua
- Pipeline (ongoing) (#4a)
- Pathways2GO paper (#1bi)