Dedupe 2.8 - Revision history

Nate: /* Only if Both */

2013-04-02T19:16:56Z

‎Only if Both

Nate: /* Only if Both */

2013-04-02T19:16:37Z

‎Only if Both

Nate at 19:16, 2 April 2013

2013-04-02T19:16:15Z

Nate at 19:16, 2 April 2013

2013-04-02T19:16:01Z

Nate at 19:14, 2 April 2013

2013-04-02T19:14:51Z

Nate: /* links */

2013-04-02T17:04:36Z

‎links

Nate: /* subfield p - Name of part/section of a work */

2013-04-01T21:15:43Z

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

Nate: /* subfield n - Number of part/section of a work */

2013-04-01T21:15:21Z

‎subfield n - Number of part/section of a work

Nate: /* Default */

2013-04-01T20:17:20Z

‎Default

Nate: /* Default */

2013-04-01T20:15:13Z

‎Default

@@ Line 84: / Line 84: @@
    <font size="3">
    Record A has:
-$a Adventures of Huckleberry Finn. $n Part two.
+$a Adventures of Huckleberry Finn. <font color="red">$n Part two</font>.
    Record B has:

@@ Line 86: / Line 86: @@
 $a Adventures of Huckleberry Finn. $n Part two.
-   Record B has no 100
+   Record B has:
 $a Adventures of Huckleberry Finn.</font>
 '''RESULT''': This would be a match because 245 $n exists in one record but not the other.

@@ Line 6: / Line 6: @@
 Every MARC record must have a 245 field, but not necessarily a subfield n and/or p.
-===245 $n====
+===245 $n===
 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.
@@ Line 13: / Line 13: @@
 $a Travels through the orient. <font color="red">$n Volume 2, pt. 4</font>.</font>
-===245 $p====
+===245 $p===
    <font size="3">
 $a Travels through the orient. $n Volume 2, <font color="red">$p Burma</font>.

@@ Line 1: / Line 1: @@
 == Dedupe 2.8: Group 1 - 245 $n, $p - Title (Verify)==
 [[Image:d2-8.png]]<br><br>
-=== Description ===
+== 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====
+===245 $n====
 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.
@@ Line 13: / Line 13: @@
 $a Travels through the orient. <font color="red">$n Volume 2, pt. 4</font>.</font>
-====subfield p - Name of part/section of a work====
+===245 $p====
-−
    <font size="3">
 $a Travels through the orient. $n Volume 2, <font color="red">$p Burma</font>.
 $a New England byways. $n Part 1, <font color="red">$p Vermont</font>. $n Part 2, <font color="red">$p Massachusetts</font></font>
-=== Verify Method ===
+== Verify 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====
+===Full===
 Full compares the entire verify string up to the verify length.
-====Partial====
+===Partial===
 Partial truncates the compare strings to the shortest string, then does a full compare:
    <font size="3">
@@ Line 32: / Line 31: @@
      $a American history in the 20th century. $p <font color="blue">Part 1</font>-1.</font>
 Partial matching returns these two records as a match.
-====Within====
+===Within===
 Within searches each compare string truncated at verify length against the full un-truncated string of the other field:
    <font size="3">
@@ Line 77: / Line 76: @@
 NOTE: Non-filers are excluded from Words.
-===Must Verify===
+==Must Verify==
 This option requires the given field to match between the two records. It also means that the verify field in question must exist in both records (and must match). This is typically common to include as part of the 245 title verification, though other fields may find it useful as well.
-===Only if Both===
+==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:

@@ Line 20: / Line 20: @@
 === Verify Method ===
-*FULL - Full compares the full verify string up to the verify length.
+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.
-*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.
+====Full====
-*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."
+Full compares the entire verify string up to the verify length.
-=== Normalization ===
+Types of normalization are:
-*NACO/CJK retains spaces and subfield delimiters.
+*NACO/CJK - retains spaces and subfield delimiters
-*FULL is NACO normalization with all spaces and subfield delimiters removed.
+*FULL - all spaces and subfield delimiters removed
-=== Length ===
+===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.
+This refers to how much of a given string the program will present for potential matches:
-=== Words ===
+===Must Verify===
-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.
+This option requires the given field to match between the two records. It also means that the verify field in question must exist in both records (and must match). This is typically common to include as part of the 245 title verification, though other fields may find it useful as well.
 == Default==

@@ Line 43: / Line 43: @@
 ==links==
-<center><font size="4">[[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]]
+<center><font size="4">[[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]] - [[Dedupe_2.13|2.13]]
 <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:Dedupe Profile Guide]]

@@ Line 10: / Line 10: @@
    <font size="3">
-$a Divine comedy. $n Third part.
+$a Divine comedy. <font color="red">$n Third part</font>.
-$a Travels through the orient. $n Volume 2, pt. 4.</font>
+$a Travels through the orient. <font color="red">$n Volume 2, pt. 4</font>.</font>
 ====subfield p - Name of part/section of a work====

@@ Line 38: / Line 38: @@
 ! style="background:lightgray" align="left" colspan="2" | Group 1 (010, 020, 022)
 |- style="background:#CCFFFF; font-size: 110%;"
-| || 245 $n, $p titles must verify if fields exist in both records (full, NACO)
+| || 245 $n, $p titles must verify if fields exist in both records (full, naco)
 |}
 <div style=clear:both></div><br>