GO-CAM November 8th, 2017: Difference between revisions
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
Attribution
Attribution with GO-CAM exports to GOC annotation files
- Current behavior: 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
- This is true for both the Annotation Preview and the gpad files on Jenkins (http://build.berkeleybop.org/job/export-lego-to-gpad-sparql/lastSuccessfulBuild/artifact/legacy/gpad/)
- 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)
- Legacy behavior: example model: http://noctua.berkeleybop.org/editor/graph/gomodel:586fc17a00000273
- No providedBy field in the evidence or at the model level
- If curator is only affiliated with one group -> providedBy
- What about annotations imported using the Function Companion?
- If curator is affiliated with multiple groups ->
GPAD Outputs
- Annotations groups will consume GPAD only?
- GPAD missing annotations via 'causally upstream of'?
- TEST: causally upstream of - KRC
- With Chris, Jim, and Karen out for today's call, I suggest that we take up these issues again on the next GO-CAM call on November 8th
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: