AC Wiki - User contributions [en]

Marcadia Profile Guide

2013-09-10T16:39:49Z

Djulien: Created page with "==About== The Marcadia Profile was created to help simplify and explain the complex options available from Backstage Library Works when choosing to find the one best, most conten..."

==About==
The Marcadia Profile was created to help simplify and explain the complex options available from Backstage Library Works when choosing to find the one best, most content rich bibliographic record within the OCLC Worldcat and/or Institution database. The profile covers topics such as: Perfect and Acceptable match return criteria, required matching criteria, hitting on 'magic-number' fields such as the 010, 020, and 022, hitting on title text and other fields, validation, keep options, and reports.

==Sections - Record Deduplication==
*[[Marcadia_1.0|Step 1 - Database]] - File transfer and data formats
*[[Marcadia_2.0|Step 2 - Match Criteria]] - Options for searching your bibliographic records
*[[Marcadia_3.0|Step 3 - Perfect Match]] - Criteria for Perfect Matches
*[[Marcadia_4.0|Step 4 - Acceptable Match]] - Criteria for Acceptable Matches
*[[Marcadia_5.0|Step 5 - Optional]] - Access field updates
*[[Marcadia_6.0|Step 6 - Ongoing]] - Ongoing options

==Revisions==
In an effort to consolidate questions and streamline the intuitive flow of the guide, we have recently updated the wiki and printed versions of the guide. We hope these changes complement the new version of the online profile.

The current version was edited September 2013.

[[category:Profile Guide]]

Dedupe 3.14

2013-04-29T15:29:54Z

Djulien: /* Default */

==Dedupe 3.14: Group 2 - 260 $c - Date (Verify)==
[[Image:d3-14.png]] 
=== Description ===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield c - Date====
The date of publication, distribution, etc. is in the 260$c.

260 $a New York :$b Pelham Press, $c 1953.
260 $a Boston :$b Imperial Press, $c 1967-1970.

When $c contains more than a year (either month and year, or month, day, and year), the date is in the order month/year or month/day/year. A comma is used to set off the month/day from the year, but not to separate a month from the year; standard abbreviations are used for the names of the months in most cases.


260 $a New York, $c Aug. 15, 1967.
260 $a Boston :$b Imperial Press, $c Sept. 1967.

Some records have dates lacking one or more digits so the 260$c date often uses square brackets around the date with a hyphen for each missing digit in the date.

260 $a New York :$b Willemsen,$c[196-]
260 $a New York, $c [19--?]

NOTE: The 260$c date can have many variations containing printing dates, copyright dates, multiple dates, open ended dates, etc. This should be represented in the 008 field positions 7-14. If you feel that your 008 date positions do not represent what is in the 260$c, please contact your Backstage project manager for possible solutions.

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "1966-1967." in one record, "1966-" on the other record : both truncated to "1966-" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "1967" will find a potential match on "1966-1967."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 260$c within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 260$c within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 260 $c publication date must verify and must exist in both records (full, naco)
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.14

2013-04-29T15:29:41Z

Djulien: /* Defaults */

==Dedupe 3.14: Group 2 - 260 $c - Date (Verify)==
[[Image:d3-14.png]] 
=== Description ===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield c - Date====
The date of publication, distribution, etc. is in the 260$c.

260 $a New York :$b Pelham Press, $c 1953.
260 $a Boston :$b Imperial Press, $c 1967-1970.

When $c contains more than a year (either month and year, or month, day, and year), the date is in the order month/year or month/day/year. A comma is used to set off the month/day from the year, but not to separate a month from the year; standard abbreviations are used for the names of the months in most cases.


260 $a New York, $c Aug. 15, 1967.
260 $a Boston :$b Imperial Press, $c Sept. 1967.

Some records have dates lacking one or more digits so the 260$c date often uses square brackets around the date with a hyphen for each missing digit in the date.

260 $a New York :$b Willemsen,$c[196-]
260 $a New York, $c [19--?]

NOTE: The 260$c date can have many variations containing printing dates, copyright dates, multiple dates, open ended dates, etc. This should be represented in the 008 field positions 7-14. If you feel that your 008 date positions do not represent what is in the 260$c, please contact your Backstage project manager for possible solutions.

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "1966-1967." in one record, "1966-" on the other record : both truncated to "1966-" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "1967" will find a potential match on "1966-1967."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 260$c within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 260$c within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 260 $c publication date must verify and must exist in both records, (full, naco)
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.13

2013-04-29T15:27:58Z

Djulien: /* Defaults */

== Dedupe 3.13: Group 2 - 260 $b - Publisher (Verify)==
[[Image:d3-13.png]] 
=== Description ===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield b - Publisher name====
The name of publisher or distributor is in the $b and can be repeated.


260 $a New York :$b Pelham Press :$b Distributed by Grant Educational, $c 1976.
260 $a Boston :$b Printed for the CLA by the Morriss Print. Co., $c 1925.
260 $a Paris :$b Gauthier-Villars ;$a Chicago :$b University of Chicago Press, $c 1975

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "Pelham Press" in one record, "Pelham" on the other record : both truncated to "Pelham" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "Press" will find a potential match on "Pelham Press."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 260$b within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 260$b within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 1 (010, 020, 022)
|- style="background:#CCFFFF; font-size: 110%;"
| || 260 $b publisher must verify if exists in both records (full, naco); checking 2 words
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.12

2013-04-29T15:27:03Z

Djulien: /* Defaults */

==Dedupe 3.12: Group 2 - 245 $h - GMD (Verify)==
[[Image:d2-9.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page. Only subfield h will be used for this parameter.

Every MARC record must have a 245 field, but not necessarily a subfield h.

====subfield h - Medium====
This subfield describes the medium, or form, of the work being catalogued. The terms used in $h are called ''General material designations'', or GMDs, in AACR2. Subfield h is normally used only for various AV formats. When no $h is present, the catalogued item is presumed to be a book, serial, or other printed text item.

When subfield is used, the GMD is enclosed within square brackets. There is no punctuation before $h, and $h is not capitalized.

The terms deemed appropriate for $h are:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| activity card || art original || art reproduction || braille
|- align="left"
| chart || computer file || diorama || filmstrip
|- align="left"
| flash card || games || globe || interactive multimedia
|- align="left"
| kit || manuscript || map || microform
|- align="left"
| microscope slide || model || motion picture || music
|- align="left"
| picture || realia || slide || sound recording
|- align="left"
| technical drawing || toy || transparency || videorecording
|}
<div style=clear:both></div> 

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$h within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$h within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 245 $h must verify if field exists in both records (full, naco)
|}
<div style=clear:both></div> 
*NOTE: If your collections contain a large amount of AV material (which have been known to vary between collections), please consult with your Backstage project manager to ensure that the best profile parameters are being used.

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.11

2013-04-29T15:26:31Z

Djulien: /* Defaults */

