Custom parameters (grader launch)

Responses selection parameters

deliveryIds

json-encoded string[]

None

Enter the ID of the delivery for which the responses needs to be scored. 

deliveryExecutionIds

json-encoded string[]

None

This parameter identifies items that require manual scoring from specific delivery execution ID (from a single test taker), and displays those items only when grader is launched. This parameter takes precedence over the combination of deliveryIds and testTakerIds. If both are present, only deliveryExecutionIds is considered. Delivery execution IDs can be retrieved using the results API.

testTakerIds

json-encoded string[]

None

Enter the ID(s) of the test-takers for which the responses needs to be scored.

presentationOrder

item , delivery, or title

None

Defines the order in which the responses will be presented to the scorer. Depending on the provided values, the sorting criteria will be either:

• item

  • Item order in the QTI test first

  • Delivery order (as given in the deliveryIds parameter) second

• delivery

  • Delivery order (as given in the deliveryIds parameter) first

  • Item order in the QTI test second

• title

  • Item title order (as defined in Authoring of Test Item title parameter)

  • Delivery order (as given in the deliveryIds parameter) second

    

unscoredFirst

"true" or "false"
true or false

None

Designates that un-scored tasks should come first:

Value can be string (“true”, “false”) or boolean (true or false); both are accepted. Examples:

“unscoredFirst”: "\"true\""
“unscoredFirst”: "\"false\""
“unscoredFirst”: "true"
“unscoredFirst”: "false"

• If “true” or true value is used: un-scored tasks are returned first.

• If “false” or false value is used or this claim is not sent: keep the existing behavior.

Precedence of custom parameters ordering tasks:
When both presentationOrderand unscoredFirst parameters are present, then the unscoredFirstparameters have precedence, meaning that all un-scored tasks are presented first, followed by the scored tasks. The un-scored tasks and the scored tasks are internally sorted by the value provided in the presentationOrderparameter.

scoringCategory

string

None

Prerequisite: A scoring category is set in test Authoring.

This parameter allows graders to do scoring for a specific scoring criteria. For example, if the test item is set with the category “x-tao-scoring-math” in Authoring, then it is possible to score the same category if it is specified in the LTI claims.

Possible values:

• Scoring category must be prefixed with x-tao-scoring-. For example:

  • for “math” it must be x-tao-scoring-math

  • for “science” it must be x-tao-scoring-science

  • for “grammar” it must be x-tao-scoring-grammar

• An item can have only one category in the same test.

• If there are more than one items in the test, it is possible to define different scoring category for each test item, meaning it will be possible to score the test items independently based on their category.

Example use case scenario:

• There are 3 different categories in 3 test items in 1 test and they are properly specified in Authoring:

  • Math: x-tao-scoring-math

    

  • Grammar: x-tao-scoring-grammar

    

  • Science: x-tao-scoring-science

    

• When creating the Scoring Tool launch using LTI, we can apply each scoring category individually, by specifying the custom claim scoringCategory with proper values:

  • Math:

    CODE

    "https://purl.imsglobal.org/spec/lti/claim/custom": {
        "scoringCategory": "x-tao-scoring-math"
    }

  • Grammar:

    CODE

    "https://purl.imsglobal.org/spec/lti/claim/custom": {
        "scoringCategory": "x-tao-scoring-grammar"
    }

  • Science:

    CODE

    "https://purl.imsglobal.org/spec/lti/claim/custom": {
        "scoringCategory": "x-tao-scoring-science"
    }

The Scoring Tool will display the test items for scoring according to the scoring category specified above.

unscoredOnly

boolean
“true” or “false”
true or false

None

Filters for not submitted tasks (items) only. If this filter is applied, then only not submitted tasks will be launched by the Scoring Tool.

scoringLimit

int

None

Specifies the maximum number of tasks, limiting the number of tasks to be launched at once by the Scoring Tool.