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

Description:
[1] We are currently implementing Primo and are confused about the LKR ("PLK") fields (PNX records) in Primo. What do you recommend?

[2] We're currently testing the Aleph 20.2 service pack, and I'm trying to determine if Change Number 3050 is applicable to
our institution. We do publish documents to Primo, but to the best of my knowledge, we are not sending the LKR field.
Would it be possible to get some additional background information? Are these implementation steps required for all institutions that publish documents to Primo?

Resolution:
The LKR fields are ones with DN, UP, and PAR as values. The rep_change makes it so the published record contains these fields in a usable form.
If you are publishing records which contain DN, UP, and PAR LKR fields, you should include the expand_doc_primo_plk in the xxx01 tab_expand.

The following SQL shows that abc01 does have DN, UP, and PAR links:

abc01@ALEPH18> select z103_lkr_type, count(*) from z103 group by z103_lkr_type;
Z10 COUNT(*)
--- ----------
348 2
ADM 389085
DN 9135
HOL 351875
ITM 3960
L 1
PAR 1994
UIT 2
UP 9134
2

The following line which you have included in abc01 tab_expand should be bringing these tags into the extracted records:
FULLP expand_doc_primo_plk

That is all you need to do.

Note: the 348, L, UIT, and blank z103's (LKR content) are mistakes. We recommend that these be corrected.

• Article last edited: 10/8/2013