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

Investigate use of the BM25 algorithm to search image titles (original #288) #751

Open
obulat opened this issue Apr 21, 2021 · 1 comment
Labels
πŸ’» aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: ingestion server Related to the ingestion/data refresh server β›” status: blocked Blocked & therefore, not ready for work

Comments

@obulat
Copy link
Contributor

obulat commented Apr 21, 2021

This issue has been migrated from the CC Search API repository

Author: kgodey
Date: Sat Apr 27 2019
Labels: ✨ goal: improvement,🏷 status: label work required,πŸ™… status: discontinued

The similarity algorithm used to search titles was switched from BM25 to boolean in cc-archive/cccatalog-api#281 to avoid ranking repeated words in titles higher.

We should investigate switching back to BM25 and set the k1 tuning value to a low value just for the title field.

See cc-archive/cccatalog-api#281 (review) and BM25 algorithm docs for more info.


Original Comments:

annatuma commented on Thu Jan 23 2020:

@aldenstpage I'm putting this in Q2 of the backlog, given that there are other search algorithm improvements scheduled for then. Please evaluate if this is a fit for community contributions and if so, label it accordingly.
source

@sarayourfriend sarayourfriend added 🟩 priority: low Low priority and doesn't need to be rushed ✨ goal: improvement Improvement to an existing user-facing feature πŸ’» aspect: code Concerns the software code in the repository labels Dec 16, 2022
@obulat obulat transferred this issue from WordPress/openverse-api Feb 22, 2023
@github-project-automation github-project-automation bot moved this to πŸ“‹ Backlog in Openverse Backlog Feb 23, 2023
dhruvkb pushed a commit that referenced this issue Apr 14, 2023
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@AetherUnbound AetherUnbound added 🧱 stack: ingestion server Related to the ingestion/data refresh server and removed 🧱 stack: backend labels May 15, 2023
@sarayourfriend sarayourfriend added the β›” status: blocked Blocked & therefore, not ready for work label Feb 7, 2024
@openverse-bot openverse-bot moved this from πŸ“‹ Backlog to β›” Blocked in Openverse Backlog Feb 7, 2024
@sarayourfriend
Copy link
Collaborator

This is effectively blocked on #3599, so that we can see what the actual effect of this kind of change would be.

It's also worth considering whether this is really more of a project than a one-off issue, but we'll wait and see what the blocking project gives us in the way of measurement tools and how much more beyond basic a/b testing rigging we'd have to do to actually test this kind of change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
πŸ’» aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: ingestion server Related to the ingestion/data refresh server β›” status: blocked Blocked & therefore, not ready for work
Projects
Status: β›” Blocked
Development

No branches or pull requests

3 participants