WordPress / WordPress/openverse

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

Open
#751 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

⛔ status: blocked ✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧱 stack: ingestion server
Dominant language
Python
Stars
380
Forks
290
Avg merge
3h 17m
Merged PRs (30d)
8

Description

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 https://github.com/creativecommons/cccatalog-api/pull/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 https://github.com/creativecommons/cccatalog-api/pull/281#pullrequestreview-230833576 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the migrated issue, the discussion in cccatalog-api#281, and the linked BM25 algorithm documentation. Investigate whether title search can use BM25 with a low k1 value, and consider the work done when the title-field behavior and ranking tradeoffs are evaluated.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.