[Bug 38703] New: Merged patrons should keep the most recent lastseen date
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38703 Bug ID: 38703 Summary: Merged patrons should keep the most recent lastseen date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: emily.lamancusa@montgomerycountymd.gov QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com 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!) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38703 Cab Vinton <bibliwho@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bibliwho@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38703 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blawlor@clamsnet.org --- Comment #1 from Brendan Lawlor <blawlor@clamsnet.org> --- This makes a lot of sense to me. Should the default be to keep whichever is the most recent last seen date? In the case of merging many records it should always get the newest lastseen date. This could also be good to retain certain other dates like dateenrolled, you'd most likely want to retain the oldest date, or dateexpiry you'd probably want the most future date. It could also be possible to allow the user to choose which lastseen date, or other dates like dateenrolled and dateexpiry, at the time of merging as in bug 30303. This bug is only for the case of merging two patrons, but it would be pretty easy to add fields as options to copy. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org