rvelices wrote:

The popularity score might be difficult to compute and maintain in php/mySql (the rating score alone appears more complicated ...). But on the long run why not have "Best rated" and "Most popular" if we come up with a solution scalable  for large dbs ?

with the method used in the wp plugin, it seems easy and not for large db : just the taking into account this new rating score, the date of insertion -file creation i think? I don't remember which one is what-, number of comments and num of views -maybe also how much user can access-.
The problem will be the update... when we should update a popularity score ? Ideally on each view, comments and rating !

We will discuss about that later and in another thread, when the score rating will be implemented.

About the rating score, when you say

Let's start with no time effect, no permission effect... We'll see later

, I don't agree : rating score should be calculated only with the ratings.

plg wrote:

flop25 wrote:

About the rating score, when you say

Let's start with no time effect, no permission effect... We'll see later

, I don't agree : rating score should be calculated only with the ratings.

I don't see where you disagree with rvelices

"we'll see later" imply it will be study later on for implementation ; I just say "we'll never see" or "we'll see later but not for rating score"

I have an almost finalized version.

It's ok for you if I backport to 2.2? With or without language keys changed ?

Should we display on the picture page the average rate in addition to rating score and number of rates ?

plg wrote:

Visitors won't understand what's the difference between "rating score" and "average rate" so I would only display "rating score" with a tooltip like "rating score includes the ratings this photo received and the number of votes but is not the average rate"

+1

plg wrote:

rvelices, no database column rename? (I'm testing the feature on my local copy before preparing 2.3.0beta3)

not yet because of sqlite. Certainly i wont spend time on this.
It's not the right place for the discussion but I think supporting something else than mysql is not a good idea. nobody does (wp, gallery3 etc...). it's used probably by 0.5% of users and it's a pain in writing optimized queries db upgrades etc...

so I will do it but nothing for sqlite if you are ok.

In my local gallery, I have some photos with rating 5+5 and they have a higher rating score than photos rated only once with a 5 => perfect !