Difference between revisions of "Dedupe 6.3"
Line 1: | Line 1: | ||
+ | ==Dedupe 6.3 - Retained Fields== | ||
[[Image:d6-3.png]]<br><br> | [[Image:d6-3.png]]<br><br> | ||
− | == | + | ===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><font size="4">[[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]] | <center><font size="4">[[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> | <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> | [[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]] | [[category:Profile Guide]] |
Revision as of 09:17, 1 April 2013
Contents
Dedupe 6.3 - Retained Fields
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
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0