Union Catalog

 
M3 allows users to create, maintain,  and communicate using the following union catalog models.  A wide area network (WAN) or dedicated Internet connection (static IP address) for each library site is required  to set up a union catalog.
 

M3  Classic Merged Model

M3’s  Classic  Merged Union  Catalog, running on one or more central servers,  pro- vides information to all affiliated libraries from a single MARC database. The  union catalog takes bibliographic  and holding records  from each participating library and merges them into the single  database. This centralized  database contains  a single master bibliographic record for each title in the union collection and sepa- rate holding records identifying location, call number, and barcodes at the site level. Duplicate  barcode records  are merged and associated holding  records,  each containing a unique holding  symbol  (location  code) identifying the owning library, are re-linked to the “master” bibliographic record. Individual  library sites can use M3’s scoping feature to browse only their local collection, selected collections,  or all collections in the union  catalog. The system links to affiliated libraries using either a WAN or the Internet.  A T1 line is highly  recommended for adequate com- munications performance. This model runs on a central server  solution.
 
 
NOTE: There is an additional charge for the creation of the Classic Merged Union
Catalog. Charges vary according to the number of sites and records.
 
OPAC Access – If all affiliated libraries run M3, no additional software is required. Patrons  can select from any number of library locations for information.
 
Circulating from the Union Catalog – Circulation  occurs independently at each individual library. Transactions update the associated holding  records  instanta- neously over the WAN. There are no local databases and the shared  database only exists on the union server.
 
Cataloging and Maintenance – Reports and batch processing, such as import and export, are run at the central site only.  Merged union  catalogs can be updated cen- trally or locally:
 
  • If cataloging is performed centrally, record edits can be made to either  the bibliographic record or the linked  holding records.  Changes are immedi- ately displayed in the OPAC. New records  can be imported  in batches with automatic system  checks for duplicates. If duplicates are found, the system  can add new holding information  to the existing bibliographic record. If the system  has both a merged union  catalog and individual cat- alogs at each location,  the union  catalog system  can output  a file of new and updated records  for downloading into the local site catalogs. Software can also be installed, allowing remote libraries to automatically download bibliographic  and/or holding records  when newly added items  are scanned.
 
  • Some systems  may want to allow affiliated libraries to edit records from remote sites. Cataloging software  can be installed  at the remote sites to provide access to any required  cataloging functions.
 
Virtual Union Catalog  using M3  Core Package and Remote  Site Software
M3 (with custom configuration) allows any multiple-site library running M3 to be part of a virtual union  catalog. If a merged  database is not desired or if libraries are not directly affiliated, libraries can participate  in a virtual union  catalog but maintain their collections  separately. A virtual union  catalog is created by installing  the M3 Core Package on all library automation servers and M3 client software  at each library site. Each participating library must  have M3 Library Automation software and set up its own separate database. M3 Server software can be configured  so patrons  can search single  or multiple databases simulta- neously. There is a charge  for customizing the software based on the number  of library collections. This model runs on central server or local server solutions.
 
OPAC Access – A directory is created which includes  the IP address  of each partic- ipating library. Once this is defined, OPAC searchers can select all sites or specific sites for searching.  When a search is executed, results are returned along with library locations. Duplicate records are not automatically removed in a virtual union catalog.
 
Circulating  from the Union Catalog – Circulation occurs at each individual library.
 
Cataloging and Maintenance – Reports are generated and cataloging is updated at each individual library.
 
Note: Mandarin offers BookWhere V4 and Book- Where Online as optional Z39.50  client software. See Chapter 12 for more information.
 

Virtual Union Catalog with M3  Core Package and Z39.50Protocol

Z39.50 software is not required for a virtual union  catalog unless libraries not using M3 are participating union catalog members.  Library sites not using M3 must  have Z39.50 client software  to access and search bibliographic information. They must  also have Z39.50 server software so M3 can broadcast their biblio- graphic information and allow it to be searched by other libraries. Performance is dependent on the total number  of sites, circulation  and patron workstations,  and the communications infrastructure (T1 lines are recommended). This model runs on central server or local server solutions.
 
OPAC Access – A directory is created which includes  the IP address of each partic- ipating library. Once this is defined, OPAC searchers can select all sites or specific sites for searching.  When a search is executed, results are returned along with library locations. Non-M3 sites require Z39.50 services to be searched by M3.  The sites running M3 need to be configured to search the non-M3  sites using Z39.50. When searching non-M3 sites, holding and transaction information is not usually available. Duplicate records are not automatically removed in a virtual union cat- alog.
 
Circulating  from the Union Catalog – Circulation occurs at each individual library.
 
Cataloging and Maintenance – Reports are generated at each individual library. Virtual union  catalogs can be updated centrally or locally:
 
  • If cataloging is performed centrally,  bibliographic  records  can be imported in batches from remote building sites to the specific record col- lections on the central server.
 
  • If cataloging functions  are performed at the local site level, cataloging can be restricted  to authorized staff and specific record collections.  Updates at the site level are immediately displayed in that site’s OPAC.