Return to menu
Linking in CDI works very similar to how it works today in Primo Central, and collections will continue to use the same linking methods with CDI. Links displayed on the UI are only those to which that library has access. In many cases, this will only be one because you subscribe to the article or book or other material on only one platform. In this case, only this link is displayed. If there are several options – you subscribe to the same item on several platforms – then one linking method described below will be used according to a priority setting. The priority settings in the merged CDI records are described in the Link Prioritization in the Merged Record.
Supported Linking Methods
Primo supports the following linking methods, which are set at the collection level:
OpenURL linking – Full text linking is handled by the link resolver (Alma/SFX), which allows the library to decide which links to display and their order. Where possible, Primo will add a platform-specific document ID to the OpenURL to allow the link resolver to use that ID to link to the full text instead of using metadata to create the link. This ensures a higher reliability of the links. OpenURL linking is used for approximately 60 percent of the collections indexed in CDI. Collections that use this method include primary publishers and, in general, collections that contain mainstream material such as articles and books that may be available from more than one platform.
Link in Record – In cases where the record is uniquely available from a single platform and/or the link is difficult or impossible to create using the link resolver, Primo will use the link stored in the record, which has been provided by the information provider, in CDI. This method is used for approximately 40 percent of the collections. Collections that use this method include for example video collections (such as Alexander Street Press), some reference collections, or collections that contain special and unique material.
Primo LinkTemplate CDI collections – This method is used rarely and is used for collections (for example, Naxos and Kanopy collections) where the linking method is the link in the record, but the provider requires Primo to add customer-specific parameters (which are stored in Primo’s linking templates) to the URL.
The term “Direct link” is often used in different contexts for different things. If not otherwise indicated, we use it to describe links that use the document ID of the original platform instead of metadata to link to the full text. Direct links are often more reliable than using metadata links. Direct links can be either links in the records (which are provided by the platform as part of the CDI data delivery) or links created by the link resolver if the OpenURL contained the document ID for a platform to which the user has access. Primo adds this document ID to the OpenURL for several collections, including Gale, Ingenta, and ProQuest and for primary publishers using a DOIs as a document ID. Both link resolvers (Alma and SFX) have functions that give preference to direct links over metadata links (if both are available) to increase the accuracy of linking. This setting is locally configurable.
For more information about this preference to direct links over metadata links in Alma, see Configuring the Order of Online Services.
For more information about this setting in SFX, see SFX General User Guide > Configuration > Menu Configuration > Menu Design – General Configuration > Giving Preference to Links Using Vendor Identifiers Validated by Ex Libris as Preferred Linking IDs.
SFX does not have online help. The link to the SFX General Users Guide in PDF format can be found here:
Link Prioritization in the Merged Record
Usually, all records that contribute to a merged record use either the link resolver or the link in the record, but there may be cases where items from a collection using the link resolver are merged with records using the link in the record. If you have only access to one of those links, then this will be displayed. However, if you have access to several of those platforms, then prioritization rules are applied. The possible scenarios and their linking behavior are as follows:
Merged records can be created from records in a collection that you may not subscribe to.
All records in a merged group are coming from collections using the link resolver – The merged record will use the link resolver (Alma/SFX), where the number of links displayed, the order of the links, and other priority settings are managed by the library. For Alma Link configuration, see Configuring the Order of Online Services.
All records in a merged group are coming from a collection using the link in the record – Typically, an institution has access rights only to one of the available platforms, and therefore links to those platforms will be displayed and used. If an institution has access to several platforms, the system will give priority to collections with the most reliable link, which is the direct link (using a document ID from the provider platform) if available.
One or more of the records in a merged group is coming from a collection using the link resolver, and others come from collections using the link in the record –
If the library has no access to any of the collections using the link in the record, the merged record will use the link resolver.
If the library has access to at least one of the collections that use the link in the record and that link is not for an open access item, those collections will be given precedence over the collections that use OpenURL. Links that use a document ID will be given priority over metadata links. If the "link in the record" collection is open access, then the OpenURL link will be given precedence.