Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Update previously loaded only uses first call number in hierarchy

    • Product: Voyager
    • Product Version: 9.2.0
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

    Symptoms

    Call number in imported bib is in field that appears after first priority field in Call Number Hierarchy.

    Call number not mapped to MFHD when import using "Update previously loaded MFHDs and/or Items"

    Defect Status

    Issue VYG-7024 is currently in Development.

    Replication Steps

    1. System Administration > Cataloging > Call Number Hierarchy > New > set Ind1 / Ind2 / Field / Subfld / Cutter-SubFld as follows:
      1. * / * / 050 / a / b
      2. * / * / 090 / a / b
    2. System Administration > Cataloging > Bulk Import Rules > New > set rule to use Call Number hierarchy from step 1 and "Update previously loaded MFHDs and/or Items"
    3. Ensure import record will match record in database and matches mfhd location, owning library and vendor reference number in line item so it can be udpated and an item created.
    4. Import record that has call number in 090 subfields a and b.
    5. Note that bib is updated, item is created, but mfhd call number is not updated.
    6. Import record that is identical except call number in 050 subfields and b, OR alter Call Number Hierarchy so that 090 is first priority in the hierarchy.
    7. Note that mfhd call number is now updated.

    Workaround

    Manually update call number; OR

    Manually edit file of records so all call numbers map from same field, and set that field as first priority in Call Number Hierarchy.

     


    • Article last edited: 21-Jun-2016
    //doorbell.io feedback widged