FAQs

You have the option of using the Ex Libris documentation on Resource Recommender or Ex Libris documentation on Discovery Import Profiles to make Springshare content discoverable in Primo VE. SUNY FAQ about Resource Recommender.

Resource Recommender Method:

• Pros:
  • Can see your guides in Alma and manage them
  • Can set up keywords that will trigger a guide to show at the top of a search results page
  • Can easily update or deactivate guides or pages
• Cons:
  • Can't automatically harvest

Discovery Import Profile Method:

• Pros:
  • Can automatically harvest content and keep guide links up to date
• Cons:
  • Complicated Alma set-up, involving norm rules, drools
  • Can't see content in Alma - it goes directly into Primo and can't easily be managed
  • Display in Primo is just the guide metadata, not data or searchable fields for page contents
• Note that many SUNY libraries who initially set up discovery import profiles for Springshare content have since deleted these integrations because of low usage and poor display in Primo

Contents

• Setting up a Discovery Import Profile
• Scheduling
• Display Examples
• Using Normalization Rules
• Add a Normalization Process Task
• Create LibGuides Scope for Searching
• Creating a Local Resource Type for LibGuides

Setting up a Discovery Import Profile

• Configuration>Discovery>Loading External Data Sources>Discovery Import Profiles
• Click Add New Profile:
  
• Choose “Discovery” as your Profile Type and click Next.
  • Profile Name = whatever you'd like, eg. LibGuides
  • Data Source Code = LIBGUIDES
  • Originating System = Other
  • Import Protocol = OAI
  • Source Format = Dublin Core
  • Data Source Label = whatever you'd like, eg. Library Research Guides
    
• Scroll down and fill out the OAI details:
  
• You can find your OAI Base URL in LibGuides. Log into LibGuides, click on Tools in the header, click on Data Exports, and click on the OAI-PMH tab to get your URL. It should look something like https://guides.upstate.edu/oai.php
• Once you've added your OAI Base URL, click Connect and Edit. This should connect to LibGuides and pull in the rest of your OAI Details, like Repository Name, set, etc. You can choose to import all of your guides or a subset, and you can choose to Open Test Page to check your settings (note: if you have LibGuides CMS this test may not work but your import will still work).
  
• Click Next
• Second Page: Normalization: Click Next (If you already have normalization set up, add it now, or you can come back and add it later.)
• Third Page: Delivery: In Link to Resource
  • Template = $$LinkingParameter1
  • Link Label = (what you want displayed in Primo)
• Linking Parameters
  • Edit linkingparameter1 by click on the three dots on the right
    
• Click the Bullet list and choose dc_identifier without an Encoding Schema
• Select Matching string using a regular expression in Use Source Tag
• Enter the Matching String = ^(?:http(s)?:\/\/).*
  
• Click Save and then Save again.

Running the job:
From your list of Import Profiles, click on the three dots for the LibGuides Profile and select Run, and then Submit:

• You’ll get taken to the Job History
• You can click refresh until the job finishes.
• You can see reports by clicking the 3 dots. This will show how many records were added and/or updated.
• It may take 10 min to several hours to see the results in Primo.

Scheduling

If you are happy with the results, schedule the import profile to run daily:

• Edit your Import Profile
• Under scheduling: select Active and choose a time under Scheduler
• Click Save
  

Examples:

No Normalization:

Example of guide with normalization on resource type:

Normalization Rules

• Ex Libris documentation on setting up normalization rule for external sources 

Rule Settings:

• Go to MD Editor in Discovery Configuration Area: Normalization rules for External Data sources
• File>Options
  • Make sure to add new rules to IZ rather than NZ
  • Select Local to place new rules
  • Click save

Add a New Rule

• File>New>Normalization Rules (DC)

• Give it a name and description:

• The following is suggested to change the “Other” resource type to “text_resource”

rule "create type"
when
(true)
then
set "text_resources" in "discovery"."resourceType"
end

• Click Save
• You can also test with a test record

After you test: 

• To Enable: Click your rule>click Properties:
  
• Select Enabled
• Click Save
  

Add a Normalization Process Task

• Go to Config>Discovery>Loading External Data Sources>Normalization Process Task
• Process Details:
  • Business Entity: Discovery Bib Records
  • Type: Discovery DC normalization
• General Information: 
  • Name: whatever you'd like, e.g. DiscoveryLibguides
  • Description: optional
  • Status: Active
• Add Tasks: add DCImportDroolNormalization if it's not there
• Edit the Normalization Task to use the Libguides key
  
• Then Edit original Discovery Import Profile and add the Normalization Rule:
  

If you want to go back and edit/rerun your import profile make sure to reconnect (Connect and Edit button) and update the Harvest Start Date back to the earliest date stamp:

Create LibGuides content for scope:

If you'd like to set up a separate search profile for the LibGuides content:

• Go to Discovery>Search Profiles>Custom Local Data Scopes tab
• Add a custom scope
• Use Inventory: External Data Source as the condition, and choose your LibGuides content:
  

How to Create a Local Resource Type for LibGuides (document below)