Skip to main content

Trailmaking Active Task Export Format

  • Updated

In the Trailmaking Active Task, the participant is prompted to touch a series of dots in order and the test tracks how many dots they touch correctly.

When your project uses the CSV export format for Survey Results, data for Active Tasks is exported in the file SurveyTrailmakingResults.csv. When your project uses the JSON export format, Active Task data is included in the file SurveyResults.json.

For a typical survey using this task, you'll expect to see:

  • One survey result each time the participant completes the survey.
  • One step result representing the Active Task.
  • One Trailmaking result for that step. The individual taps are captured within this result.

Table of Contents

Data Fields

Field Description
SurveyTrailmakingResultKey A unique, auto-generated observation ID for a single trailmaking attempt.
SurveyStepResultKey A unique, auto-generated key for this step result. Can be used to cross reference with other survey results.
SurveyResultKey The key for the survey result which this step result is contained in. Can be used to cross reference with other survey results.
ParticipantIdentifier The identifier of the participant this task was for. Can be used to cross reference with Participants.
NumberOfErrors How many errors the participant made when following the trail.
StartDate The timestamp for when the participant started the trailmaking attempt, in ISO 8601 format. Includes timezone offset information.
EndDate The timestamp for when the participant completed the trailmaking attempt, in ISO 8601 format. Includes timezone offset information.
Taps

A list of the individual taps made during the trailmaking attempt, in JSON format. Each tap reports:

  • TapIndex: Identifies what target was tapped. The first expected tap target has an index of '0', the next is '1', and so on.
  • TapTimestamp: A timestamp (elapsed seconds since the start of the trailmaking attempt).
  • TapIncorrect: A flag indicating whether the tap was incorrect.

Sample CSV Export

SurveyTrailmakingResultKey,SurveyStepResultKey,SurveyResultKey,ParticipantIdentifier,NumberOfErrors,StartDate,EndDate,Taps
1111-2222-3333,4444-5555-6666,7777-8888-9999,aaaa-bbbb-cccc,3,2020-12-14T21:06:46+00:00,2020-12-14T21:07:09+00:00,"[{""TapTimestamp"":1.6442149877548218,""TapIndex"":1,""TapIncorrect"":true},{""TapTimestamp"":2.3579819202423096,""TapIndex"":0,""TapIncorrect"":false},{""TapTimestamp"":3.123350977897644,""TapIndex"":1,""TapIncorrect"":false},{""TapTimestamp"":4.0172239542007446,""TapIndex"":2,""TapIncorrect"":false}]"

Sample JSON Export

Note that since the JSON export is included in the SurveyResults.json file, some of the reference keys either do not apply, or are part of the overall survey step data.

{
  "SurveyStepResultKey": "4444-5555-6666",
  "StepIdentifier": "TRAILMAKING_TEST",
  "StartDate": "2020-12-14T21:06:46+00:00",
  "EndDate": "2020-12-14T21:07:09+00:00",
  "Results": [
    {
      "Type": "TrailmakingResult",
      "TrailmakingResultKey": "1111-2222-3333",
      "NumberOfErrors": 3,
      "Taps": [
        {
          "TapTimestamp": 1.6442149877548218,
          "TapIndex": 1,
          "TapIncorrect": true
        },
        {
          "TapTimestamp": 2.3579819202423096,
          "TapIndex": 0,
          "TapIncorrect": false
        },
        {
          "TapTimestamp": 3.123350977897644,
          "TapIndex": 1,
          "TapIncorrect": false
        },
        {
          "TapTimestamp": 4.017223954200745,
          "TapIndex": 2,
          "TapIncorrect": false
        }
      ],
      "StartDate": "2020-12-14T21:06:46+00:00",
      "EndDate": "2020-12-14T21:07:09+00:00"
    }
  ]
}

Was this article helpful?