[Koha-bugs] [Bug 18316] Add weighting/relevancy options to ElasticSearch

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18316

--- Comment #35 from David Gustafsson <glasklas at gmail.com> ---
Sorry about the late reply.

> Fixed!
Great :)

> I'm not against renaming it. In my mind, boost is most seen as a yes/not
> choice (boosted/not boosted) and not as range of values.

As previously noted, not a big deal, my main issue with it is that boost is
used in lucene/elastic.

> Currently we can set it between 1 and 99. Do you think we need more precision?

In lucene/elastic weight is a decimal number. So I really think it should be a
decimal for that reason. The admin interface should then probably use text
inputs instead of selects with predefined values. There are also situations
where you just want to adjust the relevancy a very small amount to make sure
queries are perfectly balanced and that one does not always dominate the
relevance scoring. With integers this is much more difficult, and you will be
forced to assign boosts to many more fields to get the increased precision.

> We plan to do that later. We believed that adv search allows to search on
> specific(s) field(s). So boosting seems less relevant.

Ok, I adjusted some of the queries for authorities search to utilize fields
better in bug 20589. So perhaps I can include the field boots if I rebase that
patch on this one when it has been merged in Koha.

> See bug 20607 which depend on this one

Aha, ok.

-- 
You are receiving this mail because:
You are watching all bug changes.