1 / 23

SRU record update and its implementations in Australia

SRU record update and its implementations in Australia. NUKAT, Warsaw. 23 January 2008. Chris Thewlis (& Janifer Gatenby) OCLC Regional Council Canberra 15 th April 2010. SRU Record Update. An Overview. Introduction to SRU Record Update.

zaide
Download Presentation

SRU record update and its implementations in Australia

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. SRU record update and its implementations in Australia NUKAT, Warsaw 23 January 2008 Chris Thewlis (& Janifer Gatenby) OCLC Regional Council Canberra 15th April 2010

  2. SRU Record Update An Overview

  3. Introduction to SRU Record Update • What it is: - A Push update mechanism, designed for union catalogues Mirror OPAC Catalogue Push Documents Repository OAIPMH Pull Catalogue Union catalogue SRU Update Push

  4. Traditional update mechanisms • Proprietary mechanism – suitable for private one off agreements only • OAI PMH & FTP • Suited for batch loading • OAI PMH is used where the data source exposes the metadata to be harvested for discovery purposes • Where the data source does not expect the data to be changed by the harvesting site or does not care • Hence one way – no mechanism for response or future synchronisation Relies on regular manual treatment of batches at both ends and results in delays, gaps, less reliable alignment of identifiers

  5. Why SRU record update? • Requirement for immediate availability of records • Scalability; no scheduling & batch maintenance • Two databases are not identical • e.g. A union catalogue is not a slave of the contributing catalogues • Requirement for interactive feedback – alignment, enrichment • Identifier of the record in the target database • Inter-record links – name and subject authorities, classification, FRBR work record etc. • Diagnostics – diffused error resolution • Warnings • Errors

  6. SRU record update : Near Real Time Machine & QA corrections and merges Inserts, updates and deletions Identifiers and diagnostics Inserts, updates, deletions Identifiers and diagnostics Both CBS and WorldCat have an SRU Pusher and an SRU catcher

  7. And in the wings to update WorldCat HeBIS ABES UnityUK GBV SwissBib ++ OLIB libraries Implementations of SRU record update • Dutch union catalogue updating WorldCat (CBS) • Libraries Australia updating WorldCat (CBS) • DNB Zeitschriftendatenbank (ZDB, Germany) updated by local systems • OCLC Library registry (catcher) • ABES (Star – online dissertations, Calames – manuscripts) • WorldCat catcher and pusher

  8. Consistency checker • Coordinated generation of tables • Contents: • Local identifier, ANBD id , Holdings symbols (Libraries Australia) • EPN, PPN, Holdings symbols (GGC) • ANDB id or PPN, OCN, Holdings symbols (WorldCat) • Run at regular intervals • Remedial action automated in obvious cases ILS WorldCat

  9. Libraries Australia And SRU Record Update

  10. Libraries Australia and WorldCat blogs Repositories, various sites

  11. ILS Batch loading ILS SRU record update WorldCat WorldCat

  12. SRU Record Update Statistics CBS to WorldCat CBS from WorldCat

  13. Amlib and Libraries Australia

  14. Amlib and Libraries Australia • LMS Developed in Australia • One of 4 LMS’s owned by OCLC • 400 libraries • Currently developing two-way SRU update • CBS (Libraries Australia) • Touchpoint (OCLC locally deployed Discovery system) • Hoping to test in the next 2-3 months • Helps to proved concept • Chance to review workflows

  15. SRU Record Update Evolution • SRU from WorldCat to Libraries Australia Q2 2010 • Corrections and enrichments • Bibliographic and holdings for libraries which catalogue directly in WorldCat using Connexion • Wish list: More data exchanged in real time with WorldCat • Detailed holdings • Authority records (VIAF and ISNI) • Synchronisation Gateway

  16. Synchronisation Gateway Near Real Time Update for All Systems

  17. Other systems need to move away from batch too

  18. ILS Batch loading ILS SRU record update WorldCat WorldCat

  19. Synchronisation Gateway LibrarySystem Send SRU Tailor Detect / Elicit

  20. Synchronization Gateway • A new solution: The Synchronization Gateway • A middleware widget that is installed on a local PC • Queries the local database via multiple protocols • Elicits records via multiple protocols • Pushes data to CBS or WorldCat via a single protocol (SRU)

  21. Nearly as good solution • One way only • Bibliographic records and holdings • May not be able to detect deletions • Will employ consistency checker to handle deletions • Machine readable reports of ANBD identifiers / local identifiers are returned • The Synchronisation Gateway does not update

  22. Synchronisation Gateway and Libraries Australia • Proof of concept testing successful with UNSW and UNILINC using: • SRU enquiry for detection and eliciting • SRU record update for loading to Libraries’ Australia CBS test database • Planning other testing with Libraries Australia • Parallel testing with WorldCat catcher

  23. Conclusion • Ensures holdings are up to date [hour/second] on target catalogue/s • Ensures holdings are accurate and complete • Eliminates batch preparation and monitoring • More flexibility for services • Australian libraries can deploy services on their own ILS, on Libraries Australia and on WorldCat • Better exposure of library materials

More Related