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
4 results found
-
Add "Print Slip Report" action to the "Resource Request Monitoring" screen
The Print Slip Report function is currently available from the "Pick Up Requested Resources" and "Resource Sharing Lending Requests Task List" screens. But when a hold is placed on an item that is checked out, the returning item is automatically placed on hold and the request bypasses the "Pick Up Requested Resources" screen and shows up on the "Resource Request Monitoring" screen as "On Hold Shelf". But the Print Slip Report is not available here. It does need to be available here, as well.
"Print Slip Report" is a different action than "Print Slip." The Print Slip Report is a function that was developed for the Orbis Cascade Alliance based on our need to be able print enhanced hold slips from Alliance-hosted server. The Print Slip Report sends an XML-formatted email with metadata for requests to our server, where the XML is parsed and used to generate PDFs for printing via a web browser interface. This function is crucial to the workflow of our 38 institutions for both local and resource sharing requests. Exporting to Excel won't work, since the Print Slip Report is used to email an XML format to our server. As I indicated above, use of the Print Slip Report is a key step in our workflows at all institutions. Not being able to use the Print Slip Report for requests that bypass the "Pick Up Requested Resources" screen disrupts that workflow.
The Print Slip Report function is currently available from the "Pick Up Requested Resources" and "Resource Sharing Lending Requests Task List" screens. But when a hold is placed on an item that is checked out, the returning item is automatically placed on hold and the request bypasses the "Pick Up Requested Resources" screen and shows up on the "Resource Request Monitoring" screen as "On Hold Shelf". But the Print Slip Report is not available here. It does need to be available here, as well.
"Print Slip Report" is a different action than "Print Slip." The Print Slip Report is a…
121 votesHi,
The request monitor page is not intended to be the routine working space, but rather be an interface that allows searching and fining specific requests to query about their status, and run some specific actions (such as cancel). The routine work on the requests list is intended to be done via the task lists.
Thanks,
Moshe -
Electronic portfolios in an electronic collection/packages should inherit data displays from the collection's service
Data elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down to the individual portfolio display in Alma either. Currently, the only service level information that appears in a portfolio is the Service Parse Params. Request: Data elements that are set at an electronic collection's service level (specifically, proxy settings and public/authentication notes) should cascade down to the portfolio level display. Staff shouldn't have to check two places to see the correct settingData elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down…43 votesAs part of Alma June release Advanced search query options were expanded to include Not Contains Keywords, Is Empty and Is Not Empty for electronic resources indexes.
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
Add Lender/Borrower addresses to Label code table in select Fulfillment and Resource Sharing letters
Fulfillment letters and Resource Sharing related letters would benefit from having an easy mailing label field, to be toggled on and off in the “Labels” section for letter editing when a Library would like to add a mailing label to a letter.
With collaboration from our Alliance colleagues, we created a shipping label directly on our Ful Resource Sharing Request letter. When we print our pull slips, a second page is automatically generated with a printed mailing label with the Borrowing Schools address information, along with information to allow our mail room to expense it to the correct fund. By adding this to the pull slip, we skip needing to print a separate shipping label later, increasing our efficiency and saving paper.
We think this is a valuable enhancement to the use of this letter, and think it should be added as a “label” or set of labels to toggle on and off for other folks to use and not have to write the extensive coding we did. We like not having to waste paper and cut out extra steps when doing Resource Sharing.
We also think this could be added to other letters, such as the Borrowing Receive letter, to be kept with the item until we need to mail it back.
Fulfillment letters and Resource Sharing related letters would benefit from having an easy mailing label field, to be toggled on and off in the “Labels” section for letter editing when a Library would like to add a mailing label to a letter.
With collaboration from our Alliance colleagues, we created a shipping label directly on our Ful Resource Sharing Request letter. When we print our pull slips, a second page is automatically generated with a printed mailing label with the Borrowing Schools address information, along with information to allow our mail room to expense it to the correct fund. By…
8 votes -
Disable the license terms from cascading down from POL to electronic collections and portfolios
The current situation is that after attaching a license to a PO Line, this license will override the license(s) originally attached to the electronic collections and the portfolios. We have 5000+ Chinese ebooks that come with a wide range of number of concurrent users. While we can update them using the 'Run a Job' function, but once the POL that is connected with the electronic collection is updated, it will override the license terms we have for the individual ebooks. So we would like to see if there is an option to delink the POLs and electronic collections from the portfolios ONLY in terms of the license terms. Thank you!
The current situation is that after attaching a license to a PO Line, this license will override the license(s) originally attached to the electronic collections and the portfolios. We have 5000+ Chinese ebooks that come with a wide range of number of concurrent users. While we can update them using the 'Run a Job' function, but once the POL that is connected with the electronic collection is updated, it will override the license terms we have for the individual ebooks. So we would like to see if there is an option to delink the POLs and electronic collections from the…
3 votes
1870 results found
-
Automatic Upload of Electronic Holdings (Autoholdings integration) - Walter De Gruyter Publishing
Implement Automatic Upload of Electronic Holdings (Autoholdings integration) for Walter De Gruyter Publishing
1 vote -
Library closure added to calendar in borrowing library should affect existing Rapido loans in lending library
A library closure added to the calendar of the borrowing library will affect the due date of a Rapido loan for the borrower and the borrowing library but will not affect the due date in the lending library. On the original (lending library's) due date, the system will revert the extended due date to the original due date, mark the item overdue, but users are not notified and the due date remains unchanged in their accounts. Users could be billed for an item they didn't know was overdue.
This should have been fixed by the May 2025 release, following CERV Enhancement ID #1181. (https://knowledge.exlibrisgroup.com/Rapido/Release_Notes/2025/Rapido_2025_Release_Notes?mon=202505BASE).
We would propose that any system-induced due date update in the borrowing library should always be reflected in the lending library.
Ex Libris ticket: 10574691
A library closure added to the calendar of the borrowing library will affect the due date of a Rapido loan for the borrower and the borrowing library but will not affect the due date in the lending library. On the original (lending library's) due date, the system will revert the extended due date to the original due date, mark the item overdue, but users are not notified and the due date remains unchanged in their accounts. Users could be billed for an item they didn't know was overdue.
This should have been fixed by the May 2025 release, following CERV…
12 votes -
Add facets to left side when working with electronic collections and portfolios
The current facets for electronic collections are limited to material type. I would like to see a facet to filter by activated/non-activated collections and portfolios. Two use cases:
1. Activated collection, missing a few portfolios in our IZ because did not have auto add turned on. If I go to the CZ version, there is no way to easily see the unactivated portfolios in that collection so I can activate them. had to page through 17 pages to find the few titles that were not activated.
2. Seeing unactivated collections in CZ. What if we want to see which gale collections we haven't bought yet? No way to easily see which unactivated collections are available by vendor.The current facets for electronic collections are limited to material type. I would like to see a facet to filter by activated/non-activated collections and portfolios. Two use cases:
1. Activated collection, missing a few portfolios in our IZ because did not have auto add turned on. If I go to the CZ version, there is no way to easily see the unactivated portfolios in that collection so I can activate them. had to page through 17 pages to find the few titles that were not activated.
2. Seeing unactivated collections in CZ. What if we want to see which gale…1 vote -
Allow Digital Lending Requests to Transition to “Shipped Digitally” When Lender Ship Email Letter Is Suppressed
Description
We have encountered an issue with Resource Sharing lending requests when supplying articles or book chapters digitally.
When a digital lending request is supplied using either:
Ship Item Digitally, or
Deliver Digital Documents for scanned items,the Ful Digitization Notification Item Letter is sent successfully. However, Alma then displays a “Could not send report” message, and the lending request does not transition to Shipped Digitally.
Instead, the request remains in its previous status, such as:
Being Processed
Locate Failed
Created Lending RequestBecause the request does not move to Shipped Digitally, staff must manually update the request status in order to remove it from the active lending queue.
The “Could not send report” message itself is not new in our environment. We understand that it is related to our configuration in which the Lender Ship Email Letter is suppressed for digitally supplied requests, so that borrowers receive the digitization notification rather than both the digitization letter and the lender shipping letter.
Previously, despite the “Could not send report” message, the request still transitioned successfully to Shipped Digitally. This behavior changed recently.
We also tested selecting Complete the request on the Ship Digitally screen when uploading the file, but this did not resolve the issue.
Expected Behavior
When a Resource Sharing lending request is successfully supplied digitally:
The digital document is delivered successfully.
The Ful Digitization Notification Item Letter is sent.
The request transitions automatically to Shipped Digitally, even if the Lender Ship Email Letter has been intentionally suppressed.The request status transition should not depend on whether the Lender Ship Email Letter is enabled.
Current Behavior
The digital delivery succeeds and the Ful Digitization Notification Item Letter is sent, but because the Lender Ship Email Letter is suppressed:
Alma displays “Could not send report.”
The request does not transition to Shipped Digitally.
Staff must manually change the request status.
ImpactThis creates unnecessary manual processing for every digitally supplied Resource Sharing lending request and leaves successfully completed requests in active lending queues.
Physical lending requests are not affected. When physical items are shipped, the Lender Ship Email Letter is sent and the request status updates correctly.
Suggested Enhancement
Please separate the Resource Sharing request status transition from the successful generation of the Lender Ship Email Letter.
If the digital document has been supplied successfully, Alma should transition the lending request to Shipped Digitally regardless of whether the Lender Ship Email Letter is enabled or intentionally suppressed.
This would also allow institutions to avoid sending redundant notifications for digital lending transactions without disrupting the Resource Sharing workflow.
Description
We have encountered an issue with Resource Sharing lending requests when supplying articles or book chapters digitally.
When a digital lending request is supplied using either:
Ship Item Digitally, or
Deliver Digital Documents for scanned items,the Ful Digitization Notification Item Letter is sent successfully. However, Alma then displays a “Could not send report” message, and the lending request does not transition to Shipped Digitally.
Instead, the request remains in its previous status, such as:
Being Processed
Locate Failed
Created Lending RequestBecause the request does not move to Shipped Digitally, staff must manually update the request status in…
3 votes -
Subfield u must be preserved when linking to the Shared Authority File in fields 100 and 700
When cataloguing conference papers and articles, it is important to be able to specify the authors’ affiliation at the time of publication. According to the MARC structure, subfield u in fields 100 and 700 is intended for this purpose. However, when links are created in the MDE (F3) to the Joint Authority File for the German-speaking region (GND) in these fields, subfield u is removed. We would therefore like subfield u to be preserved when linking to the authority file in the same way as for subfield 1, in which the ORCID ID is indicated. This would improve visibility and enhance compatibility in the exchange of metadata.
When cataloguing conference papers and articles, it is important to be able to specify the authors’ affiliation at the time of publication. According to the MARC structure, subfield u in fields 100 and 700 is intended for this purpose. However, when links are created in the MDE (F3) to the Joint Authority File for the German-speaking region (GND) in these fields, subfield u is removed. We would therefore like subfield u to be preserved when linking to the authority file in the same way as for subfield 1, in which the ORCID ID is indicated. This would improve visibility and…
18 votes -
Provide a direct link to a suppressed collection that will display for a specific audience while keeping it hidden from the main Collections
It would be nice to be able to create a 'private' collection... where you can provide a direct link to a suppressed collection that will display for a specific audience while keeping it hidden from the main Collections page through Primo.
3 votes -
Display the PO line and invoice number in separate columns in Excel export
In the excel export of the funds' transactions list, we would like the PO line and invoice numbers currently displayed in the Related Record column to be displayed in two separate columns "Related PO line" and "Related Invoice Line".
This would make it easier to use the excel export for further analysis.In this same excel export and for the same reason, we would also like to find the transaction amount and its currency in two separate columns. An Idea Exchange proposal for this request already exists: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/38575105-separate-amount-and-its-currency-into-two-columns.
2 votes -
Analytics report for POLs cancelled or closed in specified Fiscal Periods
Provide an Analytics report that identifies Purchase Order Lines (POLs) cancelled or closed within user-selected Fiscal Periods. Libraries need to analyse cancellations and closures by fiscal year or accounting period for budgeting, supplier review, collection management, and audit purposes. Current reporting options do not easily support filtering by the fiscal period in which a POL was cancelled or closed. This enhancement would improve financial reporting accuracy, support year-end analysis, and reduce the need for complex workarounds or external data processing.
6 votes -
Allow custom Dewey Classification searches in Consortial Analytics
In Consortial Analytics, the Dewey Classification search only allows users to select predefined three-digit classifications (as shown in the attached screenshot). This limits the search to broad subject categories. For the purpose of collection development analysis, it would be useful to have the option to search using custom Dewey Decimal numbers, as this would enable more targeted searches.
12 votes -
Display License TOU link with CDI Link-in-Record type records
We display license terms of use for our electronic collections as we try to be compliant with the subscriptions. We noticed that with CDI link-in-record type records, there is no link for the license TOUs. It would be nice if there was a way to link to the TOUs or add a note to be able to link to TOUs.
12 votes -
Incorporate All AI Metric Types/Access Method from recent 5.1.1 COUNTER Standard Update into Analytics
Counter Standards were recently updated to incorporate new metric types and new access methods for AI Bot Traffic within COUNTER standards (https://www.countermetrics.org/code-of-practice/best-practice/bp-ai/). Requesting that Ex Libris incorporate all metric types and the new access methods into analytics.
69 votes -
Add "Available for Group" record fields to Analytics
Currently, Analytics exposes which groups have Available for Group records, but it doesn't expose the other fields in those records.
For example, Analytics can show that a collection is available for Group A and Group F, and it can show that Electronic Collection Proxy Enabled is set to Yes at the collection level; however, it can't show whether proxy is enabled for Group A or Group F.
For Network Zones, and institutions that make extensive use of Available for Groups, the lack of access to these fields in Analytics means we can't periodically audit and correct configuration inconsistencies and data entry errors. It also hinders the progress of large-scale system change projects that require reviewing and selectively updating group-level collection, service, and CDI settings.
Currently, Analytics exposes which groups have Available for Group records, but it doesn't expose the other fields in those records.
For example, Analytics can show that a collection is available for Group A and Group F, and it can show that Electronic Collection Proxy Enabled is set to Yes at the collection level; however, it can't show whether proxy is enabled for Group A or Group F.
For Network Zones, and institutions that make extensive use of Available for Groups, the lack of access to these fields in Analytics means we can't periodically audit and correct configuration inconsistencies and data…
3 votes -
Add Analytics support to compare "Available for Group" settings on electronic collections and services
Currently, Analytics can show Available for Groups on the electronic service or, if none exist there (if they're inherited from the electronic collection), then on the electronic collection.
However, we can't report on discrepancies between collection-level and service-level groups.
5 votes -
Partner Details for Filled Borrowing Requests should reflect the partner that filled the request
Currently, when creating an analytics report for filled borrowing requests and using the Partner Name, Partner Code, Partner ID, and/or Partner institution fields, the report displays all of the partners that were in the rota for the request and the same value in the Num of Request Filled column for all partners. This is confusing for filled requests as it incorrectly implies that a request was filled by each partner in the rota. When a Partner Active Status and Num of Active Partner Requests filters are added to the report, it is clear that only one partner remained active and filled the request. We would like to have the Num of Request Filled field clearly indicate the number of requests filled (as displayed in the Num of Active Partner Requests field) and the partner that filled the request when the partner details are added to a report.
Please see the attached screenshots of the analytics report results.
Currently, when creating an analytics report for filled borrowing requests and using the Partner Name, Partner Code, Partner ID, and/or Partner institution fields, the report displays all of the partners that were in the rota for the request and the same value in the Num of Request Filled column for all partners. This is confusing for filled requests as it incorrectly implies that a request was filled by each partner in the rota. When a Partner Active Status and Num of Active Partner Requests filters are added to the report, it is clear that only one partner remained active and…
6 votes -
Reactivate deferred order POLs in bulk
For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.
We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a REST API process to update the POLs and ensure the records are consistent and ready for processing.
At this point, however, reactivation can only be performed manually through the Alma UI, requiring staff to reactivate each POL individually. Having to move from a largely automated, bulk workflow to a one-by-one manual process is time-consuming and inefficient.
Could Ex Libris provide a supported way to reactivate deferred POLs in bulk, either through an existing job, a new workflow option, or a public API? This would allow institutions to return deferred POLs to In Review and continue them through the standard acquisitions workflow without requiring manual intervention for each individual record.
For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.
We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a…
12 votes -
Alma Mobile: scan in sort order and remove automatic active curser
Two suggestions that would greatly improve the workflow in the Alma Mobile app.
First, please stop placing an active cursor in the barcode field when switching to Scan In from the Pick from Shelf area.
When the cursor is active in the input field, it automatically opens the keyboard on the phone. As a result, I have to close the keyboard every time before I can access the button used to scan a barcode with the camera.
Secondly, please make it possible to sort scanned-in items in either ascending or descending order.
Currently, after each scan, I have to scroll all the way to the bottom of the list to see the action required for the item I just scanned. This is an unnecessary inconvenience. Ideally, the most recently scanned item should appear at the top of the list.
Two suggestions that would greatly improve the workflow in the Alma Mobile app.
First, please stop placing an active cursor in the barcode field when switching to Scan In from the Pick from Shelf area.
When the cursor is active in the input field, it automatically opens the keyboard on the phone. As a result, I have to close the keyboard every time before I can access the button used to scan a barcode with the camera.
Secondly, please make it possible to sort scanned-in items in either ascending or descending order.
Currently, after each scan, I have to scroll…
1 vote -
Wildcard search for MMS ID.
When working in conjunction with Excel, pasting MMS ID will be limited by the floating point standard and truncate the the last 3 digits to '000'. Only just realised this, having wildcard search would allow me to at least more efficiently identify and retrieve the now corrupted MMS ID I've been pasting into Excel.
1 vote -
Add Resource sharing requesting to block_request_if_not_loanable
Currently blockrequestifnotloanable only includes holds and bookings for items we own. And digitization requests, if you are using that functionality and not doing the fill locally workflow. We use the fill locally workflow.
A block on resource sharing requesting if people meet criteria of blockrequestifnotloanable block parameters, is essential. We are particularly trying to catch those with fees in excess of a certain amount who won't be able to check out the item they are requesting. With out it we will continue to see two types of behavior. users who cannot check out our items due to a block then getting around it by requesting a scan. Or placing a physical item borrowing request that they cannot check out once it arrives if the fee is not resolved. Thus, we will have incurred effort and in some cases expense for nothing.
If some libraries don't want to block RS under these conditions, it should at least be option to add RS requests to configuration, or you can make it a separate configuration.
We currently as a work around, before the functionality was even available at all, have a manual block created that we get put on automatically via an hourly job. And that gets taken off hourly. Based on criteria. While this is better than nothing -- it has its limitations. It is not immediate in being added or removed. As it is based off a set of users with fees over a certain amount and that repository search only includes actual active fees not transferred fees it doesn't catch a lot of students.
The new blockrequestifnotloanable does include active and transferred fees because we have it set to a parameter to include transferred fees in the active fee bk=lock for fulfillment services. That is why if we could include RS requesting in this block it would cover all our scenarios.Currently blockrequestifnotloanable only includes holds and bookings for items we own. And digitization requests, if you are using that functionality and not doing the fill locally workflow. We use the fill locally workflow.
A block on resource sharing requesting if people meet criteria of blockrequestifnotloanable block parameters, is essential. We are particularly trying to catch those with fees in excess of a certain amount who won't be able to check out the item they are requesting. With out it we will continue to see two types of behavior. users who cannot check…3 votes -
Repository search for Users using Fine/Fee total sum field filter should include transfer fees
Currently when search for users in the repository and filtering using Fine/Fee total sum field it only looks at users with fees with a status of active. The issue with this is that we have other configurations that include transferred fees in active fee field block and that leave transferred fees on users' accounts.
By not including transferred fees when doing this repository search it makes it difficult to find users with transferred fees in real time. Analytics is nice but it is a day behind. It also means that the logical set I created to find users with active and transferred fees to add a manual block of requesting via a scheduled job does not catch all users.
This need is exacerbated by the fact that the new blockrequestifnotloanable feature which does look at users with fee block which does include transferred fees in total does not include Resource sharing requesting only holds and bookings. So, this manual block is my only option.
My only other option is for users with just transferred fees it to add the block manually based on analtyics report or data from bursars job. And then disable my job to remove automatically when fees drop below a threshold otherwise after I added manually it would be removed.Currently when search for users in the repository and filtering using Fine/Fee total sum field it only looks at users with fees with a status of active. The issue with this is that we have other configurations that include transferred fees in active fee field block and that leave transferred fees on users' accounts.
By not including transferred fees when doing this repository search it makes it difficult to find users with transferred fees in real time. Analytics is nice but it is a day behind. It also means that the logical set I created to find users with active…2 votes -
Please add notification about blocks in Primo when requests are not allowed for the item or patron
This idea relates to Fulfillment configuration setting ‘Prevent Requests for Blocked Loans’ in the Alma May 2026 Release Notes (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/080General/Configuring_Fulfillment_Jobs#block_request_if_not_loanable):
In our Sandbox we changed the parameter key ‘blockrequestifnotloanable’ from NONE to PHYSICAL, which indeed activates a block when a pratron is not eligible to request an item. But now we see that in Primo the Patron is not informed about the reason for the block, so he/she gets lost.
Please add a setting that shows the user a specific notification about blocks in Primo when requests are not allowed for the item or patron by the selected policies.This idea relates to Fulfillment configuration setting ‘Prevent Requests for Blocked Loans’ in the Alma May 2026 Release Notes (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/080General/Configuring_Fulfillment_Jobs#block_request_if_not_loanable):
In our Sandbox we changed the parameter key ‘blockrequestifnotloanable’ from NONE to PHYSICAL, which indeed activates a block when a pratron is not eligible to request an item. But now we see that in Primo the Patron is not informed about the reason for the block, so he/she gets lost.
Please add a setting that shows the user a specific notification about blocks in Primo when requests are not allowed for the item or patron…6 votes
- Don't see your idea?