Recommended Merge Methods
- Lauren Magnuson (Unlicensed)
- Micah Jeffries (Unlicensed)
- Marcus Jun (Unlicensed)
Background
Merge rules determine how two records will be merged. MARC fields can be added, removed, or replaced.
Policy Statement
This policy applies only to records imported using an import profile (example: vendor records) and records imported from Connexion. This policy does not apply to merge rules for Alma’s Search External Resource functionality. For a discussion of these scenarios, please see Exlibris documentation.
The recommended merge rule is CSU Bib Overlay NZ. For a comparison of this merge rule and others please see this google doc. This merge rule is the primary rule for the Orbis Cascade Alliance. It protects the 001 field (MMS ID) and replaces the 035 if it is an OCLC number. If the 035 is non-OCLC it is protected from being overwritten. It also removes all fields from the existing record and replaces them with all fields in the incoming record.
Best practice recommendations
The merge rule, CSU Bib Overlay NZ is applied to the Connexion integration profile established in the Network Zone and applies to all records imported from Connexion into the NZ.
This merge rule should also be applied to any import profile that imports to the NZ.
Procedures in Alma
The recommended merge rule is shared with all campuses in the CSU and should be selectable in any import profile that imports into the NZ.
Action log
| Section | Point Person | Expected Completion Date | Last action taken | Next action required |
|---|---|---|---|---|
Articulate the need for the policy (background) | Â | |||
Create a Policy Statement | Â | |||
Identify and create best practice recommendations |
| |||
Where applicable, identify and write up procedures in Alma |
|
Tasks to be completed
- Type your task here, using "@" to assign to a user and "//" to select a due date