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.
65 results found
-
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.
-
Raise the limit to total number of rejections ( currently 1000) for exporting records that are not imported (due to import profile setup)
There is currently no limit to the number or records that can be imported into Alma (as far as I am aware).. there is however a limit of 1000 when needing to export the rejected data.. Workflows would be much better managed if this limit was raised to the total number of rejected records
159 votes -
Re-sequence MARC fields by each tag when running a normalization rule
Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).
Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.
I've attached an example…
264 votesChanging the existing re-sequencing task would impact all libraries, whether interested in this change or not - but we will look into adding a new re-sequencing task that will handle all fields, so libraries will have a choice on which re-sequencing behavior they want to apply.
-
'Not Needed After' date should be mandatory on patron physical request form.
It would be helpful if the 'Not Needed After' date is mandatory on the patron physical request form to improve the requesting process for Patrons when there is a high demand for physical items.
400 votesHi,
An approach we’ll be looking at is that an optional ‘Last Interest Period’ request policy will, if set, be used to set a default the last interest date (Primo and Alma). This way every request will have a last interest date set by the policy and overridable by the patron.
-
Normalization rules - adding dates
It would be great if the normalization rules could be enhanced to use variables such as date, or add datestamps.
We would like the ability to insert dates into MARC notes fields via normalization rules.
Ideally inserting variables something like %DAY%/%MONTH%/%YEAR% in a rule would add today's date in the format DD/MM/YYYY once a rule is run.
60 votes -
Allow "ignore_lender_due_date" setting to be customized per resource sharing partner
Currently the "ignorelenderduedate" setting in the Alma Customer Parameters Mapping Table is a global setting; it applies to all resource sharing partners. This is problematic for consortia who have resource sharing partners for consortia members, as well as a resource sharing partner for ILLiad.
Setting "ignorelenderduedate" to "true" works for our consortia resource sharing standard checkout, but ILLiad due dates must be entered manually.
Setting "ignorelenderduedate" to "false" works for the ILLiad lender due date, but then consortia due dates must be entered manually.
If "ignorelenderduedate" could be…153 votesThe “ignore_lender_due_date” parameter will be handled as a default value. A configuration option on the partner record will enable to override its value.
-
Add notifications to Alma reminders
I appreciate the addition of the Reminders in Alma, but I think it would be even more useful if reminders could trigger email notifications when the reminder date has arrived.
219 votesA new task will be added to the tasks widget, alerting catalogers when reminders' date arrives.
-
Initiate consortium fulfillment requests for items in another institution from Alma
In our consortium, we would like to be able to place requests for items in other institutions on behalf of our patrons in Alma.
Scenario: a patron (dean, faculty member, etc) calls the circulation desk asking if an item is owned by the library. Circ operator searches Alma and finds the item in a consortium library. Circ operator SHOULD be able to request item in Alma from the patron's record. Right now, circ operator has to tell the patron to search Primo and request on his or her own.
267 votes -
Timeout should be configurable
Timeout should be configurable to allow for longer timeout than 60 min. This would be helpful for staff who work for example in areas like information services where you need to use Alma several times during the day but not continuously
118 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 -
option to delete bib when relinking physical inventory
When relinking electronic inventory, a pop up occurs asking what to do with the bib (nothing, delete if no other holdings, or suppress).
It would be a time saver to have the same pop up when relinking physical inventory
16 votes -
Allow configuration of quick cataloguing form required fields
We currently only use the quick cataloguing form at circulation desks to create quick records to loan items found on the shelves but not found on Alma. The items are loaned and then the work order routes them to the cataloguing team on return. All these items already have call numbers so we'd like the call number field to be a required field in the quick cataloguing form. Sometimes returned items are incorrectly returned to the shelves and if the quick catalogue record does not include the call number they are often impossible to track down.
227 votesDear all, we are currently looking into the possibility of a re-design of the quick cataloging functionality - we will take this request into consideration as part of this future change.
-
Add "item policy" and "temporary location" automatically to predicted issues
Acquisition librarians want to add automatically the "item policy" and "temporary location" to predicted issues to speed up their work and limit the number of clicks. At this moment the added value of prediction pattern functionality is being restricted by the lack of functionality (parameter setting) …
Use case: It’s not possible to add the item policy/temporary location as a parameter to continuous pol’s. If issues are created via prediction patterns the item policy/temporary location should be indicated automatically based upon parameter settings on pol level. This would save a lot of time and additional clicks when receiving the issues.…492 votesWhen creating a a POL, it will be possible to also define a default item policy and temporary location. This will be used when items are created (by a prediction pattern or manually) on POL or at receive time
-
Extend the "interested users" functionality
Acquisition librarians want to extend the current "interested users" functionality in order to serve the end user in a better and faster way. The current "interested users" functionality is not sufficient enough, to become useful and really benefit from this functionality we would like to extend it with:
• The ability to sort the interested user list.
Use case: some users (e.g. academic staff) have priority and should get the issue first!
• Make it possible to create hold requests on these items regardless of the existing fulfillment policy:
Use case: some libraries don't allow requests for available items, but…289 votesDear community, this idea was reviewed and accepted, below you can find the suggested design, please feel free to comment if you have further suggestion:
1. It will be possible to sort the interested users list using arrows. The hold requests will be activated as per the order in the interested users tab.
2. A check mark for ‘Loan to first interested user’ will cause the received item to be automatically loaned to the first interested user when the item is received.
3. It will be possible to print the list of users (in the proper order) when the item is received
Thanks,
Noam Fass | Alma product management team -
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.
-
Improve Alma Job Reports for Failed Record
It would be extremely helpful if more details were given when there are failed records or records with exceptions on the jobs we run in Alma. Many of the job reports only report the number of failed records. It would be great if the report would provide MMSID information so the we know what records failed.
512 votesWe are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.
-
Fulfillment Borrowing history: allow users to choose to opt in
Currently the library can turn borrowing history on or off, but the choice applies to all users. For privacy reasons, and in order to avoid subpoena situations, we have it off, but some users do want borrowing history on as a convenience, and are not concerned about privacy risk themsleves. Why not allow those users to opt in to borrowing history, and allow the default otherwise to being off?
By the way, this "opt in" approach is how most public libraries in Eastern Massachusetts are set up, so our users expect this level of service from us also.
It is…
265 votesFrom the Circulation Desk user update form, it will be possible to turn on a ‘keep my loan history’ check mark.
Patrons that have this check on will not have their loans anonymized when the anonymization process runs.
It will be possible to get this indication also from API, and from Primo.
The option to turn ‘keep my loan history’ on should be a library decision
-
Change due date when patron account expiration date reduced
As a Fulfillment Manager, I would like the due dates of a patron's books to be changed to their account Expiration Date if this is reduced. Eg, if a book is issued to a student for 10 weeks and they withdraw from their course, the original due date remains which can be some weeks after they have left. This can cause confusion for library staff and the patron.
339 votesWhen a loan due date is shortened due to patron expiry, Alma will retain and internal an indication for that on the loan record. This way when the patron expiry is updated (shortened OR extended) the loan due date will be recalculated using the loan date (i.e. as if the recalculation is happening at loan time).
This way, the due date may be extended or shortened according to the new expiry date.
-
No Auto-Send of Activity Report Letter
The Activity Report letter automatically tries to send when “Renew Selected” and “Renew All” are selected in Alma Patron Services. This is problematic for a few reasons:
The letter is triggered even when the letter is disabled in Letter Activity configuration. It generates a ‘fail’ message for staff.
The letter slows down processes dramatically depending on how many loans are attached to the account.
A workaround is to use the letter opt-out functionality, but we'd have to continually update all of our users with the opt-out in order for this to work well for us.
I would like to see…
188 votes -
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
- Don't see your idea?