Primo and the Semantic Web

1
Primo and the Semantic Web

• Dominique Ritze
• Mannheim University Library

2
Linked Open Data Cloud

• Why?

• How?

• Which?

3
Overview

• Why?
• How?
• Client-side enrichment
• Server-side enrichment
• Realization in Primo
• Which data?
• Examples in Primo

4
Why use LD?

• Providing additional information
• Wikipedia articles
• External links
• Multilingual semantic search
• No language barriers
• No knowledge about technical terms necessary
• intelligent search

5
Enrichment
6
Client-side Enrichment

• Pro
• Provide additional information
• Minimal-invasive solution
• On-the-fly presentation
• Load on the client
• Contra
• Load on the client
• Data not searchable
• No control over the data

7
Client-side Enrichment

• Examples
• Additional links to resources, e.g. Wikipedia
• Implementation
• Query service to get further informationen, e.g.
  by using SPARQL
• Integrate information into the website, e.g. by
  using JavaScript

8
Server-side Enrichment

• Pro
• Searchable data
• Data is integrated with other data in the system
• Load on the server
• Contra
• Load on the server
• Replication of the data
• No current data
• Problems with licences

9
Server-side Enrichment

• Example
• Classification information
• Possibility to refine the search
• Implementation
• Loading the data into the database
• Additional information are part of the website

10
Discovery Systems LD

• No discovery system provides general LD support
• Workarounds
• Requirements
• Identification of resources (URI)
• Access mechanisms for LD
• Plugin mechanisms
• Proper presentation

11
Primo Plugin-API

• Example

12
Primo Plugin-API

• Client-side enrichment using JavaScript
• Allows to develop JavaScript plugins for Primo
• Abstraction from Primo
• Plugins can be used to enrich Primo

13
Primo Plugin-API
14
PermaLink

• Creates permanent link (URI) per resource
• unique identification, cool URIs 1
• First part of the link
• http//link.bib.uni-mannheim.de/primo/
• Second part of the link
• Resource ID

1 http//www.w3.org/TR/cooluris/
15
PermaLink Example
16
Database Recommender

• Recommends databases according to the search
  terms
• Better and easier research
• Uses a web service (SuUB Bremen) to assign
• subjects
• Based on linguistic and statistic analysis
• Assignment subject database performed by
  subject specialists

17
Database Recommender

• Recommend databases for the entered keywords

18
Wikipedia Article

• Shows Wikipedia articles of authors
• Additional information
• First paragraph is directly shown, further link
  to the articles itself
• Uses assignment author name authority file
• Linkresolver to get the article
• Next step DBPedia

19
Wikipedia Article

• Displays Wikipedia articles for authors

20
Wikipedia Article
21
Idea Connecting publications and research data

• On which data does a publication base on?
• Links between research data and publications are
  available (InFoLiS-project)
• Additional information, facilitates research

22
Why LD support?

• Need some services to provide the data
• Need to query the service
• Need to parse the different formats
• Need an implementation for each plugin
• LD provides the data in a standardized way
• Offers new possibilities, saves a lot of time
  and effort

23
Conclusion

• LD can be useful for libraries
• Client- and server-side enrichment
• feasability? searchability? replication?
• Primo Plugin-API client-side solution
• PermaLink, Wikipedia Article, Database
  Recommender
• Additional effort without LD support

24

• Thank you for your attention!
• dominique.ritze_at_bib.uni-mannheim.de