If I had a spare vote, I'd vote for this!

This is an audit issue for us if we have books due beyond the patrons expiry date.

This is surely a must; it's beyond belief that due dates can remain when a patron expiry date is reduced.

This appears on NERS and IDEAS exchange yearly and is something that would make a difference to the ability to recover stock as users leave with long loan items without library staff being aware

It seems absurd that Alma doesn't already do this. Can there be a daily job that runs to shorten the loan (and notify the users) based on the user expiration date?

Yes, please!

This functionality would be extremely helpful and I'm disappointed this idea did not make it through the NERS enhancement process.

This would be very useful as we have always had this issue throughout the year when students change dates or move courses or suspend studies. Very disappointed it did not make it through NERS as seems like Alma should be able to deal with this as part of the basic functionality.

Did not make it through round 2 of NERS 2021.

I just put a ticket in because we hadn't noticed the problem until all the bulk due date changes to do with COVID. It seems like something Alma should just do.

I have had a case open for months about this issue and have requested it stay open until something is done about it. As a stopgap measure I got our systems people to integrate this workflow into our patron load as we were unable to backdate loans within Alma. This means that a fulfillment process has been dealt with externally, which should not be necessary.

It’s very useful especially for solving our current difficulties to have students return their loans who graduated earlier but with loans due date after their graduation date or updated expiry date. The due date should be shortened automatically by Alma to match with the student's updated expiry date.

Could Ex Libris comment on this Idea? It's similar to NERS 6737, which was included in Round 2 of Alma NERS 2020 enhancement voting. Ex Libris sized the complexity of NERS 6737 as 25 points.

Would love to see this instigated. A much better client experience and a big time saver for everyone

This seems like a no brainer to me. We have lost double the usual amount of books this year since the introduction of auto renewals with Alma and it strikes me that this would go some way towards mitigating the problem. I would definitely vote for it if I had any spare votes.

This has also become more of an issue for Curtin in recent months as well. We spend considerable time adjusting due dates for student who have their expiry date changed but not the due date of their items. We are planning a work around with our patron loader, but we shouldn't have to do this as it should be handled automatically.

None of the "change due date" options for graduating students work for us. We can get our patron load adjusted so that current students who have applied for graduation have an expiration date moved to the current term's end. However, because the patron expiration date is not considered a due date calculation event, the patron's due dates are not adjusted and patrons are not sent notices about their new due dates. We would like to have the expiration date become a due date calculation event as well and have that event trigger the change due date notice.

Currently, Patron Expiration date is not considered a "due date calculation event" (Only loan, renewal, or a recall by another request on an item are considered due date calculation events)
We would like that Patron Expiration date will also be considered as one.

This is still a considerable gap in the fulfillment management in Alma, and the main 'oddity' encountered when dealing with students who perhaps have received a vacation loan due date, e.g. due late September, in June when they had an expected end date of October, but then have an expiration date change to finish in July. Alma ought to be able to shorten the due date of such users.