Datastore Delivery Results
This topic lists API and Data Explorer fields (and their descriptions) associated with a delivery ID and it’s results. The entities described in this topic are considered to be the most meaningful when performing a query of a delivery’s data - not all entities returned with a query are listed.
API: “Data” will be listed out for each test taker’s attempt at the delivery’s test. If the same delivery is assigned to more than one session (for the same test taker), the test taker’s attempts will be recorded as a separate data set with different a deliveryExecutionId (see below) per attempt.
CSV notes that this field is present when exporting session results in a CSV file. For more information, see Exporting and interpreting CSV session results .
Session level data
isDeleted
The value of this API field is always set to false,
as only the most recent delivery results currently display.
If the same delivery has been taken multiple times by the test taker, previous results are marked as isDeleted=true
.
This field is only valid if you are launching the delivery via LTI with multiple attempts parameter. For more information, see Custom parameters (delivery launch).
Identification
Data Explorer | API | Description |
---|---|---|
Test Qti Id |
| The Identifier for the test, which can be viewed and changed from the general properties panel in test authoring. |
Test Qti Label |
| The label provided for a test in the Test properties form. |
Full Test Resource Id |
| The Resource Identifier located in the delivery’s Properties panel. |
Login |
| CSVThe test taker’s ID/username (not name). |
Test Qti Title |
| The Title of the test, which can be viewed and changed from the general properties panel in test authoring. |
Delivery Id |
| The delivery ID of the test. |
Delivery Execution Id |
| Unique identifier for the delivery execution (the session for a given test taker/delivery combination). |
Metadata
Data Explorer | API | Description |
---|---|---|
Metadata Metadata. Label |
CODE
| Any metadata properties defined for the test will be listed with the property's name and the value assigned to the test. This field contains the same information of metadataRaw but with flat structure.
|
| This field lists the raw, unprocessed set of metadata associated with the delivery’s items. These fields are used to provide additional context to the results of the query. |
Timestamps
Data Explorer | API | Description |
---|---|---|
Publication Time |
| The exact time the delivery was published (provided as a unix timestamp). |
Session Start Time |
| CSVThe exact time the test was started by the test taker (provided as a unix timestamp). |
Session End Time |
| CSVThe time that the test was submitted (provided as a unix timestamp). This will typically be the same value as |
Duration |
| How long it took the test taker to complete the test (in seconds). The value of this field should equal the |
Submission Time |
| The exact time the test taker submitted the test (provided as a unix timestamp). This will typically be the same time as |
Last_update_date |
| The date the session was last updated (provided as a unix timestamp). For tests with manual scoring, this value will display the time at which scoring was completed. Until all manual scoring is performed (if any), the value of this field should be the same as the |
Scoring
Cut Score Ratio |
| If a cut score is configured for the test, the percentage of the cut score (a cut-off point for passing the test) achieved by the test taker’s score will display. This percentage is displayed as a decimal value. If no cut score is defined for the test, the value of this field will be |
| CSVAny scoring outcome defined on the test level (in Test authoring) will be listed here. For more information, see Configuring scoring for tests.
| |
Score |
| CSVThe amount of points achieved by the test taker, if defined by the test scoring. The value of this field should match the value of |
Max Score |
| CSVThe maximum possible score for a delivery (test). The value of this field should match the value of |
Item level data
These fields record each item in the test individually with details about the item, and how the test taker responded to it in the test.
Data Explorer | API | Description |
---|---|---|
Item Id | Listed first after
CODE
| Each item’s reference ID, which can be found in the item’s general properties in Test authoring. |
Num Attempts |
| How many times the item was seen (or attempted) by the test taker. Only the last attempt’s results are displayed and taken into account for the item’s scoring. |
|
| The metadata defined for an individual item
|
Full Item Resource Id |
| The item’s Identifier, which can be found in the Item Properties (in Item authoring). |
Status Correct |
| CSV Whether the item’s score was correct, false, partially correct, or skipped. |
Qti Title |
| CSV The title of the item in the Item Properties (in Item authoring). |
Max Score |
| The maximum score available for the item. |
Submission Time |
| The exact time the answer to the item’s question was submitted. This time is provided as a unix timestamp. |
Qti Id |
| The Identifier, which can be viewed and modified in the Item’s Properties (in item authoring). |
Qti Label |
| CSV The label of the item in the Item properties (in the Edit Item form). |
Duration |
| CSV The duration value reflects the time (in seconds) a test taker spent on a given item. The duration value excludes the time the item took to load and become available, as well as any time a test taker had their session paused. |
Score |
| The score achieved by the test taker for the particular item. |
Item End Time |
| The exact time the item was completed/submitted by the test taker (for linear tests) or last interacted with (for non-linear tests). This time is provided as a unix timestamp. |
Item Start Time |
| The exact time the test taker opened the item in the test for the first time. This value is provided as a unix timestamp. |
Completion Status |
CODE
| CSV In API results, all outcomes defined on the item will be listed here (especially the ones defined for manual scoring). Completion Status: The completion status of the item. The possible values are
In API results, SCORE AND MAXSCORE will display repeated values. |
|
| CSV
|
Manually Graded |
| Displays if a manually scored item has been scored or not. This value will display as |
Manually Graded At |
| The time an item was manually graded (if applicable). This value is provided as a unix timestamp. It will display as |
| When set to true, this field indicates the item has an upload in one of the responses. |
Reference: Serialization for item responses
This table summarizes how QTI baseTypes are serialized depending on their cardinality at export time.
BaseType | Cardinality | Serialized Example |
---|---|---|
identifier | single |
|
identifier | multiple |
|
identifier | ordered |
|
boolean | single |
|
boolean | multiple |
|
boolean | ordered |
|
integer | single |
|
integer | multiple |
|
integer | ordered |
|
float | single |
|
float | multiple |
|
float | ordered |
|
string | single |
|
string | multiple |
|
string | ordered |
|
point | single |
|
point | multiple |
|
point | ordered |
|
pair | single |
|
pair | multiple |
|
pair | ordered |
|
uri | single |
|
uri | multiple |
|
uri | ordered |
|
directedPair | single |
|
directedPair | multiple |
|
directedPair | ordered |
|
duration | single |
|
duration | multiple |
|
duration | ordered |
|
record | N/A |
|