System integration(at Stockholm University Library)

Koha (dis-)abilities

Supports plenty of workflowsRobust functionality

But, no functions for:Handling orders (call slips for closed stacks)Generating automatic invoices etc.

OAI-PMH ILS-DI

svc/ HTTP API

SIP2

REPORTSWEB SERVICE

Koha interoperability

Endpoints: REST API (Soon)

Z39.50SRU

LDAPShibboleth

System integration at SUL:

• Harvesting records from LIBRIS (union catalogue)

• Integrating Koha & Viola

(L)OPAC

LIBRISWEB SEARCH

LIBRISCATALOGUE

BIBLIOGRAPHIC RECORDS

HOLDINGS RECORDS

HOLDINGS RECORDS

BIBLIOGRAPHIC RECORDS

ITEMS

The (SUL) workflow in LIBRIS:

LOCAL CATALOGUE

”Cultivating”

The LIBRIS connection

Project goals:• Adding items to the LIBRIS XL infrastructure• Synchronization between LIBRIS and local

systems (OAI-PMH, REST API)

OAI-PMH

LIBRIS OAI-PMH server has three flows set-up:bibliographic, holdings & authority

Ongoing work:- First bibliographic records- Holdings to follow- Possibility to add support for authority data

Koha & Viola:Towards a new architecture

Stack fetching

Faculty Office Delivery

Viola Outgoing

Stack call

Ill Request

Ill Request Invoicing Missing books

National Illsystem

Order flow today

Interlibrary Loan Requests

Purchase requests National Ill Requests

Viola Incoming

Invoicing Circulation

National IllsystemViola

VoyagerOPAC

LIBRIS

Koha

ViolaOPACLIBRIS

Order flow tomorrow

Interlibrary Loan Requests

Purchase requests National Ill Requests

Viola Incoming

Invoicing Circulation

National Illsystem

Service layer

Service layer

In order to● keep Koha simple● keep Viola versatile● keep the OPAC lightweight● Enable more services:– ERM– Link resolver– ...

Koha

ViolaOPAC

LIBRIS

Service Layer