datastoreDeliveryResults

This topic lists API 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.

“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 https://oat-sa.atlassian.net/wiki/x/GgAnrQ.

Session level data

isDeleted

This value is always set to false, as only the most recent delivery results currently display.

Identification

login CSV

The test taker’s ID/username (not name).

testQtiId

The Identifier for the test, which can be viewed and changed from the general properties panel in test authoring. 

testQtiTitle

The Title of the test, which can be viewed and changed from the general properties panel in test authoring.

deliveryId

The delivery ID of the test.

deliveryExecutionId

Unique identifier for the delivery execution (the session for a given test taker/delivery combination).

testQtiLabel

The label provided for a test in the Test properties form. 

fullTestResourceId

The Resource Identifier located in the delivery’s Properties panel.

Metadata

metadata 

• label: The name of the test, which can be found in the Label field in Test Properties.   

• Any metadata properties defined for the test will be listed with the property's name and the value assigned to the test. 

Timestamps

publicationTime

The exact time the delivery was published (provided as a unix timestamp). 

sessionStartTime CSV

The exact time the test was started by the test taker (provided as a unix timestamp). 

sessionEndTime CSV

The time that the test was submitted (provided as a unix timestamp). This will typically be the same value as submissionTime.

duration

How long it took the test taker to complete the test (in seconds). The value of this field should equal the duration value(s) of each individual item added together.

submissionTime

The exact time the test taker submitted the test (provided as a unix timestamp). This will typically be the same time as sessionEndTime.

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 sessionEndTime.

Scoring

outcomes CSV

Any scoring outcome defined on the test level (in Test authoring) will be listed here. For more information, see Configuring scoring for tests.

• SCORE_TOTAL_MAX: The maximum score defined for the test.

• SCORE_RATIO: The total score achieved by the test taker divided by the maximum possible score). This value should be a decimal number between 0 and 1.

• SCORE_TOTAL: Total score from the given test taker for the test. 

cutScoreRatio

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 null. For more information, see Configuring scoring for tests.

score CSV

The amount of points achieved by the test taker, if defined by the test scoring.  The value of this field should match the value of SCORE_TOTAL in outcomes.

maxScore CSV

The maximum possible score for a delivery (test). The value of this field should match the value of SCORE_TOTAL_MAX in outcomes.

Item level data

items

This section lists each item in the test individually with details about the item, and how the test taker responded to it in the test. 

• Each item’s reference ID, which can be found in the item’s general properties in Test authoring, is listed first.

• numAttempts: 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.

• metadata: The metadata defined for an individual item

  • label: The label of the item in the Item properties (in the Edit Item form).

  • Metadata properties (propertyLabel), such as subject matter, are listed here with each property name and the value assigned to the given item. 

• fullItemResourceId: The item’s Identifier, which can be found in the Item Properties (in Item authoring).

• statusCorrect: CSV Whether the item’s score was correct, false, partially correct, or skipped. 

• qtiTitle: CSV The title of the item in the Item Properties (in Item authoring).

• submissionTime: The exact time the answer to the item’s question was submitted. This time is provided as a unix timestamp.

• qtiId: The Identifier, which can be viewed and modified in the Item’s Properties (in item authoring). 

• qtiLabel: CSV The label of the item in the Item properties (in the Edit Item form).

• duration: CSV How long it took for the test taker to complete the item (in seconds, formatted as a unix timestamp). For linear tests, this timestamp will equal itemEndTime minus itemStartTime. For non-linear tests, this number will equal the total amount of time the test taker spent on the item, including returning to it.

• itemEndTime: 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. 

• outcomes: CSV All outcomes defined on the item will be listed here (especially the ones defined for manual scoring).

  • SCORE: The score achieved by the test taker for the particular item.

  • MAXSCORE: The maximum score available for the item.

  • completionStatus: The completion status of the item. The possible values are incomplete, not_attempted, unknown, or completed.

    • not_attempted means the item was seen but no response was given.

    • completed means the item was seen and a response was given.

    • unknown and incomplete display when an item was not seen by the test taker.

• maxScore: The maximum score available for the item.

• score: The score achieved by the test taker for the particular item.

• responses CSV

  • RESPONSE_x : This value is the response identifier of all the interactions defined in the current item. It is editable from the item authoring screen. If you have multiple interactions in an item, you will have multiple entries here.

    • correct: Whether or not the test taker’s answer was correct.

    • value: The value provided by the test taker for the interaction. For information on the format of the baseType value as an interaction response, see the table below.

• hasFileUpload: When set to true, this field indicates the item has an upload in one of the responses.

• itemStartTime: The exact time the test taker opened the item in the test for the first time. This value is provided as a unix timestamp. 

Serialization for item responses

This table summarizes how QTI baseTypes are serialized depending on their cardinality at export time.