Closed Bug 499614 Opened 17 years ago Closed 17 years ago

Add "movers and shakers" to metrics dashboard

Categories

(Mozilla Labs Graveyard :: Personas Plus, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sgupta, Assigned: telliott)

Details

Please determine persona designs that have attracted the highest number of ADUs over the past seven days on a rolling basis. Open to suggestions for other parameters, including a "floor" number of ADUs to be considered a mover and shaker persona design.
From the meeting, it was decided: 1. Eric will get us a good number for the floor numbers for the formula 2. We won't use any weighted average 3. We'll use weekly rolling averages 4. Arrange with toby where that info will sit 5. webdev / client tools implementation of the movers and shakers
The formula we decided on is: [(ThisWeek - LastThreeWeeks) / LastThreeWeeks] Where ThisWeek = avg. #requests over the last 7 days, and LastThreeWeeks = avg. #requests of the 21 days before that. Note that this is not a "7+7" formula; this is to smooth out a little of the noise in the Personas requests. The floor conditions are (ThisWeek > 100) and (LastThreeWeeks > 1). Who is taking control of #4 in Comment #1?
Pedro said he would coordinate with Toby.
I'm now updating a column called 'movers'. That column is currently a INT but should be changed to a float. Toby, can you make that change? it reflects the percentage evolution, eg, a value of 0.5 means 50% increase. Do it on both old and new db. It's still connected to the old database, as I don't have access to the new one yet
Assignee: kkovash → telliott
column changed.
And it's done. Updating popularity and movers nightly to the new server, plus new dashboard done here: https://metrics.mozilla.com/pentaho/content/pentaho-cdf-dd/Render?solution=metrics&path=/weblogs/personas/personas_3&file=personas.wcdf Closing this bug
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: Mozilla Labs → Mozilla Labs Graveyard
You need to log in before you can comment on or make changes to this bug.