Bug 37819 - Koha could auto-update due dates if patron dateexpiry is updated to before current item due date
Summary: Koha could auto-update due dates if patron dateexpiry is updated to before cu...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-03 10:55 UTC by Chris Rowlands
Modified: 2024-09-13 15:44 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Rowlands 2024-09-03 10:55:52 UTC
This is currently achieved by library staff renewing the patron's items with the ReturnBeforeExpiry setting set to "Require". A couple of libraries in our consortium have suggested it would be more convenient if this was done automatically when saving a patron record after editing the dateexpiry field.

I expect for professional/health libraries where users leave their posts at quite short notice would find this useful.

I'm imagining a couple of solutions; maybe a checkbox in the patron edit screen under date expiry saying something like "Update due dates" or an admin setting sitting with ReturnBeforeExpiry that checks and updates due dates if the patron's dateexpiry is edited.
Comment 1 Jeremy Evans 2024-09-13 15:44:11 UTC
We would support this.
The user expiry dates on our system are set/updated by the daily feed from our Active Directory so they are the date their IT accounts expire. It is usual if staff have outstanding annual leave that their last working day is before that date.   So a config option to specify a value may be useful - e.g. if we wanted any due dates to be set at 14 days before the user expiry date to allow time for pre/overdue emails to run and we have a chance to contact the user before they leave.