GO-CAM August 23, 2017: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 47: Line 47:
**Adding more relations to CC could potentially generate another point for annotation inconsistency and noise
**Adding more relations to CC could potentially generate another point for annotation inconsistency and noise
*One question: when would curators make an annotation to a CC and when not?
*One question: when would curators make an annotation to a CC and when not?
**If you don't know anything about a protein, but its localization, curators would typically make that CC
**If you don't know anything about a protein but its localization, curators would typically make that CC






[[Category: Annotation Working Group]]
[[Category: Annotation Working Group]]

Revision as of 11:33, 23 August 2017

Zoom URL

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

Agenda

github Trackers

  • Clarification about which one(s) to use
    • noctua - client and middleware code
    • noctua-models - annotation (may be merged with go-annotation)
    • minerva

Table Editor Workbench

  • Chris and Seth will demo the new 'Simple annoton editor' workbench now available in Noctua
  • The table editor allows curators to add, and edit, simple annotons in a table format
  • Annotations entered in the table are automatically added to the Noctua graph editor

Annotation Provenance

  • Review of how attribution is assigned for Noctua annotations
    • de novo annotations
    • imported annotations using function and component companions

Annotating with any UniProtID

  • Use add individual functionality

Minutes

  • On call: Chris, Harold, Karen, Kevin, Kimberly, Pascale, Paul T., Rob, Sabrina, Sage, Seth, Stacia, Suzi

New Noctua Features

  • Curators can submit an issue to the github tracker from the Issues menu
    • Model will be automatically referenced in the github ticket and the github ticket number will be listed in the models menu
  • Simple annoton editor
    • Curators are prompted to add an annoton, but can add distinct parts of the annoton, if needed
    • Will be prompted to add evidence and a reference
      • References are fairly neutral right now - can add PMIDs, GO_REFs - just need to have them be properly formatted (e.g., PMID:nnnnnnnn or GO_REF:nnnnnnnn)
    • Save annoton button adds the annoton to the graphical view, but curators still need to add a title and save their models in the graph view
  • ACTION: Curators need to test the editor and give feedback.

Modeling in Noctua

  • We discussed what the current modeling statements in Noctua actually mean
  • For example, the model currently requires that a molecular_function is associated with a cellular component
  • Is it possible to make a different type of statement in Noctua, or GO in general?
    • For example, a TF is observed in the cytoplasm, but it does not execute its MF there
  • Curators should read Paul T.'s chapter about representation of function in the GO Handbook
  • Can different localizations be annotated using different CC qualifiers?
  • Counter-argument
    • Shouldn't GO just be focused on capturing where activities occur?
    • Adding more relations to CC could potentially generate another point for annotation inconsistency and noise
  • One question: when would curators make an annotation to a CC and when not?
    • If you don't know anything about a protein but its localization, curators would typically make that CC