Evegreen should be able to un-merge records
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
In the case where bib records are merged incorrectly, it may be desirable to undelete the subordinate record rather than reimporting it. When the subordinate record is undeleted, the merge history is still highlighted at the top of the record (please see attached screenshot). While this situation is likely to occur infrequently, this display can be confusing to staff. It would be preferable to suppress the merge history display on undeleted bib records.
Note: another option would be to update the merged_to field in biblio.record_entry during the undelete process. However, discussion on the original wishlist bug (https:/
EG 3.5.1
Changed in evergreen: | |
assignee: | nobody → Rogan Hamby (rogan-hamby) |
summary: |
- Merge history should not display on undeleted records + Evegreen should be able to un-merge records |
Changed in evergreen: | |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
assignee: | Rogan Hamby (rogan-hamby) → nobody |
Since Evergreen doesn't have a native undelete concept this will be awkward. We could add a trigger that triggers off an undelete but it won't have any idea if the undelete is because of a merger reversal or not. Note that if we add something like a utility function to unmerge record merges that bundles undeleting a record and unsettling the merge to I think we should take that as an opportunity to add some merge tracking, specifically tracking volumes moved and title level holds and move those back as appropriate.