db-details.txt 1.2 KB

123456789101112131415161718192021
  1. The SLOODLE Tracker has 3 database tables:
  2. == sloodle_tracker ==
  3. This is the secondary module table which is required for all SLOODLE modules. It is the equivalent of "sloodle_presenter" etc.. The Tracker doesn't actually have any secondary data, so it contains no useful data.
  4. == sloodle_activity_tool ==
  5. Each time an in-world Tracker tool (such as a button or scanner) gets configured and setup, it will send off a request to "mod/tracker-1.0/auth_tool_linker.php". That script will register the tool in this table. Each tool counts as a single task within a Tracker activity module.
  6. Note that the "trackerid" field gives the course module id of the Tracker activity module to which this tool belongs. It should be the "sloodleid" -- this could be fixed in a future release.
  7. The UUID field stores the UUID of the tool itself.
  8. == sloodle_activity_tracker ==
  9. Each record logs an avatar completing a particular task (i.e. their actions have been logged by a tool).
  10. The activity is identified by the "objuuid" field, which corresponds to the "uuid" field of the sloodle_acitvity_tool table. This means we have an unfortunate caveat: if you replace the tracker tools in-world, then existing progress will not be carried over. This needs to be fixed.