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 ~
1750 results found
-
Add SUSHI “Status Description” field for uploaded files as column option in Analytics
Ex Libris has said “No valid report items found in the file” is behavior that should still be listed as a “Fully Processed” file, but it would be helpful if we could more easily find files that we believe may not have loaded properly based on their Alma “Status Description” in Analytics.
1 vote -
Create the button "claim never borrow" on Loan service
Since Alma has a "Claimed Return" button, could create a button for users who never borrow this book in the loan tab.
1 vote -
serial type
Be able to lookup bibliographic titles by serial type (Fixed field 21 SrTp: Type of continuing resource), especially for monographic series type m. Our serials desk wants a way to easily find these so when they receive materials they can separate the standing orders from the subscriptions. They could also generate reports from the data parsed in Analytics to assist their students during the receiving process.
3 votes -
Create a job to send a notification letter to users when their expiry date is near so they can request to renew their library user account
The option to notify users whose accounts have or will expire of their options for renewing their library user account would help us to stay engaged with users whose library user account will expire soon (or has recently expired). Users who want to continue using their library account can renew it prior to the expiry date, thus reducing any barriers to accessing their account and using library materials.
A notification letter could be created to support this type of messaging. It would be great if a job could be scheduled to send to users whose expiry date is upcoming. It would be good to be able to filter the job according to a profile or in job criteria by account type (internal / external), user group, expiry date range, etc.
The option to notify users whose accounts have or will expire of their options for renewing their library user account would help us to stay engaged with users whose library user account will expire soon (or has recently expired). Users who want to continue using their library account can renew it prior to the expiry date, thus reducing any barriers to accessing their account and using library materials.
A notification letter could be created to support this type of messaging. It would be great if a job could be scheduled to send to users whose expiry date is upcoming. It…
12 votes -
Check box option to disable Alma from appending file names in publishing profiles
We publish files to many third party vendors. Some vendor systems must have their files named with a certain convention and CANNOT process them if that filename convention is altered in any way.
Alma publishing profiles are current configured to append "_new" to the end of files it publishes, even if you specify a file name already. We would like the option to either enable or disable each publishing profile from appending the filenames it sends. They can be enabled by default, or not, but the option would be helpful.
Use case: We are publishing files of electronic holdings to OCLC because the current OCLC Data Sync profiles as they exist within Alma do not handle electronic materials (see https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/110Publishing_to_OCLC#Publishing_Electronic_Holdings_to_OCLC ). OCLC asks for a specific file naming convention, and that name cannot be altered. The profile adds "_new" to the end of the file name, which prevents their system from processing the file entirely. As a result, we have to either manually download these incredibly large files, change the file name, the put them on OCLC's server, or write a script to do this for us with no coders on staff.
We publish files to many third party vendors. Some vendor systems must have their files named with a certain convention and CANNOT process them if that filename convention is altered in any way.
Alma publishing profiles are current configured to append "_new" to the end of files it publishes, even if you specify a file name already. We would like the option to either enable or disable each publishing profile from appending the filenames it sends. They can be enabled by default, or not, but the option would be helpful.
Use case: We are publishing files of electronic holdings to…
5 votes -
Excel - Allow personalization of the fields to be export
Our proposal, is to allow include bibliographics fields to the excel archive.
In order to manage the purchase requests, we need an excel archive that iclude fields like ISBN, edition, year, ...1 vote -
Analytics: Add Purchase Request Requester user information at the time of request
The Purchase Request Subject Area Purchase Request Requester user information is updated every day by ETL to the current user information.
In many cases, this is useful. But it is not useful for reporting when it is important to know the information of a user at the time of an action.
As one example: We would like to report on the number of patrons submitting purchase requests by user group such as undergrads vs postgrads vs staff. If a patron submits a purchase request as an undergrad and then becomes a postgraduate, the outcome of current analytics is that all their purchase requests are reported as submitted by a postgraduate. This is completely incorrect and cannot be reported upon.
As another example, we have Statistical Categories for School and Faculty. If a student is associated with one School by a course they are enrolled in for one semester and then is associated with another in the next semester, all purchase requests update to the latest information and the data is again useless.
It is proposed that Analytics cover this scenario by adding fields for user information at the time of action of submitting a purchase request.
This is the same concept as in the Fulfillment area to record user information at the time of loan.
In order to avoid disruption, the request is specifically to add fields, not replace them.
Note: This submission covers all relevant fields in the Purchase Request Requester dimension table, not just user group.The Purchase Request Subject Area Purchase Request Requester user information is updated every day by ETL to the current user information.
In many cases, this is useful. But it is not useful for reporting when it is important to know the information of a user at the time of an action.
As one example: We would like to report on the number of patrons submitting purchase requests by user group such as undergrads vs postgrads vs staff. If a patron submits a purchase request as an undergrad and then becomes a postgraduate, the outcome of current analytics is that all…1 vote -
Ability to make financial adjustments to previous fiscal years after rollover
We would like to be able to make financial adjustments to prior fiscal years after rollover occurs. We want to complete rollover in a timely fashion to be able to continue business as usual, however our University's closing occurs later than we complete rollover in Alma and there are times when I need to adjust Alma to match any last minute general ledger changes.
1 vote -
claims - serials - populate item description
It will be very helpull to include the item description in the list of claims.
3 votes -
Add the Inventory price, Receiving date,Inventory date fields on the output results display
It is important for the acquistition staff to add the following items to the display options based on the output results display retrieved by the physical item:
Receiving date
Inventory date
Inventory price32 votes -
Make requests for multi-volume works fulfillable at location scanned in
Hi there,
If patrons submit a request for a multi-volume work at the holdings level, only the circulation desk for the Library where the volume is held can see the 'existing holdings requests may be fulfillable by scanned in item' message when the requested volume is scanned in.
We would like all circulation desks to be able to see this message and had the option to attach the item to the request at the holdings record.
Our use case is that we have many items held at offsite storage, which is set up as a Library in Alma but is not a real location (it is a commercial storage facility). The items are delivered to the pick-up location (one of our Libraries) requested by the user and scanned in by Library staff. However, they cannot fulfil the request from the Library they are signed in as.Hi there,
If patrons submit a request for a multi-volume work at the holdings level, only the circulation desk for the Library where the volume is held can see the 'existing holdings requests may be fulfillable by scanned in item' message when the requested volume is scanned in.
We would like all circulation desks to be able to see this message and had the option to attach the item to the request at the holdings record.
Our use case is that we have many items held at offsite storage, which is set up as a Library in Alma but is…6 votes -
Include the workflow step status of a "pick from shelf" request in the API
If a "pick from shelf" request is created in Alma, it initially has the workflow step status "new". After printing the Resource Request Slip Letter, the workflow step status switches to "in process", showing that the request is now being fulfilled (meaning an employee is now picking the item from the shelf).
If this difference was included in the API call, it could be used by a discovery system to enable patrons to cancel a request only if the Resource Request Slip Letter has not yet been printed. Thus, patrons could cancel "new" requests, but not those that are "in process".
A detailed description of the issue can be found in the attached .docx file. Also, the salesforce ticket #06672528 refers to this request.
If a "pick from shelf" request is created in Alma, it initially has the workflow step status "new". After printing the Resource Request Slip Letter, the workflow step status switches to "in process", showing that the request is now being fulfilled (meaning an employee is now picking the item from the shelf).
If this difference was included in the API call, it could be used by a discovery system to enable patrons to cancel a request only if the Resource Request Slip Letter has not yet been printed. Thus, patrons could cancel "new" requests, but not those that are "in…
6 votes -
Archived Reading Lists show up in Reading List Tasks
When I archive reading lists, they show up in reading list task section and there isn't way to remove them from there. I don't need know that they've been archived, so it would be nice if they didn't show up in this area since I use it to monitor reading lists I'm currently working on. If there is a way to configure this, so they don't show up, I haven't been able to find any documentation for it. (Most of the time I get pointed to Leganto and we don't use it)
28 votes -
Stop Change Due Date from overriding hold request
There's an issue we're having where changing the due date of a loan allows the current owner to extend their checkout time, even after a hold request has been placed. We have Alma configured so that it prevents a renewal from occuring, but change due date seems to ignore that function.
1 vote -
Generate item-level request for reading room materials
Currently, if there is one copy of an item in general stacks and another in a reading room location, assuming both are available, Alma will prioritize the stacks copy for requests and the request form will be based on the stacks request TOU. Some institutions use reading rooms for Special Collections materials, so the items may not be interchangeable and if a patron requests the reading room copy, we want the request to be specific to that item and the form to follow the reading room request TOU (limiting the pickup location).
Giving the items unique descriptions forces item-level requests, so the correct TOU is applied, however it can clutter the records. I propose either configuring Alma to only create item-level requests when it comes to reading room materials, or add a field that can be toggled in the item record to mark it as unique so that requests for that item will always be item-level, even if other items exist on that record.
Currently, if there is one copy of an item in general stacks and another in a reading room location, assuming both are available, Alma will prioritize the stacks copy for requests and the request form will be based on the stacks request TOU. Some institutions use reading rooms for Special Collections materials, so the items may not be interchangeable and if a patron requests the reading room copy, we want the request to be specific to that item and the form to follow the reading room request TOU (limiting the pickup location).
Giving the items unique descriptions forces item-level requests,…
3 votes -
Add vendor information to Order Now Letter
Currently in the Order Now Letter the vendor information is not output in the XML, which is automatically generated when submitting an order.
With adding this feature, the ordering person could then also receive the information by e-mail from which vendor the resource was ordered.
1 vote -
Alma to automatically process pending requests when recalls are switched back on
During Easter and Christmas vacation we turn off recalls in Alma, so requests are still placed by the user but recalls are not made. After the vacation, we turn recalls back on however Alma does not 'catch up/update' the pending requests into a recall.
We would like Alma to therefore be able to process those requests in pending and turn them into recalls once the recalls have been switched back on.
3 votes -
Improve “Chat for Support” role to add product specific scoping or separate roles per product
As more products are added and managed by the Alma HEP it becomes a concern that Ex Libris is not adding necessary granularity for roles. The “Chat for Support” role does not have any granularity for different products.
For example, we would like for some of our senior acquisitions staff to have visibility and ability to open Chat sessions for minor title by title issues with Rialto, which we have recently implemented. But this is not possible, as the role gives visibility and ability to open Chat sessions for Alma also, which is not appropriate per our internal management of staff support and case handling.
Fulfillment of this request would be ability to assign staff a role of Chat for Support, scoped to Rialto and then separately another role scoped to Primo VE, and then separately another role scoped to Alma etc. Or alternatively completely separate roles such as ‘Chat for Support – Rialto’, ‘Chat for Support – Alma’, etc.As more products are added and managed by the Alma HEP it becomes a concern that Ex Libris is not adding necessary granularity for roles. The “Chat for Support” role does not have any granularity for different products.
For example, we would like for some of our senior acquisitions staff to have visibility and ability to open Chat sessions for minor title by title issues with Rialto, which we have recently implemented. But this is not possible, as the role gives visibility and ability to open Chat sessions for Alma also, which is not appropriate per our internal management of…1 vote -
When cancelling requests from the pick list, display a warning message
On the pick list, requests are displayed at a title level. This means it is possible that multiple requests are present for the title. When clicking 'cancel request' from the title, all requests are cancelled, not only the first one. Since this behaviour occurs even when requests are from different requesters, for different volumes or different digitisations, we would like a warning message to appear before deleting multiple requests from this screen.
1 vote -
Allow the existing configuration of the user form to apply also on the "Vendors > Contact People tab > Add Contact" page
This idea was opened by Ex Libris to see how the community supports it.
There is an existing configuration for the user form which was added in August 2022: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2022/Alma_2022_Release_Notes#Configure_the_User_Form
Please have this configuration apply also when creating a new vendor "Contact" (Vendors > Contact People tab > Add Contact).
For example, if an institution selected that some fields should not appear in the user creation form, these field should also not appear in the vendor contact creation form.
0 votes
.png){kind=link}
- Don't see your idea?