Bug 22081 - Alternate biblio merging functionality
Summary: Alternate biblio merging functionality
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-08 11:04 UTC by Simon Hohl
Modified: 2020-05-12 11:04 UTC (History)
1 user (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 Simon Hohl 2019-01-08 11:04:42 UTC
Currently the merging process let's you select which fields ought to be copied over to the "winning" record from the "loosing" record(s). Afterwards, the "loosing" record is deleted (moved to tables "deletedbiblio" etc.). 

One problem with the current solution: You can't tell after the fact, which deleted record was merged with which existing record. This is bad if you want to provide stable links to bibliographic records, for citation in research papers for example: Ideally you would want to be able to redirect to the "winning" records if somebody calls URL to a deleted record.
Comment 1 Simon Hohl 2019-01-08 12:51:28 UTC
One solution:

1. Add a toggle when merging "keep merged record"
2. If the toggle is active, let the user specify into which of the loosing record's fields to write the replacement's system number.
3. Remove all data from the loosing record except the replacement's sys number

If somebody navigates to a record replaced in this manner either redirect directly (OPAC) or show a link to the replacement record (Backend).
Comment 2 Simon Hohl 2020-05-12 06:53:58 UTC
http://www.loc.gov/marc/bibliographic/bd882.html