2012 Solr Preconference - Revision history

Bobbifox at 19:26, 6 February 2012

2012-02-06T19:26:16Z

2012-02-06T18:56:26Z

2012-02-06T18:54:23Z

2012-02-06T18:53:43Z

2012-02-06T18:51:27Z

2012-02-06T18:50:07Z

2012-02-06T18:29:50Z

2012-02-06T18:15:05Z

New page: The Solr 2012 Preconference Notes of Greatness:

New page

The Solr 2012 Preconference Notes of Greatness:

@@ Line 23: / Line 23: @@
 * don't be afraid to use jetty
 * buy this book: http://www.amazon.com/Apache-Solr-3-1-Cookbook-Rafal/dp/1849512183
-* look in comments, dont' necessarily trust the wiki
+* look in comments, don't necessarily trust the wiki
-* dont' use the example, start from scratch
+* don't use the example, start from scratch
-* lucidimagination.com :  run by erikhatcher, solr conference.
+* lucidimagination.com :  run by erikhatcher, solr conference (http://www.lucenerevolution.com/ ).
 * https://issues.apache.org/jira/browse/SOLR
 * http://lucene.apache.org/solr/mailing_lists.html
@@ Line 31: / Line 31: @@
 How to get data in:
-* sunburn in python ( https://github.com/tow/sunburnt )
+* sunburnt in python ( https://github.com/tow/sunburnt http://pypi.python.org/pypi/sunburnt)
 * solrmarc for marc
 * rsolr for ruby ( https://github.com/mwmitchell/rsolr )
@@ Line 38: / Line 38: @@
 How to track results?
 * google analytics
 * put in specific fields for tracking what people search for and click, especially which result number.
 Relevance testing:
@@ Line 45: / Line 49: @@
 * cucumber http://cukes.info/
 * talk to ndushay about stanford's use of this

← Older revision		Revision as of 18:56, 6 February 2012
Line 39:		Line 39:
	* google analytics		* google analytics
	* put in specific fields for tracking what people search for and click, especially which result number.		* put in specific fields for tracking what people search for and click, especially which result number.
		+
		+	Relevance testing:
		+	* types of tests that should always be true (hyphenation should work this way)
		+	* worry about adding too many "result X should appear here"
		+	* cucumber http://cukes.info/
		+	* talk to ndushay about stanford's use of this

← Older revision		Revision as of 18:54, 6 February 2012
Line 5:		Line 5:
	* exact title match fields, boost those. (left and right anchored)		* exact title match fields, boost those. (left and right anchored)
	* create boost fields on index for specific things (like serials, you want to boost)		* create boost fields on index for specific things (like serials, you want to boost)
		+
		+	Things coming down the pike on solr:
		+	* Solr 4.0: hierarchical facets? (do any nightlies work?)
		+	* new way of handling other languages other than CJK

← Older revision		Revision as of 18:53, 6 February 2012
Line 25:		Line 25:
	* http://lucene.apache.org/solr/mailing_lists.html		* http://lucene.apache.org/solr/mailing_lists.html

		+
		+	How to get data in:
		+	* sunburn in python ( https://github.com/tow/sunburnt )
		+	* solrmarc for marc
		+	* rsolr for ruby ( https://github.com/mwmitchell/rsolr )

@@ Line 22: / Line 22: @@
 * dont' use the example, start from scratch
 * lucidimagination.com :  run by erikhatcher, solr conference.
 How to track results?
 * google analytics
 * put in specific fields for tracking what people search for and click, especially which result number.

← Older revision		Revision as of 18:29, 6 February 2012
Line 1:		Line 1:
	The Solr 2012 Preconference Notes of Greatness:		The Solr 2012 Preconference Notes of Greatness:
		+
		+	How to get titles like Nature (specifically, big journals like "Nature") to appear near the top:
		+
		+	* exact title match fields, boost those. (left and right anchored)
		+	* create boost fields on index for specific things (like serials, you want to boost)
		+
		+
		+
		+	How to get started on solr?
		+	* don't be afraid to ask on list
		+	* don't be afraid to use jetty
		+	* buy this book: http://www.amazon.com/Apache-Solr-3-1-Cookbook-Rafal/dp/1849512183
		+	* look in comments
		+	* dont' use the example, start from scratch
		+
		+
		+	How to track results?
		+	* google analytics
		+	* put in specific fields for tracking what people search for and click, especially which result number.