This article is intended for use by members of the Digital Learning Partner Program and is not designed for general Campus users.
Assignments created and scored in a third-party vendor can be passed back to Campus through the OneRoster API.
The timing of sending line items to Campus is up to the vendor; for example, some vendors allow teachers to trigger the sync, while others sync nightly.
To pass back scores to Campus, create line items using the PUT endpoint for each assignment. Then create a result objects.
Line Items
Vendors are responsible for creating line items and passing them back to Campus through the API. A line item is an assignment record being sent to Campus. Each line item must have a globally unique sourcedId.
V1P1: Line items are not required to have Categories or Grading Periods. OneRoster's definition of a category is not section-specific and therefore does not meet Campus' needs. OneRoster Assignment Line Items will have a category value of '11111111-1111-1111-111111111111'. If null, the Grading Period is auto-calculated based on the Term in which the Due Date falls.
V1P2: Line items are required to have a category and cannot be '11111111-1111-1111-1111-111111111111'. Grading periods are still optional. Score Scales are not required.
Results
A result record includes scores info to pass back to Campus, including date, score, score status, the sourcedId of the line item/assignment, and the sourcedId of the student who received the score.
V1P1 Score Flags
Teachers can flag assignments in Campus to provide additional information about student scores. Some of these flags affect grade calculation. The following table describes the Campus flags that are mapped to scoreStatus values in the OneRoster specification. ScoreStatus options not listed here are not mapped to Campus flags. Vendors should map their product's status options based on the scoreStatus descriptions in the IMS Global Specification.
| Specification scoreStatus | Campus Flag | Campus Description |
|---|---|---|
| Exempt | Dropped | Scores can be entered for these assignments, but they do not contribute to grade calculations. |
| Not Submitted | Missing | The missing flag affects grade calculations based on district setup. The flag may be an indicator only, or may calculate as a specified percentage of possible points. |
V1P2 Score Flags
As of the release of Campus.2339:
| Result Property | Campus Flag Applied | Campus Description |
|---|---|---|
"scoreStatus": "exempt" | Exempt | Scores marked exempt do not contribute to in-progress grades. |
"late": true | Late | Indicates a late assignment; this flag has no effect on the score. |
"incomplete": true | Incomplete | Indicates an incomplete assignment; this flag has no effect on the score. |
"missing": true | Missing | The missing flag affects grade calculations based on district setup. The flag may be an indicator only, or may calculate as a specified percentage of possible points. |
Prior to the release of Campus.2339. Note: this behavior can still be used after the case is taken by omitting the properties late, missing, incomplete, and inProgress on the Result.
| Result Property | Campus Flag Applied | Campus Description |
|---|---|---|
"scoreStatus": "exempt" | Exempt | Scores marked exempt do not contribute to in-progress grades. |
"scoreStatus": "late" | Late | Indicates a late assignment; this flag has no effect on the score. |
"scoreStatus": "exempt" | Incomplete | Indicates an incomplete assignment; this flag has no effect on the score. |
"scoreStatus": "withdrawal" | Dropped | Scores can be entered for these assignments, but they do not contribute to grade calculations. |
"scoreStatus": "missing" | Missing | The missing flag affects grade calculations based on district setup. The flag may be an indicator only, or may calculate as a specified percentage of possible points. |
