Open rtibbles opened 10 years ago
rtibbles
commented
10 years ago @wangguan59 @kennahasson Would love your input/ideas on this issue. See #1725 as a first pass of a redesign of one item.
Also, can someone ping Josh? I don't know his github handle.
ghost
commented
10 years ago @jdklein
I know all of these things have been mentioned before, but here's my input on them...
I think it's extremely important to have the data points afford clicking. Maybe changing the color, or giving them a border/gradient to look more similar to a radio button. Right now it's unclear they display more information unless the user randomly clicks the buttons.
Another idea is having small arrows above each point, like on a map. It's always obvious that points are clickable on a map because of this, but could also be misleading in a graph. Just a thought!
Also, putting 'Bored' and 'Mastery', etc. directly in the quadrants of the graph might be tricky when there are more data points. Making a basic key that went along with the axis blurb, may be helpful in those situations and could simplify the display at first glance. Should be formatted similar to the way the axis key is made. Possibly something similar to this, but without labeling the quadrants Q1,Q2?
ghost
commented
10 years ago I also think the button 'View Report' is not very prominent. It's almost running into the list of reports and just separating it by one line would make it more salient.
Might be helpful to have it change colors once a topic is selected and report is viewable (discovered today that not all heading topics are viewable... selecting 'Math' will not generate a report, must specify something more specific). It currently remains gray whether or not a working report has been selected.
ghost
commented
10 years ago Good points, Kenna. Definitely agree that "View Report" could use some work. Subjects should be unable to be checked if there are no reports available for that subject. "View Report" button itself could be made gray/unclickable if no subject is selected, turn green when subjects can be selected for viewing, perhaps be red if too many subjects are selected (or prohibit this entirely by not allowing checkboxes to be checked after a certain amount of subjects have been selected, not sure what the hard limit is on this).
As we progress forward, would definitely love to see us going in the direction of the link mentioned in #1748 (above, or here: https://www.edsurge.com/n/2014-03-19-endangered-report-cards). The 4-quadrant mastery graph is definitely an improvement, but being able to compare multiple circular/linear diagrams across multiple subjects at the same time would be great as well. Attached is a sketch based on the first image in the link (apologies, forgot my mouse today). Jamie informed me we might have issues with screen resolution on smaller devices, didn't account for that when creating this.
mjptak
commented
10 years ago You mean Pearson hasn't Trademarked the circle? (Just dumped $300 into participant observing at their testing center) Anyway as you are all working your magic on the coach (and self assessment) reports it is worth taking a gander at ALECKS (no not ALEC). I always noticed similarities between their reports and the dual circles that KA uses (one for video and othe other for exercises). I think KA has gone it a little different direction as the number of granular things to stick in the "mastery report" has grown.
rtibbles
commented
10 years ago Another idea here is 'alerts' to show more salient, timely information - such as students struggling recently and needing intervention.
Feature Name: Redesign of coach reports
Team members: @rtibbles @christinepham
Need more!
PR reviewer: @jtamiace or @66eli77 for front end code, @MCGallaspy or @benjaoming for back end code.
Description:
Refactor and reimplement coach reports to provide a more immediate and deeper experience for the user.
Key features will include:
This work will begin with a refactor of the existing tabular coach report to be rendered in Backbone/Handlebars and driven by an API endpoint.
The next step will be to implement a new landing page based on the work of @sethachoi and Mikaela Oen. This will be the place for the aggregated recent activity data to be displayed.
Every display of learner data will be amenable to clicking to produce a more detailed display of the user data shown (whether it is learner activity on the aggregate page, learner progress on the tabular report, or items on the real time display).
Milestones: April 10 - Refined mockups of each of the new interfaces. April 17 - Submit refactoring of tabular report for PR. April 24 - PR for implementation of activity aggregation endpoint. First pass implementation of learner data detail endpoint. May 1 - PR for Coach landing page/aggregate view. Embeddable view for learner data detail. May 8 - PR for first pass implementation of push API. May 15 - Opening PRs for live interface. May 23 - Efficiency testing of aggregation engine complete - target: Run well on a Raspberry Pi. May 26 - PRs merged.