For Developers
Implementation Details
Important Note
Providers implement OneRoster in their own unique ways. It is not possible to guarantee that all providers will support the same functionality. The following is a list of common OneRoster functionalities that providers may support:
OneRoster 1.1 vs OneRoster 1.2
Whenever possible, we recommend using OneRoster 1.2 as it is the latest version of the standard and handles user roles more effectively.
Provider Specific Limitations
Please refer to the specific provider docs for more information on the limitations of each provider.
- Aspen does not support creating or updating categories.
- Aspen, Blackbaud, and Skyward do not support listing categories by class.
- Blackbaud does not support deleting categories.
Entity Mapping
OneRoster Entity | Edlink Entity |
---|---|
Org | District, School |
Academic Session | Session |
Course | Department, Subject, Course |
Class | Class |
Enrollment | Enrollment |
User | Person |
User (Relationships) | Agent |
Category | Category |
LineItem | Assignment |
Result | Submission |