[Blacklight-development] solr schema; facetting vs searching

[Jonathan Rochkind]

So I finally have luke up and running to look at this stuff!

I expected luke would give me a way to look through all the indexes and 
tell me the characterstics/settings of each one, but note quite.

It does let me look at each document, and how it's indexed. I expected 
the index called "text" would have all searchable words for each 
document? But when I look at a document in luke, 'text' is empty for all 
of them. "<not present or not stored>".

In general, what I want to figure out next is where those "_text" fields 
are coming from. I could probably hack the indexer and/or the solr 
schema so that every single *_facet field automatically got a 
corresponding searchable *_index field, yes? Any hints as to where I'd 
do this? (Not sure if I'd do it in the indexer code, the solr schema 
file, or both).

Jonathan

Erik Hatcher wrote:
>
> On Feb 15, 2008, at 3:00 PM, Jonathan Rochkind wrote:
>> Perfect, thanks. Before I was asking if you could do a fielded search in
>> the current blacklight. You said, yes, using lucene syntax, if you knew
>> the name of the field you wanted to search. But it sounds like most of
>> the fields you might want to search actually aren't stored in the index
>> in a suitable way at present.
>
> I wouldn't say that.   There are a lot of *_text fields that are 
> surely useful for searching.   And take a look at the schema.xml - all 
> fields are being stored currently so they are 
> retrievable/highlightable from the front-end easily.
>
> Have a look at the Lucene index using Luke 
> <http://www.getopt.org/luke/> or Solr's Luke Request Handler - check 
> out the fields indexed and play around.   There is more there than 
> meets the eye.   Certainly there is much more to MARC than the indexer 
> is extracting currently, though - so lots more can be done.
>
>> If Blacklight doesn't do sortable fields yet.... how does Blacklight
>> sort search results?
>
> Depends - if you're purely navigating by facets, the order is in index 
> order (the order the records were indexed).
>
> However, once you add a full-text query, sorting is by.... 
> relevance!   Imagine that :)
>
>     Erik

-- 
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886 
rochkind (at) jhu.edu