Handling deleted Aleph records in Primo
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Description:
How does Primo deal with deleted Aleph records? Are such deletions passed to Primo?
Resolution:
When a record which exists in Primo is deleted in Aleph, the Aleph z00p (Publishing) record should appear with z00p_status DELETED and with a z00p_timestamp of the date of its deletion. Assuming so, it will be sent to Primo.
When a record is deleted in Aleph, even if it is part of a base specified in col. 2 of the ./xxx01/tab/tab_publish and even if that base's $alephe_tab/tab_base.lng entry specifies "alldocuments not wst=(suppressed or deleted)", testing shows that the z00p_status *will* be updated to "DELETED". (And, thus, subsequently sent to Primo.)
Note: When a deleted record is re-deleted in GUI Cataloging, its z00p_timestamp *is* updated to the current date. Thus, in order to have deleted records be re-sent to Primo -- assuming that they have an existing z00p which can be updated -- they could be re-deleted in Aleph.
Additional Information
Primo identifies records as 'deleted' only if the value of position 05 of the LDR field is set to d. In this case the record is deleted logically from Primo DB and it is deleted from the indexes. The deleted records still have been stored in the database (p_pnx table) with SECONTROL=3.
- Article last edited: 12-Mar-2016