Bug 41909 - Patron record needs a modification time stamp
Summary: Patron record needs a modification time stamp
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: 2026-02-23 18:46 UTC by Christopher Brannon
Modified: 2026-02-23 22:57 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
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 Christopher Brannon 2026-02-23 18:46:27 UTC
There does not seem to be a sufficient time stamp to indicate when a patron account/record has been modified/updated.  The Last Updated time stamp seems to change any time a patron logs in, which completely makes it useless as an indicator as to when a staff member has updated the account information.
Comment 1 Katrin Fischer 2026-02-23 19:06:32 UTC
That's because the last active date is updated nowadays when the user logs in, also cusing the last modification date to update as it's a timestamp updating automatically with every change of the record.
Comment 2 Christopher Brannon 2026-02-23 20:13:50 UTC
Correct.  Which is problematic for those of us wanting something to reference when  the record is actually changed and not just logged in to.  Last seen makes sense for the time stamp to be updated when the patron has logged in.  But I have not appreciated the last updated being changed for this.  This was a bad choice, in my opinion.  I wish we could configure what affects this timestamp.
Comment 3 Katrin Fischer 2026-02-23 21:06:04 UTC
It's a database automatism, so not really a conscious choice to make it so. If we want to change the behavior now, we will have to make Koha change the modification date instead of relying on the database mechanisms.
Comment 4 Christopher Brannon 2026-02-23 22:57:52 UTC
Which is why this bug is suggesting a modification timestamp.