You can configure the order in which records appear in results lists by creating relevance ranking strategies. You configure separate relevance ranking strategies for record searches and dimension searches.

Configuring a relevance ranking strategy for record searches

You configure a relevance ranking strategy for record searches by editing the following properties of the resultsListDefaultConfig bean in assembler-context.xml:

<property name="relRankKey" value="All" />
<property name="relRankMatchMode" value="ALLPARTIAL" />
<property name="relRankStrategy" value="nterms,maxfield,exact,
  static(product.analytics.conversion_rate,descending)"> 

The three properties have the following meanings:

Configuring a relevance ranking strategy for dimension searches

You configure a relevance ranking strategy for dimension searches by editing the following properties of the dimensionSearchResultsDefaultConfig bean in assembler-context.xml:

<property name="relRankStrategy" value="exact,static(nbins,desc)" />

where exact, static, nbins, and desc are relevance ranking modules. For more information, see Configuring matches.

Configuring a relevance ranking strategy for individual queries

At the MDEX Engine query level, relevance ranking strategies can be selected to override the default specified for the selected search interface. This makes it possible to configure relevance ranking for individual queries.

For information about URL query parameters for relevance ranking, refer to the Oracle Commerce Guided Search MDEX Engine Developer's Guide.


Copyright © Legal Notices