Revision as of 15:08, 1 September 2020

Agenda

Everyone should have sent their section(s)

15 Sep deadline for update article

Time ran out on last meeting- any last thoughts?

Amigo regulates closure: The current behavior is probably not the best one - regulates closure should NOT be applied by default

Summary from Software call

Request to include regulates closure in GO enrichment tool and results from the tests.

The different phases, the responsibility of product owner, technical lead and architect for each phase

- requirement phase

- implementation plan

- project validation

- tickets and assignment

Noctua Imports (#3a)
- MGI/wormbase imports
- GPAD/GPI 2.0
- Minerva/gpad output
Legacy data (#6)

Pascale, Laurent-Philippe

1. gp2protein, gp2RNA files, gpi files: Any preferences for keeping/dropping them ?
- gp2protein, gp2RNA: https://github.com/geneontology/archive-reconstruction/issues/3
- gpi: https://github.com/geneontology/archive-reconstruction/issues/2
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

@@ Line 59: / Line 59: @@
 ** gpi: https://github.com/geneontology/archive-reconstruction/issues/2
 * 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
+* 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'''