Adding Links to the PNX

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Links that relate to a specific record are always stored in the links section in the PNX. As noted above, the links can be static and transferred with no change from the source record, or they can be a template as shown below:

<links>
    <openurl>$$Topenurl_journal</openurl>
    <backlink>$$Taleph_backlink$$Ebacklink</backlink>
    <linktorsrc>$$Uhttp://purl.access.gpo.gov/GPO/LPS70411$$DOn campus access only</linktorsrc>
    <thumbnail>$$Tamazon_thumb</thumbnail>
    <thumbnail><links>$$Tgoogle_thumb</links></thumbnail>
    <linktotoc>$$Tamazon_toc$$Elinktotoc</links></linktotoc>
    <openurlfulltext>$$Topenurlfull_journal</openurlfulltext>
    <linktoholdings>$$Taleph_holdings</linktoholdings>
    <linktouc>$$Tamazon_uc$$Eamazon</linktouc>
    <linktouc>$$Tworldcat_isbn$$Eworldcat</linktouc>
</links>

Static links should be prefixed by $$U, as shown in the following example:

<linktorsrc>$$Uhttp://purl.access.gpo.gov/GPO/LPS70411$$Don campus access only</linktorsrc>

Template codes should be prefixed with $$T, as shown in the following example:

<linktotoc>$$Tamazon_toc$$Elinktotoc</linktotoc>

The template codes are defined in the Templates mapping table. For more details, see Mapping Table Reference.

In addition to the URL and template codes, the link fields can include the following prefixes:

$$D/$$E – allows you to display text for links. Links that display in the Details tab can display text in place of the link. The text is added to the field in the PNX either as simple text (which must be prefixed with $$D) or a code (which must be prefixed with $$E). The code is translated to text via the Full Display Labels code table in the Front End subsystem.
$$G – For CDI, it contains the provider name if included in the links/linktorsrcadditional field and allows multiple links to be sorted by provider name.
$$H – For CDI, it contains an open access indication if included in the links/linktorsrcadditional field. This subfield should include the text free_for_read if the link is Open Access.
$$I – allows you to add an institution code to links. This will ensure that the link is visible and used only by users who belong to the institution in $$I. Only one institution can be defined.

For example, there is a dedup record to an online e-book that requires a subscription to access it and the Primo installation is a consortium. You can add $$I to the link so that it only displays in the Details tab and is only used by the delivery manager for users belonging to INST1 and INST3. These links may appears as follows in the PNX record:

Links/linktorsrc $$Uhttp://www.ebsco.com/book1$$DElectronic version$$IINST1

Links/linktorsrc $$Uhttp://www.ebsco.com/book1$$Delectronic version$$IINST3
$$A - $$Z/$$a - $$z/$$0 - $$9 – allows you to include data required for the link. In most cases, the data that is required for the link is present in the PNX (such as the source system number or ISBN). If this is not the case, it is possible to add this data to the link field using the prefix $$, followed by any digit or English letter. The digit or letter can then be used in the template as a placeholder. This option does not apply to static links.

For example, if the template is defined as follows:

http://purl.opac.access/Vakka/search.action?series={{$$1}}}&avain={{control/addsrcrecordid}}}

And the PNX record contains the following link information:

<links>

<backlink>$$TMYINST_ds1_backlink$$Eds1_backlink$$1AY</backlink>

</links>

The system will display the URL in the FE as follows:

http://purl.opac.access/Vakka/search.action?series=AY&avain=SARK__5401.SARK