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.
1903 results found
-
Add the "Assign selected" option to In Review Invoices and unassigned Purchase, Lending and Borrowing Requests
Since the introduction of the New unified PO Line Task list, we can bulk assign PO lines using the "Assign selected" option. This is very useful.
We would also like to be able to do this for unassigned invoices and requests in review (Purchase Requests, Lending Requests and Borrowing Requests). Currently, we can only assign invoices and requests one by one and this may sometimes be time consuming.
Specifically for our invoices, many of them are created by EDI, and this "Assign selection" option would be very helpful to quickly assign them to the appropriate invoice operator to finalize their…
43 votes -
Allow lending libraries to send lost resource sharing item invoices directly to the borrowing library in Alma
Currently, Alma does not allow a lending library to send an invoice to a borrowing library within Alma in the event a resource sharing item is lost or damaged. This requires libraries to develop a manual resource sharing billing workflow outside of Alma. An Alma letter that can serve as a lost resource sharing item invoice would be incredibly helpful. We would need to be able to trigger this letter manually for specific requests on demand, but it would also be extremely helpful if this letter could be triggered automatically once an item is more than a certain number of…
43 votes -
Merge Patron Accounts API
Add an API endpoint that provides a programatic interface to the merging patron accounts functionality.
43 votes -
Purge User Records – Add field to prevent purge of users with active requests.
In addition to Number of days, user record, user group, and waive threshold, an institution should have the option:
Do not purge if there is active request(s)43 votes -
Estimated price -field for following year on continuous POL
Estimated price -field is needed for databases and another continuous purchase orders for following year budget planning. There should be price fields for both current year and the following year (also possibility to split them to different funds). Estimated price -field should also to be selected on the analytics reports. Publishers may change database or journals prices a lot more than average rate.
43 votes -
A new Community Zone Updates Task List report for when a portfolio changes vendors
CZ updates task list does not show titles switching from one vendor to another - that is a big issue for us. Eg. Philosophy of science changed from University of Chicago Press to Cambridge University. The portfolio URL is still Chicago Press, but one is redirected to Cambridge University.
Finding info in CZ updates is extraordinarily difficult. Mostly because there are thousands of titles we don't have any reason to look at.
It would be very helpful to be able to search the list by ISSN and OCLC number as well.
It would be helpful to have a report indicating…43 votesHi Liz,
We would like to better understand the situation of "portfolio changes vendors":
- Does this mean that the interface of the portfolio was changed?
- Is it enough to report this on collection/service level, and not in portfolio level?
- What actions would you take upon such report?
Thanks,
Tamar Fuches
Alma product team
-
Creating expected items in status acquisition without using prediction pattern
In the current workflow for periodicals, when using predicted items, there is no easy way to add just one predicted item. This means that if we make a mistake or there is a change in the publication pattern, for example we receive the wrong item/delete the wrong item, or that a periodical is published as a combined issue (ex: issue 2 and 3 together, as number 2/3 2023), there is no easy way to fix it. We must then create predicted items for that whole year again which involves editing “next predicted item information” in the metadata editor, opening and…
43 votes -
Analytics: Transit end time NOT registered
Hello,
Please see our public ticket 00903860.
If you make a query containing the field "Physical item historical events->Event end date->event end date and time" with the conditional "event type description=physical item went into transit" on this field is NOT registered the end of transit process, but the start of the following process (if any). Please correct this behaviour.43 votes -
Enable Alma to add to the letters a "Reply to" in the email message header
reply to can only be added as a text line, it would be much better if it was added in the header
43 votes -
Allow edits to POL Bib Descriptions on Cancelled POLs
We want to be able to edit the POL Bib Description fields on cancelled POLs without having to reopen the POL. Reopening a cancelled order on a closed ledger causes complications, especially if the fund doesn't exist in the current ledger. It would be better for your users if we could just edit this tab without impacting the POL status. Thank you!
43 votes -
Enable Printing of Borrow requests ("Print Slip")
There is no way to print a copy an outstanding Borrow request (that includes request citation information, patron info) from the Borrowing requests queue and this would be a very useful function to have. This could be like the Print Slip option available for requests in the Lending request queue.
43 votes -
Ability to surface details of recipients/subscribers to Scheduled Analytics Reports
Allow for export/inclusion of subscriber details when exporting list of scheduled reports or creating Analytics reports from Analytics Usage Tracking subject area or Analytics Objects subject area.
I am trying to do an audit on recipients/subscribers of our Scheduled Reports in Alma. The aim is to streamline who receives which reports/ remove staff who have moved roles and/or staff who have left the institution.
Currently neither the extract of Analytics Objects from Alma or any of the Analytics Subject Areas include details about the recipients/subscribers and I feel this would be very useful for auditing/access control.
43 votes -
Display “Service unavailability display message” at Collection Level in Primo
Currently, the “Service unavailability display message” is only shown at the Journal and article level in Primo. It would be highly beneficial to extend this functionality to the collection level as well. This enhancement would provide users with clearer information about service availability, improving their overall experience and reducing confusion when accessing collections.
43 votes -
Ability to de-activate collections with EasyActive setting
Once you have chosen EasyActive over FullyFlexible, there is no way to switch back (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Electronic_Resource_Management/070Alma_Single_Activation_Source_for_CDI/020Single_Activation_with_the_EasyActive_Setting). However, at the time of switching there is no way of knowing what future collections will be added, and all CDI records of future collections will be returned in an unfiltered Primo search. For various reasons, we have had to switch to a default unfiltered search in Primo and now results are flooded with CDI records, some not of good quality. If there is no way to switch to FullyFlexible, then please provide an easy method to de-activate collections so that the CDI…
43 votes -
Suppress Items from discovery for a particular physical location but keep Holding statement
We feel that it would be useful to be able to suppress items from discovery from a particular Physical location but still display the holdings information.
This would be extremely useful for our Journals collections, whereby we receive individual items but only want to display the holdings statement to the end user.42 votes -
Option to Return Items Without Filling Patron Requests
Items checked in that have patron requests on them are automatically placed on hold shelf and the patron is immediately emailed. Currently Ex Libris allows a delay for the notice for a maximum of 999 minutes, which is often not long enough. Sometimes materials come back that need repair, updates, or to be quarantined. This can take varying amounts of time. It would be ideal if the system would allow us to have the option to check materials in without triggering the hold process, so we may complete any necessary steps we need to before an email is triggered to…
42 votes -
A separate booking calendar
Now, it is not possible to establish a separate calendar for booking request, the library's opening and closing times are used.
We would like the booking request to have a separate calendar from the Library's general hours.42 votes -
Update Customer Linking Parameters in Bulk via E-Collection Quick Update Cloud App
Please add the ability to update customer linking parameters (such as the Gale location ID) in bulk via the E-Collection Quick Update Cloud App.
As Ex Libris moves away from centrally configuring linking parameters for different interfaces, it would save so much time to be able to do this in bulk via the cloud app.
42 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 -
Death of a patron - Need to immediately and permanently cease sending all letters
In the unfortunate event that we learn that a patron passes away, we need a quick, clear, and finite procedure to immediately and permanently cease/stop any and all IZ and NZ notifications to the patron's email account, especially those that are tied to a SIS load (Example: Banner). College administration directs the library to ensure no emails are sent to the deceased's email account. We need to be able to definitively state to college administrators "Absolutely zero communications, automated or manually generated, will be sent regarding the deceased patron's library account from the IZ or NZ."
Existing work-arounds include toggling…
42 votes
- Don't see your idea?