Use a Field Process to Boost Relevance

You can set up a field process that identifies specific fields in documents and manipulates the weight of terms in these fields if they match the query terms.

For example, use the following procedure to boost the weight of results that contain query terms in their DRETITLE and SUMMARIES fields.

  1. For each field whose content you want to use to determine whether to boost result weights, list a process in the [FieldProcessing] section of the IDOL Content component configuration file that indexes the field and manipulates its term weights. You can use one field process to boost terms in several fields by the same factor.

    For example:

  2. Create a section for each of the processes that you listed, in which you create a property for the process (you define the property later by setting one or more applicable configuration parameters). Identify the fields that you want to associate with the processes.


    The properties that you create must not have the same name as the processes.

    For example:

  3. Create a section for each of the properties and specify configuration settings for each. The Index parameter ensures that Content indexes the fields that you associate with the field process. The Weight parameter determines the factor by which to boost terms in the associated PropertyFieldCSVs fields if they match query terms.

    For example:

  4. Save and close the configuration file.

  5. Restart the IDOL Content component for your changes to take effect.

In future queries, IDOL Server boosts the relevance of the result to the query according to how many times the terms in the result SUMMARY and DRETITLE fields match the query terms.

For example, the following query boosts results whose SUMMARY and DRETITLE field matches the query terms cat and dog:

http://IDOLhost:port/action=Query&Text=cat and dog

This means that these results return in the following order:

Without the boosting to the weight of the SUMMARY and DRETITLE field, Result 2 is the top result, with Result 1 following in second place.

Result 3 does not rank higher than Result 2 in either case. Although its weight is slightly boosted because its SUMMARY field contains one of the query terms, this boost is not sufficient to outrank Result 2.