1 of 62

⌁ Lightning Talks ⌁

Utilizing Linked Data Features

in Ex Libris Products

Hosted by the

IGeLU/ELUNA Linked Open Data Community of Practice Working Group

26 April 2023

Linked Open Data Community of Practice

2 of 62

Overview

  • Introduction
  • About the IGeLU/ELUNA Linked Open Data Working Group
    • Xiaoli Li, University of California Davis Library
  • Lightning Talks
  • Questions & Discussion
    • Use Zoom’s Q&A feature to pose questions

3 of 62

IGeLU/ELUNA

Linked Open Data Community of Practice Working Group

Xiaoli Li

4 of 62

Adding Linked Open Data to a Digital Humanities Collection in Alma

Sai Deng, Metadata Librarian

Lee Dotson, STARS Administrator

University of Central Florida Libraries

5 of 62

Linked Data

  • Linked Data
    • A recommended best practice for exposing, sharing, and connecting pieces of data, information, and knowledge (structured data) on the semantic web.
  • Wikidata
    • A free, open and multilingual knowledge base; Can be read and edited by humans and machines; Provides a low-barrier platform for library’s Linked Open Data.
  • Collaboration with Digital Humanities
    • People, Religion, Information Networks, and Travel (PRINT) Collection
  • Integrating LOD Vocabularies into bibliographic records in Alma and digital collections in the IR (STARS/Digital Commons)
    • Wikidata (people, places…)
    • LC name entities, subjects, FAST headings, GeoNames, genre headings etc.

6 of 62

Collaboration with Digital Humanities

7 of 62

Collaboration with Digital Humanities

8 of 62

Print Migration Network

  • NHPRC Major Collaborative Archival Initiatives Grant for PRINT
    • People, Religion, Information Networks, and Travel (PRINT) Collection
    • Build PRINT portal; research and create metadata and LOD for people and places in the 2700 letters; crowdsourcing transcription of letters

9 of 62

10 of 62

11 of 62

Download Correspondence & Transcription

12 of 62

Creating Entities in Wikidata: �People in Pemberton Correspondence Collection

  • People in Pemberton Correspondence
    • Wikidata example set: https://w.wiki/4pLt
    • Person model
    • Visualizations:
      • Family relation-ships
      • Maps
      • Timeline

13 of 62

Maps and Timeline�

14 of 62

Adding Entities to LC Linked Data Service

15 of 62

Linking Entities to IR Records

16 of 62

Adding LOD Entities to Alma Records

  • Alma & Linked Data
    • LOD coding in MARC Records
    • LOD linking in Alma

  • Linked Data Fields added in Alma

  • Automatically linked to entities/authorities
    • For LC name entities (e.g., creator/author, contributor, name subject)

    • For FAST headings

    • For LC subjects (650, e.g., LCSH)

    • For genre headings (655, e.g., LCGFT, FAST genre/form heading)

17 of 62

LOD Related Guidelines

  • Linked Data Guidelines
  • Examples

  • Guidelines
    • Formulating and Obtaining URIs: A Guide to Commonly Used Vocabularies and Reference Sources

(https://www.loc.gov/aba/pcc/bibframe/TaskGroups/formulate_obtain_URI_guide.pdf

    • PCC Task Group on Linked Data Best Practices Final Report

(https://www.loc.gov/aba/pcc/taskgroup/linked-data-best-practices-final-report.pdf)

  • Examples
    • $1 for Real World Object (RWO) URIs, $0 for traditional identifiers (authority file, controlled vocabularies)
      • VIAF- Virtual International Authority File
        • Example: http://viaf.org/viaf/7386077
        • MARC Subfield for Capturing URIs: $1

      • GeoNames
        • Example: http://sws.geonames.org/2657896
        • MARC Subfield for Capturing URIs: $1

      • ORCID
        • Example: https://orcid.org/0000-0002-7731-8944
        • MARC Subfield for Capturing URIs: $1

      • Wikidata
        • MARC Subfield for Capturing URIs: $1
        • Example: http://www.wikidata.org/entity/Q19526

      • LC Name Authority
        • Example: 100 1# $a Mitchell, Joni, $e composer.

$0 http://id.loc.gov/authorities/names/n82108794

($0 LC authority; no need to manually add it; will be auto-linked in Alma)

$1 http://id.loc.gov/rwo/agents/n82108794 ($1 RWO)

$1 http://www.wikidata.org/entity/Q205721 ($1 Wikidata)

    • $4 for relationships, e.g., 700 1# $a Lattimore, Richmond.

$4 http://id.loc.gov/vocabulary/relators/trl (*translator)

  • Note: no need to manually add $0 links in Alma in general (they’ll be automatically linked eventually, such as LCSH, LCDGT, LCGFT, TGM)

18 of 62

LOD Display �in Alma

  • Ex Libris & Linked Data
    • LOD display in Alma

19 of 62

LOD Display in Alma

  • Ex Libris & Linked Data
    • LOD display in Alma (see right)

Presentation Title

Record: Phineas Pemberton, Ralph Pemberton, September 12, 1680 / by Phineas Pemberton.

Context

bibo:oclcnum

(OCoLC)on1263183145

bibo:oclcnum

(OCoLC)1263183145

dct:creator

Pemberton, Phineas, 1650-1702,

dct:creator

Pemberton, Phineas, 1650-1702,

dct:subject

Social networks.

dct:subject

Society of Friends.

dct:subject

Quakers.

dct:subject

Society of Friends England

dct:subject

Quakers England

dct:subject

Society of Friends England Lancashire.

dct:subject

Quakers Correspondence.

dct:subject

Pemberton, Phineas, 1650-1702

dct:subject

Pemberton, Phineas, 1650-1702

dct:subject

Quakers England Lancashire.

dct:subject

Quaker businesspeople.

dct:subject

England Lancashire

dct:subject

England Radcliffe (Bury).

dct:subject

Personal correspondence.

dct:language

---

JSONLD version

---

null

Pemberton, Ralph, 1610-1697,

null

Pemberton, Ralph, 1610-1697,

Creator

Pemberton, Phineas, 1650-1702,

Contributor

Pemberton, Ralph, 1610-1697,

Vocabularies display as LOD in this example:

  • LC vocabularies (e.g., LCNA, LCSH)
  • VIAF
  • WorldCat entities (e.g., title)
  • FAST
  • Wikidata

20 of 62

Display in Primo

Presentation Title

LOD fields display in source record:

100 1#$aPemberton, Phineas, $d1650-1702, $eauthor, $1https://www.wikidata.org/entity/Q94253673

651 #7$aEngland $zRadcliffe (Bury). $2fast $1https://sws.geonames.org/6691227/

651 #7$aEngland $zLancashire $2fast $1https://sws.geonames.org/11609047/

700 1#$aPemberton, Ralph, $d1610-1697, $eCorrespondent, $1https://www.wikidata.org/entity/Q102033482

21 of 62

LD Integration Profile &LD Enrichment in Alma Publishing Profile

  • Configure Linked Data Integration Profile
    • Go to Configuration Menu > General > External Systems > Integration Profiles, select Add Integration Profile;
    • Page 1 of the External System Wizard:

Code: LOD Name: Linked Open Data Integration Type: Linked Data

    • Page 2 of the External System Wizard:
      • Active - Select to enable the profile
      • Alternative Context URL – Leave empty to use the default context, https://open-na.hosted.exlibrisgroup.com/alma/contexts/bib 

  • Configure LD Enrichment in Alma Publishing Profile

  • Alma Refine
    • Alma Refine matches could be tricky;
    • LOD will only display in the MARC source record in the discovery interface Primo;
    • It will not affect Primo display without additional plug-in or configuration (under development).

  • Challenges
    • LOD display in Primo still in testing phase;
    • Concerns on “what will happen to the public interface” in the library;
    • Not able to test LD integration and publishing in sandbox;
    • Access rights;
    • Consortia environment

22 of 62

Reflections, Challenges and Opportunities

  • LOD can be integrated into library systems to enrich information, help to break down library data silos and open library data to the web;
  • LOD will eventually improve discovery and user experiences in searching the library catalog;
  • Wikidata provides a low barrier platform for libraries to adopt linked data, enables the creation of rich data that may be unavailable or difficult to create in the traditional library environment; its visualization & knowledge graphs can enhance representation and discovery of knowledge; it can be incorporated into the library system in some way;
  • Knowledge graphs in Wikidata and under-development Info Card for Primo can be used to represent structured knowledge and entity (e.g., people, space, time) relationships for collections, and they can be integrated into users’ search experiences;
  • Librarians at UCF will keep exploring linked data, Wikidata and ILS with colleagues in digital humanities, history and other disciplines.

  • Work smarter = Library expertise + Researcher knowledge
  • Relationships build additional partnerships
  • Platform isn’t perfect? Do what you can to move forward

23 of 62

Acknowledgements

University of Central Florida (UCF):

People, Religion, Information Networks, and Travel: The Dynamics of Migration in the Early Modern World

Project Team (Dr. Rose Beiler, Dr. Amy Giroux, Brook Miller, Project students and other participants)

Kerri Bottorff, Digital Collections Projects Coordinator

Jeanne Piascik, Head of Cataloging Services, UCF Libraries

WikiProject: Chinese Culture and Heritage Group

Lihong Zhu, Greta Heng, Xiaoli Li and All Members

24 of 62

Thank you

Sai Deng

sai.deng@ucf.edu

Metadata Librarian

Lee Dotson

STARS Administrator

University of Central Florida Libraries

25 of 62

Using the Alma BIBFRAME Tab

to Introduce Staff to Linked Data

Heather Pretty

Memorial University of Newfoundland

April 26, 2023

26 of 62

Goals of 2018 unit training

  • Know where to find “Linked Data” and �“BIBFRAME view” in Alma
  • Identify BIBFRAME Work, Instance, and �Item metadata in a MARC record
  • Find Work and Instance metadata �in the corresponding BIBFRAME view
  • Explore what metadata is in a MARC record, �but not in BIBFRAME view
  • Explore what metadata is in BIBFRAME view, �but not in a MARC record

27 of 62

Where to find linked data and BIBFRAME in Alma

28 of 62

BIBFRAME view tab

29 of 62

3 types of metadata

  • Structural
    • MARC format / BIBFRAME format�
  • Administrative
    • File type, date created, etc.�
  • Descriptive
    • Work
    • Instance
    • Item

30 of 62

Structural and administrative metadata

MARC: LDR and Control Fields

BIBFRAME: xml specifications and bf:adminMetadata

31 of 62

Descriptive metadata: Work

32 of 62

Linked Data

Context

bibo:oclcnum

(OCoLC)75426

dct:creator

Nicholson, G. W. L. (Gerald William Lingen), 1902-1980.

dct:creator

Nicholson, G. W. L. (Gerald William Lingen), 1902-1980.

dct:subject

World War, 1914-1918 Regimental histories Newfoundland and Labrador.

dct:subject

Great Britain. Army. Royal Newfoundland Regiment

dct:subject

Great Britain. Army. Royal Newfoundland Regiment

dct:language

---

JSONLD version

---

Creator

Nicholson, G. W. L. (Gerald William Lingen), 1902-1980.

33 of 62

Descriptive metadata: Instance

34 of 62

Descriptive metadata: Item

35 of 62

Item metadata not moved to BIBFRAME

36 of 62

$1 not recognized in MARC→BF conversion

������

37 of 62

Partial match to subject heading

38 of 62

Continuing the discussion

  • URIs in Ex Libris Products: LOD CoP Town Hall Apr 2022
    • https://www.youtube.com/watch?v=F0f9T2ytUeM&t=3s
    • More discussion about $0 and $1
    • Suggestion to only add URIs if available for the whole subject heading�
  • 2023-2024 Alma Road Map: Metadata Management
    • Linked Open Data – Adding and managing BIBFRAME Instances in Alma UI
    • Linked Open Data – Cataloging via a third party editor
    • Linked Open Data – Searching for Works in the catalog

39 of 62

Thank you

Heather Pretty�hjpretty@mun.ca

40 of 62

Considerations for Designing

a Linked Data Editor in Alma

Greta Heng, San Diego State University

Tricia Lampron, University of California, Irvine

Myung-Ja (MJ) K. Han, University of Illinois at Urbana-Champaign

40

41 of 62

Outline

  • First, some questions!
  • What Alma currently has … and what it’s lacking
  • Functionality of other Linked Data editors
  • Linked Data editor in Alma
  • What we have learned

41

42 of 62

Linked Data Editor in Alma???

First, some questions

  • Why does Alma need a Linked Data editor?
  • Should Alma be the place for creating linked ‘catalog’ data and sharing?
    • Will we have one place to create and use Linked Data?
  • Will Alma become a database for locally created Linked Data?
  • What would be the workflow from data creation to sharing and using?
    • How are we using Alma?
  • Is the ‘metadata’ we’re creating really Linked Data? We are still creating a ‘record’!

42

43 of 62

What Alma Currently Has…

and What it’s Lacking

43

44 of 62

What Alma Currently Has …

Add authority links (URIs)?

  • Metadata Editors – Find Matches

44

https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/014Navigating_the_Metadata_Editor_Page

45 of 62

What Alma Currently Has …

Add authority links (URIs)

  • Alma Refine

45

46 of 62

What Alma Currently Has …

Convert and publish metadata as Linked Data

  • Include authority URIs when applicable
  • Can see and download by title and in bulk
  • Under development of creating a knowledge card (Info Card) for discovery in PRIMO

46

47 of 62

… and What it’s Lacking

  • Metadata Editors – Find Matches
    • Appears to be not working for our trials
  • Alma Refine
    • Disambiguation functionality
      • No check and verify features for same names
    • Efficient batch reconciliation process

47

48 of 62

… and What it’s Lacking

Linked Data creation and enhancement:

  • Only produces links if there is a controlled authority from source record
  • No mechanism to match (reconcile) with authority files, IF creating records using Alma Metadata Editor

48

49 of 62

Functionality of Other Linked Data Editors

49

50 of 62

Alma Metadata Editor

50

51 of 62

Marva

Sinopia

  • Ontologies: BIBFRAME
  • Outputs: BIBFRAME in XML�
  • Profiles are built in
  • Ease of navigation: not easy
  • Requires training

  • Ontologies: BIBFRAME, RDA, others
  • Outputs: BIBFRAME and others in different representations
  • Can create resource templates
  • Ease of navigation: not easy
  • Requires training

51

52 of 62

Functionality of Linked Data Editors

Profiles: Marva

52

53 of 62

Functionality of Linked Data Editors

Templates: Sinopia

53

54 of 62

Functionality of Linked Data Editors

Templates: Sinopia

  • Ontology agnostic
  • Customizable

54

55 of 62

Functionality of Linked Data Editors

Sinopia

Marva

Querying by string

55

56 of 62

Linked Data Editor in Alma

56

57 of 62

Linked Data Editor in Alma

What Alma has -

  • Metadata editor
  • Template feature
  • Connect to Linked Data sources (y/n)

What Alma does not have -

  • Sharing the output with others
  • Working with triple data
  • Assign URIs for resources

57

58 of 62

BIBFRAME input

BIBFRAME output

RDA

input

RDA output

INPUT

OUTPUT

BIBFRAME input

BIBFRAME output

Sinopia

Marva

Linked Data sources

Linked Data sources image is from “https://minitex.umn.edu/tags/oclc-research-webinars-linked-data-marc”

59 of 62

Alma Linked Data Editor

‘Some’ Functional Requirements

  • One simple editor with clear and easy to understand labels
  • Provide a set of templates for different resource types
  • Built-in mappings for different outputs (MARC, BIBFRAME in different representations, etc.)
  • Customizable templates and mappings to other outputs
  • Autocomplete and lookup functions using Linked Data sources

59

60 of 62

Alma Editor

Simple input

BIBFRAME

MARC

Other ontologies

Other outputs of your choice

Work

Template -Work

Instance

Template -Instance

Mono

Template Type1

Serials

Template Type2

……

Template Type..

61 of 62

What We Have Learned

Still, some questions

  • Why does Alma need a Linked Data editor?
  • What would be the workflow from data creation to sharing and using?
    • How are we using Alma?
  • Should Alma be the place for creating linked ‘catalog’ data and sharing?
    • Will we have one place (like OCLC) to create and use Linked Data?
    • Will Alma become a database for locally created Linked Data?
  • Is the ‘metadata’ we’re creating really Linked Data? We are still creating a ‘record’!

61

62 of 62

Questions?

Greta Heng, gheng@sdsu.edu

Tricia Lampron, plampron@uci.edu

Myung-Ja Han, mhan3@illinois.edu

62