1. Loading External Resources into Primo VE
Discovery Import Profiles
Clarice Shin | Technical Support Analyst
Jonathan Dror | Technical Support Analyst

2. Introduction Clarice Shin Jonathan Dror
Joined ExLibris Tier 1 Support team in Working with Primo (Enjoying VE too)
Will always have a good recommendation for a new dining experience.
Jonathan Dror
Joined ExLibris Content Operations team in Working on Data correction and imports into the Alma CZ.
Switched to Primo Tier 2 Support in 2017.
On a quest to find the worlds greatest hamburger.

3. Objectives
Introduce external sources that can be imported to Discovery
Learn how to set up and run an import profile
How to spot problems and troubleshoot

4. Overview
Configuration Menu
Testing Import Profiles
Troubleshooting
Upcoming Developments

5. Why add External Data Sources?
Data does not meet quality standards
Easier to load external records (no need to “clean” metadata)
Rely on existing local data sources
Unique records that library does not want to manage in Alma
External Data sources are records that you do not want to catalog in Alma but do want them in Discovery. The reasons could be that your data doesn’t meet the quality standards. You do not have to clean the metadata. You might want to rely on an existing collection that you have elsewhere, like a database. Or you do not want these records.

6. Data Sources Generic XML Dublin Core MARC 21
Usually uploaded as a file / text
Dublin Core
OAI
MARC 21
Data sources that can be imported into Primo VE are…
Generic XML – uploaded as file or text. there are different types of records.
If you do choose to upload Generic XML – you will need to write your own NRs to map XML elements to dc.

7. It’s all DC
Generic XML are normalized to dc records

8. Common sources
LibGuides

9. Alma Records vs. External
External Record
MMS ID
alma99….
Searchability
In Alma and Discovery
Discovery Only
Source record management
Alma
In the external source + NR
Data type
Physical and Electronic
Electronic only
how are the records different? Alma records versus external records.

10. Import External Data Create Rules (Drool) Create Import Profile
Test Rules
Create Process
Create Import Profile
Configure Source (Upload Files / OAI / FTP)
Assign Process
Configure Delivery
Run Profile
Test immediately in Primo
Three high level steps.
create a rule a drool format. Drool is a special format for rules in Alma that we will explain further later in this presentation. Process – is a group of rules that were created.
Create Import Profile Assign Process – If created
Run Profile

11. When running a profile Harvest Normalize and add local data
Simple Match (by record ID only)
Add / Update / Delete
Save to Repository + Index
This is what Primo does when you run a profile
Harvest
Normalize
Emphasize simple match (identifiers)
Add / Update / Delete
Save and Index

12. Configuration Steps

13. Alma Configuration Menu
We are going to start with step to setup an import profile. Here is that Alma config menu.
Normaliztion rules for external data sources – this will direct to the MD editor to create NR rules / drools
Test NRs – This is where you can try a test record and verify that the NRs are working correctly. We advise testing multiple records
NR process task – This is where you can combine separate rules to create a task that will run each import
Discovey import profile – the main configuration for creating and editing profiles and main troubleshooting
DC type to discovery type mapping – This is where you can map resource type for DC records

14. Adding a Profile Alma Configuration Menu -> Discovery
Adding you own profile.
Add new profile to add a new profile.
You can use the ellipsis to edit/view, view the history of past jobs
and RUN the profile

15. Adding a Profile
Alma Configuration Menu -> Discovery -> Discovery Import Profiles
Data Source Code = ‘KD_DATA’
Label = ‘ Knowledge Days 2019’
Import protocol = “Upload’
Physical source format = ‘XML’
Source Format = ‘DC’ / XML / MARC 21

16. Adding a Profile
Alma Configuration Menu -> Discovery -> Discovery Import Profiles
Data Source Code = ‘KD_DATA’
Label = ‘ Knowledge Days 2019’
Import protocol = “Upload’
Physical source format = ‘XML’
Source Format = ‘DC’ / XML / MARC 21

17. Details Section: Generic XML
Genreric XML will have A structure based on XML elements.

18. Details Section: MARC
Leader/00-23 *****nam##22*****#a# <control number> 003 <control number identifier> /00-01
A marc record would look similar to Alma records.

19. Details Section: DC
DC records should be imported as XMLs, but have their own standardized syntax

20. Details Section Harvest Start date Date Stamp For FTP and OAI imports
Earliest Date stamp - The earliest that data exists in the OAI provider records, populated by Alma.
Harvest Start date - Only files that are after this date will be harvested.
This can be used backtrack you import profile and reharvest records if needed.

