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

    p_manage_18: protecting ALEPH tags when loading processed bibs from vendor

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    We thought we were successful in loading our first batch of bibs precessed by our authorities vendor, Backstage Library Works. We loaded 118,000+ records into Prod. However, we have created a major glitch for ourselves.

    Our process is to add a 928 local MARC tag to every bib in cataloging that has $$a AUTHORITY. We indexed that field and use it to retrieve records to send out using p_ret_03. We then use p_print_03 to send them to BSLW. We download them in MARC format with a 001 field for the system record number. We load them back in after having employed a fix on the whole file enabling the use of SYSIN fix routine to match on the system number. In p_manage_18 we used "Procedure to run" "Update current records in database", Replace entire record, full indexing, SYSIN fix routine, and no merge routine.

    We lost all the ALEPH tags. Most critical were the OWN codes and the LKR fields. We need to have a way to protect LKR. We would also like to save the CAT field. How do I set up a merge routine to do this? Is this handled in tab_merge_overlay or do we need a separate merge routine? What we need to do is retain the OWN, LKR, CAT, etc. in the database record while taking all the BSLW processing from the incoming record.

    We are also trying to figure out if there is a way to restore what we lost.

    This would be done with the p_manage_38 merge followed by p_manage_18 -- or just p_manage_18. See KB 16384-8081.

    The site did not have an individual backup of the bib records from before they were overwritten by the reload, but in the meantime a switch from 32-bit Oracle to 64-bit Oracle had occurred for all of the Oracle tables, and the old, 32-bit instance was still available. Rather than restoring a complete backup, we were able to: connect to that 32-bit instance, extract the affected bib records using p_print_03, connect back to the current 64-bit instance, and then run p_manage_18 with Merge to add the STA, LKR, CAT, and OWN fields to the records.

    • Article last edited: 10/8/2013