Increase the number of local fields for search and facets
If the library has many specialized and local fields it should be possible to improve the user search without the build-in restriction of 10 locally defined fields. There should not be a limit to use of local fields.
-
Manu_Schwendener
commented
Can this be set to Closed, to release the votes?
-
Manu_Schwendener
commented
Statement by Ex Libris about
PENH-I-28389 Increase number of possible local search/facet fields to at least 20
"Primo 2025 Enhancements cycle: This submission will not be included in the second ballot by the following Product Management statement:
As discussed previously, the current default limit of 10 such fields was introduced intentionally. We observed that many institutions were using these fields - designed for more advanced use cases - instead of simpler and more lightweight alternatives such as local fields for display purposes or the 5xx/9xx fields, which can also be configured for display and search with significantly less overhead.
By setting a default limit of 10, we encourage institutions to evaluate whether a simpler approach might meet their needs before resorting to the more complex normalization rule option. That said, we recognize that some institutions do have legitimate use cases that require more than 10 normalized search fields. As confirmed in our product direction, institutions that need additional fields beyond the default can request an increase via a Support ticket, and these requests will be approved.
At this time, we do not plan to expand the out-of-the-box limit, as the current threshold meets the needs of most institutions while encouraging efficient configuration. However, we remain committed to accommodating specific needs through the existing request process."
-
Manu Schwendener commented
NERS 8130, open for voting now.
-
Manu Schwendener commented
+1