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.
1771 results found
-
Add Melingo to ALMA
Hello,
The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
It would be nice if it can also be implemented in ALMA.
If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.Thanks.
59 votes -
Add a job that can set the CDI option collectively
We would like you to add a job to set "Activate for search in CDI" collectively for the electronic collection set of CZ.
Also, please add a job to batch update the following CDI options for the electronic collection set of IZ.
- CDI Search activation status
- We subscribe to only some titles in this collection
- CDI-only full text activation
- Do not show as Full Text available in CDI even if active in Alma59 votes -
Optimisation of reminders and overdue letters (anti-phishing)
The reminders and reminder letters sent to patrons currently often end up in upstream spam filters of the mail providers. If this is not the case, we regularly receive feedback that they considered some of the automated notifications to be spam or phishing mails.
On the one hand, we would like to be able to optimise the automated notifications so that they are less automatically classified as spam according to today's standards. Ideally, Alma would already take common standards into account. On the other hand, we would like to see the possibility to personalise the notifications more and, for example,…
59 votes -
Expand SIP2 message support to include patron birth date
Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.
For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).
We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age
This enhancement would enable safer and more autonomous self-service environments, particularly…
59 votes -
Make the amount of a user account's TOTAL outstanding fees a feature in the Fines/Fees Notification Profiles
Presently, the amount-for-user-limit in the Fines/Fees Notification Profiles targets only those accounts with fees of the selected trigger fee type(s) that are all - BY THEMSELVES - in a certain range, let's say between 1 and 25 Euros. We want to be able to select fees of a certain fee type and a certain creation period to trigger a notification, but ONLY, if the TOTAL SUM of outstanding fees amounts to a certain sum. Thus, we could decide to send letters to heavily indebted accounts and e-mails to accounts that owe not much.
A second, immensely helpful improvement of the…
59 votes -
Manage EDI Tasks - Addition of Fund Code column
The addition of a sortable Fund Code column within Manage EDI Tasks would be incredibly useful for us. We use two strands of ordering at our institution, depending on if a title is required for research or teaching. The addition of a fund code column would allow staff to easily identify the EDI Tasks for their area.
59 votes -
Fully receive items through receiving date only
Currently, if an item with a POL has a receiving date, it is not considered fully received until it has been received under Acquisitions > Receive. Items with a POL and a receiving date that have not been received through the receiving process show up in the task list under Order Lines with Claims > Not fully received. If an item has a receiving date, it should be considered fully received, whether or not it has been through the receiving process.
59 votes -
Create resource sharing integration with DOCLINE
Create integration for borrowing and lending requests to be pushed/pulled to/from DOCLINE.
See https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/37290289-alma-to-docline-oai-pmh-integration for holdings integration to DOCLINE.
59 votes -
Persistent User Group Data in Borrowing Requests Subject Area
We would like to request that the Borrowing Requests subject area in Analytics captures and stores the patron's information (specifically the User Group) at the time of the transaction, rather than pulling the current status from the user record.
Currently, historical reports on borrowing requests reflect the requester's present-day group. If a student who made a request three years ago is now a staff member, or if their record has been deleted, the historical data is either overwritten or lost. This makes the data entirely out of context and renders historical analysis and longitudinal reporting impossible.
In the Fulfillment subject…
59 votes -
Autocomplete
It would be extremely helpful for ALMA to have an autocomplete feature when searching for title, author or even call number. Many times you can be off by one letter and ALMA won't find the item.
58 votes -
Better information design for pop-ups in the New Circ UI
When managing return items in Alma: information in the pop-up on subsequent steps in the process is difficult to read due to a small typeface. Also, not all information is relevant or, strictly speaking, correct (e.g. "item is not on loan" even when there is an active request).
We would like to see a larger font in general, or, if this is not feasible, at least the requester's name in bold typeface. This would add a much needed visual cue for staff processing returns.
The bullet point about the item not being on loan could be supressed as it offers…
58 votes -
Item Sequences Configuration: import option
In the area of the "Patron/User Groups" there is already an import option (Excel file) for the configuration table.
Please provide the same feature for the Item Sequences configuration table.
Since our counters contain the year and always have to start counting with 1, we have to change this table every year. Due to our sublibraries we have more than 50 active counters.58 votes -
Add "Scan In Items" functions to "Return Items" processing
We would like to build "Scan In Items" features to the "Return Items" function, i.e. "Return Items" should be able to process requests, expired holds, and items in transit between locations the same way as "Scan In Items" does. This includes the radio button for automatically printing slips (configuration should be able to define a default)
58 votes -
Notify receiver of Hold Items
Currently within an order when the Hold Item box is ticked for an Interested User the patron physical item request is not placed for the item until after the item is received.
This means that receiving staff do not get the pop up notification that the item has a user request at the time the item is received.Upon receipt of an item that contains an Interested User with the Hold Item checked can you please generate the same pop up notification generated for physical item requests.
We have found that we have to manually add the physical item request…
58 votes -
Receive items without generating an item record.
Law libraries have loose leafs and pocket parts and do not need to have an item generated for them. We would like to be able to track when they are received but having them show up in Primo is messy and having a suppressed holding just to receive these items is also messy. Both would make running statistic more difficult because the count would be inaccurate. Voyager was capable of receiving these sorts of items without automatically generating a barcode while also allowing to track the receiving information. It would useful if you added this feature to Alma.
57 votes -
Purchase Requests options
We would really like to be able to utilize Alma/Primo VE to its fullest potential, but one of the things lacking in the Purchase Request options is that there is no way to modify the fields or even add additional fields. We are needing at least two additional fields for us to be able to use the built-in functionality - a note field for special instructions (usually entered by faculty) and a level of priority (i.e., Rush or no rush - in the event this request is for a course reserve, it needs to be a priority, but there is…
57 votes -
Add check-out function to Alma mobile
I think it would be useful to add the check-out function to Alma mobile. Sometimes the circulation desk is busy so it would be helpful if library staff could check-out books for users from a mobile device.
57 votes -
Add 880 field to the Bibliographic Details dimension table in Analytics
In MARC bibliographic records, the 880 field is used for non-Roman script equivalents of other fields in the bib record. CJK (Chinese, Japanese & Korean) libraries, for example, may use the 880 to record the non-Roman script equivalent of the Romanized characters in a 245. We would like the 880 field to be searchable in Analytics so we can create new book lists in the CJK scripts. New book lists are very popular with our users and we would like to be able to present these lists in the CJK scripts.
57 votes -
Vendors : simplify Contact information and People contact tabs
Hello,
Handle vendors in ALMA is pretty twisted and not user friendly !
We can understand the distinction between Vendor details (network level) and Vendor account details (institution level).
But why distinguish Contact information and People contact in two separate tabs ?
This makes us input twice same informations.Our request : to get one tab for all Contacts ; each contact would be distinguished by a specific frame with name, first name, job description, email, postal mail and phone nember. All display in one single screen.
If you share this request, VOTE.
57 votes -
Block when overdue: add a "days per overdue days" unit of measurement option
Hello everyone,
when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first…57 votes
- Don't see your idea?