Manager Call 2016-11-16: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Bluejeans URL=
=Bluejeans URL=
*https://bluejeans.com/588333403
*https://bluejeans.com/588333403
'''Agenda:''' Kimberly Van Auken
'''Minutes:''' Moni Munoz-Torres
'''Present:''' Paul, Kimberly, Suzi, Huaiyu, David H, Chris, Melanie, Moni, Paola.


=Agenda=
=Agenda=
Line 7: Line 13:
*What should be listed on the website?  See http://geneontology.org/faq/where-can-i-find-software-allow-me-make-or-edit-go-annotations
*What should be listed on the website?  See http://geneontology.org/faq/where-can-i-find-software-allow-me-make-or-edit-go-annotations
**The current FAQ on this only specifically mentions CANTO:  http://geneontology.org/faq/where-can-i-find-software-allow-me-make-or-edit-go-annotations
**The current FAQ on this only specifically mentions CANTO:  http://geneontology.org/faq/where-can-i-find-software-allow-me-make-or-edit-go-annotations
<pre>
- For the GO-help issue, see http://jira.geneontology.org/browse/GO-1379
- For historical context, this FAQ was ported over from the old website and last updated on October 14 of 2014.
- The answer we should add to this FAQ is that curators can use Noctua. Given that there is not yet a system / plan in place to open Noctua for the public to contribute annotations, in the mean time we can list Canto, Cacao, Protein2GO, and Pathway Tools (http://pathwaytools.com/)
- Paul: Add comments informing curators that if you have a small number of annotations, you can send them to us, see "here". If you want to start a new effort, let us know “here”.
- Moni: Let’s send them through the decision tree we created and added to the 'Contributing to GO' page! This will allow them to contribute their annotations in the most efficient way.
ToDo: Send Paul contact info for Pathway Tools to be added to registry at Elixir (Melanie did this? MC: yes, done :)).
</pre>
*Note that we also do mention other tools on our FAQ page for performing enrichment analyses for species not included in the drop-down list on the website
*Note that we also do mention other tools on our FAQ page for performing enrichment analyses for species not included in the drop-down list on the website
**http://geneontology.org/faq/how-can-i-do-term-enrichment-analysis-species-not-present-list-amigo
**http://geneontology.org/faq/how-can-i-do-term-enrichment-analysis-species-not-present-list-amigo
<pre>
- Proposal (Paola): general recommendation for endorsing software for use of GOC resources should be that at least one of the members of GOC has used it.
- ToDo: Make the FAQ (http://geneontology.org/faq/how-can-i-do-term-enrichment-analysis-species-not-present-list-amigo) match what’s on the Enrichment Analysis Help Page at http://geneontology.org/page/go-enrichment-analysis
</pre>
*From Minutes of last call?
*From Minutes of last call?
**Genomespace looks a bit too much like an environment in which tools can be linked rather than a registry per se.
**Genomespace looks a bit too much like an environment in which tools can be linked rather than a registry per se.
**We propose to use the Elixir registry assuming we can punctually request to add content. (Melanie sent email to Jon) If it's only a handful of request we can add on a case by case, if it's more than that we can revisit this issue.
**We propose to use the Elixir registry assuming we can punctually request to add content. (Melanie sent email to Jon) If it's only a handful of request we can add on a case by case, if it's more than that we can revisit this issue.
==2016 Year-End Progress Reports==
==2016 Year-End Progress Reports==
*Formats?  
*Formats?  
**Google docs
**Google docs
**Wiki pages
**Wiki pages
<pre>
- ToDo: create Google Doc per institution, and also a separate document where all efforts will be combined and summarized.
- As we ask institutions to prepare their individual documents, ask them to follow a template. Suzi will prepare the templates and add them to this directory:
https://drive.google.com/drive/u/1/folders/0B8kRPmmvPJU3SzNuZ0YzVVJEOWc
</pre>
==Food for thought==
==Food for thought==
*What is the biggest challenge for ontology development?
*What is the biggest challenge for ontology development?
Line 21: Line 53:
*What tool is most urgently needed?
*What tool is most urgently needed?
*How can we be consumers and users of GO ourselves? (eat our own dog food?)
*How can we be consumers and users of GO ourselves? (eat our own dog food?)
<pre>
- Suzi: suggestion to set up main and large-scope goals for the year. Addressing the questions in the agenda. Suzi requests that everyone thinks of these questions.
- Paul suggests that these goals should be organized on the GOC Projects page at https://github.com/orgs/geneontology/projects
</pre>


[[Category: GO Managers Meetings]]
[[Category: GO Managers Meetings]]

Latest revision as of 05:57, 17 November 2016

Bluejeans URL

Agenda: Kimberly Van Auken

Minutes: Moni Munoz-Torres

Present: Paul, Kimberly, Suzi, Huaiyu, David H, Chris, Melanie, Moni, Paola.

Agenda

Annotation Tools

- For the GO-help issue, see http://jira.geneontology.org/browse/GO-1379
- For historical context, this FAQ was ported over from the old website and last updated on October 14 of 2014.
- The answer we should add to this FAQ is that curators can use Noctua. Given that there is not yet a system / plan in place to open Noctua for the public to contribute annotations, in the mean time we can list Canto, Cacao, Protein2GO, and Pathway Tools (http://pathwaytools.com/)
- Paul: Add comments informing curators that if you have a small number of annotations, you can send them to us, see "here". If you want to start a new effort, let us know “here”.
- Moni: Let’s send them through the decision tree we created and added to the 'Contributing to GO' page! This will allow them to contribute their annotations in the most efficient way. 

ToDo: Send Paul contact info for Pathway Tools to be added to registry at Elixir (Melanie did this? MC: yes, done :)).
- Proposal (Paola): general recommendation for endorsing software for use of GOC resources should be that at least one of the members of GOC has used it.
- ToDo: Make the FAQ (http://geneontology.org/faq/how-can-i-do-term-enrichment-analysis-species-not-present-list-amigo) match what’s on the Enrichment Analysis Help Page at http://geneontology.org/page/go-enrichment-analysis


  • From Minutes of last call?
    • Genomespace looks a bit too much like an environment in which tools can be linked rather than a registry per se.
    • We propose to use the Elixir registry assuming we can punctually request to add content. (Melanie sent email to Jon) If it's only a handful of request we can add on a case by case, if it's more than that we can revisit this issue.

2016 Year-End Progress Reports

  • Formats?
    • Google docs
    • Wiki pages
- ToDo: create Google Doc per institution, and also a separate document where all efforts will be combined and summarized.
- As we ask institutions to prepare their individual documents, ask them to follow a template. Suzi will prepare the templates and add them to this directory: 
https://drive.google.com/drive/u/1/folders/0B8kRPmmvPJU3SzNuZ0YzVVJEOWc

Food for thought

  • What is the biggest challenge for ontology development?
  • What is the biggest challenge for annotation?
  • What tool is most urgently needed?
  • How can we be consumers and users of GO ourselves? (eat our own dog food?)
- Suzi: suggestion to set up main and large-scope goals for the year. Addressing the questions in the agenda. Suzi requests that everyone thinks of these questions. 
- Paul suggests that these goals should be organized on the GOC Projects page at https://github.com/orgs/geneontology/projects