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.
- or
No existing idea results
- ~ No ideas found ~
1692 results found
-
Advanced Search for Citations
Enable Advanced Search for Citations along with the ability to save the Advanced Search results as a set.
As we use Leganto, the number of citations in Alma continues to increase. It is becoming increasingly difficult to wade through these citations to find the ones that need attention.
For example, we are using 3 different tags to indicate if a book needs to be temporarily moved to the course reserves collection/location of the library. In this example, we frequently need to view books with these 3 tags at the same time but currently there is no way to do this in Alma. We'd also like to be able to view citations for courses for the upcoming semester with different tags/alerts but again currently there is no way to do this in Alma.
I'd like to ask that the Advanced Search option that would include searching by citation tags be implemented. I'd also like to be able to save the query as a logical set so that people can use it as a shortcut to get to the list of citations that need attention.
Enable Advanced Search for Citations along with the ability to save the Advanced Search results as a set.
As we use Leganto, the number of citations in Alma continues to increase. It is becoming increasingly difficult to wade through these citations to find the ones that need attention.
For example, we are using 3 different tags to indicate if a book needs to be temporarily moved to the course reserves collection/location of the library. In this example, we frequently need to view books with these 3 tags at the same time but currently there is no way to do this…
9 votes -
Allow to change the default value of “Item owner” field to “Any Institution” when lending items
When lending items, the default value of the field “Item owner” is “My Institution“. It should be possible to decide the default value of this field, “Any Institution” for example. This would save many clicks for people working at desk.
15 votes -
More column in "Waiting For Approval Invoices"-View
We would be pleased if the fields
Invoice reference #
Prepaid
Internal copy
VAT Type
should be integrated into the "Waiting For Approval Invoices" view11 votes -
Ability to pull the"Unassigned tab" data in Analytics
It will be great to view the 'UnAssigned Tab' data in Analytics for for 'Waiting for Payment' invoices
3 votes -
merge vendor records
Most libraries have multiple records for the same vendor. This is often the result of migrated records from a previous system, but can also occur because of changes in library workflows or even the acquisition of one company by another.
Currently, the only option is to choose one vendor record going forward and stop using the other vendor records. However, this creates extra work for libraries, such as changing the vendor on purchase order lines and including multiple vendors when running reports on historical expenditures. The ability to merge vendor records would solve these difficulties.
94 votes -
Alma: Quick login/user switching on shared workstations
Staff working service desks often use shared workstations that aren't their primary workstation to serve patrons. Can a function be added to allow staff to switch users quickly to maintain good security practices while allowing for prompt service?
Perhaps a scan/swipe ID plus PIN like in restaurant service paired with an adjustable quick time-out that can be workstation specific. Alternatively, maybe a fulfillment specific application can be developed for general fulfillment activities only on shared workstations (check out/in, holds, etc.). Thanks.
6 votes -
when importing, create portfolio links *after* Process / Normalization Rules ( NR ) are applied (and not before as it is now)
Right now static links in portfolios can be derived form 856 tags in imported MARC records.
Sometimes however we need to manipulate those links to fit the needs of our institution. We could do that easily with a process based on a Normalization Rule (NR) defined in the import profile. But this doesn't work, since our changes to 856 are not considered by Alma when creating the Static links in Portfolios. Our best guess is that static links are created before NR/process are applied and not after. That's a pity.
It would be great if static links were extracted from 856 $u tags after the NR/process manipulation.Thank you and best regards,
Luigi Sicilianowhen importing, create portfolio links after NR are applied and not before
Right now static links in portfolios can be derived form 856 tags in imported MARC records.
Sometimes however we need to manipulate those links to fit the needs of our institution. We could do that easily with a process based on a Normalization Rule (NR) defined in the import profile. But this doesn't work, since our changes to 856 are not considered by Alma when creating the Static links in Portfolios. Our best guess is that static links are created before NR/process are applied and not after. That's a pity.
It would be great if static links were extracted from…29 votes -
Letter for purchase requests initially approved and finally canceled
Sometimes it happens that a user's purchase request is initially approved by the acquisitions staff and sent to the vendor, but sometimes it ends up being canceled for some reason.
Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Then it will be manually canceled.
We request the creation of a letter in which the user is informed of this circumstance. Together with this, we request that a new check be added in the "Interested Users" section of the POL that allows activating the sending of this letter to all interested users of that POL.Sometimes it happens that a user's purchase request is initially approved by the acquisitions staff and sent to the vendor, but sometimes it ends up being canceled for some reason.
Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Then it will be manually canceled.
We request the creation of a letter in which the user is informed of this circumstance. Together with this, we request that…0 votes -
Has Local Information on CZ Updates Task List shows up even when Global Coverage is being utilized instead
If a portfolio is using global coverage information, but has local coverage information remaining, the portfolio shows up in the CZ Updates Task List under "Has Local Information" when updates come in, even though local coverage is not being utilized. If local coverage is not selected, it would make more sense for it not to show up in the list since it's not being utilized and therefore does not really matter at that point.
1 vote -
Pop-up note to alert operator when checking out item with "0 Day Loan" item policy
When checking out an item with a "0 Day Loan" policy, operator is not alerted that the item is due that day and consequently patrons are not being informed at the time they check out the item. This can lead to overdue items and overdue fees charged in error to patron. A pop-up alert would require operator to acknowledge the note before completing the loan, also alerting operator that item should be assessed for item policy correction.
Possible message: This item has an Item Policy of "0 Day Loan." Do you want to proceed? <options: CANCEL or OK>
27 votes -
Make the current publication location discoverable in Analytics
When a record contains both a 260 and 264 field, Analytics will only display the publication location from the 260 field, which often isn't the current publisher's location if a publisher change has occurred. This is also inconsistent with how the publisher field works. The publisher field returns all publishers, separated by a semicolon, but publication place only returns the original publisher's location. Not returning all publication locations makes it difficult to do maintenance on the 260, 264, or 008 country code fields. It also doesn't allow you to accurately record collection development statistics by current country of publication.
6 votes -
Add a Delete button for portfolios in the Community Zone Updates Task List
Could a "Delete" button be added to the set of available options when reviewing portfolios in the CZ Updates Task List? There are options to Test Access and Edit the portfolio, but in order to delete a portfolio you must leave the list and do a separate search. It would be much more efficient if there was an option to delete from within the list.
11 votes -
Differentiate “regular” Hold Request and Interested User Request or Change “Interested User Check” Order
Because Alma does not have the granularity to separate an Interested User request and a regular hold request, our Interested User hold process does not work.
When the “Non-Requestable Processes Fulfillment Unit Rule or Change Order” is configured to prevent “in process” items from being requestable, any items that have an Interested User that are in our Technical Services Work Order are treated as “in process” and therefore, the interested user request is blocked. While we do not want most “In Process” items to be requestable, we do want our Interested User requests to be fulfilled.
Because of this configuration, the following workflow does not allow Interested User hold to process: When the item is marked “Done” from the Technical Services workflow, two actions occur (per Ex Libris): the first action is checking for an interested user and an attempt to create a hold request. The Second is to clear the “in process” type and move the item to the next process type. Because of the order of operations, the item is still “In Process” when Alma checks for Interested Users, so the hold is not allowed, due to our Fulfillment Unit Rule.
If there can be a way to either differentiate between a “regular” hold request and one from an interested user, perhaps that granularity can be applied so that the Interested User hold function can work without changing our Fulfillment Rule. Or, if the Interested User check and hold request can be made after the item is cleared from the “in process” type, then the hold would apply.
Because Alma does not have the granularity to separate an Interested User request and a regular hold request, our Interested User hold process does not work.
When the “Non-Requestable Processes Fulfillment Unit Rule or Change Order” is configured to prevent “in process” items from being requestable, any items that have an Interested User that are in our Technical Services Work Order are treated as “in process” and therefore, the interested user request is blocked. While we do not want most “In Process” items to be requestable, we do want our Interested User requests to…
59 votes -
Enable the ability to associate vendors
Similar to associating POLs, it could be useful if it were possible to associate/link vendors to each other. It would enable organizing individual vendors (mostly access providers) under broader vendors (billing agents, IP Registry, etc) and consortia.
5 votes -
Have searchable Notes fields in vendor records
It would be great if the data in the Notes tab of vendors records could be searchable - possibly as an Advanced Vendor search, or as part of a keyword search, or even within Analytics. Some data from Voyager's 'alternative vendor name' field has been migrated into the notes and it would be useful to be able to search on this.
35 votes -
Overdue notifications to be sent also on days after closed days
We noticed that if closed days are configured, and a closed day is between the due date of a loan and the planned day on which the first reminder should be sent, the job does not generate a notification on that day but waits until the next one.
This leads to misunderstanding on the patrons side, because the grace period is not always identical and can vary depending on possible closed days.
We described the issue in case nr. 05301818 (old SF nr.: 00953477) and were told that this is the expected behaviour. The Product manager decided that when there's a closed day between the job run and the due date, due to the request for not sending emails on closed days, it will check another extra day.
We would like IZs to be allowed to choose whether they want this extra day or not, by adding e.g. some parameter in the overdues configuration.We noticed that if closed days are configured, and a closed day is between the due date of a loan and the planned day on which the first reminder should be sent, the job does not generate a notification on that day but waits until the next one.
This leads to misunderstanding on the patrons side, because the grace period is not always identical and can vary depending on possible closed days.
We described the issue in case nr. 05301818 (old SF nr.: 00953477) and were told that this is the expected behaviour. The Product manager decided that when there's…131 votes -
Improve Job "Change Physical items information" parameter "Item call number"
Our "Item call number" are made up of two parts, one alphabetical and the other numerical. We need to be able to modify the alphabetic part in a group of items, and keep the numerical part exactly the same.
98 votes -
When a hold expires, have them display in the task list
In the same way that requests show in the task list, it would be helpful that when the hold is expired that it will also show in the task list. People would see on their desktop if an item needs to be shelved or returned to a campus library, instead of remember to check the Expire Hold shelf.
4 votes -
When a hold expires, have them display in the task list
In the same way that requests show in the task list, it would be helpful that when the hold is expired that it will also show in the task list. People would see on their desktop if an item needs to be shelved or returned to a campus library, instead of remember to check the Expire Hold shelf.
9 votes -
Allow lending RS locate process to fail if it cannot determine which volume from a multi-volume set is being requested
Currently, Alma's lending locate process will automatically select a single volume from a multi-volume set if it can't determine which specific volume is being requested in a title level lending reqeust. It often selects the incorrect volume, and that error is rarely caught before the incorrect volume arrives at the borrowing library. It would be very helpful if the lending locate process failed in these scenarios rather. That would give library staff the opportunity to manually review the reqeust and select the correct volume.
5 votes
- Don't see your idea?