p_manage_50: Second Run Disconnects Existing Item from HOL Record
- Article Type: General
- Product: Aleph
- Product Version: 17.01
- Relevant for Installation Type: Dedicated-Direct; Direct; Local;
Problem symptoms
* Attempt to load items and holdings records for 2 sublibraries within the same ADM with v17; when p_manage_50 is run second time to create items/holdings records for the second sublibrary, it loads double the number of holdings records and messes up the 852 field.
* Log message from manage-50 run
Number of bib records read: 000000314
Number of ADM records created: 000000000
Number of HOL records created: 000000628
Number of item records created: 000000314
Note HOL count is double bib records read and item records created, and first Holding record which is formatted correctly after running p_manage_50 the first time no longer has an Item record attached to it, and neither Holding record is formatted correctly.
Cause
Both runs of p_manage_50 are specifying: p_hol_item_interact "A".
Resolution:
"A" should be used only in the case where there are no existing HOL records.
In the case where one is running p_manage_50 multiple times and creating both the item record and the HOL record in each run, the value you want to use for p_hol_item_interact is "N".
- Article last edited: 10/8/2013