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.
7 results found
-
Per user feeds
Rialto should support per user feeds that are useable only by users that they are assigned to. This will create a less cluttered experience for selectors that are only interested in their own feeds.
53 votes -
Automatically remove titles that no long meet DDA Selection Plan criteria from Rialto DDA pool, Ebook Central/LibCentral and Alma repository
When a DDA title increases in cost so it exceeds the maximum cost we set for our DDA, it becomes untriggerable and inaccessible on the Ebook Central platform, but the title remains in our DDA pool in Rialto and our Alma holdings, so users can find the title in Primo but cannot access it. Removing these titles requires a cumbersome manual workflow. This enhancement would make it so titles that no longer meet our DDA selection plan criteria are removed from our DDA pool automatically in Rialto, Ebook Central/LibCentral, and in the Alma repository.This would ensure users don't discover inaccessible…
16 votes -
Duplicate a Selection Plan
We'd like to be able to duplicate existing selection plans. See the image for more information. We're finding it helpful to duplicate them for experimentation. Thanks!
6 votes -
Better publisher filters in Rialto query builder
It is difficult to exclude publishers from a DDA pool due to poor filter design in Rialto. The filters rely on keyword matching rather than controlled values. This allowed unwanted publishers' books to enter our DDA pool, and the removal process was tedious and highly error prone, taking months to complete. Rialto needs better publisher filtering so unwanted publishers do not enter the DDA pool at all. One possibility is that publisher names could be a controlled vocabulary selected via a dropdown menu. This would ensure that unwanted publishers are excluded from libraries' selection plans. This would also eliminate the…
6 votes -
Export Feed to Title Alert
Please add the ability to save or export a Feed as a Title Alert. Building a Feed and Title Alert are very similar, and it would save our staff time if they could export an existing Feed to a Title Alert.
4 votes -
Ability to Set Parameters in Purchase Request Forms
We have a preferred set of publishers, platforms, and/or vendors that buy eBooks from. Currently, there is no way to set up Purchase Request Forms for our users to request ONLY from those preferred sellers.
It would be great if there was a way to define our preferred publishers (and even other facets) in the Purchase Request Form configuration, so we don't have to deny a ton of incoming requests.
2 votes -
keep history of rejected titles from selection plans
It would be helpful to have a history of what titles have been rejected from selection plans. This data can help us understand when certain titles did not come on selection and give us a dataset to analyze to improve the selection plan for the goal of making it more automated.
1 vote
- Don't see your idea?