Table of Contents
Linked Open Data - Discovery of Person Entity
With the integration of Linked Open Data (LOD), Primo VE can now associate records with LOD, specifically persons (such as authors and historical figures) and display this information in the UI. The person entities are based on LoC (Library of Congress) and are enriched with Wikidata.
NOTE
In this phase, person entities are linked only to local records that are linked to LCNAMES authorities.
The information gathered from the LoC and Wikidata is updated once weekly.
Currently, this functionality is supported in English only.
To support this functionality, the following changes were made to the UI:
Autocomplete Person – Person entity suggestions are now provided for search terms entered for simple and advanced searches. Selecting a suggestion opens the associated Person page.
Person Info Card – Displays the person's information in the Recommendations panel on the Full Display page if the record is associated with a linked person entity. Selecting the person's name in the card opens the Person page. A title may be associated with more than one person entity. In the following example, the book is linked with the author and the person about which the book was written.
Person page – Displays the person's information on a full page. In addition to the person's information, this page also includes the following sections, which enable users to discover titles associated with that person: Titles in Library Written by Person, Titles in Library Written about Person, and People Associated with Person.
(Additional Analytics and Configuration sections are included in the release notes.)
Additional Documentation: Wikidata
Ideas Exchange: Enable person entity functionality at the view level
Discussion
UCR: Would like to know what value it gives to the user. Is there an impact to search results (does it create lag)?
UCD: Have it turned on in the sandbox. Haven’t noticed any specific lag but that’s hard to tell in the sandbox. The way it’s laid out now it drops you into a different UI. Questions about how it’s calculating things. Haven’t asked Ex Libris any specific questions yet.
UCSD is looking at it more next week. UCR has it on the things to look at list.
Support Discovery of Local Authority Records
UCR: Very disappointed it’s only local authority records. Felt it shouldn’t have go live without LC being supported. Special collections have asked for better ways to search for collections by donors. Maybe use local authority files for that. So, might be able to leverage this after all.
Add "Exclude CDI Resource Types" Option to CDI Scopes
UCR: Potentially could be useful to reduce duplicates but would need a lot more testing.
Analytics Improvements (NZ)
In Alma Analytics, staff accounts in the Network Zone can access all of their member institutions' data, but they could not do so in Primo VE Analytics. With this enhancement, the NZ can view their member institutions' data in Primo VE Analytics for all Subject Usage areas.
Discussion
CDL Observations:
Currently, we only see the new-to-Alma campuses at the NZ level (presumably this is a bug)
The new Design Analytics Limited roles (Designs Analytics – Resources, etc) do not have access to Primo Analytics. (Weirdly, they also don’t have access to the Shared Community Folders in regular Analytics. I’m not sure if this is by design or not.)
Examples of things one
Usage of top menu links
What user groups and the actions they’re used.
Zero searches and popular searches
How are people coming into Primo (doesn’t include IP addresses)
Features Not Discussed
Support HAN Proxy for CDI Links
Translate Letter Names for Patron Opt-In/Out in My Library Card
Showcase Carousel Enhancements
Bibliographic Call Number Browsing Improvements - Indexing
Support Subject Indexing of MARC 689 Field for German Region
Linked Data - Add Dedup Local Key for Work URI
Split Configuration for Hypertext Linking Using Exact and Only
New Linking Template for InfoBase
Monthly Refresh of CSL Styles
EndNote Icon for Primo Export Options