Difference between revisions of "Dedupe 6.1"

From AC Wiki
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
==Dedupe 6.1: Backstage Change Stamp==
 
==Dedupe 6.1: Backstage Change Stamp==
 
[[Image:d6-1.png]]<br><br>
 
[[Image:d6-1.png]]<br><br>
MARS 2.0 can '''stamp''' each bibliographic record with one or more of the following identifiers or only those bibliographic records that were changed during the MARS 2.0 process.
+
Some customers prefer to have a stamp added to records that a vendor has modified in some way. These stamps make it easier to identify which records have already undergone processing and which records may still need to be submitted.
 
+
Backstage can add an 040 $d UtOrBLW to all or only merged records.
Indicate in Step 4.2 which, if any, of the following stamp options you would like in your bibliographic records and indicate if you would like to stamp all bibs or only the bib records where fields were merged in from other matching records:
+
===All Records===
*'''040''': MARC Organization Code '''UtOrBLW''' can be added to the modifying agency $d in the 040 field. A new 040 field is added to any record lacking an 040 field.
+
All will add this field to all records, regardless of whether the record deduped into another record.  This option is useful for customers that wish to designate every record that was processed by Backstage
 
+
===Merged Only Records===
 +
Merged will only add this stamp to records where fields were retained from a matched record.  Note that this option will only add the stamp to records where some other field was merged into the matching record.  So if a record is deduped (where the original record found a matching record), yet no fields were retained during the dedupe, the 040 $d UtOrBLW will not be added in this case.
 +
===Default===
 +
*Add 040 $d UtOrBLW to all records.
 
==links==
 
==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]]

Latest revision as of 10:05, 1 April 2013

Dedupe 6.1: Backstage Change Stamp

D6-1.png

Some customers prefer to have a stamp added to records that a vendor has modified in some way. These stamps make it easier to identify which records have already undergone processing and which records may still need to be submitted. Backstage can add an 040 $d UtOrBLW to all or only merged records.

All Records

All will add this field to all records, regardless of whether the record deduped into another record. This option is useful for customers that wish to designate every record that was processed by Backstage

Merged Only Records

Merged will only add this stamp to records where fields were retained from a matched record. Note that this option will only add the stamp to records where some other field was merged into the matching record. So if a record is deduped (where the original record found a matching record), yet no fields were retained during the dedupe, the 040 $d UtOrBLW will not be added in this case.

Default

  • Add 040 $d UtOrBLW to all records.

links

6.1 - 6.2 - 6.3 - 6.4 - 6.5
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0