From: kilsdonka <43423795+kilsdonka@users.noreply.github.com> Date: Fri, 21 Sep 2018 21:22:36 +0000 (-0700) Subject: Docs: bibliographic record merging and overlay X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=1bbf52d978ed9faa595a5391a020ce888bfffe6f;p=evergreen%2Fpines.git Docs: bibliographic record merging and overlay Signed-off-by: Jane Sandberg --- diff --git a/docs/cataloging/merge_overlay_bibs.adoc b/docs/cataloging/merge_overlay_bibs.adoc new file mode 100644 index 0000000000..094be726da --- /dev/null +++ b/docs/cataloging/merge_overlay_bibs.adoc @@ -0,0 +1,64 @@ +Bibliographic Record Merging and Overlay +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Catalogers can merge or overlay records in record buckets or using records obtained from a Z39.50 service. + +Merge Records in Record Buckets +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1. Click *Cataloging>Record Buckets*. +2. Create and/or select a record bucket. +3. Select the records that you want to merge, and click *Actions>Merge Selected Records*. + +image::media/marcoverlay1.png[] + +4. The Merge Selected Records interface appears. +5. The records to be merged appear on the right side of the screen. Click *Use as Lead Record* to select a lead record from those that need to be merged. + +image::media/marcoverlay2.png[] + +6. Select a merge profile from the drop down box. + +image::media/marcoverlay3.png[] + +7. After you select the profile, you can preview the changes that will be made to the record. + +image::media/marcoverlay4.png[] + +8. You can change the merge profile at any time; after doing so, the result of the merge will be recalculated. The merge result will also be recalculated after editing the lead record, changing which record is to be used as lead, or removing a record from consideration. +9. When you are satisfied that you have selected the correct merge profile, click the *Merge* button in the bottom right corner. +10. Note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge. + +Merge Records Using Z39.50 +^^^^^^^^^^^^^^^^^^^^^^^^^^ + +1. Search for a record in the catalog that you want to overlay. +2. Select the record, and click *MARC View*. +3. Select *Mark for: Overlay Target*. + +image::media/marcoverlay5.png[] + +4. Click *Cataloging>Import Record from Z39.50*. +5. Search for the lead record that you want to overlay within the Z39.50 interface. +6. Select the desired record, and click *Overlay*. + +image::media/marcoverlay6.png[] + +7. The record that you have targeted to be overlaid, and the new record, appear side by side. + +image::media/marcoverlay7.png[] + +8. You can edit the lead record before you overlay the target. To edit the record, click the *Edit Z39.50 Record* button above the lead record. +9. The MARC editor will appear. You can make your changes in the MARC editor, or you can select the *Flat Text Editor* to make changes. After you have edited the record, click *Modify* in the top right corner, and then *Use Edits* in the bottom right corner. Note that the record you are editing is the version from the Z39.50 server not including any changes that would be made as a result of applying the selected merge file. +10. You will return to the side-by-side comparison of the records and then can proceed with the overlay. +11. Once you are satisfied with the record that you want to overlay, select a merge profile from the drop down box, *Choose merge profile*. +12. Click *Overlay*. The overlay will occur, and you will be taken back to the Z39.50 interface. +13. Note that the staff client remembers the last merge overlay profile that you selected, so the next time that you open the interface, it will default to that profile. Simply change the profile to make a different selection. +14. Also note when the merge profile is applied, the Z39.50 record acts as the target of the merge. For example, if your merge profile adds 650 fields, those 650 fields are brought over from the record that already exists in the Evergreen database (i.e., the one that you are overlaying from Z39.50). +15. Also note that merge profiles that contain a preserve field specification are not available to be chosen in this interface, as they would have the effect of reversing which bibliographic record is considered the target of the merge. + +New Admin Settings +^^^^^^^^^^^^^^^^^^ + +1. Go to *Admin>Local Administration>Library Settings Editor>Upload Default Merge Profile (Z39.50 and Record Buckets)*. +2. Select a default merge profile, and *click Update Setting*. The merge profiles that appear in this drop down box are those that are created in *MARC Batch Import/Export*. Note that catalogers will only see merge profiles that are allowed by their org unit and permissions. diff --git a/docs/media/marcoverlay1.png b/docs/media/marcoverlay1.png new file mode 100644 index 0000000000..558397987f Binary files /dev/null and b/docs/media/marcoverlay1.png differ diff --git a/docs/media/marcoverlay2.png b/docs/media/marcoverlay2.png new file mode 100644 index 0000000000..3f124e30fc Binary files /dev/null and b/docs/media/marcoverlay2.png differ diff --git a/docs/media/marcoverlay3.png b/docs/media/marcoverlay3.png new file mode 100644 index 0000000000..0965353a4f Binary files /dev/null and b/docs/media/marcoverlay3.png differ diff --git a/docs/media/marcoverlay4.png b/docs/media/marcoverlay4.png new file mode 100644 index 0000000000..68af923002 Binary files /dev/null and b/docs/media/marcoverlay4.png differ diff --git a/docs/media/marcoverlay5.png b/docs/media/marcoverlay5.png new file mode 100644 index 0000000000..9271bcdcc8 Binary files /dev/null and b/docs/media/marcoverlay5.png differ diff --git a/docs/media/marcoverlay6.png b/docs/media/marcoverlay6.png new file mode 100644 index 0000000000..96cc4d4cca Binary files /dev/null and b/docs/media/marcoverlay6.png differ diff --git a/docs/media/marcoverlay7.png b/docs/media/marcoverlay7.png new file mode 100644 index 0000000000..69c105930b Binary files /dev/null and b/docs/media/marcoverlay7.png differ diff --git a/docs/root.adoc b/docs/root.adoc index de497b77aa..9c5644acfd 100644 --- a/docs/root.adoc +++ b/docs/root.adoc @@ -365,6 +365,8 @@ include::cataloging/record_buckets.adoc[] // Return titles to correct level. :leveloffset: 0 +include::cataloging/merge_overlay_bibs.adoc[] + include::cataloging/physical_char_wizard.adoc[] include::admin/staff_client-return_to_results_from_marc.adoc[] diff --git a/docs/root_cataloging.adoc b/docs/root_cataloging.adoc index 363b6fc668..9349788edd 100644 --- a/docs/root_cataloging.adoc +++ b/docs/root_cataloging.adoc @@ -93,6 +93,8 @@ include::cataloging/record_buckets.adoc[] :leveloffset: -1 +include::cataloging/merge_overlay_bibs.adoc[] + include::cataloging/MARC_batch_edit.adoc[] :leveloffset: 0