p_manage_31: COR fields are not being created when loading Authorities

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

Description:
Using p_manage_31, we loaded a series of Authority record files, which represented updates to existing Authority records on our database. These updates included name changes, addition of death dates, etc.

We have fix_doc_preferred included in section P-31 of tab_fix in the $data_tab directory of our Authority library. The header of tab_fix states this:

! P-31 is run automatically when authority records are loaded to the
! authority database by the Load authority records batch process (p_manage_31).

The records were successfully matched and overlaid, with the new 1xx fields in place. However, the COR field, which would be used for automatic correction of Bib records, was not created.

Resolution:
The tab_fix header is incorrect. The default fix-routine for p_manage_31 is "NONE". You must explicitly select "P-31" as the fix routine from the droplist on the submission form.

(Note: We are requesting that P-31 be made the default -- or that the tab_fix header be changed.)