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
Logging New Data
There are a number of ways to log data from your course or study to DataShop. Important factors for selecting a method are the stage and technology of the tutoring system implementation. We'll examine a variety of cases in detail below, including each of their requirements and benefits.
The definitive reference for the logging format accepted by DataShop is the Guide to the Tutor Message format. This guide is intended primarily for software developers who to want implement logging in an educational tutoring application, or convert existing logs created by a tutoring application.
- Logging URLs
- CTAT- and OLI-based tutors
- Java or Flash tutors or educational applications not CTAT- or OLI-based
- Tutors deployed via Carnegie Learning
- Tutors not created in Java or Flash
Tutors or applications logging to DataShop should use one of the following URLs based on the status of data collection and the study in general. See the log conversion schedule for exact log conversion times. If you don't see your data, please contact us.
|DataShop QA||http://pslc-qa.andrew.cmu.edu/log/server||Log here to test that logging works from your application, course, or study, and to verify the content of your log messages. This server is for test data only, not for data from real subjects. No research can be done on data collected on this server. Processed logs are generally available in the DataShop QA web application within two hours: http://pslc-qa.andrew.cmu.edu/datashop|
|DataShop Production||http://learnlab.web.cmu.edu/log/server||Log here to record real student data from a study or course. Processed logs are generally available in the DataShop Production web application the following day: http://pslcdatashop.web.cmu.edu/|
CTAT- and OLI-Based Tutors
Any tutor created with the Cognitive Tutor Authoring Tools (CTAT) or Open Learning Initiative's (OLI) tools has logging functionality built-in. Within this category, the scenarios for logging differ slightly depending on the deployment environment:
CTAT Flash tutor deployed to the PSLC server within the context of an OLI course: this type of tutor will log to DataShop if configured properly.
In a learning page (deprecated), the flash_tutor element must be used, as specified in the OLI learning page DTD. In addition, logging properties should be set using the vars attribute. For example:
<flash_tutor src = "../webcontent/buffers-1a.swf" height="200" width="500" vars="problem_name=buffers1a&school_name=CMU&dataset_name=Chemistry_Buffer_Study &unit_name=Chemistry_Buffers§ion_name=Buffers" />
In a workbook page (recommended), the flash element must be used, as specified in the OLI workbook page DTD. Logging parameters should be set using the param elements (see the CTAT web site for a reference of the various parameters. Also note that you must have and reference the Flash logging library. For example:
<flash height="475" width="700" src="../../../webcontent/flash/resources1-exp.swf"> <caption>Ressources humaines </caption> <params> <param name="Logging">ClientToLogServer</param> <param name="dataset_name">French_Culture_Tutor_Fall_2005</param> <param name="question_file">../../../webcontent/flash/resources1.brd</param> <param name="problem_name">resources1</param> <param name="school_name">CMU</param> <param name="dataset_level_type1">Unit</param> <param name="dataset_level_name1">CMU</param> <param name="dataset_level_type2">Section</param> <param name="dataset_level_name2">E</param> <param name="LoggingLibraryPath">http://learnlab.web.cmu.edu/swf/CommLoggingLibrary.swf</param> </params> </flash>
- CTAT Flash tutor deployed on a server other than the PSLC server: this type of tutor can log to DataShop, but this setup must be coordinated with us to ensure that your tutor's logging request is accepted by the PSLC server. See the CTAT web site for how to enable logging and for documentation describing the various logging parameters.
- CTAT Java tutor: this type of tutor can log either to the hard disk of the system running the tutor, or if the system has Internet connectivity, directly to the PSLC server. Enabling and configuring logging is described on the CTAT web site. Contact us prior to running your study if you're interested in using this option.
- Flash tutor created using the OLI tools and deployed to the PSLC server with the context of a course: this type of tutor will log to DataShop if properly configured. See the workbook page syntax above for an example of how to specify logging parameters. Note that the logging library is built in for these tutors.
Java or Flash tutors or educational applications not CTAT- or OLI-based
If you are creating a Java or Flash tutor or educational application and would like to log to DataShop, download and use the existing logging libraries. Both the Java and Flash logging libraries include well-documented APIs and sample applications for learning to integrate logging functionality into your application. Also see the Guide to the Tutor Message format for more on the logging format produced by the logging libraries.
Tutors deployed via Carnegie Learning
Carnegie Learning provides logging of tutors deployed in their curriculum management system. To view these logs in DataShop, the logs must first be harvested from the local machines used in the study. As honest broker, Carnegie Learning then anonymizes the data and provides DataShop with converted logs.
If you are running a study involving Carnegie Learning tutors and you would like to use DataShop, please contact us and inform us of the location of the study, who's involved, and the timing of the study. Early notice is appreciated.
Tutors not created in Java or Flash
An existing project with sufficient technical resources may be best suited to implementing logging in a different language. If so, developers should consult the Guide to the Tutor Message format. In this case, the tutor should write log data to files, and the files can be zipped and sent to us.
Note: DataShop currently supports versions 2 and 4 of the logging format.