== Dedupe 3.11: Group 2 - 245 $n, $p - Title (Verify)==
[[Image:d2-8.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page. Subfields n and p will be used for this parameter.

Every MARC record must have a 245 field, but not necessarily a subfield n and/or p.

====subfield n - Number of part/section of a work====
If a book includes only a part or section of a larger work, the number of that part or section may be entered in $n. Numbering includes letters as well as numbers, and any other designation of sequence.


245 $a Divine comedy. $n Third part.
245 $a Travels through the orient. $n Volume 2, pt. 4.

====subfield p - Name of part/section of a work====


245 $a Travels through the orient. $n Volume 2, $p Burma.
245 $a New England byways. $n Part 1, $p Vermont. $n Part 2, $p Massachusetts

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$n and $p subfields within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$n and $p subfields within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 245 $n, $p titles must verify if fields exist in both records (full, naco)
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.10

2013-04-29T15:25:36Z

Djulien: /* Defaults */

==Dedupe 3.10: Group 2 - 245 $a, $b - Title (Verify)==
[[Image:d2-7.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page.

Every record must have a 245 tag.

Subfields a and b will be used for this parameter. If only subfield a is wanted to be used, or if other subfields are to be added other than subfields $n, $p and $h, please use section 2-13 of the dedupe profile to add this information.

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$a and $b subfields within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$a and $b subfields within the verify method chosen above.

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 245 $a, $b main entry must verify (full, naco); all characters are considered
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.7

2013-04-08T15:20:39Z

Djulien: /* LCCN */

==Dedupe 3.7: Group 2 - 010 $a - LCCN (Verify)==
[[Image:d3-7.png]] 
===LCCN===
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.

'''LCCN - 010 subfield a:'''
For the Library of Congress Control Number, the subfield a will be used as default. For searching only (not changed in the final record), this field will be normalized. This will remove extra spaces, punctuation and extra data that is usually contained in a different subfield.

*Examples of LCCN normalization: 

Example 1: ###755262 becomes 75005262
Example 2: ###80020863 /AC/r86 becomes 80020863ACr86 and 80020863
Both will be searched to find a potential match.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 010 $a LCCN is not used as a default verification point
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.7

2013-04-08T15:20:15Z

Djulien: /* LCCN */

==Dedupe 3.7: Group 2 - 010 $a - LCCN (Verify)==
[[Image:d3-7.png]] 
===LCCN===
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.

'''LCCN - 010 subfield a:'''
For the Library of Congress Control Number, the subfield a will be used as default. For searching only (not changed in the final record), this field will be normalized. This will remove extra spaces, punctuation and extra data that is usually contained in a different subfield.

*Examples of LCCN normalization: 

Example 1: ###755262 becomes 75005262
Example 2: ###80020863 /AC/r86 becomes 80020863ACr86 and 80020863
Both will be searched to find a potential match.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 010 $a LCCN is not used as a default verification point
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.7

2013-04-08T15:17:49Z

Djulien: /* Default */

==Dedupe 3.7: Group 2 - 010 $a - LCCN (Verify)==
[[Image:d3-7.png]] 
===LCCN===
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.

'''LCCN - 010 subfield a:'''
For the Library of Congress Control Number, the subfield a will be used as default. For searching only (not changed in the final record), this field will be normalized. This will remove extra spaces, punctuation and extra data that is usually contained in a different subfield.

*Examples of LCCN normalization: 

Example 1: ###755262 '''becomes''' 75005262
Example 2: ###80020863 /AC/r86 '''becomes''' 80020863ACr86 and 80020863
Both will be searched to find a potential match.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 010 $a LCCN is not used as a default verification point
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.8

2013-04-08T15:16:46Z

Djulien: /* Default */

==Dedupe 3.8: Group 2 - 020 $a - ISBN (Verify)==
[[Image:d3-8.png]] 
===International Standard Book Number (ISBN/020)===
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

For comparing the ISBN, the normalization will remove all spaces and punctuation and will do a special normalization for the ISBN to standardize it. This normalization only happens in the compare of the records within the program, not in the output.

===Defaults===
The default for verifying on the 020 (ISBN) within Hit Group 2 (245) is as follows:
#Must verify if field exists in both records
#FULL method
#NACO normalization
===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 020 $a ISBN must verify if exists in both records (full, naco)
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.9

2013-04-08T15:16:06Z

Djulien: /* Defaults */

==Dedupe 3.9: Group 2 - 1XX $a - Main entry (Verify)==
[[Image:d3-9.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.'''

'''PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

'''WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 1XX $a main entry must verify if it exists in both records (full, naco); 1 word must verify
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.7

2013-04-08T15:14:35Z

Djulien: /* Default */

==Dedupe 3.7: Group 2 - 010 $a - LCCN (Verify)==
[[Image:d3-7.png]] 
===LCCN===
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.

'''LCCN - 010 subfield a:'''
For the Library of Congress Control Number, the subfield a will be used as default. For searching only (not changed in the final record), this field will be normalized. This will remove extra spaces, punctuation and extra data that is usually contained in a different subfield.

*Examples of LCCN normalization: 

Example 1: ###755262 '''becomes''' 75005262
Example 2: ###80020863 /AC/r86 '''becomes''' 80020863ACr86 and 80020863
Both will be searched to find a potential match.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 010 LCCN is not used as a default verification point
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.8

2013-04-08T15:12:59Z

Djulien: /* Defaults */

==Dedupe 3.8: Group 2 - 020 $a - ISBN (Verify)==
[[Image:d3-8.png]] 
===International Standard Book Number (ISBN/020)===
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

For comparing the ISBN, the normalization will remove all spaces and punctuation and will do a special normalization for the ISBN to standardize it. This normalization only happens in the compare of the records within the program, not in the output.

===Defaults===
The default for verifying on the 020 (ISBN) within Hit Group 2 (245) is as follows:
#Must verify if field exists in both records
#FULL method
#NACO normalization
===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || Full method verify on 020 if it exists in both records; NACO normalization
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.7

2013-04-08T15:11:28Z

Djulien: /* Default */

==Dedupe 3.7: Group 2 - 010 $a - LCCN (Verify)==
[[Image:d3-7.png]] 
===LCCN===
LC changed the structure of the LCCN beginning on Jan. 1, 2001 in order to accommodate a four-digit year. The length of the control number remains 12 characters as it was prior to the change. However, in the old LCCN structure (A), suffixes were occasionally used. Under the new LCCN structure (B), the location of elements is slightly altered to accommodate a four-digit year. Under both structures, the prefix, year and serial number are the basic elements required to make a LCCN unique.

'''LCCN - 010 subfield a:'''
For the Library of Congress Control Number, the subfield a will be used as default. For searching only (not changed in the final record), this field will be normalized. This will remove extra spaces, punctuation and extra data that is usually contained in a different subfield.

*Examples of LCCN normalization: 

Example 1: ###755262 '''becomes''' 75005262
Example 2: ###80020863 /AC/r86 '''becomes''' 80020863ACr86 and 80020863
Both will be searched to find a potential match.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| ||Do not verify on the 010
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.6

2013-04-05T20:12:50Z

Djulien: /* Defaults */

==Dedupe 3.6: Group 2 - 008 Position 23 (Verify)==
[[Image:d2-5.png]] 
=== 008 position 23 -- Form of item ===
This fixed field position indicates the form of the catalogued item. It can include:
*'''''blank''''' - none of the following
*'''a''' - microfilm
*'''b''' - microfiche
*'''c''' - microopaque/microcard
*'''d''' - large print
*'''f''' - braille
*'''r''' - regular print reproduction (eye-readable print, such as a photocopy, Xerox, facsimile)
*'''s''' - electronic
*'''| [pipe]''' - no attempt to code

Choosing to verify on the 008 position 23 allows for stricter matching parameters, especially in cases where the collection contains ''large print'' and ''electronic'' data.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 008[23] form of item must verify
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.5

2013-04-05T20:11:07Z

Djulien: /* Defaults */

==Dedupe 3.5: Group 2 - 008 Date (Verify)==
[[Image:d3-5.png]] 
=== 008 date ===
Verify Date: This is for verifying on the publication date used in the 008 date fields (positions 7-10 and 11-14).

=== Verify Method ===
Parameters in this verification allow partial dates to match to either full dates or other partial dates. Different methods are used in this FULL/PARTIAL/WITHIN.

*FULL compares both date1 and date2 of each record - both have to match.
*PARTIAL compares date1 of each record. If no match it compares date2 if the dates don't start with fill characters (space or |).
*WITHIN compares date1 of one record to date2 of the other and vice-versa. If no match it also does a parital verify.

=== Tolerance ===
The date tolerance for the Verify Date parameter is the number of years the date can differ and still qualify as a matched record. This allows for more leniency with hits on the 010/020 and stricter criteria for the TITLE or other fields.

The tolerance allows for dates to match within a specified number of years:


Match Exactly : 1996 can only verify with 1996. It will not match with 1995 or 199| or 199[blank].
Off by 1 year : 1996 would match with 1995 or 1997. It will not match with 199| or 199[blank].
Off by __ years : This would allow the tolerance to be specified to 2 or more years.

NOTE: If the 260 $c date is more complete than the 008 date positions, or the 008 positions are not filled in at all, please talk with your project manager for possible options, e.g., having the Backstage staff populate the 008 using the 260 $c.

===Default===
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || 008 date blocks must verify; must be exact same year
|-
|}
<div style=clear:both></div> 

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.4

2013-04-03T20:04:14Z

Djulien:

==Dedupe 3.4: Group 2 - Leader (Verify)==
[[Image:d2-3.png]] 
===Leader Verification===
The first line of every record, the leader, contains coded information enabling the computer to process the record. The leader contains 24 positions, but for deduplication purposes, only position 06 and 07 will be used. For more information on all the leader positions, please use the following link : [http://www.loc.gov/marc/bibliographic/bdleader.html]

====Position 06 - Type of Record====
This position identifies the kind of material the record is catalogued in.
Position types include:

*'''a''' - language materials (books, magazines, newspapers)
*'''c''' - printed music
*'''d''' - manuscript music
*'''e''' - printed maps
*'''f''' - manuscript maps
*'''g''' - projected graphics (e.g., videorecordings, slides, filmstrips)
*'''i''' - nonmusical sound recordings
*'''j''' - musical sound recordings
*'''k''' - two-dimensional non-projected graphics (e.g., pictures, drawings)
*'''m''' - computer files
*'''o''' - kits
*'''p''' - mixed materials
*'''r''' - three-dimensional objects
*'''t''' - manuscript language material

====Position 07 - Biblographic Level====
This position identifies the bibliographic level of the record.
Position types include:

*'''a''' - monographic component part
*'''b''' - serial component part
*'''c''' - collection
*'''d''' - subunit
*'''i''' - integrating resource
*'''m''' - monograph
*'''s''' - serial

In most cases this position is catalogued as '''m''' or '''s'''.
==Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || Use positions 06 and 07 of the leader for verification
|-
|}

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.4

2013-04-03T19:57:09Z

Djulien:

==Dedupe 3.4: Group 2 - Leader (Verify)==
[[Image:d2-3.png]] 
===Leader Verification===
The first line of every record, the leader, contains coded information enabling the computer to process the record. The leader contains 24 positions, but for deduplication purposes, only position 06 and 07 will be used. For more information on all the leader positions, please use the following link : [http://www.loc.gov/marc/bibliographic/bdleader.html]

====Position 06 - Type of Record====
This position identifies the kind of material the record is catalogued in.
Position types include:

*'''a''' - language materials (books, magazines, newspapers)
*'''c''' - printed music
*'''d''' - manuscript music
*'''e''' - printed maps
*'''f''' - manuscript maps
*'''g''' - projected graphics (e.g., videorecordings, slides, filmstrips)
*'''i''' - nonmusical sound recordings
*'''j''' - musical sound recordings
*'''k''' - two-dimensional non-projected graphics (e.g., pictures, drawings)
*'''m''' - computer files
*'''o''' - kits
*'''p''' - mixed materials
*'''r''' - three-dimensional objects
*'''t''' - manuscript language material

====Position 07 - Biblographic Level====
This position identifies the bibliographic level of the record.
Position types include:

*'''a''' - monographic component part
*'''b''' - serial component part
*'''c''' - collection
*'''d''' - subunit
*'''i''' - integrating resource
*'''m''' - monograph
*'''s''' - serial

In most cases this position is catalogued as '''m''' or '''s'''.
== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || Use positions 06 and 07 of the leader for verification
|-
|}

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.0

2013-04-02T17:05:47Z

Djulien: /* Default */

==Dedupe 3.0: Group 2==
Section 3.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the title (245) field.
===Group 2 Title Text Hits===
Grouping allows the user to have different parameters for different potential matches. Since the title field (245) could yield extremely different potential match possibilities than a numeric hit, it is separated out to it's on group and will have the different verification parameters than the other groups.

====Title (245)====
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page.

Every record must have a 245 tag. If some of the records in the catalog do not have a title please refer to your Backstage project manager for possible suggestions.

The 245 will be used as a default for searching, although it will be searched a little different than the other default hit fields.

===Group 2 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245$a Adventures of Huckleberry Finn.
RESULT: Example 1 would be a match because the 100 exists in one but not the other.

Example 2:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
RESULT: Example 2 would not be a match because the 100 differs.

===Default===
The default for finding a potential match for this field is as follows:
#Use subfield a and b
#Use first 64 characters
#Use NACO normalization

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
|- style="background:#CCFFFF; font-size: 110%;"
| || Use NACO normalization on the 245 $a and $b and search the first 64 characters
|-
|}
<div style=clear:both></div> 

Other options include:
*Include other subfields, e.g., n or p
*Use more or less than 64 characters: minimum of 1, maximum of 1024
*Use other normalization methods
*CJK - also retains spaces and subfield delimiters
*FULL - This is the same as NACO normalization except it will remove spaces and subfield delmiters

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.0

2013-04-02T17:05:30Z

Djulien: /* Defaults and Options */

==Dedupe 3.0: Group 2==
Section 3.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the title (245) field.
===Group 2 Title Text Hits===
Grouping allows the user to have different parameters for different potential matches. Since the title field (245) could yield extremely different potential match possibilities than a numeric hit, it is separated out to it's on group and will have the different verification parameters than the other groups.

====Title (245)====
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page.

Every record must have a 245 tag. If some of the records in the catalog do not have a title please refer to your Backstage project manager for possible suggestions.

The 245 will be used as a default for searching, although it will be searched a little different than the other default hit fields.

===Group 2 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245$a Adventures of Huckleberry Finn.
RESULT: Example 1 would be a match because the 100 exists in one but not the other.

Example 2:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
RESULT: Example 2 would not be a match because the 100 differs.

===Default===
The default for finding a potential match for this field is as follows:
#Use subfield a and b
#Use first 64 characters
#Use NACO normalization

== Default==
{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
! style="background:lightgray" align="left" colspan="2" | Group 1 (010, 020, 022)
|- style="background:#CCFFFF; font-size: 110%;"
| || Use NACO normalization on the 245 $a and $b and search the first 64 characters
|-
|}
<div style=clear:both></div> 

Other options include:
*Include other subfields, e.g., n or p
*Use more or less than 64 characters: minimum of 1, maximum of 1024
*Use other normalization methods
*CJK - also retains spaces and subfield delimiters
*FULL - This is the same as NACO normalization except it will remove spaces and subfield delmiters

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 2.0

2013-04-02T16:31:29Z

Djulien: /* Verification Terms - Only if Both */

==Dedupe 2.0: Group 1==
Section 2.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the 010/020/022 fields.
===Group 1 Hit Fields===
Grouping allows the user to have different parameters for different potential matches. Since numeric fields such as the LCCN, ISBN, and ISSN are fairly reliable in most cases, they are grouped together and will have the same verification parameters.

====Library of Congress Control Number (LCCN/010)====
The Library of Congress control number assigned to a catalogued item is recorded in the 010 tag. This number is used to to distinguish each record from every other record in the database Library of Congress database.

The LCCN has three parts: the prefix, a year (represented by two or four digits) and a serial number (six digits) followed by another space in the case of pre-2001 LCCNs. Suffixes and revision dates following some printed LCCNs may or may-not be keyed into MARC record.

The following subfields are valid in the 010 tag:
*'''a''' - LC control number
*'''b''' - NUCMC control number -- This subfield is used only in archival/manuscripts format
*'''z''' - Cancelled/invalid LC control number

010 $a 91001938
010 $a 2001012884
010 $a 08000123 $z 80000123 

====International Standard Book Number (ISBN/020)====
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

====International Standard Serial Number (ISSN/022)====
An International Standard Serial Number (ISSN) is an identification number assigned to a serial (the entire serial, not just a particular issue). The ISSN is similar in function to the ISBN assigned to books.
The 022 tag is repeated whenever a serial has two or more valid ISSNs. This sometimes happens when a serial changes its title and a new ISSN is assigned; when a record is created for the new title, both the new and the old ISSNs (both still valid) are entered in the new record.

The following subfields are valid in the 022 tag:
*'''a''' - International Standard Serial Number
*'''l''' - ISSN-L
*'''m''' - Cancelled ISSN-L
*'''y''' - Incorrect ISSN
*'''z''' - Cancelled ISSN

This field only contains digits except the last digit may be ''X'' (roman numeral 10):

022 $a 1234-5678
022 $a 9876-123X

Subfield l links together various media versions of a continuing resource:

022 $a 1234-5678 $l 1234-1231

===Group 1 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245 $a Adventures of Huckleberry Finn.
'''RESULT''': This would be a match because the 100 exists in one but not the other.

However, when two records each have their own 1XX field and they differ, we have this scenario:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
'''RESULT''': This would not be a match because the 100 differs.

==links==
<center>[[Dedupe 2.1|2.1]] - [[Dedupe 2.2|2.2]] - [[Dedupe 2.3|2.3]] - [[Dedupe 2.4|2.4]] - [[Dedupe 2.5|2.5]] - [[Dedupe 2.6|2.6]] - [[Dedupe 2.7|2.7]] - [[Dedupe 2.8|2.8]] - [[Dedupe 2.9|2.9]] - [[Dedupe 2.10|2.10]] - [[Dedupe 2.11|2.11]] - [[Dedupe 2.12|2.12]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 2.0

2013-04-02T16:30:27Z

Djulien: /* Verification Terms - Method */

==Dedupe 2.0: Group 1==
Section 2.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the 010/020/022 fields.
===Group 1 Hit Fields===
Grouping allows the user to have different parameters for different potential matches. Since numeric fields such as the LCCN, ISBN, and ISSN are fairly reliable in most cases, they are grouped together and will have the same verification parameters.

====Library of Congress Control Number (LCCN/010)====
The Library of Congress control number assigned to a catalogued item is recorded in the 010 tag. This number is used to to distinguish each record from every other record in the database Library of Congress database.

The LCCN has three parts: the prefix, a year (represented by two or four digits) and a serial number (six digits) followed by another space in the case of pre-2001 LCCNs. Suffixes and revision dates following some printed LCCNs may or may-not be keyed into MARC record.

The following subfields are valid in the 010 tag:
*'''a''' - LC control number
*'''b''' - NUCMC control number -- This subfield is used only in archival/manuscripts format
*'''z''' - Cancelled/invalid LC control number

010 $a 91001938
010 $a 2001012884
010 $a 08000123 $z 80000123 

====International Standard Book Number (ISBN/020)====
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

====International Standard Serial Number (ISSN/022)====
An International Standard Serial Number (ISSN) is an identification number assigned to a serial (the entire serial, not just a particular issue). The ISSN is similar in function to the ISBN assigned to books.
The 022 tag is repeated whenever a serial has two or more valid ISSNs. This sometimes happens when a serial changes its title and a new ISSN is assigned; when a record is created for the new title, both the new and the old ISSNs (both still valid) are entered in the new record.

The following subfields are valid in the 022 tag:
*'''a''' - International Standard Serial Number
*'''l''' - ISSN-L
*'''m''' - Cancelled ISSN-L
*'''y''' - Incorrect ISSN
*'''z''' - Cancelled ISSN

This field only contains digits except the last digit may be ''X'' (roman numeral 10):

022 $a 1234-5678
022 $a 9876-123X

Subfield l links together various media versions of a continuing resource:

022 $a 1234-5678 $l 1234-1231

===Group 1 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245$a Adventures of Huckleberry Finn.
'''RESULT''': This would be a match because the 100 exists in one but not the other.

However, when two records each have their own 1XX field and they differ, we have this scenario:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
'''RESULT''': This would not be a match because the 100 differs.

==links==
<center>[[Dedupe 2.1|2.1]] - [[Dedupe 2.2|2.2]] - [[Dedupe 2.3|2.3]] - [[Dedupe 2.4|2.4]] - [[Dedupe 2.5|2.5]] - [[Dedupe 2.6|2.6]] - [[Dedupe 2.7|2.7]] - [[Dedupe 2.8|2.8]] - [[Dedupe 2.9|2.9]] - [[Dedupe 2.10|2.10]] - [[Dedupe 2.11|2.11]] - [[Dedupe 2.12|2.12]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 2.0

2013-04-02T16:30:10Z

Djulien: /* Verification Terms - Method */

==Dedupe 2.0: Group 1==
Section 2.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the 010/020/022 fields.
===Group 1 Hit Fields===
Grouping allows the user to have different parameters for different potential matches. Since numeric fields such as the LCCN, ISBN, and ISSN are fairly reliable in most cases, they are grouped together and will have the same verification parameters.

====Library of Congress Control Number (LCCN/010)====
The Library of Congress control number assigned to a catalogued item is recorded in the 010 tag. This number is used to to distinguish each record from every other record in the database Library of Congress database.

The LCCN has three parts: the prefix, a year (represented by two or four digits) and a serial number (six digits) followed by another space in the case of pre-2001 LCCNs. Suffixes and revision dates following some printed LCCNs may or may-not be keyed into MARC record.

The following subfields are valid in the 010 tag:
*'''a''' - LC control number
*'''b''' - NUCMC control number -- This subfield is used only in archival/manuscripts format
*'''z''' - Cancelled/invalid LC control number

010 $a 91001938
010 $a 2001012884
010 $a 08000123 $z 80000123 

====International Standard Book Number (ISBN/020)====
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

====International Standard Serial Number (ISSN/022)====
An International Standard Serial Number (ISSN) is an identification number assigned to a serial (the entire serial, not just a particular issue). The ISSN is similar in function to the ISBN assigned to books.
The 022 tag is repeated whenever a serial has two or more valid ISSNs. This sometimes happens when a serial changes its title and a new ISSN is assigned; when a record is created for the new title, both the new and the old ISSNs (both still valid) are entered in the new record.

The following subfields are valid in the 022 tag:
*'''a''' - International Standard Serial Number
*'''l''' - ISSN-L
*'''m''' - Cancelled ISSN-L
*'''y''' - Incorrect ISSN
*'''z''' - Cancelled ISSN

This field only contains digits except the last digit may be ''X'' (roman numeral 10):

022 $a 1234-5678
022 $a 9876-123X

Subfield l links together various media versions of a continuing resource:

022 $a 1234-5678 $l 1234-1231

===Group 1 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared. l ksajdf;lkasd jflskadjfl askdjf;sldakfjsd;lkfjl;kjsdf.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245$a Adventures of Huckleberry Finn.
'''RESULT''': This would be a match because the 100 exists in one but not the other.

However, when two records each have their own 1XX field and they differ, we have this scenario:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
'''RESULT''': This would not be a match because the 100 differs.

==links==
<center>[[Dedupe 2.1|2.1]] - [[Dedupe 2.2|2.2]] - [[Dedupe 2.3|2.3]] - [[Dedupe 2.4|2.4]] - [[Dedupe 2.5|2.5]] - [[Dedupe 2.6|2.6]] - [[Dedupe 2.7|2.7]] - [[Dedupe 2.8|2.8]] - [[Dedupe 2.9|2.9]] - [[Dedupe 2.10|2.10]] - [[Dedupe 2.11|2.11]] - [[Dedupe 2.12|2.12]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 2.0

2013-04-02T16:29:47Z

Djulien: /* Verification Terms - Method */

==Dedupe 2.0: Group 1==
Section 2.0 of the dedupe profile will guide you through the verification and parameters used for hitting on the 010/020/022 fields.
===Group 1 Hit Fields===
Grouping allows the user to have different parameters for different potential matches. Since numeric fields such as the LCCN, ISBN, and ISSN are fairly reliable in most cases, they are grouped together and will have the same verification parameters.

====Library of Congress Control Number (LCCN/010)====
The Library of Congress control number assigned to a catalogued item is recorded in the 010 tag. This number is used to to distinguish each record from every other record in the database Library of Congress database.

The LCCN has three parts: the prefix, a year (represented by two or four digits) and a serial number (six digits) followed by another space in the case of pre-2001 LCCNs. Suffixes and revision dates following some printed LCCNs may or may-not be keyed into MARC record.

The following subfields are valid in the 010 tag:
*'''a''' - LC control number
*'''b''' - NUCMC control number -- This subfield is used only in archival/manuscripts format
*'''z''' - Cancelled/invalid LC control number

010 $a 91001938
010 $a 2001012884
010 $a 08000123 $z 80000123 

====International Standard Book Number (ISBN/020)====
This field records the International Standard Book Number(s) assigned to a catalogued item. Each valid ISBN is entered in a separate 020 tag; two or more invalid or cancelled ISBNs may be recorded in a single 020 tag.

The following subfields are valid in the 020 tag:
*'''a''' - International Standard Book Number
*'''c''' - Terms of availability
*'''z''' - Cancelled/invalid ISBN

Valid ISBNs are always ten or thirteen digits long; all ISBNs are assumed valid unless they have too many or too few digits, or unless a shelflist card specifically identifies an ISBN as cancelled or invalid:

020 $a 0049812187
020 $a 9780049853217

The only letter that is ever part of an ISBN is X (roman numeral 10); it must always be capitalized:

020 $a 012817409X

Subfield a may contain qualifying information (publisher, binding, format, volume numbers). This information is usually entered within parentheses; separate pieces of information with space-colon-space:

020 $a 001281947X (pbk.)
020 $a 0018942113 (Bally Bros. : pbk.)
020 $a 0137183911 (large print)

Prices appearing after ISBNs are catalogued in subfield c:

020 $a 0174620684 :$c $21.95
020 $a 0049812187 (pbk.) :$c $17.40

====International Standard Serial Number (ISSN/022)====
An International Standard Serial Number (ISSN) is an identification number assigned to a serial (the entire serial, not just a particular issue). The ISSN is similar in function to the ISBN assigned to books.
The 022 tag is repeated whenever a serial has two or more valid ISSNs. This sometimes happens when a serial changes its title and a new ISSN is assigned; when a record is created for the new title, both the new and the old ISSNs (both still valid) are entered in the new record.

The following subfields are valid in the 022 tag:
*'''a''' - International Standard Serial Number
*'''l''' - ISSN-L
*'''m''' - Cancelled ISSN-L
*'''y''' - Incorrect ISSN
*'''z''' - Cancelled ISSN

This field only contains digits except the last digit may be ''X'' (roman numeral 10):

022 $a 1234-5678
022 $a 9876-123X

Subfield l links together various media versions of a continuing resource:

022 $a 1234-5678 $l 1234-1231

===Group 1 - Verification Criteria and Terms===
The Verify criteria is used to reduce the number of initial matches found using the Hit criteria. This allows you to further define what constitutes a good match based on the existence of other fields within your records.
Fields should be selected on the basis of the match-rate you expect to see with the deduplication. Selecting fewer fields will result in more matches; selecting more fields will result in fewer, but better matches.
Verify criteria should also be selected in conjunction with Hit criteria.

====Verification Terms - Method====
There are a few methods for verifying: FULL, PARTIAL, and WITHIN. These methods will be used for comparing data found in a specific field against the same field in a potential match record.

*FULL - Compares the full verify string up to the verify length.
*PARTIAL - Truncates the compare strings to the shortest string, then does a full compare:

"The fox in and the hound" in one record, "The fox" on the other record: Both truncate to "The fox" and compared. lksajdf;lkasdjf;lskadjf;laskdjf;sldakfjsd;lkfjl;kjsdf.
*WITHIN - Searches each compare string truncated at verify length against the full un-truncated string of the other field:

"Cat" will verify against "The cat in the hat."

====Verification Terms - Normalization====
Normalization refers to how the string will be presented when compared to another string. Note that any normalization will not change anything in the record, but is only used when the program compares the strings.

Types of normalization are:
*NACO/CJK - retains spaces and subfield delimiters:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''$a daniel boone :$b a pioneer'''
*FULL - NACO normalization with all spaces and subfield delimiters removed:

'''245 $a Daniel Boone :$b a pioneer.''' would be normalized as '''danielbooneapioneer'''

====Verification Terms - LENGTH and WORDS====
This refers to how much of a given string the program will present for potential matches:
*LENGTH - Refers to the number of characters for the verify field. The number of characters to be used is 1-2048, or all:

Using 10 for LENGTH would truncate '''245 $a Daniel Boone :$b a pioneer.''' to '''Daniel Boon''' if FULL method was used.
*WORDS - Refers to a count of words to match within a given string:

Using 2 words for '''245 $a Daniel Boone :$b a pioneer''' returns any of the words as keywords for match possibilities.
NOTE: using WORDS will not include non-filers.

====Verification Terms - Must Verify====
If this option is used for any given field, then that verify has to verify or it is not considered a match. This is almost always used for the 245verification and is common in other fields as well

====Verification Terms - Only if Both====
This only does a verify comparison if both records have a specified field; verifies as true if only one of the records has the field. If this option was used on the 1xx field, the following would be true:
Example 1:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has no 100
245$a Adventures of Huckleberry Finn.
'''RESULT''': This would be a match because the 100 exists in one but not the other.

However, when two records each have their own 1XX field and they differ, we have this scenario:

Record A has:
100 $a Twain, Mark.
245 $a Adventures of Huckleberry Finn.

Record B has:
100 $a Clemens, Samuel.
245 $a Adventures of Huckleberry Finn.
'''RESULT''': This would not be a match because the 100 differs.

==links==
<center>[[Dedupe 2.1|2.1]] - [[Dedupe 2.2|2.2]] - [[Dedupe 2.3|2.3]] - [[Dedupe 2.4|2.4]] - [[Dedupe 2.5|2.5]] - [[Dedupe 2.6|2.6]] - [[Dedupe 2.7|2.7]] - [[Dedupe 2.8|2.8]] - [[Dedupe 2.9|2.9]] - [[Dedupe 2.10|2.10]] - [[Dedupe 2.11|2.11]] - [[Dedupe 2.12|2.12]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.4

2013-04-01T16:29:04Z

Djulien:

==Dedupe 6.4 - Do Not Index==
[[Image:d5-2.png]] 
===Definition===
This allows for the removal of certain records from the deduplication process.
===Tag===
Input field for the program to look at:
035
If only 035 is chosen, then any record with an 035 will be removed from the deduplication process, and will not be allowed to be matched against.
035 $z
This would remove any record that contained an 035 $z from the process.
035 $a GPO
This would remove any record that contained 'GPO' in the subfield a of the 035.

Other examples include:
245 $h kit
300 $a DVD
852 $k Special Collection

==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.3

2013-04-01T16:22:10Z

Djulien:

==Dedupe 6.3 - Retained Fields==
[[Image:d6-3.png]] 
===Definition===
There may be certain fields your institution would prefer to retain when one record is deduped into another, better match. It could be a field that represents your holdings or items, or a control number, or subject headings, etc. Entire ranges of fields (i.e., 65X) can also be merged in this step.
Once one record is deduped into another record, the original record's fields are lost unless they are retained in the matched record.
If you do choose to merge your original fields into the matched record, we can merge either all of your fields or only the unique fields.

===Tag===
Input tag number to be retained.
852
9XX
===All Fields===
If you choose All, then our system will make sure to retain all selected original fields into the matched record. This includes the possibility of merging fields that may duplicate another field already present in the matched record. This option is useful for customers that wish to retain similar subject headings that only differ in indicator values.
===Unique Fields Only===
If you choose Unique, then our system will normalize the headings using NACO standards and run a comparison check. Unique indicators are ignored during the comparison check.
===Longest Field===
When merging a field from a ''dying'' record, choosing this option will match that field against the same field in the retained record. If the 2 fields are the exact same up until the shorter field, the longer field will be retained:

'''650 $aMissing persons$xInvestigation'''.
'''650 $aMissing persons$xInvestigation'''$vFiction.
'''650 $aMissing persons.'''

If the longest field parameter is being used, then '''650 $aMissing persons$xInvestigation$vFiction''' will be retained in the final record.
===Only if it doesn't exist===
This will merge the indicated field from the ''dying'' record into the final record if it doesn't already exist in the final record.

Example:
Retained record does not have an 856, but this record is kept because of the options chosen in section 5
Dying record record has an 856 that is wanted to be retained

Choosing the ''only if it doesn't exist'' option will enable retention of the 856.

==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.3

2013-04-01T16:17:52Z

Djulien:

==Dedupe 6.3 - Retained Fields==
[[Image:d6-3.png]] 
===Definition===
There may be certain fields your institution would prefer to retain when one record is deduped into another, better match. It could be a field that represents your holdings or items, or a control number, or subject headings, etc. Entire ranges of fields (i.e., 65X) can also be merged in this step.
Once one record is deduped into another record, the original record's fields are lost unless they are retained in the matched record.
If you do choose to merge your original fields into the matched record, we can merge either all of your fields or only the unique fields.

===Tag===
Input tag number to be retained.
852
9XX
===All Fields===
If you choose All, then our system will make sure to retain all selected original fields into the matched record. This includes the possibility of merging fields that may duplicate another field already present in the matched record. This option is useful for customers that wish to retain similar subject headings that only differ in indicator values.
===Unique Fields Only===
If you choose Unique, then our system will normalize the headings using NACO standards and run a comparison check. Unique indicators are ignored during the comparison check.
===Longest Field===
When merging a field from a ''dying'' record, choosing this option will match that field against the same field in the retained record. If the 2 fields are the exact same up until the shorter field, the longer field will be retained:

'''650 $aMissing persons$xInvestigation'''.
'''650 $aMissing persons$xInvestigation'''$vFiction.
'''650 $aMissing persons.'''

If the longest field parameter is being used, then '''650 $aMissing persons$xInvestigation$vFiction''' will be retained in the final record.

==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.2

2013-04-01T16:06:02Z

Djulien: /* Definition */

==Dedupe 6.1: Maximum Records per Report==
[[Image:d6-2.png]] 
===Definition===
Reports of matched records will be provided in a side-by-side comparison. This will be provided in .htm format and will have the retained record on one side, and the ''deduped'' record on the opposite side.

This option allows for the user to decide how many matched records will display in each report. If the final count of duplicate matches is 3370 and '500' is chosen for this option, then the reports will be sent as follows:
Report 1 : Matches 1-500
Report 2 : Matches 501-1000
...
Report 7 : Matches 3001-3370

===Default===
*Display 500 matches per report

==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.1

2013-04-01T16:05:21Z

Djulien:

==Dedupe 6.1: Backstage Change Stamp==
[[Image:d6-1.png]] 
Some customers prefer to have a stamp added to records that a vendor has modified in some way. These stamps make it easier to identify which records have already undergone processing and which records may still need to be submitted.
Backstage can add an 040 $d UtOrBLW to all or only merged records.
===All Records===
All will add this field to all records, regardless of whether the record deduped into another record. This option is useful for customers that wish to designate every record that was processed by Backstage
===Merged Only Records===
Merged will only add this stamp to records where fields were retained from a matched record. Note that this option will only add the stamp to records where some other field was merged into the matching record. So if a record is deduped (where the original record found a matching record), yet no fields were retained during the dedupe, the 040 $d UtOrBLW will not be added in this case.
===Default===
*Add 040 $d UtOrBLW to all records.
==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.2

2013-04-01T16:03:46Z

Djulien:

==Dedupe 6.1: Maximum Records per Report==
[[Image:d6-2.png]] 
===Definition===
Reports of matched records will be provided in a side-by-side comparison. This will be provided in .htm format and will have the retained record on one side, and the ''deduped'' record on the opposite side.

This option allows for the user to decide how many matched records will display in each report. If the final count of duplicate matches is 3370 and '500' is chosen for this option, then the reports will be sent as follows:

Report 1 : Matches 1-500
Report 2 : Matches 501-1000
...
Report 7 : Matches 3001-3370

===Default===
*Display 500 matches per report

==links==
<center>[[Dedupe 6.1|6.1]] - [[Dedupe 6.2|6.2]] - [[Dedupe 6.3|6.3]] - [[Dedupe 6.4|6.4]] - [[Dedupe 6.5|6.5]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 6.1

2013-04-01T15:55:58Z

Djulien:

Dedupe 6.0

2013-04-01T15:52:39Z

Djulien:

Dedupe 5.2

2013-04-01T15:42:20Z

Djulien: /* Definition */

==Dedupe 5.2: Keep Constraint==
[[Image:d5-2.png]] 
===Definition===
This step is optional and takes precedence over Step 5.1 if filled out. If both the original record and the potential match are equal after this step, then the choice in Step 5.1 takes precedence.

It is also important to note that the order in which Step 5.2 is filled out determines the order the system will take the desired match.
The match information in this step can either be a straight string search (e.g., "OCoLC") or it can be a regular expression match (e.g., "[0-9]$"). Both scenarios are case-insensitive.

For example, you may instruct us to include these two constraints:
035 $a "OCoLC"
949 $a "[0-9]$"
Our system would initially check to see if an 035 $a contains "OCoLC". If this is found, then this particular record will be preferred over any others.
If that is not found, our system will then check to see if the record has a 949 $a that ends with any number. Again, if found, that record takes precedence in the matching process.
If none of the terms filled out in Step 5.2 is present in the potential match, the choice in Step 5.1 takes precedence.

This step is useful for when potential matches contain actual information that indicates it is a good match or a preferred location code.

==links==
<center>[[Dedupe 5.1|5.1]] - [[Dedupe 5.2|5.2]] - [[Dedupe 5.3|5.3]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 5.2

2013-04-01T15:41:40Z

Djulien:

==Dedupe 5.2: Keep Constraint==
[[Image:d5-2.png]] 
===Definition===
This step is optional and takes precedence over Step 5.1 if filled out. If both the original record and the potential match are equal after this step, then the choice in Step 5.1 takes precedence.

It is also important to note that the order in which Step 5.2 is filled out determines the order the system will take the desired match.
The match information in this step can either be a straight string search (e.g., "OCoLC") or it can be a regular expression match (e.g., "[0-9]$"). Both scenarios are case-insensitive.

For example, you may instruct us to include these two constraints:
035 $a "OCoLC"
949 $a "[0-9]$"
Our system would initially check to see if an 035 $a contains "OCoLC". If this is found, then this particular record will be preferred over any others.

If that is not found, our system will then check to see if the record has a 949 $a that ends with any number. Again, if found, that record takes precedence in the matching process.

If none of the terms filled out in Step 5.2 is present in the potential match, the choice in Step 5.1 takes precedence.

This step is useful for when potential matches contain actual information that indicates it is a good match or a preferred location code.

==links==
<center>[[Dedupe 5.1|5.1]] - [[Dedupe 5.2|5.2]] - [[Dedupe 5.3|5.3]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 5.1

2013-04-01T15:38:58Z

Djulien:

==Dedupe 5.1: Keep Which Record==
[[Image:d5-1.png]] 
===Definition===
When comparing 2 records, the program will decide which record to keep based upon the options chosen in this section.

===Base===
Keeps the first record in a file (or group of files). Any subsequent matching records will be merged into the original record. When a record is read into the deduping process, if it does not match any previously read records, it becomes the base record into which all future matches will be merged.

===Latest===
This option will retain the record with the latest processing date according to the 005.
If one of the records doesn't have an 005 it compares the 008's date (positions 0 through 5). If one of the records doesn't have an 008 it keeps the record with an 005. If neither record has an 005 it keeps the record with an 008. If neither record has an 005 or an 008 it keeps the base record.

===Incoming===
This option is the opposite of the ''Base'' option.
If you have a database of 1000 records being sent through the deduplication process and record 1 and record 200 are duplicates, then record 200 will be retained regardless of which record might be better.

===Most tags===
Compares the original record with the potential match. The best match is determined to be the one with the highest count of a given field in the record, which may not necessarily represent the largest record.

This can be used if you want to retain records with the highest count of 650 fields, or 5XX fields.

===Largest===
Compares the original record with the potential match. The best match is determined to be the one that has the most data, which may not necessarily represent the one with the most fields.
Record A has a lot of data in a 5XX field, but has no 6XX fields
Record B has limited data in the 5XX field along with 6XX fields
Record A will be the retained if it has more data in total number of characters/bytes.

====Ignore fields====
Within the Largest option, a field(s) can be chosen to be omitted from the ''largest'' equation. For the example above, if 5XX were chosen to be ignored, then it would retain Record B, barring another field. This allows for the 9XX and holdings fields to be ignored.

===Defaults===
*Keep Largest Record and ignore the 9XX fields in determining largest record

==links==
<center>[[Dedupe 5.1|5.1]] - [[Dedupe 5.2|5.2]] - [[Dedupe 5.3|5.3]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 5.0

2013-04-01T15:21:01Z

Djulien:

==Dedupe 5.0: Keep Options==
In the ''Keep Options'' section, parameters are set to define which record to keep.
This allows the user to ensure that the best, or the most valuable record, is retained when the program finds verified duplicate matches.
==links==
<center>[[Dedupe 5.1|5.1]] - [[Dedupe 5.2|5.2]] - [[Dedupe 5.3|5.3]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.14

2013-04-01T15:13:42Z

Djulien:

==Dedupe 3.14: Group 2 - 260 $c - Date (Verify)==
[[Image:d3-14.png]] 
=== Description ===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield c - Date====
The date of publication, distribution, etc. is in the 260$c.

260 $a New York :$b Pelham Press, $c 1953.
260 $a Boston :$b Imperial Press, $c 1967-1970.

When $c contains more than a year (either month and year, or month, day, and year), the date is in the order month/year or month/day/year. A comma is used to set off the month/day from the year, but not to separate a month from the year; standard abbreviations are used for the names of the months in most cases.


260 $a New York, $c Aug. 15, 1967.
260 $a Boston :$b Imperial Press, $c Sept. 1967.

Some records have dates lacking one or more digits so the 260$c date often uses square brackets around the date with a hyphen for each missing digit in the date.

260 $a New York :$b Willemsen,$c[196-]
260 $a New York, $c [19--?]

NOTE: The 260$c date can have many variations containing printing dates, copyright dates, multiple dates, open ended dates, etc. This should be represented in the 008 field positions 7-14. If you feel that your 008 date positions do not represent what is in the 260$c, please contact your Backstage project manager for possible solutions.

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "1966-1967." in one record, "1966-" on the other record : both truncated to "1966-" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "1967" will find a potential match on "1966-1967."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 260$c within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 260$c within the verify method chosen above.

===Defaults===
The default for verifying on the 260$c within Hit Group 2 (245) is as follows:
#Must verify, must exist
#FULL verify method
#NACO normalization

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.15

2013-04-01T15:13:25Z

Djulien:

==Dedupe 4.15: Optional Group - 260 $c - Date (Verify)==
[[Image:d2-11.png]] 
===Description===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield c - Date====
The date of publication, distribution, etc. is in the 260$c.

260 $a New York :$b Pelham Press, $c 1953.
260 $a Boston :$b Imperial Press, $c 1967-1970.

When $c contains more than a year (either month and year, or month, day, and year), the date is in the order month/year or month/day/year. A comma is used to set off the month/day from the year, but not to separate a month from the year; standard abbreviations are used for the names of the months in most cases.


260 $a New York, $c Aug. 15, 1967.
260 $a Boston :$b Imperial Press, $c Sept. 1967.

Some records have dates lacking one or more digits so the 260$c date often uses square brackets around the date with a hyphen for each missing digit in the date.

260 $a New York :$b Willemsen,$c[196-]
260 $a New York, $c [19--?]

NOTE: The 260$c date can have many variations containing printing dates, copyright dates, multiple dates, open ended dates, etc. This should be represented in the 008 field positions 7-14. If you feel that your 008 date positions do not represent what is in the 260$c, please contact your Backstage project manager for possible solutions.

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "1966-1967." in one record, "1966-" on the other record : both truncated to "1966-" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "1967" will find a potential match on "1966-1967."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 260$c within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 260$c within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.14

2013-04-01T15:11:58Z

Djulien:

==Dedupe 4.14: Optional Group - 260 $b - Publisher (Verify)==
[[Image:d4-14.png]] 
=== Description ===
This field contains the name of publisher, distributor, etc. for the title. Only subfield b of the 260 field will be used for this parameter

====subfield b - Publisher name====
The name of publisher or distributor is in the $b and can be repeated.


260 $a New York :$b Pelham Press :$b Distributed by Grant Educational, $c 1976.
260 $a Boston :$b Printed for the CLA by the Morriss Print. Co., $c 1925.
260 $a Paris :$b Gauthier-Villars ;$a Chicago :$b University of Chicago Press, $c 1975

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "Pelham Press" in one record, "Pelham" on the other record : both truncated to "Pelham" and compared.
*WITHIN - Within searches each compare string truncated at verify length against the full un-truncated string of the other field. "Press" will find a potential match on "Pelham Press."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 260$b within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 260$b within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.13

2013-04-01T15:10:21Z

Djulien: /* Defaults */

==Dedupe 4.13: Optional Group - 245 $h - GMD (Verify)==
[[Image:d4-13.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page. Only subfield h will be used for this parameter.

Every MARC record must have a 245 field, but not necessarily a subfield h.

====subfield h - Medium====
This subfield describes the medium, or form, of the work being catalogued. The terms used in $h are called ''General material designations'', or GMDs, in AACR2. Subfield h is normally used only for various AV formats. When no $h is present, the catalogued item is presumed to be a book, serial, or other printed text item.

When subfield is used, the GMD is enclosed within square brackets. There is no punctuation before $h, and $h is not capitalized.

The terms deemed appropriate for $h are:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| activity card || art original || art reproduction || braille
|- align="left"
| chart || computer file || diorama || filmstrip
|- align="left"
| flash card || games || globe || interactive multimedia
|- align="left"
| kit || manuscript || map || microform
|- align="left"
| microscope slide || model || motion picture || music
|- align="left"
| picture || realia || slide || sound recording
|- align="left"
| technical drawing || toy || transparency || videorecording
|}
<div style=clear:both></div> 

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$h within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$h within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.13

2013-04-01T15:10:05Z

Djulien:

==Dedupe 4.13: Optional Group - 245 $h - GMD (Verify)==
[[Image:d4-13.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page. Only subfield h will be used for this parameter.

Every MARC record must have a 245 field, but not necessarily a subfield h.

====subfield h - Medium====
This subfield describes the medium, or form, of the work being catalogued. The terms used in $h are called ''General material designations'', or GMDs, in AACR2. Subfield h is normally used only for various AV formats. When no $h is present, the catalogued item is presumed to be a book, serial, or other printed text item.

When subfield is used, the GMD is enclosed within square brackets. There is no punctuation before $h, and $h is not capitalized.

The terms deemed appropriate for $h are:
{| border="1" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
|- align="left"
| activity card || art original || art reproduction || braille
|- align="left"
| chart || computer file || diorama || filmstrip
|- align="left"
| flash card || games || globe || interactive multimedia
|- align="left"
| kit || manuscript || map || microform
|- align="left"
| microscope slide || model || motion picture || music
|- align="left"
| picture || realia || slide || sound recording
|- align="left"
| technical drawing || toy || transparency || videorecording
|}
<div style=clear:both></div> 

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$h within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$h within the verify method chosen above.

=== Defaults ===
The default for verifying on the 245$h within Hit Group 2 (245) is as follows:

#Must Verify if exists
#Full verify method
#NACO normalization

*NOTE: If you collections contains a lot of AV material, and, since AV material can vary so much from collection to collection, please consult with your Backstage project manager to ensure that the best profile parameters are being used.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.12

2013-04-01T15:08:41Z

Djulien:

==Dedupe 4.12: Optional Group - 245 $n, $p - Title (Verify)==
[[Image:d4-12.png]] 
===Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page. Subfields n and p will be used for this parameter.

Every MARC record must have a 245 field, but not necessarily a subfield n and/or p.

====subfield n - Number of part/section of a work====
If a book includes only a part or section of a larger work, the number of that part or section may be entered in $n. Numbering includes letters as well as numbers, and any other designation of sequence.


245 $a Divine comedy. $n Third part.
245 $a Travels through the orient. $n Volume 2, pt. 4.

====subfield p - Name of part/section of a work====


245 $a Travels through the orient. $n Volume 2, $p Burma.
245 $a New England byways. $n Part 1, $p Vermont. $n Part 2, $p Massachusetts

===Verify Method===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

===Normalization===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

===Length===
This pertains to the number of characters to be used in the verification for the 245$n and $p subfields within the verify method chosen above. The max number of characters that can be used is 2048.

===Words===
This pertains to the number of words to be used in the verification for the 245$n and $p subfields within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 4.11

2013-04-01T15:07:26Z

Djulien:

==Dedupe 4.11: Optional Group - 245 $a, $b - Title (Verify)==
[[Image:d4-11.png]] 
=== Description ===
This field contains the title of the book, including main title, subtitle, statement(s) of responsibility, and occasionally other information appearing on the title page.

Every record must have a 245 tag.

Subfields a and b will be used for this parameter. If only subfield a is wanted to be used, or if other subfields are to be added other than subfields $n, $p and $h, please use section 2-13 of the dedupe profile to add this information.

=== Verify Method ===
*FULL - Full compares the full verify string up to the verify length.
*PARTIAL - Partial truncates the compare strings to the shortest string, then does a full compare. "The fox in the hound" in one record, "The fox" on the other record : both truncated to "The fox" and compared.
*WITHIN - Withing searches each compare string truncated at verify length against the full un-truncated string of the other field. "Cat" will ind a potential match on "The cat in the hat."

=== Normalization ===
*NACO/CJK retains spaces and subfield delimiters.
*FULL is NACO normalization with all spaces and subfield delimiters removed.

=== Length ===
This pertains to the number of characters to be used in the verification for the 245$a and $b subfields within the verify method chosen above. The max number of characters that can be used is 2048.

=== Words ===
This pertains to the number of words to be used in the verification for the 245$a and $b subfields within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 2.6

2013-04-01T15:05:49Z

Djulien:

==Dedupe 2.6: Group 1 - 1XX $a - Main entry (Verify)==
[[Image:d2-6.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.'''

'''PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

'''WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

=== Defaults ===
The default for verifying on the 1XX $a main entry within Hit Group 1 (010/020/022) is as follows:

*Do not use as a verification parameter

==links==
<center>[[Dedupe_2.1|2.1]] - [[Dedupe_2.2|2.2]] - [[Dedupe_2.3|2.3]] - [[Dedupe_2.4|2.4]] - [[Dedupe_2.5|2.5]] - [[Dedupe_2.6|2.6]] - [[Dedupe_2.7|2.7]] - [[Dedupe_2.8|2.8]] - [[Dedupe_2.9|2.9]] - [[Dedupe_2.10|2.10]] - [[Dedupe_2.11|2.11]] - [[Dedupe_2.12|2.12]]
<hr>
[[Dedupe_1.0|1.0]] - [[Dedupe_2.0|2.0]] - [[Dedupe_3.0|3.0]] - [[Dedupe_4.0|4.0]] - [[Dedupe_5.0|5.0]] - [[Dedupe_6.0|6.0]]</center>
[[category:Dedupe Profile Guide]]

Dedupe 4.10

2013-04-01T15:05:21Z

Djulien:

==Dedupe 4.10: Optional Group - 1XX $a - Main entry (Verify)==
[[Image:d2-6.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.'''

'''PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

'''WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

==links==
<center>[[Dedupe 4.1|4.1]] - [[Dedupe 4.2|4.2]] - [[Dedupe 4.3|4.3]] - [[Dedupe 4.4|4.4]] - [[Dedupe 4.5|4.5]] - [[Dedupe 4.6|4.6]] - [[Dedupe 4.7|4.7]] - [[Dedupe 4.8|4.8]] - [[Dedupe 4.9|4.9]] - [[Dedupe 4.10|4.10]] - [[Dedupe 4.11|4.11]] - [[Dedupe 4.12|4.12]] - [[Dedupe 4.13|4.13]] - [[Dedupe 4.14|4.14]] - [[Dedupe 4.15|4.15]] - [[Dedupe 4.16|4.16]] - [[Dedupe 4.17|4.17]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.9

2013-04-01T15:04:42Z

Djulien: /* Length */

==Dedupe 3.9: Group 2 - 1XX $a - Main entry (Verify)==
[[Image:d3-9.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.'''

'''PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

'''WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

=== Defaults ===
The default for verifying on the 1XX $a main entry within Hit Group 2 (245) is as follows:
#Must verify if both records contain 1XX
#FULL verify method
#NACO normalization
#Use 1 word

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.9

2013-04-01T15:04:22Z

Djulien: /* Length */

==Dedupe 3.9: Group 2 - 1XX $a - Main entry (Verify)==
[[Image:d3-9.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

Examples of ''length'' being used with the different verify methods:
'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.'''

'''PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

'''WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

=== Defaults ===
The default for verifying on the 1XX $a main entry within Hit Group 2 (245) is as follows:
#Must verify if both records contain 1XX
#FULL verify method
#NACO normalization
#Use 1 word

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.9

2013-04-01T15:03:41Z

Djulien: /* Length */

==Dedupe 3.9: Group 2 - 1XX $a - Main entry (Verify)==
[[Image:d3-9.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

Examples of ''length'' being used with the different verify methods:
'''FULL verification with length of 5 being used''':
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.
'''
PARTIAL verification with length of 10 being used''':
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.
'''
WITHIN verification with length of 5 being used''':
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

=== Defaults ===
The default for verifying on the 1XX $a main entry within Hit Group 2 (245) is as follows:
#Must verify if both records contain 1XX
#FULL verify method
#NACO normalization
#Use 1 word

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]

Dedupe 3.9

2013-04-01T15:02:38Z

Djulien: /* Length */

==Dedupe 3.9: Group 2 - 1XX $a - Main entry (Verify)==
[[Image:d3-9.png]] 
=== Description ===
When an author (personal, corporate, or meeting) or a uniform title is used as the main entry of the record, the MARC record contains a 1XX tag.

*100 Main entry -- Personal name
*110 Main entry -- Corporate name
*111 Main entry -- Meeting name
*130 Main entry -- Uniform title

A MARC record may have only one 1XX tag, or no 1XX tag at all (in the case of a title main entry).

Only '''subfield a''' will be used for this verification parameter. If you want to use other subfields, please put a note in the online dedupe profile section 2-13.

=== Length ===
This pertains to the number of characters to be used in the verification for the 1XX field within the verify method chosen above. The max number of characters that can be used is 2048.

Examples of ''length'' being used with the different verify methods:

FULL verification with length of 5 being used:
If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.

This would mean that it would verify against all main entries that had '''100 $a Johns''' regardless of what followed. So '''100 $a Johnson, Mark''' would return a positive verify with '''100 $a Johns, Jason'''. In this case choosing a longer length, or using the default ''all'' may be more desirable.

PARTIAL verification with length of 10 being used:
If record had, '''110 $a Backstage Library Works''', then '''Backstage L''' would be used as the verify string.

Since the PARTIAL method was chosen, this would match against '''110 $a Backstage''' or '''100 $a Back'''. But it would not match against '''1XX $a Backstage Travel'''.

WITHIN verification with length of 5 being used:
If record had, '''100 $a Card, Orson Scott''', then any combination of 5 characters could be used;
'''Orson''', '''Scott''', or '''Card''' could be used.

=== Words ===
This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.

=== Defaults ===
The default for verifying on the 1XX $a main entry within Hit Group 2 (245) is as follows:
#Must verify if both records contain 1XX
#FULL verify method
#NACO normalization
#Use 1 word

==links==
<center>[[Dedupe 3.1|3.1]] - [[Dedupe 3.2|3.2]] - [[Dedupe 3.3|3.3]] - [[Dedupe 3.4|3.4]] - [[Dedupe 3.5|3.5]] - [[Dedupe 3.6|3.6]] - [[Dedupe 3.7|3.7]] - [[Dedupe 3.8|3.8]] - [[Dedupe 3.9|3.9]] - [[Dedupe 3.10|3.10]] - [[Dedupe 3.11|3.11]] - [[Dedupe 3.12|3.12]] - [[Dedupe 3.13|3.13]] - [[Dedupe 3.14|3.14]] - [[Dedupe 3.15|3.15]] - [[Dedupe 3.16|3.16]]
<hr>
[[Dedupe 1.0|1.0]] - [[Dedupe 2.0|2.0]] - [[Dedupe 3.0|3.0]] - [[Dedupe 4.0|4.0]] - [[Dedupe 5.0|5.0]] - [[Dedupe 6.0|6.0]]</center>
[[category:Profile Guide]]