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.
579 results found
-
Z39.5 MARC field filtering
Alma's current settings on integration profile do not have the functionality to prevent exposure of specific MARC field. It will create problem if some of the MARC content are licensed and are not supposed to be shared easily.
134 votes -
Automatic orders claiming
At the moment Alma only sends one claim request to the vendor. If the ordered item is still not received, staff need to follow up and re-claim manually; usually a number of times.
We would like to see claim cycle functionality in Alma so that we can configure follow-up claims based on a set interval per vendor, as well as a maximum number of claims to be sent before the order is automatically cancelled and the vendor automatically notified. It would also be useful to be able to see the history of claims for an order, and be able to…
130 votesDear community,
As described in a comment below, In December 2019 Alma introduced the Reclaim functionality which is set to address the need described in this idea. See https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/050Purchasing/Receiving_Material/Processing_Claims for more details.
The concept of limiting the number of reclaims sent before canceling the order was not added as part of this enhancement, it is recommended to open a new dedicated idea exchange to validate the need and see that the community supports this.
Thanks,
Tamar Fuches
Alma product team
-
Implement Just in Time (JIT) SAML provisioning
With Just-in-Time provisioning, you can use a SAML assertion to create users on the fly the first time they try to log in. This eliminates the need to create user accounts in advance from a SIS or FTP file download. Only an authenticated user would be created once validated through the login process. JIT provisioning is common in larger systems like SalesForce.
129 votesYou can now create an Alma user when a user is authenticated with SAML but does not have an existing Alma user. This eliminates the need to create user accounts in advance from a SIS or FTP file download. This option is supported for Primo VE.
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes#SAML_User_Creation -
Advanced search option for Users search
Create an advanced search for Users search, just like for physical titles / items. In this search, make it possible to search (for instance) users with specific roles or job categories, identifiers starting with specific prefixes, users with different kinds of blocks, users with outstanding loans or requests, etc, and the possibility to combine these.
128 votesAs of July release you can search for users by combining search criteria, using Alma advanced search. This is available only to users with the roles and privileges to search for users.
For more information please see
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
Print without the cloud and reduce failure points for printing Pull Slips
The process for printing Pull Slips has multiple failure points. Suggestion: Use the Print Slip Report as the data source for a mail merged Word document Pull Slip.
Creating email pull slips is too reliant on multiple systems working at all times. All of the required systems (servers, printers, scripts…) are potential failure points. These failure points often require staff from other departments to resolve. When there is a failure at any of the many points, the result is an inability to process Pull Slips through the normal workflows.
Suggestion: (1) Execute Print Slip Report, (2) Open Word document Pull…
127 votes -
Provide patrons notification of reasons for failure to renew a loan
Please note: this idea is not ours originally. We voted for this as an institution as part of the first round of NERS 2018, where it was Req ID 5782. I noticed that it isn't in Ideas Exchange now (or at least I don't think so).
Quoting the original description: 'We would like it to be possible to notify users when they have an item on loan that cannot be renewed, and to explain the reason to them so as to avoid confusion to patrons. Reasons may include: - because it is requested, - the patron has reached their expiry…
127 votesThe Courtesy Notices now includes the last renew status and date in its XML. This can be used to notify the patron why the last automatic renew failed.
For more information please see Alma December release notes. -
Adding more scheduling options for emailing Scheduled Reports (Alma Analytics Objects)
Currently, there are limited scheduling options for emailing Scheduled Reports (Alma Analytics Object area). Many of our users need reports delivered on the 1st of each month in order to capture the previous month's data. The only option right now somewhat close to that is delivery on the 2nd of each month. This doesn't work for us because it adds the first day's worth of data from the next month to the previous month. I propose adding delivery options for the 1st of each month. Better yet - how about offering a drop-down list where users can choose a certain…
124 votesDear Colleagues,
We have added a new and flexible scheduling Module in the Analytics UI. With it, it is possible to schedule any day or time and define its recorrance level (wether monthly/daily or hourly). In addition we have added the ability to schedule Analytics links as well as attachments (links will work for authorized users) . We encourage Analytics admins who did not switch on the new analytics UI yet, to do so and try the new UI and its new scheduling capabilities.
-
Include access information as part of the data that are published from Alma to Primo for Alma-D records
We would like to have the possibility to include access information in the data that are published from Alma to Primo for Alma-D records (per representation).
Use case:
At this moment, we make the digitized content of all institutions searchable in the views of all institutions of the network.
This is can be very useful for items that are freely available, including digitized heritage.
However, it is inconvenient and confusing for items with restricted access, when the content can only be viewed by users of the institution.
Yet the availability indication for these items is "Online access", because we cannot…124 votesAccess right information is now published to Primo , for more information please see:
-
Make it possible to delete a NZ bib record from the Institution tab for records that are CZ in origin (consortial environment)
It is possible to delete a Network Zone bib record from one's institution tab, provided that (1) it is a record created within the Network Zone and (2) it is not "Held by" other institution from the network. However, when the record is originally from the Community Zone deleting it is not possible. Even when it is not "Held by" any other institution from the network. This results in a multitude of Community Zone bib records to which there are no holdings in the network. Needless to say, it will be a great asset if institutions can actually delete them.
122 votesNow records that are originated from the Community Zone and used by either the Institution or the Network can be deleted.
-
Show completed requests in RS without having to enter search term
At the moment, completed requests are hidden from records and have to be searched by entering matching search terms. Our ILL staffs are finding facets appearing left to active requests records very helpful, as they reportedly spare staff members' effort and time to enter search terms and go through all the unwanted information. This applies to completed requests as well, as the staffs have to revisit them every now and then. It would be greatly appreciated if completed request records could be seen, limited, searched and browsed just like active requests, without having to enter search terms.
120 votesCompleted Resource Sharing requests are not displayed without needing to search them explicitly.
-
Add the possibility to open more than one record in MD editor
On a search result list, I can click on 'edit' to open a record in MD editor. If I want to open more than one record in MD editor, I need to click 'edit' for the first record, click 'Back' on the MD editor screen, click 'edit' of the next record an so forth.
I would be nice if more than one record could be selected to open in MD editor.119 votes -
Delete multiple MARC fields after they are highlighted / selected in Metadata Editor
At the moment, you can select multiple MARC fields when you hold down CTRL, as can be seen by the fields highlighted in BLUE in the attached screenshot.
However, when one attempts to remove them (CTRL+F6), only the first field is deleted.
This is a request to delete all highlighted fields
117 votes -
Usage statistics Missing Data page should use different symbols
Currently in the Missing Data page, Alma uses the same red symbol to indicate Data not available for that month. When we investigated, some of them had error in connection so we had to contact the vendors to fix the problems. However, some of them actually worked fine, only there were no usage data available for the requested dates.
I am requesting ExL to use a different symbol to indicate no usage, otherwise everything else is fine. So at a glance at the Missing data page, we could easily explain which months have no usage, so nothing needs to be…
117 votesAs of March release the SUSHI harvest process contains new performance enhancements. Additionally, the Missing Data tab has been renamed to the Monthly Usage Data tab. The errors on this tab are now further refined to help you troubleshoot connection issues. The yellow icon indicates that the connection to the vendor was successful, but the vendor did not send any data. While the red icon indicates that the the vendor connection attempt was unsuccessful. The green icon indicates, as previously, that the usage report file was successfully uploaded.
For more information please see Alma Release Notes https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
update collections job
Allow Information Update for Electronic Collections. Sometimes, we need to add a public note to all of the collections that are tied to a specific interface, due to scheduled maintenance, or unexpected downtime. It would be great if we could add/remove these notes with a job. Some large providers, like Ebsco, Proquest, or Wiley can have over 15 collections we have to manually edit, which is a big time drain
115 votesAlma December release includes an enhancment to cloud app application by the name of e collection quick update which provides an easy way to update of supported fields in a set of e-collections.
(you can read more about here:
https://github.com/ExLibrisGroup/alma-e-collection-quick-update/wiki/Help)Now the cloudAPP includes additional fields:
1. Public description
2. "Activate new portfolios associated with service automatically? "
3. Service temporarily unavailable message
4. Service unavailability reason
5. Service unavailable message as of date
6. Internal description -
When using Scan in Items, provide a pop-up window when there is a hold on an item.
When we process returned materials from resource sharing partners we use Scan in Items. If there is a hold on an item it only displays the message on the screen, and does not provide a pop-up alert. It would seem useful to provide a similar pop-up like you get when processing items with Return Items.
114 votesAs of March release you can configure how pop-up messages will display in the Scan In Interface. All messages can be configured to appear as a pop-up message, a feedback message, or to not appear at all. This is defined in the Scan In Messages Configuration table. Additionally, a yellow icon is added to the list of scanned items for patron request of types Booking Requests, Physical Requests, and Patron Digitization Requests to draw the scanning operator’s attention that some items have a patron request associated with them.
An additional informational message was added to the Scan Items page for lost items which were returned (Lost status removed). This message appears as a feedback message and can be configured similar to all other messages in the Scan In interface to appear as a pop-up message, a feedback message, or to not appear at all.
For more information please see Alma… -
Change the “No requesting from available holding” functionality (check item availability)
Circulation desk librarians want to make a distinction between items and holdings that are (not) available for requesting purposes.
Patrons shouldn't be able to request items that are available, but they should be able to request items that are NOT available. In our case our items are created under the same holding, and Alma checks the holding for availability, not the item.
Use case: 1 holding with 3 items (with the same item description): 2 items are loanable, 1 item should stay in the shelves for consulting.
When the 2 loanable items are on loan and the 3rd one being…114 votesHi,
In the July 2017 release the following was done:
The calculation of the fulfillment unit On Shelf Request Policy was changed for serial titles. For each item, if there are available items that have the same description and are requestable, then the request link will be suppressed. If the available items are not requestable then the request link will not be suppressed.
Thank you for this very helpful suggestion !
Moshe
-
Make all PNX elements referable in Template URLs (of General E-Services) and Dynamic URLs
In the Template URL of a General E-Service and in the Dynamic URL of a given collection of e-resources you can currently refer to any piece of metadata that Alma has included in the Context Object ("CTO"). The attributes of the Context Object are based on the OpenURL 1.0 standard but while this standard provides slots to convey any kind of locally scoped metadata (e.g. local identifiers) as well as globally scoped metadata (e.g. ISBN, ISSN, OCN, DOI) and descriptive metadata (e.g. author name, book title, journal title, article title) there is currently no way to let Alma include locally…
113 votes -
Indicators for e-collection status when viewing portfolios/titles in CZ
Workflow would be greatly improved with an indicator for the activation status of e-collection when viewing the list of portfolios for a title in the CZ. This would be similar to the green dot display currently in SFX. Currently in the Alma CZ one is unable to detect if an e-collection is being used or not when looking at portfolios/titles. This would prevent an inactive e-collection being turned on by mistake.
112 votesAs part of Alma June release: Icon indicators that show the status of electronic collections (activated/not activated, available/not available) were added to the Community and Network tabs in the Electronic portfolios and Electronic titles search results.
for more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes -
Ability to log 2 sets of dates on electronic portfolios - Perpetual and Current Access
Most publisher packages only allow perpetual access for subscribed years, post-cancellation, but they give you access to a much larger set of dates during your active subscription. For example, many of our Wiley titles have access back to 1997, but our perpetual access does not begin until 2003. If we could select both perpetual and current access for a title, and have the ability to log both sets of dates, that would be very helpful. Ideally, we would like to use this to do a broad overlap analysis between our print and perpetual electronic holdings.
112 votesIdea was implemented as part of August release.
When a resource has both current and perpetual access, there is now an available access type combination option (Current and perpetual) for electronic collections and portfolios. This option is available in the Electronic Collection Editor and the Electronic Portfolio Editor, and supported by the portfolio loader and Excel exports using the extended export option. -
batch job de/activation of proxy enabled setting at service level
You can de/activate the proxy setting in batch for portfolios, by using the "Change electronic portfolio information" job on a set. Unfortunately you cannot at this stage do the same on Services or Collections.
I have approximately 30 services that I would like to change EZproxy enabled from YES to NO. I do not want to run a batch job on the portfolios - I want the proxy to be determined at service level and the portfolios to inherit the settings. It would be helpful if this could be done as a batch job rather than editing each service manually.
112 votesHello Community,
Thanks for raising this idea.
This Idea exchange was developed and is available in Alma.
You can read about it in the Release notes:
For updating the Electronic Service Proxy Enables (Yes/No) you can now use the following flow:
Run a job -> Information Update -> 'Change Electronic Collection information' job -> Select a set of collection/s -> open the section named 'Change Set Service linking information' -> Proxy enabled (Yes/No) (see attached Electronic Service Proxy.png)
For updating the Electronic Collection Proxy Enables (Yes/No) you can now use the following flow:
Run a job -> 'Information Update -> Change Electronic Collection information' job -> Select a set of collection/s -> Open the section named 'Change Electronic Collection information' -> Set Proxy enabled (Yes/No) (see attached Electronic Collection Proxy.png)
Thanks,
Uri Beladev | Product owner
- Don't see your idea?