1 Batch Importing MARC Records
2 ----------------------------
4 The cataloging module includes an enhanced MARC Batch Import interface for
5 loading MARC records. This interface allows you to specify match points
6 between incoming and existing records, to specify MARC fields that should be
7 overlaid or preserved, and to only overlay records if the incoming record is
8 of higher quality than the existing record. Records are added to a queue where
9 you can apply filters that enable you to generate any errors that may have
10 occurred during import. You can print your queue, email your queue, or export
11 your queue as a CSV file.
16 To use match sets to import records, you will need the following permission:
18 ADMIN_IMPORT_MATCH_SET
21 Record Display Attributes
22 ~~~~~~~~~~~~~~~~~~~~~~~~~
24 This feature enables you to specify the tags and subfields that will display in
25 records that appear in the import queue.
31 This feature enables you to create custom match points that you can use to
32 accurately match incoming records with existing catalog records.
37 In this example, to demonstrate matching on record attributes and MARC tags and
38 subfields, we will create a record match set that defines a match based on the
39 title of the record, in either the 240 or 245, and the fixed field, Lang. You
40 can add multiple record attributes and MARC tags to customize a record match
44 1) Click *Cataloging -> MARC Batch Import/Export*.
46 2) Create a new record match set. Click *Record Match Sets -> New Match Set*.
48 3) Enter a name for the record match set.
50 4) Select an *Owning Library* from the drop down menu. Staff with permissions
51 at this location will be able to use this record match set.
53 5) Select a *Match Set Type* from the drop down menu. You can create a match
54 set for authority records or bibliographic records.
59 image::media/Batch_Importing_MARC_Records1.jpg[Batch_Importing_MARC_Records1]
62 7) The screen will refresh to list the record match set that you created. Click
63 the link to the record match set.
65 8) Create an expression that will define the match points for the incoming
66 record. You can choose from two areas to create a match: *Record Attribute* or
67 *MARC Tag and Subfield*. You can use the Boolean operators AND and OR to
68 combine these elements to create a match set.
70 9) Select a *Record Attribute* from the drop-down menu.
72 10) Enter a *Match Score.* The *Match Score* indicates the relative importance
73 of that match point as Evergreen evaluates an incoming record against an
74 existing record. You can enter any integer into this field. The number that
75 you enter is only important as it relates to other match points. Recommended
76 practice is that you create a match score of one (1) for the least important
77 match point and assign increasing match points to the power of 2 to working
78 points in increasing importance.
80 11) Check the *Negate?* box if you want to negate the match point. Checking
81 this box would be the equivalent of applying a Boolean operator of NOT to the
84 image::media/Batch_Importing_MARC_Records2.jpg[Batch_Importing_MARC_Records2]
88 13) Drag the completed match point under the folder with the
89 appropriately-named Boolean folder under the Expression tree.
91 image::media/Batch_Importing_MARC_Records3.jpg[Batch_Importing_MARC_Records3]
93 The match point will nest underneath the folder in the Expression tree.
95 image::media/Batch_Importing_MARC_Records4.jpg[Batch_Importing_MARC_Records4]
97 14) Enter another *Boolean Operator* to further refine your match set.
99 15) Click *Boolean Operator*.
101 16) Select the *OR* operator from the drop down menu.
105 18) Drag the operator to the expression tree.
107 image::media/Batch_Importing_MARC_Records5.jpg[Batch_Importing_MARC_Records5]
109 19) Click *MARC Tag and Subfield*.
111 20) Enter a *MARC tag* on which you want the records to match.
113 21) Enter a *subfield* on which you want the records to match.
115 22) Enter a *Match Score.* The *Match Score* indicates the relative importance
116 of that match point as Evergreen evaluates an incoming record against an
117 existing record. You can enter any integer into this field. The number that
118 you enter is only important as it relates to other match points. Recommended
119 practice is that you create a match score of one (1) for the least important
120 match point and assign increasing match points to the power of 2 to working
121 points in increasing importance.
123 23) Check the *Negate?* box if you want to negate the match point. Checking
124 this box would be the equivalent of applying a Boolean operator of NOT to the
129 image::media/Batch_Importing_MARC_Records6.jpg[Batch_Importing_MARC_Records6]
131 25) Drag the completed match point under the folder with the
132 appropriately-named Boolean folder under the Expression tree. The Expression
133 will build across the top of the screen.
135 26) Add additional MARC tags or record attributes to build the expression tree.
137 27) Click *Save Changes to Expression*.
139 image::media/Batch_Importing_MARC_Records7.jpg[Batch_Importing_MARC_Records7]
144 Replace Mode enables you to replace an existing part of the expression tree
145 with a new record attribute, MARC tag, or Boolean operator. For example, if
146 the top of the tree is AND, in replace mode, you could change that to an OR.
148 1) Create a working match point.
150 2) Click *Enter replace mode*.
152 3) Highlight the piece of the tree that you want to replace.
154 4) Drag the replacement piece over the highlighted piece.
156 5) Click *Exit Replace Mode*.
162 1) Set the *Quality Metrics for this Match Set*. Quality metrics are used to
163 determine the overall quality of a record. Each metric is given a weight and
164 the total quality value for a record is equal to the sum of all metrics that
165 apply to that record. For example, a record that has been cataloged thoroughly
166 and contains accurate data would be more valuable than one of poor quality. You
167 may want to ensure that the incoming record is of the same or better quality
168 than the record that currently exists in your catalog; otherwise, you may want
169 the match to fail. The quality metric is optional.
171 2) You can create quality metrics based on the record attribute or the MARC Tag
174 3) Click *Record Attribute.*
176 4) Select an attribute from the drop down menu.
178 5) Enter a value for the attribute.
180 6.) Enter a match score. You can enter any integer into this field. The number
181 that you enter is only important as it relates to other quality values for the
182 current configuration. Higher scores would indicate increasing quality of
183 incoming records. You can, as in the expression match score, increase the
184 quality points by increasing subsequent records by a power of 2 (two).
188 image::media/Batch_Importing_MARC_Records8.jpg[Batch_Importing_MARC_Records8]
193 The *Import Records* interface incorporates record match sets, quality metrics,
194 more merging options, and improved ways to manage your queue. In this example,
195 we will import a batch of records. One of the records in the queue will
196 contain a matching record in the catalog that is of lower quality than the
197 incoming record. We will import the record according to the guidelines set by
198 our record match set, quality metrics, and merge/overlay choices that we will
202 1) Select a *Record Type* from the drop down menu.
204 2) Create a queue to which you can upload your records, or add you records to
205 an existing queue. Queues are linked to match sets and a holdings import
206 profile. You cannot change a holdings import or record match set for a queue.
208 3) Select a *Record Match Set* from the drop down menu.
210 4) Select a *Holdings Import Profile* if you want to import holdings that are
211 attached to your records.
213 5) Select a *Record Source* from the drop down menu.
215 6) Select a *Merge Profile*. Merge profiles enable you to specify which tags
216 should be removed or preserved in incoming records.
218 7) Choose one of the following import options if you want to auto-import
221 a. *Merge on Single Match* - Using the Record Match Set, Evergreen will only
222 attempt to perform the merge/overlay action if only one match was found in the
225 b. *Merge on Best Match* - If more than one match is found in the catalog for a
226 given record, Evergreen will attempt to perform the merge/overlay action with
227 the best match as defined by the match score and quality metric.
229 NOTE: Quality ratio affects only the *Merge on Single Match* and *Merge on Best
232 8) Enter a *Best/Single Match Minimum Quality Ratio.* Divide the incoming
233 record quality score by the record quality score of the best match that might
234 exist in the catalog. By default, Evergreen will assign any record a quality
235 score of 1 (one). If you want to ensure that the inbound record is only
236 imported when it has a higher quality than the best match, then you must enter
237 a ratio that is higher than 1. For example, if you want the incoming record to
238 have twice the quality of an existing record, then you should enter a 2 (two)
239 in this field. If you want to bypass all quality restraints, enter a 0 (zero)
243 9) Select an *Insufficient Quality Fall-Through Profile* if desired. This
244 field enables you to indicate that if the inbound record doees not meet the
245 configured quality standards, then you may still import the record using an
246 alternate merge profile. This field is typically used for selecting a merge
247 profile that allows the user to import holdings attached to a lower quality
248 record without replacing the existing (target) record with the incoming record.
249 This field is optional.
251 10) *Browse* to find the appropriate file, and click *Upload*. The files will
252 be uploaded to a queue.
254 image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
256 11) The screen will display records that have been uploaded to your queue.
258 image::media/Batch_Importing_MARC_Records15.jpg[Batch_Importing_MARC_Records15]
260 12) If Evergreen indicates that matching records exist, then click the
261 *Matches* link to view the matching records. Check the box adjacent to the
262 existing record that you want to merge with the incoming record.
264 image::media/Batch_Importing_MARC_Records10.jpg[Batch_Importing_MARC_Records10]
266 13) Click *Back to Import Queue*.
268 14) Check the boxes of the records that you want to import, and click *Import
269 Selected Records*, or click *Import All Records*.
271 15) A pop up window will offer you the same import choices that were present on
272 the *Import Records* screen. You can choose one of the import options, or
275 image::media/Batch_Importing_MARC_Records9.jpg[Batch_Importing_MARC_Records9]
277 16) The screen will refresh. The *Queue Summary* indicates that the record was
278 imported. The *Import Time* column records the date that the record was
281 image::media/Batch_Importing_MARC_Records12.jpg[Batch_Importing_MARC_Records12]
283 17) Search the catalog to confirm that the record was imported.
285 image::media/Batch_Importing_MARC_Records14.jpg[Batch_Importing_MARC_Records14]