1 / 31

Consortium Models in the European Market

This seminar discusses the different data models for shared systems in consortia, focusing on the European market. Topics include administrative data, bibliographic data, circulation data, and more.

nevels
Download Presentation

Consortium Models in the European Market

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. ALEPH Consortial Models: European Market Test Cases Birgit Thede Implementation Manager Olybris, Ex Libris Seminar 2005 Kos, April 2005

  2. Consortia and ALEPH 500 • What is a consortium? • Consortium may be a shared system • Consortium may consist of single libraries that share software or services • This session refers to different data models forshared systems, and focuses on the European market.

  3. ADM Administrative data BIB Bibliographic data . . Items Serials Acquisition data Circulation data Administrative data Authority data AUT System wide library administration Holdings HOL Authorization Defaults User ALEPH: Database and Logical Structure Standard formats ALEPHformat

  4. Single Local System Copy Cataloging BIB AUT External data Updates HOL ADM

  5. Single Local System (cont) • Shared installation/server • All institutions share a single BIB record • All institutions share one ADM library (one ADM record per BIB) • Institutions use different sub-library codes • Partially shared ADM data (vendors, users), if desired • Shared ADM configuration tables • Authorization/permission setup required to limit access control per institution

  6. Single BIB with Multi-ADM Libraries Copy Cataloging BIB External Data AUT Updates HOL ADM ADM ADM

  7. Single BIB with Multi-ADM Libraries (cont) • Shared installation/server • All institutions share a single BIB record • ADM library per institution or group of institutions • Shared users, if desired • Separate ADM configuration tables • Each institution controls its own ADM data • Separate sub-library codes if a group of institutions share one ADM library

  8. BIB BIB BIB BIB BIB BIB BIB BIB BIB BIB BIB BIB BIB HOL HOL HOL HOL HOL HOL HOL HOL HOL HOL HOL HOL HOL ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM Multiple Local Systems – Shared Installation AUT External Data

  9. Multiple Local Systems – Shared Installation (cont) • Shared installation/server • Shared node tables (ALEPH 500) • System downtime involves all institutions • Collective upgrade to higher version • Separate BIB/ADM per institution or group of institution • Each institution controls its own BIB and ADM data • Separate configuration tables per BIB/ADM • Shared users, if desired

  10. ADM Record ADM library VirtuallyDe-duplicated Union Catalog (Union View) with Multi-ADM BIB file BIB Record* BIB Record* BIB Record* ADM Record ADM Record ADM library ADM library * Three copies of the same BIB record

  11. VirtuallyDe-duplicated Union Catalog (Union View) with Multi ADM (cont) • Shared installation/server • Each institution controls its BIB and ADM data • Separate configuration tables per BIB/ADM • Virtually de-duplicated Union Catalog (Union View) for OPAC (desirable) • Logical views/logical bases are recommended for cataloging purposes

  12. Separate Catalogs and a Union Catalog Union Catalog BIB Library BIB Library BIB Library BIB Record BIB Record BIB Record ADM Record ADM Record ADM Record ADM library ADM library ADM library

  13. Separate Catalogs and a Union Catalog (cont) • Enables multiple servers (per institution) • Each institution controls its BIB and ADM data • Virtually de-duplicated Union Catalog for OPAC (desirable) • Upload of bibliographic records and HOL information • Circulation status may be obtained from local systems • ALEPH and NON-ALEPH local systems

  14. Z300 BIB ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM HOL Z30 BIB Central Catalog – ALEPH Cluster AUT External data Copy Cataloging Updates Central System HOL Updates Replication ALEPH -Cluster Local Systems

  15. Central Catalog – ALEPH Cluster (cont) • Enables multiple servers (per institution) • Each institution controls its own BIB and ADM data • Bibliographic and AUT records are cataloged centrally (ALEPH CAT client) • Holdings and items are entered locally • Interface: ALEPH Cluster replication • Replication of BIB records: central -> local (ue_11) • Replication of HOL records and items (z30): local -> central (ue_11) • Local systems use central AUT data (ue_08) • Web-OPAC: Jump into the local OPAC • ALEPH Cluster: connection ALEPH <-> ALEPH and ALEPH <-> ALEPHINO

  16. Central Catalog – ALEPH Cluster (cont) Workflow • BIB records are always created centrally first, then copied manually (CTRL+N) to the local BIB • BIB records are centrally available -> copy (CTRL+N) to the local BIB. • Every BIB or AUT update is automatically replicated to the local systems. • HOL and item records are only created locally, and updated with automatic replication to the central system.

  17. message (z105) ue_11 No Exit ADM ADM ADM ADM BIB BIB Central Catalog – ALEPH Cluster (cont) Central BIB Local BIB BIB Update ue_11 Does it exist locally? Yes Update BIB Replication

  18. ADM ADM HOL Central Catalog – ALEPH Cluster (cont) Local HOL Central HOL Message (z105) HOL ue_11 Does it exist centrally? Creation Update Deletion YES No ue_11 Update Delete Create HOL Replication HOL

  19. ADM ADM Z30 Central Catalog – ALEPH Cluster (cont) Local Items Central BIB (z300) Message (z105) Z300 ue_11 Does it exist centrally? Creation Correction Deletion Yes No ue_11 Update Delete Create Item Replication Z300

  20. ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM ADM AUT BIB Central Catalog – Local Owner Update -> Non-ALEPH Local Systems Central BIB records contain local owner information (LOW-tag) External Data Copy Cataloging AUT BIB Updates Local systems

  21. Central Catalog – Local Owner Update -> Non-ALEPH Local Systems (cont) • Central “LOW” creation and deletion triggers z115 message • Central record update triggers z115 message • Local system fetches z115 messages • Local system collects record (Z39.50) • Interface: • VST server provides z115 messages • Web-OPAC: Jumps into the local OPAC • GUI-Search: Displays remote items

  22. Central Catalog – Local Owner Update -> Non- ALEPH Local Systems (cont) Workflow • BIB and AUT records are catalogued centrally (ALEPH-GUI-Client). • LOW tag is added/deleted manually -> triggers the creation of a z115 message. • Administrative data and holdings are only maintained locally. • Local system collects BIB and AUT data based on z115 message, using Z39.50 (automatic process).

  23. Central Catalog – Local Owner Update -> Non-ALEPH Local Systems (cont) Special functionality • Adding a LOW tag triggers export of record information (record identifier + short BIB information) to local PC. • Information can be used to collect a record if automatic background update failed (or is not fast enough).

  24. Central Catalog – Local Owner Update -> Non-ALEPH Local Systems (cont) Function: View Local Owner Client-Konfiguration: Catalog.ini [General] LOWSupport=Y “View Local Owner” is available in Cataloging and Search!

  25. Central Catalog – MEX Items -> Non-ALEPH Local Systems HOL External Data AUT BIB • Central Holdings include item information – MEX items. • One MEX tag per item. • Items are cataloged using the ALEPH GUI client.

  26. Central Catalog – MEX Items -> Non-ALEPH Local Systems (cont) • Non-ALEPH local systems • Central cataloging of BIB and AUT records - ALEPH-CAT-Client • HOL and item information is created centrally – ALEPH-CAT-Client • Items = MEX – no Z30! • No automatic replication! • Interfaces: • CAT-Download • Batch-Update

  27. Central Catalog – MEX Items -> Non-ALEPH Local Systems (cont) Workflow for Non-ALEPH-Systems • BIB, AUT, HOL and items are entered centrally • Items = MEX Items (item information is part of the HOL record) • CAT-Download: manual export of single BIB, AUT or HOL + items (MAB) – automatic import (local function) • Batch update of local system in addition to Cat-Download

  28. Central Catalog – MEX Items -> Non-ALEPH Local Systems (cont) HOL record includes item information Client-Konfiguration: Catalog.ini [General] HOLItemSupport=Y

  29. Central Catalog – MEX Items -> Non-ALEPH Local Systems (cont) ALEPH Cataloging - Items tab -

  30. Central Catalog – MEX Items -> Non-ALEPH Local Systems (cont) LDR L 00134vM2.01200024------l … CAT L $$aBATCH$$b00$$c20000216$$lHBZ60$$h2246 MEX L $$aUDO50000000036-000020$$b505645$$c001 $$eJc B 858$$iJc66/1609$$j20000718$$kkA $$mBOOK$$o20000718$$s290_6$$u20000718 MEX L $$aUDO50000000036-000030$$c103$$eP 490 ABEG $$iBSR 2000/912$$j20000217$$kkA$$mBOOK $$o20010202$$s290_6$$u20010202 MEX L $$aUDO50000000036-000040$$c103$$eP 490ABEG $$iA 107/67$$j20000217$$kkA$$mBOOK $$o20010202$$s290_6$$u20010202

  31. Central Catalogs – Examples HBZ – Hochschulbibliothekszentrum des Landes Nordrhein-Westfalen, Köln • ALEPH-Web: http://okeanos-www.hbz-nrw.de/F • Data model: ALEPH Cluster + MEX-items BVB – Bibliotheksverbund Bayern, München • Metalib: http://bvba2.bib-bvb.de/V?RN=680510815 • Data model: Local Owner Update ACC – Österreichischer Bibliothekenverbund, Wien • ALEPH-Web: http://magnum.bibvb.ac.at/ALEPH • Data model: ALEPH Cluster

More Related