Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    What can prevent a deleted Aleph bib record from being removed from Primo

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description

    What can prevent a deleted Aleph bib record from being removed from Primo?

    Resolution

    In order for a deleted Aleph bib record to be removed from Primo, these conditions must be met:

     1. there needs to be an existing z00p for the record in Aleph

     2. a z07p (publishing request) needs to be created for the record

     3. ue_21 needs to process the z07p and update the z00p_status to "Deleted".

     4. publish-06 needs to create a publishing tar file containing the z00p for this record (manually changing the $aleph_root/tab/tab_publish_timestamp could prevent this from happening)

     5. the tar file needs to be successfully harvested and indexed by Primo.

    If any of these steps doesn't happen, the deleted Aleph bib record will not be removed from Primo.

     

    In such cases, especially with a smaller database, the simplest/best way to correct the problem is a complete republishing, as described in the article How to re-publish all Aleph records .  Be sure to specify multiple processes as described in the article.

     
    See also: Handling deleted Aleph records which lack z00p and can't be removed from Primo .

     


    • Article last edited: 16-Aug-2016