Open chloeatplay opened 11 years ago
Some first passes on tracking stats like the one requested above. This will show on top of the Review Queue.
1) Progress Bar tracking against goals such as Revieweing 1K Badges etc. Those get updated when reached and a mentor badge is assigned Scenario 1: you re doing well and reaching your goal Scenario 2: You re lame and running behind (jess note: just experimenting with our color palette here, preferences?) 2) Simple progress bar that just tracks progress made by comparing badges remaining to be reviewed versus badges reviewed in a day 3) The super pack edition: What Nichole is asking in the note above plus 1&2; a little panel showcasing how many badges have been reviewed each day, how many remaining for review, the total number of badges reviewed and a progress bar tracking your goals as mentors, i.e. 1.5K badges
cc @toolness & @iamjessklein @cmcavoy :fire: away your feedback :v:
Nice! Is the 1K/1.5K goal something that's fairly static? Can we have it be something that's set by the system administrator or something? My main concern is that making an admin panel for setting goals will take time, but the rest of the stuff doesn't seem like it'd be that hard to bust up.
Great point @toolness I was thinking the same :bulb: ==> maybe its a formula that sets dynamic goals i.e. like average badges reviewed per day multiplied by 10 (so something that would take approx 10 days to achieve) to set goal1. Then goal2 would be =goal1+ 10x (number of average reviewed badges). These would get updated when each goal is achieved. Eventually they could get harder like goal5= goal4+ 15x (number of average reviewed badges) The final numbers could be rounded up to the closest full one, so if 134=> 130 etc.
@chloeatplay looking good. I would have to see these in context to know for sure, but I am leaning towards the teal one. The legibility could be improved a bit by bumping up the contrast. In general, I like the palette that you are playing with, it will complement nicely with the rainbow comments.
Re: @toolness point : For aestimia it feels like the head mentor should be setting the goal in this use case (like Nichole). However for the modular version of the tool, it would be neat to have the mentor be able to set the goal like @chloeatplay is suggesting.... or maybe there's a "my goal is to complete x # of assessments in x # of weeks" kind of like the running goals in Nike + (requisite screenshots below for future iteration): Pick the goal type:
Set # of times you want to run:
Set how long goal lasts:
Set name for goal:
Goal Progress bar action shot:
Is there a way we can split this into two separate features--one that shows the statistics, and another that adds the goal functionality? That would make it easier to iterate on this, I think.
@toolness :thumbsup: yes makes sense, i ll iterate on this today :) @iamjessklein thanks for the feedback, pallete follows your UI designs for this page. Re: goals==> I think that setting goals ala nike plus is not sthg that we should integrate in such a great level in aestemia at this phase, since this is just the assessment site- so i don't want to overwhelm mentors with things to do, I d still like them to have some tiny motivation, like with common goals but overall make it a fast and fun experience. I think what you are talking about will fit nicely in the backpack :)
Ok, I've just added a super janky implementation of a stats dashboard in 460449c40db53c20c411aa122a9b3d437c6f355f. The review queue page now features this at the top:
Obviously not ideal, but it's a start. Most importantly, though, does it show the right information?
Nice! I would remove the last one (submissions today needing assessment) as the queue favors the ones that have been waiting the longest.
Hmm, but the original problem (at the top of this ticket) says
... the number of submissions waiting to be assessed (overall, day) ...
IIRC, it was so they could know when to scale up/down the number of mentors attending to the submissions or something, but I'm not sure.
Here is an integration of the stats based on #18
Problem: "Can we see the number of submissions waiting to be assessed(overall, day), number assessed (overall, day)?"