- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
We want change the collection codes in certain items. What tables are involved?
My understanding is that a global change to z30 will not of itself result in a cascaded change to the HOL records. The same situation presumably pertains in reverse, i.e., that globally changing 852$b and $c in the xxx60 records will not cascade the change to the z30 sublibrary and collection codes in xxx50.
(Note: If it's the *Sublibrary Code* you are wanting to change, see KB 8192-3736.)
The Collection Code is used in 6 tables. (Do "asm copy", then "grep COLLECTION *" to see them.) The important one, besides z30, is the z16: you should check to see if there are subscription records containing the code.)
Accounting for the preceding, if you want to change the collection code in items and HOL records:
First, use the p_manage_21 global change job to change the collection code in the HOL 852 field. In the case where there are items connected to the HOL record via their z30_hol_doc_number and where the TAB100 : 852-ITEM-OVERRIDE is set to "Y" and where the z30_temp_location flag is not "Y", the change will be propagated to the associated item records automatically (via ue_01; make sure ue_01 is running in the xxx60 library).
After this job is finished you should use SQL to check the z30 table to see if there are still items with the old collection, since there may be items not linked to any HOL or items containing the collection as a temporary location. These would need to be changed using SQL.
Note: A change via SQL will not result in the item being sent for reindexing, unlike the p_manage_21.
p_manage_62 ("Update items records") could be used in this step instead of SQL *if* you are updating just the sublibrary or just the collection. It doesn't allow for a combination of fields (such as you can do in SQL).
- Article last edited: 21-Sep-2017