Wishlist: Tracking bib record merges
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Evergreen 3.0 / Wishlist
It would be nice if admins could tell when a bib record has been merged with/to and when the merge occurred. Similarly, it would be good to know the target record for subordinate record merges. As a practical use case, it helps diagnose cases where hold queues jump in size due to bib merges.
I propose 2 new biblio.record_entry fields, last_merge_date and merged_to. Both source and target records would have values applied for last_merge_date for any merges. And merged_to would be applied to subordinate records (and left NULL for the target record).
At a glance, toward the end of the asset.merge_
Thanks to J. Boyer for the merged_to suggestion.
Thoughts?
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
As noted by Dan Scott in IRC, the merged_to value could be used to apply 301 redirects in the catalog, automatically sending users to the merge target of merge-deleted records.
Note that since bib records can be un-deleted, though, it would be possible to create single and muti-step merge loops.