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.
1690 results found
-
Set continuing orders not to claim
There are some continuing orders for which we do not "receive" every item, such as newspapers that will be discarded after several weeks. It would be great if PO lines had an option to indicate that they should not be claimed. They end up cluttering up the Claims list and making the list harder to work with, when we are never going to claim or receive those issues. We also can't set up automatic claiming because we don't want emails sent for these titles.
43 votes -
Link POLs to EDI invoice lines using Identifier field
When loading EDI invoices from a vendor that do not include POL information, use the Alma Identifier field (usually the ISBN) to match the EDI invoice line to the POL.
2 votes -
Allow a block to be created as part of the 'change to lost' overdue and lost loan profiles.
We'd like the ability to create a block when an item is made 'lost' as part of the overdue and lost loan profile schedules.
At the moment we can only add a block on the overdue notification types, which we do for the last overdue notification we send before it becomes considered lost.
However, as soon as the item is changed to lost by the profile schedule it removes the block automatically created by the overdue notification profile.
The advantage of using the profile block is that they are automatically removed if the item is renewed or returned and we…
116 votes -
Loan due date should appear in Facets and/or Analytics
It should be possible to the the actual Loan Due Date given to the patron, in addition to the Due Date given by the Lender in Facets.
It should also be possible to retrieve a list of such RS requests by Loan Due Date via Analytics.1 vote -
Data visualization to include export to Excel/CSV function
Currently users without Design analytic role can use Data visualization(DV) reports but they can only export report in PDF, powerpoint. It would be very useful to have an export of data in Excel or CSV.
3 votes -
MMS ID and Keyword searching of existing RS requests
It should be possible to search existing RS requests (Borrowing and Lending) by MMS ID and Keywords using the dropdown menu.
1 vote -
Invoice templates
Allow a template so if I'm invoicing dozens of orders in a row for one vendor I don't need to go through a bunch of drop down menus every time- Just one vendor, default account, same invoice date, pre-paid, with a credit card, etc.
7 votes -
Creating an invoice without PO number as invoice number
Now when I create a new invoice from PO, then at the tab Summary there is automatically filled a PO number as an invoice number. We would appriciate some setting which would cause that this field wouldn't be filled out automatically and would stay empty. Our librarians are using other invoice numbers and current setting of Alma is leading to errors because sometime the librarian forgets to change the invoice number. We would appriciate if Alma wouldn't filled out the invoice number automatically with PO number. We would like only a warning by saving the invoice that the invoice number…
6 votes -
Add Financial System Code to the Vendor Dimension of Alma Analytics in the Funds Expenditure SA
The Financial System Code field is often the matchpoint between Alma and external payments systems. Being able to search or query on this would help avoid creating duplicate vendors, especially as vendor names can change so much over time, that a vendor name search will not return results. Having this reportable in Alma Analytics would be more beneficial than in the Alma Advanced Search, as it could also help to de-duplicate existing instances of having more than one vendor record for the same vendor.
25 votes -
Improve discoverability of rejected requests in the Monitor Requests page
We often have to locate cancelled patron physical and digitisation requests in the Monitor Requests page. However, these requests are difficult to locate as they can only be retrieved by Title (a non-unique field) and cannot be filtered or sorted.
Please add:
-A filter for request status which includes 'rejected'
-The ability to sort requests by date created or date updated so that recent rejected requests can be seen at the top of the page
-retain the requester id. The main search term we use to locate a rejected request is the requester name or id. However this is removed…12 votes -
Add Patron Limit threshold block for number of lost items
It should be possible to automatically block users based on a set threshold for the number of items they have checked out that are in a lost status.
Currently, the Patron Limits table only contains delinquency threshold blocks for Max Overdues, Max Cash, and Max Overdue Recalls.
Not all institutions automatically charge a lost item replacement fine for lost materials. For some lost items, the replacement cost may be below the Max Cash block threshold for the user’s user group, but the library would still like the user to be accountable for/aware of their lost status materials; being unable to…
59 votes -
Support full SIP2 protocol
For the communication between selfcheck kiosks and Alma, the SIP2 protocol is needed.
The full protocol can be found here: https://developers.exlibrisgroup.com/wp-content/uploads/2020/01/3M-Standard-Interchange-Protocol-Version-2.00.pdfUnfortunately, Ex Libris does not support all fields that would be available in the protocol (marked as 'not supported' in this document): https://developers.exlibrisgroup.com/alma/integrations/selfcheck/sip2/
Please make the whole SIP2 protocol available for Alma.
134 votes -
Allow Alma to export preferred names to ILLiad when automatically creating ILLiad user records
When Alma automatically created an ILLiad user record for someone who has submitted a resource sharing request that must be exported to ILLiad, it always passes the First Name and Last Name fields to ILLiad even if the user's records contains a Preferred First Name and/or Preferred Last Name. It would be incredibly helpful if Alma could pass preferred names to ILLiad if the user's record contains any preferred names.
35 votes -
Ful Resource Request Slip Letter split in two
We would like the Ful Resource Request Slip Letter printout to split in two: one letter for staff when picking material from stacks, and one for use on the hold shelf for end users to see. These two functions are difficult to combine since staff need to know who the requester is at the same time as GDPR makes anonymization of the hold shelf slip necessary.
We currently try to solve this by using the Ful Hold Shelf Request Slip Letter as the hold shelf slip. But this printout is meant only for staff and so is printed in the…
4 votes -
Australian Copyright compliance within Resource Sharing
Add Australian Copyright Compliance alongside the American Copyright Compliance option so Australian clients can utilise this feature via the Resource Sharing Borrower Copyright Management parameter.
49 votes -
Save Facet Settings
There are facet settings/searches we tend to run more than others. It would be really excellent and save a lot of duplicated work if it was possible to save certain facet configurations or bookmark the search so we could quickly access it again later. Would be even better if those searches could be shared among our staff, like how public sets are.
An example would be having a saved Request/Process type facet filter so we could quickly see what items were needing to be shipped physically, but there are any number of facet searches that it would be fantastic to…
1 vote -
Borrowing Renewal Workflow (non-ISO): Letter to patron in case of a not accepted Renewal Request
If a Renew Request was accepted, a letter (Ful Borrowing Info letter) is sent to the patron.
However, if a Renew Request was not accepted, no letter is sent to the patron.That's what we found in the documentation:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/050Resource_Sharing/Borrowing_Requests_(New_Layout)/Managing_Borrowing_Renewals_(New_Layout)
"5. If the request is renewed, a message is sent to the patron and a renewal fee may be charged. The letter is the Ful Borrowing Info letter. To configure the letter, see Configuring Alma Letters. A resource sharing renew fee is set as part of a fulfillment policy; see Adding Fulfillment Policies. If the request is rejected by the…28 votes -
Add Purchase Requests to blocked actions
We would like to prevent blocked users from submitting Purchase Requests. Although it is possible to ask Ex Libris to configure a blocked action for Resource Sharing Requests, it is not possible to do this for Purchase Requests. It would be useful to have a blocked action for Purchase Requests that we could use in Block Definitions.
5 votes -
Export funds from a PO Line
Allow the funds codes, amounts, and percentages, on a specific order to be exportable.
We often need to communicate these amounts with selectors, and this ensures no errors. The old interface allowed copy/paste into a table, and this has been lost with the new interface4 votes -
Ability to create true temporary "on the fly" items that disappear
The "quick cataloging" in fulfillment is fine for items that are expected to be shunted to technical services after they are returned, but some items, like journals that don't normally circulate, don't need to be processed after, just returned to the shelf. There should be a true "on the fly" process that creates a temporary record that is automatically deleted once the item is scanned back in.
8 votes
- Don't see your idea?