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

    Implementation Prerequisites

    General

    • Personalized timetable/class schedule data must be available for students.
    • Timetable must include the class schedule and information (class title, start and end times. Location is mandatory if geolocation validation is to be used)
    • Each event (class) should have a unique EVENT ID. This should be per event, as opposed to per course / series of classes, for example. The EVENT ID has to match the same event on the staff timetable.

    When using predefined Geolocation validation:

    • Geolocation (latitude and longitude) data must be available for all positions with a location reference used within student and lecturers’ timetables.
    • Location references must be provided for each position assigned to events.

    For Lecturer Check-In

    • Personalized timetable/class schedule data must be available for lecturer for lecturer check-in.
    • The timetable service must be provided as a different endpoint for lecturers and students. The student timetable API should not return any data for a lecturer, and the lecturer timetable API should not return any data for a student.
    • As per the student timetable, each event (class) should have a unique EVENT ID. This Event ID should be the same as that returned for the same event instance for the student as for the lecturer. (The EVENT ID is tied to the event instance for both the student and the lecturer.)
    • Attendees' in-class data must be available for each event for lecturer check-in.

    Services Requirements

    • Student personalized timetable: A student information system must be configured with all class schedule information and integrated with campusM. The information includes each student's class schedule. Each class should have a unique EVENT ID.

      See campusM Timetable for details and prerequisites.

    • Staff personalized timetable: If the lecturer wants to check in students on their behalf, the lecturer's class schedule and the list of students who are scheduled to attend each class must also be available to the lecturer. Each class should have a unique EVENT ID.

      See campusM Timetable for details and prerequisites.

    • To include the lecturer check-in functionality that allows the lecturer to check-in a student , the Retrieve Attendees service should be deployed.

      See Retrieve Attendees for Events for details and prerequisites.

    • The student timetable API should not return any data for a lecturer, and the lecturer timetable API should not return any data for a student.
    • If using geolocation, each class location must be configured as a location with the correct location, and these locations must be linked to the classes in the schedule.
    • Was this article helpful?