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.
1812 results found
-
Seasonal Serials Prediction Patterns only work when beginning with Spring.
Area of concern: Serials Prediction in Alma.
Currently, when creating 853 predictive patterns, there are limitations to titles with a seasonal frequency. Attempting to create seasonal prediction patterns, whose enumerations begin with anything but Spring (21) results in errors, such as skipped issues, or improper numbering.
This limitation means that many journals with seasonal patterns cannot have their issues correctly predicted out through Alma’s automated process. Staff members are stuck manually creating/receiving issues for these titles. This decreases efficiency, increases the likelihood of human error, and prevents Alma’s claiming process from working correctly.
What should be changed: As Serials Processors,…
66 votes -
Add warning to "Scan In Items" and "Shipping Items" for certain item policies
We would like to suggest the implementation of a pop-up for "Scan In Items" and "Shipping Items" to alert staff when they are about to process an item with a restrictive item policy (e.g. 63, 67, 68, etc.).
For example, when a request is placed at the title level and there are multiple items with differing item policies, this pop-up would be helpful to avoid processing the wrong item.
66 votes -
Add 245 subfield n to the letter XML node for title
Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.
We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
245 10 |a Prisma Physik |n 1
245 10 |a Deutsch |n Drei
245 00 |a Prisma |n 1
245 10 |a <<Die>> Sprachstarken |n 2 |b…66 votes -
We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them o
This is about allowing Course Reserves course and reading lists to be able to be managed in sets and deleted in bulk.
We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them one at a time and have thousands of old outdated ones. This could either be done in the Mange Fulfillment Sets or just Manage Sets and then we would want a way to delete them too with a job.
65 votes -
Note Type
Have the options to create different Note Types under the patrons note tab.
65 votes -
Indication rule that checks if subfields are in the same field
Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:
Record 1:
690 $$a mercury $$b venusRecord 2:
690 $$a mercury $$b mars
690 $$a earth $$b venusI'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.…
65 votesI recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.
-
Change default value in pop-up message for shipped items in the scan in interface
This warning message was added in July 2020 release to prevent accidentally completing a lending request:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes
With the introduction of Rapido, we noticed this warning message popping up a lot more often, and since the default value is on "Confirm", many requests are cancelled accidentally by double-scanning. We would like to suggest that this message be set by default to "Cancel" rather than "Confirm" or being able to configure the preselected default value.
The mapping table is under: IZ Configuration > Fulfillment > Physical Fulfillment > Scan In Messages Configuration > line 3 Complete lending request.65 votes -
Open / Closed Stacks Request Possibilities Priority
Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.
In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.
We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item…
65 votes -
Improvements to Pick From Shelf list needed
Currently our staff spend too much time managing requests. Improvements to the interface for Pick From Shelf would help in some of these cases. We would like to see:
- A search box.
Very often we need to target a particular request, a task made more difficult by less than ideal facets (see #2). Search functionality exists under Monitor Requests & Item Processes, but not all options for handling requests are available in that view (such as "Skip Location").
- Better facets.
Two of the facets available in the Monitor Requests & Item Processes view would be great for Pick from Shelf:…
64 votes -
Ability to use import profiles on OCLC Connexion exported records
Currently import profiles can applied to Marc files that are uploaded into Alma. One can use the import profile to specify match methods, tell Alma how to deal with matches of existing and incoming records (overlay, merge, or use NZ record), and also specify inventory info to map the Marc 949 field to holdings and item records. Although the OCLC Connexion integration profile deals with importing records it lacks the features described in the previous sentence. Please see screenshot of settings in Oclc integration profile versus in an import profile.
Basically we would like the ability to specify an import…
64 votes -
Colour/shade gradients to tell the different between license statuses (Active, Retired, Deleted)
In the list of licenses it would be useful to have a colour/shading gradient difference between active and inactive licenses.
For example, when you delete a license it still remains in Alma, it is just given the status deleted. This is fine as it provides a history, however, as the deleted licenses in the list look exactly the same as active licenses, apart from the status note it can often be difficult to tell the active and deleted licences apart, especially at a glance.It would be useful to change the colouring/shading gradient, for example, grey out the text, for…
64 votes -
Display logic rules should work on Primo users NOT logged in
Display logic rules currently only work if a user logs in Primo. Also, the rules only work to hide a service (not show a service). Also, Primo New UI does not allow forcing users to log in.
So, we have a scenario where we want CCC Get It Now articles to display only for our Faculty user group. However, the article links are displaying to everyone (guest) - until the user logs in and then the links are hidden for everyone except our faculty. Because everyone starts out in Primo as guest, this defeats the purpose of the rule.
Another…
64 votes -
Vendor Interface > Contact Information > Email addresses
The default display for Vendor Interface > Contact Information > Email addresses, does not include an option to display the "description" field on the main page. The fields available for display are: Preferred, email address, created by, creation date, and type.
Since most correspondence with vendors and sales representatives happen by email now, it would be useful to be able to see the description on the main page without having to click on .... and Edit for each email listed to see who is the correct contact.
Some email addresses do not contain the person's full name, and if you…64 votes -
Update 863/864/865 when items are withdrawn
There is a crucial step missing in the Automatic Generation of the Summary Holdings Statement Based on Items process. The process is documented here:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/020Navigating_the_MD_Editor_Page?uxp=true#Automatic_Generation_of_the_Summary_Holdings_Statement_Based_on_ItemsWhen items which are linked to the Holdings record are withdrawn, there is no process to update the Holdings record 863/864/865 fields to create an updated 866/867/868 field. When items are withdrawn, the user has to manually edit the Holdings records.
Since the creation of the 863/864/865 field is now automated based on received items being linked to the holdings record, there is a need for the 863/864/865 to be automatically re-created when the linked…
64 votes -
Hide ‘edit’ option from My Library Card > Personal Details for specific user groups only
In Alma you can choose to hide the "Edit" option from the 'Personal Details' under 'My Library Card' for ALL your users by changing the parameter key 'primopatroninfo_updatable' to N
This works fine if all your users are set up as external users who automatically gets their contact information updated from a system outside Alma. But if you set up your students as external users and public users as internal users you will have to choose between letting the students update contact information that will be wiped out next time data is loaded in to Alma or not…
64 votes -
A "kill switch" for General System Administrators to immediately disconnect individual Alma users
Use case: A library employee (student or staff) responds to a phishing text message by providing their Single Sign-On (SSO) credentials; SSO is used on our campus for Alma authentication. I want to (1) disable all the roles on the library employee's account except for Patron; (2) disconnect the employee if he/she/they/* has an active session in Alma; and (3) be notified with the IP address of the originating computer if he/she/they/* attempts to log in again. I would like to accomplish both #1 and #2 by checking a box ("Disable roles") and moving a slider ("Disconnect user"), WITHOUT having…
64 votes -
Allow access to "Roles Privileges" configuration for General System Administrator
Allow access to "Roles Privileges" configuration for General System Administrator
Ex Libris staff have the ability to remove specific privileges from Alma roles via the "Roles Privileges" configuration (User Management - Roles and Registration - Roles Privileges)
Since roles in Alma are not very fine-grained, and roles often grant access to groups of privileges that shouldn't necessarily be granted as a set, it would be very helpful for customers to have access to the "Roles Privileges" configuration.
Ideally we would have the ability to make edits ourselves, but Read-Only access would also be valuable, because it would allow us to:
- …
64 votes -
Allow Alma users to choose the match routine when using the ‘Link to Community’ tool to link portfolios to a community zone collection.
The ‘Link to Community’ match routine for matching local portfolios to the CZ is too restrictive. We would like to be able to use our local bibliographic records and have them link to portfolios in the CZ, however, the match rate is dependent on what metadata is available in the CZ records, which are often brief and do not contain the ISSN/ISBN match point that Ex Libris has selected for that collection in the CZ.
Alma users should be able to choose the match routine when using the ‘Link to Community’ tool, similar to how we can choose the match…64 votes -
Add Electronic Service Information Update Job
Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.
Job Name: Change Electronic service information
Job Description: Update Electronic service information for a set of Electronic services
Job Content Type: Electronic Service
Job Type: Information UpdateUse Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time…
64 votes -
The line separator in Analytics outputs is normally a semicolon, but should not be ambiguous
In various exports from Analytics, it was noticed that the characters present in Alma are output as follows:
- sharp bracket < present in Alma is put out by Analytics as & l t ;
- sharp bracket > in the Alma (bibliographic data) material is put out by Analytics as & g t ;
- ampersand & as & a m p ;
This is likely due to HTML being used as the export format in Analytics. However, for the further processing of large amounts of data, it is disruptive that a semicolon is used for coding here. The semicolon appears both…
64 votes
- Don't see your idea?