User Story: As a contributor I'd like to see how often threads get read. Knowing that a thread has been read 3000 times this month means I'm more motivated to get to a solution than when it's only being read by one person. On the individual thread we can add this to the meta data at the top. See http://note.io/10pDZKv On the thread listing page, we can swap it for one of the "me too" counts. I think view count is a better proxy for the severity of the issue. Also, because often times the "me too" votes are too low to distinguish threads from each other even though the "view count" is quite high. Case in point: https://support.mozilla.org/en-US/questions/949205 It has 200 "me too" votes, but about 5500 unique page views.
We're going to have to pull this data from Google Analytics and store it locally in some shape or form.
Whiteboard: u=contributor c=questions p= s=2013.8 → u=contributor c=questions p=3 s=2013.8
Oops, I hit save too quick. I am setting this to 3 pts because: * We need code to pull page views from Google Analytics for questions. * We need to call that code on a daily basis to refresh the counts. * We need to store those numbers somewhere durable. Maybe add a column to the questions table, maybe in a separate table, maybe somewhere else? * We need to display the data. This might need breaking up once we jump into it.
Some concerns: 1- We have 100s of thousands of questions. Do we need to pull page view data for all of them every day? We can probably get paginated results per question, I'm not sure if there is a limit to the # of results we can get though. We are limited to 50,000 API calls per day. 2- New questions will show zero views until next the daily cron job runs. Is that OK? 3- Are we only grabbing unique page views in the last month?
Ricky, all good questions. I should have mentioned here that we'll discuss this in tomorrows KB meeting. I just wanted to have a bug to be able to point to it. I'll bring these questions up tomorrow for sure.
Pending further input: 1- Let's only look at open questions (newer than 180 days) for now. The closed ones are not shown to search engines or in our internal search, so very few people will see that. 2- This sucks, but unless there is a way to get more recent data, I don't see a way around it. 3- Here is what I'm thinking currently: * We should get uniques for last 24 hours and add to our current value. * We should get uniques for the last week to show on the thread listing page. How does this sound?
(In reply to Kadir Topal [:atopal] from comment #5) > How does this sound? *gulp*
I started this but didnt get past making the API calls. About 2pts left I am hoping. Moving to next sprint.
Whiteboard: u=contributor c=questions p=3 s=2013.8 → u=contributor c=questions p=2 s=2013.9
In a pull request: https://github.com/mozilla/kitsune/pull/1350
Deployed to prod. The cron job runs overnight. Hopefully tomorrow we will have some views on the question page \o/ I'll file a new bug about adding the view count to the question listing page. I wasn't exactly sure where to add it and I want to spend some time making sure it doesnt kill our performance more on that page. Also, need to figure out what to do in the case of new questions that don't have a view count until the cron jobs overnight.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Filed bug 872198
(In reply to Kadir Topal [:atopal] from comment #0) > User Story: As a contributor I'd like to see how often threads get read. > Knowing that a thread has been read 3000 times this month means I'm more > motivated to get to a solution than when it's only being read by one person. For the record, there are things suggested in the comments of this bug that didn't get implemented. But the user story provided is satisfied by the solution provided. In the future, please be more specific if you need specific things. I can't guess from anywhere in this bug that sorting is important or having view counts other than total is important. I think the total view count is enough for being a motivation factor. We also need to balance adding everything into kitsune vs being able to use Google Analytics to answer questions. Sorting seems like a feature for the sumo team, and I'm sure all of sumo team has access to google analytics.
I guess we need to talk about these things when there is any doubt. In this case I'm not sure what the weekly "me too" votes are accomplishing. Nobody was using them when I asked during the SUMO platform meeting. That's when we decided to go ahead and replace the "me too" count with the view count. The sorting would be for contributors, ideally you want to work on questions that are not resolved yet and have a high view count this week. Anyway, we can follow up on this in the more comprehensive forum redesign that is planned for Q3.
You need to log in before you can comment on or make changes to this bug.