1. Configuring Resource Types in Primo
Hello everyone and Welcome to the Resource Types session.
Configuring Resource Types in Primo
Matt Warnock| Customer Success Manager

2. Introductions
Joined the Exlibris Tier 1 Support team in 2014, working with Primo, SFX and Primo Central products.
In 2017 transitioned to the Customer Success Team.
Matt Warnock

3. You will receive tools to help manage your resource type mappings.
Session Description
This session explores configuration of resource types in Primo and provides a framework for customizing Primo’s defaults to the needs of your library.
We will discuss PNX elements related to resource type and demonstrate how to align your e-books with Primo Central books.
You will receive tools to help manage your resource type mappings.
Brief Session Description
In this session we will go over the configurations of the resource types in Primo and will overview the steps to customize Primo defaults to fit your library needs.
We will also review the PNX elements related to the resource types and will learn how to align your local ebooks with Primo Central books.
By the end of this session you will have a better understanding of how resource types work in Primo
And will be able to set up customized resource types that apply to your institution.

4. Objectives and Target Audience
By the end of this sessions you will know, understand and/or be able to:
Understand how resource types work in Primo
Understand the difference between resource types for Primo Central and local Primo records
Configure custom resource types for your institution.
Session Objectives
New and Experienced Customers
Session Target Audience
In this session we will go over the configurations of the resource types in Primo and will overview the steps to customize Primo defaults to fit your library needs.
We will also review the PNX elements related to the resource types and will learn how to align your local ebooks with Primo Central books.
By the end of this session you will have a better understanding of how resource types work in Primo
And will be able to set up customized resource types that apply to your institution.

5. 1 2 3 4 5 Agenda What are resource types in Primo?
Resource types in the PNX 3
Why add a new resource type? 4
Configuration Steps
The agenda for this session agenda includes 5 main sections:
We will talk about what are the resource types in Primo
We will review the resource types in the PNX
We will discuss why to add a new resource type
Go over the configuration steps to add a new resource type
We will see an example of how to align Primo Central and your local ebooks. 5
Example: Aligning Primo Central and Local ebooks

6. What is a Primo Resource Type?
In Primo Front End the resource type is visible to the user in the three main sections.
What is a Primo Resource Type?

7. Resource Types in Primo – Advanced Search
Material Type Pre-filter
First section is the Advanced Search
Here you can see the resource types in the Material Type drop down menu.
This is a prefilter that allows a user to search for the results that match a specific material type.
So if I choose journals the results list will include only records that are defined as journals.

8. Resource Types in Primo
Facets and Results list
On the Brief results page resource type will appear in two sections:
The Resource Type facet and above the title of each record.
The user can refine the results by any of the values that appear under the Resource Type facet and to narrow the results to a specific resources.
In a carefully configured environment, I would expect that the resource type above the title will match the resource that I chose from the facets value.
However this is not always the case as these represented by a different sections in the PNX.
We will see what section applies to which part in the Front End later in this presentation.

9. The “resource type” – separately configurable PNX elements
Basic Concepts
The “resource type” – separately configurable PNX elements
Out of the box list covers commonly used formats
New types can be added
Lets go over some basic concepts related to the Resource types:
1. Resource Type in Primo is a set of separately configurable PNX elements:
These may be the same in each PNX section or can be completely different.
It depends on the normalization rule that is configured for each PNX section and the field in the source record that was used to set that specific rule.
PNX sections for resource types have no inherent relationship
2. Primo does have a set of default Out of the Box resource type values that cover most of the commonly used formats.
These pre-defined types are also used by Primo Central to define the type of the Primo Central records.
3. You can add new resource types based on the needs of you library, but these can only be added for the local records.
Primo Central records have assigned PNX elements for resource type that cannot be changed.

10. Resource Types in the PNX
Now we will review the section of the PNX that associated with the different parts where Resource types is visible to the users in the Front End.
Resource Types in the PNX

11. Key PNX elements for Resource Type - Display/type
The icon above the title corresponds to the <type> field in the display section of the PNX.
In the PNX you will see the value that appears above the icon in the Display section under the <type> field
This is the example of the PNX section.

12. Key PNX elements for Resource Type – Facets/rsrctype
Corresponds to the material type in the facets area
This will be the same value as appears in the Facets section of the PNX:

13. Key PNX elements for Resource Type – Facets/prefilter
Material type prefilter in the Advanced Search corresponds to the prefilter field in the Facets section of the PNX.

14. Search/rsrctype Honorable Mentions
Resource type is also used by Primo in other PNX sections.:
In the search section: searching for the resource type will find results based on this section.
For example, I searched for journal and can see results on the list that have a resource type of journal.
Primo found these records because the resource type field in the search section includes that value.
Search/rsrctype also used for snippet display

15. Used in the Actions menu for Export RIS, RefWorks, etc.
Honorable Mentions
Used to populate the OpenURL used for delivery of electronic resources.
Used in the Actions menu for Export RIS, RefWorks, etc.
Addata/ristype, Addata/format, Addata/genre

16. Resource type values may vary between PNX sections
A Look at the PNX
Resource type values may vary between PNX sections
Display
Search
Use magnifier to show the sections.
Move the Display and search above the PNX section.
Notes:
Since the PNX elements are separately configurable, resource type values may vary between PNX sections.
In this example, the Display and the Search section have the same resource type value.
This will usually be the same in these sections as the default Normalization rules for the search section take the value from the display section.

17. A Look at the PNX – Normalization rule for search_rsrctype
So if you did not customize the rules for the resource type field in the Search section, you will have the matching values in the PNX.
If you did customize them then performing a search for the resource type will look at the values in the resource type search section

18. A Look at the PNX Facets Facets Additional Data
Here you can see that the prefilter and the rsrctype fields in the facets section, have a different value than the ristype in the Add data section.
This is due to the different Normalization rule that was used to created these fields.

19. The Normalization Rules for Display and Addata
As we can see the Normalization Rules for these sections are not the same.
The facets resource type is using the display/rsrctype field together with format_mean mapping table.
However, the addata/rsrctype is using the display/rsrctype with RIStype mapping table.
Since the mapping values are different in those tables the field value that is finally assigned to each PNX field is different.

20. Why add a new resource type?
Why to add a new resource type?
Why add a new resource type?

21. Why add a new resource type?
Represent local collections that don’t fit the pre-defined types
Add granularity
Distinct resource types for audio and video formats
Distinct resource type for libguides/research guides
Unusual collections unique for the institution
Examples
Although we do have an Out of the box list of resource types values in Primo, your local collections might not fit in this pre-defined list.

22. Problem: Video formats are not specific
No indication if the video is DVD, VHS, or something else
Problem:
I searched for the term “rear window”
I get a result that has a type of Video
However, it does not specify if the format is DVD, VHS or maybe something else.
So the potential problem is that searching for a video title, doesn’t provide information on the format of the item.
But maybe my user wants to know immediately whether the video can by played on their device.

23. Problem: No resource type facet after pre-filtering
Another scenario:
I am performing an Advanced search and using a Material Type drop down to pre filter my results.

24. Problem: No resource type facet after pre-filtering
Now looking at the results list, I see that there is no Resource type facet, although the record on the list do have
Different resource types
The circled records for example are CD and video.
Since all audio visual materials have the facets/rsrctype “media” the resource type facet doesn’t display after applying audio visual pre-filter:
<facets>
<prefilter>audio_video</prefilter>
<rsrctype>media</rsrctype>
If we can distinguish between the video formats such as DVD or Blu ray, we would see a resource type facet after applying the Material type pre filter..

25. Goals for new Video Format resource types
Objectives
Goals for new Video Format resource types
Individual records display specific format (DVD, Blu-ray, etc.)
Facet values also display specific format
Pre-filter dropdowns show the more general type “Audio Visual” that contains all relevant formats
So our goal here is:
To display specific format for individual record.
To adjust the facets values to the same formats as the records
Material type prefilter will show a general type “Audio Visual” that will include all relevant formats.

26. Configuration Steps

27. Adding a new Resource Type
Normalization Rule changes
Display/Type field
Mapping Tables Changes:
Normalization Sub System:
format_mean
pre_filter
Static Facets Sub System:
facet_rtype_values
facet_pfilter_values
Code Tables Changes:
Facet Resource Type
Icon Codes
Advanced Media Type
Basic Media Type
This is the general workflow to the configurations.
We will start with the Normalization rules changes to the Display/Type field
Then we will adjust a few related mapping table to accommodate the Normalization rules changes.
Changes to the Code tables.

28. Walkthrough: Adding a new resource type
Identify the field in the Source record to determine the Resource Type
Example:
<controlfield tag="007">vf-cbahou</controlfield
Position 4
First step in configuring this would be to identify the field in the source record that we will use to determine the resource type of the record in Primo.
I am going to use the MARC 007 field and look at the value at position 4.
The specific data source doesn’t matter, as long as it can be used to consistently identify the resource type.

29. Walkthrough: Adding a new resource type – Display/type
Normalization rule for display type
This Rule will check for the character at the position 4 in the MARC 007 field.
Will then go to the type_007_4 mapping table to assign the value to the display/type field in the PNX.

