Primo Central Interaction with Uresolver or SFX
- Article Type: Q&A
- Product: Alma
What interaction is there between SFX or the Uresolver and Primo Central (PC) and what are the implications for the user interface (UI)?
This is a general explanation of the interaction between SFX / Uresolver (Alma) and PC and the UI implications.
The process is divided into 3 parts:
1. Results from Primo Central that are shown in the Primo UI
2. Availability status that is displayed for each result record in the Primo UI
3. Delivery options, as provided in the SFX or Uresolver menu that provides links to the cited item via activated Targets.
The records that are displayed in the Primo UI are a result of the customer-activated collections in the PC registration system via "Edit client resource collections" section. The collection configuration is responsible for the records that show up in search results, without relation to SFX or Uresolver configuration.
NOTE that changes made in the PC activated collections take up to 7 days until the impact is seen in the UI due to the PC weekly cycle that applies the local changes to PC.
The Availability status is determined by the local holdings file. This is achieved by comparing record identifiers (ISSN, ISBN, DOI, etc) in activated collections with the same attributes in the holdings file content. The holdings file is created by a cron'd SFX / Uresolver process which exports the activated Objects from SFX / Alma. After the file is created, PC retrieves the holdings file during its weekly cycle. Only then is the information updated in PC and the Availability status will be changed to its new status.
NOTE that it can take up to 14 days till a new Availability status will be displayed in the UI. It depends on the SFX / Alma record update date, the holdings file export, and PC weekly cycle (which can vary).
The links to the item are created online based on the SFX / Alma configuration and activations. Based on record metadata, corresponding links are displayed in the SFX / Uresolver menu.
- Article last edited: 12/26/2013