Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Overview

    Ex Libris' campusM is a powerful multi-service integration platform to create an app (Android and/or iOS) that provides staff and students personalized access to university/HE services and information.
    The app you create using campusM is available as an app store download for iOS (Apple) and Android (Google) mobile products. You can also make the app accessible by Web browser for PC or mobile use. The app can be used as your university's student portal, replacing existing, less flexible, and less manageable in-house Web-only systems.
    You build and configure the campusM app and its services using the Web-based App Manager. Your institution can create multiple apps and/or multiple end-user profiles for the apps, targeting the different needs of certain groups of end-users, for example, one for staff and one for students.
    campusM is part of the Mobile Campus Solutions Business Unit of Ex Libris. The App Manager and other campusM software are provided using Ex Libris' Software as a Service (SaaS) model.

    About This Guide

    The purpose of this guide is to explain the following:
    • How to use the App Manager to build, configure, and publish your app
    • How to access and manage the App Manager
    This guide does not include:
    • Initial installation and configuration of the campusM software. This is performed in coordination with Ex Libris. Any changes to the software must be made in consultation with Ex Libris. Example include changing the name and other text elements of the software, installing language packs for your apps, and creating an interface between the App Manager and your existing backend servers. See also Changing App Manager Installation Settings.
    • How to use Web services. For help using Web services, open a support ticket. Contact Ex Libris customer support for more information.
    • Anything covered in other documentation guides, such as branding guidelines, how to use the Application Extension Kit to create integration services, and the campusM Scheme.

    Services and Other App Elements

    Services are the heart of your app. The app provides access to a range of standard university/HE services, for example: Learning Management System (LMS) resources, classroom and library availability hours, class attendance, inter-university email, an events calendar, and student records, including course enrollment and grades. Other services can be incorporated into the app. Services are accessed in the app through tiles.
    campusM App Screenshot
    campusM Web App Screenshot (With Services as Tiles)
    The following types of services are available:
    • Basic – A non-functional tile, or one that links to another service or URL.

      A basic service is just a tile with text, or a tile that the end-user selects to open a link.

    • Static Content – A service that presents a page of information, or a menu of information pages. Each option in the menu is a) a sub-menu, b) a link to another service or URL, or c) a static page of information. These are also known as pocket guides.

      A static content service tile is text, a picture, or both. The end-user selects the tile and sees the page with HTML, pictures, text, and so forth. Alternately, the end-user sees a menu with options to view pages (with HTML and so forth), open other services, or open a sub-menu.

    • Feed – A service that provides dynamic syndicated content from one or more RSS feeds.

      Unlike a basic or static content service, a feed tile presents dynamic information on the tile itself. The end-user can view the dynamic information without selecting the tile. The end-user can select a link on the tile to open other contents (such as in a web browser).

    • Banner – A service that presents an image marquee. The images can link to another service or URL.

      Like a feed service, a banner tile presets dynamic contents even before the end-user selects the tile. When configured, the end-user can select one of the rotating images to open some other service or contents.

    • Integration – A service that provides other dynamic content, built using the Application Extension Kit (AEK).

      Integration services can present almost anything, since they are min-programs that operate within the application. Typical services could be available parking spaces, weather, class status, and so forth.

    The app also has the following elements:
    • A hierarchy of profiles and roles to hide/display services, in whole or in part, to specific users or types of users (see Customizing Access to Services, below).
    • Configurable layouts based on the OS environment and device rotation.
    • A name, icon, and description.
    • An authentication method that provides user authentication for the app.
    • Information screens, such as a splash screen, an About screen, and a Terms of Use screen.
    • A configuration menu that enables the user to switch profiles, edit personal details, search for a service, share the app or a service on social networking, or submit feedback to your institution.
    • Emails and notifications that are sent to the end-user, as required.
    Some services are created for your institution by Ex Libris during the installation process. For a list of these services, see Integration Directory. These services cannot be deleted in the App Manager.

    Users

    In this documentation, the following types of users are referred to:
    • End-users refers to the people who use the app, including students, visiting parents, instructors, and staff.
    • Users refers to the users of the App Manager, and does not include end-users.
    • Administrators refers to the users of the App Manager who manage other App Manager users (have add/change/delete user permissions). Administrators also work together with Ex Libris to create the initial campusM installation and link the App Manager to existing institution backend servers, such as LDAP.
    Administrators can assign or remove user permissions to/from users, which restrict these users' ability to manage certain areas within the App Manager. Permission types are defined during installation and cannot be changed. For added convenience, these permissions can be grouped into user groups, which can then be assigned to users.
    In addition, users can be restricted as to which profiles, roles, and services they can manage.

    Customizing End-User Access to Services

    campusM provides multiple levels of restrictions to services for the end-users, by means of multiple apps, authentication, profiles, and roles.
    • Multiple apps are typically not necessary, but are sometimes used for branding or marketing purposes. You can create one app for students and one app for alumni, for example, or one app for registration day and another for year-round usage. The services provided by each app can be tailored to the end-users of that app.
    • Several options are provided for end-user authentication to the app itself, including requiring registration, creating lists of authorized end-users, and authentication by LDAP or another backend server. Authentication types are assigned to a profile group. When registration is required, end-users register for the app on their first use.
    • Profiles (also known as app profiles) provide a means of grouping end-users into types, such as first year or graduate students, staff, and so forth. You can tailor the app interface and enable services for specific profiles. An end-user associated with multiple profiles in a profile group can switch between them in the app, seeing different services based on the selected profile. Profiles are grouped into profile groups. When the end-user accesses the app, he or she selects the relevant profile group. After logging in, the end-user has access to only the profiles in that profile group (that are authorized for that end-user).
      You can configure entirely different branding for each profile, so that the app looks and feels different to end-users logged in to that profile.
    • App roles are assigned to end-users. A service, or in some cases part of a service, can be configured for certain app roles, in which case the service only appears to end-users who have at least one of these app roles.
      While an end-user can switch between profiles in the app, end-users cannot switch their app roles. For example, the end-user can view the app as a graduate student and also as a faculty member, but the app roles assigned to the end-user apply in each profile.
      For example: If a service is associated with the app role First Year Students, an end-user associated with the app roles First Year Student and Physics Student sees the service in the app, while an end-user associated only with the app roles Graduate Student and Physics Student does not.
      App roles are initially assigned to end-user by means of a backend service that Ex Libris builds together with your institution. The service uses a mapping feature called customer roles, which maps codes returned from your backend service during end-user registration to the app roles assigned to the end-user. These codes are returned by a custom-designed API call from the App Manager to your backend service. In the App Manager, you can also add or remove app roles from specific end-users.

    End-User Communication

    Communication to End-Users

    App Manager users can communicate with end-users by sending notifications. See Sending Notifications to End-Users.The end-user sees the notifications in the app and can view and/or delete them. End-users can select notifications to receive by adding themselves to specific types of notifications in the app. This adds them to the corresponding Alert Group. see Configuring Alert Groups and Managing Profiles.

    Communication From End-Users

    The end-user can use menu options in the app to communicate with campusM administrators. The options are:
    • Problems - Problems with the app. You configure a list of problem categories for the end-user to select along with his or her feedback.
    • Ideas – Ideas for the app.
    • Feedback – Any other feedback.
    The end-user can submit feedback about the current page or the app in general. After submitting feedback, the end-user is prompted to submit a rating for the app. After the end-user submits feedback, the feedback is available to view in the App Manager (see Viewing Feedback) and an email is sent to the default email address for the profile. To configure this email, see Configuring App Emails. To configure app feedback, see Configuring App Feedback.
    Communication between end-users:
    You can add integration services that include campus email, chat rooms, and forums for end-users to communicate with each other. See Working with the Application Extension Kit.
    In addition, end-users can share a link to the app, or to a page of the app, by email, Twitter, and Facebook. To configure this feature, see Configuring App Social Network Sharing.

    Getting Help

    To get to these help pages, select Support Resources.

    To open a SalesForce case, select Raise a Ticket.

     

    • Was this article helpful?