30. Example: Resource Types for Video Formats
The type_007_4 mapping table – created to map video formats
My rule uses a mapping table I created for video formats.
Normalization rule will check character at MARC field 007 position 4 and copy the target Code to display/type.
For my example the character at the position 4 was “b”
So here the target code for that character is “vhs”.
All Mapping Tables > Normalization Sub System > Create a new Table

31. Resource Type: Normalization Rules for other PNX sections
Normalization rule for resource type Facet
Format_mean mapping table used in the Normalization Rules to define the resource type filter in the Facets section.
For the resource type in the facet section, the rule is using the value in the display/type as a source field.
It will then look for that value in the format_mean mapping table and assign the associated value to the facet/rsrctype field in the PNX.

32. Normalization Mapping Tables – format_mean
Mapping Table: format_mean
Add a row for the new resource type
So we previously assigned a type of vhs to the record in the type Display section, so here we need to add that as a source code.
I’ve added the vhs as a Source code and also as a target code, which will be copied into the resource type field in the Facets section of the PNX.
All Mapping Tables > Normalization Sub System > Mapping table: format_mean

33. Normalization Rule for pre_filter facet
Normalization rule for facet pre_filter
Used to define the prefilter facet in the Facets section.
This is for the Advanced search material type.
The Normalization Rules for the pre_filter facet is also using the display/type as a source field, but it will look at the different mapping table to match the values.
If the resource type facet was looking at the format_mean mapping table, pre_filter will look at the pre_filter mapping table.

34. Normalization mapping tables - Pre_filter Mapping table
Mapping Table: pre_filter
Add a row for the new resource type.
So, for our example the Source code is vhs, and the target code would be audio_video.
The reason we are not putting the vhs value in the Target Code is because I want the Material Type prefilter in the Advanced search, to have a general type of Audio_Video.
And the results list to include all Audio_Video materials.
All Mapping Tables > Normalization Sub System > Mapping table: pre_filter

35. A glance at the PNX
<display> <type>vhs</type> <facets> <prefilter>audio_video</prefilter> <rsrctype>vhs</rsrctype>
Display section
Facets section
So at this point what we will see in the PNX is that the display type is vhs

36. Static Facets Mapping Tables

37. Static Facets Mapping Tables
Mapping Table: facet_rtype_values
Defines the facet value for static facets
Resource Type is a static facet
This is the resource type facets.
- facet_rtype_values mapping table - this mapping table uses the code in the record's facets/rsrctype field. It will map the codes in the records' PNX to the labels in the Resource Type facet on the Front End.
The code from the facets/rsrctype field will need to be entered in the Values* column, and the label in the Value Name column.
Example: If the facets/rsrctype field value is "ebooks", this is the code that will go in the Values* column. The label in the Value Name column will be "eBooks".
After adding the values to this table, save, and then click on the Sync button. This will propagate the changes that were made to the applicable code tables.
Check the Code Table in any case, to verify all changes went through well.
Wait until the browser stops looking like it's working after clicking the sync button.

38. Mapping Table: facet_pfilter_values
Static Facets Mapping Tables - facet_pfilter_values – no changes needed
Mapping Table: facet_pfilter_values
Mapping Table: facet_pfilter_values
Defines the facet pre-filter values.
Populates the Basic Media Type code table and the media types on the Basic Search tile in the Views wizard.
Since the normalization pre_filter table maps all video formats to audio_video, no changes are needed for this table

39. Code table: Facet Resource Type
Code Tables
Code table: Facet Resource Type
Facet Resource Type code table - this code table is used to define labels for the Resource Type facet. It should be populated by the facet_rtype_values mapping table.
If a line for "ebooks" was created in the mapping table, the code in the Code column should look like this: default.facets.facet.facet_rtype.ebooks; the label will be in the Description column, and will be identical to the value in the Value Name column in the mapping table, "eBooks".
The language column also plays part here, so if the mapping table contains multiple language lines, they will need to be checked under their applicable languages.

40. Code Table: Icon Codes Code Tables
Determines the text next to the item’s resource type icon

41. Code Table: Advanced Media Type
Code Tables
Defines labels in the Material Type drop down in Advanced Search
Populated by facet_pfilter_values mapping table
Code Table: Advanced Media Type
Advanced Media Type code table - this code table is used to define labels for the Material Type drop down in the Advanced Search. It should be populated by the facet_pfilter_values mapping table, but in case the codes need to be entered manually, below you will find the code's structure.

