GO-CAM November 8th, 2017

From GO Wiki
Jump to navigation Jump to search

Zoom URL

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

Agenda

Noctua GitHub Organization

  • Using projects to organize tickets
  • Using milestones for ticket prioritization

Requirements/Roadmap

Noctua Requirements/Roadmap

Attribution

Attribution with GO-CAM exports to GOC annotation files

  • Example model: http://noctua.berkeleybop.org/editor/graph/gomodel:59dc728000000246
  • Each piece of evidence is associated with values for Contributor and providedBy
    • Contributor = orcid
    • providedBy = annotation group
  • Currently, for new annotations, even when the appropriate annotation group for an individual contributor is selected in Noctua, the Assigned By field in the resulting GPAD is populated with GO_Noctua
  • Currently, for annotations imported using the Function Companion:
    • The Contributor field is the curator who imported the annotation into the model
    • The providedBy field is a PURL for the annotation group who originally made the annotation
  • Note that at the model level, all providedBy values are associated with the model (see Model -> Edit Annotations)
  • For legacy models
    • No providedBy field in the evidence

GPAD Outputs

  • ACTION ITEM: on a future GO-CAM call, review the Inference Explanations for some models

Simple Annoton Editor

dealing with blank MF in the simple annoton editor

Extend form to include standard GO-CAM model fields

Bare MF annotation should generate part-of triples

  • Editor enhancements to come:
    • Ability to add basic set of annotation extensions, e.g. has_input for an MF
    • Ability to just add a CC annotation and get the resulting part_of annotation in the graphical interface

Minutes

  • On call: