An unbroken chain

Approaches to implementing Linked Open Data in libraries

Comparing local, open-source, collaborative and commercial systems

Rurik Greenall - Norwegian University of Science and Technology (NTNU) LibraryLukas Koster - Library of the University of Amsterdam

IFLA LLD Satellite meeting 2014

What we do

[funny pictures of chaos and tools and despair]

Rurik Thomas Greenall works at NTNU, the Norwegian university of science and technology with software development. The major foci for this work are REST, LOD and Web APIs. His work typically integrates components familiar from the Web and linked-data

stacks as well as elements from more traditional library systems. As of August 2014, Greenall will be a member of staff at Computas AS, an IT consultancy, where he will work with semantic Web applications. He will work with Oslo public library’s development

team, on behalf of Computas.

As Library System Coordinator, Lukas Koster deals with commercial systems used by the Library of the University of Amsterdam for their core library workflows and functions. These systems are provided by Ex Libris: Aleph ILS, SFX Link Resolver, Primo Discovery

Tool, bX Recommender Service. These systems are highly customized by local staff to fulfill local requirements. The Library of the UvA also uses a number of Open Source tools for other functions, among others, developing their own repository systems. Lukas

Koster has been active in the independent International Group of Ex Libris Users IGeLU, most recently as coordinator and member of the Linked Open Data Special Interest Working Group which is working with Ex Libris to implement LOD features in their

systems.

Libraries: types, content, audiences

Public

Company

Special

National

Research

Academic

Books

Science

Entertainment

Articles

Data

Music

Movies

Fiction

InformationMaps

Art

Researchers

Staff

People

Institutions

Politicians

Students

Heritage

Libraries and the Web

Business as usual

OR

Adapt to the Web Library

Library

About Linked Open Data

RDF

Open licence/world

HTTP-URIs

Linked

Of the Web, not on the Web

LOD management options

Original RDF

Mapping (On the fly)

ETL (Extract Transform Load)

Issues with legacy data: strings, not things

Objectives for library LOD

Cataloguing/CREATING

Exposing

Consuming

Content and systems

Content : “Open Data”

“Legal” access

Currently: no access, no policy

Systems: “Linked Data”

“Actual” access

Currently: separate dedicated systems/silos

Lifecycle planning

Plan-Do-Check-Act

Plan-Design-Implement-Test-Deploy-Maintain

...

Use cases

Standards

Support

Community

Adapt

Legacy Data

Current

Staff

Audience

Legacy Data

RDF

RDF

External Process

ExternalProcess

External RDF

Current RDF Cataloguing

Exposing

Consuming

Staff Staff

Audience Audience

?

?

?

ETL

Mapping

External RDF

Server side

Client side

One time

Iterative

?

Cataloguing/CREATING LOD

What: Data/metadata

Why:

How: Original RDF

Local/FOSS: Complicated - Lifecycle planning

Consortia: Between local development, commercial

systems

Commercial vendors: Waiting for BIBFRAME et al.

Legacy Data

Current

Staff

Audience

Legacy Data

RDFExternal Process

RDF Cataloguing

Staff Staff

Audience Audience

?

External RDF

?

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?

Library

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?

FOSSLibrary

Library

Library

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?

Consortium

LibraryLibrary

Library

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?User Group

Vendor

Library

Library

Library

Library

RDFExternal Process

RDF Cataloguing

Staff

Audience

?

External RDF

?User Group

Consortium

FOSSLibrary

Library

Library

Library

Library

Library

Library

Vendor

Exposing LOD

What: Local data/metadata

Why: To be used

How: Export, Sparql, mapping

Local/FOSS: Frequently done

Consortia: Frequently done

Commercial vendors: First steps

Legacy Data

Current

Staff

Audience

Legacy Data

RDF

ExternalProcess

Current

Exposing

Staff

Audience

?

?

ETL

Mapping

Legacy Data

RDF

ExternalProcess

Current

Exposing

Staff

Audience

?

?

ETL

Mapping

User Group

Consortium

FOSSLibrary

LibraryLibrary

Library

Library

Library

Library

Vendor

Consuming LOD

What: Enriching local data with external data

Why:

How: Query/Dereference/Embed

Local/FOSS: Diverse

Consortia: Diverse

Commercial vendors: Not really

Legacy Data

Current

Staff

Audience

Legacy Data

External RDF

Current

Consuming

Staff

Audience

Server side

Client side

Legacy Data

External RDF

Current

Consuming

Staff

Audience

Server side

Client side

User Group

Consortium

FOSSLibrary

Library

Library

Library

Library

Library

Library

Vendor

Legacy Data

RDF

ExternalProcess

External RDF

Current

Exposing

Consuming

Staff

Audience

?

?

ETL

Mapping

Server side

Client side

Legacy Data

RDF

RDF

External Process

ExternalProcess

External RDF

Current RDF Cataloguing

Exposing

Consuming

Staff Staff

Audience Audience

?

?

?

ETL

Mapping

External RDF

Server side

Client side

One time

Iterative

?

Reconciling approaches

Fulfillment

Timeframe

User base

Conclusions, recommendations

Did we mention Lifecycle planning?

Standards

Community