Sharebar?

OneRoster 1.1 Real World Scenarios

OneRoster 1.1 Real-world Scenarios

These scenarios provide examples of the implementation of OneRoster to solve issues schools and districts experience.

Scores

Through the concept of ‘lineItem’, OneRoster 1.1 presents the ability to transmit formative score level data between systems. 

Scores Scenario 1

A school system has implemented a Learning Management System (LMS) and a Student Information System (SIS). Using OneRoster 1.1, assignments (assignment title, assignment description, assignment date, due date, assignment category) may be transmitted from the LMS to the SIS.  The information from the LMS will be sufficient for the SIS to be able to create and store the outcome (grade) for each student.

Scores Scenario 2

A school system has implemented a Learning Management System (LMS), a Student Information System (SIS) and a Formative Assessment System (FAS).  Using OneRoster 1.1, both the LMS and the FAS transmit assignments with scores to the SIS. Thus the SIS combines all assignments in one place for ease of use, eliminating the need for  teachers to create activities in the LMS and FAS and then re-create these as assignments in the SIS gradebook for the purpose of reporting grades.
 

Resources

Through the concept of ‘resources’, OneRoster 1.1 presents the ability to associate and transmit digital learning objects associated with a Class or a Course.

Resources Scenario 1

A school system has implemented a Learning Management System (LMS) and a Digital Content Provider (DCP). Using OneRoster 1.1, the DCP will be able to send a collection of resources for a specific course.  For example, the 7th grade Language Arts course within the LMS will receive learning objects from the DCP.

Resources Scenario 2

A school system has implemented a Learning Management System (LMS) and has adopted digital textbooks from a publisher.  Using OneRoster 1.1, the publisher is able to provide the specific textbook resources for each course (grade level/subject area) based on rostering information.

Enrollment

Through the concept of ‘enrollment’, OneRoster 1.1 offers the ability to show whether an individual will be taking part in a course or class. In the vast majority of cases, users will be students learning in a class, or teachers teaching the class. Other roles include administrator, aide, guardian, parent, proctor [new in 1.1] and relative

Enrollment Scenario 1

A school system has implemented a Learning Management System (LMS) and Student Information System (SIS).  Using OneRoster 1.1, the SIS transmits the beginning and ending date for enrollment in courses and classes to the LMS. Thus, allowing the LMS to create courses and sections (classes) with correct dates attached.

Enrollment Scenario 2

A school system has implemented a Learning Management System (LMS) and Student Information System (SIS).  Using OneRoster 1.1, the SIS transmits information about the role each user holds to the LMS so that school administrators are available see all courses within their school, while those with the role of exam proctor can only see the course for which they will proctor the final exam.

Digital Ecosystem

Aggregator Scenario

A school system has implemented a Learning Management System, Student Information System, Digital Content Provider, Library Management System, Notifications System, Food Service System and several other applications that each implement OneRoster 1.0 or 1.1.  Some of these applications support CSV while others support only REST. Enrollment is Provided by the SIS and Consumed by the other applications while some of the Consumers of Enrollment wish to Provide Resources and/or Scores back to the SIS or to each other. By implementing an Aggregator service (application gateway) these integrations may be centrally managed and supported without each application being directly connected or aware of the others resulting in a simplified enterprise integration architecture.