1. Match and Merge Routine in the import profile
Yoel Kortick
Senior Librarian

2. The four sample records
Introduction
The four sample records
The import profile
The results
Summary

3. Rules - A typical merge routine for importing from OCLC Connexion.docx
Introduction
See also the following presentations at
Rules - A typical merge routine for importing from OCLC Connexion.docx
Rules - Merge rules and routines.pptx
Rules - Merge rules syntax for copy cataloging.docx
Rules - Merge Rules - How to make a merge rule and routine which will save the 9XX fields of record already in Alma.docx

4. Search External Resources
Introduction
As is explained in the aforementioned documents: The logic of the merge routine differs for
Import Profiles
Search External Resources
This specific presentation is showing an example using the import profile.
By looking at the setup of the import profile, as well as the characteristics of the existing and new records in the input file, we will see the logic used by the import profile.

5. The four sample records
Introduction
The four sample records
The import profile
The results
Summary

6. Title “Work in progress: building feminist culture”
Example one
Already exists in Alma
Title “Work in progress: building feminist culture”
035 $$a (DLC)###
Here it is in the Alma Metadata Editor

7. Example one
Here is the same record in the MARC XML input file
Title is “Works in progress” in the 245 instead of “Work in progress”
900 field has “Feminist Studies” instead of “Gender Studies”

8. Title “Feminism, the left, and postwar literary culture”
Example two
Already exists in Alma
Title “Feminism, the left, and postwar literary culture”
035 $$a (OCoLC)ocn
Here it is in the Alma Metadata Editor

9. Example two
Here is the same record in the MARC XML input file
It has “post-war literary culture” in the 245 instead of “postwar literary culture”
It has “Feminist Studies” in the 900 instead of “Gender Studies”

10. This record does not exist in Alma
Example three
This record does not exist in Alma
Here is the record in the input file
Title “Women in Eighteenth-Century Scotland: intimate, intellectual and public lives”
035 $$a (OCoLC)ocn

11. This record does not exist in Alma
Example four
This record does not exist in Alma
Here is the record in the input file
Title “Painting, literature, and film in Columbian feminine culture, ”
035 $$a (OCoLC)ocn

12. The four sample records
Introduction
The four sample records
The import profile
The results
Summary

13. The match profile matches on 035
The import profile
The match profile matches on 035

14. These are typical other match routines which could have been chosen
The import profile
These are typical other match routines which could have been chosen

15. The import profile
The match actions state that when there is a match it merges and does merge method “Overlay all fields but local”

16. Here are some other default sample merge methods
The import profile
Here are some other default sample merge methods

17. When there is no match it imports the record
The import profile
When there is no match it imports the record

18. The import profile
Note that, as previously pointed out, we are choosing merge method “Overlay all fields but local”.
This means that a field such as 245 will be overlaid, but a field such as 900 will not be overlaid.
245 is not local, 900 is local.

19. The import profile
The method ‘Overlay all fields but local” uses a merge routine like this.
All fields except 001, 035 and anything starting with 9 will be overlaid
See the aforementioned documents for further details regarding the merge rules syntax.

20. The four sample records
Introduction
The four sample records
The import profile
The results
Summary

21. The import profile runs and completes and we will view the report
The results
The import profile runs and completes and we will view the report

22. The results 2 records had a match and were imported
It is possible to preview the matched records, build a set of the matched records, or download them to a MARC file.

23. The results
A total of 4 records were imported
2 records had a match and were merged
2 records had no match and were imported
For all types of results it is possible to preview the records, build a set of the records, or download them to a MARC file.

24. The two records which had no match were imported “as is”
The results
The two records which had no match were imported “as is”

25. The results
The two records which did have a match were imported and merged. The 245 title fields changed

26. The title changed but the 900 field did not change.
The results
The title changed but the 900 field did not change.
Here is first merged record
Original record in Alma had “Work in progress” and the input file had “Works in progress”
Input file had “Feminist Studies”. The 900 field did not change.

27. The title changed but the 900 field did not change.
The results
The title changed but the 900 field did not change.
Here is second merged record
Original record in Alma had “postwar literary culture” (no dash). The input file had “post-war literary culture”
Input file had “Feminist Studies”. The 900 field did not change.

28. The four sample records
Introduction
The four sample records
The import profile
The results
Summary

29. Summary The import profile can be used to handle records which
Already in the repository.
Do not yet exist in the repository (but are in input file).
In the case of records which do already exist in the repository there are four options:
Merge
Overlay
Do Not Import
Import New Record
When the option to Merge is chosen various merge routines may be used, both default “out of the box” as well as “customized” routines.

30. Summary
In the case of records which do not yet exist in the repository (but are in input file) there are two options
Do Not Import
Import

31. Summary
By using the “Merge” option for existing records the institution can enrich the records in the repository.
By using a routine such as the one we saw here, it is possible to enrich the records yet not lose locally made changes such as those in local fields.