WordPress / WordPress/openverse
Use size and compression as metrics (original #575)
Nobody has claimed this yet.
- 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: aldenstpage
Date: Wed Jul 29 2020
Labels: ✨ goal: improvement,🏷 status: label work required,🙅 status: discontinued
Problem
Images with low resolution or high compression sometimes show up in the first page of results, even with popularity boosting.
This issue blocks on consuming outbound data from the web crawler.
Description
We should heavily weigh down results with low resolution and high compression. Both of these metrics can be distilled into a single "quality_penalty" value (high compression OR low resolution will result in higher quality penalties). The thinking here is that small resolution or high compression are strong indicators that an image is not worth showing, but high resolution and low compressibility do not necessarily correlate with relevance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no implementation files or tests and is blocked on consuming outbound data from the web crawler. Start by confirming whether that crawler data and the required size and compression fields are available; define the quality_penalty inputs and verify that search results weigh down low-resolution or highly compressed images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100