From 22489de26ef87f724e4151931c53976d994877d1 Mon Sep 17 00:00:00 2001 From: Bill Erickson Date: Thu, 25 Jan 2018 11:28:47 -0500 Subject: [PATCH] LP#1744996 Record merge tracking release notes Signed-off-by: Bill Erickson Signed-off-by: Remington Steed Signed-off-by: Dan Wells --- .../Cataloging/record-merge-tracking.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/Cataloging/record-merge-tracking.adoc diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/record-merge-tracking.adoc b/docs/RELEASE_NOTES_NEXT/Cataloging/record-merge-tracking.adoc new file mode 100644 index 0000000000..e1ad8ff561 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Cataloging/record-merge-tracking.adoc @@ -0,0 +1,14 @@ +Track Record Merges +^^^^^^^^^^^^^^^^^^^ +When 2 or more bib records are merged, all records involved are stamped +with a new merge_date value. For any bib record, this field indicates +the last time it was involved in a merge. At the same time, all +subordinate records (i.e. those deleted as a product of the merge) are +stamped with a merged_to value indicating which bib reord the source +record was merged with. + +In the browser client bib record display, a warning alert now appears +along the top of the page (below the Deleted alert) indicating when a +record was used in a merge, when it was merged, and which record it was +merge with, rendered as a link to the target record. + -- 2.43.2