Designing KohaCatA Discovery Framework for Authority Recommendation and ILS-DI based OPAC Functionalities

Dr. Parthasarathi Mukhopadhyay Department of Library and Information Science

University of Kalyani

1

A set of three problems in libraries of India

1. No single-window search interface for different library resources

Let us imagine the difficulties of users

What we need?

Let us imagine the scenario with a discovery layer

A set of three problems in libraries of India

2. Two different interfaces for search – OPAC and Authority

Even in LoCTwo Search Interfaces !!!!

No

Name

Authority

In WorldCat too !!

No Subject

Authority

What we need?

Authority

Recommendation

System

Authority

Integration

in

Discovery

Reuse of Authority Data in Discovery

Earth—See Earth (Planet)

Earth (Planet)—13 Related Subjects

Earth (Planet) 117

Earth (Planet)—Figure—Mathematical models 5

Earth (Planet)—Mantle 76

Subjects: Before & after authorities processing

Earth 116

Earth—Figure—Mathematical models 2

Earth—Mantle 67

Earth (Planet) 1

Earth (Planet)—Figure—Mathematical models 3

Earth (Planet)—Mantle 9

Metadata BEFORE Metadata AFTER

See ref to correct term

See also refs

Consolidates

Old forms and the new form of a subject heading separate the collection.

Authority control brings your holdings together.

Example based on LCSH

Sacred works: Before & after authorities processing

Bible. Genesis—Criticism, interpretation, etc. 1Bible. Mark—Criticism, interpretation, etc. 2Bible. N.T. Mark—Criticism, interpretation, etc. 49Bible. N.T.—Criticism, interpretation, etc. 153Bible. New Testament—Criticism, interpretation, etc. 1Bible. O.T. Genesis—Criticism, interpretation, etc. 57Bible. O.T.—Criticism, interpretation, etc. 307Bible. Old Testament—Criticism, interpretation, etc. 1Koran--Criticism, interpretation, etc. 37Qur’an--Criticism, interpretation, etc. 1

Bible. Genesis—Criticism, interpretation, etc. 58

Bible. Mark—Criticism, interpretation, etc. 52

Bible. New Testament—Criticism, interpretation, etc. 154

Bible. Old Testament—Criticism, interpretation, etc. 308

Qur’an--Criticism, interpretation, etc. 38

Metadata BEFORE Metadata AFTER

Updates to LC

Consolidates

Even non-authorizedheadings are reformatted.

Example based on LCSH

Other benefits….

Authority control provides the user with the term that is currently used and also adds current term to tag cloud

Authority record points to other works by the same author under a different name (including pseudonym)

Uniform titles authority further enhance discovery● Critical for music searches, scores & sound recordings.

Popular form of title is in uniform title.● Search on popular name without authority cross

reference in place. Work is lost!

FAST (Faceted Application of Subject Terminology) in Koha

Solr Biblio Index

VUFIND

Discovery ILS IDR Others

Authority Recommender in Search Interface

AuthorityRecommendation

Module

Authority

Display

Logic

Authority

Reference

Control

[TopRecommendations]Author[] = "AuthorFacets"Author[] = "SpellingSuggestions"Author[] = "AuthorityRecommend:record_type:Personal Names:source:ILS-FAST:__resultlimit__:50"Subject[] = "AuthorityRecommend:record_type:Topical:source:ILS-FAST:__resultlimit__:50"Title[] = "AuthorityRecommend:record_type:Uniform Titles:source:ILS-FAST:__resultlimit__:50"

Authority Reference Control

mechanization of library

A set of three problems in libraries of India

3. Union Catalogues are lacking OPAC functionalities

National Union CatalougeIndCat

National Union CatalougeIndCat

National Union CatalougeCSIR Knowledge Gateway

National Union Catalouge - UKCopac

National Union Catalouge - UKCopac

National Union Catalouge - UKCopac

National Union Catalouge - AustraliaTrove

National Union Catalouge - AustraliaTrove

National Union Catalouge - AustraliaTrove

