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

    expand_doc_primo_plk not created for “father” records

    • Article Type: General
    • Product: Aleph
    • Product Version: 21
    • Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

    Problem Symptoms: 

    Program expand_doc_primo_plk creates a field PLK with information from a UP or DN linked record in order to make it possible after publishing to Primo to show the appropriate links in Primo. But PLK field is only created when a record is saved on server which means that if you create a father record which is published to Primo (without PLK field) and afterwards you create a son record the PLK field will never be created in the father record except you save the father record again on server (what you normally don't do).




    Rep_change #2377 in Aleph 21.

    Description: The expand_doc_primo_plk routine creates a PLK field with information from "UP" or "DOWN" linked records. This field is used to show the relevant links in Primo, after publishing from Aleph is performed. However, PLK fields are created only when a record is saved on the server. This means that if a "father" record is created and published to Primo (without a PLK field) and then a "son" record is created, the PLK field is not created in the "father" record, unless it is saved to the server again (which is usually not done).

    Solution: This has been corrected by adding a new routine - update_z103_primo_plk - to be used in the tab_z103 table.


    • Article last edited: 16-June-2016