UB & UC @ USG

1. UB & UC @ USG An Update on Resource Sharing Developments Kathryn Harnish — June 5, 2000

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

3. 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

4. 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 USG • Ensures delivery of the most up-to-date item status information

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

6. 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

7. 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

8. 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!

9. Current Status of UC • Phase 1 was delivered on time to beta in April • Four institutions currently testing the automatic update processing • Phase 2 requirements awaiting USG signoff with development to begin soon • Phase 2 delivery scheduled for September 30, 2000

10. Let’s Look at Phase 1 UC!

11. 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

12. 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.

13. 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

14. “In Person” Borrowing • Assumes that patron visits a library other than his or her local library • e.g., a GA State student visits UGA’s library • Patron identifies desired material and proceeds to Circulation to charge the items

15. “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

16. “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

17. 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

18. 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

19. 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

20. 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

21. Thanks to USG…. • Your colleagues have spent a lot of time in discussions with Endeavor • Their experience has made both UB and UC a success!