[Evergreen-catalogers] Creating a Merge Profile That Only Adds Non-Duplicate MARC Fields?

[Jennifer Pringle]

Hello William,

I don't think it's currently possible.  We'd love to see the ability to do that with subject headings for incoming records to avoid duplication.

It's included in this bug - https://bugs.launchpad.net/evergreen/+bug/2023599 (and someone has commented to say they'd like the same for 020s)

Jennifer
--
Jennifer Pringle (she/her)
Co-op Support - Training Lead
BC Libraries Cooperative
Toll-free: 1-888-848-9250
Email:jennifer.pringle at bc.libraries.coop
Website: http://bc.libraries.coop

Gratefully acknowledging that I live and work in the unceded Traditional Territory of the St'at'yemc Nations.

From: Evergreen-catalogers <evergreen-catalogers-bounces at list.evergreen-ils.org> On Behalf Of Szwagiel, Will via Evergreen-catalogers
Sent: Monday, April 8, 2024 10:01 AM
To: Evergreen Community Catalogers <evergreen-catalogers at list.evergreen-ils.org>
Cc: Szwagiel, Will <william.szwagiel at dncr.nc.gov>
Subject: [Evergreen-catalogers] Creating a Merge Profile That Only Adds Non-Duplicate MARC Fields?

Good afternoon,

We are currently working on a project to try and streamline the bibliographic record merging process to assist catalogers with performing manual merges of records they deem duplicates.  To that end, I have been working on some potential merge profiles they can use, because there are certain MARC fields we try to make sure are included on the final, merged record.

For example, because we do not separate hardcover and paperback versions of a book, we instruct catalogers to include the ISBNs for both versions on the record.  It is easy enough to create a merge profile that adds all =020 MARC fields to the final, merged record, but is it possible to create a merge profile that only adds the non-duplicate fields?  I have been playing around with different permutations of the merge profile, and I cannot seem to find one that works (though it is entirely possible I am overlooking an incredibly simple solution).

I can only seem to create a profile that adds all of the =020 MARC fields, so the final, merged record ends up with repeated fields.  I know worst case scenario we can go in and manually delete the duplicate fields after the fact, but I am hoping there is a way to avoid that, if at all possible.

Thank you in advance for your help.


William C. Szwagiel

NC Cardinal Project Manager

State Library of North Carolina

william.szwagiel at ncdcr.gov<mailto:william.szwagiel at ncdcr.gov> | 919.814.6721

https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal

109 East Jones Street  | 4640 Mail Service Center

Raleigh, North Carolina 27699-4600

The State Library is part of the NC Department of Natural & Cultural Resources.

Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.



________________________________

Email correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official.
This message originated from outside the M365 organisation. Please be careful with links, and don't trust messages you don't recognise.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20240408/2be64978/attachment-0001.htm>