The re-run the report button is coded with the path to the prompted report in Analytics. It is created by adding a narrative view and some HTML code.

1. Before you create this button, make sure your Analytics report is in the folder where it will live from now on. If you decide to move it, you will need to re-code the button. You also want to make sure your prompts are working before you code the button in.

(How to configure a basic prompt for your report: https://knowledge.exlibrisgroup.com/@api/deki/files/48622/How_to_create_a_prompt_in_an_Alma_Analytics_report.pptx?revision=3) Or, go to https://knowledge.exlibrisgroup.com/Alma/Training/Extended_Training/Presentations_and_Documents_-_Analytics#Advanced_-_Prompts and click on the How to create a prompt in an Alma Analytics report link.)

2. From your Analytics folder, use “Open” to run your prompt, save the path to Notepad. You do not want to use edit, because the path will not include the prompt.

3. Copy the full path at the top of the screen and paste it to Notepad.

4. Copy and paste the path after the saw.dll? to Notepad below the first path. You don’t want to erase the initial path in case of copy and paste errors.

5. Paste in this HTML code to Notepad below the path you recorded:

<p align=”left”>

<button onclick=”window.location.href=’saw.dll?add your path here'”>Rerun the report</button></p>

6. Copy the path from step 4, and replace the add your path here text in the HTML code with the path. Keep your Notepad open and return to Alma Analytics

7. Click “Edit” to edit your report. Filter on a single element in your report and run it, because it will make the next steps easier.

8. Go to the top level menu and click on the symbol that looks like a bar graph with a plus sign. The is the New View dropdown menu. Click New View->other views->Narrative. 

9. This will create the narrative view at the bottom of the report. Click and drag it above the table view. (The part of the report containing your results)

10. Click on the pencil to the right of the grey “Narrative View” line, this will open the narrative view configuration. 

11. Click on the box to the right of Contains HTML/JavaScript/CSS Markup – a checkmark should appear.

12. Copy the Notepad code from step 6. Paste it into the “Narrative” box in the Narrative View configuration. You will notice a lot of repeat boxes. This is normal.

13. Click into the box to the right of Rows to display, your cursor should be blinking.

14. Type in 1, then click somewhere outside the box, you should now only have one button appearing.

15. Click on Done in the upper right corner. 

16. This will take you back to the results window. You should see a single button with the “Rerun the report” text on it. Save your report.

17. Test to make sure the button works. When you click on it, you should be taken to your prompt.

18. Now that the report works, you just need to remove the filter. Click on “Edit”.

19. Remove the filter. Save your report.

20. Now when you put your report in a widget, the button will appear. (Directions on how to add a widget: https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Adding_an_Analytics_Widget_(e.g._Report)_to_the_Home_Page)

21. Click on the rerun button and your prompt will appear.

The post How To Format a Prompted Report to Run in a Widget appeared first on Ex Libris Developer Network.

How It Works

When triggering a new job, you’ll now find a new toggle:

When checked:

1. The node submits the job to Alma.

2. It polls the Alma Job Status endpoint in the background.

3. Once the job reaches a terminal state (Completed / Failed / Cancelled), it returns that final result to your workflow.

Why Use Await Job Completion?

• No more external polling loops
• Cleaner, easier workflows
• Immediate feedback from the job

Adjusting the Timeout

Because some Alma jobs can take longer than an hour to complete, it’s important to ensure your LibOW execution settings allow enough time.

You can configure the timeout on the workflow:

Path to Configuration
Settings > Timeout After

The post Library Open Workflows – Await Job Completion for Alma Job creation appeared first on Ex Libris Developer Network.

When Yoel was here to deliver training in January, he told us that we can remove the “(Online)” from the end of the title in the Primo full view.  It seems to be appearing because it is in the 130 field of the bibliographic record.   We did not have time to configure and customize the normalization rule together with Yoel.  Can you please explain to us how we can do it?  I do have some familiarity with the Primo VE normalization rules, but I do not know how to remove a certain string of text from a title.  Yoel said that you can help us and we should send clear examples.

Here are two examples.  You can see that in the MARC21 bibliographic record the 130 ends with “(Online)” and then the 130 displays as the title and it includes the “(Online)”.  We want to remove it.

Example One of Two

Title “Journal of literary semantics” appears like this in Primo:

Brief Results:

Full View:

And here is the MARC21 Bibliographic record where we see that the “(Online)” is coming from the 130 field:

Instead of

Journal of literary semantics (Online)

We want it to appear without the “(Online)” as follows:

Journal of literary semantics

Example Two of Two

Title “Beiträge zur Geschichte der deutschen Sprache und Literatur” appears like this in Primo:

Brief Results:

Full View:

And here is the MARC21 Bibliographic record where we see that the “(Online)” is coming from the 130 field:

Instead of

Beiträge zur Geschichte der deutschen Sprache und Literatur (Online)

We want it to appear without the “(Online)” as follows:

Beiträge zur Geschichte der deutschen Sprache und Literatur 

Answer:

We need to change the Primo VE normalization rule for the title and replace the string “(Online)” with nothing.

This basically means that we want to remove the string “(Online)”.

Let’s first see what the “Title” field above is doing when it displays the fields.  We can see this by looking at the corresponding Primo VE Normalization Rule.

Go to “Discovery > Display Configuration > Manage display and local fields”.

• If you do already see a row with “Display label” “Title” then edit that row.
• If you do not already see a row with “Display label” “Title” then add it as follows: Add field > Add Display Field > In ‘field to edit’ choose ‘Title’

Edit the “MARC21 normalization rule for display”

Add the following line to the normalization rule:

remove string (TEMP"1","\\(Online\\)")

Here is the rule with the new line:

Make the change and click “Save”

After clicking “Save” click “Back” and then “Apply Rules”

Check the display for the first example now in Primo VE and see that the “(Online)” no longer displays as part of the title:

Before	After

Check the display for the second example now in Primo VE and see that the “(Online)” no longer displays as part of the title:

Before	After

The post How to use a Primo VE Normalization Rule to remove the text (Online) from the title appeared first on Ex Libris Developer Network.

• PNX stands for “Primo Normalized XML”.
• It is the standardized format that Primo uses internally to store and index bibliographic records from various sources.
• A PNX record is the underlying data structure that powers how resources are displayed and searched in the Primo interface.

Note: PNX historically stood for “Primo Normalized XML” because the records were originally in XML format.  However, there has been a transition to using JSON as the underlying format in more recent versions of Primo VE and Primo VE NDE.

Why view a PNX record?

Viewing a PNX record is like looking “under the hood”.  Most end users never need to see it, but it is sometimes essential for the people maintaining and optimizing the system.

Library staff and administrators typically view PNX records for troubleshooting and configuration purposes.

These troubleshooting and configuration purposes may include:

• Diagnosing display problems – if a record isn’t displaying as desired in the user interface, viewing the PNX shows exactly what data Primo has available and how it’s structured, helping identify if the issue is with the source data or the display configuration
• Troubleshooting search issues – when records aren’t appearing in expected searches, examining the PNX reveals which search fields contain what values and whether the data is properly indexed
• Understanding normalization – to see how Primo has transformed the original source metadata (for example MARC) into its normalized format, which helps understand what information might have been lost or transformed
• Configuring display and indexing – when setting up custom display fields or search configurations, administrators need to know the exact PNX field names and see what data is available in those fields
• Debugging enrichment or deduplication – to verify whether external enrichment services have added data correctly or to understand why certain records are (or are not) being grouped together as duplicates

The syntax to view a PNX record?

In the example here we are using Primo VE NDE.  The same syntax exists for Primo VE (for those users who have not yet moved to Primo VE NDE).

To view the PNX

1. Search Primo for a record
2. From the brief results click the title
3. Add the following string to the end of the URL: &showPnx=true and hit “Enter”
4. The PNX will open in a new tab

For example this URL:

https://exldeveu00.primo.exlibrisgroup.com/nde/fulldisplay?query=%20It%27s%20not%20a%20glass%20ceiling,%20it%27s%20a%20sticky%20floor&tab=LibraryCatalog&search_scope=MyInstitution&searchInFulltext=false&vid=EXLDEV1_INST:Alma_NDE&lang=en&docid=alma99653190500121&adaptor=Local%20Search%20Engine&context=L&isFrbr=false&isHighlightedRecord=false&state=

Will change to this to view the PNX:

https://exldeveu00.primo.exlibrisgroup.com/nde/fulldisplay?query=%20It%27s%20not%20a%20glass%20ceiling,%20it%27s%20a%20sticky%20floor&tab=LibraryCatalog&search_scope=MyInstitution&searchInFulltext=false&vid=EXLDEV1_INST:Alma_NDE&lang=en&docid=alma99653190500121&adaptor=Local%20Search%20Engine&context=L&isFrbr=false&isHighlightedRecord=false&state=&showPnx=true

From the brief results click the title:

Add the following string to the end of the URL: &showPnx=true and hit “Enter”

The PNX will open in a new tab

For example

In a particular institution users are reporting issues finding article citations when searching by subjects. 

The institution does not know if this is an issue with the indexes in the records or with the methodology users are using to search.

The institution therefore wants to look at the “search” section of the PNX and verify that the subjects are included as part of the indexes.

The Primo administrator of the institution then does as follows:

1. Search for an article citation, for example with title “Female Managers in Taiwan: Opportunities and Barriers in Changing Times”
2. Click on title to get to full view
3. Add &showPnx=true to the end of the URL and hit enter

The PNX appears in a new tab and includes the subjects as follows as part of the “search” section.

Users should be able to search by any of these terms by subject and find the article citation:

"subject": ["Ambition", "Asia", "Authors", "Career development", "Culture", "Culture conflict", "Discrimination in employment", "Employment", "Executives", "Family", "Females", "Management", "Marital conflict", "Occupations", "Sex discrimination", "Statistics", "Taiwan", "Women", "Women employees"],

Let’s try it 

We find the article citation

We therefore now know that the subjects are correctly indexes with the record and can be searched in Primo.  We should therefore contact the users and investigate their retrieval issues from a different angle, as our research here shows that there may be an issue with the methodology users are using to search.  The records in Primo are correct.

The post How to view the PNX record in Primo VE using showPnx=true appeared first on Ex Libris Developer Network.

Once a workflow is ready, you can copy it from Sandbox to Production by exporting it from one environment and importing it into the other.
The process is simple, but there are a few important details related to credentials and privacy that must be handled carefully.

This post walks you through the process step by step.

When would you need to copy a workflow?

Typical use cases include:

• Promoting a tested workflow from Sandbox to Production
• Creating a backup of an important workflow
• Reusing the same workflow structure across environments

Important note about credentials and privacy

This section is critical.

When you export a workflow from LibOW:

• The exported file includes the workflow structure, nodes, connections, and configuration
• References to credentials are included, such as credential names or identifiers
• Secret values such as passwords, tokens, and keys are not included

This behavior is intentional and designed to protect security and privacy.

However, it is important to be aware of the following:

• If a node contains values entered directly as plain text, such as a custom HTTP header or token typed into a field, those values may appear in the exported file
• Credential names may be descriptive and could reveal information if the file is shared

Best practice is to treat exported workflow files as sensitive artifacts and review them before sharing or storing them.

After import, credentials must be recreated or reselected in the target environment.
Until this is done, the workflow will not run successfully.

Step 1 – Export a workflow from Sandbox

1. Open LibOW in your Sandbox environment
2. Open the workflow you want to copy in the editor

In the top right corner of the editor, open the workflow options menu.

3. Select Download

LibOW downloads the workflow as a JSON file to your computer.
This file represents the workflow logic and configuration, excluding secret credential values.

Keep this file until you are ready to import it into Production.

Step 2 – Import the workflow into Production

1. Open LibOW in your Production environment
2. Open the workflows list or workflow editor

From the top right workflow menu, choose Import from file.

3. Select the JSON file you exported from Sandbox

Once imported, the workflow appears in the Production workflows list.

At this stage, the workflow exists but is not yet ready to run.

Step 3 – Reconfigure credentials in Production

Open the imported workflow in the editor.

You will likely see warning indicators on nodes that require credentials, such as Alma APIs, external services, or email integrations.
This is expected.

For each affected node:

1. Open the node settings
2. Select an existing Production credential or create a new one
3. Save the node

Important reminders:

• Credentials are environment specific
• All credentials must be explicitly configured before the workflow can run

Step 4 – Review and activate the workflow

Before activating the workflow:

• Review trigger configuration and scheduling
• Confirm environment specific values such as URLs or identifiers
• Check for any hard coded values that should differ between Sandbox and Production

Once everything is verified, activate the workflow.

Your workflow is now live in Production.

Best practices and tips

• Always develop and test workflows in Sandbox first
• Keep exported workflow files as backups
• Name workflows clearly to distinguish Sandbox and Production versions
• Review exported files before sharing them
• Avoid placing secrets directly into plain text fields when possible

Summary

Copying a workflow from Sandbox to Production in Library Open Workflows is a safe and well defined process when done correctly.

Exporting preserves workflow logic while protecting sensitive credential data.
Importing allows you to recreate that logic in another environment, with full control over configuration and security.

By understanding what is included in the export, what is intentionally excluded, and what must be reconfigured after import,
you can confidently move workflows into Production and keep your LibOW environments secure and consistent.

The post Library Open Workflows – How to copy a workflow from Sandbox to Production appeared first on Ex Libris Developer Network.

You are a cataloger or e-resources person who loads bibliographic records into Alma. You have experience configuring import profiles (requires Catalog Administrator role) and creating indication rules in Metadata Editor.

Scenario

Your vendor provides all bib records in one file but you’d like to load the records separately by bibliographic level (monograph, serial, and integrating resource).

For example, you’re loading US government documents from WorldShare Collection Manager. (WCM can separate “serials” in a separate file but the documentation doesn’t mention how integrating resources are handled.)

For each bibliographic level you want to specify a portfolio material type.

Documentation

Managing Import Profiles – Ex Libris Knowledge Center

Working with Indication Rules – Ex Libris Knowledge Center

Bibliographic Level (OCLC) (Bib level (Blvl) is encoded in the MARC leader position 7)

Procedure

In Alma you can use indication rules to filter bib records during import. In import profiles the logic is: if the indication rule is true, then exclude from import. True = Exclude

rule "SCP mbj Import monogr only"
when
not existsControl "LDR.{07,1}.m"
then
set indication."true"
end

Basically, the indication rule is saying if the bib record is not a monograph then exclude it from import. In other words, load monographs only.

For your monograph import profile, in the Normalization & Validation tab,
Filter, Filter out the data using
you’ll select the indication rule that imports monographs only.

–

The following indication rules are for the serials import profile and integrating resources import profile.

rule "SCP mbj Import serials only"
when
not existsControl "LDR.{07,1}.s"
then
set indication."true"
end

rule “SCP mbj Import int res only”
when
not existsControl “LDR.{07,1}.i”
then
set indication.”true”
end

The post Alma import profiles: how to use indication rules to filter records by bibliographic level (monograph, serial, integrating resource) appeared first on Ex Libris Developer Network.

II. Make sure you have a Resource Sharing Library in Alma, or set up an existing library as a Resource Sharing Library.  Madison has had this set up from the beginning.  

1. This could be done using the default Resource Sharing Library in Alma or you can make your main library the Resource Sharing Library. It depends on your workflow preference. 
2. In Alma Config>Fulfillment> (Configure your RS or Main Library) >Library Details
   1. Institutions must have the Resource Sharing Library option checked either under a main library or the default Resource Sharing library. If you already have this set up, you can keep what you likely have.  
   2. There are five main match points you will want to note here:  
      1. Your library path – usually your institution code and library code in a string
      2. Your institution code
      3. Your library code
      4. Your ISO code which is for us is ISO_[library code].  You would supply them with whatever you have in that box and Share it needs to prefix this with EXL:
      5. Your url domain with exlibris – aka – naxx.alma.exlibrisgroup.com.   Do not include http:// or https://
   3. You will then need to share your information with your new partner and vice versa.  Also, discuss if you want to share patron information (we did not), and if you are able to share barcodes without collisions (we were able to).  

The data we shared to ShareIT was:

• Madison’s Connection
  • Code: INSTCODE.LIBCODE (view the library level and copy this.   It should be something like institution code.Library code.
  • Code Type: ISO:{Symbol}   * Don’t include the {} and fill in what you have defined in your main RS Library Symbol box. Note to your ShareIT partner they will need to prefix it with EXL:
  • Hostname: wisconsin-xxx.alma.exlibrisgroup.com or na02.alma.exlibrisgroup.com
  • Port number: 9001

III. Create a Locate Profile for your new partner

1. Alma Config>Fulfillment>Locate Profiles

• We set up a z39.50 connection with Exlibris, opened a ticket and provided the WISCAT information.    Once they set it up we used this connection to build the locate profile.  We match on title and ISBN

IV. Setup a local partner

1. Set up a local Partner (Alma Config>Fulfillment>Partner>Add a new Partner)

• ShareIT needs to provide the following information:
  • Code: AAAA – this is the account code
  • Code Type: A-G:XXXX – the four letter organization code for Wiscat it A-G:STWI
  • Hostname: xxxx-isoill.auto-graphics.com
  • Port number: 1611
• You will enter this into the partner information as:

  

   On the Contact tab, do add in something in the email field as it is required.  Usually you would want to add the main ILL or circ email.   We also added the name of the library, which consortium they belong to (because that is how our state delivery system sorts them) and their address.  This all prints out on the printing slip

  On the Parameters tab you need to add the url, ISO symbol and then only check boxes if you are allowed to share patron information and or barcodes.  Our ISO codes start ISO_.   ShareIT assumes that they will start EXL: so if they do not you do need to check the option Add prefix to institutional symbol.
  

  

• We should note that you will need to set up a partner for each unique account code / library you are going to do business with.  As we are part of an NZ, we were able to setup each partner once in the NZ and have that partner share to all our members.

Test the connection

** If you happen to be testing on Sandbox first.  You will need to contact ShareIT to find out their IP range.  We then entered a rule to allow them from their IPs.   On Production, Exlibris notes that it should be all open.

*** If you have libraries in your ShareIT partnership who are also using OCLC or ILLiad in the mix, we have found that having Alma talk to ShareIT and then to OCLC or ILLiad, does not work well.   For those libraries we tried to do a direct Alma to ILLiad connection.

*** These instructions have worked for Brandeis University, a Rapido / Alma single institution and several schools in the University of Wisconsin consortia, which is currently a mix of Rapido and Alma only institutions but all share an NZ.  

The post Setting up an Alma connection with ShareIT appeared first on Ex Libris Developer Network.

This blog post will show how to identify the exact syntax of the names of the fields (labels). The example here is done in Primo VE NDE.  The same methodology also works in Primo VE (not NDE).

Let’s first look at three examples of places in Primo where an institution may wish to change the display names of the fields (labels), then we will see how to identify the technical names of these fields (labels) so that we can change them.  We will also make the actual changes to the fields (labels) and see the changes in Primo.

Three examples of places in Primo where the institution may wish to change the display names of the fields (labels)

For example, in the screenshot below, which is the “Brief Display” in Primo VE NDE, the institution may wish to change the label “By” or the label “Published on”:

Additionally, in the “Locations” section below the institution may wish to change the labels “Item status Queue” or “Terms of use”.

Similarly, in the screenshot below, which is the “Full Display” in Primo VE NDE, the institution may wish to change the label “Creator” or the label “Source” or the label “Collection Path”:

The syntax to identify the exact names of the fields (labels)

In order to identify the exact names of the fields (labels) the user needs to add the following text to the end of the URL:  &debugLabels=true

If this is the URL:

https://exldeveu00.primo.exlibrisgroup.com/nde/fulldisplay?query=sticky%20floor&tab=Everything&search_scope=MyInst_and_CI&searchInFulltext=false&vid=EXLDEV1_INST:Alma_NDE&lang=en&docid=alma99653190500121&adaptor=Local%20Search%20Engine&context=L&isFrbr=false&isHighlightedRecord=false&state=

Then this would be the URL to show the exact names of the fields (labels):

https://exldeveu00.primo.exlibrisgroup.com/nde/fulldisplay?query=sticky%20floor&tab=Everything&search_scope=MyInst_and_CI&searchInFulltext=false&vid=EXLDEV1_INST:Alma_NDE&lang=en&docid=alma99653190500121&adaptor=Local%20Search%20Engine&context=L&isFrbr=false&isHighlightedRecord=false&state=&debugLabels=true

The labels in the Brief Display

Here we can see the brief display without and with &debugLabels=true added to the URL.

We see that

• The label “By” is called “nde.briefdisplay.first“
• The label “Published on” is called “nde.briefdisplay.second“

Without &debugLabels=true added to the URL	Without &debugLabels=true added to the URL

The labels in the Locations Display

Here we can see the locations display without and with &debugLabels=true added to the URL.

We see that

• The label “Item status Queue” is called “nui.item.brief.1“
• The label “Terms of use” is called “nui.item.brief.2“

Without &debugLabels=true added to the URL	Without &debugLabels=true added to the URL

The labels in the Full Display

Here we can see the full display without and with &debugLabels=true added to the URL.

We see that

• The label “Creator” is called “fulldisplay.creator”
• The label “Source” is called “fulldisplay.source”
• The label “Collection Path” is called “nui.colldiscovery.details.paths”

Without &debugLabels=true added to the URL	Without &debugLabels=true added to the URL

Using the label name to change display field for the Brief Display

We will now change the brief display so that instead of “Published on” it will state “Publication Date”.

Using debugLabels=true we already saw that the label “Published on” is called “nde.briefdisplay.second“

Therefore we will do “Discovery > Display Configuration > Labels” and then search for code “nde.briefdisplay.second“.

We see that the field exists in table “Results Tile Labels”.

We will edit “Results Tile Labels” and change this

To this:

Now the display in Primo has changed

Before	After

Using the label name to change display field for the Locations Display

We will now change the brief display so that instead of “Terms of use” it will state “Policy”.

Using debugLabels=true we already saw that the label “Terms of use” is called “nui.item.brief.2“

Therefore we will do “Discovery > Display Configuration > Labels” and then search for code “nui.item.brief.2“.

We see that the field exists in table “Item Display Brief Display Labels”.

We will edit “Item Display Brief Display Labels” and change this

To this:

Now the display in Primo has changed

Before	After

Using the label name to change display field for the Full Display

We will now change the full display so that instead of “Source” it will state “Originating System”.

Using debugLabels=true we already saw that the label “Source” is called “fulldisplay.source”

Therefore we will do “Discovery > Display Configuration > Labels” and then search for code “fulldisplay.source”.

We see that the field exists in table “Full Display Labels”.

We will edit “Full Display Labels” and change this

To this:

Now the display in Primo has changed

Before	After

–

The post How to change the display labels in Primo VE using debugLabels=true appeared first on Ex Libris Developer Network.

Currently in the “Details” section of the Primo VE display, for field “Subject”, we are seeing all of the 650 fields which are in the bibliographic record.

This is the case regardless of the vocabulary which is used in the 650 field.

We want to see the 650 subject field only if it is a Library of Congress subject field (meaning it has a second indicator 0).

If the 650 subject field is not a Library of Congress subject field (meaning it has a second indicator which is not 0) then we do not want it to appear in the “Details” section of the Primo VE display, for field “Subject”.

How can we do this?  You asked me to provide a real example, here is a real example from our catalog:

Title “Women’s Pathways to Power : Cracking the Glass Ceiling” has 10 different 650 fields.  Only 4 of them are Library of Congress subject fields (meaning they have a second indicator 0).  Those are the only 650 fields that we want to display in the “Details” section of the Primo VE display, for field “Subject”.

Here I am presenting it for you visually.  Only the fields in the green square should appear in the “Details” section of the Primo VE display, for field “Subject” (they have second indicator 0).  The fields in the red square should not appear in the “Details” section of the Primo VE display, for field “Subject (they have second indicator which is not 0).

Here is the record in Primo VE with all 10 subject fields:

Answer:

We need to change the Primo VE normalization rule for field Subject to take the 650 only if the second indicator is 0. 

Let’s first see what the “Subject” field above is doing when it displays the fields.  We can see this by looking at the corresponding Primo VE Normalization Rule.

Go to “Discovery > Display Configuration > Manage display and local fields”.

• If you do already see a row with “Display label”  “Subject” then edit that row.
• If you do not already see a row with “Display label”  “Subject” then add it as follows: Add field > Add Display Field > In ‘field to edit’ choose ‘Subject’

Edit the “MARC21 normalization rule for display”

Change the section of this rule which deals with the 650 field as follows. 

• Change “AND NOT” to “AND”
• Change “MARC.”650”.ind”2″ equals “2“” to “MARC.”650”.ind”2″ equals “0“”

You can do the same for any other field listed in the rule.

Make the change and click “Save”

After clicking “Save” click “Back” and then “Apply Rules”

Check the display now in Primo VE and see that only the 650 fields which have a second indicator 0 are displaying in the Subject field:

The four subjects appearing now (after changing the Primo VE Normalization rule) are the four subjects which have a second indicator 0:

Here is the “Before” and “After” screenshots:

Before changing the Primo VE Normalization Rule	After changing the Primo VE Normalization Rule

The post How to use a Primo VE Normalization Rule to display the 650 subject fields only if the vocabulary is Library of Congress Subject Headings (second indicator is 0) in the Primo details section appeared first on Ex Libris Developer Network.

I followed your instructions to display the 546 subfield a in the Primo details section.  Thank you for the detailed clear instructions.  It works.

However, the corresponding 880 field “Alternate Graphic Representation” (which I added to the Alma record following your instructions at Alternate graphic representation 880 field in Alma.pptx ) is not displaying.

What do I need to do to make the 880 field appear together with the 546 field in the Primo “Details” section?

I know there is an 880 in the record with a subfield a which corresponds to my 546 field subfield a.  I can see it when I view the record via the links in Primo and click “Display Source Record”.

Here is the 880 subfield a which corresponds to my 546 subfield a:

In the Primo “Details” I see the 546 but not the 880:

The directions I followed (which I got from you earlier) to add the 546 field to make it appear in the Primo “Details” section as above are as follows:

1. Go to “Discovery > Display Configuration > Manage display and local fields”

2. Add field > Add Local Field > choose local_field_02

3. Make the display label “Language Note (546)”

4. Change the default “MARC21 normalization rule for display” as follows:

5. Click “Save” and then “Apply Rules”

6. Edit the view and go to the “Full Record Services” tab and click “”configure” for the row named “Details”

7. Add the field “Language Note (546)” which was added above in steps 1-5

What do I need to do to make the 880 field appear together with the 546 field in the Primo “Details” section?

Answer

The instructions which I provided above, as you discovered, will display only the 546 subfield a.

However, you want to also display the 880 field subfield a which corresponds to the 546 subfield a.

Therefore you need to change the “MARC21 normalization rule for display” which you defined in step 4 above as follows.

Add the bold section, which includes handling an 880 field which is connected to a 546 field:

Let’s check in Primo VE to be sure the changes have been made as desired.

We see that the 880 field which corresponds to the 500 field does display

Before the normalization rule change	After the normalization rule change

The post How to use a Primo VE Normalization Rule to display the 546 subfield a and the corresponding 880 field (Alternate Graphic Representation) in the Primo details section appeared first on Ex Libris Developer Network.