Random items, holdings, etc. attached to new bib records.

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

Description:
When you create a bib record you find that already-existing items, HOL records, and/or subcription (Z16) are automatically linked to it.

Resolution:
This happens when there are already-existing xxx50 ADM records (and xxxx60 HOL records) with LKR fields linking them to bib records which don't exist in this file. (This happens ONLY in a conversion or upgrade situation where the xxx50 or xxx60 libraries are extracted after the xxx01 library. This can *not* happen when the ADM records in question have been created online.) When a bib record with this number is created, rather than creating a new ADM, the system uses this already-existing ADM (with its Z30, Z16, etc., records).

In this situation, the solution is to increase the last-doc-number in the bib library (util g/2) to be 1 higher than the adm library last-doc-number.

{In the case where the adm last-doc-number is in the 9 million range (to permit xxx01/xxx50 synchronization where there are xxx30 or xxx02 libraries sharing the xxx50) you need to check, using sql, to find what the last pre-9-million-range ADM # is and make it higher than that.}

After changing the bib last-doc-number, you need to add a record using the GUI client before running any batch jobs -- see KB# 3961for explanation.

In a production database, you would need to answer the question, "What happened to the bib records?"