Make it possible to add or exclude records from the OTB resource display types based on locally-defined conditions
We would like to have more flexibility with Primo VE resource types and the related facet and prefilter values. There are situations in which we would like to be able to add records to an OTB resource display type that don't meet the OTB conditions. For example, for certain textual integrating resources that users are likely to think of as books, we use conditions based on the presence of form/genre headings to add them to the OTB ""book"" display type in Primo BO (e.g., open textbooks that are periodically updated: https://searchit.libraries.wsu.edu/permalink/f/j5jme3/CP71251613210001451). Conversely, we would sometimes like to be able to exclude records from a particular OTB display type.
Here are two possible ways to accomplish this request:
1) Make the OTB resource display type rules locally editable.
2) Use a local field to override the OTB resource display type rule. For example, 999 $a could be defined as the local override field for resource types. Each OTB resource type could be associated with a code that could be added to 999 $a to force that record to have that OTB resource type.
Conditions could be added to the OTB rules as follows in this example for conference proceedings:
--If 999 is null, then execute the standard OTB rule for conference proceedings
--If 999 is not null, then check if 999 = ""conferenceproceeding""
-----If 999 = ""conferenceproceeding"" then mark record as conference proceeding #force include
-----If 999 != ""conference_proceeding"" then do nothing #force exclude
Blake Galbreath
shared this idea
The option to customize the mapping for OTB resource types will be available in May 2023 release.
Best regards,
Yael.
-
Manu Schwendener commented
NERS 7790, round 2 open for voting now.