GO-CAM November 22, 2017

Zoom URL

https://stanford.zoom.us/j/679970729

Agenda

Updates/Discussion on 1.0 Release Milestones

Annotation Attribution in GPAD Output Files

• noctua github ticket #458 - Attribution with GO-CAM exports to GOC annotation files
• noctua github ticket #502 - providedBy should be used in GPAD export
• go-site github ticket #453 - All Noctua curators should have "updated" metadata associated in the YAML file (including group and URI)
• Issue summary: we want to make sure that, in the GPAD files, attribution in the 'Assigned By' field is correctly populated with a curator's annotation group
• Is this a good time to clean house wrt older or test models?
  • Step 1: Curators need to have entries in the groups field of the users.yaml file
    • Some groups still need to review their users.yaml (i.e. they are missing groups and also sometimes even missing orcids):
      • USC
      • UniProt (SIB and EBI)
      • PomBase
      • FlyBase
      • SynGO
      • Xenbase
    • Groups that are okay:
      • BHF-UCL
      • dictyBase
      • MGI
      • SGD
      • TAIR
      • WB
      • Zfin
  • Step 2: Convert any remaining GOC:nn identifiers to orcids
  • Step 3: Determine if, for any models, curators would not want their default groups to be used to populate providedBy value
  • Step 3: Populate providedBy value with appropriate group for each evidence statement 'Contributedby' a given curator
• Question: What is the significance of the model-level providedBy and how is it populated?

Display user and group labels from minerva metadata

• noctua github ticket #380 - Display user and group labels from minerva metadata

Allow negation in Noctua and SAE and in GPAD export

• noctua github ticket #524 - Allow negation in Noctua and SAE and in GPAD export

export-lego-to-gpad-sparql should collate by MOD

• go-site github ticket #431 - export-lego-to-gpad-sparql should collate by MOD

MInutes

• On call: Barbara, Chris, Edith, Harold, Jim, Kimberly, Pascale, Sabrina, Seth