Q. Where do Primo VE Resource Types come from? And if our content is not displaying with the correct resource type, how can we fix that?
Table of Contents:
Resource type comes from the bib record. The Resource Type field is constructed based on existing bibliographic fields such as the LDR and 008 or dc:type or dcterms:type fields, in the case of Dublin Core. The Resource Type field supplements (but does not replace) the Material Type field. To see how MARC fields combine to create this review this documentation:
- Rules Used to Create the Resource Type in Alma
- Mapping to the Display, Facets, and Search Sections in the Primo VE Record
If you want to change the default name for a resource type, you can inspect the display code, find the name of the code that you want to change, look it up in your display labels, and make your change. For example, if you want to change the default "Audio CD" resource type to "Audio," you'd inspect the code in your browser, see that the code is mediatype.audio, go to config->discovery->display configuration->labels and look up mediatype.audio in the code lookup box:
Click on the three dots to edit the table and add the name that you want to use.
Lynn replied: The resource type is defined from the LDR and 008, so to change the resource type you would update the bib record(s). Please see https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/050Other_Configuration/Mapping_to_the_Display%2C_Facets%2C_and_Search_Sections_in_the_Primo_VE_Record#Mapping_Resource_Types_in_Primo_VE for information on what values in the LDR and 008 apply.
Other people have wondered how to fine-tune their resource types. You can create 20 local resource types by following these directions. Once you create the type, you'll need to create a set of the records that you want to change and then run the Recalculate Local Resource Types Job to get the change to take effect.
Creating a new resource type adds a new line to the Icon Codes Labels table for that type and you'll need to create a new image for that icon if you want it to display something other than the default sheet of paper icon. Lynn noted "to change the icon, you'll have to add a corresponding icon_Album.png to your img directory in the customization package (see https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/008Primo_VE_User_Interface/010Primo_VE_Customization_-_Best_Practices#Customizing_Image_Files)."
Lynn also noted the limitations inherent in the configuring local resources set-up. You can only match on one field from the MARC record, and all of the data in all of the records that you want to change has to match EXACTLY. For example, GCC tried to set up a local resource for Record Album in order to differentiate it from the Audio CD local resource, since that's an inaccurate description for those records. Here's what the local resources set-up looked like:
The selection parameter of MARC field 300 $a worked for a large percentage of the collection, but it wouldn't work for material that has more than one disc, or if there was any inconsistency in cataloging, such as a missing colon after "disc." There's no way to use wildcards in these fields, and you can only match on one field. There's a suggestion in the Idea Exchange to add the MARC LDR and fixed fields to create resource types: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/35488570-utilize-ldr-and-marc-fixed-fields-006-007-008-in but that is still pending, although it's now marked as "Planned" with the note "This enhancement is planned for April 2019 release." The proposal states, this "way facets could be created for DVDs, Blu-Ray discs and streaming video etc. without workarounds, using standard cataloging."
If you really want to create a foolproof matching point for all records in your collection, you could establish a local field, apply it to all of the records that you want to change, and make sure that you fill it with exactly the same content in each record. You can set up rules to apply these local fields to a specific group of records.
Lynn Higgins notes: "Earlier in this thread was discussion of creating a local field with a singular value which can then be used by Primo VE to assign local resource types. The Alma normalization rules allow for checking multiple values in multiple fields/subfields (i.e., the LDR and 008 and 336) whereas the Primo resource type page requires an exact value in a field. I had attached a document describing the process to create normalization rules and update bib records, but I've modified the document specifically for creating a local field for resource types which has the necessary rule syntax (using UB data as an example). Please see attached."