Controlling relevance ranking at the query level
At the MDEX Engine query level, relevance ranking strategies can
be selected to override the default specified for the selected search
interface.
This allows relevance ranking behavior to be fully customized on a
per-query basis. MDEX Engine URL relevance ranking strategy strings must
contain one or more relevance ranking module names. Module names can be any of
these pre-defined modules:
exact
field (useful for record
search only)
first
freq
glom (useful for record
search only)
interp
maxfield (useful for record
search only)
nterms
numfields (useful for
record search only)
phrase (for details about using
phrase, see the section below)
proximity
spell
stem
thesaurus
static (for details about using
static, see the section below)
wfreq
Module names are delimited by comma (,) characters. No other stray
characters (such as spaces) are allowed. Module names are listed in descending
order of priority.
Example 92. Valid relevance ranking strings
The following are examples of valid relevance ranking strategy
strings:
exact
exact(considerFieldRanks)
field,phrase,interp
static(Price,ascending)
static(Availability,descending),exact,static(Price,ascending)
field,MyStrategy,exact
(assuming that
MyStrategy is the name of a valid search interface
with a relevance ranking strategy)
phrase(approximate,subphrase)
