Yeah, that is exactly what I mean. There should possibly be one more
layer on top of that though, right? Lets say someone says 'Oh yeah, I
mean thriller' then you want to show author. You don't want to list
5000 author names right off the bat -- you want to let them pick a
letter like 'author last name starts with a', then display author
names under that, so there is a sort of rule based precedent on when
to return which value list. The flip side is, if there are only 5
authors under thriller category, maybe we should skip the pick a
letter step and just show the author names. What if the todo went
something like
Simple faceted browsing (grouping) support in the standard query handler
get resultset and possible refine fields
limit refine fields to those appropriate based on result set and
precedence of fields
group by field (provide counts for each distinct value in that field)
group by (query1, query2, query3, query4, query5)
Does that make sense? I can be really bad at explaining sometimes.
Corey
PS - This is gonna rock once it starts maturing.
On Mar 7, 2006, at 6:16 PM, Yonik Seeley wrote:
On 3/7/06, Corey Tisdale <[EMAIL PROTECTED]> wrote:
Is there any way to get metadata about a search result off of
this bad dog?
Hi Corey,
From the standard request handler, you can currently only get the
stored fields of documents that matched a query, and the relevancy
score of each document.
I am trying to find a good way to search through
several million items, and I think that being able to aggregate data
about the results would help people refine the search, so if they
search for "legal" I could show a result set with 22000 books but
then also ask if they meant thrillers or test prep or career
planning, etc.
This type of functionality has been implemented with Solr (faceted
browsing), but it's not out-of-the-box functionality - you need to
implement a request handler to calculate and return this extra data.
See here for an explanation on how CNET did it:
http://www.mail-archive.com/java-user@lucene.apache.org/msg02645.html
Simple built-in faceted browsing support is planned though... from
http://wiki.apache.org/solr/TaskList
* Simple faceted browsing (grouping) support in the standard query
handler
* group by field (provide counts for each distinct value in
that field)
* group by (query1, query2, query3, query4, query5)
Would that meet your needs?
-Yonik