Annotation Conf. Call 2017-12-12

From GO Wiki
Revision as of 12:47, 12 December 2017 by Vanaukenk (talk | contribs)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Meeting URL

Agenda

Infrastructure

  • Report on missing orcids and groups in users.yaml file
  • users.yaml
  • groups.yaml
    • Some groups still need to be added, e.g. UniProt (GOA, Swiss-Prot)
  • Please keep in mind that the report is generated as part of the new build and a new attempt is made every night.
  • This means that:
    • 1) if the load fails the report may not be there (which is a good thing)
    • 2) there will times every day during regeneration when the report is not yet there

github review

  • go-annotation tracker is used for issues and project management related to the annotation working group
  • All curators who need to work on an issue should be listed in the Assignee field
    • Remove your name from the list when you've addressed or complete the work
  • Types of issues:
    • Annotation review
    • PAINT annotation/family review
    • Keyword mapping questions, e.g. InterPro2GO
    • Questions about annotation practice
    • Requests/proposals for annotation guidelines
  • Use of labels
    • Please always add a label to your issue
    • Trying to simplify the list of labels
    • Removed some that were overlapping, not applicable to this repo
    • Would like to move from using group labels to tracking submission via author
      • is:issue author:vanaukenk
  • Notifications
    • Not watching - will be notified when you are specifically mentioned (@yourname) or comment
    • Watching - will be notified of all activity

Annotation Review

Signaling Project

Canonical Wnt Signaling Pathway

HTP annotations

  • Continue to check and update evidence codes as needed.
  • New HTP paper google spreadsheet for potential HTP papers annotated using the GO:Sheet laballed:"Over_40_per_evidencecode"

https://docs.google.com/spreadsheets/d/11xExGJfj_39xPQUGkam3Xvtd6dtZ5DfANXhM2ZtDYB0/edit?ts=58d39700#gid=2144791301

  • https://github.com/geneontology/go-annotation/issues/1655
  • Generated by splitting out the experimental evidence codes and collating the papers with >40 lines of annotation per paper/per evidence code.
  • For most contributors, I have been able to do this directly from the GAF they submit to the GOC so that any DB-specific refs are included and any other sources that are incorporated into the anointed set.
  • For a few others, indicated on the sheet, had to download them from QuickGO.
  • Note: As they have been separated on evidence code, same paper may feature on separate lines.
  • Note: Only equivalent evidence codes to HTPs looked at (EXP, IDA, IEP, IGI, IMP).

Progress Reports

Next Call

  • Tuesday, January 9th, 2018

Upcoming Working Meetings

  • Docathon - Berkeley, January 22nd - 26th
    • Annotation, Pipelines
  • Ontology Editors - Denver, February 12th - 16th
    • github backlog
    • Please review old tickets and comment or close, as needed

Minutes

  • On call: David H., Edith, George, Giulia, Harold, Karen, Kevin, Kimberly, Midori, Paul T., Petra, Rob, Sabrina, Shur-Jen, Stacia, Stan, Tanya

Infrastructure

  • Nearly all current curators and users are okay wrt the users.yaml file
  • UniProt will be sorting out this week how they should be represented

github review

  • Reviewed tracker use, labels, assignees, watching
  • Need to confirm what is the best way to track issues according to group