AmiGO 1 7 (Archived): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 26: | Line 26: | ||
** direct access jump or search | ** direct access jump or search | ||
** available on all labs pages | ** available on all labs pages | ||
** available on | ** available on Firefox Add-Ons site | ||
= Current work = | = Current work = |
Revision as of 18:08, 28 April 2009
Status
Currently experimental.
Planned Features
TBD
Done Features
- new/easy graphviz-style graph generation [1]
- RESTful API (as yet unpublished)
- basic and advanced inputs (AmiGO_Manual:_Visualize)
- all graph displays backed by same backend
- interactive and static everywhere
- term enrichment
- browser
- homolset
- visualize client
- Google analytics throughout AmiGO and associated sites
- optional file to add tracking
- now used on AmiGO Labs, rehomed GOOSE, news4go
- Basic lucene index generation
- OpenSearch AmiGO_Manual:_OpenSearch
- gene product and term completion suggestions in web browser
- direct access jump or search
- available on all labs pages
- available on Firefox Add-Ons site
Current work
Deferred features
- Organizing annotation results by qualifier
- Term request client for SF (AKA ART)
- could this be better done in wiki?
- Cross-product and inter-ontology link support (may be punted until following release, but we will start on necessary infrastructure changes)
- xprods in 1.5
- xprods in 1.6
- Examples (all using experimental bp_xp_mouse_anatomy xps):
- heart
- heart development
- TAZ orthoset (notice heart in top right corner)
- Examples (all using experimental bp_xp_mouse_anatomy xps):
Future work in progress (visible in live experimental)
- Coannotation (possible coannotation interface)
- More Lucene (concept page)
- speed
- complex search
- boolean
- distance
- weight
- graph information as well?
- advanced graph visualizations [2] [3]
- bi-ax test [4] (defunct?)
- Workspaces (generalization of session)
TBD
- Expand the scope of community annotation (depending on user feedback).
- Switch caching over from page render caching to data caching (currently evaluating sqlite3)
- RSS update on terms and gps (could be tied to GONUTs for timeliness?)
- looking at other ways to supply search results (perl clucene (apache) vs. lucene (tomcat) vs. solr (tomcat or jetty) vs. perl/xapian (apache) vs. ruby/ferret (apache))
- look at ways of solving "*ase" problem(if it is) (e.g. reverse indexing and merge results)