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.
1730 results found
-
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 -
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".
30 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 votes -
Add "Which coverage statement will be applied?" option to "Change Electronic portfolio information" job
The "Change Electronic portfolio information" job includes the task "Remove local coverage" which removes local coverage from all the portfolios in a set so the only coverage remaining is global coverage. I run this in cases where the global coverage was once poor, so we loaded local coverage, but now the global coverage has been fixed and is good, so now we want to remove our local coverage and use the good global coverage. However, "Remove local coverage" does not also change the "Which coverage statement will be applied?" radio button from "Only local" to "Only global."
It is important…
87 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…
59 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,…23 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…
53 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.
-
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.42 votes -
Browse Shelf Listing Call Numbers - 852 $$j
Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.
Example:
852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.
We need a 'Browse Shelf Listing' that lists ALL…
72 votes -
Add General Electronic Services information to Analytics
In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".
Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would…
67 votes -
Community-Managed electronic collections: Add several portfolios to one title
In Community-Managed electronic collections, it is not possible to contribute a second portfolio to the same title that is pointing to a different URL. Use case: Both URLs are valid, both contain copies (in part) of the journal. It would be nice, if the contribution only gets blocked, if the URL of the newly contributed portfolio is identical to the existing one.
34 votes -
Add reminders to Analytics
The function reminders is only partly useful at the moment. Improve it by adding reminders to Analytics. Creating and scheduling reports on reminders by type, status, text and so on would be very helpful for us.
32 votes -
Allow for an authority file to be addressed by different codes in $2 of various BIB fields
In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.
In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,…
142 votes -
Prevent items to be loaned immediately when they are returned at a SIP2 Self check machine and have a Rapido personal delivery request
When a loaned item is returned at a SIP2 Self check machine and has a Rapido personal delivery request, the item is automatically loaned to the patron (and sorted to a request bin). Requested items then are scanned in at a circulation desk for further processing. In case of a personal delivery request, the item is immediately returned and marked for reshelving. Librarians do not see that there was a request (and a short loan).
Previously we handled personal delivery requests via a GetIt request. The effect was the same, but we were able to prevent this behaviour by de-selecting…
46 votes -
Pop-up window with information about blocks and reader's fees when create a request
It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.
For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders…
20 votes -
Alma Split View Hides Main Menu, Affecting Cloud App Access
After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.
This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.
As a consequence, many staff members have stopped using cloud apps…
36 votes -
Rapido – Popup warning when local/consortium copy exists
We have more than 4 millions documents in our consortia, and a Rapido service. Sometimes patrons order a document via Rapido while this document is available locally. This can be choice or an error. To avoid errors, Rapido should display a configurable popup whenever a patron submits a Rapido request for an item that is available in our consortium. The popup would warn the user that a free local loan exists and ask for explicit confirmation before sending a paid ILL request, for example: “One or more copies are available from your library network for free loan. Would you still…
18 votes -
Have multiple pickup locations available in Primo when requesting items from the same library
Our wish is to be able to offer several pickup locations in Primo for the same library when documents are available for loan (not linked to a reading room desk) without having to create a new virtual library. The library must be able to configure the visibility of these pickup locations based on certain user criteria (e.g., user group).
For example, a library may offer a special room whose access is reserved for teachers and doctoral students. The library would like doctoral students/teachers to be able to choose this room as their pickup location at the time of the request…
27 votes -
Keep patron physical requests active even if “deliver to” relationships are temporarily interrupted
Our consortia has several libraries connected through “deliver to” relationships, allowing patrons to request and pick up physical items from different sites.
Currently, when these relationships are interrupted — for example, due to maintenance, or temporary closures — all related patron requests are automatically cancelled, and patrons receive cancellation notifications. That makes them angry.
We would like Alma to preserve these requests in an active or pending state during such interruptions, so they can be fulfilled automatically once the relationship is restored, without requiring patrons to place new requests.
This would improve the user experience and reduce administrative workload for…
33 votes
.png){kind=link}
- Don't see your idea?