Projects update meeting 2022-06-29: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
Line 33: Line 33:
===[https://github.com/orgs/geneontology/projects/80 Model copy]===
===[https://github.com/orgs/geneontology/projects/80 Model copy]===
* Status
* Status
* Tremayne submitted PR; Seth updated noctua-dev
* Tomorrow morning - Kimberly will systematically test
** This is a large PR with changes to multiple workbenches besides model copy; will require some pretty thorough testing
* Workbenches at 10am PDT Thursday - aiming to make a call on production by then


===MOU draft===
===MOU draft===

Revision as of 08:09, 29 June 2022

Attendees

  • Members: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Paul, Chris, Cynthia
  • Present:
  • Regrets: David

GOC meeting

Only 12 people would attend in person, out of 30 responses: https://docs.google.com/forms/d/14pCJd-tiYtVB0prij_EXc1F80Vqfvnuc0sBe_Gdolf4/edit#responses

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
  1. Dustin will generate stats on the json to ttl conversion
  2. Ask Frank at SynGO to check models on dev, proposed date to get feedback by: June 23rd
  3. Make a syngo-specific pipeline to give them a report
  4. We will put the models on prod no matter what in 2 weeks (whether or not we are able to do this work)
  5. Produce a MOU (see below)

Model copy

  • Status
  • Tremayne submitted PR; Seth updated noctua-dev
  • Tomorrow morning - Kimberly will systematically test
    • This is a large PR with changes to multiple workbenches besides model copy; will require some pretty thorough testing
  • Workbenches at 10am PDT Thursday - aiming to make a call on production by then

MOU draft

Can this be automated from the yaml?

  • CHRIS: YES!!!!

Potential priorities short list

https://docs.google.com/document/d/1TrxTZMRMAS0BCektM79nqvcZq8R3PXEMVWd_CbW-RfI/edit#heading=h.nntgv5th4cph