1 / 34

Request Circles

Request Circles. One library's experience. Shirien Chappell Laura Willey University of Oregon NWIUG 2005. Request Circles allow libraries to:. determine which collections and branches may have items paged and delivered to/from them.

moorechristine
Download Presentation

Request Circles

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. Request Circles One library's experience Shirien Chappell Laura Willey University of Oregon NWIUG 2005

  2. Request Circles allow libraries to: • determine which collections and branches may have items paged and delivered to/from them. • decide which patrons can participate in this delivery service.

  3. Tables and fields • Fields in item, bib and patron records • Request Rule table • Circulation and OPAC options • Automatic patron blocks • Loan rule determiner and loan rules • Hold pickup locations table • WWWoptions • Locations Served table

  4. Case Study: 3 branches

  5. Eligible patrons • Only students, faculty and staff • No public borrowers, alumni or other guests

  6. Request Rule Table 1 > RECTYPE is ITEM AND STATUS = ‘o‘ 2 > RECTYPE is ITEM AND I TYPE = '31‘ 3 > RECTYPE is ITEM AND LOCATION = 'aaa2‘ OR LOCATION = 'bbb2‘ OR LOCATION = 'ccc2'

  7. Gathering data from records: Loc codes ITypes Status codes

  8. Gathering patron data

  9. Determiner table LOCATION PTYPE ITYPE RULE # 01 > ????? 999 999 0 02 > aaa1 0 0 2 03 > bbb1 0 0 2 04 > ccc1 0 0 2

  10. Loan Rule 01 > NAME 2w AAA 02 > CODE R 03 > NORMAL LOAN 14 04 > HOLDABLE Y . . .

  11. WWWOptions • REQUEST_CIRCLE_MSG • Ineligible patrons: PTypes and message • REQUEST_CIRCLE_PICKUP • Eligible patrons: PTypes

  12. What we know so far: • Patron wants Moby Duck delivered to Branch C. • It’s available at A & B. • It’s not denied via the Request Rule Table. • It is holdable for this PType. • Patron is eligible for service.

  13. Hold Pickup Locations HOLDSHELFMAP MAINTENANCE DISPLAY NAME LOCATIONS 01 > A Branch aaa1, aaa2 02 > B Branch bbb1, bbb2, bbb3 03 > C Branch ccc1, ccc2

  14. Locations Served • A Branch • aaa1 • aaa2 • B Branch • bbb1 • bbb2 • bbb3 • bbb4 • C Branch • ccc1 • ccc2 • ccc3 • ccc4

  15. End of case study Getting the book to patron: • Branch A prints paging slip • Branch A pages item & checks it in • Item’s status changes to “in-transit” • Item is delivered to Branch C and checked in • Hold pickup notice is enqueued • Patron checks out Moby Duck

  16. Things we learned • Locations Served entries must be Valid lists. • Invalid lists: system looks at all locations EXCEPT those listed.

  17. More… • You can choose which hold pickup locations display in the catalog by editing tokens in WWWoptions.

  18. More… Inn-Reach holds ignore local hold parameters

  19. Some little bugs: • Volumes act like copies • Ineligible patrons get wrong message • Maintaining the Hold Pickup table in Millennium is a known issue problem.

  20. Disclaimer Each library is different. Your experiences with Request Circles may not match ours.

  21. Thanks for coming!! Discussion

More Related