GSoc 2017: Add Rating System in CritiqueBrainz

[Deleted_Editor_1240840]

@Pinank_Solanki

Implement a rating system on a scale of 10

The plan in the tickets you linked was to initially have a 5-star rating system. Like what we have on MusicBrainz already.

@Pinank_Solanki

a) Addition of rating tables to the database.
b) Add the rating feature.

I’d say tables are a part of the rating feature. Do you mean UI integration?

@Pinank_Solanki

First of all, there will be a need to introduce two new tables to the existing schema viz. rating and avg_rating.

rating - to store score by user of a given entity
avg_rating - to store average score of an entity

Can’t average score be computed from data in the rating table?

@Pinank_Solanki

The aim behind providing guidelines to users before rating is to maintain a uniform standard for all so that readers of the rating can get a fair and accurate idea of the logic with which the user rated. This will play a key role in showing what is the general response for entity (Average rating). The guidelines will be simple and lucid.

I don’t think this is such a good idea. Each author should decide on their own how they rate reviews no matter what the scale is. Besides, it’s kind of obvious that 1 star is bad and 5 starts is good.

@Pinank_Solanki

Optional Ideas

I would like to work on second phase of building the rating system - CB-248. The users will be able to create different scales of their own choice and their average will be stored as the overall rating for an entity.

Change schema accordingly to store scores for every scale and have revisions (Decision required).
UI changes and update the guidelines.
The page for showing all ratings will of true essence now that readers can get insight of various aspects of an entity.

If this is out of scope for your GSoC proposal then it’s better to leave it out and focus what the idea that you plan to work on.

---

This is slightly different from how I imagined this would work. My thinking was to consider rating as an extension of a review. So review would be one of these three things:

• text (that’s what we have currently)
• text + rating
• rating

When user clicks on “Review this” they can choose what their review is going to include. Things like average rating can be computed only from reviews that have a rating on them.

You also mention support for editing ratings, but I’d think that would be an important part of revision system. Let’s say we have text + rating kind of review. If author modifies text and rating, I’d say it’s important to know what the rating was before, not only what it is currently.

So to summarise, not considering rating being a separate thing, but just a part of a review would make it easier to think about in the context of other things (like revision system) we already have.