AmiGO 1 8

From GO Wiki
Revision as of 18:15, 29 April 2010 by Sjcarbon (talk | contribs)
Jump to navigation Jump to search

Status

Currently experimental.

New features

  • Centralized internal testing (kappa)
  • GOOSE integrated into framework (GOOSE)
  • Rapid searching (live search)

Current work

Frontend

  • Try and lighten up on some of the POSTs in AmiGO to make searches easier to track
  • Finish new term details page--find way to avoid confusion with old view
    • Try different icons
    • Try dynamic lines to highlight ancestors
    • Explore text-based views
  • Re-expose the buckets in slimmer
  • Update docs to most recent version (final item)

Backend

  • Work out CVS to SVN transition one way or another (this will be done by June first; give production plenty of heads-up during transition)
  • Setup production to produce their own indexes locally (don't want to shift db generation; will probably juggle frontend servers while producing indices (so much more benchmarking probably not needed))
  • See if association search index can be added/generated in a timely manner (talk to Tanya).

Bugs

  • Resolve Val's slimmer bug
  • Check and make sure that E. coli is done consistently (done first pass to 83333; need to check with Jim/upstream)

Experimental (beta) features

  • Matrix tool (nmatrix)
  • Integrate new RG views from Sven (likely deferred) (phylotree)
    • Check licensing of JS tree viewer (ntree)
  • Relation filtering (may be bumped to deferred)
    • Start with term enrichment and work out
  • Term request client for SF (AKA ART) (XP term request)
    • Could this be better done in wiki?

Deferred (alpha) features

Plans and TBD

  • Migrate peripheral pages to new framework (ongoing)
  • Migrate core pages over to the new framework (ongoing)
  • Cross-product and inter-ontology link support (may be punted until following release, but we will start on necessary infrastructure changes)
  • Organizing annotation results by qualifier
  • 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)