21. Test OAI fetch
by ID – not the ID in VE

22. Normalization Optional for DC Required for Generic XML
Most DC records are normalized by Primo VE with OTB rules but custom ones can be added. For XML, we need to map every single field in Primo VE to the element in the XML source.

23. Create a Process
Alma Configuration > Loading External Data Sources > Normalization Process Task
To do that we create a process, which includes multiple rules. Choose type of process depending on the source

24. Create a Process
Alma Configuration > Loading External Data Sources > Normalization Process Task
To do that we create a process, which includes multiple rules. Choose type of process depending on the source

25. Create a Process: General Information
Alma Configuration > Loading External Data Sources > Normalization Process Task

26. Create a Process: Add Tasks
Alma Configuration > Loading External Data Sources > Normalization Process Task
ADD SCREENSHOTS

27. Create a Process: Add Tasks
Alma Configuration > Loading External Data Sources > Normalization Process Task
ADD SCREENSHOTS

28. Create a Process: Task Parameters
Alma Configuration > Loading External Data Sources > Normalization Process Task

29. Choose the Process

30. Delivery
In the delivery section, we configure the delivery links that are in the source and thumbnails.

31. Link to Resource Template: Static URL from source:
We can use the link to source by a template. It usually starts with a url and a parameter that we congifure later on. Or a static URL that copies the value of a DC tag into a link.

32. Link to Thumbnail Template: Static URL from source:
Thumbnails are very much the same, you can use a template or a static link. In this example, we are using a local field that was populated by a rule.

33. Define Linking Parameters

34. Define Linking Parameters
Source tag
Matching Screen
NORMALIZING SOURCE TAG

35. <record>
<metadata>
<qdc:dc>
<dc:title>Efficient contact determination between geometric models</dc:title>
<dc:type>book</dc:type>
<dc:identifer>XYZ1234</dc:identifer >
<dc:identifer>
</qdc:dc>
</metadata>
</record>

38. Testing Normalization Rules

39. Where?

40. Test a record
Option 1: Upload test file
Option 2: Paste text

41. Add a record

42. Run test

43. Supported File Types
DC XML file (oai_dc or qdc format) that contains a single DC record
XML Generic XML format that contains one or more generic XML records.
MARC21
MARCXML file that contains one or more MARC21 records.
Binary MARC file that contains one or more MARC21 records.

44. Special Characters Ampersand (&) – use &
Left angle bracket (<) – use <
<dc:subject>
Engineering & Technology </dc:subject>

45. Mapping Resource Types

46. How does PrimoVE choose a Resource Type?
discovery:resourceType field
Mapping table value -> Map dc:type / dcterms:type to discovery:resourceType field
dcterms:type field
dc:type field

47. How can I change the Resource Type?
Option 1: Replace value of dc:type / dcterms:type
Option 2: Map to discovery:resourceType
Option 3: Dublin Core Type to Discovery Type Mapping

48. Option 1: Replace value of dc:type / dcterms:type
rule “from dc:type book to dc:type pbook”
when
“dc”.”type” equals “book”
then
set “pbook” in “dc”.”type”
end

49. Option 2: Map to discovery:resourceType
rule “from dc:type book to discovery.resourceType pbooks”
when
“dc”.”type” equals “book”
then
set “pbooks” in “discovery”.”resourceType”
end

50. Option 3: Dublin Core Type to Discovery Type Mapping
dc:type or dcterms:type field
discovery.resourceType

51. Delete all records Import Profile
Cannot delete profiles if records are not deleted
Admin > run a job
Delete External Data Sources
Choose Data Source
Run the Job

52. Troubleshooting

53. History

54. Report

55. Reports Reports Reports
We know that the errors messages when first launched were not very informative. The development are slowly adding more indications and clearer messages. However, some errors may still not be that clear and we do encourage you to open a case to add those to our dictionary of error messages.

56. View File Details
Up to groups o

57. Parsing the record

58. Completed with 0 records

59. Next Steps Loading Records from External Sources into Primo VE
Configuring Local Resource Types for Primo VE
Additional support resources from Ex Libris:
Idea Exchange – ideas.exlibrisgroup.com
Developer Network – developers.exlibrisgroup.com
2019 Knowledge Days Seminar Presentations

60. Questions?

61. We value your feedback! Please complete the session survey in the schedule section of the app.