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.
120 results found
-
Embargoed resources displaying in Primo
Currently records from within an embargo period are discover-able to end-users via Primo.
The user then thinks we have access to the records and selects it only to be presented with No full text available.
Embargoed records are outside of our coverage range and should not display in our discovery interface.39 votes -
Improve the ease of reordering the Online Services Order and General Electronic Services Order tables
Currently, items in the General Electronic Services Order and Online Services Order tables need to be moved using up and down arrows. This can be very time-consuming if the tables contain numerous items. It would significantly improve the ease of use i, the items in this list could be resorted either through drag-and-drop or by moving a given item to a numbered slot in the table (similar to the Netflix interface).
37 votes -
Add the option to custom harvest the entire institution's SUSHI accounts
We usually analyse the usage data of the whole previous year. In our "Monthly usage data" overview many reports failed. We have 100+ vendors with SUSHI accounts.
To manually go to each vendor and custom harvest the year's usage data takes a long time.
Please include the option to run a job that harvests ALL SUSHI data as a custom harvest.
37 votes -
Make "updated by" field configurable, not primary ID
There are many areas in Alma that will list the last Alma user to update something. These fields will display the primary identifier of the last updater, but we find this is not particularly helpful when we log in with our campus shib accounts, as this makes our employee ID number show up here. It would be more helpful if we could use Last Name, First Name or something similar in the Updated By fields.
36 votes -
Alma should remove any whitespace before/after identifiers, barcodes, call numbers etc.
Alma should automatically remove any leading or trailing whitespace in user identifiers, barcodes, call numbers etc. - any kind of identifiers entered manually or via copy&paste. Barcodes that are not working, users that are not matched at login are examples of real-life malfunctions that cost us time to analyze, all caused by a simple trailing blank entered in a form. It could be easily trimmed by Alma itself with neglectible implementation effort.
31 votes -
rfid: write AFI-value to the tag in item editor
Please write the secure AFI-Value, if a staff user use the button "write RFID and save" inside item-editor.
We use empty RFID-Tags. So we have to initialize the AFI-Value for each tag. Now we have to go into fulfillment area and return an item to write the secure value to the tag.
If in the item-editor the AFI-value would be written it helps a lot and save time.
30 votes -
Default options for tasks should be configurable by the library
I have a support case open (Case 06893601) that requests the ability to change the default option for “In-House Use”. This support case and others like it could be addressed by allowing the library to configure whether an action is the default.
A search of the Idea Exchange for "change default" results in a lengthy list from all areas, the cumulative effect of which clearly illustrates the need for this change.A few examples:
Reading Room Final Check-in
Warning message to confirm Check-In for Shipped Items
Release remaining encumbrance
Metadata Editor Templates to suppress from discovery and Don't publish to…30 votes -
Model the Course/Reading List association as a many-to-many relationship
We need to be able to affiliate the same reading list with multiple course objects in Alma. Currently, reading lists can only be assigned to a single Alma Course object at a given time. At our university with a complex course timetable structure we need to be able to accommodate complex relationships between cross-listed and "meets with" courses. For these courses, we must accommodate a single course that is offered by multiple departments or at multiple course numbers (e.g., undergraduate and graduate versions of the same course "meet with" each other by sharing a lecture).
For example, our Computer Sciences…
29 votes -
Alma new layout: better visual distinction between Alma Main Menu and Alma Configuration
Hello.
I'm testing the new layout of Alma. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/045Usability_Improvements/Layout_Improvements
One major change is that the Main Menu (with the Alma functional areas: Acq, Resources, Fulfillment,...) is now on the left side. The Alma Configuration Menu is also on the left side.
It can be difficult to visually distinguish between the Main Menu and the Configuration Menu. (Please see "Alma new layout, Main Menu vs Config Menu.png")
For example, I think I'm in the Alma Main Menu so I click on Resources to Manage Import Profiles. But I'm actually in the Configuration Menu so when I click on Resources I go…
28 votes -
File differences included with Release Notes
It would be very helpful if ExL included a Differences report (.diff file) for the Delivery-System-Skin mashup CSS file (mashupnew.css) and also any Letter-template XSLT files which have changed for each new Alma Release, and to post them alongside the Knowledge Base article for the release (ie. https://knowledge.exlibrisgroup.com/Alma/ReleaseNotes/00992017/May2017 ).
Any institution which has made local customizations based on these files needs to perform a manual review each month. While this isn't so horrific for the single mashup_new.css file, it is for the Letter-templates. Having a section which lists the differences would be a huge time-saver. Bonus…
28 votes -
Ability to exclude Primo Journal Search from display logic rules
We would like the ability to exclude the Journal Search function from display logic rules.
Why?
In the Primo view the limit of links is set to 25, and it cannot be reduced (which deserves another Idea....). The only way to reduce it is through the user of display logic rules.
However, the rules also apply to the "Journal Search" in Primo, where users actually want to see all the available full text due to differences in coverage.27 votes -
Ability to select Columns exported via Tools->Excel option
When in a view or screen with Tools option (for Excel) saving, it would be very helpful to be able to have more contol over the columns output.
User Roles is a great example. The list does not include the ACTIVE (Y/N) option, yet it is clearly an important piece of information when comparing users or building role templates. A repository search is another example. It has 18 fields pre-selected, however this could prove much more efficient if we could select to add or remove the columns that make the most sense to us prior to saving.25 votes -
Simple letter formatting and testing
Amending and testing letters and notifications is simply too complicated with many steps in various tables, not identical names, test users receiving all types of letters not just the ones they are working on etc. Some form of WYSIWYG editor with test recipient per letter type would be great.
25 votes -
Do not automatically highlight search terms
After completing a search in the persistent search box, the inputted text remains in that field. When clicking back into the persistent search box to edit this text, all of the text is automatically highlighted. This often results in accidentally deleting the entire search phrase when attempting to edit it slightly, or at the very least having to pay extra careful attention to click twice into the search box to un-highlight before editing. Removing auto-highlighting would streamline the process of editing searches and alleviate the frustration of many accidental deletions.
24 votes -
Highlight text in persistent search box when pressing "/"
After completing a search in the persistent search box, the inputted text remains in that field. When pressing "/" to select the persistent search box, the cursor jumps to the beginning of the previously inputted text without highlighting it. Automatically highlighting the text would allow one to overwrite the previous text (e.g., scanning a barcode) without selecting and deleting it.
22 votes -
Browser's back button!
What would it take to make the browser's Back Button functional throughout Alma? It's just killing me to have to reload all the time because I accidentally use it. Plus, there are some screens that you can't back-up from to go where you were without starting all over again. As a newbie, it's surprising to me that this is a problem and that everyone else has learned to work around it.
22 votes -
cover art
When the cover art thumbnail is incorrectly displayed in Primo/Discovery, we have the ability to correct it by searching for the image and inserting an 856 or 956 tag in the bib record. When the cover art is incorrect in Alma, there is no ability to correct the Alma display ourselves. The solution offered by ExLibris is to contact Google books and submit a correction. Unfortunately, when I checked one such title, it was displaying correctly in Google Books so I don't know why it is not displaying correctly in Alma. In this case I would like the ability to…
22 votes -
JavaScript in the Alma Resolver Menu (GetIt/ViewIt)
"Delivery system skins" enable customers to modify the Alma resolver menu using custom CSS and images, but it would be extremely useful if customers could also add custom JavaScript to the resolver menu.
In many cases, desired customizations require DOM manipulation that cannot be achieved with CSS alone. Moreover, many libraries rely on JavaScript-driven web analytics tools (such as Google Analytics) to track user engagement across various web properties.
21 votes -
Tables need an option to clear the default value
There are various code tables in Alma that prompt you to choose "Default Value -- Yes/No" when adding a row to the table. Once multiple rows have been added, it's possible to select one value to be the default value. However, once one value has been chosen as the default at any point in time, there is NO option to clear the default value (short of deleting the default value row which causes other problems). There are times when we don't want a default value but "Yes" was chosen by mistake when adding a new row.
One example of this…
20 votes -
Enhance Report to ExLibris ticket fields within Alma
Enhance the Report To ExLibris form in Alma with the following so that it matches the tickets submitted via SalesForce:
Contact Name field: defaults to whomever is logged in/made the default contact if there is no match. Ex: if Person B is logged into Alma and is configured to report from Alma, they are the default when submitting a problem, not Person A (which is currently listed first because its an alphabetical listing). This would help staff to submit tickets faster and without having to go into SalesForce after submitting to change the name.
Priority: Allow this as a field!…19 votes
- Don't see your idea?