You can configure different types of matches between keywords and properties or dimension values, from exact matches to various forms of partial matches. The different types of matches are known as match modes.
Match modes control how many records are returned by a record search. They do this by specifying requirements for matches. Depending on the match mode, the records returned must be tagged to properties or dimension values that match the entire search term or only some words in the search term.
To specify the match mode used for keyword searches by your
application, specify the match mode as the value of the
defaultMatchMode property of the
navigationStateBuilder component in
assembler-context.xml. For example:
<property name="defaultMatchMode" value="ALLPARTIAL"/>
Note
Match modes apply to all components of the response, such as results lists, refinement menus, and they may affect spotlighting.
The following table lists the supported match modes and shows the phrases that would match the search term "ultra compact digital" when each of the match modes is selected.
|
Match mode |
Description |
Given the search term "ultra compact digital", returns records where there is a match on: |
|---|---|---|
|
MatchAll (default) |
Returns records that have a property or are tagged to a dimension value that matches the entire search term. |
|
|
MatchPartial * |
Returns records that have a property or are tagged to a dimension value that matches two or more words in the search term. |
|
|
MatchAllPartial* |
Returns records that have a property or are tagged to a dimension value that matches the entire search term If the record search finds no such records, it returns records that have a property or are tagged to a dimension value that matches any possible combination of words in the search term. If the record search finds no such records, it returns nothing. |
or else
or else
|
|
MatchAny |
Returns records that have a property or are tagged to a dimension value that matches at least one word in the search term. |
|
|
MatchAllAny |
Returns records that have a property or are tagged to a dimension value that matches the entire search term. If the record search finds no such records, the record search returns records that have a property or are tagged to a dimension value that matches at least one word in the search term. If the record search finds no such records, it returns nothing. |
or else
or else
|
|
MatchPartialMax* |
Useful only when the search term consists of four or more words. The record search returns records that have a property or are tagged to a dimension value that matches the entire search term. If it finds no such records, it returns records that have a property or are tagged to a dimension value that matches any combination of three words in the search term. If it finds no such records, it returns records that have a property or are tagged to a dimension value that matches any combination of two words in the search term. If it finds no such records, it returns nothing. |
Given the search term "deluxe ultra compact digital", the record search returns records that have a property or are tagged to a dimension search that matches:
or else
or else
or else
|
|
MatchBoolean |
Matches by using a Boolean query expression using AND, OR, NOT, ONEAR and NEAR |
MatchBoolean is useful only for applications whose end users know how to enter boolean-formatted queries. It is not appropriate for eCommerce websites. The MatchBoolean match mode has negative interactions with relevancy ranking, processing rules, and other aspects of MDEX engine query processing. |
* The partial match modes (MatchPartial, MatchAllPartial, and MatchPartialMax) specify that matches occur only when at least two words in the search term match the property or dimension value and that matches can omit no more than two words in the search term.
Note
MatchAllPartial and MatchPartialMax are the most commonly chosen match modes in eCommerce applications.
The following text manipulation features must be configured for use in particular languages:
These features may affect how your Guided Search application matches search terms. For more information, refer to the Oracle Commerce Guided Search internationalization Guide and the Oracle Commerce Guided Search MDEX Engine Developer's Guide.
