How to use a Voyager Global Data Change scan job to identify records that do not have a certain MARC field
- Product: Voyager
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Question
How do I run a GDC scan job to identify records that do not have a certain MARC field (for example the 946)?
Answer
Add the following two scan rule sets to a single scan rule set group:
- Create a scan rule with a consequence of Include, which is "always true" (for example use "MARC Control Field Exists" for Field LDR).
- Create a scan rule with the condition "MARC Field/Subfield Exists" for (for example) Field 946, and a consequence of Exclude.
This will put the BIB IDs of the records without a 946 field in your record set.
Additional Information
Frequently customers want to use this functionality in GDC to then add a new MARC field and subfield to the records in the record set. See: Overview of using Voyager Global Data Change to add a new MARC field and subfield
See also: GDC: Scan to Exclude does not add records to set
A variation of the condition in Step 2, but using a consequence of Include, can be used to identify records that have a certain MARC field. In this case Step 1 is not required.
- Article last edited: 13-May-2020