Return to Navigation

Understanding the LMS Interoperability Batch Extract

The goal of an LMS is to use a common set of interoperability standards that enable the sharing of instructional content and data between learning and administrative environments. Based on instructional management systems (IMS) enterprise system specifications, currently PeopleSoft LMS interoperability batch extract supports one-way file transfer between PeopleSoft Campus Solutions and an external learning management system.

PeopleSoft LMS extract enables institutions to provide a third-party LMS (such as Blackboard CourseInfo) with personal profile data for learners and instructors, enrollment data and maintenance, and limited course scheduling data and maintenance. The LMS batch extract also provides basic integration with PeopleSoft Student Portal. Depending on your extract target, you can format LMS data with a unique file type of XML V1.1, Blackboard CourseInfo 4, or API Input (a WebCT format currently being phased out). WebCT Campus Edition Institutional (version 4.1) and WebCT Vista 2.1 both support XML V1.1

Currently, the feature does not support passing data or information back to PeopleSoft Campus Solutions from another LMS environment; nor does it include a real-time transactional messaging interface based on event processing.

PeopleSoft LMS batch extract supports IMS Enterprise Specification V1.1 XML data binding specifications. It also supports a simple, common, delimited option for API Input format.

File selection criteria are available at runtime for you to specify which type of files to pass. In addition, you can use packaging options to indicate how you want the system to organize the extract files.

The PeopleSoft LMS interoperability extract includes the following extract functions:

High-level definitions for each of these data are provided in the following sections.

Properties Object Data

The properties object data serves as a file header and contains descriptive data about the contents of the file.

Person Object Data

Person object data includes:

  • The person source ID wherein 1) the source is the academic institution with which the student or instructor is associated, and 2) the ID is either the individual's employee ID or user ID, depending on which is specified on the Academic Institution 3 page.

  • The user ID, which is either the employee ID or user ID, depending on which is specified on the Academic Institution 3 page, of the student or instructor.

  • Personal data for all students enrolled or previously enrolled in the selected LMS classes and the instructors teaching the classes.

Group Object Data - Term Information

Group object data - term information includes:

  • The source ID wherein 1) the source is the description of the academic institution in which the classes are scheduled, and 2) the ID is the term code.

  • The term description information and the term start and end dates.

Group Object Data - Course Information

Group object data - course information includes the source ID, wherein 1) the source is the description of the academic institution in which the class is scheduled, and 2) the ID is a unique identifier for the group. The group identifies the LMS class, which, by default, is TERM-INSTITUTION-SUBJECT-CATALOG NBR-SEC#-CLASS NBR

The ID includes the term code and class number added to the autogenerated LMS extract group ID from the LMS Data page in the schedule of classes.

Group Membership Object Data - Group

Group membership object data - group includes the source ID, which is the same as the source ID for group object data - course information.

Group Membership Object Data - Member

Group membership object data - member includes:

  • The source ID, which is the same as the person source ID for person object data.

  • The ID type for person or group.

  • The role and, for instructors, the subrole, if any.

  • The user ID (same as the person user ID for person object data).

  • The class start and end dates.

  • The enrollment status reason.

  • For students only, a mode (grading basis) and result final grade.

  • The student's preferred email address, or campus or home email address.

  • The datasource, which is set on the run control page.