|5min||Logic for due date calculation check||Cate Boerema||Review of logic for truncated due date calculation||Have I captured the expected logic correctly in the SIG meeting notes? (#8 under Loan policy mockup section in Meeting outcomes section): https://wiki.folio.org/display/RA/2018-11-29+Resource+Access+Meeting+Notes|
|20min||Request-related notices||Darcy Branchini||UI options||Decisions on UI and field options for request related notices.|
|20min||Disabling and deleting service points||Cate Boerema||What if a SP is created by accident or is no longer in use? Deleting SPs is challenging because of the various dependencies. Should we inactivate instead? What's the expected behavior in both cases for locations, requests and loans that use the SP?|
|Planned Release (if known)|
Link to Supporting Materials
|e.g. loans, fees/fines||Name||e.g. Q4 2018, Q1 2019||Clearly stated decision||e.g. mock-up, JIRA issue|
How do minimum guaranteed loan period, original due date, and recall return interval interact when an item has been recalled?
Always use current date + recall return interval = new due date?
Check to see if original due date is earlier than current date + recall return interval?
Stress case: using the recall return interval to extend any loan by X number of days may have the effect of _extending_ a loan, even on a non-renewable item
Chicago currently does this (and does not have recalls on short-term loans), Duke does not
Workaround: Use recall return interval to set up the appropriate degree of generosity to the patron whose item has been recalled
If your recall return interval is 1 day, the loan period is 7 days, and the minimum guaranteed loan period is 7 days
Then Days 1-6, if the item is recalled, the original patron gets a 7 day loan
Then Day 7, if the item is recalled, the original patron has to turn it in on day 8, getting an extra day without even renewing the item
Then Days 8-infinity, if the item is recalled, the original patron has to return it the next day (and they've already gotten it beyond the guaranteed 7 days)
Can set recall return interval to 0 if the recalling patron should never be kept waiting
Ideal (parking lot): Create a separate setting at the policy level (not tenant) to decide whether original due date or current date + recall return interval is used
Question about whether the policies are containers for (loan, fee/fine, request) and a loan rule points to one container, or are the policies broken up and the circ rule points to individual policies
Fields in policy:
Darcy showed possible configurations for request available, request available reminder, cancellation, and hold expired, as well as for recall notices