Dedupe 3.9 - Revision history

Djulien: /* Defaults */

2013-04-08T15:16:06Z

‎Defaults

Djulien: /* Length */

2013-04-01T15:04:42Z

‎Length

Djulien: /* Length */

2013-04-01T15:04:22Z

‎Length

Djulien: /* Length */

2013-04-01T15:03:41Z

‎Length

Djulien: /* Length */

2013-04-01T15:02:38Z

‎Length

Djulien: /* Length */

2013-04-01T15:02:17Z

‎Length

Djulien: /* Length */

2013-04-01T15:01:42Z

‎Length

Djulien at 15:00, 1 April 2013

2013-04-01T15:00:37Z

Nate at 14:57, 1 April 2013

2013-04-01T14:57:59Z

Djulien at 20:14, 29 March 2013

2013-03-29T20:14:19Z

@@ Line 33: / Line 33: @@
 This pertains to the number of words to be used in the verification for the 1XX field within the verify method chosen above.
-=== Defaults ===
+===Default===
-The default for verifying on the 1XX $a main entry within Hit Group 2 (245) is as follows:
+{| border="0" cellspacing="0" cellpadding="5" align="left" style="border-collapse:collapse;"
-#Must verify if both records contain 1XX
+! style="background:lightgray" align="left" colspan="2" | Group 2 (245)
-#FULL verify method
+|- style="background:#CCFFFF; font-size: 110%;"
-#NACO normalization
+| || 1XX $a main entry must verify if it exists in both records (full, naco); 1 word must verify
-#Use 1 word
+|-
 ==links==

@@ Line 16: / Line 16: @@
 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.

@@ Line 20: / Line 20: @@
    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.
+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''':
+'''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''':
+'''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.

@@ Line 17: / Line 17: @@
 Examples of ''length'' being used with the different verify methods:
-  <font size="3">
+'''FULL verification with length of 5 being used''':
-FULL verification with length of 5 being used:
+   If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.
-   If record had, '''100 $a Johnson, Mark''', then Johns would be used as the verify string.</font>
 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:
+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.</font>
+   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:
+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.</font>
+   '''Orson''', '''Scott''', or '''Card''' could be used.
 === Words ===

@@ Line 23: / Line 23: @@
 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 l0 being used:
+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.</font>

← Older revision		Revision as of 15:00, 1 April 2013
Line 12:		Line 12:

	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.		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 ===		=== Length ===

@@ Line 1: / Line 1: @@
 [[Image:d3-9.png]]<br><br>
-==LINKS==
+=== Description ===
 <center><font size="4">[[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]]</font></center>
 [[category:Profile Guide]]