Brady Cross
My feedback
13 results found
-
114 votes
Dear community,
Thanks for raising this idea.
The conceptual solution which is currently being evaluated, is to allow the user to choose/control the desired timeout session period from 4 options (in minutes) - 60 (current, and default) , 90, 120 or 150.
This reflects a potential increase of up to 250% in session timeout period.
Please let us know if you have any comments regarding the suggested solution.
Thanks,
Uri Beladev
Platform Product Management team
An error occurred while saving the comment An error occurred while saving the comment Brady Cross
commented
Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.
An error occurred while saving the comment Brady Cross
commented
Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.
Brady Cross
supported this idea
·
-
7 votesBrady Cross
shared this idea
·
-
59 votesBrady Cross
supported this idea
·
-
4 votesBrady Cross
shared this idea
·
-
3 votesBrady Cross
shared this idea
·
-
4 votesBrady Cross
shared this idea
·
-
9 votesBrady Cross
supported this idea
·
-
37 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 Management
Brady Cross
supported this idea
·
An error occurred while saving the comment Brady Cross
commented
I would like to add to Jonathan's suggestion by stating that adding notes, interested users, etc. at the moment an item is located in the Marketplace would dramatically enhance Rialto's usefulness. Equally as important, all notes, etc. should be included all the way through the cataloging process. I would rather the cataloger make the decision to delete any notation. This would enable the selector to communicate important information to other selectors as well as technical services without having to duplicate their efforts.
-
27 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
An error occurred while saving the comment Brady Cross
commented
All notes, all comments, all associated content should be available to be added at the time of selection and all markups should remain with the item all the way through approval and also be available when cataloging the item. The selector needs to be able to communicate why the item was selected to the cataloger and that information needs to be part of the item record. I would rather the cataloger decided if notes need to be removed. For example, the selector chooses "Nursing, 3rd ed." in February, they may not remember why this item was selected a month later or even after the item is sent to a list. The selector needs to indicate why the item was selected (for NURS 101, Dr. Soandso) when the item is investigated in search. The attached notes need to go all the way through the process to the cataloger and need to be part of any exports to Excel at any point in the process.
Brady Cross
supported this idea
·
-
17 votes
An error occurred while saving the comment Brady Cross
commented
I agree. This would enable functionality in Rialto that we have been using for years in Gobi.
Brady Cross
supported this idea
·
-
3 votesBrady Cross
shared this idea
·
-
6 votesBrady Cross
shared this idea
·
-
35 votesBrady Cross
supported this idea
·
I would suggest going as far as 8 hours. Ideally, I would like to be able to select the timeout setting per user. Frontline student assistant staff may need shorter timeouts (15 to 30 minutes) whereas technical service staff would benefit from an extended timeout (8 hours). It would be OK if the timeout configurations were associated per role (manager has longer timeout than student assistant staff).