2021-06-14 Resource Access Meeting Notes
Date
Zoom
Attendees
Discussion Items
| Time | Item | Who | Description | Goals/Info/notes |
|---|---|---|---|---|
| 2min | Administrivia |
| ||
| 45 Min | Title level requests | Stephanie Buck Erin Nettifee | Continued discussion and updates on TLR Slide deck: https://docs.google.com/presentation/d/1m1cP0A47tmS6DcROyhQfrzaDbNFbZCwp7vgfXpG9xes/edit?usp=sharing Our TLR folder for additional info, with use cases, mock-ups and technical info: https://drive.google.com/drive/folders/1ao5l4aKi-aNLlXwzT5CJ-UCXaba5tEKE |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Reasoning | Link to supporting materials | Comments |
|---|---|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision |
| e.g. mock-up, JIRA issue | |
Request prioritization of title vs. item level requesting
what will happen if a library does both types? especially if it's both types on one instance with a combined queue
scenarios for title level only: popular novel
scenarios for item level only: multivolume sets, serials/journals
what are scenarios for when both is needed on the same instance?
- staff needs
- items from a specific collection
- hardcover, paperback, large print preference (if it is cataloged as one instance)
- items with different loan conditions when a certain loan period is needed
library staff must be able to do item level requests at any time
what happens if some copies are not requestable at all? we still need the circ rules to apply, so returned non-requestable copies wouldn't fill a request
what factors would be important in prioritizing requests?
basic: request creation date, queue position
nice to have: patron groups, location, fulfillment option, custom field
Patron group prioritization could be used for staff requests, as long as we don't have the three-part item status, or moving staff requests to the top of the queu
new idea: staff could place a title level request to get several or all items on an instance for reserve
Consortia SIG has additional needs for cross-tenant requesting like prioritize local patrons, this could fit in with patron group prioritization
not possible to move a TLR to ILR, would need to be redone
doesn't make sense to have different queues