The Skyward Qmlativ uses OneRoster for grade passback.
Entity Mapping
This document explains how Qmlativ entities are mapped to Edlink entities.
| Qmlativ Entity | Edlink Entity |
|---|---|
| Course | Course |
| Department | Department |
| Enrollment | Enrollment |
| GradingPeriod | Session |
| Guardian | Person, Agent |
| Section | Section |
| Staff | Person |
| Student | Person |
| Subject | Subject |
| OneRoster Entity | Edlink Entity |
|---|---|
| Category | Category |
| LineItem | Assignment |
| Result | Submission |
Notes
student_gpa_method_nameis a configurable property which controls how GPAs are calculated. By default we use the'Weighted'method.- A class may be linked to more than one session when Skyward schedules it across multiple grading periods (for example, a year-long section).
- Not all Qmlativ instances have support for the same requested fields. For example, Qmlativ instances for Texas districts have different demographic tables/fields that those in Illinois or Indiana. Furthermore, administrators can configure their Qmlativ instances to prohibit reading of specific databases, tables, and/or fields. So, if you encounter missing fields on an object, first verify that it exists in the Qmlativ instance, and that it is shared.
Custom Field Mapping
The following fields can be custom-mapped in our dashboard UI:
- agent relationships