Bug 38703 - Merged patrons should keep the most recent lastseen date
Summary: Merged patrons should keep the most recent lastseen date
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-13 17:46 UTC by Emily Lamancusa (emlam)
Modified: 2024-12-13 17:46 UTC (History)
2 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 Emily Lamancusa (emlam) 2024-12-13 17:46:41 UTC
Let's say a patron has duplicate accounts, account #1 and account #2, with the following data:

             lastseen
Account #1   2024-05-01
Account #2   2024-11-15

Let's say a staff member merges the duplicate accounts and chooses to keep account #1 based on whatever criteria they use to decide. Currently, account #1 would keep its lastseen date of 2024-05-01.

Since the lastseen date may be used to determine account retention and automatic renewal, it would make more sense to keep the more recent lastseen date in this case, especially for patrons who use the library relatively infrequently. (As an extreme example, I recently found a patron account in our system that has a lastseen date from 5 years ago yet also still has current checkouts from earlier this year!)