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 ~
1826 results found
-
Add the ability to batch change the expiry date of items on the hold shelf
It can be useful to manipulate the Expiry date of items on the hold shelf. However you have to do this per item. It would be good to be able to batch update all items due to expire in a given period to a new value.
176 votes -
Allow batch deletion of user notes
It's possible to add notes to user records in batch using the "Update/Notify Users" job on a set of users. It would be helpful if we could also batch delete notes on user records.
There are occasions when we have subsets of users who receive special permissions to check out subsets of materials (e.g. students in a specific class who are the only people allowed to use specific equipment or reserve items, collections/materials where we require a signed agreement on file from the user to allow access). In these situations, we add notes to the user record to indicate whether a specific user may use a specific physical resource during a set period of time, such as an academic term. We would like to be able to delete these notes in batch, rather than having to manually edit individual user records-- of which there may be several hundred-- to remove the note that is no longer applicable.
Ideally, the job would allow operators to delete only those user notes that contain text specified by the operator. (e.g. Delete user notes that contain the phrase "Fall 2016" or delete user notes that contain the word "approved")
It's possible to add notes to user records in batch using the "Update/Notify Users" job on a set of users. It would be helpful if we could also batch delete notes on user records.
There are occasions when we have subsets of users who receive special permissions to check out subsets of materials (e.g. students in a specific class who are the only people allowed to use specific equipment or reserve items, collections/materials where we require a signed agreement on file from the user to allow access). In these situations, we add notes to the user record to indicate whether…
178 votes -
New role for Manage Import Profiles
Currently users must have a Cat Admin role or Gen Sys Admin role to be able to Manage Import Profiles (change/add profiles). This also gives them access to the Configuration area of Alma. There should be a role to permit users to Manage Import Profiles that does NOT also give them access to the Alma configuration area. Access to the Alma configuration menu should be separate from the ability to Manage Import Profiles.
178 votes -
May release : deletion of empty holdings.
Dear all
the May release introduced a change concerning the deletion of empty holdings:The 'Delete Holdings' link in the 'List of Holdings' page, which was formerly visible to users with the 'Physical Inventory Operator' role, is now visible only to users who have the 'Physical Inventory Operator Extended' role.
This change is a problem because not all the operators can have the physical Inventory Operator Extended role: this role allows operators to delete copies and it is quite dangerous.
It would be better for us that operators with the physical inventory role keep the permission to move copies from an holding to another and then delete the empty holding. (let’s think of a correction of call numbers)
We propose the creation of a second Physical Inventory Operators’ role :
One without the possibility of delete empty holdings
and another one with the possibility of delete them.
So that, according to the job that operators have to do, they could keep doing the work deleting empty holdingsDear all
the May release introduced a change concerning the deletion of empty holdings:The 'Delete Holdings' link in the 'List of Holdings' page, which was formerly visible to users with the 'Physical Inventory Operator' role, is now visible only to users who have the 'Physical Inventory Operator Extended' role.
This change is a problem because not all the operators can have the physical Inventory Operator Extended role: this role allows operators to delete copies and it is quite dangerous.
It would be better for us that operators with the physical inventory role keep the permission to move copies from…177 votes -
Job for copying the configuration from the production environment into the Standard Sandbox
Making testing and training in an Alma Standard Sandbox based on Ex Libris provided configuration is very difficult since this configuration may be very different from the one in the customer's production environment.
Currently Ex Libris is offering two types of Sandboxes for Alma:
(1) "Standard" - by default included in Alma subscription pricing. This sandbox contains Ex Libris provided data and configuration
(2) "Premium" – for addition subscription fee – this sandbox includes a full copy of the customer's data and configurationRefresh of the Alma sandbox environment is possible up to once a quarter, upon request. In the case of a Premium Sandbox, Ex Libris updates the customer’s Premium Sandbox with the most recent data and configuration copied from the production environment. In the case of Standard Sandbox, Ex Libris resets the Sandbox data and configuration to the original copy.
We would like Ex Libris to propose an improved Standard Sandbox so that customers can export the configuration from the production environment with a job in order to import it in the Standard Sandbox. This Standard Sandbox would still contain Ex Libris provided data, only configuration would be copied from prod to sandbox. A Standard sandbox containing the customer's configuration would be very useful for staff training, testing of setup scenarios, new enhancements, integration with other systems, etc. This service is already proposed for Primo!
Making testing and training in an Alma Standard Sandbox based on Ex Libris provided configuration is very difficult since this configuration may be very different from the one in the customer's production environment.
Currently Ex Libris is offering two types of Sandboxes for Alma:
(1) "Standard" - by default included in Alma subscription pricing. This sandbox contains Ex Libris provided data and configuration
(2) "Premium" – for addition subscription fee – this sandbox includes a full copy of the customer's data and configurationRefresh of the Alma sandbox environment is possible up to once a quarter, upon request. In the…
176 votes -
sound alert for pop-up windows
A sound alert to accompany a pop-up window would be very helpful. We find that our student workers often fail to see important pop-up notes when they are checking out or returning materials. A distinct sound would help immeasurably!
174 votesIt will be possible to configure an audio alert for pop up messages that appear at the Patron Services WB or at the Scan In Interface.
-
Enable bulk due date changes based on a set of items listed by barcode
We've had occasions where it would have been useful to be able to create a set of items, for example, in Alma Analytics. Then to take that set of items, e.g. a CSV or Excel file listing the barcodes, and then to update the due dates of all those items, to a new fixed value.
This is similar to the current Bulk Due Date Change functionality, but with the addition of uploading a list of items to change.
Regards,
Ciaran
The University of Manchester Library
172 votes -
controlled vocabulary list upload
Hi,
Instead of create term by term when working with controlled vocabulary, enable the option of upload an excel file or any csv file that will do that.
172 votes -
Claimed returned option for Lost items
In our previous system, with one click we were able to change items to Claimed Returned status, no matter what their current status was. one click and it was done.
But in Alma, for some reason, this is not possible once the item has been declared Lost. One has to go through a long and convoluted process creating a file and saving it then creating a set and saving it then running a job on the set. This involves three pages of instructional documentation and about 15 minutes of staff time every day.
We often have items claimed returned when they have automatically gone to Lost status, and it would be really useful to have the Claimed returned option appear as a choice in the elipsis also when the item is Lost.In our previous system, with one click we were able to change items to Claimed Returned status, no matter what their current status was. one click and it was done.
But in Alma, for some reason, this is not possible once the item has been declared Lost. One has to go through a long and convoluted process creating a file and saving it then creating a set and saving it then running a job on the set. This involves three pages of instructional documentation and about 15 minutes of staff time every day.
We often have items claimed returned when…168 votesThe 'Claimed Returned' action will be available for lost loans. It will change the loan status to 'claimed returned'.
A customer parameter will determine whether the change to claimed returned should trigger a 'Find Item' action (and refund the lost item fees) + change to 'claim return', or only change to 'claim return'.
-
Fulfillment: Physical item recall: option to recall more than one copy
Currently in Alma when a request is placed on a title where there are 10 copies all out on loan, and none available, a single real-time recall notification is sent to the patron who has the oldest loan, changing their loan status to 'recalled'. The 9 other patrons who have a copy are not made aware of the potential demand for the item at that time.
For the case where there are many copies of a title, the patron requesting the title could be better served if we were to recall more than one item. For example, we might say: up to 3 copies - recall 1, 4-6 copies - recall 2, 7-9 copies - recall 3, etc, etc
This proposal seeks to enhance how Alma's request mechanism handles recall of loans, with potentially more than one item being recalled, perhaps in proportion to the total number of copies.
Currently in Alma when a request is placed on a title where there are 10 copies all out on loan, and none available, a single real-time recall notification is sent to the patron who has the oldest loan, changing their loan status to 'recalled'. The 9 other patrons who have a copy are not made aware of the potential demand for the item at that time.
For the case where there are many copies of a title, the patron requesting the title could be better served if we were to recall more than one item. For example, we might say:…
169 votes -
More easily edit/delete POL templates
We would like to be able to more easily update our POL templates. As far as I can tell, you need to create a new order, make adjustments in the POL, and then Save As Template - overwriting the old template. There should be an easier process.
166 votes -
delete users with expired purge date daily with scheduled job
Now deleting users with an expired pruge date has to be done manually and cannot be scheduled with a job. We would like to have a job that can delete these records more easy than now.
ExLibris came with this answer: Alma product management is aware of this issue and most likely scheduling will be possible in future Alma versions. However, there is no specific timeline for this solution, yet. Once the fix is released, information will be included in the relevant release notes and documentation.
It would be an efficiënt addidition in the ALMA jobs.
167 votesYes, it will be possible to schedule the purge users job.
-
Pop-up note when patron has something on the hold shelf
When scanning the patron's barcode or searching for a patron in Manage Patron Services, can a pop-up notification be configured to alert staff that there are items held for the patron on the hold shelf?
Currently, you have to look at the User Notes section on the right hand corner of the screen and it's gray text that does not draw attention. You can also look in the request tab if it is dog-eared but it will display all requests statuses; not just when an item is on shelf ready for pick up.
Since patrons don't always check their email and let staff know that there is an item at the library to be picked up- staff can miss items that are on the hold shelf to check out to patrons when they are visiting to borrow other materials. An alert to check the hold shelf would be very helpful to staff. Our older ILS, Aleph had this so I don't understand why Alma does not.
When scanning the patron's barcode or searching for a patron in Manage Patron Services, can a pop-up notification be configured to alert staff that there are items held for the patron on the hold shelf?
Currently, you have to look at the User Notes section on the right hand corner of the screen and it's gray text that does not draw attention. You can also look in the request tab if it is dog-eared but it will display all requests statuses; not just when an item is on shelf ready for pick up.
Since patrons don't always check their email…
167 votes -
Interested In Letter – improvement to the usability
When working on a purchase request, you can tick a box if you would like to notify the patron upon receiving/activation, and upon cancellation.
OTB the Interested In Letter sends the same message when the request is received or cancelled. The letter in use does not seem designed for the cancellation message.
This creates a discrepancy between what we choose to notify the patron of, and what we are actually able to communicate.
Since we neither have access to the message table used as an input to this letter, or the opportunity to differentiate by using labels, we are forced to hard code most of the editing. This applies to both different messages, and different languages. This is tiresome work, and hard to maintain.
We would like a subject line that accurately reflects the content of the email (e.g., "Library Order Cancelled" or “Item received/activated”).
The same issue applies for the message to the patron (label = Youwerespecify). We need to differ between each possible use of the letter.
One solution would be to add labels in the table. For instance:
Subjectactivated
Subjectreceived
Subject_cancelledIn addition to the Youwerespecify label, we would also like:
Messageactivated
Messagereceived
Message_cancelledThe XSL must then be enriched to integrate these new labels.
A labels table designed for all three scenarios would also make it easier to edit all languages in use.
When working on a purchase request, you can tick a box if you would like to notify the patron upon receiving/activation, and upon cancellation.
OTB the Interested In Letter sends the same message when the request is received or cancelled. The letter in use does not seem designed for the cancellation message.
This creates a discrepancy between what we choose to notify the patron of, and what we are actually able to communicate.
Since we neither have access to the message table used as an input to this letter, or the opportunity to differentiate by using labels, we are forced…
167 votes -
It would be helpful if there were an option to "print MARC record" within the MD editor and from the Repository Search.
We sometimes have need of a hard copy of the MARC record for tracking certain workflows. One such example is for making notes about title changes and tracking them across several records. It would be nice if there was a "print full record" option, both in the MD editor and in the repository hit list. Right now, we need to either do print screens or do a screen capture and print from that. Thank you!
165 votes -
Ability to create a chosen quantity of predictions
As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.
It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at times to find the item you are looking for. Also, due to variations in publishing schedules and the general inconsistent nature of periodicals, creating weekly predictions a year in advance often results in inaccurate predictions which will need to be modified later.
As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.
It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at…
164 votes -
Add more flexibility in Request TOU Pickup Locations policy
We’d like more flexibility in Request TOU Pickup Locations policy.
We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between some libraries.
Currently, we cannot achieve the above requirement in Alma. If more options are added to the Pickup Locations policy, libraries in the similar situation will also benefit.
For example, it would be more flexible if there are “In List (where we can select one or more libraries in our Institution)”, “In other Campus”, or “In other Libraries” options in the Request TOU Pickup Locations policy.
Another idea is to allow staff to override pickup locations and deliver-to relationship policies so that they can place any pickup request on behalf of patrons when appropriate. It will also be beneficial for those who need special assistance.
We’d like more flexibility in Request TOU Pickup Locations policy.
We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between some libraries.
Currently,…
162 votes -
Multiple Quick-Cataloging Templates
Scenario:
There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.Problem:
Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature, it is essential that staff are able to quickly complete record creation tasks without having to “fix” the records later because the current “Book” and “Article” templates don’t contain the correct coding.This lack of proper templates leads to the need for libraries to educate non-cataloging staff on why records look/work the way they do, and to create “cheat sheets” for their use in editing quick-cataloged records to match their resource type. These fixes and workarounds add a considerable amount of time to the “Quick” Cataloging workflow.
Request:
The ability to configure multiple Quick Cataloging templates would more effectively meet libraries’ needs. For each template, staff should be able to configure the template’s default fields and mandatory fields. The templates, once configured, should appear in a drop-down selection list alongside the existing book and article record types when the Quick Cataloging feature is used.Scenario:
There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.Problem:
Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature,…163 votes -
Purchase request conversion into a resource sharing request
It would be good if it was possible to convert a purchase request into a resource sharing request on Alma. This might arise in circumstances where the user has originally requested a purchase request for a journal article on Primo. It would be useful if this purchase request could be converted into an ILL request simply without having to re-key in the information
161 votes -
Consultation in Alma FF
There is no easy solution in Alma FF to indicate that an item has been consulted in the library and that it can be reshelved.
When items are placed on the hold shelf and are briefly consulted in the library, there is no easy way to directly reshelve them in Alma FF. The workarounds are far from ideal and are very labour-intensive when facing a large amount of physical requests: cancel the request (but this is not correct and influences our request statistics) and reshelve via the expired hold shelf, update the expiry date to yesterday (but this requires a lot of clicks) or wait until the item automatically appears on the expired hold shelf and reshelve from there. With this last option there is too much time between the moment of consultation and the moment of reshelving, which makes that items are not available on shelf or for request for a too long time period. It also makes that new features like the hold shelf reminder letter cannot be set up (because patrons could receive a reminder when they already consulted the item).
Possible solutions are: for an item that is scanned in via ‘return items’ the underlying request will disappear and the item will be reshelved automatically. A button ‘consulted’ (like there is a button ‘cancel’) which immediately reshelves the book when you handle a request is another – less preferable – option.There is no easy solution in Alma FF to indicate that an item has been consulted in the library and that it can be reshelved.
When items are placed on the hold shelf and are briefly consulted in the library, there is no easy way to directly reshelve them in Alma FF. The workarounds are far from ideal and are very labour-intensive when facing a large amount of physical requests: cancel the request (but this is not correct and influences our request statistics) and reshelve via the expired hold shelf, update the expiry date to yesterday (but this requires a…
159 votes
- Don't see your idea?