Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status

IN PROGRESS

Scope

post go-live

Description

provide best practices for resolving multi-matches found in the NZ

Decision

see below

Owning group

[group name] + (email contact)

Approver

PPC

Stakeholders

R = RMFG
A = RMFG
C = CDL
I = Campuses

Decision-making process

Priority

Due date

Recommendation

Campus catalogers will run into situations where they have an OCLC record that now matches multiple bibliographic records in the Alma NZ due to merges in OCLC. In order to keep the Alma NZ in line with the OCLC database as much as possible, campus catalogers can resolve these multi-matches without needing to notify any system-wide groups. Each campus should determine which staff are able to resolve multi-matches since it involves merging records and moving inventory for other campuses. Generally, catalogers should only resolve matches for resources that their campus holds. In addition, catalogers can make updates in Connexion and then wait for the WorldCat daily updates to merge the records at the system-wide level. Lastly, RMFG will issue additional documentation to ensure bound-with relationships are identified and retained to the extent possible.

Campuses should enable the following configuration with the settings below:

How to resolve multi-matches:

In the Alma Metadata Editor (MDE):   

        Locate the matched records in the Alma NZ and push them into the MDE

       

In the MDE, open the records using the split-screen (open the record that you want to keep first). You may need to do this more than once if there are more than two matches.

With both records open, go to “Record actions” and select “Merge & Combine”

You’ll get a pop-up asking for a merge routine. Select “allUC MDE External Search Merge #1” and then merge preview:

Check that everything looks the way you want and then click “ok”


Finally, make sure that the secondary record is set to “suppress”

Do not choose “delete” here.

And then click “ok” one more time. 

You should now have 2 NZ-linked records but one of them will be suppressed. Click on the suppressed record and in “record actions” select “enhance the record” and select “allUC Mark bib for deletion” to flag the record for deletion by CDL. 


  • Handling 035s

    • Should we move the 035 data to a new field after merging so that people can overlay the record?

      • Propose moving into 935

       


Via import profile

    Campus import profiles do not allow “merge & combine” inventory when “Use Network Zone” is checked. In addition, IZ-only import profiles will not recognize NZ-linked multi-matches.  Campuses are able to resolve IZ-only multi-matches using import profiles but multi-matches for NZ-linked records have to be resolved in the MDE or via an import profile within the NZ. This will most commonly happen during the WorldCat daily updates for non-serials and will be done by CDL staff using an import profile that will automatically merge & combine inventory. For non-serials, campus catalogers have the option to either wait for the daily updates to resolve the multi-match or do it themselves in line with the policy and procedure outlined above. Multi-matches for serials will need to be resolved manually as outlined above. 

Reasoning

Background

Dependencies

Questions to consider

Action Log

Action/Point Person

Expected Completion Date

Notes

Status

  • No labels