Global Union Catalouge - WorldCat

Global Union Catalouge - WorldCat

Global Union Catalouge - WorldCat

Facts in a nutshell

● No union catalogue (national or global) is using ILS to design union catalogue;

● Union catalogues are not using ILS as end user iterface but Discovery Interface (DI) as single-point serach entity;

● Union catalogues are mostly depending on the process of harvesting to gather metadata of books (manifestation level) in a central index inside a discovery service;

● Most of these services have sucessfully implemented FRBRized display (gathering all manifestion of the same work in the display);

● Most of these services implemented Deduplication (gathering all items of the same manifestion in one place);

● But almost all of these services failed to implement minimum OPAC functionalities like real-time item availability status, holds placement/reservation, login with respective library credentials etc.

Why? Simple dear, ILS can’t talk to DIWhy? Simple dear, ILS can’t talk to DI

What is ILS-DI?

“From the standpoint of libraries it would be – ideal to be able to mix‐and‐match ILS and – discovery platforms to suit local needs. To – create such a rich environment the library and – vendor community will need agreement on – the specific technical details of how discovery – and ILS systems are to integrate.” –

– ‐ Peter Brantley, DLF ExecuQve Director, 23/05/2007 – http://blogs.lib.berkeley.edu/shimenawa.php/2007/05/23/ils_abstr

acQon_api

Berkeley Accord, 2008

ILS-DI Standard

https://old.diglib.org/architectures/ilsdi/DLF_ILS_Discovery_1.0.pdf

Koha supports ILS-DI

What OAI/PMH compatibility is doing?

http://localhost:7001/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=oai_dc

http://localhost:7001/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=marcxml

http://localhost:7001/cgi-bin/koha/oai.pl?verb=ListRecords&metadataPrefix=marcxml

What ILS-DI can do additionally?

http://localhost:7001/cgi-bin/koha/ilsdi.pl

ILS-DI call in REST fashion

http://localhost:7001/cgi-bin/koha/ilsdi.pl?service=GetAvailability&id=1+2&id_type=item

ILS-DI call in REST fashion

http://localhost:7001/cgi-bin/koha/ilsdi.pl?service=GetPatronInfo&patron_id=2&show_contact=0&show_loans=1

The prototype

Five Koha Instances (ILS)→ OAI/PMH and ILSDI emebled → Fifty Records X Five Instances → VuFind (DI)

Issue 1

How to provide Unique bibid for records from different Koha instances?

Koha Instane 1 Koha Instane 2 Koha Instane 3 Koha Instane 4 Koha Instane 5

/opac-detail.pl?biblionumber=2

collection = "Kohacat - Catalogue of Library1"institution = "KohaCat-Library1"building = "Library1-Koha1"id = 999c, (pattern_map.id_prefix), firstpattern_map.id_prefix.pattern_0 = (.+)=>KohaILSDI1.$1

collection = "Kohacat - Catalogue of Library2"institution = "KohaCat-Library2"building = "Library2-Koha2"id = 999c, (pattern_map.id_prefix), firstpattern_map.id_prefix.pattern_0 = (.+)=>KohaILSDI2.$1

Issue 2

● How to make KohaILSDI driver Multibackend ready?

Koha Instance 1KohaILSDI

driver Discovery Interface (DI)

[Catalog]; database host, port, user, password, databasehost = localhostport = 3306username = koha_library1password = kohakohadatabase = koha_library1

; Url to the ILS-DI APIurl = http://localhost:7001/cgi-bin/koha/ilsdi.pl

The Multibackend Driver

Final words before demonstration..

Koha 17.05.x

as

ILS

OAI/PMH ILSDI

ILSDI driverMultibackend driver

Vufind 4.x

as

DI

DirectDatabase

Call

(Past)

ILSDI Call in REST fashion

(still ILS data structure dependent)

(Present)

ILSDI Call in RESTFul

(ILS data structure independent)

(Future)

The Future: RESTFul DriverThe Future: RESTFul Driver

Thank you…...