Projects update meeting 2022-06-29: Difference between revisions
Jump to navigation
Jump to search
Line 32: | Line 32: | ||
** schedule final round of testing - planned for this week | ** schedule final round of testing - planned for this week | ||
** deploy on prod - end of this week, early next week? | ** deploy on prod - end of this week, early next week? | ||
===MOU draft=== | ===MOU draft=== |
Revision as of 02:18, 29 June 2022
Attendees
- Members: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Paul, Chris, Cynthia
- Present:
- Regrets: David
Ongoing work updates
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.
SynGO Updates
- Actions
- PO: Paul T
- TL: Dustin
- Ask Frank at SynGO to check
- Do we have some SOP? sanity checks?
- David to provide list of MGI checks
- Dustin will generate stats on the json to ttl conversion
- Ask Frank at SynGO to check models on dev, proposed date to get feedback by: June 23rd
- Make a syngo-specific pipeline to give them a report
- We will put the models on prod no matter what in 2 weeks (whether or not we are able to do this work)
- Produce a MOU (see below)
Model copy
- Tasks required before moving to production
- Project meeting tomorrow on the Noctua work benches call, to know:
- schedule final round of testing - planned for this week
- deploy on prod - end of this week, early next week?
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!!!!