Difference between revisions of "Dedupe 2.1"
(→historical fact) |
(→Numeric Field Hits) |
||
| Line 4: | Line 4: | ||
=== LCCN === | === LCCN === | ||
| − | + | historical fact | |
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. | 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: | + | '''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. | 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:<br> | *Examples of LCCN normalization:<br> | ||
| − | ###80020863 /AC/r86" will become "80020863ACr86" and in this case "80020863" as well. Both will be searched to find | + | Example 1: ###80020863 /AC/r86" will become "80020863ACr86" and in this case "80020863" as well. Both will be searched to find a potential match. |
| − | + | Example 2: ###755262" will become "75005262" | |
| − | ###755262" will become "75005262" | + | |
| − | ISBN - 020 subfield a: | + | === ISBN === |
| + | |||
| + | '''ISBN - 020 subfield a:''' | ||
For the International Standard Book 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. | For the International Standard Book 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. | ||
| − | |||
| − | |||
| − | |||
| − | ISSN - 022 subfield a: | + | *Examples of ISBN normalization: |
| + | Example 1: "0937295124 : $12.95" will become "0937295124" | ||
| + | Example 2: "978-0-06-108096-8" will become "9780061080968" | ||
| + | Example 3: "0688076815 (pbk.)" will become "0688076815" | ||
| + | |||
| + | === ISSN === | ||
| + | |||
| + | '''ISSN - 022 subfield a:''' | ||
For the International Standard Serial 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. | For the International Standard Serial 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 ISSN normalization: | |
| + | Example 1: "0829-0784" will become "08290784" | ||
| + | Example 2: "0009-5753 PERIODICAL" becomes "00095753" | ||
Since each of the above fields have unique standards, the normalization option is default, but can be turned off if preferred. | Since each of the above fields have unique standards, the normalization option is default, but can be turned off if preferred. | ||
Revision as of 09:24, 26 March 2013
Contents
Dedupe 2.1: Numeric Field Hits - Group 1
Numeric Field Hits
LCCN
historical fact
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: ###80020863 /AC/r86" will become "80020863ACr86" and in this case "80020863" as well. Both will be searched to find a potential match. Example 2: ###755262" will become "75005262"
ISBN
ISBN - 020 subfield a:
For the International Standard Book 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 ISBN normalization:
Example 1: "0937295124 : $12.95" will become "0937295124" Example 2: "978-0-06-108096-8" will become "9780061080968" Example 3: "0688076815 (pbk.)" will become "0688076815"
ISSN
ISSN - 022 subfield a:
For the International Standard Serial 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 ISSN normalization:
Example 1: "0829-0784" will become "08290784" Example 2: "0009-5753 PERIODICAL" becomes "00095753"
Since each of the above fields have unique standards, the normalization option is default, but can be turned off if preferred.
links
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
