Difference between revisions of "2012 GOC Meeting Caltech"

From GO Wiki
Jump to: navigation, search
(Biological Representation - Paul T)
Line 6: Line 6:
 
* PAINT annotation progress
 
* PAINT annotation progress
 
* LEGO status: current model and how it relates to col. 16 extensions
 
* LEGO status: current model and how it relates to col. 16 extensions
 +
** 'annoton' data model (Chris and Paul)
 +
** Protege plug-in for annotation (Heiko)
 +
** Current examples (Kimberly and David)
 +
** col. 16 extensions and LEGO (Paul, Chris, Jane, Rachael)
 
* Automated ontology checks [[Jenkins]]
 
* Automated ontology checks [[Jenkins]]
 
* External ontologies
 
* External ontologies
Line 18: Line 22:
 
** Architecture
 
** Architecture
 
** Status of difference services
 
** Status of difference services
** 'annoton' data model
 
 
** WormBase experience with protein2go
 
** WormBase experience with protein2go
** Protege plug-in for annotation
 
 
* Automated annotation tools
 
* Automated annotation tools
 
** Should we make more use of text mining pipelines?
 
** Should we make more use of text mining pipelines?

Revision as of 10:14, 19 September 2012

Goals

Biological relevance - Paul S

  • GO as a biological reference (critique?)
  • Objectives for next quarter (or until next meeting?)

Biological Representation - Paul T

  • PAINT annotation progress
  • LEGO status: current model and how it relates to col. 16 extensions
    • 'annoton' data model (Chris and Paul)
    • Protege plug-in for annotation (Heiko)
    • Current examples (Kimberly and David)
    • col. 16 extensions and LEGO (Paul, Chris, Jane, Rachael)
  • Automated ontology checks Jenkins
  • External ontologies
    • Report on migration of NIF subcellular AO to GO-CC (Jane)
    • BFO 2.0 - do we comply with BFO and split part_of into 2 relations?
    • CHEBI
    • CL
  • Objectives for next quarter (or until next meeting?)

Tools - Suzi

  • CAT
    • Architecture
    • Status of difference services
    • WormBase experience with protein2go
  • Automated annotation tools
    • Should we make more use of text mining pipelines?
    • Wormbase CC tool
  • PAINT
  • Enrichment tool improvement plans
    • Standardize interface to tools & allow plug in play eg via Galaxy
    • Promote tools that provide access to latest GO, work with those that don't. See GO Tools Registry
    • Getting enrichment tools to leverage ontology and annotation improvements
  • Objectives for next quarter (or until next meeting?)

Annotation Production - Judy

  • Term requests
    • Current rate of additions & rate of clearance
    • TermGenie
  • GO Help
    • Move to JIRA
    • any new approaches?
    • biostars etc
    • Tweeting?
    •  %of questions we can answer with available tools?
  • Submissions from outside groups
    • Web page with instructions (Rama)
    • Future work here... (who has been in contact? any active outreach?)
  • Automated annotation production
  • Project-led GOC annotation efforts (Paul S)
    • New reporting page
    • Observations/Comments
  • Move to SVN
  • Objectives for next quarter (or until next meeting?)

Web - Cherry

  • Licensing issues
  • User interfaces
    • GO-Mine/Enrichment
    • AmiGO
    • QuickGO
    • Galaxy?
    • New logo (just tell us)
  • GO Website
    • Need a webmaster?
    • Switch to Drupal? (Seth)
  • Dissemination
    • Publication plans
    • Meetings to attend
    • New training material
  • GO Tools Registry
  • GO & Linked Data
  • Objectives for next quarter (or until next meeting?)