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.
1691 results found
-
Add flags to tabs in vendor interface record area
We noticed the little corner/flag is not changing on the vendor interface details tabs when we add administrative information/access information/statistics information. We thought it would show like the notes tab with a dark corner when we enter information so we know that we have stuff in these tabs. We thought it was a glitch, so we reported to Ex Libris. They said it is by design:
The answer is that it is by design. The little corner flag is an indicator that there is system or user generated content like populated tables or lists. It doesn't indicate that form data…3 votes -
SUSHI harvesting for JSTOR
I noticed that our SUSHI harvesting for JSTOR hadn't worked successfully since May 2023. The requests for reports were coming back with this message:
{"Code": 1011, "Severity": "Warning", "Message": "Report Queued for Processing", "Help_URL": "https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview", "Data": "Successful request. You must re-request this report to receive data. Please allow 1 hour for processing before retrying."}
So I reviewed the information here:
https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overviewThis page makes it clear that this is expected behaviour.
I ran a custom harvest for June-Sept 2023 and it failed (as expected).
I ran a second custom harvest an hour later and it succeeded.I'm not…
10 votes -
Make it possible to choose to which Work Order Department an item goes after receipt (not just Acquisitions)
We have noticed that our real-life workflow doesn't align well with Alma's behavior regarding receiving items. In practice, when we receive an item, it promptly moves to a different department – transitioning from acquisitions to the catalog department. In Alma, however, achieving this requires manual department adjustments each time an item is received. While we are familiar with options such as "keep in department," "shelf ready," and work orders, none of these options yield the desired outcome or contribute to streamlining the process. Our objective is to minimize unnecessary clicks, and it would greatly enhance the user experience if items…
36 votes -
Not "Notify user" when canceling a "Patron physical item request"
In most situations we don’t want a request cancellation to be sent to users when we cancel a patron physical item request (Ful Cancel Request Letter). But since the checkbox “Notify user” is checked by default, the letter often gets sent by mistake, resulting in users thinking they will not receive the requested material, when in fact they will. We want the checkbox to be unchecked by default. Maybe this could be a configurable option in Alma (whether the checkbox is checked or not) so that each library can decide this for themselves?
20 votes -
Physical item editor Receiving date
In the Physical Item Editor Receiving date field, in order to add today's date, one must click on the calendar, then click on the day. Since today's date is already highlighted in the calendar, I would like the option to hit Enter to fill in the field. Even better would be the option of typing a t (for example) and having today's date autofill.
5 votes -
Configurable hard coded date for request expiry
We've struggled with users not understanding the purpose of the 'Not needed after' date field in the various request forms linked to Primo VE. This often means we received requests with supplied 'Not needed after' dates of a few days later meaning they're cancelled before even being in transit or picked, particularly on unstaffed weekends. Relabelling the field hasn't helped matters due to users not paying attention to it and thinking it's a 'needed/collect on' mandatory date.
If possible we would like the ability to set a hard coded expiry range for non-processed requests. For example, if a recall request…
3 votes -
Add option for patron name suffixes like Jr., Sr., or III
Name searches in Alma for names containing suffixes like Jr., Sr., or III yield strange results.
Example: Someone named Joe Johnson Jr. will have first name "Joe" and last name as "Johnson Jr." When performing searches in Alma for "Joe Johnson", "Joe Johnson*", or "Joe *Jr." will not yield any results.
Alma looks for "Jr." as a last name rather than the person's surname. This isn't helpful when SIS has the suffix but the patron may not use the suffix all the time in their everyday life.
Creating the option for a patron name suffix or updating the search for…
4 votes -
Add a new privilege to the "Purchasing Operator" role which will prevent users with this role from being able to delete items
This Idea was submitted by ExLibris to check the community support for the following enhancemnet:
Currently, users with "Purchasing Operator" role can delete items, the existing logic behind this is, when a PO line is created (even before it is received), there is a need for the Purchasing Operator to be able to delete the item in case of an error on the order.This Idea suggest to add a new privilege to the Purchasing Operator role which will prevent this user from being able to delete items - the new privilege should be enabled by default to maintain existing…
0 votes -
New role for limited user account editing
It would be helpful if we had a separate role for User Operator that could edit any user account's contact details and merge user records as well as run analytics on users BUT not change or add roles attached to that account OR delete records. This is primarily to allow circulation staff more control over user accounts but to restrict access to higher-level abilities for cybersecurity reasons.
1 vote -
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 -
Analytics widget - customize/remove Open in a new window link
I'd like to be able to remove or customize the "Open in a new window" link that appears on top of a widget of an analytics report.
The widget can only fit a very short report. Opening this short report in full view is not that useful. It would be better to link to a longer report or a dashboard.
1 vote -
Add a link from the PO line to the "Receive" workbench
It would be helpful to have a link to the receiving workbench from a POL, to eliminate the extra step of receiving items that are ordered but already in hand. This applies especially to standing orders and gifts. We already have the items in hand at the time of order creation. With the current setup, we have to 1) create the POL, 2) write down the POL number or copy it before selecting Order Now, 3) switch to Receive to receive the item in order to close the POL. Merging step 3 into the POL creation process would save a…
23 votes -
Time stamp on printed Resource Request Slip Letter and Hold Shelf Request Letters
Add the time stamp to Resource Request Slip Letter and on Hold Shelf Request letters when printed.
1 vote -
Physical PO line creation - allow the interested user defined on the PO line to place a title level request when the PO line is created
This idea was submitted by Ex Libris to evaluate the need for the enhancement specified below:
Today, when a physical PO line has an interested uset, a hold request is not created on the bibliographic title until the book is scanned in at a circulation desk (Item is received).
Customer rely on being able to see all requests on a title from the moment it is purchased. This is because they want both users and staff to be able to see the whole physical request queue from the moment a book is purchased, currently it creates uncertainties about who is…0 votes -
attachement tab in e collection editor
can we have an attachements tab in e collection editor so we can attach useful docs/comms relevant to that source, thank you
3 votes -
Claiming at Item Level
Being able to claim at item-level so that we can mark an expected issue at CLAIMED/CLAIM so that magazines, journals, newspapers, and serial publication books would be easier to claim.
7 votes -
Allow AFN loans and returns via Offline Circulation
AFN (Automated Fulfillment Network) items can neither be loaned nor returned via Offline Circulation. The Offline client accepts the AFN barcodes, but when we attempt to load the file into Alma the resulting error message is "Item not found. Barcode: [barcode number]". Since non-AFN resource sharing loans are considered “local” records in Alma, they can circulate via Offline Circulation. Please add this functionality for AFN loans and returns as well.
1 vote -
Notes in POL's should only be for notes (not history)
The notes tab in POL's for serials/journals should only be for notes that pertain to that order. When orders are set to automatic renewal, every year when it renews a note is added saying "PO Line has been renewed automatically". Over the years this note takes over and all of the pertinent notes are moved to the bottom. I am constantly having to remove those automatic renewal notes to keep the important notes at the top. The automatic renewal note should go into the history tab not the note tab.
163 votesDear all,
Thank you for sharing this idea.
I have read it carefully, and would like to make sure that I understand it:
Current situation:
There are several processes in PO line workflow which add automatic internal notes, for example:
- Renewal ("PO Line has been renewed automatically on…")
- Moving PO line out of PO (""Line was removed from Order ...")
- other.
Desired outcome:
Have a configurable option to disable these notes from being created. Each of these processes is/will be saved in the PO line history.
Please let me know if this understanding is correct.
Thanks,
Zohar Shemesh
Alma product team
-
Configuration option to prevent Digitization request when item is on loan.
Issue: Digitization requests are typically needed “ASAP” by our users. When an item is on loan, we don’t want to recall it as it will typically take longer than the requester can wait.
Current configuration options:
When Configuring Loan Recall Requests and the following is set to “Yes” PHYSICALTODIGITIZATION - Patron digitization request for physical resource, the item will be recalled. When set to “No” the item will not be recalled, instead a hold is placed on the item.Need: A configuration option for digitization requests that does not recall or place a hold(prevent renewal) on items that…
2 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
- Don't see your idea?