Annotation Conf. Call 2019-11-26: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
 
(10 intermediate revisions by 4 users not shown)
Line 16: Line 16:
*[https://docs.google.com/document/d/1DZu25YKdH_D3Ics5BSmyvN8IGfGlTcCcwQ4HzviZeWM/edit#heading=h.e6msjvy4rdk9 User Guide]
*[https://docs.google.com/document/d/1DZu25YKdH_D3Ics5BSmyvN8IGfGlTcCcwQ4HzviZeWM/edit#heading=h.e6msjvy4rdk9 User Guide]
*[https://geneontology.github.io/noctua-form/ Draft User Guide with short video]
*[https://geneontology.github.io/noctua-form/ Draft User Guide with short video]
== Upcoming Meetings ==
*Pathways2GO - NYU, December 2nd-4th
*Alliance F2F and SAB - Cambridge, MA, December 9th - 12th


= Minutes =
= Minutes =
*Present:  
*Present: Chris, Colin, Dave F, David H, Edith, Giulia, Harold, Helen, Karen, Kimberly, Laurent-Philippe, Leonore, Michele, Niels, Pascale, Patrick, Penelope, Petra, Sabrina, Seth, Shur-Jen, Stacia, Stan, Suzi A, Val, Ruth
 
== activated_by annotation extensions ==
*Petra suggested we look at some specific examples that may not be immediately amenable to re-annotating with an MF 'binding' term
*Pascale will create a ticket in go-annotation so we can track discussion in the ticket
 
== Pipeline Reports ==
*Will create two tickets based on latest report on snapshot:
**InterPro2GO mapping to 'gocheck_do_not_annotate' term
**More inclusive BP terms to check rule 15 for allowing dual taxon annotations
 
==Noctua Form 2.0 Demo==
*Demonstration of editing in table view and causal relations editor
*Questions:
**Can you change a relation in the table?  This is a little tricky because the form is restrictive in the types of annotations curators can make.  Can discuss further and spec out.
**How will curators search through models to find annotations to fix? The Noctua search and annotation review tools (ART) will be coming on board after Noctua Form 2.0 goes into production.
 
==Upcoming Meetings==
*Next meeting will be the first full week of January, on Tuesday, January 7th
 


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

Latest revision as of 13:59, 26 November 2019

Agenda

Progress Reports

  • Reminder: due mid-December
  • Annotation Group Template
  • GO will generate annotation stats

Pipeline Reports

Noctua Form 2.0 Demo

Upcoming Meetings

  • Pathways2GO - NYU, December 2nd-4th
  • Alliance F2F and SAB - Cambridge, MA, December 9th - 12th

Minutes

  • Present: Chris, Colin, Dave F, David H, Edith, Giulia, Harold, Helen, Karen, Kimberly, Laurent-Philippe, Leonore, Michele, Niels, Pascale, Patrick, Penelope, Petra, Sabrina, Seth, Shur-Jen, Stacia, Stan, Suzi A, Val, Ruth

activated_by annotation extensions

  • Petra suggested we look at some specific examples that may not be immediately amenable to re-annotating with an MF 'binding' term
  • Pascale will create a ticket in go-annotation so we can track discussion in the ticket

Pipeline Reports

  • Will create two tickets based on latest report on snapshot:
    • InterPro2GO mapping to 'gocheck_do_not_annotate' term
    • More inclusive BP terms to check rule 15 for allowing dual taxon annotations

Noctua Form 2.0 Demo

  • Demonstration of editing in table view and causal relations editor
  • Questions:
    • Can you change a relation in the table? This is a little tricky because the form is restrictive in the types of annotations curators can make. Can discuss further and spec out.
    • How will curators search through models to find annotations to fix? The Noctua search and annotation review tools (ART) will be coming on board after Noctua Form 2.0 goes into production.

Upcoming Meetings

  • Next meeting will be the first full week of January, on Tuesday, January 7th