Skip to main content
ExLibris

 

  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Preparing for Leganto Implementation

    This document explains Leganto's implementation requirements, including the following:

    Customer Project Team - Roles and Responsibilities

    Responsibilities

    • Form an implementation team with the following roles:
      • Project manager
      • Library representative
      • CMS administrator
      • Course instructors/faculty representatives
    • Manage the internal institution’s implementation team.
    • Implement Leganto within the agreed upon timeframe.
    • Prepare a sample of course data, reading lists and instructor data for a pilot.
    • Configure the Leganto CMS integration (LTI) on the CMS side.
    • Perform ongoing tests during the Leganto UI implementation, Alma course management, and Leganto LTI integration phases.
    • Decide on a rollout plan for loading and maintaining courses in Alma.

    Roles

    • The project manager has the following roles:
      • Lead and coordinate Leganto implementation activities that are assigned to the institution.
      • Coordinate between internal teams (Library, CMS/LTI administration, and faculties) to guarantee successful implementation.
      • Manage internal and external communications related to the project status and priorities.
      • Assist in mitigating project risks.
      • Keep the project moving and on track.
      • Acts as primary point of contact with the Ex Libris project manager including the following specific activities:
        • Provide data extracts based on Ex Libris requirements.
        • Ensure the availability of CMS staff.
        • Prepare training activities for the library staff and instructors.
        • Attend project meetings.
        • Review project plans.
        • Manage and oversee testing processes and provide feedback.
        • Set and communicate relevant priorities with the Ex Libris project manager.
    • The library representative has the following roles:
      • Provide configuration requirements for Leganto.
      • Provide information about courses and reading list workflows used by the library.
    • The CMS administrator has the following roles:
      • Supervise the Leganto CMS integration from the CMS side.
      • Provide information related to CMS configuration.
      • Determine preferences related to Leganto CMS usability, such as links, authentication, etc…).
    • The course instructors/faculty representatives have the following roles:
      • Provide end-user feedback and experience.
      • Provide configuration requirements for Leganto.

    CMS/LTI and Technical Requirements

    LTI Integration

    During the implementation project the institution team will set up the Learning Tools Interoperability (LTI) integration between Leganto and the institution’s Learning/Course Management System (such as CMS or VLE).

    Leganto currently supports integration with the following systems:

    • Moodle
    • Canvas
    • Blackboard
    • Desire2Learn (Brightspace)
    • Sakai
    • Other - allows you to add further information related to your current CMS. Please contact your EXL team and inform them before selecting this option.

    For more information about setting up the Alma LTI integration, see Configuring Learning Tools Interoperability (LTI).

    For more information about setting up the CMS side, see the Developer Network - LTI.

    Integrating LTI enables you to determines how to link your patrons to Leganto from their CMS and how to authenticate them in Leganto. You can also select CMS roles to set as instructors in Leganto.

    Courses

    While implementing Leganto you will need to define courses in Alma before they can be used in Leganto. When enabled, instructors can create missing courses when they access Leganto from a CMS.

    You can use one of the following three methodologies for loading or creating your course information:

    • Course Loader integration profile - Import course information from your CMS. Alma supports importing course information using the Course Loader integration profile that runs according to the schedule you configure.
      The following requirements apply to the course information:
      • Saved in a tab-separated value file format (not comma-separated).
      • Located in a dedicated directory on an FTP server accessible by Alma.
      • Saved either as a .txt or .csv file.
        For more information about the Course Loader integration profile and format of the course information file, see Configuring Course Loading.
    • For Alma Course API, the course API gives you access to courses and reading list related information. For more information about course APIs, see the Developer Network - Courses.
    • For manually adding courses to Alma, the library staff can create them in Alma or enable the instructors to create them in Leganto when accessing Leganto from the CMS.
    • For more information about adding a course, see Adding a Course.

    Roles in Alma

    Before implementing Leganto, you need to make sure that users in Alma have the following correct roles:

    • Users with the Instructor or Leganto Course Operator role have access to all (non-librarian only) Leganto features.

      For instructors to view reading lists associated with a course, or to associate a reading list with a course, users must be associated with the course, or a reading list collaborator or owner.

    • Users with the Patron (and no higher role, such as Instructor or Course Reserves Operator) role can access Leganto as a student. When accessing Leganto from a CMS, users are associated with the reading lists associated with the course in the CMS.
    • Users that are not logged in have guest access.
    • Users with the Course Reserves Operator/Manager or Fulfillment Services Operator/Manager (or General System Administrator) role have access to Leganto as a librarian, which enables additional features, such as creating reading list templates and setting statuses directly in Leganto.

    Training Requirements

    Implementing Leganto requires the institution's project team to be familiar with the following Leganto training content:

    Ex Libris also recommends reading the Leganto Product Overview before beginning the Leganto Implementation project.

    General Implementation Project Overview

    The Project Preparation (Onboarding) phase begins prior to implementation. This phase includes technical readiness of the institution and defines specific setup requirements, identifying project stakeholders and potential team members. It also works with the Ex Libris Engagement Team to identify key teaching and learning stakeholders and starts working closely with them.

    The Leganto implementation project is divided into the following three stages, which start at the Kickoff meeting.

    1. During the first stage, the Ex Libris project manager contacts the institution’s implementation team to set up the project plan, agree on milestones, and define any institutional requirements.
    2. During the second stage, Leganto is activated and the system is configured according to the customer’s requirements. In parallel, integration between Leganto and the CMS is established.
    3. During the third stage, which begins when Leganto is intially launched within the institution, Ex Libris will provide support for the institution’s implementation team until transitioning to the support team.

    For more information about the structure of Leganto Implementation project, see the following article <Link to Ex Libris Leganto Implementation Methodology>.

    • Was this article helpful?