Alison Davis
My feedback
27 results found
-
70 votes
Thank you for your suggestion. The Rialto team is reviewing this idea to determine how it might fit into our future plans. We cannot provide a timeline for these ideas, but be sure to check back often and vote for the ideas you support to receive status and comment updates.
Best,
Heidi Whitehead
Rialto Product Manager
Alison Davis supported this idea · -
96 votesAlison Davis supported this idea ·
-
486 votes
This improvement is planned for the 2024 Roadmap.
Alison Davis supported this idea · -
121 votesAlison Davis supported this idea ·
-
182 votesAlison Davis supported this idea ·
-
72 votesAlison Davis supported this idea ·
-
114 votes
We are exploring options for this idea. The priority of the results is set by either Primo or Summon, so we cannot simply show the newest edition first unless the discovery ranking changes. However, we could potentially develop an option using the Questions feature in which the system could recognize that the instructor has added something which has other editions. The library could then configure a question for the instructor to understand if they want that edition, any edition, or the newest edition, for example. Would this help meet the need?
Alison Davis supported this idea · -
103 votesAlison Davis supported this idea ·
-
391 votesAlison Davis supported this idea ·
-
339 votes
When a loan due date is shortened due to patron expiry, Alma will retain and internal an indication for that on the loan record. This way when the patron expiry is updated (shortened OR extended) the loan due date will be recalculated using the loan date (i.e. as if the recalculation is happening at loan time).
This way, the due date may be extended or shortened according to the new expiry date.
An error occurred while saving the comment Alison Davis supported this idea · -
19 votesAlison Davis supported this idea ·
-
6 votesAlison Davis supported this idea ·
An error occurred while saving the comment Alison Davis commentedI'd like to request that this not be a button at all, but rather have the queue information displayed by default. Why should the patron have to click a button (which doesn't even display as a button, but rather just capitalized text) to show how many people are ahead of them on a request? Primo (not VE) has the ability to automatically show this information AFTER the request is submitted, but this message isn't available in VE. We consider this a great loss in functionality.
-
336 votesAlison Davis supported this idea ·
-
3 votesAlison Davis shared this idea ·
-
4 votesAlison Davis supported this idea ·
-
50 votesAlison Davis supported this idea ·
-
135 votesAlison Davis supported this idea ·
-
40 votesAlison Davis supported this idea ·
-
5 votesAlison Davis supported this idea ·
-
1 voteAlison Davis shared this idea ·
In NERS, there is a private note that says "2023: This functionality is already available." Where is this configurable?