Table of Contents
- What is DataShop?
- Getting Data In
- Accessing DataShop
- Project / Dataset Administration
- Citing DataShop and Datasets
- Filtering Data
- Export: Getting Data Out
- Using Other Tools
- Contact Us
You can import a tab-delimited text file of transaction data similar to that generated by the DataShop transaction export. Use the Upload Dataset page to upload and verify your file(s). You may want to import data as tab-delimited text to:
- create a smaller dataset from an existing one
- rename problems or steps
- clean up an existing dataset
- add data to DataShop without creating XML
Read more about the import process.
Note: If you want to create a new domain KC model for an existing dataset in DataShop, use the KC Model export/import feature.
Import file column requirements are described below.
For a handy list of columns, check out our printable DataShop Cheat Sheet.
|Column||Required?||Additional Description||Size Limit (characters)|
|Anon Student Id||*||An anonymized student identifier.||≤ 55|
|Session Id||*||A dataset-unique string that identifies the user's session with the tutor.||≤ 255|
|Time||*||Local time when the transaction occurred. For instance, if a student types "25" and presses return, the transaction time is at the point in which they press return. Must be given in one of the following standard time formats |
|Time Zone||Local time zone ID as provided by the zoneinfo (or tz) database. Select a time zone name from the "TZ" column in this List of zoneinfo time zones.||≤ 50|
|Student Response Type||A semantic description
of the event. DataShop-expected values are
|Student Response Subtype||A further classification of student response type.||≤ 30|
|Tutor Response Type||A semantic description of the tutor's response. DataShop-expected values are
|Tutor Response Subtype||A further classification of tutor response type.||≤ 30|
|Level ()||*||A Dataset Level.
An example of the correct use of this column heading is
|Problem Name||*||The name of the problem or activity.||≤ 255|
|Problem View||The number of times the student encountered the problem so far. This counter increases with each instance of the same problem. Provide either this column or Problem Start Time, but not both. If both are provided, Problem Start Time is used to determine Problem View. A longer description of problem view, including how it is determined if it's not present in the imported data, is available here.|
|Problem Start Time||The time the problem is shown to the student. Must be given in one of the standard time formats . Provide either this column or Problem View, but not both. If both are provided, Problem Start Time is used to determine Problem View. A longer description of problem start time, including how it is determined if it's not present in the imported data, is available here.|
|Step Name||†||The name of a discrete problem-solving step. Include a step name for a transaction if the transaction also has a Tutor Response Type and an Outcome. Otherwise, Attempt At Step will not be calculated.||≤ 255|
|Attempt At Step||DataShop ignores the values in this column when processing the import file. "Attempt at Step" is computed from the rest of the transaction data, but only if Step Name is provided.|
|Outcome||The tutor's evaluation of the action, if applicable. DataShop prefers the
|Selection||†||A description of the interface element that the student selected or interacted with. Multiple Selection columns are OK. Also see Selection in the Guide.||≤ 255|
|Action||†||A description of the manipulation applied to the selection. Multiple Action columns are OK.||≤ 255|
|Input||The input the student submitted. Multiple Input columns are OK. Also see Input in the Guide.||≤ 255|
|Feedback Text||The body of a hint, success, or error message shown to the student.||≤ 65,535|
|Feedback Classification||A further classification of the outcome. See action_evaluation / classification in the Guide. Note that if Feedback Classification has a value, Feedback Text must have a value as well.||≤ 255|
|Help Level||Applicable only to hints, this is the current hint level/depth. If given, value must be a number.|
|Total Num Hints||Total number of hints available to the student for this step. If given, value must be a number.|
|Condition Name||A study/experimental condition. Must always be paired with Condition Type, even if a condition does not have a condition type. Multiple Condition Name columns are OK. See condition in the Guide.||≤ 80|
|Condition Type||A condition classification. Must always be paired with Condition Name, even if a condition does not have a condition type. Multiple Condition Type columns are OK. If Condition Type is specified, Condition Name must have a value as well.||≤ 255|
|KC ()||A knowledge component.
An example of the correct use of this column heading could be
|KC Category ()||A knowledge component category. An example of the correct use of this column
heading could be
|School||The school in which the data were collected, if applicable.||≤ 100|
|Class||The class in which the data were collected, if applicable.||≤ 75|
|CF ()||A custom Field. Use this element to describe other contextual information or a
new variable not adequately captured by the other columns. An example of the correct use of
this column heading could be
† At least one of Step Name, Selection, or Action must have a value for each row.
 Time must be given in one of the following formats:
|Format||Example and Notes|
|2001-07-04 12:08:56.0 ** OLI and DataShop export format|
|2001-07-04 12:08:39:110 ** Carnegie Learning format|
|2001-07-04 12:08:56 ** CTAT Flash format|
|July 04, 2001 12:08:56 AM ** WPI-Assistments format|
|2010/05/11 16:06:28.65 ** CTAT Java format|
|1239939193 ** Unix time in milliseconds|
|01239939193.31 ** Unix time in milliseconds|
This date-less format is the result of Excel applying its own formatting. You may see this format if you opened and saved a DataShop transaction export file in Excel, but didn't apply TEXT formatting to the columns while opening it. See our advice on how to avoid this issue. To correct it, you will need to find a copy of your file that has date information.
 For columns that are required as pairs— Condition Name and Condition Type, or KC and KC Category—these columns must be listed in the order that they are paired. For example, if a dataset file has two condition columns, the column format would be Condition Name, Condition Type, Condition Name, Condition Type.