Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weight of titles #115

Open
karindalziel opened this issue Jun 25, 2021 · 1 comment
Open

Weight of titles #115

karindalziel opened this issue Jun 25, 2021 · 1 comment

Comments

@karindalziel
Copy link
Member

karindalziel commented Jun 25, 2021

In archives with an item and things about that item, for example the story "The Wife of His Youth" and "Review of the Wife of His Youth", the actual item gets buried in search results.

One proposed solution would be to add a "search boost" field to elevate the rankings or particular items (perhaps items with a particular author, etc)

On the schema and datura side, we would need to add the field, on the API side, we would need to have it recognize that field to boost results (see: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-boost.html)

We will also need to figure out how to handle multiple languages, so one search boost field per text language field?

Related to CDRH/chesnutt#87

@jduss4
Copy link
Contributor

jduss4 commented Jun 27, 2021

Pardon my intrusion. I agree it looks like to use that boost on a text field you'd have to be using something like title_text_en and title_text_es in order to get the value out of it, unless if there's some way to include keyword fields in a text search.
You'd also need to change it somewhere in the orchid bridge default settings, the orchid config, or have the API automatically assume that any text searches should include those new text fields with the boosted value. I would think some combination so that you could override the settings would be good, because I feel like multiple languages could get kinda funky unless if orchid bridge was smart enough to know "oh, you're searching text_es so you must also need title_text_es or something like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants