The following table lists and briefly describes the relevance ranking modules.
Relevance Ranking Module | Description |
---|---|
| Records that are included in the search results because of an exact match on the shopper’s query are ranked above records that are in the search results because of partial matches. Thus, exactly matching records appear before partially matching records. |
| Records are ranked according to their priority in your search interface. |
| Rank based on how close the match is to the start of the field. |
| Rank based on how frequently the terms appear in the matched data. |
| Rank single-field matches above cross-field matches. |
| Weight by whether interpretation is used to get match. |
| Rank based on field priority; equal weight to cross-field matches. |
| Rank based on the number of terms found. |
| Rank on the number of fields that completely match the query. |
| Rank on phrase, substring, or other; configurable. |
| Rank based on how close the multi-terms are to each other in the matches. |
| The |
| The |
| The |
| The |
| The |
Understand which modules are the more useful for commerce applications
The most commonly used modules in commerce applications are:
phrase
(all options turned on)glom
maxfield
static
The following modules are less commonly used:
field
wfreq
The following modules are not ordinarily useful in commerce applications:
first
interp
nterms
proximity
stem
thesaurus
Oracle recommends against the use of the following modules:
exact
, because of its effect on performance. Usephrase
instead.freq
, because it adds up the counts of every word, affecting performance.