Waiving fines based on additional criteria or based on  an input file.

It will be possible to waive fines based on additional criteria, such as a Users set or a date range. In addition, it will be possible to waive a known set of fees that are listed in an Analytics report.

Enhanced flexibility in processing fees that have been identified as waived fees.

An additional ID will be added to requests. The institution will be able to control different attributes of the ID.

A new request ID will be assignable to requests. The institution will be able to set the maximum number after which the ID will reset, as well as a prefix and a padding option for the ID.

Better control over the IDs that are used to sort request lists. 

In addition to being able to set the "Not Needed After" field as mandatory on the request form, it will also be possible to set a default policy for this field.

It will be possible to hide the "Not Needed After" field from the Primo VE request form and have Alma use a date that is set by a library policy.

Improved efficiency for request queues. The library can set highly requested items to have short expiration dates so they do not get sent to the hold shelf if time passes until they can be fulfilled.

An option to set the system to block requesting items that have loan policies or a block that prevents loaning the item.

A configurable parameter will support setting the system to check the patron's permissions to loan. If the patron cannot loan the item, requesting will also not be allowed.

Improved request service for library patrons by  being unable to request items they are currently blocked from loaning.

An option for staff to override policy-related blocks that prevent placing hold requests.

A button on the Alma request form will enable staff to override requestability/limit hold policies. Clicking the button will enable submitting the request while overlooking the preventing policy.

More flexibility in handling requests by having the option to override a situation where the request is not possible because of request policies.

Institutions can perform user purges based on predefined Users sets. This enhancement allows for greater flexibility and precision in user management by enabling bulk deletions using standard purge validations and the configured delete user policy.

• Enables purging of user records based on selected user sets.

• Utilizes standard purge validations to ensure compliance with institutional policies.

• Provides enhanced flexibility compared to the existing purge job, which is limited to user record types and user groups.

This feature empowers institutions to streamline their user management processes by providing more granular control over user record deletions. It helps optimize system performance and maintain data accuracy by allowing targeted purging of user records according to specific criteria.

Booking functionality will be enhanced with features that will improve both the end user experience and the library booking workflow management tools, focusing on space booking use cases.

• Improved calendar for requesting.

• Repeatable bookings support.

• Support for grouping multiple items in one request.

The new tools will enable patrons who use Primo and Alma for space booking to enjoy  more efficient and intuitive request interfaces that better reflect their space booking requirements.

An option to configure a warning that pops up when the Change Due Date is used on a recalled loan. 

It will be possible to set the system to warn if a due date for a recalled item is changed at the circulation desk.

Better loan service clarity by preventing manual change of due dates for already recalled items.

Improvements with using a proxy patron account in Manage Patron Services.

It will be possible to easily identify a proxy patron at the circulation desk and choose the sponsor on whose behalf an item is checked out. 

Improved efficiency of proxy-patron management at the circulation desk.

It will be possible to configure the courtesy and overdue reminders for short loans as a percentage of the loan period instead of in exact minutes.

It will be possible to set the courtesy and overdue message for short loans to be set by a percentage of the loan period. For example, a value of 50% would cause a two-hour loan to have an overdue message to be sent one hour after due time.

Courtesy and overdue messages for short loans will better match the specific loan's due time, resulting in clearer messages to the patrons.

Proxy relationships between patron accounts will get an expiration date, ensuring they automatically expire after a set period.

• Expiration Date Field:  An expiration date field will be added to the Proxies tab in the user form and API.

• Automatic Expiry: Proxy relationships will be considered inactive and ignored by the system after the expiration date.

• Editable Expiry Date: This will allow editing of the expiration date directly in the Proxies tab.

This enhancement enables academic institutions to manage proxy relationships more effectively by setting automatic expiration dates, ensuring permissions do not extend indefinitely and align with academic schedules.