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

Transcription

1 Designing KohaCat A Discovery Framework for Authority Recommendation and ILS-DI based OPAC Functionalities Dr. Parthasarathi Mukhopadhyay Department of Library and Information Science University of Kalyani 1

2 A set of three problems in libraries of India 1. No single-window search interface for different library resources

3 Let us imagine the difficulties of users

4 What we need?

5

6

7 Let us imagine the scenario with a discovery layer

8 A set of three problems in libraries of India 2. Two different interfaces for search OPAC and Authority

9 Even in LoC Two Search Interfaces!!!!

10 No Name Authority

11 In WorldCat too!!

12 No Subject Authority

13 What we need?

14 Authority Recommendation System

15 Authority Integration in Discovery

16 Reuse of Authority Data in Discovery

17 Subjects: Before & after authorities processing Metadata BEFORE Metadata AFTER Earth 116 Earth Figure Mathematical models 2 Earth Mantle 67 Earth (Planet) 1 Earth (Planet) Figure Mathematical models 3 Earth (Planet) Mantle 9 Old forms and the new form of a subject heading separate the collection. Authority control brings your holdings together. See ref to correct term See also refs Earth See Earth (Planet) Earth (Planet) 13 Related Subjects Earth (Planet) 117 Earth (Planet) Figure Mathematical models 5 Earth (Planet) Mantle 76 Consolidates Example based on LCSH

18 Sacred works: Before & after authorities processing Metadata BEFORE Bible. Genesis Criticism, interpretation, etc. Bible. Mark Criticism, interpretation, etc. Bible. N.T. Mark Criticism, interpretation, etc. Bible. N.T. Criticism, interpretation, etc. Bible. New Testament Criticism, interpretation, etc. Bible. O.T. Genesis Criticism, interpretation, etc. Bible. O.T. Criticism, interpretation, etc. Bible. Old Testament Criticism, interpretation, etc. Koran--Criticism, interpretation, etc. Qur an--criticism, interpretation, etc. Even non-authorized headings are reformatted. Metadata AFTER Updates to LC Consolidates 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 Example based on LCSH

19 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!

20 FAST (Faceted Application of Subject Terminology) in Koha

21 V U F I N D Discovery 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" Solr Biblio Index ILS IDR Others Authority Recommender in Search Interface Authority Authority Recommendation Display Reference Module Logic Control Authority

22 mechanization of library

23

24

25 A set of three problems in libraries of India 3. Union Catalogues are lacking OPAC functionalities

26 National Union Catalouge IndCat

27 National Union Catalouge IndCat

28 National Union Catalouge CSIR Knowledge Gateway

29

30 National Union Catalouge - UK Copac

31 National Union Catalouge - UK Copac

32 National Union Catalouge - UK Copac

33 National Union Catalouge - Australia Trove

34 National Union Catalouge - Australia Trove

35 National Union Catalouge - Australia Trove

36 Global Union Catalouge - WorldCat

37 Global Union Catalouge - WorldCat

38 Global Union Catalouge - WorldCat

39 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? Why?Simple Simpledear, dear,ils ILScan t can ttalk talkto todi DI

40 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/ acqon_api

41 Berkeley Accord, 2008

42 Koha supports ILS-DI ILS-DI Standard

43 What OAI/PMH compatibility is doing?

44

45

46

47 What ILS-DI can do additionally?

48

49 ILS-DI call in REST fashion

50 ILS-DI call in REST fashion

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

52 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), first pattern_map.id_prefix.pattern_0 = (.+)=>KohaILSDI1.$1 collection = "Kohacat - Catalogue of Library2" institution = "KohaCat-Library2" building = "Library2-Koha2" id = 999c, (pattern_map.id_prefix), first pattern_map.id_prefix.pattern_0 = (.+)=>KohaILSDI2.$1

53 Issue 2 How to make KohaILSDI driver Multibackend ready? Koha Instance 1 KohaILSDI driver Discovery Interface (DI) [Catalog] ; database host, port, user, password, database host = localhost port = 3306 username = koha_library1 password = kohakoha database = koha_library1 ; Url to the ILS-DI API url =

54 The Multibackend Driver

55

56

57

58

59

60

61

62 Final words before demonstration.. Koha x OAI/PMH ILSDI ILSDI driver Multibackend driver as ILS Direct Database Call (Past) ILSDI Call in REST fashion (still ILS data structure dependent) (Present) Vufind 4.x as DI ILSDI Call in RESTFul (ILS data structure independent) (Future)

63 The TheFuture: Future:RESTFul RESTFulDriver Driver

64 Thank you...