Annotation Conf. Call 2020-01-21: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 32: Line 32:
*Review (soon-to-be) retired relations:
*Review (soon-to-be) retired relations:
**'has direct input' -> 'has input' for MF
**'has direct input' -> 'has input' for MF
**
**'occurs at' -> 'occurs in' for MF





Revision as of 18:20, 20 January 2020

Agenda and Minutes

  • Present:

Pipeline

  • gp2protein, gp2rna, gp_unlocalized files
    • plan is to retire these from GOC, but want to double-check if there is any use for these files that would require GOC to keep them
  • Announcement sent to go-friends, 2020-01-16
  • Summary of ticket:
    • the GOC pipeline is not using gp2protein files for any data processing
    • gpi files
      • produced as complementary file for gpad
      • produced to populate annotatable entity ontology for Noctua
    • a gene/gene product identifier mapping file would be of use to the broader scientific community, but the exact file format and who should produce and distribute it, remains to be determined
    • form a working group of representatives from the Alliance and other databases/projects to develop a common standard here?
      • GO's gpi file format might be a good place to start
      • UniProtKB also produces an idmapping file as part of the Quest for Orthologs work

Noctua Form 2.0

  • Software updates made to ensure correct environment of all components
  • Additional updates:
    • Entity identifiers now displayed along with labels (particularly helpful when annotating gene product isoforms)
    • Causal relations decision tree (available via Connect on the Noctua form table)
  • Available (SOON!) from Noctua landing page and workbenches menu on graph editor (NOW)
  • Noctua Manual
  • User Guide - Google doc from Berkeley meeting, will be retired
  • ACTION: curators should try out the new form, give us feedback; we will continue to update and organize the documentation to try to help with workflow

Annotation Relations

  • Goal is to review use of relations across annotations (standard and GO-CAM) and the ontology to ensure consistency wherever possible
  • Review (soon-to-be) retired relations:
    • 'has direct input' -> 'has input' for MF
    • 'occurs at' -> 'occurs in' for MF