About Ex Libris Leganto

Leganto, the Ex Libris resource list management system, makes it easy to create, access, and manage course resource lists. Instructors can build, maintain, and share resource lists that include all material types, librarians can provide resources more efficiently and scale up to support more courses, and students can access all course materials in one place and from any device.  

Leganto tightly integrates with Ex Libris Alma® as well as learning management systems, library discovery services, mobile apps, citation tools, and other campus systems.

User Activities

Users can use any Leganto functionality from the app. For example, students can view their reading lists, view which resources are used for the course, access online resources, find the location of physical resources, etc.

Authentication

The following is the authentication flow:

1. The user logs in to the app.
2. The app calls IDP to get the AlmaID attribute (the user identifier in Alma).
3. IDP returns the AlmaID.
4. The app sends the AlmaID and Authorization Token to Leganto. (The token is configured on both sides – Alma and campusM, see Prerequisites).
5. Leganto verifies the token and the AlmaID using the Alma login flow. 
6. Leganto sends the app the authentication confirmation.

Offline Support

Not supported.

Screenshots

The following is an overview of the Leganto product integration user interface for a reference when configuring it.

Lists Tab	Find Lists Tab	Collections Tab
Citation	Specific Reading List

Example of 2 x 2 dimensions

Live Tile Configuration Rules

The Leganto live tile is designed to work with the following sizes. The tile will attempt to display as many elements as possible regardless of the dimensions set, but we cannot guarantee the intended experience if you do not adhere to the following dimensions. The tile dimensions are set in the App Builder, while the widgets per row (and other details) are set in the Configuration page for this product integration.

• 1 wide x 1 high
  • This is a special case. The tile only displays one widget (the highest prioritized, enabled widget).
• 2 wide x 1 high
  • We recommend using 1 - 2 widget rows and using 1 - 3 widgets per row.
• 2 wide x 2 high
  • We recommend using 2 - 3 widget rows and using 1 - 3 widgets per row.
• 3 wide x 1 high
  • We recommend using 1 - 2 widget rows and using 2 - 4 widgets per row.
• 3 wide x 2 high
  • We recommend using 2 - 3 widget rows and using 2 - 4 widgets per row.

We also recommend keeping the header text and widget labels for the live tile short.

Prerequisites

The following are the prerequisites for the Leganto product integration:

• IDP must 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. For CMAuth, this attribute can have any name in the IDP attribute response (from SAML/OAUth/LDAP) but needs to be mapped in Additional Mapping in the CMAuth Integration Profile. Otherwise, the AlmaID attribute must be returned in the LDAP attribute response. Due to this new mapping in the authentication token, users need to log out and log in again to the app. This is the same AlmaID configured for the Primo VE product integration.
• Handshake between Alma and campusM: to enable secure access to Primo VE, an authorization token must be configured in Alma (Configuration > Discovery > Customer Settings > app_authorization_token). The same code must be configured in the app (App Manager > Product Integrations > Add Product Integration > Primo VE > Authorization Code). This is the same authorization token configured in Alma for Primo VE product integration.

Technical Flow Diagram 

The following is the technical flow diagram for the Leganto product integration:

The user logs in to the app and the Leganto tile is available.

The user selects the Leganto tile.