Sloodle Database Usage

From SLIS Second Life Wiki

Jump to: navigation, search

Sloodle adds various pieces of information to Moodle's database. You can the information about exactly what it does here.

Contents

Sloodle Tables

When the Sloodle module is installed (see Installing the Sloodle Module), Moodle will create new database tables specially for it. All of these tables are prefixed with "sloodle_" (note, Moodle may also add its own prefix before that, such as "mdl_" or "moodle_"). You can find the database installation files in the Sloodle module soure code, in folder "db".

Sloodle 0.3

Sloodle Versions: 0.3 (?)

Developers: Sloodle 0.3 Database Schema
Table Name # Fields Description
sloodle 7 Each entry defines an instance of a Sloodle module (such as a Controller or a Distributor module)
sloodle_controller 4 Provides additional data about a Sloodle Instance specific to the Controller module type
sloodle_distributor 4 Provides additional data about a Sloodle Instance specific to the Distributor module type
sloodle_distributor_entry 3 Each entry describes a single object available through a particular Distributor module
sloodle_users 5 Stores the details of each known avatar, and which Moodle account they are linked to (see Registration and Enrolment)
sloodle_course 8 Stores Sloodle settings for each Moodle course, such as the location of the course LoginZone object, and whether or not auto registration and auto enrolment are enabled for this particular course
sloodle_pending_avatars 5 During the avatar registration process, avatar data is temporarily stored here until it is linked to a Moodle user account
sloodle_active_object 8 Maintains a list of objects and internal passwords which have been authorised for use with a particular Controller
sloodle_object_config 4 Stores the configuration settings for an authorised object (or 'active' object)
sloodle_login_notifications 5 If an avatar is auto registered, then their automatically generated login details are stored here until they can be sent into Second Life (via email, initiated by a cron job)
sloodle_layout 4 Identifies a particular named layout of objects, stored using a Sloodle Set
sloodle_layout_entry 5 Each entry stores the name, position and rotation of an object in a layout
sloodle_loginzone_allocation 5 If a Moodle user has opted to use the LoginZone to register their avatar, then their allocated login position is stored here until used
sloodle_user_object 7 The Sloodle Toolbar (and in future possibly other objects) can be authorised by a user for their own user-centric tasks, such as writing blogs. This table stores the object/avatar association and security details.


Sloodle 0.2 / 0.21

Sloodle Versions: 0.2, 0.21 (?)

Table Name # Fields Description
sloodle 3 (For future use.) Defines instances of the Sloodle module.
sloodle_active_object 5 Each entry represents one known Sloodle object, which has been authorized.
sloodle_classroom_setup_profile 3 Each entry represents a classroom profile, which stores a layout of Sloodle objects for the Sloodle Set.
sloodle_classroom_setup_profile_entry 5 Individual object entries for classroom profiles.
sloodle_users 9 Stores the avatars associated with the Moodle site, and notes which Moodle account each one is linked to.



Sloodle 0.19

Sloodle Versions: 0.19 (?)

NOTE: this information is no longer current. It is stored only for reference.

Table Name # Fields Description
sloodle_users 8 Stores the avatars associated with the Moodle site, and notes which Moodle account each one is linked to.
sloodle_config 2 Stores Sloodle configuration settings.
sloodle_active_object 5 Each entry represents one known Sloodle object, which has been authorized.
sloodle_classroom_setup_profile 3 Each entry represents a classroom profile, which stores a layout of Sloodle objects for the Sloodle Set.
sloodle_classroom_setup_profile_entry 5 Individual object entries for classroom profiles.


Other Tables

Sloodle also affects other table in the database, but it only ever adds entries to these tables, so it should behave in exactly the same way as the normal Moodle tools.

Moodle Config

Sloodle 0.3 stores the following data in the central Moodle configuration table:

Sloodle 0.2/0.21 stores the following data in the central Moodle configuration table:


Blog

If anybody uses the Sloodle Toolbar to write blog entries, then Sloodle will add entries to the blog entry table ("post") in your Moodle database.

Chat

If the Sloodle WebIntercom is used with a chatroom on your Moodle site, then Sloodle will read from and write to the "chat_messages" messages table.

Quiz

If the Sloodle Quiz Chair is used with a quiz on your Moodle site, then a student may make official attempts at the quiz (table "quiz_attempts"). Question data is read using the standard Moodle code. This can ultimately affect the grading. WARNING! Before Sloodle 0.3, the Quiz Chair could skew results by allowing unlimited re-attempts.
Note: the Sloodle Pile On Quiz will not add attempts for the students who use it, although it may have to create a 'ghost' attempt for the educator in order to read question data correctly.

Glossary

The Sloodle MetaGloss tool will read from (but not write to) the glossary tables in your database ("glossary", "glossary_alias", "glossary_entries").

Choice

Sloodle 0.3 only: The Sloodle Choice tool will read information from your choice module tables ("choice" and "choice_options"), and if anybody selects an option in-world, then it will add responses to the "choice_answers" table.

PrimDrop

Sloodle 0.3 only: If you choose to install the Sloodle Object Assignment plugin and use the Sloodle PrimDrop with it, then whenever a student submits an object in-world, an attempt will be added to the assignment you specify (table "assignment_submissions"). This will be reflected in the Moodle gradebook if you grade the submission.


This page is part of the Sloodle documentation
SloodleDocs Home | User Documentation | Administrator Documentation | Developer Documentation | Sloodle Wiki Home
Personal tools