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
-
Link single or selected local portfolios in a CZ collection to the community instead of all local portfolios in a CZ collection
Currently, when linking local portfolios in a CZ collection to the Community Zone (CZ) using “Link Local Portfolios to Community”, it is only possible to run the job on all local portfolios in that collection, rather than just a single portfolio or a selection of portfolios. (Linking a single portfolio only works for stand-alone portfolios, not for local portfolios in a CZ collection).
It would be useful if an option could be added to link a single local portfolio in a CZ collection to the CZ. Also, it would be helpful if the "Link Local Portfolios to Community" option in…
9 votes -
Receiving queue - continuous, claim status and last issue collected
I am an acquisitions librarian at a legal deposit library. We have nearly 9000 active subscriptions and we often want to look at the status of other active POLs by the same vendor when receiving. It would be helpful to see in the receiving queue the receipt status of a POL at a glance, rather than having to go into manage items. This would be whether the POL has overdue items (is in claim); and the description of the last issue collected.
9 votes -
Alma as a linked entity User Interface
The Alma backend comprises a large bunch of linked entities of different types like title, holding, request, item, report, ... However, on the user interface side theses links and references often are only displayed implicitly. We propose to make these references explicit. Example: The list of requests shown in "Monitor Requests and Item Processes" display a MMS-ID as well as (in certain cases) an Item ID. In order to view the respective title or item entity one has to copy the ID and paste it into the title, respectivly item search. We propose to add a "one click link" for…
9 votes -
add modification date to "Monitor Requests & Item Processes"
It would be helpful to have the modification date, not just the request date as filter on the "Monitor Requests & Item Processes" page. Now it's almost not possible to find items which are e.g. stuck in hold shelf processing.
The request date does not allow to filter for items/requests which have been processed recently.8 votes -
Consider only the opening days and hours when calculating the transit time
The Transit Time Rule for Physical Item Requests calculates the transit time in calendar days.
As a result, days and times when the library is closed are also indicated as estimated delivery times for the requested media.
These times are also displayed in Primo and thus give users incorrect information.
Would it be possible to consider only the opening days and hours of the libraries when calculating the transit time?8 votes -
Possibility to duplicate a Staff User record
We do use Role Profiles to create new Sfaff Users as easily as possible.
However, we have about 30 sublibraries and colleagues, some of them working in several libraries or have special WO Department permissions, etc. Therefore we do not have suitable Role Profiles for all combinations.It would be great if we could duplicate an existing Staff User record instead of having to create a user from scratch.
Thank you in advance!
8 votes -
Add "Status" to user searches
There is no current method for adding "Status" to the list of available selections when running a User search in Alma; as such, the only way to find a list of active users is to either use the filter provided post-search (the selections in which are "All," "Active and not expired," and "Not active and expired") or to use Analytics.
However, these filter options exclude searches for users who are both Active and Expired, and using Analytics to create a report for this result requires multiple steps to set up before you can get a result (and subsequently run jobs…
8 votes -
Implement AutoHoldings for Alexander Street Press
Implement auto holdings (autoholding, auto load, autoload) for Alexander Street Press Academic Video Online, as is already available for ProQuest, Elsevier, Ovid, and Springer, and Wiley.
8 votes -
User action history report
Our institution's security protocols require systems that handle confidential patron/student data have the ability to log backend staff user actions. After inquiring to ExL, the only way to know what a staff member has done in the system is to go through their individual history tab. However, this data is incomplete and doesn't give a full scope of what actions they took. In Analytics, the options provided are not useful and do not give us any useful information.
We'd like to track things like:
- When roles were issued
- Who issued roles
- Changes in configuration and who made…8 votes -
Bulk update block expiry date
In January 2018, fulfillment enhancement was added to allow library staff to manually add a block expiry date and edit the expiration date on an existing block. (See https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/12_January_2018/Alma_January_2018_Release_Notes/04Fulfillment_-_January_2018_Enhancements)
We would really like to have the option to input a block expiry date in the bulk update/notify users job when adding a block type, instead of manually adding the blocks with expiry date one at a time for a batch of library user records.
8 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 -
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…
8 votes -
Additional Report to ExLibris Option
Adding the option to "Report to Ex Libris" from the Electronic Titles search page would make reporting issues to them much more streamlined.
Currently you have to
1) Find out what collection it is in
2) Go to the portfolio list
3) Search for the title
4) Then you have the option to Report to Ex Libris by clicking the three dots8 votes -
Add "Copy ID" to loan information in Manage Patron Services
When viewing a patron's current loans in "Manage Patron Services", Alma will display information like the loaned item's barcode, but it doesn't display its "Copy ID". When libraries have multiple copies of one item, it can be difficult to tell which item is out on loan to a specific patron without leaving the Patron Services page and going to view the item itself. "Copy ID", like "Barcode", is a unique identifier for an item and should be visible in the same way.
8 votes -
Add option in Analytics to report on user notes that are set to pop up note
Alma does not currently offer the ability to use Analytics to identify user notes that are set to pop up. We would like to be able to more easily identify these notes that are set to pop up to prioritize them during a user note clean up project.
8 votes -
Interface field "Admin Documentation" - Extend default display size
The Interface field "Admin Documentation" contains often a lot of text which covers several rows.
In order to read the content of the field more quickly without scrolling, It would be helpful if the default display size of the field could be extended - ideally to four rows instead of two.
8 votes -
Expand API access to all record fields across all record types
Libraries frequently use API access to Alma records to complete a variety of tasks, provide services, and support special projects. Currently, the types of records and fields that are accessible via APIs are limited. For example, in bibliographic records, the 024 (UPC) field data is inaccessible via the API. Please Expand API access to all record fields across all record types.
8 votes -
Flag an alert when a purge date falls earlier than an expiry date
A colleague has raised the point that currently when editing and saving a user record, if the purge date precedes the expiry date no alert is raised. This means if the purge date is adjusted and is set before the expiry in error, nothing alerts the user to this fact.
Would it be possible to have a an alert either in the form of a message or sidebar error alert to make the operator aware of the data issue when saving the changes?
8 votes -
Add Cancellation Reason code and Notes to the Interested In Letter XML
This essentially replicates an earlier request that was closed in 2021 without resolution:
We would like to have Cancellation Reason code and Cancellation Note available in the XML that is supplied to the Interested In letter template. The Cancellation Reason code is a distinct field In Analytics, so I would hope that this would be easy to add to the XML. The cancellation note might be trickier -- it is stored as a PO Line Note in Analytics. If the cancellation note is just one of several PO Line notes in Alma, we would be happy to have all…
8 votes -
Allow deleting or editing a manually packaged PO without deleting all the POLs
There needs to be a way to delete a manually packaged PO without also deleting all the POLs associated with that PO. I can understand not allowing this if the PO is closed, but if the PO is only in "sent," then it should be allowable to either delete that PO without also deleting all the associated POLs OR allow editing that PO to attach additional POLs to that PO. This would essentially be the same logic when manually creating an invoice in Alma: it's possible to add as many POLs as needed when creating an invoice in Alma by…
8 votes
- Don't see your idea?