- Article Type: Q&A
- Product: Aleph
- Product Version: 20
The Aleph Publishing Mechanism document recommends deleting the 005 field in publishing. From page 15: "Tab_fix: The following setup is recommended to prevent the updating of Z00P due to a change in the 005 field (which is updated whenever the BIB record is saved in the cataloging client): ...."
Why is this is recommended, and what effect it will have?
If most bib records don't have 005 fields, these table changes can be omitted.
If bib records do have 005 fields and are often sent to the server without having any change made, then these table changes will prevent the records from being re-sent to Primo unnecessarily. (This doesn't do any harm; it just adds to the publishing workload.)
This change will *not* prevent changed records from being re-sent to Primo; Primo does not need or use the 005 field.
Subject: Publishing Server Configurations
- Article last edited: 10/8/2013