Sorting of Results

Created on 14 April 2022, over 2 years ago
Updated 16 May 2023, over 1 year ago

Problem/Motivation

I have added a sort boost to the "test" content type but the autocomplete still lists other entity/contentypes(with lower boost) above that content type. So it seems the boosting doesnt work correct inside autocomplete.

Boost

Example

The first entry is a "test" conten ttype and the last is too. The results between are other low ranked content types.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Closed: works as designed

Version

1.6

Component

User interface

Created by

🇩🇪Germany marcoka

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇹Austria drunken monkey Vienna, Austria

    Sorry it took me so long to get back to you. Is this still relevant for you?

    If so, did you configure the underlying search to sort results by Relevancy/Score, descending? Only then will the boost have any effect.
    But even then it’s just a boost, not a fixed order. A Frage with lots of occurrences of the search term will still rank higher than a test with just a few occurrences. (A similar problem is discussed in Term Frequency limit processor feature Active .)
    What happens when you search for the same string in the underlying search? Is the sorting as desired then? If not, then this is not a problem for this module, but either for the Search API or for whatever module provides the search backend you’re using.
    But, as said above, everything might be working perfectly but the results might still be as they are, depending on how many times each item contains the word “Sennheiser” (and, depending on other boost settings, in which fields or HTML tags).

    If you always want tests ranked first, then articles, etc., type-specific boosting is not really the right tool for you. You’d instead need to add a custom field with a type-based weight to the search index and just sort on that.

  • 🇩🇪Germany marcoka

    Thank you for the info. I understand now. We can close it then.

  • Status changed to Closed: works as designed over 1 year ago
Production build 0.71.5 2024