- Article Type: General
- Product: Voyager
- Product Version: 8.1.2
Bug Report for Issue 16384-14417
Date: 3 May 2011
Module: GDC (Global Data Change)
Release replicated in: 8.0.0
Last version without bug: n/a
Expected results: To be able to specify multiple conditions in a data change rule when necessary to ensure appropriate fields are changed.
Actual results: If it is necessary to specify an additional condition for a data change rule, the data change rule doesn’t work.
Workflow implications: Some fields in some records cannot be changed with GDC.
1. Import and save the two attached records in your database. In GDC, create a set with these two bibs.
2. Import the 2 attached data change rule docs in GDC. The rules are both intended to add a death date to $d in 600 fields for Richard Nixon.
3. Preview the data change using the two bib set, and the rule Born1913.dslr; this rule specifies the condition:
4. MARC Field Value 600d Equals 1913-
and specifies the consequence
Replace String with String Field 600d Replace String 1913- With String 1913-1994
5. Notice that the first record (“The resurrection of Richard Nixon”) displays the change, adding a death date of 1994 to the 600 field.
6. Now look at the second record (“We the people”). Notice that the 600 $d for Gerald Ford matches the condition in the rule.
7. Go back and preview the data using the rule Nixon1913.dslr, which adds the additional condition:
MARC Field Value 600a Contains Nixon
The rule cannot be implemented with this additional condition.
Workaround: Remove records from set where multiple fields match condition and some should not be changed, and make edits manually. Or, specify Field Occurrence in the rule if consistent through record set.
Fixed in Voyager 8.1.2.
- Article last edited: 3/4/2015