Projects update meeting 2022-07-06: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→SynGO Updates) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
==Documentation== | ==Documentation== | ||
===Process for review and approval of documentation=== | ===Process for review and approval of documentation=== | ||
Can someone provide more context on this? [[User:Cjm|Cjm]] ([[User talk:Cjm|talk]]) 20:42, 5 July 2022 (EDT) | |||
* Who? | * Who? | ||
** managers? form a 'documentation committee'? | ** managers? form a 'documentation committee'? | ||
* How? | * How? | ||
** set up calls? via email/google docs + comments? | ** set up calls? via email/google docs + comments? | ||
===Distinction_between_'has_input'_and_'with/from'=== | ===Distinction_between_'has_input'_and_'with/from'=== | ||
| Line 23: | Line 25: | ||
===Google drive move=== | ===Google drive move=== | ||
https://github.com/orgs/geneontology/projects/90 | https://github.com/orgs/geneontology/projects/90 | ||
* Suzy to report on status | * Suzy to report on status & check on other people | ||
* Chris to move his files | |||
===[https://github.com/orgs/geneontology/projects/80 Model copy]=== | ===[https://github.com/orgs/geneontology/projects/80 Model copy]=== | ||
* Status | * Status | ||
** Latest software updates are now on noctua-dev | |||
** Kimberly is aiming to test later today | |||
=== Adding SO terms as valid range for 'occurs in' annotation extension === | === Adding SO terms as valid range for 'occurs in' annotation extension === | ||
| Line 33: | Line 38: | ||
* Any reason(s) not to add SO terms as a valid range? | * Any reason(s) not to add SO terms as a valid range? | ||
** A few years ago, there was discussion of MSO vs SO that might have had some bearing on this, but that discussion seems to have tailed off. | ** A few years ago, there was discussion of MSO vs SO that might have had some bearing on this, but that discussion seems to have tailed off. | ||
** Chris: Right, now it's just SO | |||
=== [https://github.com/ | === [https://github.com/geneontology/syngo-go-cams/issues/3 SynGO Updates] === | ||
===Loading widgets into AmiGO=== | ===Loading widgets into AmiGO=== | ||
* [https://github.com/geneontology/amigo/issues/650 Preliminary work indicates that this is not too much work] | * [https://github.com/geneontology/amigo/issues/650 Preliminary work indicates that this is not too much work] | ||
** Before we drop the pathway widget in AmiGO, we should first fix: https://github.com/geneontology/api-gorest-2021/issues/6 | |||
** no blockers for dropping in ribbon | |||
*** do we want to use the AGR slim? | |||
What's next? How high of a priority is this? | What's next? How high of a priority is this? | ||
* Need to decide exactly what we want - needs have a proper project and propose some specs and deliverables (and PI, PO, TL) | * Need to decide exactly what we want - needs have a proper project and propose some specs and deliverables (and PI, PO, TL) | ||
Latest revision as of 12:01, 6 July 2022
Attendees
- Members: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Paul, Chris, Cynthia
- Present:
- Regrets:
GOC meeting
Documentation
Process for review and approval of documentation
Can someone provide more context on this? Cjm (talk) 20:42, 5 July 2022 (EDT)
- Who?
- managers? form a 'documentation committee'?
- How?
- set up calls? via email/google docs + comments?
Distinction_between_'has_input'_and_'with/from'
Ongoing work updates
Google drive move
https://github.com/orgs/geneontology/projects/90
- Suzy to report on status & check on other people
- Chris to move his files
Model copy
- Status
- Latest software updates are now on noctua-dev
- Kimberly is aiming to test later today
Adding SO terms as valid range for 'occurs in' annotation extension
- Curators would like to be able to specify chromosomal regions where MFs occur
- Right now, SO terms are not a valid range for 'occurs in'
- Any reason(s) not to add SO terms as a valid range?
- A few years ago, there was discussion of MSO vs SO that might have had some bearing on this, but that discussion seems to have tailed off.
- Chris: Right, now it's just SO
SynGO Updates
Loading widgets into AmiGO
- Preliminary work indicates that this is not too much work
- Before we drop the pathway widget in AmiGO, we should first fix: https://github.com/geneontology/api-gorest-2021/issues/6
- no blockers for dropping in ribbon
- do we want to use the AGR slim?
What's next? How high of a priority is this?
- Need to decide exactly what we want - needs have a proper project and propose some specs and deliverables (and PI, PO, TL)
MOU draft
- https://docs.google.com/document/d/1T1yW4dPaztjTJIkDPLBi3ob_-IGiqkP-kvGscprYijY/edit#
- update contributors list: http://geneontology.org/docs/go-consortium/
- unify with: http://geneontology.org/docs/annotation-contributors/
- http://geneontology.org/docs/collaborations/
Can this be automated from the yaml?
- CHRIS: YES!!!!