UB & UC An Update on Resource Sharing Developments

History of the Projects Libraries wanted to offer additional resource sharing capabilities in Voyager EIS formed UB Task Force with representatives from U System of GA, Keystone Library Network (PA), and Wisconsin System UC Task Force comprised of U System of GA staff

Task Forces and Voyager Task Forces enable Endeavor’s Product Management and Development staff to meet with end users of the product Endeavor gathers requirements through discussions about desired functionality TF members sign off on requirements to ensure that needs are met

Universal Catalog A physical union catalog with real- time links to holdings and item information maintained in the local catalogs –Supplements Simultaneous Search, Voyager’s virtual union catalog option –Single search executed against the entire cataloged holdings of U System of GA –Ensures delivery of the most up-to-date item status information

…And UC+ for Non-Voyager Libraries A physical union catalog built from the holdings of non-Voyager libraries Static holdings information provided through UC+ –No item status data Simul Search UC and UC+ for even more resource discovery options!

A Phased Project Development for UC occurs in two phases Phase 1 deals primarily with the creation and automatic updating process (database maintenance) Phase 2 provides the dynamic links from the UC to the local holdings Phase 2 also includes WebVoyage interface changes necessary for UC display

What’s UC Supposed To Do? For Phase 1, Task Force identified a set of rules that would determine UC record addition, update, and deletion –Automatically adds new bibliographic records –Creates “pointer” holdings records to local catalog –Deletes holdings records based on actions taken in local catalog –Deletes bibs in UC

What It Does: Phase 2 Using the “pointer” holdings records, UC links back to the local catalog and retrieves detailed holding and item information UC formats and displays the holdings of all libraries that own a particular title and presents these to the user Phase 2 includes several usability features, too!

Universal Borrowing Provides a mechanism for cooperative borrowing between two or more separate Voyager databases Allows libraries to share patron and item information in real-time, using “owning library” rules to determine privileges Patrons may borrow books “in person” or via a requesting function

Another Phased Project Phase 1 of UB is due to beta by September 30, 2000 Addresses the “basics” of the UB process –Communication between databases, matrices, patron information, etc. Phase 2 will include additional capabilities –Holds/Recalls, “Smart Requesting”, complex load leveling, etc.

General UB Principles UB is a circulation function, not ILL! UB should be as seamless as possible The library that owns an item “owns” the transaction and governs the privileges that are extended –Flexibility to implement local policies –Counters kept at both local (aggregate) and owning institution to allow 2 levels of blocking –Fines/fees paid to owning institution

“In Person” Borrowing Assumes that patron visits a library other than his or her local library Patron identifies desired material and proceeds to Circulation to charge the items

“In Person” Borrowing, cont. Circ staff scans borrower ID and selects appropriate “home” institution for patron Patron record at “home” library checked for blocks “Stub” record created at “owning” library “Home” library patron group mapped into UB patron group at “owning” library

“In Person” Borrowing, cont. Blocks checked for patron in “owning” library Item charged based on UB patron group and item type as defined in “owning” library privileges matrix In person borrowing should be a seamless process similar to a regular circulation transaction

Remote Requesting Patron identifies a desired item through a Simultaneous or UC search Patron logs in via the Request button and selects “Remote Request” UB queries the individual databases in which the item is held to determine eligibility for remote requesting UB randomly selects an eligible copy on which to place the request

Remote Requesting, cont. As with in person borrowing, patron stub record created in owning library Request routed to owning library Staff selects book from shelf and processes the request –Shipping label produced –In transit message applied to item –Materials sent to pick-up location specified in the request

Remote Requesting, cont. When the item arrives at destination, staff discharge item to trigger notice production and update status Patron charges book –Matrix at owning library checked and used to determine privileges

Return an Item Anywhere! UB also provides the ability for patrons to return a borrowed item at any participating UB library Voyager determines to which library the item belongs and contacts that library to discharge the item “Stub” record in owning library database updated or deleted Patron record in “home” library database updated