Re: Dev chat reminder, issue 55bb3f03-c4b3-4b1e-b410-665962130786
Shadab Zafar <[email protected]> Mon, 1 Jun 2015 23:18:19 +0530
| Newsgroups | gmane.comp.audio.musicbrainz.devel |
|---|---|
| Message-ID | <CAKP=8n3pXN2rNYtrCEE3_1d77uY0UGd5eqQ7uhPyMkxJ4WaAww@mail.gmail.com> |
I began re-working Gentlecat's pull on adding ratings to CB. https://bitbucket.org/metabrainz/critiquebrainz/pull-request/239/ Most of the time was spent in understanding the existing code, and editing the commits to allow for a different star ratings extension. http://plugins.krajee.com/star-rating The new pull is here. https://bitbucket.org/metabrainz/critiquebrainz/pull-request/270/ But, the original reason that the old pull was closed is still standing. The way we're currently doing things is: We have an interface similar to MB that allows a user to rate a release group directly from the release group entity page (I still need to finish this.) We also allow a user to rate the release group when they're writing a review. We send this rating to MB, but also keep it in our own database (so that we can access it faster.) The problem arises, when a user rates the release group via MB. Now, what do we display with the review? the old rating that is in our DB or the updated one? One solution is to just not store the rating on CB's side. We will still allow a user to rate the release while writing a review. In this case no rating will be displayed on the review's entity page. But some people might want to associate a rating with the review. We can't seem to decide what would be better. Any and all feedback appreciated. Regards, dufferZafar