Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by YonikSeeley: http://wiki.apache.org/solr/TaskList ------------------------------------------------------------------------------ == Make things presentable to a wider audience (developers, like [EMAIL PROTECTED]) == * Migrate to Apache, change names to solr, make buildable - * let Solr find config via server's cwd by default (for easly setup) + * let Solr find config via server's cwd by default (for easy setup) * Example/Demo * Do they have to build themselves, or can we provide a precompiled WAR & config (and maybe even servlet container?) - * Tutorial on solr website * Clean up straggling CNET links on admin pages, remove links that no longer apply (resin-status, etc) * Minimum Documentation * Feature List on Website - * Tutorial on Website (get them started with the Demo) + * Tutorial on Website (walk through install & demo) + * How to build (if not part of tutorial) + == Near Term Tasks == + * Move webapp from ROOT to solr + * provide alternate way to specify where solr configuration and index directories are (don't have to depend on cwd) + * make indexing easier (it currently requires an HTTP POST of an XML document + * be able to load a text file, with variable delimiters + * point it at a database and give it SQL + * try and clean up css for IE + * clean up the admin pages more, refactor repeated code, remove stuff that doesn't work + * figure out how user can supply a plugin, since we can't depend on the previous method we had used with resin (which added a webapp external directory to the classpath). + * Documentation + * Analyzer components available from the schema + * Document how to set up distribution/replication + * Standard Query Handler: query params + * result XML format + * update XML format + * analysis stuff (available tokenizers and filters) + * Replication + * clean up the scripts, provide an alternate configuration mechanism (in the CNET internal version, + they had macro expansion performed on them) + * Testing + * make more JUnit tests + * try to make the current big testapp more modular, and maybe make a junit test out of it. + + == Ideas for the future == + * Alternate replication strategy that can work on Windows? +
