Rialto
Your feedback matters to us. Help us improve Rialto by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
22 results found
-
Fund code retention for order history needed
When a title awaiting approval in Market is rejected, the fund name is retained but the fund code is dropped. This is a problem because once it's rejected, the code information is gone and we have no other way to get that information back. Can you fix this so that the fund code is retained along with the fund name in the order history for the rejected titles (it can be retained for all if that program fix is easier, but we need it primarily for the rejected titles.
1 vote -
Allow libraries to toggle the 'Approve and order' option in the 'Manage Purchase Requests' workflow
We’ve recently discovered that our librarians, despite only having the selector role in Rialto, and thus not being able to directly place orders, are still creating POLs in Alma by selecting the ‘Approve and order’ option in the ‘Manage Purchase Requests’ workflow.
In our case, a few dozen POLs were created that had no vendor, fund code, shelving location, no platform or access model for eBooks, and no format or edition for print titles. Getting all of this after the fact from the librarians then editing the POLs is quite cumbersome and undoes a lot of the efficiency Rialto otherwise…
1 voteThank 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
- Don't see your idea?