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.
- or
No existing idea results
- ~ No ideas found ~
1748 results found
-
ADD RECORDS TO SETS
Be able to add selected records to a set that's already created. There is often multiple ways to find records that are part of a group. It seems there's no ability to do a search and select records to add to a set that's already in existence. This could also help if multiple people are trying to find a large number of records that could belong to one set for export or modification.
1 vote -
Increased efficiency thanks to new “Send externally” field in CZ update
The additional “Send externally” field in the CZ update increases efficiency and communication within the library and with external partners and is structured in the same way as the “Report to Ex Libris” field. This allows messages to be sent directly from ALMA, eliminating the need to copy information. This reduces errors, saves time, and minimizes manual effort. Faster processing of requests and better coordination between departments and partners increase service quality and satisfaction and make the library forward-thinking.
This option includes the following fields:
- Sender (automatically filled in by ExLibris based on the login)
- Field for entering the email address(es) to which the message should be sent
- Drop-down menu with various options, such as: No access – request title, etc.
- Free text field “Description”
- Additional information: automatically filled in as for “Send to Ex Libris”
The additional “Send externally” field in the CZ update increases efficiency and communication within the library and with external partners and is structured in the same way as the “Report to Ex Libris” field. This allows messages to be sent directly from ALMA, eliminating the need to copy information. This reduces errors, saves time, and minimizes manual effort. Faster processing of requests and better coordination between departments and partners increase service quality and satisfaction and make the library forward-thinking.
This option includes the following fields:
- Sender (automatically filled in by ExLibris based on the login)
- Field for entering the email…
15 votes -
Add clarifying language to the Delete Holdings records with no Physical Items job
Adjust the wording on the “Delete Holdings records with no Physical items” job to match wording from the “Withdrawn Physical items” job. Change “Delete bibliographic records” to “Delete bibliographic records that have no other holdings” AND "Suppress bibliographic records” to “Suppress bibliographic records that have no other holdings from publishing”. This would add needed clarity to what is happening when running the "Delete Holdings records with no Physical items" job.
4 votes -
Monitor request page
Currently on the Monitor requests page for the Activity status filter there are the following options:
Completed; Active, All. It would be useful to have the option that filters requests with status Rejected80 votes -
API access to suspend realtionships among libraries
Currently, there is no API access to manage the suspension of relationships between libraries in Alma, which requires manual intervention to suspend them at the appropriate time when there is an interruption in the logistics shuttle between libraries. This process can be time-consuming and requires staff to handle it during off-hours, such as early mornings or late nights.
We propose implementing an API endpoint that would allow libraries to schedule the suspension of relationships at a given date and time. This feature would help streamline operations, reduce manual intervention, and ensure that interruptions in logistics are handled efficiently and at the correct times without requiring staff to be on duty outside of regular working hours.Currently, there is no API access to manage the suspension of relationships between libraries in Alma, which requires manual intervention to suspend them at the appropriate time when there is an interruption in the logistics shuttle between libraries. This process can be time-consuming and requires staff to handle it during off-hours, such as early mornings or late nights.
We propose implementing an API endpoint that would allow libraries to schedule the suspension of relationships at a given date and time. This feature would help streamline operations, reduce manual intervention, and ensure that interruptions in logistics are handled efficiently and at…4 votes -
Alma Show Access Type value (e.g. Perpetual ) in Alma brief view search for Electronic Collections
Please show Access Type in Alma brief view search for Electronic Collections.
Access Type is quite important, since it may be not only Current but also Perpetual or Current and Perpetual. From the brief view many operation, included deletion, can be performed. Having this information at first glance, if possible together with a warning on deletion attempt as suggested here ( https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/42179845-prevent-deletion-of-portfolios-with-access-type-pe ) may help preventing accidental deletion of important perpetual assets.40 votes -
Manage Purchase Requests [Acquisitions > Purchase Requests > Manage Purchase Requests] menu
All user purchase requests are directed to the 'Unassigned' tab in the "Manage Purchase Requests" menu. It seems that this could be somewhat inconvenient for the staff handling acquisitions. Therefore, we would like to propose two suggestions. ① Enable the selection of multiple items within the 'Unassigned' tab for bulk assignment, either to oneself ('Assigned to Me') or to another staff ('Assigned to Others'). ② We would like purchase requests to be automatically assigned to the appropriate staff member based on the MARC format or vendor selected during the request.6 votes -
bluk edit vendor information
There is some information in vendor records which could be the same for all vendors, such as library, vendor type, whether to make vendors active or inactive, delivery claim information, etc. It would be great if there were a way to edit these details for multiple vendors at one time rather than going through each vendor to change their information.
1 vote -
License Section Names - Customizing Capabilities and Upgraded Reordering
I'm bringing back an idea that was posted years ago because I really think it's important.
Many of us would REALLY like to have the ability to create our own Section Names. If it's possible for us to create our own license terms, then I don't see any reason why we shouldn't have the ability to personalize Section Names.
As the original idea stated, the existing section names don't always match well with our agreements and there are some clauses that don't fit under the current sections. The lack of ability to create our own license sections can really make coding licenses feel less useful when we can't organize the content in a way that makes sense for our institution.Also, can we please consider a new method for reordering license sections? The numbering system is absolutely tedious and inefficient..
I'm bringing back an idea that was posted years ago because I really think it's important.
Many of us would REALLY like to have the ability to create our own Section Names. If it's possible for us to create our own license terms, then I don't see any reason why we shouldn't have the ability to personalize Section Names.
As the original idea stated, the existing section names don't always match well with our agreements and there are some clauses that don't fit under the current sections. The lack of ability to create our own license sections can really make…5 votes -
Need more facets electonic collection search
When searching for items in the CZ, I find the left side facets and sort by options to be too limited.
Would love a way to sort electronic collections by most recently added to CZ.
for example, I am looking to see if any new gale collections were added so I can activate them. There is no way to sort by this, and there is no facet on the left to limit to non-activated collections. Adding a left facet to search for In IZ or activated/non-activated collections would be very helpful.1 vote -
Folders in "Manage sets"
We would like the option to make folders in "manage sets". This would make it easier for different depatmants to navigate through the public sets of the institution.
46 votes -
Run 3 Game
With all those great things, I highly recommend you to play Run 3 to make sure you have real fun.
1 vote -
Block when overdue: add a "days per overdue days" unit of measurement option
Hello everyone,
when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first one, "days...", generates larger block periods, but they are over in a shorter time; on the other hand, when using the second one, "open days...", the block periods are smaller but they take more time to be fulfilled.
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/Configuring_User_Blocks#Configuring_User_Blocks_Due_to_Overdue_Loans
So, I guess that the "perfect" option for us would be something in between, an "Days per open overdue days" which does not currently exist in Alma.
Would it be possible to add this "Days per open overdue days" option and, as its opposite, an "Open days per overdue days"?
Thanks a lot in advance and best regards.Hello everyone,
when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first…57 votes -
"Make Embase available in CDI"
Access URL: https://www.embase.com
Could you please try to contact Elsevier again regarding this.
3 votes -
Missing Padding Option for Accession Number Sequences in Call Number Generation
Currently, Alma does not support padding (adding leading zeros to reach a fixed number of digits) for accession number sequences used in the automatic generation of call numbers (e.g., via the "Generate" / "Calculate" button in the item editor). If the next sequence value is set to "0003," the leading zeros are removed upon saving. Even if the next sequence remains "0003" in the sequence configuration, the zeros are still automatically stripped when generating the next call number in the item editor.
Institutions that use custom call number schemes requiring padding can therefore only use Alma’s "Generate" or "Calculate" button as a basis for their call numbers, requiring manual addition of the missing zeros each time.
This process is prone to errors and unnecessarily time-consuming, especially since the padding function is already implemented for other item sequences (inventory, receiving, and weeding numbers).
We would therefore like to request the same padding functionality for accession number sequences.
Currently, Alma does not support padding (adding leading zeros to reach a fixed number of digits) for accession number sequences used in the automatic generation of call numbers (e.g., via the "Generate" / "Calculate" button in the item editor). If the next sequence value is set to "0003," the leading zeros are removed upon saving. Even if the next sequence remains "0003" in the sequence configuration, the zeros are still automatically stripped when generating the next call number in the item editor.
Institutions that use custom call number schemes requiring padding can therefore only use Alma’s "Generate" or "Calculate" button…
9 votes -
Add Electronic Collection Type (override) to Analytics
We use the Electronic Collection Type field to keep track of whether we have all portfolios activated (Aggregator Package), only some activated (Selective Package) or none activated (Database). Using an Analytics report we can check these values against our Auto Active Settings and CDI settings to make sure all our settings are in alignment.
However, there is no Electronic Collection Type (override) field in Analytics so the reports cannot be accurate. We use an override when we have selected a Type that is different from the Type in the CZ collection. It seems like an oversight that this field isn't indexed in Analytics.We use the Electronic Collection Type field to keep track of whether we have all portfolios activated (Aggregator Package), only some activated (Selective Package) or none activated (Database). Using an Analytics report we can check these values against our Auto Active Settings and CDI settings to make sure all our settings are in alignment.
However, there is no Electronic Collection Type (override) field in Analytics so the reports cannot be accurate. We use an override when we have selected a Type that is different from the Type in the CZ collection. It seems like an oversight that this field isn't…2 votes -
More options for scheduling integration profile jobs
For our local purchasing processing, we really need to be able to schedule invoices to be exported to the FTP server every Monday evening at 5:00 pm. This is not currently an option. This is specifically the Export Invoices For Payment job in the Integration Profiles.
3 votes -
Add the edition statement to the citation display in alma
Could you add the edition field to the display of citations within Alma? It would make it easier to check that the newest edition is the one listing. Law books, for instance, might have a new edition each year and there is sometimes a cataloguing mismatch between the copyright and the publication dates with print/eBooks which is easier to disentangle if you can see the edition. The edition displays in the Title search results in Alma and in the citations on Leganto.
42 votes -
The Provenance field in the physical item editor
We would like the Provenance field in the physical item editor to be mandatory.
It is possible to have a default for the list but that is not the same thing. We are afraid people will be not so attentive, and the default option will be the one they always choose. We want it to be mandatory and default to nothing. The user then has to choose something in order to save the item.4 votes -
Allow granularity in API limits
The Universities of Wisconsin make extensive use of APIs, both Alma and Primo, in our consortium.
We use APIs for our locally developed discovery environment, for reporting purposes, and for staff/business processes where Alma functionality does not meet our needs.
However, all these uses of APIs are forced to contend with one set of limits. So if we hit our limit for whatever reason - a bot crawling our catalog, a call-intensive app used by our staff, etc., ALL of our API using applications suffer and/or fail.
UW is a responsible user of APIs and has an experienced development group that engages in prudent practices to minimize API calls. But the developer network/API limits provide us no way to prioritize the API calls needed by staff over those needed by our discovery environment. If we hit the limits, whatever applications are using API calls at that time suffer.
We would like Ex Libris to provide some "buckets" for API keys to allow us to segregate the keys used by our staff/business processes from those used by our patrons. Furthermore, we'd like to be able to prioritize buckets so that we could guarantee that the API keys used by our business processes "come first" over those used elsewhere.
In doing so, we'd be able to ensure our business processes, which are often time sensitive and scheduled to run at particular times of the day, continue to run even if our catalog is being crawled by bots is otherwise experiencing heavy use.
The Universities of Wisconsin make extensive use of APIs, both Alma and Primo, in our consortium.
We use APIs for our locally developed discovery environment, for reporting purposes, and for staff/business processes where Alma functionality does not meet our needs.
However, all these uses of APIs are forced to contend with one set of limits. So if we hit our limit for whatever reason - a bot crawling our catalog, a call-intensive app used by our staff, etc., ALL of our API using applications suffer and/or fail.
UW is a responsible user of APIs and has an experienced development group…
13 votes
- Don't see your idea?