Upload
others
View
13
Download
0
Embed Size (px)
Citation preview
Published by Articulate® Storyline www.articulate.com
Primo Administration: Normalization Rules Configuration
1. Normalization Rules Configuration
1.1 Primo Administration: Normalization Rules Configuration
Notes:
Hello, and welcome to this session on Primo normalization rules configuration.
Published by Articulate® Storyline www.articulate.com
1.2 Agenda
Notes:
We’ll start by creating a new normalization rule set from a template. Then we’ll see how to edit a normalization rule
to change how the title of a record displays in the front end. And then we’ll see how to add a new field to a section,
which will allow us to display notes in the details section.
1.3 Creating a Normalization Rule Set
Published by Articulate® Storyline www.articulate.com
Notes:
Creating a normalization rule set
1.4 Getting to the Normalization Rules
Notes:
Here in the Primo Back Office we can create a normalization rule from a template by going to Ongoing
Configuration Wizards > Pipe Configuration Wizard > Normalization Rules configuration.
We can also get to this page by going to Local Data > Normalization Sets in the navigation bar at the top of the
screen.
Published by Articulate® Storyline www.articulate.com
Navigation menu (Slide Layer)
1.5 Creating a normalization rule set
Notes:
Once we’re here, we can see that no rules currently display for the institution. However, if we check the Display
Template NR box, we’ll see all of the template normalization rules that we can use. Notice that I cannot edit these
templates, but I can view them.
Today we’re going to create a normalization rule set from a template. To do so, I would scroll down to the bottom
Published by Articulate® Storyline www.articulate.com
of the screen and select the template I would like to duplicate, in this case, the Alma MARC - Template. Then I would
name my template and click create.
I get a pop-up asking me whether or not to duplicate the set. I click OK and after a moment, the new rule appears at
the top of the list.
Templates displayed (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Bottom of screen (Slide Layer)
Name new rule set (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Duplicate confirmation (Slide Layer)
New rule set created (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.6 Editing and Adding Rules
Notes:
Editing and adding rules
1.7 Reason for creating and editing a rule
Notes:
Published by Articulate® Storyline www.articulate.com
The primary reason to create a normalization rule from a template is so that we can edit it. To understand why we
would want to do this, let’s look at a record in the front end.
Here we have the record Anne of Green Gables. I can see the title Anne of Green Gables, but let’s say that I know that
there’s also a subtitle I’d like to include, and it’s not currently visible.
My next step would be to see if the subtitle is actually in the original MARC record. Looking at the original data
using the PNX viewer, I can see the subtitle I’m looking for in the 245$c.
In order to get the 245$c visible in the front end, I’ll need to edit the normalization rule associated with the display
title section.
PNX Viewer (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.8 Editing the rule
Notes:
Now that we know which section of the rules we need to edit, we go back to the normalization rules sets list and
select edit.
Doing so brings us to the Manage Normalization Rules screen, and by default we see the Control section of the PNX.
Since we want to edit the title field in the display section, I’m going to select ‘Display’ here in the drop down.
Once we’re in the display section, further below on the screen we can see the title field, and we can edit the
display:title field by clicking edit.
Published by Articulate® Storyline www.articulate.com
Control section (Slide Layer)
Select Display section (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Display Section (Slide Layer)
Display Title (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.9 Editing the rule
Notes:
Now we’re almost ready to edit the display:title rule. First, notice that at the top of the screen we can see the
normalization rule set, as well as the section and field we’re in. We can use these dropdowns to navigate to
different normalization rules altogether, or we can go to different sections and fields within this rule set.
In the next section down, we have the option to move to the ‘Advanced’ view. Doing so will allow us to see all of the
conditions associated with the rules below, so we recommend using the Advanced view. Notice that when I click
Advanced the button turns to ‘Basic’ and the rules below show additional information that wasn’t visible before.
Let’s take a closer look at the second rule in the group. The rule states that for the display title we go to the MARC
245, and include the data in the a, b, f, g, k, n, and p subfields. We take that data, remove any of the following
characters from the end, and write it to the display title field. We can see that the rule is enabled, meaning that
when we perform the normalization the rule is in use.
So why didn’t the subfield appear for this record in the front end? Let’s go back to the record for a moment. The
subtitle is in subfield c, but we’re not currently including that subfield in the normalization rule.
Let’s add the subfield c here, and test the rule to see what happens.
Published by Articulate® Storyline www.articulate.com
Advanced view (Slide Layer)
Rule 2 (Slide Layer)
Published by Articulate® Storyline www.articulate.com
PNX (Slide Layer)
Subfields original (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Subfield c added (Slide Layer)
1.10 Testing the rule
Notes:
To test the rule we use the next section below.
First, we select edit record, which opens up a new tab or window.
Published by Articulate® Storyline www.articulate.com
This new tab allows us to edit a sample record, or we can load a test record using the loading prompts here.
I’m going to load the original record in so that I can test it. There - now we can see the file name has changed, and
the 245 section is here on the screen.
When I click test (pause) we’re brought to a screen where I can see the original record on the right and the PNX
section I’m testing on the left.
It’s not perfect, but now the display title includes the subtitle like we wanted it to. However the forward slash at the
end of the title is not taken out - and it would display better if it read title : subtitle.
Configure test (Slide Layer)
Published by Articulate® Storyline www.articulate.com
My record (Slide Layer)
Test result (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.11 Adding a rule
Notes:
Let’s try something else to see if we can improve on this. I’m going to remove the c subfield from the rule group.
This will ensure that the forward slash at the end of the title will be removed.
Then I’m going to create a new source mapping.
Now we can fill this new source mapping, or rule group, in.
Let’s look at what’s been added. The source is still the MARC 245, but this time we are just using subfield c. We are
not applying any transformations here, but we are changing the action behavior from OR to MERGE. Doing this will
merge the data being brought over from this field with the data being brought over by the rule above it. When the
data is merged, we’re going to use a colon delimiter, and put a space before and after that colon by selecting ‘both’.
Let’s test this change and see if it makes a difference.
Published by Articulate® Storyline www.articulate.com
Remove c subfield (Slide Layer)
New rule group (Slide Layer)
Published by Articulate® Storyline www.articulate.com
New rule group filled in (Slide Layer)
1.12 Testing the rule
Notes:
Much better! Now we have our title and subtitle separated by a colon, with no extra punctuation.
Published by Articulate® Storyline www.articulate.com
1.13 Applying the changes
Notes:
Now that we have edited the normalization rule and the test has proven successful, we can save the rule, go back to
the normalization rules sets list, then deploy the normalization rule so the change takes effect.
While these steps ensure the normalization rule is properly updated, we would still need to go to the pipes list, and
renormalize the data by running a No harvesting - Update DS pipe. Then we would need to wait for the data to be
indexed before the changes are visible in the Primo Front End.
Published by Articulate® Storyline www.articulate.com
Normalization Sets List (Slide Layer)
Pipes List (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.14 Adding Normalization Rules
Notes:
Adding a new field to a section
1.15 Reason for adding a new field
Notes:
Published by Articulate® Storyline www.articulate.com
Before we renormalize and re-index the data, there’s another type of normalization rule change we can apply.
Up until now we were making changes to an existing rule, namely the display:title field. Let’s say that there are
some notes in the MARC data that we want to include in the display as well. To do so, we will want to create a new
section in the PNX using one of the local display fields, and identify the data we want to use in the MARC record.
Let’s look at the original MARC data. It looks like the data we want is in the MARC 500 subfield a fields, and it looks
like it’s possible to have multiple instances of the 500$a. For now we’re going to assume that we want to add both
to a new section called ‘Notes’ in the display.
PNX (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.16 Adding a new field
Notes:
Starting in the Normalization Rules Sets list, we click edit, then ensure we’re in the correct PNX section, in this case,
display. Then, we check the display empty PNX fields box.
Scrolling down reveals the empty local PNX fields we can use. It looks like the first empty field is display:lds02, so
let’s edit that one.
Then we’re going to create a new source mapping.
To write the correct data to this new field, I’ll fill in the values. Let’s walk through the changes. The source data
we’re using is from the MARC 500 subfield a. I’ve also added a few transformations to remove the quotation marks
around each entry - it’s possible to add new transformations using the plus sign at the end of the line, and it’s
possible to remove them using the minus sign.
I’ve also defined my action to merge all of the 500 fields, and put a space after each one.
Published by Articulate® Storyline www.articulate.com
Display section (Slide Layer)
Display empty PNX (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Scroll down (Slide Layer)
LDS02 edit (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Rule group (Slide Layer)
Rule group filled in (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.17 Testing the rule
Notes:
When we test this new field rule, we can see the results on the left, and the original data on the right.
1.18 Applying rule changes
Notes:
Published by Articulate® Storyline www.articulate.com
Again, to apply these changes we click save, then return to the normalization rules sets list and deploy the rules.
After the deploy is finished, we would need to go to the pipes list, run the re-normalization pipe, then wait for the
data to be re-indexed.
When we add a new field to the display, links, or facets sections, we also need to make adjustments to other areas
in the Primo Back Office to ensure the new fields are visible in the Front End. Changes to those areas of the Primo
Back Office are covered in the Code Tables and Primo Views trainings.
Norm rule list (Slide Layer)
Published by Articulate® Storyline www.articulate.com
Pipes list (Slide Layer)
1.19 Summary
Notes:
Today we learned how to make a few basic customizations to the normalization rules.
Template normalization rules exist for many different data sources, and creating new normalization sets based on
these templates allows us to make changes to how the library’s data is processed. We can edit and add to existing
data fields to ensure the data displays properly, helpful facets are generated, and searching is optimized. It’s also
Published by Articulate® Storyline www.articulate.com
possible to create new fields in many PNX sections - for example we can create a new field to be displayed and
indexed for search, and we can create our own local facets.
We saw how to test these changes in the Primo Back Office before they are applied, and we learned that applying
changes involves saving and deploying the normalization rules, as well as re-normalizing and re-indexing the data.
All this makes it possible control how the library’s data appears and behaves in Primo.
1.20 Session Review and Quiz
Notes:
Session Review and Quiz
Published by Articulate® Storyline www.articulate.com
1.21 Session Review
Notes:
In this session we covered How to create a normalization rule set, how to edit and add normalization rules, and how to test normalization rule changes
After the brief quiz that begins on the next page, please complete the exercise that is provided in the Knowledge Center where you launched this training. Please refer to the Recommended Articles section for additional information. After finishing the exercise, you can continue on to the next training session in this series.
1.22 Question 1
(Multiple Choice, 10 points, 1 attempt permitted)
Published by Articulate® Storyline www.articulate.com
Correct Choice
X Duplicate an existing normalization rule set, then edit it.
Load in an XSLT sheet
Create one from scratch
Download a template from Ex Libris
Load the data first
Feedback when correct:
In order to create a normalization rule set, you need to duplicate an existing normalization rule
set, then edit it.
Feedback when incorrect:
In order to create a normalization rule set, you need to duplicate an existing normalization rule
set, then edit it.
Notes:
Published by Articulate® Storyline www.articulate.com
Correct (Slide Layer)
Incorrect (Slide Layer)
1.23 Question 2
(Multiple Response, 10 points, 1 attempt permitted)
Published by Articulate® Storyline www.articulate.com
Correct Choice
X The rule must be edited and saved
X The rule set must be deployed
X The data from the data source needs to be re-normalized using a No-Harvest
Update DS pipe
X The data needs to be re-indexed
The data must be deleted and reloaded
Feedback when correct:
In order to see the results of a normalization rule change, the rule must be edited and saved, the
rule set must be deployed, the data from the data source needs to be re-normalized using a No-
Harvest Update DS pipe, and the data needs to be re-indexed
Feedback when incorrect:
In order to see the results of a normalization rule change, the rule must be edited and saved, the
rule set must be deployed, the data from the data source needs to be re-normalized using a No-
Harvest Update DS pipe, and the data needs to be re-indexed
Published by Articulate® Storyline www.articulate.com
Correct (Slide Layer)
Incorrect (Slide Layer)
1.24 Question 3
(True/False, 10 points, 1 attempt permitted)
Published by Articulate® Storyline www.articulate.com
Correct Choice
True
X False
Feedback when correct:
It is possible to load in a record to use for testing.
Feedback when incorrect:
It is possible to load in a record to use for testing.
Notes:
Published by Articulate® Storyline www.articulate.com
Correct (Slide Layer)
Incorrect (Slide Layer)
Published by Articulate® Storyline www.articulate.com
1.25 Thank You!
Notes:
Thank you for joining this session!
1.26 About this Training
Notes:
Published by Articulate® Storyline www.articulate.com
1 (Slide Layer)
2 (Slide Layer)
Published by Articulate® Storyline www.articulate.com
3 (Slide Layer)
4 (Slide Layer)