Alma
Your feedback matters to us. Help us improve Alma 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.
4 results found
-
More possibilities for the Alma Color Theme
In the new UI, libraries can manage branding in Alma by selecting one of 6 basic colors (blue, purple, red, green, brown, orange). This configuration can only be made by a General administrator and is valid for all Alma users. We would like:
- a larger variety of colors (proposing the 216 web-safe colors would be fine);
- the possibility for any user to define their own Color Theme: color experience may be very different from one individual to another and giving everyone the possibility the use a convenient color would be appreciated.327 votes -
Pick the fields that can be exported to Excel in a set
Currently, we are limited by a pre-determined list of fields that we can export from a set. E.g. If i have a set of "Electronic Collections" or "Electronic Portfolio" records, why can't i export the URL field? Many other useful fields are also not available. Is this a challenge technically?
53 votesAfter reviewing this idea, Alma Product Management has decided to update our development plans to include this suggested change. Thank you for your contribution
-
Dark Mode/Theme
Like the title suggest, A dark mode/theme for Alma.
Having the white background can be very sore on the eyes, and many prefer the reverse ( black background / white font ).23 votesAs part of our roadmap, we are planning to add a high contrast color scheme each user can switch to when needed.
-
Consistently include Use Cases for new features listed in Release Notes
We'd like to see a use case or rationale for all Release Notes, in addition to the description of the new functionality and any necessary documentation. This could be something you could link to from the Release description, in the interest of brevity. While these are sometimes provided, their inclusion is currently sporadic.
Often while reviewing Release Notes with colleagues we find ourselves wondering exactly what problem is being solved and why someone would want to enable or adopt a new functionality. Including the use case or rationale for each enhancement could increase buy-in and understanding for a wider user…
3 votesThank you for the idea, we will work towards adding use cases for the relevant new functionality that is introduced as part of the release notes
- Don't see your idea?