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

    GDC: fixed fields must have placeholders to update correct field position

    • Product: Voyager
    • Product Version: 8.0.0 - 9.1.0

    Symptoms

    New value in fixed field added in wrong position

    Defect Status

    Issue VYG-5808 is resolved for Voyager 9.1.0 and higher.

    Replication Steps

    1. Create a Data Change Rule Set to
      1. add an 006 field
      2. 006 field has only 1 value, m in byte 00
    2. Add Data Change Rule Set to Data Change Rule Set Group.
    3. Run a Data Change Job to add this 006 field to 1 or more records.
    4. Create a Data Change Rule Set to add value o to byte 06 in 006 field.
    5. Preview change with set of records from steps 1-2. Note that the value o is added in byte 01.
    6. Run a Data Change Job to add this value to the 006 fields in the same record set used in step 1-2. Note that value o is added to byte 01 in the 006 field.

    Workaround

    If 006 is already added to the record, fill any bytes between the last byte in the field and the one being replaced with spaces & adjust rule to at the correct position.
    In example above, string would start at byte 01 and have 5 spaces, the new value (o), and any remaining space in the fixed field should be filled with spaces as well for future changes.
    ____o_____
    where underscore (_) is a space/placeholder for empty values in the field.
    If creating new 006, create 006 using a space as placeholder for any empty byte values in the field.

     


    • Article last edited: 17-Oct-2014
    • Was this article helpful?