"Purge" deleted user records (actor.usr) which result from a patron merge operation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.1 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
EG 2.10
Basic troubleshooting seems to reveal that, when merging patron accounts in the staff client, the non-lead account is simply flagged as "deleted" rather than actively purged from the DB. This has the unfortunate effect of forever occupying certain useful fields (e.g. usrname), and in a way not obvious to the end user.
In current Evergreen, manually "deleting" a patron record will in fact do a "purge" internally, retaining the row for DB integrity reasons, but otherwise filling uniquely-
description: | updated |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
assignee: | Bill Erickson (berick) → nobody |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Confirmed in our 2.12 system and in the master sandbox. We would love to see this - we often get help desk inquiries in which the wrong patron was marked as the lead and the barcode and username need to be recovered.