Saturday, March 28, 2026

The Surgical Merge: MarcEdit Edition

Preserving Metadata Integrity for the Sirah Research Hub

Merging records in MarcEdit is like performing a surgical transplant: you take the "healthy" metadata from one file and move the "vital" local data (barcodes and URLs) from another into it.

The Scenario: A Practical Example

Imagine you have two separate files for the same 100 Sirah books:

File A (Source)

High-quality bibliography. Perfect titles and Islamic subject headings, but no barcodes.

File B (Merge)

SSMK Library records. Messy titles, but contains unique barcodes and shelf locations.

Goal: The Perfect Master Record

The Step-by-Step Process

1
Open the Merge Tool: Launch MarcEdit and navigate to Tools → Merge Records.
2
Select Your Files: Set File A as your Source and File B as your Merge file. Name your output Sirah_Hub_Final.mrc.
3
Define the "Match Key": Use the ISBN (020 $a) or Title (245 $a) so MarcEdit recognizes which books are identical.
4
Select Specific Data: Only check the boxes for fields you need from File B (e.g., 952 for barcodes, 856 for URLs).
💡 Pro-Tip: Do NOT select fields like 245 (Title) or 100 (Author) in Step 4. You want to keep the "clean" metadata from your Source file, not overwrite it with the "messy" data from the Merge file.

The Final Result (Behind the Scenes)

Feature File A (Source) File B (Merge) Final Merged Result
Title (245) The Life of the Prophet Prophet Life (SSMK) The Life of the Prophet
ISBN (020) 9780123456789 9780123456789 9780123456789
Barcode (952$p) (Empty) ML-100444 ML-100444

Common Troubleshooting

  • "No Matches Found": Standardize your ISBNs first. One file might have dashes while the other does not. Use the MarcEdit ISBN Tool to fix this.
  • Duplicate 952s: Use the "Replace Existing" option in merge settings if your Source file already contains empty placeholder tags.

Merging in MarcEdit is faster and safer than merging in Koha because you can verify 5,000 records in seconds before they ever touch your live catalog.

No comments:

Post a Comment

Display in OPAC of Different datatypes

⚠️ Diagnosis: Your Koha is defaulting to "text" because the Item Type Codes in your ...