Update to HOL 852 Collection code doesn't trigger update to Primo

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

Description:
Changes to collection description (column 4) in tab40 are reflected immediately in the Aleph OPAC, but the PNX in Primo isn’t changed; the old description displays in Primo.

Resolution:
The ue_21 publishing daemon needs to be restarted after the change to tab40.lng and the bib record, with the changed Collection description, resent to Primo.

Assuming the collection code is included in a bib word index (such as "wsc"), run the ret-03 Service to retrieve the keys of bib records linked to HOL records with the collection code which has had its text changed.

Use the output from ret-03 as input to manage-40 in the bib library. This will generate a z07 record, which will be processed by ue_01 to generate a z07p, which will be processed by ue_21, which will generate a changed z00p record with the changed collection description included, which will be processed by publish-06 and included in the tar file processed by the Primo pipe to create new PNX in Primo. Note that ue_21 needs to be restarted after making the change to tab40, in order for the new tab40 to be used in generating the changed text for the z00p AVA field.

The same principle applies to sublibrary description changes (in tab_sub_library.lng).

• Article last edited: 2/26/2015