1 / 14

Virtual Union Catalogue Using Koha ILS

Virtual Union Catalogue Using Koha ILS. Dibyendra Hyoju Madan puraskar pustakalaya June 14, 2011. Current scenario. Most of the Nepali libraries are using WINISIS or CDS/ISIS library application Inconsistency in cataloging standards

augustl
Download Presentation

Virtual Union Catalogue Using Koha ILS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtual Union CatalogueUsing Koha ILS DibyendraHyoju Madanpuraskarpustakalaya June 14, 2011

  2. Current scenario • Most of the Nepali libraries are using WINISIS or CDS/ISIS library application • Inconsistency in cataloging standards • Electronic records found in most of the OPACs of Nepali libraries are inconsistent in record format • In the recent years, few of the Nepali libraries have migrated to Koha ILS and started to migrate their records into MARC standard • Currently, there is no electronic union catalog in Nepal • Nepal National Library (NNL) has published a printed version of union catalogue containing catalogs of 15 different Nepali libraries.

  3. Virtual Union Catalogue • The idea of developing virtual union catalogue is to help end-users to find out holdings information about a particular library material in the target libraries • It is being developed using PHP with PHP-YAZ library (http://ftp.indexdata.dk/pub/phpyaz/) • End-users can query in a single interface the different collections of the Nepali libraries • Libraries can reuse the MARC records instead of recreating the records again

  4. Configuring Koha to expose Z39.50/SRU services • Remove the commenting characters from the line in the /usr/share/koha/koha-conf.xml file so as to make the line look like following: • Copy the “server” and “serverinfo” elements and replace the term “biblioserver” with “publicserver” in koha-conf.xml <server id=“publicserver" listenref=" publicserver"> … … </server> <serverinfo id=" publicserver"> … <user>username</user> <password>password</password> </serverinfo> <server id="biblioserver" listenref="biblioserver"> … … </server> <serverinfo id="biblioserver"> … <user>username</user> <password>password</password> </serverinfo>

  5. Adding database in MarcEdit Z39.50 client

  6. Adding New Z39.50 Server in Koha

  7. Virtual Union Catalogue

  8. Searching in MarcEdit

  9. Searching Z39.50 targets in Koha

  10. Search result in Koha Z39.50 client

  11. Searching algorithm of VUC • Search and retrieve bibliographic information from the different Koha systems; • Extract holdings data from the retrieved MARC records; • Merge the records according to the titles or other appropriate fields; • Create a unique list of titles containing bibliographic information and holdings data of the specific titles; • Display the unique list of records in a sorted order

  12. Problems with our current approach • Depends on bandwidth and sometimes it returns no result • Dumping all the search results from the Z39.50 servers in the MySQL database and displaying the database results uniquely with holdings information of the libraries was successful, but it gets unreliable when the search returns a large set of records

  13. Challenges • Merging the search results from the different Koha ILSs and displaying unique records with their holdings information without using database has not yet been possible • Searching multiple attributes • We are looking for alternate approaches • To process the MARC records of the partner libraries properly and to identify the records uniquely, MARC records need to be complete and correct, in compliance with the MARC 21 standard.

  14. Thank you! Questions and answers

More Related