One last thing to keep in mind is the tradeoffs:
Querying a single all encompasing "text" field will be faster, but the
scoring won't be as relevant. The types of queries dismax generates
can get you better relevance, at the cost of performance.
-Yonik
On 12/5/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: > [We are most interested in always having "title", "description", and a
: > few other
: > fields boosted. We have both user queries of phrases/words as well as
: > "field-specific" queries (eg: "mediatype:moves AND collection:prelinger")
: > so my thought is std might be better than dismax.
it depends ... based on what you've said so far, i would think dismax
would work perfectly for you...
* put the fields you use and their relative weights in the qf param
qf=body^0.5+title^2.0+author^1.5
* put query string you get from the user in the q param
q=tracy+pooh
* put field constraints on other fields in fq params
fq=mediatype:moves&fq=collection:prelinger
* put any score boosting clauses in a bq param (or bf if it's a function)
bq=promote:yes^3
bf=recip(rord(docDate),1,2,3)^2
-Hoss
