Differences

This shows you the differences between two versions of the page.

Link to this comparison view

plp:xc_opts [2013/09/04 16:35]
richard
plp:xc_opts [2013/09/04 16:36] (current)
richard [About CIP]
Line 1: Line 1:
 +====== PLP: Crosscheck Options ======
 +
 +The crosscheck options are a set of boolean values that modify the behavior of some of the crosschecks; these options are accessed from the main Match Rules form.
 +
 +The default crosscheck options form looks like this:
 +
 +{{:plp:xcopts.jpg|}}
 +
 +**CIP reduce crosschecks**
 +
 +If this option is selected, and the records being compared match the following criteria:
 +  * 010$a present and matches
 +  * 040$a = DLC
 +
 +and a configured crosscheck is not in the following list: 
 +  * XTITL
 +  * XRTYP
 +  * X245H
 +  * XBLEV
 +  * XMTYP
 +  * XDVDR
 +  * XFORM
 +  * XVTYP
 +  * XISSN
 +
 +then that (configured) crosscheck will be skipped.
 +\\
 + 
 +**Electronic resource exceptions**
 +
 +Records for electronic resources often cause problems because of their similarity to records for the print items from which they were (often) derived. To reduce the number of ER items that are sent to MCU for manual review, configure the following crosscheck options. 
 +
 +The first two options try to identify cases where one record is an electronic resource, and the other represents a print resource, and, in those cases, treat the items as 'NoMatch' instead of 'XCFail'.
 +
 +1. If XFORM fails force NoMatch if one record is ER and the other record is for print 
 +
 +If the XFORM crosscheck (008/23) fails, and one record has a GMD of 'electronic resource', and the other record has either no GMD, or a GMD of 'microform', then redirect record from XCFail to NoMatch
 +
 +2. If X245H fails force NoMatch if one record is ER and the other record is for print 
 +
 +If the X245H crosscheck (GMD) fails, and one record has a GMD of 'electronic resource', and the other record has either no GMD, or a GMD of 'microform', then redirect record from XCFail to NoMatch
 +
 +The remaining two options provide conditions for handling duplicate ER records from different vendors. This exception has been split into two separate options to facilitate separate policies for e-books and e-serials. In each case, you can opt to:
 +  - Take no special action
 +  - Merge the duplicate records (ie. send to 'Match')
 +  - Retain the duplicate records (ie. send to 'NoMatch')
 +
 +The processing is the same in each of the two options:
 +
 +  * If all crosschecks pass except for XAUTH, which fails only because of a differing 710((ie all other authors in 100/700 matched))
 +  * If both records have a form code of 's' (electronic resource)
 +  * If both records have 856 fields and they do not match, then
 +\\
 +Follow the condition selected (no action, match, or no-match). Note that this special exception requires that XAUTH, XFORM, and XBLEV all be present in the Match Rules.
 +
 +===== About CIP =====
 +
 +Several of the options above refer to CIP (Cataloging-in-publication), which indicates a record that is not complete. The 'CIP-ness' of a record is True if either of the following conditions is met:
 +
 +  - the record has 300$a='p.cm'
 +  - Ldr/17 is '8' and Tag 263 is present
 +
 +
  
plp/xc_opts.txt ยท Last modified: 2013/09/04 16:36 by richard
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed