Home → Cataloging Bibliographic Records → Merging Bib Records → Duplicate Records and Merging
Last Updated 02/17/2026
On This Page
Bibliographic catalogers may need to merge duplicate records, or may choose to use the merge function when importing new records or after editing a record in MARCEdit. In all cases, catalogers should follow a set of guidelines to ensure their merges are correct.
When Bibliographic Catalogers discover,or are shown, duplicate records, they should merge those records to help keep the catalog clean and ensure efficient hold fulfillment. Additionally, when importing new records or improving poor records, catalogers may choose to merge new or improved records with existing records, rather than working off the original record.
There are three scenarios that could require merging:
In all cases, a bibliographic cataloger should carefully evaluate the record before merging records.
NOTE: Make sure you clean up the resulting merged record to comply with current NC Cardinal Best Practices.
When merging records, any Title level holds from the deleted record will migrate to the lead record.
Copy level holds and Metarecord holds will remain on the Holds View list for the deleted record. However, they will be actively in the queue for either the designated item (for copy level holds), or any title records still combined in the metarecord. Their holds will be fulfilled in queue order.
To reduce confusion, you can avoid these lingering holds.
Follow the instructions to transfer the holding for the designated copy in the copy hold. The hold will transfer with the holdings. Merge the records as normal.
The metarecord hold will only show up on the Hold View list for the lead record in the metarecord. Once you have determined that metarecord hold requests are active on one of the records you plan to merge, select that record as the lead record when merging. This will retain all active metarecord hold requests in the Hold View tab of the merged record.