Why are Resource Sharing renewals rejected?
- Product: Alma
Question
Why was a renewal request rejected for a Resource Sharing item?
Answer
A renewal request may be rejected for several reasons.
-
Maximum Renew Date
-
Any requests for renewals will be blocked if the desired due date exceeds the Maximum Renew Date. The desired due date will not automatically truncate based on this date.
-
-
Original Due Date
-
Another factor in place when requesting renewals is the original due date determined by Terms of Use that are set by the lending library. In order for renewals to be processed successfully, they must extend the length of the original loan. If the loan is not extended, the renewal may be blocked even if the Maximum Renew Date is not exceeded.
-
For example, if an item falls under Terms of Use that allow loans for 2 weeks on the lender side, but loaned under the Terms of Use that only allow 1 week on the borrower side, any requests for renewals would fall inside the original due date set by the lender. Since the length of the loan would not be extended, the item would not register as eligible for renewal.
-
-
-
Library Opening Hours
-
Additionally, the borrowing library will need to be open on the new desired due date. If the borrowing library is closed on the desired due date, the desired due date will be moved backward in time to the closest open date. The Lending Resource Sharing Terms of Use has implied closed due date management and that is set to default at the previous open day.
-
The ignore_lender_due_date parameter is in place to ignore the lender due date when loaning an item. However, this parameter does not apply to renewals, and renewals are based on the lender's response to the request. Thus, the renew cannot be set after the given due date and is always set backwards. If this open date is before the original due date, the renewal would be blocked as it does not extend the length of the loan.
-
-