File size: 6,951 Bytes
4f8d571 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | ,Field,Annotation
0,Row,A row counter
1,Sample Name,"The sample that contains the transaction. If a transaction appears in multiple samples, the transaction will be repeated, but with a different sample name."
2,Transaction Id,A unique ID that identifies the transaction. Currently used for annotating transactions with custom fields via web services.
3,Anon Student Id,"DataShop-generated anonymous student ID. To obtain original student identifiers or to learn more about data anonymization, see About data anonymization below."
4,Session Id,A dataset-unique string that identifies the user's session with the tutor.
5,Time,"Time 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."
6,Time Zone,"The local time zone (e.g., EST, PST, US/Eastern)."
7,Duration (sec),"Duration of the transaction in seconds. This is the time of the current transaction minus that of the preceding transaction or problem start event��whichever is closer in time to the current transaction. If this difference is greater than 10 minutes, or if the prior transaction occurred during a different user session, DataShop reports the duration as null (a dot). If the current transaction is preceded by neither another transaction or a problem start event, duration is shown as null. The duration is formatted without decimal places if the two times used in the calculation were without millisecond precision."
8,Student Response Type,"The type of attempt made by the student (e.g., ""ATTEMPT"" or ""HINT_REQUEST""). This is logged in the semantic_event element."
9,Student Response Subtype,"A more detailed classification of the student attempt. For example, the CTAT software describes actions taken by the tutor on behalf of the student as having subtype ""tutor-performed""."
10,Tutor Response Type,"The type of response made by the tutor (e.g., ""RESULT"" or ""HINT_MSG"")."
11,Tutor Response Subtype,A more detailed classification of the tutor response.
12,Level (level_type),"The problem hierarchy name (e.g., ""Understanding Fractions"") of the type specified in the column header (e.g., ""Unit""). There may be multiple ""Level"" columns if the problem hierarchy is more than one level deep. Level is logged in the level element."
13,Problem Name,"The name of the problem. 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. These fields are logged in the problem element."
14,Problem View,"The number of times the student encountered the problem so far. This counter increases with each instance of the same problem. See ""Problem View"" in the ""By Student-Step"" table below."
15,Problem Start Time,"If the problem start time is not given in the original log data, then it is set to the time of the last transaction of the prior problem. If there is no prior problem for the session, the time of the earliest transaction is used. Earliest transaction time is equivalent to the minimum transaction time for the earliest step of the problem. For more detail on how problem start time is determined, see Determining Problem Start Time."
16,Step Name,"Formed by concatenating the ""selection"" and ""action"". Also see the glossary entry for ""step""."
17,Attempt at Step,"As of this transaction, the current number of attempts toward the identified step."
18,Outcome,"The tutor's evaluation of the student's attempt. For example, ""CORRECT"", ""INCORRECT"", or ""HINT"". This is logged in the action_evaluation element."
19,Selection,"A description of the interface element(s) that the student selected or interacted with (for example, ""LowestCommonDenominatorCell""). This is logged in the event_descriptor element."
20,Action,A description of the manipulation applied to the selection.
21,Input,"The input the student submitted (e.g., the text entered, the text of a menu item or a combobox entry)."
22,Feedback Text,"The body of a hint, success, or incorrect action message shown to the student. It is generally a text value, logged in the tutor_advice element."
23,Feedback Classification,"The type of error (e.g., ""sign error"") or type of hint."
24,Help Level,"In the case of hierarchical hints, this is the depth of the hint. ""1"", for example, is an initial hint, while ""3"" is the third hint."
25,Total Num Hints,The total number of hints available. This is logged in the action_evaluation element.
26,Condition Name,"The name of the condition (e.g., ""Unworked"")."
27,Condition Type,"A condition classification (e.g., ""Experimental"", ""Control""); optional at the time of logging."
28,KC (model_name),"The knowledge component for this transaction. It is a member of the knowledge component model named in the column header. One ""KC (model_name)"" column should appear in the export for each KC model in the dataset. "
29,KC Category (model_name),"The knowledge component ""category"" logged by some tutors. It is a member of the knowledge component model named in the column header. One ""KC Category (model_name)"" column should appear in the export for each KC model in the dataset."
30,School,The name of the school where the student used the tutor to create this transaction.
31,Class,The name of the class the student was in when he or she used the tutor to create this transaction.
32,CF (custom_field_name),"The value of a custom field. This is usually information that did not fit into any of the other logging fields (i.e., any of the other columns), and so was logged in this special container. "
33,Event Type,"Allowed values are ""assess"", ""instruct"" and ""assess_instruct"". Blank is also allowed. Only ""instruct"" and ""assess_instruct"" values are treated as learning opportunities. "
|