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

Description:
We did some loads/updates earlier in the week to our Authorities records using p_manage_18. Later in the week we noticed that there was a large number of records in the z07 of the *Bib* library which were waiting to be indexed (well over 200,000 records). We cannot figure out if these records came from the run of p_manage_18 or from something else.

Questions:

1) Could running p_manage_18 on ABC10 really cause that many updates to ABC01?

2) If it was not that, how best can we determine where these z07 records did come from. There were a couple Marcive loads to ABC01, but it is still unclear how that would have placed so many records into ABC01 z07.

Resolution:
We see this in the abc01 $data_scratch:

-rw-rw-r-- 1 aleph18 exlibris 799935 Sep 7 03:00 run_e_08.22047
-rw-rw-r-- 1 aleph18 exlibris 1062643 Sep 14 03:00 run_e_08.13168
-rw-rw-r-- 1 aleph18 exlibris 524326936 Sep 21 03:00 run_e_08.5837
-rw-rw-r-- 1 aleph18 exlibris 15190 Sep 21 10:10 run_e_08.15034

>>grep -c 'Update doc -' run_e_08.5837

1198246

This means that ue_08 generated 1.1 million z07s. Looking at the run_e_08.5837 log we can see that the source was authority updates.

The Z07_SEQUENCE is a date/time. To give priority to current Cataloging, new z07's are backdated to "1990" and GUI cataloging updates are backdated to "1998". ue_08 updates are not backdated. This is described in KB 8192-7643.

Thus, if it is not your intention to have these authority updates flip the bib record heading fields, you could delete the z07's generated by ue_08 by limiting the delete to z07's with a Z07_SEQUENCE beginning with the current year.

KB 4093 has more on sources of z07's.

• Article last edited: 10/8/2013