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.
1897 results found
-
Improve job "Requests - Handle Expiration steps"
The job "Requests - Handle Expiration Jobs" updates requests and at present, the output of the job informs only on the number of outputs. The job can block on a request-ID which then must be manually handled.
In order to save time and better inform the lending libraries, it would be helpful to have at least an information on any Error-causing request, with it's request-ID. Ideally it would be great to also have an output of successfully handled requests in form of a list, which can be exported to Excel.Improve the job "Requests - Handle Expiration Jobs" with output…
4 votes -
Additional "Suppress from FRBR/dedup" option and display
When viewing a bib record, the pop-out information to the side of the screen lists whether or not the bib is suppressed from discovery and suppressed from search. It would be helpful if this info also contained whether the bib was suppressed from FRBR/dedup.
Additionally, when you edit a bib record, you can select "Suppress from Discovery" and "Suppress from External Search" under the Record Actions dropdown menu. It would be helpful if there was also a "Suppress from FRBR/dedup" here.
1 vote -
Mass deletion of purchase requests
Purchase requests can be mass rejected but cannot be mass deleted after that, so they need to be deleted individually, which is frustrating and time-consuming.
2 votes -
Duplicate "Discovery Interface Display Logic" functionality to Configuration > Discovery
Many libraries have staff structures where discovery and fulfillment configuration are handled by different staff (who may be in different departments.) Having the "Discovery Interface Display Logic" menu in Configuration > Fulfillment means that discovery administrators must be granted fulfillment administrator roles to configure those aspects. In a "least risk" permission model, it would be much more preferable for those options to be on the Discovery Administrator menu - instead of fulfillment, or at the very least in addition to fulfillment, so that the extra role does not have to be granted.
1 vote -
Update Email Records Letter XML to use tags instead of metadata
Currently, the EmailRecordsLetter.xsl file has to use the <metadata> tag in EmailRecordsLetter XML. This prevents libraries from being able to customize the display of the emailed record.
EmailRecordsLetter XML should have tags similar to other letters, like <title> and <mms_id>. This would enable libraries to customize and create a professional, modern email.
1 vote -
Display Number of Records in Set Information Section
It would be extremely beneficial to have the ability to view the number of records in a set directly within the Set Information Section, without the need to click through to the content.
Specifically, adding a line such as “Number of Records: ####” in the Set Information Section would streamline the process of sorting through sets. For example, when managing multiple sets of items for withdrawal, it would allow me (or my students) to quickly ascertain the number of remaining items without the need to navigate into each set, view the content, and then return to the previous screen.
This…
9 votes -
Ability to make bulk bookings in Excel and import (similar to updating calendars in Excel)
We use the booking feature for student study rooms, but occasionally some (though not all) of these rooms need to be booked off for special events, i.e., convocation, reserving time for reference interviews, etc.
Our library could benefit from the ability to create these bulk bookings in Excel (copying/duplicating rows) as we would when updating our hours of operation.
Excel columns might include the barcode for the room, the barcode for the special patron account we use to block off rooms as needed, dates, start/end times, and a yes/no for whether the booking may override normal booking rules/restrictions.
1 vote -
Ability to report on the source of a MARC record
It would be useful to be able to report on the source of a MARC record in Alma Analytics. This should be part of the 'Titles' Subject Area, providing information on whether the record was created using a record from a Z39.50 query or via a scheduled or manual import job.
If the record is imported via a Z39.50 query, the source bibliographic knowledgebase should be reportable (e.g. OCLC WorldCat, Jisc Library Hub etc.).
If the record was created via an import job, the name of the import profile should be reportable.
This would help libraries to better maintain statistics…
3 votes -
Add "Rule details", "Terms of use", and "Fulfillment Policy" as shared descriptive dimensions with Fulfillment subject area
We would find it very useful to be able to report on fulfillment activity as tied to configuration. For example, we'd like to be able to report on items that allow unlimited renewals versus items that allow renews but limit the time frame.
From what I can tell, only the loan length is included in the Fulfillment subject area, but the terms of use information is in the Configurations (Limited) subject area. But, we cannot do a multiple subject report without them being shared dimensions in Fulfillment. It would be very helpful if they could be added.
1 vote -
Request limit
It will be useful to limit the number of request for a specific library. Likewise for loan limits.
If an institution has more than one library then it may want, for example, to allow a patron to borrow from several of them. Then the order limit should be correspondingly larger. However, if the loan limit is larger than the request limit, this situation can be confusing for the user. For example - a patron has a request limit of 10, and loan limit 5 in Library A and 5 in Library B. However, for the moment he can request 10…18 votes -
Include MARC leader in General Electronic Services Bib Fields Enrichment
The addition of bib fields enrichment for general electronic services has been helpful in creating service availability rules for GESes, but there is no way to configure enrichment based upon content in the MARC record leader. This is where primary resource aspects are noted, such as record type, bibliographic level, and whether a resource is under archival control. Being able to use this criteria when displaying or hiding a service would be much easier than the convoluted and imperfect workarounds we've resorted to.
3 votes -
Alma Community Zone collection for Mucchi Editore OA
Mucchi Editore publishes open access ebooks and I am interested in making them discoverable via Primo VE. Information about the books is available at https://mucchieditore.it/catalogo/open-access
Thank you0 votes -
Add CSIRO Publishing BioSelect Collection to Alma
The newest eBook collaboration between CSIRO Publishing and BioOne is not yet available in Alma.
Please consider adding it your collection.
https://bioone.org/csiro-ebooks3 votes -
Expand webhook monitoring to all record types in Alma
Libraries utilize the webhook tool in Alma to be notified when some events occur, and includes information on the results or status of that event. Unfortunately, the tool does not include all record types in Alma. For example, portfolio and representation records, though mentioned in Ex Libris webhook documentation ( https://developers.exlibrisgroup.com/wp-content/uploads/alma/xsd/webhook.xsd ), are not actually monitored by the tool. In August 2024, this was communicated to Ex Libris for these two specific record types, and a “planned for future release” clause was added to their page, but with no timeline. Ex Libris recommended submitting an enhancement. Please expand webhook monitoring…
3 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.
3 votes -
Allowing the relink of a holding from a bib record to another maintaining the call number even if the location is the same.
Now in Alma if you try to relink a holding with the same location (ex.: ABC) and call number 123 (1) from a record to another that have already a holding with the same location (ABC) and call number 123 (2), the holding with location ABC and call number 123 (1) disappear and everything is under the location ABC and call number 123 (2),.
This happens with a relink of a POL or an item.
We want to maintain the call number 123 (1).
If it is not possible to do it automatically at least a pop up message that…58 votes -
Allowing the Bulk Scan In App to Export List of Items Scanned
When using the bulk scan in app, you get a list of items that have been scanned in and those that have errors. Currently there is no way to export this list into excel to be able to keep track of the errors. If you click off the app to check a barcode with an error, the information disappears and you have to rerun the bulk scan in again. It would be great if you could export the whole list at once to excel to have a good record of the those that were successful and those that had errors.
17 votes -
Alma Link Resolver on all Google Scholar Records
As an Alma Administrator at Kettering University, we would like the option for our Alma link resolver to appear on all Google Scholar records.
It would be nice for our patrons searching in Google Scholar to see the option to check access in our library holdings or request through our resource sharing without leaving the platform. We have activated it now in the library links settings, but it only appears in limited records (image attached).
Related to Support Ticket ID: 07235331
Thank you,
Courtney1 vote -
Vendor Communication will not send without PO Line Attached
As an Alma Administrator at Kettering University, we would like the ability for the 'Acquistions>Vendors>Communications tab' area to send emails to vendors without a PO line attached. Currently, correspondence will not be sent if you try to email a vendor without an associated PO Line. This will help us keep vendor correspondences more streamlined and structured, eliminating the need to download personal emails to PDF format and upload them.
Not all communications we have with a vendor will be order-based. Does anyone know of any fixes or backend settings allowing those to be sent? We were informed at the Support…
1 vote -
Improvements for the MDEs left pane
The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
- Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…38 votes
- Don't see your idea?