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.
1692 results found
-
Show the same note both in Edit service and on Edit collection level
For a bether overwiev show the note addedd in collection service also under Edit collection. Saves a lot of work.
Note is a great field.25 votes -
Open Predicted Items feature in MDE should bring in the Item Policy value from the previous item
The feature of Open Predicted Items in MDE cannot bring in the Item Policy as it does for the Material Type, which is inherited well from the previous item.
25 votes -
""Display in Discovery" link should go to Primo view based on your location in Alma
Currently if your Alma instance has multiple Primo views, you can only choose one for the ""Display in Discovery" link to go to. This can be incredibly frustrating for anyone needing to see the display in a different Primo view, as they have to edit the url.
Every Alma user already has to choose a location when they log in. Therefore, Alma should be configurable to go to a specific Primo view based on the current location of the Alma user.
25 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 -
Check coverage dates on physical holdings by link resolver
When there is no full-text match for an electronic title, the link resolver can bring back a bib record for physical holdings. However, since the coverage in the 866 field is not being checked, this shows records which do not match the dates desired sent by the the open URL.
Please consider implementing a check on the coverage dates of physical holdings to make things less confusing for patrons.
25 votes -
Tasks menu – customising display options.
UNSW Library are proposing that libraries can determine the options in the Alma Tasks menu “Citations” and “Reading Lists” display.
In Alma the Tasks menu displays as a widget or clipboard icon. (See screenshot)
The Tasks menu is an important feature for monitoring Citation/Reading List statuses. Over the years we have created local statuses and would like to build these into the display. As well as remove those statuses we do not need to monitor.
The benefit of this customisation allowing a library to configure these displays improves processing workflow.
25 votes -
Item Statistics Notes fields - choose controlled/not controlled individually
At present it is possible to choose for all three of the Item Statistics Notes to be controlled (i.e. select field contents from a drop-down list) or for all three not to be controlled (i.e. free text).
This is restrictive and inflexible. It would be preferable to be able to choose field by field which are controlled and which are not, i.e. have some of the Statistics Notes free text and others controlled.
25 votes -
Retain loosing accounts identifier in all IZ and NZ after a merge
After merging two accounts the primary identifier of the loser account can only be found in those IZs via the search in which it was also merged manually. In such cases, the message that the two accounts have been merged is added to the Notes of the winner account; including the primary identifier of the loser account.
We think this information should appear in the NZ as well as in all other IZs so that it can be tracked which accounts have been merged. This is important, for example, in cases where fines and fees in Alma have been closed,…25 votes -
Allow option to only send scheduled report from Analytics object if report has results
We want to set up reports to help us monitor for data inconsistencies and other issues that need addressing. We have noticed that we can set up reports as analytics objects and users can subscribe to them, but the report is sent even if there are no results.
We should have the option to not send empty reports, and only send if the report brought back one or more records.
25 votes -
Show more details about Work orders in user roles
When work orders are attached to circulation desks, the details of the work order cannot be edited.
This leads to a problem with maintaining roles, since the work order only shows its associated circulation desk. It is impossible to see from the user record what work order is associated with that user, making it difficult to add or remove desired work orders.
If the role parameters could show at least the Code, then that would provide useful information. This would be useful both in the user role view and the preset user profiles.
This idea was generated because my support…
25 votes -
Overlap and Collection Analysis reports enhancement
As a collection development librarian, I propose allowing the selection of multiple collections we want to compare. Repeating the same process for different collections is time-consuming. For example, we have 8 active IEEE collections, and I have to match them one by one with other collections.
Also, is it possible to re-run the Overlap analysis report if I forget to include some collections, instead of creating a new analysis each time?25 votes -
Add Ability to Exclude Holdings Records from LHR Publishing to OCLC When Holding/Bib Records Are Suppressed from Discovery
Currently, Alma's LHR Publishing job for OCLC does not exclude holdings records from publishing when the holdings record or the related bibliographic record is suppressed from discovery.
We request the addition of an option in the LHR publishing job to exclude such holdings records from publishing to OCLC. This functionality is particularly important for suppressed holdings records, as the management tag for publishing to OCLC is set at the bibliographic level. Currently, if a bib record contains two holdings records, it is not possible to publish one holding to OCLC while excluding the other.
25 votes -
Import Profiles - support mapping to E-Collection
See https://enhancements.exlibrisusers.org/ideas/AENH-I-36318
We need the ability to map to Electronic Collection. Because you cannot map to E-Collection, you have to have a separate profile for each collection for which you want to load portfolios. This dramatically increases the number of profiles we need to maintain. In addition, this requires more staff to have the ability to modify import profiles, even though the only thing changing each time is the collection name.
Mapping either the collection name (exact match) or the collection ID would be sufficient. This will enable more uniform loading of records.
25 votes -
EDI check in for print journals
Alma documentation states that Alma supports the following Edifact message types – INVOIC, ORDERS, OSTENQ, ORDRSP, ORDCHG. However our old LMS Aleph supported an additional Edifact message type called DESADV.
This allowed our serials agent, Ebsco, to check in our journals in on the LMS remotely via EDI once our monthly consolidated deliveries of print journals were despatched from the warehouse.
Provided our prediction patterns matched the PIA line this worked efficiently. An example of EDI text is as below:-
LIN+1'
PIA+5+0001-4788(2012)42?:1;1-9:SI::28'
IMD+L+050+:::ACCOUNTING AND BUSINESS RESEARCH'
QTY+12:1'
RFF+SNL:52280023'
RFF+SNA:52280023'The above essentially means that for order no 52280023 (linking to…
24 votes -
Add more options for ILL integration
Adding ILLiad integration to Alma was welcome but also brings more issues into the system. For example - patrons are shown in their account via Primo that ILL loaned items are not renewable. They are but not via Alma. A customizable message for the Resources sharing library that would display in "My Account" saying "Renewable via ILLiad" would be welcome. We have configured ILLiad to send courtesy notices. Now that we have integrated with Alma patrons get two courtesy and "due today" letters because Alma cannot turn off letters for specific locations. The ability to turn off those two letter…
24 votes -
Allow a differentiation of library addresses
Although we can define a library e-mail address for Billing, Claim response, Patron communications, Primary, Shipping, the preferred address is systematically used for all library specific communications.
This is problematic, as the service responsible for claim responses and orders is different from the service handling patron communications. Therefore, their e-mail addresses are different. Some libraries are too big for just providing a generic e-mail address for the whole library, as a person would then have to dispatch continuously the incoming e-mails.
So ideally, the e-mail specification possibility in Alma should actually help make this distinction.
24 votes -
Display override message consistently
Based on Block preferences, override messages can be configured. But these messages are shown only once in a session (as confirmed by Ex Libris, ticket 380696). We need this message to be displayed consistently each time that an action requires an override.
We would like to be able to configure for each Block preference whether the override message is to be shown only once per session or at each action triggering an override.24 votes -
Field creation date by changes via API
While changing a specific field in a user records via API the "creation date" should be changed only in this field and not in any other fields – which happens now – in order to be able to recognize the newest changes in a user profile.
24 votes -
Use Pieces field from item record to trigger a confirmation pop-up at checkout or return
Use the Pieces field from item records to trigger a confirmation pop-up at item checkout or return when that item has two or more pieces. Taking measures for prompting staff to add notes manually item-by-item or creating sets and running jobs to populate fulfillment notes for items that have 2,3,...9,10,...39,40,... pieces are both impractical. Not having a pieces confirmation at checkout feature is a frequent complaint on the Alma Listserv.
24 votes -
Borrowing Activity Letter
Currently, Alma limits the borrowing activity letter to list only 100 loans.
It would be great to have the letter list all loans without a limit.
24 votes
- Don't see your idea?