Difference between revisions of "Dedupe 2.6"
(→Description) |
(→Length) |
||
| Line 26: | Line 26: | ||
Examples of ''length'' being used with the different verify methods: | Examples of ''length'' being used with the different verify methods: | ||
FULL verification with length of 5 being used: If record had, '''100$aJohnson, Mark''', then Johns would be used as the verify string. | FULL verification with length of 5 being used: If record had, '''100$aJohnson, Mark''', then Johns would be used as the verify string. | ||
| − | + | ||
| − | + | This would mean that it would verify against all main entries that had '''100$aJohns''' regardless of what followed. So '''100$Johnson, Mark''' would return a positive verify with '''100$aJohns, Jason." In this case choosing a longer length, or using the default ''all'' may be more desirable. | |
| + | |||
| + | PARTIAL verification with length of l0 being used: | ||
| + | If record had, '''110$aBackstage Library Works''', then '''Backstage L''' would be used as the verify string. | ||
| + | |||
| + | Since the PARTIAL method was chosen, this would match against '''110$aBackstage''' or '''100$aBack'''. But it would not match against '''1XX$aBackstage Travel'''. | ||
| + | |||
| + | WITHIN verification with length of 5 being used: | ||
| + | If record had, '''100$aCard, Orson Scott''', then any combination of 5 characters could be used; Orson, Scott, or Card could be used. | ||
==links== | ==links== | ||
Revision as of 10:27, 29 March 2013
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.
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 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$aJohnson, Mark, then Johns would be used as the verify string.
This would mean that it would verify against all main entries that had 100$aJohns regardless of what followed. So 100$Johnson, Mark would return a positive verify with 100$aJohns, Jason." In this case choosing a longer length, or using the default all may be more desirable.
PARTIAL verification with length of l0 being used: If record had, 110$aBackstage Library Works, then Backstage L would be used as the verify string.
Since the PARTIAL method was chosen, this would match against 110$aBackstage or 100$aBack. But it would not match against 1XX$aBackstage Travel.
WITHIN verification with length of 5 being used: If record had, 100$aCard, Orson Scott, then any combination of 5 characters could be used; Orson, Scott, or Card could be used.
links
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0
