Search Tuning: Minimum Relevance Score Slider, a Search Operators Help Panel, Cleaner Pagination and a Minimum Match Save Fix

Four changes to search tuning and the search page: a threshold that removes weak hybrid matches, a help panel for query operators, a tidier pagination layout, and a fix for custom Minimum Match values that were being silently truncated on save.

01 Minimum Relevance Score

There is a new Minimum Relevance Score slider in Search Tuning. It drops hits whose combined lexical + vector score falls below the threshold, which cleans noise out of facet counts and result totals.

This matters for hybrid search on catalog-style content. Without a threshold, numFound balloons to the entire filter set and facet counts pick up documents the user would never consider relevant.

02 Search Operators help panel

A new Search Operators help button sits next to the Search bar. It opens a panel explaining the "phrase match", +required and -excluded operators with examples, plus a note on why they matter in hybrid search.

Users can now refine a query like +laptop "13 inch" -refurbished and cut through semantic noise instantly.

03 Pagination moved into the results column

The search page pagination layout has been cleaned up. Pagination is now rendered inside the results column instead of drifting to the left under the facet sidebar, and the redundant top pagination block — the one that appeared next to the "Did you mean" spellcheck line — has been removed. Pagination now lives only at the bottom of the results, aligned with the rest of the content.

04 Custom Minimum Match values save again

Custom Minimum Match values were not saving. Any value containing the less-than character, for example 2<95% 5<90% 8<80%, was silently truncated to just the first number, because the global XSS filter stripped the < before the value reached the save handler.

The tuning form now reads the raw request body for this field, so custom mm presets save and apply correctly.