42. Code Table: Basic Media Type
Code Tables
Defines labels for Material drop down in Basic Search – Classis UI only!
Code Table: Basic Media Type
Basic Media Type code table - this code table is used to define labels for the Resource Type drop down in the Simple Search.
The Material type prefilter in the New UI only available with the Advanced Search, therefore this code table is irrelevant to the New UI.
Below you will find the code's structure.
Example: If the mapping table contains a line for "ebooks", the code in the Code column should look like so: default.search-simple.mediaType.option.ebooks; the label will be in the Description column, and will be identical to the value in the Value Name column in the mapping table, "eBooks".

43. Completing the Process
Deploy all mapping and code tables 
split

44. Completing the Process
Run a No-Harvest Pipe to renormalize data, then Index and Hotswap

45. Configuration Tips
Source code in pre_filter mapping table must be equal to the value in display/type
Add images of the mapping tables and the codes in the PNX.

46. Configuration Tips
Code and mapping tables should maintain consistent capitalization and singular/plural values across resource types
Mapping tables often have corresponding Code tables
Example: facet_rtype_values  Facet Resource Type

47. Customizing the Resource Type Icon
Custom resource types will use the “book” icon in the Classic UI, and the “other” icon in the New UI
Use New and classic UI examples and directions
Unless otherwise configured, custom resource types will use the “book” icon in the Classic UI, and the “other” icon in the New UI

48. Customizing the Resource Type Icon – Classic UI
Upload new icons
Primo Home > Primo Utilities > File Uploader
Add the new ui after this slide

49. CSS changes – Classic UI
Add the following to your CSS file:
.EXLResultMediaTYPEdvd .multipleCoverImageContainer {background-image: url('./icon_dvd.jpg');}
Reference the newly uploaded icons in your custom CSS file

50. Customizing the Resource Type Icon – New UI
Download the Customization Package
Primo Home > Primo Utilities > UI customization Package Manager

51. Customization Package
Unzip the Customization Package
Add customized images to the img folder
Zip and upload the customized package

52. Example: Aligning Primo Central and Local eBooks

53. Primo Central Resource Types
Primo Central uses resource type “book” for electronic books
Most local collections use resource type “book” for physical books
Solution: customize resource type for physical books
PC uses book for electronic books.

54. Physical books will have “pbook” value in these PNX fields:
Customization goals
Display/type
Facets/prefilter
Facets/rsrctype
Physical books will have “pbook” value in these PNX fields:
Faceting by Physical Books will not return Primo Central ebooks
Faceting by ebooks will return local and Primo Central ebooks

55. Normalization Rule Display/Type Section
We will add a normalization rule that will assign type “pbook” to all physical resources that would otherwise be “book”.
Electronic books receive resource type “book” to match Primo Central ebooks
The normalization rules to assign the “book” type to local electronic books will depend on the individual cataloging for each institution.
But what we want to achieve in general is that physical resources will have a resource type of pbook and electronic ones will be assigned type of “book”.

56. Mapping table adjustment
format_mean mapping table
prefilter mapping table
Add “pbook” to:
In order to assign the pbook type to the facets resource type and the facets prefilter

57. Electronic Books: local and Primo Central
A Look at the PNX
Display Section
Physical Books
Electronic Books: local and Primo Central
Here is what the PNX will look like after the type Normalization rules adjustment in the Display section.
On the right is the Physical Book, with type “pbook” and on the right is the electronic book with type “book”.

58. Electronic Books: local and Primo Central
A Look at the PNX
Facets Section
Physical Books
Electronic Books: local and Primo Central

59. Facet Resource Type code table
Code Table adjustment
Icon Codes code table
Facet Resource Type code table

60. Improved Facet Behavior
Faceting by Physical Books no longer returns Primo Central e-books
New ui

61. Improved Facet Behavior
Faceting by e-books returns local and Primo Central e-books

62. Next Steps and Support Resources
Resource Types - All You Need to Know
How to add a searchable resource type to Primo
Preventing FRBR Groups Based on a Resource Type
Additional information on setting up Resource Types in Primo:
Idea Exchange
System Status Pages: Single Tenant ENV / Multi-Tenant ENV
Developer Network
Additional support resources within the ExLibris Ecosystem:
2018 Technical Seminar Presentations (Cross-Product section of CKC)
Mention what it is the audience should do after the tech seminar is over – how they retain what they learned.
Mention links to relevant documentation articles associated with your topic.
Refer to Idea Exchange to provide development ideas for features they think are important to add
Systems Status page
Dev Network
They can find this session – all of the Tech Seminar – presentations in the CKC (link to the article).

63. Q & A
Any Questions?
Any last questions?

64. Session Feedback
We Value Your Feedback! Please complete the brief Session Comment Card:

65. THANK YOU