| Summary: | Patron record needs a modification time stamp | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
| Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | gmcharlt, kyle |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Christopher Brannon
2026-02-23 18:46:27 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. 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. 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. Which is why this bug is suggesting a modification timestamp. |