: That is currently how I have it set up. The agent field is not
: tokenized. However, I need it to be. Here's a concrete example.
: "Dante Gabriel Rossetti" is one of the agents in our system. Users
: should be able to find him by typing either "d", "g", or "r" (case
: insensitive) and they'd see "Dante Gabriel Rossetti (42)" in the
: suggest popup where 42 is the number of documents he's involved in
: given the constraints.
Ohhhh... i was totally missing your point. i thought you had a tokenized
field for searching and you just needed a non tokenized field for facets.
Hmmmmm....
Off the top of my head, i can't think of any cool way Solr cna help you
with this. My best bet on how to solve the problem in general would be an
analyzer that doesn't to any tokenizing, but does create multiple tokens
at the same position after "rotating" all of the words, ie for the
inputtext...
"Dante Gabriel Rossetti"
create the following tokens, all at the same position...
"Dante Gabriel Rossetti"
"Gabriel Rossetti, Dante"
"Rossetti, Dante Gabriel"
...and then keep using TermEnum.
: Here's a concrete multivalued example... a work has two agents "Otis
: Hatcher" and "Erik Gospodnetic". The user types "g" and "Erik
: Gospodnetic (2)" pops up, or types "o" and "Otis Hatcher (1)" pops
that should still work with an analyzer like i described correct? you just
get the part of the agents name the user was type completing first .. not
sure if that's a deal breaker.
-Hoss
