Tagging Configuration

In Kolibri, tagging is used on results to establish groupings in the result sets. This allows mechanisms such as aggregation of different results based on equal tags. Thus tags effectively define the granularity of your results. Let’s say you tag by the query-parameter and you run the evaluation on a range of parameters, all over a set of 1000 queries. Now you will have 1000 single results. To the contrary, in case you have a parameter that can only assume two values, and you tag based on this parameter, you will only have two results. Yet tags can also be combined to refine the tagging further. This is what the extend flag is for. If this attribute is set to true, the tag will extend existing tags. If set to false, an additional tag will be added, which defines a grouping separate from already existing tags.

The currently available taggers are:

  • request tagger
    • by request parameter (every distinct value of the given parameter will have a distinct tag, leading to as many partial results as there are queries)
  • parsing result tagger
    • by length (meaning: number of results)
    • none