AmiGO 1 8: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 32: | Line 32: | ||
== Future work in progress (visible in live experimental) == | == Future work in progress (visible in live experimental) == | ||
* | * Migrate core pages over to the new framework | ||
** Front page with completion ([http://amigo.berkeleybop.org/cgi-bin/amigo/amigo_exp?mode=front_page concept]) | ** Front page with completion ([http://amigo.berkeleybop.org/cgi-bin/amigo/amigo_exp?mode=front_page concept]) | ||
* Matrix tool ([http://amigo.berkeleybop.org/cgi-bin/amigo/amigo_exp?mode=nmatrix nmatrix]) | * Matrix tool ([http://amigo.berkeleybop.org/cgi-bin/amigo/amigo_exp?mode=nmatrix nmatrix]) | ||
Revision as of 18:41, 23 November 2009
Status
In discussion--currently this is a close descendant of 1.7. Currently experimental.
Planned Features
- TBD...
- ...
- ...
Done Features
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)
- Migrate core pages over to the new framework
- Front page with completion (concept)
- Matrix tool (nmatrix)
- Coannotation (possible coannotation interface)
- Lucene as general search (concept page)
- graph information as well?
- advanced graph visualizations [1] [2]
- early plugin framework done
- heatmap and random plugin examples
- Workspaces, generalization of sessions (concept)
TBD
- Expand the scope of community annotation (depending on user feedback).
- Switch TE 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)