Integrating campusM and Primo VE enables users to enjoy the full user experience of Primo VE built into their campusM mobile app and web portal. The simple-to-deploy integration, configured only within the App Manager, delivers a mobile-specific styling and structure, providing users with a seamless engagement of their library services through campsuM.
About Ex Libris Alma
Alma is the solution your library needs as the focal point of learning and research at your institution. Alma is designed to ensure that your entire collection can be managed through a single interface and that you can continue to serve students, instructors, and researchers with a collection optimized for their needs. With Alma you can manage all the resource types your collections include within a single interface, including electronic, print, and digital.
About Ex Libris Primo VE
Primo VE is Ex Libris' patron-facing discovery service, providing centralized and personalized access to all resources in your fulfillment network: your institution and any partner institutions. Patrons can locate physical, electronic, and digital resources in all locations, with availability information for physical resources (including the ability to request these resources for checkout at the location of the patron's choice), and instant online access to electronic and digital resources.
Alma information is published to Primo VE on a regular basis. Primo VE empowers libraries to shape the discovery experience, providing students, faculty and staff an intuitive, end-to-end service, and maximizing the value of library collections.
The following section describes information relating to the user experience for the Primo VE product integration.
Users are able to use Primo VE integration for any functionality available in Primo VE: search, view library card, submit a request, etc.
As described in the technical flow diagram, once user is logged in to campusM, authentication to Alma/Primo VE is being done behind the scenes (SSO) with the AlmaID received from the IDP. A login is not required from the user at any stage. If campusM sends an invalid AlmaID to Alma, the user will not be logged in and will need to do a manual login.
The following is an overview of the Primo VE user interface for a reference when configuring it.
|Select the Library tile to open the Primo VE integration profile (recommended tile size 2*1):||After selecting the Library tile, the following Home page appears to the user:||Perform a search and the results are displayed:|
|Select the Overview tab to see a list of your items:||Select the Saved Records page to see your saved records:|
The following section describes technical information for the Primo VE product integration.
Alma November 2019 release.
The following are the prerequisites for the Primo VE product integration:
- IDP should return the AlmaID attribute. The Alma ID attribute is a unique ID controlled by the customer that is defined per student/staff member in Alma.
If using CMAuth - this attribute can have any name in the IDP attributes response (from SAML/OAUth/LDAP), but need to be mapping in Additional Mapping in the CMAuth Integration Profile.
Otherwise - AlamaID attribute must be returned in LDAP attributes response.
Due to this new mapping in authentication token, users will need to logout & login to the app.
- Handshake between Alma and campusM: in order to allow secured access to Primo VE, an authorization token needs to be configured in Alma (Configuration> Discovery> customer settings > app_authorization_token) and the same code needs to be configured in campusM (App Manager> Product Integrations> Add Product Integration> Primo VE> Authorization Code).
- Native app (Android/iOS) need to be in January release at least.
Technical Flow Diagram
The following is the technical flow diagram for the Primo VE product integration:
Primo VE Technical Flow Diagram
When the home page is active, the live tile is refreshed automatically every five minutes. If the home screen is inactive, it is not updated in the background. When the home screen becomes active again, the timer starts again if the update period has elapsed.
To configure the Primo VE product integration, select Add Product Integration from the Product Integrations main menu option.
Select Primo VE and the following configuration page appears:
Primo VE Configuration
The following table describes the configuration options available on this page.
|Configuration Option||Description||Mandatory||Data Type||Default||Example|
|Enable Product Integration||Select to enable the product integration on the user's campusM app.||No||Check box||Yes|
|Product Integration Description||A description of the product integration for internal use||Yes||Description||-|
|Screen Title||The title that appears in the top header of the service||No||String||Primo VE|
|Page Title||The secondary title, after Screen Title.||No||Description||-||Our Library|
|Base URL||The base URL of your Primo VE instance||Yes||URL||-||https://alma-eu02-.campusm.exlibrisgroup.com|
|View ID||The View ID of your Primo VE||Yes||String||-||NORTH_INST|
|Authorization Token||Must be the same authorization token as in Alma, in the following format:
For more information, see Prerequisites.
|Language Code||The language to display Primo VE integration. Not applied to the live tile.||No||String||en
|General Error Message||General error message if the page fails to load.||No||String||Please try again later||Failed to load. Please try again later|
|Landing Page||The page displayed by default on the Primo VE PI homepage|
|Look and Feel|
|Primary Theme Color||Select a color for the main elements on the page||Yes||Color Code||#444444|
|Secondary Theme Color||Select a color for the secondary elements on the page||Yes||Color Code||#6f8ea4|
|Enabled||Select to make the Primo VE tile live||No||Check box||Yes|
|Live Tile Look and Feel|
|Badge Color||Select a color for the badge||Yes||Color Code||#cd5c5c|
|Live Tile: Displayed Items
|Enabled||Whether the specific item is part of the live tile.||No||Check box||Yes|
|Label||The label for this live tile item.||No||String||<Exist for each item>|
|Item Due Back Soon – Days Before Due Date||The maximum number of days before the due date to be considered an Item Due Back Soon||No||Number||3|