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.
1809 results found
-
Reading Lists in the Task List Customise Alma task list (tasks requiring your attention) to match all our reading list statuses
As Acquisitions & Reading Lists Manager I would like to customise the Alma task list (tasks requiring your attention) to help the reading list team manage the reading list workflow as using facets is a time-consuming long way round to find the list categories each time.
Alma task list (tasks requiring your attention), section Reading lists, we would like to customise this list of tasks or add all reading list statuses each Library may have.
We have reading lists with status other than Unassigned - processing, complete, reading for processing.
We have 'updated' and 'core done' to help us manage…
44 votes -
Add Resource Sharing Partner Setting for ILLiad Cleared Status
When a library creates a resource sharing partner for ILLiad and checks the Create User in ILLiad box, Alma does not pass a Cleared value in the CreateUser ILLiad API call. This means all ILLiad user records created by Alma need to be manually cleared. Please add a new setting to the ILLiad resource sharing partner type that allows libraries to select a Cleared value of either "No" or "New".
34 votes -
Wikidata URIs
We request that Wikidata be maintained within Alma as an authority vocabulary source. This functionality should include the ability to search against Wikidata as part of the Metadata Editor F3 linked data enrichment function. Cataloguers should be able to enrich bibliographic records by manually selecting the authority to apply the corresponding Wikidata URI to a name heading. This is useful for non-Library of Congress cataloguers and for those with Special Collections and archiving cataloguing responsibilities to use a more agile and international authority source in our cataloguing.
68 votes -
Expand SIP2 message support to include patron birth date
Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.
For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).
We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age
This enhancement would enable safer and more autonomous self-service environments, particularly…
67 votes -
Improve locate process to accurately determine an article’s availability based on the partner’s portfolio coverage
Currently, when a digital resource sharing request include only the publication date year, the system interprets the publication date as January 1 of that year. If the partner’s portfolio coverage includes only volume/issue, the availability is calculated based on the volume/issue information in the request. However, if the portfolio coverage includes both year and month, then the availability is calculated based on dates only. Even if the coverage also includes volume/issue, the volume/issue data in the request is ignored, and the link resolver does not estimate dates based on volume/issue. The locate process then checks if there is an embargo…
14 votes -
Improve precision of locate process for digital resource sharing article requests
Currently, when identifiers are not included in a resource sharing request form, Alma uses a search mechanism based on keywords to guide the locate process. This results in many false positive matches. Additional locate by fields (title, author) selected in the partner’s locate profile and Resource Sharing Library lending setup are not considered in the process. Turning on the Locate only when all fields match setting does not improve the accuracy of the locate for article requests, as article author is not considered in the matching process for article, with the journal title being the main matching element.
We would…
16 votes -
Allow customers to select multiple retention reasons for Item records.
Allow customers to select multiple retention reasons for Item records.
As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:
Institutional last copy
Faculty publication
Rare
Committed to some Shared Print program
Digitized material
Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff…
70 votes -
Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3
When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.
Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end…
48 votesCan you please confirm whether the $e subfield is always expected to appear before $0 and $1 in your workflows? If this is consistently the case, it may be possible to address the issue using an XSL normalization rule to automatically position the $e subfield before these subfields.
-
Increase the number of available facets for all POL searching
All aspects of the POL should be available as facets, assuming they appear sufficiently frequently in a set of results. Most notably, all 5 reporting code fields should be available as facets.
Additionally, other sources of POL lists, such as the Alma Vendor Record should offer all of the same faceting functionality, including the ability to customize which facets are visible.47 votes -
Search Authority Headings: Mariano Moreno National Library of Argentina. Import BNA10 - Z39.50 protocol
Implement the import of authority records via Z39.50 from the Mariano Moreno National Library of Argentina. Is not listed in “Authority vocabularies in the Community Zone” https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(Espa%C3%B1ol)/Gesti%C3%B3n_de_metadatos/050Trabajar_con_registros_de_autoridad
Downloading authority records
https://www.bn.gov.ar/bibliotecarios/protocoloZ3950
Z39.50 protocolIP: 200.123.191.9
Port: 9991
Database: BNA10
Authentication: YES
Username: Z39.50
Password: Z39.50
Character set: UTF-8
Format syntax: MARC21
Contact: dpt@bn.gob.arA Proquest case (10586567) was submitted—Search for Authority Headings: Mariano Moreno National Library of Argentina. It was noted that "Alma currently allows the import of bibliographic records from the Mariano Moreno National Library using the BNA01 database. However, the incorporation of the BNA10 database for authority records…
18 votes -
Allow merge rules for authority import profiles
It would be very useful allowing custom merge rules in Alma authority import profiles for ensure controlled, automated updates of authority records,
especially in a cooperative cataloguing environment.
Configuring these rules to selectively merge, keep, or add specific MARC fields during import, would ensure enhancing data quality for both local
and network zones.16 votes -
Add an API endpoint to rerun an import profile job that failed
We are monthly running an automated import profile to import electronic resources. Almost every time the import profile job finishes with status Completed with Errors and needs to be manually "rerun". This is a documented behavior: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/060Record_Import/080Monitor_and_View_Import_Jobs#Rerun.
We would like to have an API endpoint through which we can simply rerun the import profile job that have failed due to the error "Failed in Commit after calling NZ" in some of it's files. This would allow to have the whole import process truly automated and without the need to manually intervene every time it runs.
31 votes -
Add function to monitor broken display logic rules
When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken…
56 votes -
Improve cookies on Alma and other Clarivate sites
Alma-specific:
* Re-configure the OneTrust settings so that performance cookies default to off
* Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
* Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)Clarivate-wide:
* Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,…21 votes -
Option to mark Home Delivery addresses added during requests as "Preferred"
Most of our patrons do not have a pre-registered address in their records, so we rely heavily on the Home Delivery option in Primo VE, which allows users to provide their address directly during the request process. While this feature is highly valued by our patrons, it presents a significant operational issue because these addresses are not automatically marked as "Preferred" in Alma. Consequently, this information does not appear on the patron’s activity page and, more critically, it cannot be retrieved within the Analytics Fulfillment subject area, where only preferred addresses are accessible for reporting.
To resolve this, we request…
21 votes -
Encumbered Balance Amounts only link to unpaid purchase order lines
In the Summary Details of an allocated fund code, there are hyperlinked amounts listed next to Expended Balance and Encumbered Balance. We want the Encumbered Balance amount to link through to only purchase order lines that make up the total balance amount listed in the hyperlink.
Currently it links through to any purchase order line that had an encumbrance placed on it with this allocated fund code. Regardless of whether the purchase order line has already been expended and disencumbered or still has an outstanding encumbrance waiting to expend on it.
This would be helpful as it would give us…
9 votes -
Predicted Items - Add columns in Metadata overview
When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.
Currently, the following columns are shown:
- Description
- Status
- Expected arrival datePlease add:
- First level of enumeration (= Enumeration A in the physical item editor)
- Second level of enumeration (= Enumeration B)
- First level of chonology (= Chronology I)
- Second level of chronology (= Chronology J)This addition would make it easier to verify whether all relevant fields are correctly…
50 votesHi all,
Please note that this idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.
-
Added fine/fee notification
It is possible to schedule a job sending letters for outstanding fines and fees. However, it would be helpful if patrons could get a notification the moment a fee or fine is created aside from this "reminder letter". We would like to have the option to "notify user" when adding a fine or fee.
13 votes -
Suggested update to Automatic Due‑Date Adjustment for Early Patron Expiry
At UWA, users receive no warning when their records expire in Alma. If we implemented the Automatic Due‑Date Adjustment for Early Patron Expiry, users would receive an email advising that their loans were due the same day, which is not client-focused.
Would it be possible to have a configurable loan grace period, so that loans would be due a certain amount of time after user expiry?
11 votes -
acquisition vendor analytics expansion: all URLs
We would like to see more complete vendor information in Analytics in general, however this specific request is for inclusion of all URL types, along with both their description and note fields.
The use case is that we are hindered from fully using all the fields within Alma when we cannot run reports on that information in order to back it up. The backup is necessary due to the lack of an "are you sure" popup for the Delete action. Also, administrative and statistics login information needs to be available to all acquisitions and e-resources staff, however it needs to…
19 votes
- Don't see your idea?