goodb
commented
6 years ago I'd like to put 2 votes in:
- include a prominent button along the lines of interpret your gene list. This button would lead the user to a best-in-class user experience for conducting interpretation analysis using the Gene Ontology and related knowledge sources. This should be approached through a collaboration with leading developers of relevant statistical methods and in conjunction with developers of other knowledge bases (e.g. Reactome, MetaCyc). The interface should be as hand-holdy as possible - something along the lines of the 'wizard' pattern. This is the best way to explain what the GO is for, the best way to deliver the highest value to end-users, the best way to expose the latest approaches supported by the new GO-CAM structure and the best way to place geneontology.org as the goto place for structured biological knowledge and the discoveries it can enable.
- develop a wholistic visual overview of the ontologies and their relationships that supports hierarchical browsing. Something akin to the zoomable graphical view of the Reactome browser. We need a way to show the basics of what the GO contains at a high level, but then allow the user to zoom in to see details in their area of interest. Right now this is very difficult to do because of the size of the ontologies - even for people that are experienced with ontologies and tools such as Protege.
Hi everyone,
I have been asked to create the future geneontology.org site and in that spirit, I would like to invite you all to provide suggestions, comments and ideas including:
The site will be developed iteratively based on your comments and suggestions and should reflect whenever possible, the identity, uniqueness, the main differentiators and benefits of GO compared to existing scientific resources. For instance, to describe GO, it would probably be relevant to highlight some major statistics: e.g. 700k GO annotations, 2200 GO-CAMs, 35+ labs and 50 ~FTE across the world, number of annotations (resp. GO-CAM) produced / month (...) and to keep track of them over time.
We should also clearly state what we provide (ontology, GO annotations, GO-CAMs), how they relate to each other and how we provide them (downloads, APIs, tools) as well as the documentations and tutorials. Following the talk of Suzi A., it could also be the place to announce GO-related events and how people external to GO could connect GO representatives for instance at conferences.
It also sounds like we should describe and give credits to all major communities using GO. Please voice your opinion on the GO communities you feel are important. If you know a representative of such GO community, it would probably be interesting to gather their contacts to help us describe how and why they use GO and collect use cases representatives of their own (but related) communities.
All suggestions and opinions are welcome, thanks in advance for your participation !