OpenOLAT records course activities of participants and authors in so-called log files. By using the data archiving tool you can download those log files to your personal folder.
|The user log file with personalized data is only available for system administrators for privacy reasons.|
Users with the right to archive (usually course administrators) can save the desired log files as a ZIP file (e.g. CourseLogFiles_2010-01-28_14-55-55.zip) in their personal folder (Personal folder -> private -> archive). This ZIP file contains the selected files course_statistic_log.csv, course_admin_log.csv or course_user_log.csv.
Please note that in the file course_statistic_log.csv course participants are anonymized as follows:
Each course participant receives a number (e.g. *7FFBA8C371B1A3DACCF5F12227A75CE82D6C4CE6) generated at random; this number remains unchanged within a course. This number persists throughout the course. Thus it is possible to observe activities of participant X in course Y but you will not be able to compare these data with course Z since your participant will get another number in course Z.
Possible entries in the log file columns actionCrudType (database operation), actionVerb (action) and actionObject (handled course object)(sorted)
calendart, chat, course, cpgetfile
feed, feeditem, file, folder, forummessage, forumthread
glossar, gotonode, groupmanagement, group, grouparea, groupareaempty
resource, rights, rightsempty
testattempts, testcomment, testid, testscore, testsuccess, tools, toolsempty
The column actionCrudType summarizes the executed actions in basic database operations. As these are broken down in the column actionVerb, the column actionCrudType is not relevant for you. Nevertheless, the operations as follows:
The column actionVerb now further examines what the user (from "userName) actually did with the course object from column actionObject. The entry from column actionObject thus represents the course object being altered, als least from the database's perspective.
So, the third row
u / add / participant / [group name] / [user name]
would be read accordingly (database operation: update / modify): Add user [user name] to [group].
Options to analyze log files graphically will be further described in the section "Statistics".