Bug 22137 - Koha should warn when maxRecordsForFacets is less than numSearchResults or OPACnumSearchResults
Summary: Koha should warn when maxRecordsForFacets is less than numSearchResults or OP...
Status: RESOLVED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-16 00:04 UTC by Barton Chittenden
Modified: 2023-09-23 09:01 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2019-01-16 00:04:48 UTC
When configuring search results, many libraries will increase maxRecordsForFacets to more than what's found in numSearchResults or OPACnumSearchResults, so that they will show more facets than what is seen on the page. This won't generally cause confusion -- unless a patron is looking for a facet, they tend not to pay attention to them. If, however, numSearchResults or OPACnumSearchResults is increased and maxRecordsForFacets is *not* increased, it is possible to have search results on the page that aren't reflected in the facets, and that will get noticed / cause confusion.

I'm not sure that maxRecordsForFacets should *necessarily* be equal to the larger of these two, but we should at least show a warning.
Comment 1 Katrin Fischer 2023-09-23 09:01:26 UTC
I believe this would need a lot of additional explanation for something that is not likely to cause issues as it neither applies to a libraries using Zebra facets nor libraries using Elasticsearch. Closing WONTFIX.