Closed Bug 407742 Opened 12 years ago Closed 9 years ago

Top 10 List should be based on recently popular articles


( :: General, defect)

Not set


(Not tracked)



(Reporter: djst, Assigned: cww)


Instead of basing the top 10 list on total page hits, it should be based on the page hits of the last ten or so days.
Assignee: nobody → nelson
I have been thinking about page hits. I think it makes no sense storing all this hit history info by date in the db. I also cannot simply zero all hits by cron job because that leads to temporary nonsensical rankings. We need a better solution.  Maybe we can do it by votes of usefulness? using the functionality in bug 398786? 
What happens with page hits when we're using proxycaching btw? For that reason alone, it might be worth looking into alternative ways of measuring ranking.

If we're switching to measure ranking based on votes, I think we should use the total number of votes, regardless of score. An article that gets a lot of negative votes should get a higher rank than an article that has only one positive vote and nothing else.
I agree with David. There may be articles that address rare obscure problems, but get a lot of high votes. ('Forgot my master password' comes to mind.)

If we can't use hit count, it needs to be indicative of how many times users have searched for that question.
Target Milestone: --- → 0.6
Nelson, what's the status on this one? 
Target Milestone: 0.6 → ---
Nelson: ping?
Target Milestone: --- → 1.0
The status on this one is that:

1) using hit count is out.

2) using vote count is possible, if this is what you want. We could try it - Eric can implement it.

Otherwise making a manual list based on results from Omniture might actually be a very good low tech solution.
Assignee: nelson → smirkingsisyphus
Target Milestone: 1.0 → 1.1
With the l10n list plugin in bug 481306, we will be able to use that in the front page by just making sure a list is created for the most popular support articles.

The only question is about performance, but I'm guessing the front page is cached anyway?
Priority: -- → P2
The front page uses ob to cache all output, so yes.
Target Milestone: 1.1 → 1.0
Target Milestone: 1.0 → 1.0.2
With the pagelist plugin, this should just be something we change on the wiki right?
Cww/djst which list from the l10n import should be used for this?
the scores table.

The above is the syntax used to generate the list. Prior to testing in the content block, I tested on an actual page:

That worked so I did the content block:

So, the front page is now using the 'scores' list to display the top 10 articles (once the cache refreshes or if you're logged in).

If everything is okay, this can be done on prod independent of the code push.
Closed: 11 years ago
Resolution: --- → FIXED
Can someone (Cheng?) verify this bug, or respond to comment 12?  Thanks!
I've just applied this to <>. Look good to everyone?
It seems superfluous to include the in-product pages in the list on the front page like this. Yes, those pages are popular, but people access them from in-product, not by searching for them.

We might need a new list=>xxx that is a copy of list=>scores but sans in-product pages. Not sure how complicated that would be to add?
Resolution: FIXED → ---
not hard, just need a name for the list and a list of inproduct pages to exclude.
Because the new start page will
Target Milestone: 1.0.2 → 1.3
oops, sorry about that half-sentence. :-) Just ignore it. I'm pushing this to 1.3, so we don't forget it.
What's the status of this?

Does it still need to be assigned to me?
Cheng, in comment 16 you said you need a list of inproduct pages. All inproduct pages should be in the "Linked from in-product" category. Can that be used, or does the list have to be manually created?
Can this
Assignee: smirkingsisyphus → paul.craciunoiu
Target Milestone: 1.3 → 1.4
I meant to say, "Can this move" then I decided that it could :)
Assignee: paul.craciunoiu → jsocol
Target Milestone: 1.4 → 1.5
Assignee: james → cwwmozilla
Is this still open because of comment 15? If not, can we close it?
It's still open. Right now, we are still editing the list manually, and we want it to be automatically generated without including certain articles (i.e. For IE users, Options window - foo panel, etc.).
Don't think this depends on a push. In any case, this can wait and doesn't have to be in 1.5.
Priority: P2 → --
Target Milestone: 1.5 → ---
I don't think this is even still applicable. If there are issues with how we calculate top articles in the new L10n dashboard, please file new bugs.
Closed: 11 years ago9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.