GO-CAM November 8th, 2017: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 33: Line 33:
== GPAD Outputs ==
== GPAD Outputs ==
*Annotations groups will consume GPAD only?
*Annotations groups will consume GPAD only?
**[https://github.com/geneontology/noctua/issues/330 Issue dealing with converting isoforms correctly to GAF]
*[https://github.com/geneontology/noctua/issues/500 GPAD missing annotations via 'causally upstream of'?]
*[https://github.com/geneontology/noctua/issues/500 GPAD missing annotations via 'causally upstream of'?]
*[http://noctua.berkeleybop.org/editor/graph/gomodel:59bee34700000110 TEST: causally upstream of - KRC]
*[http://noctua.berkeleybop.org/editor/graph/gomodel:59bee34700000110 TEST: causally upstream of - KRC]

Revision as of 11:24, 8 November 2017

Zoom URL

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

Agenda

Noctua GitHub Organization

  • Using projects to organize tickets
  • Using milestones for ticket prioritization
  • Creating new tickets - do we need a different SOP?

Requirements/Roadmap

Noctua Requirements/Roadmap

Attribution

Attribution with GO-CAM exports to GOC annotation files

GPAD Outputs

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: