| ,Field,Annotation | |
| 0,Row,A row counter. | |
| 1,Sample,"The sample that includes this step. If you select more than one sample to export, steps that occur in more than one sample will be duplicated in the export." | |
| 2,Anon Student ID,The student that performed the step. | |
| 3,Problem Hierarchy,The location in the curriculum hierarchy where this step occurs. | |
| 4,Problem Name,The name of the problem in which the step occurs. | |
| 5,Problem View,"The number of times the student encountered the problem so far. This counter increases with each instance of the same problem. Note that problem view increases regardless of whether or not the step was encountered in previous problem views. For example, a step can have a ""Problem View"" of ""3"", indicating the problem was viewed three times by this student, but that same step need not have been encountered by that student in all instances of the problem. If this number does not increase as you expect it to, it might be that DataShop has identified similar problems as distinct: two problems with the same ""Problem Name"" are considered different ""problems"" by DataShop if the following logged values are not identical: problem name, context, tutor_flag (whether or not the problem or activity is tutored) and ""other"" field. For more on the logging of these fields, see the description of the ""problem"" element in the Guide to the Tutor Message Format. For more detail on how problem view is determined, see Determining Problem View." | |
| 6,Step Name,"Formed by concatenating the ""selection"" and ""action"". Also see the glossary entry for ""step""." | |
| 7,Step Start Time,"The step start time is determined one of three ways: If it's the first step of the problem, the step start time is the same as the problem start time If it's a subsequent step, then the step start time is the time of the preceding transaction, if that transaction is within 10 minutes. If it's a subsequent step and the elapsed time between the previous transaction and the first transaction of this step is more than 10 minutes, then the step start time is set to null as it's considered an unreliable value. For a visual example, see the Examples page." | |
| 8,First Transaction Time,The time of the first transaction toward the step. | |
| 9,Correct Transaction Time,"The time of the correct attempt toward the step, if there was one." | |
| 10,Step End Time,The time of the last transaction toward the step. | |
| 11,Step Duration (sec),"The elapsed time of the step in seconds, calculated by adding all of the durations for transactions that were attributed to the step. See the glossary entry for more detail. This column was previously labeled ""Assistance Time"". It differs from ""Assistance Time"" in that its values are derived by summing transaction durations, not finding the difference between only two points in time (step start time and the last correct attempt)." | |
| 12,Correct Step Duration (sec),"The step duration if the first attempt for the step was correct. This might also be described as ""reaction time"" since it's the duration of time from the previous transaction or problem start event to the correct attempt. See the glossary entry for more detail. This column was previously labeled ""Correct Step Time (sec)""." | |
| 13,Error Step Duration (sec),The step duration if the first attempt for the step was an error (incorrect attempt or hint request). | |
| 14,First Attempt,"The tutor's response to the student's first attempt on the step. Example values are ""hint"", ""correct"", and ""incorrect""." | |
| 15,Incorrects,Total number of incorrect attempts by the student on the step. | |
| 16,Hints,Total number of hints requested by the student for the step. | |
| 17,Corrects,Total correct attempts by the student for the step. (Only increases if the step is encountered more than once.) | |
| 18,Condition,"The name and type of the condition the student is assigned to. In the case of a student assigned to multiple conditions (factors in a factorial design), condition names are separated by a comma and space. This differs from the transaction format, which optionally has ""Condition Name"" and ""Condition Type"" columns." | |
| 19,KC (model_name),"(Only shown when the ""Knowledge Components"" option is selected.) Knowledge component(s) associated with the correct performance of this step. In the case of multiple KCs assigned to a single step, KC names are separated by two tildes (""~~"")." | |
| 20,Opportunity (model_name),"(Only shown when the ""Knowledge Components"" option is selected.) An opportunity is the first chance on a step for a student to demonstrate whether he or she has learned the associated knowledge component. Opportunity number is therefore a count that increases by one each time the student encounters a step with the listed knowledge component. In the case of multiple KCs assigned to a single step, opportunity number values are separated by two tildes (""~~"") and are given in the same order as the KC names. Check here to see how opportunity count is computed when Event Type column is present in transaction data." | |
| 21,Predicted Error Rate (model_name),"A hypothetical error rate based on the Additive Factor Model (AFM) algorithm. A value of ""1"" is a prediction that a student's first attempt will be an error (incorrect attempt or hint request); a value of ""0"" is a prediction that the student's first attempt will be correct. For specifics, see below ""Predicted Error Rate"" and how it's calculated. In the case of multiple KCs assigned to a single step, Datashop implements a compensatory sum across all of the KCs, thus a single value of predicted error rate is provided (i.e., the same predicted error rate for each KC assigned to a step). For more detail on Datashop's implementation for multi-skilled step, see Model Values page." | |