Inform users when wildcard limit has been reached for local records (when still displaying CDI results)
Based on Salesforce case 06390632.
When using wildcards in a Primo search, there is a limit to how many you can use before the search triggers an error that excludes all local records.
This limit is only for local records. The CDI search does not follow the same limitations and will still gather results even if this limit is reached.
If a users crosses the wildcard threshold when searcing in a scope containing only local records, there will be an error message displayed that explains why no results were found. However, if the same search is done in a blended scope (Local + CDI) then this message is not displayed - the local records are just cut while still displaying the CDI records. Only the most attentive and/or experienced users of Primo will notice that the local records are not displaying, while the majority of users will assume that the results presented are the only hits. This skews the search to only show CDI-results and "hides" the local collection that probably has a lot of relevant documents on the subject.
The preferred outcome of this Idea is to give users the error information even if CDI results are displaying. This would improve their ability to A: understand what is presented to them and B: alter the search to find local records.
Fredrik Solvang Pettersen
shared this idea
-
Manu Schwendener commented
Just to add:
I can do the search from
https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Long_combinations_of_Boolean_operators_and_truncated_terms_(wildcards)_return_0_resultsin our Primo VE (local records only) without triggering "No results found"
https://basel.swisscovery.org/discovery/search?query=any,contains,segregat*%20OR%20isolat*%20OR%20supermax*%20OR%20violen*%20OR%20effect*%20OR%20organ*%20OR%20media*%20OR%20influe*&tab=DiscoveryNetwork&search_scope=DiscoveryNetwork&vid=41SLSP_UBS:live&lang=en&offset=0 -
Stacey van Groll
commented
This is a parity issue with VE only having the Zero Results message and not the broad range of informative feedback messages which are in Primo using Back Office.
Although it does sound like there is worse behaviour on VE in not showing any results at all, because BO will still display some local results typically.
It could also be that the results do vary further for other messages for BO, and perhaps they aren't all relevant for VE, given the lucene vs solr aspect.
But definitely there are some instances like for this submission where there are definitely limits in place for VE and yet it has no messages to advise patrons.
See the "Partial results found." message on this page to meet this example: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/End_User_Help_-_New_UI/Feedback_Messages