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
When activated, this report provides a logging diagnostic by displaying counts of all recent log messages received by the logging server, organized by dataset and student session. It is intended for use by technical researchers or staff who are in the process of verifying logging activity from a study site.
Since this report is generated by querying the live logging database, and using it has the potential to affect that database, we are requesting that you agree to follow the guidelines at the top of the page before using the page.
- Session ID
- A unique identifier that identifies the student session with the tutor. Although this varies by logging implementation, expect one session ID for every student session (an instance of a user logged in and generating log data). Although session ID should be a guaranteed unique identifier (a GUID), a duplicate session ID is possible, and the presence of duplicates could skew the data in this report.
- First Message Receipt Time
- The time on the DataShop server when the first message of the session was received. Note that this is first message for the session within the specified time frame.
- Last Message Receipt Time
- The time on the DataShop server when the last message of the session was received.
- The total number of log messages (Context, Tool, Tutor, and Plain messages) received within the specified time frame.
- The number of context messages received within the specified time frame. A typical number of context messages is one per problem or activity.
- The number of tool messages received within the specified time frame. A typical number of tool messages is one per click or other student action.
- The number of tutor messages received within the specified time frame. A typical number of tool messages is one per click or other student action.
- The number of plain messages received within the specified time frame. The number of plain messages, or generic messages repurposed by the tutoring system, varies more widely than the other message types. For most systems, this message type should be used far less than the other types.