Changes between Version 2 and Version 3 of SolrInterface

Timestamp:

02/23/10 12:22:11 (4 years ago)

Author:

dread

Comment:

--

SolrInterface

@@ -2 +2 @@
 
 == Use Cases ==
-As an admin of a CKAN instance I want to have the facility to use SOLR, both alongside and as a replacement for the existing full text search in CKAN.
+As a user of a CKAN instance I want to be able to make complicated searches, referencing the data fields.
 
 == Design == 
+
+Search technology - Apache SOLR is selected
+
+Architecture: SOLR to work both alongside and as a replacement for the existing full text search in CKAN.
 
 There are two main options for getting data into SOLR:
@@ -19 +23 @@
 == Tickets ==
 
- * Get a SOLR instance running locally and/or eu1, using basic config.
- * Get indexing and searching working with name and title fields only:
+ 1 Get a SOLR instance running, using basic config.
+ 2 Get indexing and searching working with name and title fields only:
    * Harness one of the three python SOLR libraries to send SOLR Update XML of CKAN Packages (triggered on the command-line). 
    * Write tests for SOLR by sending data with SOLR library and using JSON interface for queries.
- * Get it working with all package fields, optimising the field descriptions in schema.xml. 
- * Trigger the indexing sensibly (as decided above).
- * Provide option to connect CKAN's search WUI to SOLR back-end.
- * Developer docs - description of how to setup SOLR and provide link to schema.xml in developer docs.
+ 3 Get it working with all package fields, optimising the field descriptions in schema.xml. 
+ 4 Trigger the indexing sensibly (as decided above).
+ 5 Provide option to connect CKAN's search WUI to SOLR back-end.
+ 6 CKAN Developer docs - description of how to setup SOLR link and schema.xml.