They appear as "renewable" items that really aren't
In Primo, they appear as "renewable" copies really are not because they already have the maximum number of renovations. Why not say directly "not renewable"?
![](https://secure.gravatar.com/avatar/e286df9bb8574f6dd07441557a8fce12?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 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 Primo.
Best regards,
Primo Product Team
-
Manu Schwendener commented
This sounds more like a bug to me.
(Meaning: I agree that this should not be happening) -
Chris Jones commented
This is a cross LMS issue with Primo. Customers query why they see "Status: Renewable" (which is the theoretical policy), rather than the dynamic user reality, i.e. will a loan renewal attempt succeed? It causes confusion all around as staff do not see this information from the LMS - commonly occurs in Alma and Primo customer queries, but clearly others as well.
-
Anonymous commented
The check does Aleph in the time of renewal but no before and there is no kind of pre-programmed-check into the system.