Skip to main content
Ex Libris Knowledge Center

BULK: Wrong call number sometimes pulled with multiple hierarchies

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

Problem Symptoms:
* Import records with multiple call number fields & wrong field used in mfhd
* Import rule contains Mapping with multiple call number hierarchies

Cause:
This behavior is the result of Issue VYG-5301.

Resolution:
Issue VYG-5301 is resolved for Voyager 9.1.0 and higher.

Additional Information

1. In SysAdmin, set up 2 call number hierarchies:
-- Hierarchy 1: Call Number Type=Library of Congress
* * 099 a b
* * 090 a b
* * 050 a b
-- Hierarchy 2: Call Number Type=Dewey Decimal
* * 099 a b
* * 092 a b
2. Create a bulk import rule that
-- Creates bibs & mfhds
-- Contains both call number hierarchies in Mapping
-- Will match Hierarchy 1 with the incoming record. For attached record, use
PBBA / {Voyager item} / PBBA / {Voyager Loc} / Hierarchy 1
PBBK / {Voyager item} / PBBK / {Voyager Loc} / Hierarchy 2
* / {Voyager item} / * / {Voyager Loc} / Hierarchy 1
and use 049 |a as Location field & item type field.
3. Import 4th record in attached file.
4. View resulting records in Cataloging. Note that while the incoming bib record contains PBBA in the loc & item type field/subfield, which matches to the first mapping line & should use Hierarchy 1 (050 field), the mfhd call number is from Hierarchy 2 (092 field).

Category: Batch jobs


  • Article last edited: 10/16/2014