You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.

Class: Aws::Kendra::Types::Relevance

Inherits:
Struct
  • Object
show all
Defined in:
(unknown)

Overview

Note:

When passing Relevance as input to an Aws::Client method, you can use a vanilla Hash:

{
  freshness: false,
  importance: 1,
  duration: "Duration",
  rank_order: "ASCENDING", # accepts ASCENDING, DESCENDING
  value_importance_map: {
    "ValueImportanceMapKey" => 1,
  },
}

Provides information for manually tuning the relevance of a field in a search. When a query includes terms that match the field, the results are given a boost in the response based on these tuning parameters.

Returned by:

See Also:

Instance Attribute Summary collapse

Instance Attribute Details

#duration ⇒ String

Specifies the time period that the boost applies to. For example, to make the boost apply to documents with the field value within the last month, you would use \"2628000s\". Once the field value is beyond the specified range, the effect of the boost drops off. The higher the importance, the faster the effect drops off. If you don\'t specify a value, the default is 3 months. The value of the field is a numeric string followed by the character \"s\", for example \"86400s\" for one day, or \"604800s\" for one week.

Only applies to DATE fields.

Returns:

  • (String) —

    Specifies the time period that the boost applies to.

#freshness ⇒ Boolean

Indicates that this field determines how \"fresh\" a document is. For example, if document 1 was created on November 5, and document 2 was created on October 31, document 1 is \"fresher\" than document 2. You can only set the Freshness field on one DATE type field. Only applies to DATE fields.

Returns:

  • (Boolean) —

    Indicates that this field determines how \"fresh\" a document is.

#importance ⇒ Integer

The relative importance of the field in the search. Larger numbers provide more of a boost than smaller numbers.

Returns:

  • (Integer) —

    The relative importance of the field in the search.

#rank_order ⇒ String

Determines how values should be interpreted.

When the RankOrder field is ASCENDING, higher numbers are better. For example, a document with a rating score of 10 is higher ranking than a document with a rating score of 1.

When the RankOrder field is DESCENDING, lower numbers are better. For example, in a task tracking application, a priority 1 task is more important than a priority 5 task.

Only applies to LONG and DOUBLE fields.

Possible values:

  • ASCENDING
  • DESCENDING

Returns:

  • (String) —

    Determines how values should be interpreted.

#value_importance_map ⇒ Hash<String,Integer>

A list of values that should be given a different boost when they appear in the result list. For example, if you are boosting a field called \"department,\" query terms that match the department field are boosted in the result. However, you can add entries from the department field to boost documents with those values higher.

For example, you can add entries to the map with names of departments. If you add \"HR\",5 and \"Legal\",3 those departments are given special attention when they appear in the metadata of a document. When those terms appear they are given the specified importance instead of the regular importance for the boost.

Returns:

  • (Hash<String,Integer>) —

    A list of values that should be given a different boost when they appear in the result list.