Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    GDC: Data change fails with "equals" in Condition

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.2

    Issue number: 16384-20593
    Module: Global Data Change
    Releases replicated in: 8.0.0 – 8.1.2
    Last version without bug: n/a

    Expected results: If a GDC Data Change Rule using condition MARC Field Value “equals” with the exact string held in a subfield, GDC would identify the match and make the change.

    Actual results: When the “equals” operator is used in a condition for a change rule, no change is applied.

    Workflow implications: Unable to make some changes with GDC.

    Replication steps:
    *example Rule and record set is attached.
    1. GDC>Rules>Data Change Rule Set>New>Add>Conditions>Add
    2. Select “MARC Field Value” and enter a Field/Subfield.
    3. For operator, select “equals” and input the exact contents of the subfield from step 2.
    4. Give the rule a consequence and save the Rule Set.
    5. Add the Rule Set to a Rule Set Group in GDC>Rules>Data Change Rule Sets
    5. Go to GDC>Preview or GDC>Job Management> Submit Data Change job and select the rule you created and a Record set that includes the field and value from steps 2 and 3.
    6. In Preview, you’ll receive “There are MARC validation errors in the ‘after’ record” and when you click on “View Validation Errors …” you see ‘Error implementing data change rule’
    7. When actually running a job with the rule, it will fail:
    INFO - Start Transforming records...
    INFO - Error Transforming records!!!
    INFO - Transform 1 Elapsed Time: 00:00:11
    ERROR - Record Transform Failed
    ERROR - Job failed...
    End Time = Mon Dec 10 11:35:27 CST 2012
    Records Processed = 0
    Records Deleted = 0
    Record Errors = 0
    Running Time = 00:00:26

    Workaround: Use “contains” instead of “equals” where possible.

    Other information: If the “contains” string is part of multiple fields in a record, it may match more fields than desired for the data change.

    Fixed in Voyager 8.2.2.

    • Article last edited: 3/4/2015