2018 NYU SAB Meeting Agenda: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 47: | Line 47: | ||
* Should we push out GO-CAMs into pathway databases like pathwaycommons, ndex, ...? | * Should we push out GO-CAMs into pathway databases like pathwaycommons, ndex, ...? | ||
* Are there other communities that the SAB recommends/suggests we connect with ? | * Are there other communities that the SAB recommends/suggests we connect with ? | ||
=Somewhat random items from managers call that we might want to raise with the SAB= | |||
* Reactome import into Noctua | |||
* Alliance: | |||
** How do the priorities of the Alliance GO working group align with the priorities of the GOC overall? | |||
** What are the most important things for GO to do in the next six months? | |||
'''Discussion''' | |||
* '''GO work that is driven by priorities of alliance (Chris):''' | |||
* Get the GO API up and running (done by Nathan) | |||
* Noctua being rolled out to Alliance members (Noctua is a shared Alliance tool) | |||
* Visualization of Noctua models | |||
* GO ribbon | |||
* GO is not just 'tags on genes' anymore, but also pathways, so we need to coordinate this | |||
* See | |||
** https://docs.google.com/document/d/1WfQRoYLhoEJ-0h3JJQghEtok_DXR_vaIdV3Rti9QYro/edit | |||
** https://docs.google.com/document/d/1oTZwwNHkfA0GY02gX4z38XXGiXX1CojfJKcq5W2aOHY/edit |
Revision as of 04:46, 27 March 2018
date: May 15, 2018
TO DO
- Go over last SAB report, make sure we've addressed everything
- What materials do we need to prepare in advance ?
- Update on priorities/progress
- Metrics of our accomplishments
- Are there any specific questions we have for the SAB?
- Mention relationship with AGR, etc
What we'd like to show
- Noctua 1.0: demo, show groups using it
Important points from the 2015 SAB report
- Organization of the GOC
- Goals
- GOC projects and resources
- QA group
- Tools:
- PAINT
- update functionality, pipeline
- show impact using one of Suzi's TCGA cancer pathways
- Noctua
- Ask David H to report MGI's experience with Noctua
- Capella: paper viewer tool
- PAINT
- Broader community initiatives
- Developer community: R packages for GO (technical outreach)
- Draft some best practices for the developer community (See also paper - reproduciblity with GO PMID:29572502)
- Best practices document for using GO, including GO enrichment (Paul)
- Suggestion to have a “Certified GO tool developer” program with badges (not implement but what do people think ? can we also do that for curators?
- Can GO partner with other enrichment tools beyond panther?
- Make GO data available via web services to help people keep their data up to date (ongoing)
- What is the future of https://github.com/cmungall/term-enrichment-protocol for standardizing among various enrichment tools? (not updated since 2014)
- Create an index of external tools that have been evaluated by key standard metrics and this could translate into a gold star rating system on the GO website -> No resources to do that
- Provide geneontology.org progress/usage metrics, particularly usage of enrichment analysis and compare to DAVID stats - see 2017 progress report for ideas
- GO should provide more information about literature coverage in curation, so that users are better-informed about potential gaps and progress in annotation.
- Outreach group
Questions we'd like to ask
- Should we push out GO-CAMs into pathway databases like pathwaycommons, ndex, ...?
- Are there other communities that the SAB recommends/suggests we connect with ?
Somewhat random items from managers call that we might want to raise with the SAB
- Reactome import into Noctua
- Alliance:
- How do the priorities of the Alliance GO working group align with the priorities of the GOC overall?
- What are the most important things for GO to do in the next six months?
Discussion
- GO work that is driven by priorities of alliance (Chris):
- Get the GO API up and running (done by Nathan)
- Noctua being rolled out to Alliance members (Noctua is a shared Alliance tool)
- Visualization of Noctua models
- GO ribbon
- GO is not just 'tags on genes' anymore, but also pathways, so we need to coordinate this
- See