2017-10-16 Resource Access Meeting Notes
Date
Oct 16, 2017
Attendees
Andrea Loigman
Tania Hewes
William Weare
Mark Canney
Cate Boerema (Deactivated)
Rameka Barnes
Kimie Kester
Deb Lamb
Mark Canney
Charlotte Whitt
Wendy Wilcox
David Botorff
Goals
Begin developing requesting functionality
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
5min | Housekeeping | Andrea Loigman |
|
55 min | Requesting | Tania Hewes |
|
Notes:
Topic: Requests
Tania Fersenheim
Loan Policy Metadata
Request types / “requestable”
Hold: non-renewable
Hold: alternatively, could be renewed so patron can keep as long as s/he needs it; or this could be flagged for circ review, etc; see staff request;
Recall: shortens loan period; non-renewable
Storage request: Storage & paging need to be separate requests; the system needs to be able to talk to external system (ASRS, for example)
Paging request (“paging”)
Set aside for later discussion:
Staff request (examples)
Recalls for reserves
Scanning requests
Fulfillment (?)
Set aside for later discussion:
Scanning / digitization
Resource sharing request: externally initiated, by ILLiad, etc. via NCIP
[Interoperability w/ ILLiad]
Loan policy / Request policy
ALMA: Fulfillment Configuration Utility Page:
Can request policy settings be included in loan policies? Are these separate things?
Link to Filip’s prototype:
If loan rules and request rules are separate, how would they work together?
Not all requests are for something that is a loan (storage, paging)
Loan policies: what governs the transaction: is it loanable?
Loan rules: this is how you target a loan policy to a transaction; [Ex: for this transaction, use loan policy A]
Next steps?
Tania:
Focus on one request type & think about all the pieces
Look at recall & holds, what policies do we want to govern them?
Cate:
Proposed user interface for locations