Ratings 2.0
Objectives
Ratings are grades entered away from the gradebook. They can be entered by students and teachers and are aggregated into grades.
The goals of ratings 2.0:
- Manage ratings centrally
- Use a consistent approach for all ratings throughout Moodle
- Easily integrate ratings 2.0 with existing modules
- Remove duplicate implementations of ratings functionality
Overview
The ratings 2.0 provides APIs to:
- Add ratings
- Update ratings
- Access collected ratings for grade calculation purposes
- Delete ratings
Current tracker issues
MDL-21389 Write spec for separate Ratings 2.0
MDL-20514 Allow Aggregate Type in Glossary Activity
MDL-21657 Implement Ratings 2.0
Interface
When Javascript is enabled ajax submission means the button can be removed. In the future it would be possible to automatically interpret a 1 to 5 rating as a star rating style UI element.
If the user has 'post' permission as returned by modname_rating_permissions() the dropdown box and submission button will be displayed.
If the user has 'view' permissions the text to the left of the dropdown box will be displayed. The displayed text consists of the aggregate of the ratings, 4 out of 5 in the example. The number in brackets is the number of ratings that have been submitted. There have been two ratings submitted in the example.
If the user has 'viewall' permissions they can click on the aggregate summary to view a list of all of the ratings that have been submitted. This is a listing of each user's profile pic, their name and the rating they submitted.
Database changes
New tables
Ratings
Field | Type | Default | Info |
---|---|---|---|
id | int(10) | auto-incrementing | The unique ID for this comment. |
contextid | int(10) | The context id defined in context table - identifies the instance of plugin owning the comment. | |
itemid | int(10) | Some plugin specific item id (eg. forum post blog entry) | |
scaleid | int(10) | ID of the scale (1-5, 0-100, custom) from which the user selected their rating. Including this allows smarter handling of previously entered ratings should the scales be changed. | |
rating | int(10) | The user's rating | |
userid | int(10) | The user who submitted the rating | |
timecreated | int(10) | ||
timemodified | int(10) |
Altered tables
The forum, glossary and data tables need to be altered to contain the required fields specificed in [1]
Removed database tables
The following tables will have their data migrated to the above ratings table and then be removed:
data_ratings
forum_ratings
glossary_ratings
Scales
Course modules will continue to store the scale associated with their ratings. For example the glossary table has a scale column.
Scales are going to be refactored as part of a separate issue. See MDL-17258.
Ratings code changes
lib/ratinglib.php will contain...
class rating
__construct($contextid, $itemid, $scaleid, $userid)
Initialize a class instance.
update_rating($rating)
Add rating to database
get_rating()
get the rating
delete_rating()
delete the rating. Not implemented yet as it hasn't been required.
static get_rating_permissions($context)
Returns an array representing the current user's permission to view and submit ratings.
static load_ratings($context, $items, $aggregate=RATING_AGGREGATE_AVG, $scaleid, $userid = null, $returnurl = null)
Returns an result set of ratings including aggregated ratings. $items is an array of objects with an id member variable ie $items[0]->id.
function load_ratings($context, $items, $aggregate=RATING_AGGREGATE_AVG, $scaleid, $userid = null, $returnurl = null) {
global $DB, $USER;
if (isnull($userid)) {
$userid = $USER->id;
}
$itemids = array();
foreach($items as $item) {
$itemids[] = $item->id;
}
list($itemidtest, $params) = $DB->get_in_or_equal(
$itemids, SQL_PARAMS_NAMED, 'itemid0000');
$sql = "SELECT r.itemid, ur.id, ur.userid, ur.scaleid,
$aggregatestr(r.rating) AS aggrrating,
COUNT(r.rating) AS numratings,
ur.rating AS usersrating
FROM {ratings} r
LEFT JOIN {ratings} ur ON ur.contextid = r.contextid AND
ur.itemid = r.itemid AND
ur.userid = :userid
WHERE
r.contextid = :contextid AND
r.itemid $itemidtest
GROUP BY r.itemid, ur.rating
ORDER BY r.itemid";
$params['userid'] = $userid;
$params['contextid'] = $context->id;
return rating::make_rating_subobjs($context, $items, $DB->get_records_sql($sql, $params), $aggregate, $scaleid, $returnurl);
}
private static make_rating_subobjs($context, $items, $ratingsrecords, $aggregate, $scaleid, $returnurl)
Similar to make_context_subobj(). Iterate over forum $items (forum posts, glossary items etc) and create the $item->rating objects. Properties of the individual ratings, such as $item->rating->aggregate and $item->rating->rating, are stored on the rating object directly. Settings common to the ratings are stored at $item->rating->settings->aggregationmethod. For example $item->rating->settings->aggregationmethod.
Rendering ratings
As rendering a rating will consist of only a single function call a new method called render_rating() will be added to the core renderer.
If necessary a ratings renderer could be added. Located in mod/ratings/renderer.php this new class core_rating_renderer should extend plugin_renderer_base defined in lib/outputrenderers.php Almost all renderers appear to inherit from plugin_renderer_base rather than core_renderer.
core_renderer::render_rating(rating $rating)
returns rating UI html snippet. Used to include ratings in pages.
Using the rating renderer
The process to render ratings is as follows:
// in mod/forum/discuss.php (for example)
$posts = // Some forum/lib.php function call.
//these are supplied by the calling module (forum etc)
$aggregate =
$scaleid =
$userid =
$returnurl =
//The current scaleid comes from the forum or glossary object and may be changed at any time so supply it each time
//Also, a user should only see their own ratings
$posts = rating::load_ratings($context,
$posts/* Optional array of items (forum posts or glossary items) with an 'id' property. If null returns all ratings for the context by the user*/,
$aggregate,
$scaleid,
$userid,
$returnurl);
//ratings are now attached to the post objects. $posts[0]->rating
foreach ($posts as $postid => $post) {
$forumoutput->post($post);//access the rating info at $post->rating, $post->rating->aggregate and $post->rating->count
}
// in mod/forum/renderer.php, in the post($post) method:
// ... output most of the post ... starts around line 5813 of mod/forum/lib.php
echo $OUTPUT->render($item->rating);
// ... output the rest.
// and finally in rating/lib.php in the Rating class:
public function core_renderer::render_rating(rating $rating) {
//return html representation of the rating
}
Ratings Aggregation
Forums currently support multiple forms of rating aggregation such as average, maximum, sum etc. These options should be available everywhere that ratings are available.
They are calculated within rating::ratings_load_ratings()
Ratings Settings
Settings for ratings are stored by the module. Each module table, for example forum, must contain the following columns.
Field | Type | Default | Info |
---|---|---|---|
aggregation | int(10) | The aggregation method to apply. Currently this is stored in the assessed column in the table "forum". | |
allcanrate | int(10) | Allow anyone to rate items. Currently this is stored in the assessed column in the table "glossary". | |
assesstimestart | int(10) | From when can users submit ratings | |
assesstimefinish | int(10) | When must users submit ratings by | |
scale | int(10) | What scale to use |
Where is the "Restrict ratings to posts with dates in this range:" flag stored?
Settings interface
moodleform_mod::standard_coursemodule_elements()
Adds elements to an instance of moodle form. The ratings elements should appear in a separate block from Common Module Settings.
It will determine whether to include ratings settings by calling plugin_supports() found in lib/moodlelib.php like this...
if (plugin_supports('mod', $this->_modname, FEATURE_RATINGS, false)) {
//include ratings elements
}
mod/%modulename%/lib.php defines a function called %modulename%_supports() that lists the elements that the module supports.
FEATURE_MOD_RATINGS will have to be added to lib/moodlelib.php
Rating Submission
lib/rating.php will be the target for posted ratings. Currently each module implements their own ratings submission. For example mod/glossary/rate.php within the glossary module.
The supplied fields should consist of
Field | Type | Default | Info |
---|---|---|---|
contextid | PARAM_INT | The context id defined in context table - identifies the instance of plugin owning the comment. | |
itemid | PARAM_INT | Some plugin specific item id (eg. forum post blog entry) | |
scaleid | PARAM_INT | ID of the scale (1-5, 0-100, custom) from which the user selected their rating. Including this allows smarter handling of scales being changed. | |
rating | PARAM_INT | for example, in user profile, you can comment user's description or interests, but they share the same itemid(==userid), we need comment_area to separate them | |
returnurl | PARAM_LOCALURL | Null for ajax requests. If not null the url to which the user should be redirected after recording the rating |
The process to record a rating is as follows:
$permissions = forum_rating_permission();
if($permissions['post']) {
$rating = N; //the actual rating from the user
$ratingObj = new Rating($contextid, $scaleid, $userid, array($itemid));
$ratingObj->set_rating($rating);
//redirect to return url if supplied
}
//within the class Rating
function Rating::update_rating($rating) {
$ratings = rating_system::load_ratings($scaleid, $userid, $contextid, array($itemid));
if( !$ratings || sizeof($ratings)==0) {
$data->contextid = $this->contextid;
$data->scaleid = $this->scaleid;
$data->userid = $this->userid;
$data->rating = $rating;
$DB->insert_record($this->table, $data);
}
else {
$data->id = $this->id;
$data->rating = $rating;
$DB->update_record($this->table, $data);
}
}
Ajax submission
Ajax submission of ratings must be possible for sites with ajax enabled. ForumNG (http://moodle.org/mod/data/view.php?d=13&rid=2927) written by Sam Marshall contains an ajax implementation of the rating UI elements that may be useful to reference.
Check if ajax is enabled like this...
if (empty($CFG->enableajax)) {
//no ajax
}
else {
//add ajax stuff
}
Permissions changes
New ratings permissions
Permission could be handled in one of two ways.
Centralized ratings permissions
Control the ratings related permissions within the ratings module itself. This would allow less fine grained control but makes adding ratings to new areas of Moodle much less invasive.
As each module currently has its own ratings permissions migrating to single set of rating permissions could be tricky. What should happen if a user has viewall permissions in the forums but not in the glossary for example?
Rating::get_ratings_permissions()
public static function get_rating_permissions($context) {
return array(RATING_VIEW=>has_capability('moodle/ratings:view',$context), RATING_VIEW_ALL=>has_capability('moodle/ratings:viewall',$context), RATING_POST=>has_capability('moodle/ratings:rate',$context));
}
If more fine grained control is required the modules could provide a permissions check callback...
Module callback
This allows modules to individually control ratings so, for example, the user may be able to rate forum posts but not glossary items.
modname_rating_permissions()
Modules can implement a function named modname_rating_permissions to control post and view permission. This is called prior to rendering a set of ratings. It is also called by lib/rating.php when it receives and ajax rating submission.
This function will return an array: array('view'=>true, 'viewall'=>true, post'=>true)
This example shows how this would work for the forum module
function forum_rating_permissions() {
$context = get_context_instance(CONTEXT_MODULE, $this->cm->id);
return array('view'=>has_capability('mod/forum:viewrating',$context), 'viewall'=>has_capability('mod/forum:viewanyrating',$context), 'post'=>has_capability('mod/forum:rate',$context));
}
Old ratings permissions
Assuming centralized rating's permissions are used module specific permissions can be removed:
- mod/data:rate
- mod/data:viewrating
- mod/forum:rate
- mod/forum:viewanyrating
- mod/forum:viewrating
- mod/glossary:rate
- mod/glossary:viewrating
See also
- MDL-21657 Implement Ratings 2.0