|
Technology (How do they make it do that?)
The Shared Catalog (Z39.50)Usually when libraries create a shared catalog, they all have the same automated library system. OhioLINK uses Innovative Interfaces, CLEVNET uses SirsiDynix Unicorn, and SEO and the CLC uses SirsiDynix Horizon. In order to connect every library in the state (school, public, academic), the VDX software uses the Z39.50 standard, which provides a searching interface among disparate systems. By using Z39.50, users do not have to be familiar with searching commands for each system or the address for each catalog. By clicking the "OHIO LIBRARIES SHARE MORE" (OLS: MORE) button in their Web catalog or the library's Web page, users can re-execute their search statewide, find the desired item, view holdings, and place a request. Z39.50 translates the search and sends it to the catalogs of all participating libraries. It retrieves bibliographic information for display to the patron, along with holdings. Many automated library system vendors have a Z39.50 interface for linking library catalogs; OCLC also has a Z39.50 interface for their cataloging subsystem. MORE information on Z39.50 can be found on the Library of Congress Web site. [top] Patron Authentication (SIP)Because remote searching of catalogs has become increasingly popular, more information from automated systems has been needed to accommodate complex transactions, and SIP has evolved to accommodate these demands. There are two versions of SIP: SIP and SIP2. SIP can communicate basic transactions such as validating a patron and checking an item out and in; SIP2 prevents delinquent patrons from making requests and has a holds messaging feature that places holds for items directly into your local system. Documentation for SIP and SIP2 is available in from the 3M Website.
More Advanced Functions (SIP2)Because remote searching of catalogs has become increasingly popular, more information from automated systems has been needed to accommodate complex transactions, and SIP has evolved to accommodate these demands. There are two versions of SIP: SIP and SIP2. SIP can communicate basic transactions such as validating a patron and checking an item out and in; SIP2 prevents delinquent patrons from making requests and has a holds messaging feature that places holds for items directly into your local system. Documentation for SIP and SIP2 is available in from the 3M Website. Not all implementations of SIP are the same. Because SIP is only a protocol and not a standard,automation vendors interact with SIP in different ways, and probably have not put all of the SIP functions into their system. Talk to your automation vendor about their use of SIP and what messages they support. Here are some desired message functions:
Will this ever be more standard?Yes! The National (U.S.) Information Standards Organization approved the NCIP standard, Z39.83. It takes time for automation systems to incorporate NCIP, because standards, being robust and reliable, are more difficult to implement than protocols. In saying that, the schedule for those vendors who are NCIP compliant with OCLC is as follows:
NCIP will allow you to do more of the resource sharing tasks in one system as opposed to duplicating tasks in both systems. If your automation vendors is not listed above; now that it has been approved, contact yours and ask them about their development plans! If your automation vendor is up there contact them and find out when they will be done with Testing and Development of NCIP with OCLC. Details about NCIP are available from the NISO Website. [top] [Back to the OLS: MORE Project Information Page] |