RS-Enable shipped items to remain managed with their original TOU in order to allow requests to be done with the TOU of the permanent loc.
In some cases, requests for items under a Resource Sharing library are cancelled as their terms of use are not taken from their permanent locations. It should be possible to have shipped items remain managed by their original TOU in order to allow requests to be done with the TOU of the permanent location.

Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team
-
Anonymous commented
It would be necessary that requesting is allowed for items in Resource Sharing because
1. requests already existent BEFORE the item goes to the RS partner would indicate that the item can be loaned to RS partner only with a short loan period. Now these requests are cancelled as soon as the item is moved to the temporary RS location.2. requests that are placed WHILE the item is at the RS partner stop renewals - otherwise it would be not possible to reach the goal of borrowing items not needed by our users to other library's users as long as they need it (1 year maximum renew date) and guaranteeing that our users get items as fast as possible when they request it
This behaviour should not only be enabled for Resource Sharing, but for ALL temporary locations. As soon as an item is moved to a temporary location, the library should be able to decide if the request rules of the temporary or permanent location are in place. So probably the best place to configure this is for the (temporary) location.
-
On behalf of the Product management team we would like to understand the need and use cases of the following 'Planned' feature (which it's need was raised by a specific library) - any comment is welcome.