Closed G-White-ISB closed 3 years ago
@G-White-ISB if I recall correctly our today's discussion, we planned to add a text right below the piecharts with the pointer to the documentation, no (cc @wlongabaugh )?
One idea for the text: "This documentation section explains why the charts include items other than the attributes selected in the left panel".
My suggestion is something more conversational, with a glyph that catches the eye, e.g.:
Clicking away for an explanation is annoying. I think we should attempt an explanation in the text so that most people either understand or think they understand without following the link.
"As some attributes have non mutually exclusive values the charts may contain non zero counts for these values even when they are not selected in the left hand panel. See here for a detailed explanation."
OK, how about a mouse over with more text then, plus the link? I am trying to capture attention here with something short and pithy. In my experience, verbose text gets ignored...the "fine print"
True text is usually ignored, but our use case here is someone who is confused by the chart results and is looking for an explanation. If we had text that reveals more text in a mouseover, well it would have to be crystal clear that you could mouseover the initial text.
I'm not crazy about the conversational style but that might just be me. Somehow it reminds me of clippy. I'll make a couple of prototypes for a web app meeting in the new year and we can spend 15 minutes reviewing them.
At least I'm not suggesting eyeballs on a wiggly paperclip 8^D. Might run ideas past the original reviewer? Note I'm not trying to explain the situation in the visible text (too complex), but provide a more noticeable and compelling "hook" to provide the explanation besides a tiny (i) glyph. Thanks.
Issue 4.4 in Tin's test report addressed in this ticket.
Also, issue 4.5
New clarification section for filters returned example, @ulrikew @fedorov
@G-White-ISB I'm wondering if the pie chart shown in the glyph (corresponding to nothing selected) should correspond the the attributes selection (Abdomen selected). I found that somewhat perplexing when trying to understand what was being conveyed.
@wlongabaugh @fedorov Is this considered testing passed? (That glyph is simply a fixed image, it's not a realtime drawing.)
@s-paquette My preference would be to swap in this image instead and then consider it testing passed:
Concur with change proposed in image. Actually I had meant the filter selection to correspond with the pie chart.
@G-White-ISB Are we going to get to this adjustment this Sprint, or should I push this into Sprint 19?
@G-White-ISB Should be able to take the above image and drop it in place. Original file just edited to produce above file.
I can put this in now. George
On Fri, Feb 26, 2021 at 12:33 PM wlongabaugh notifications@github.com wrote:
@G-White-ISB https://github.com/G-White-ISB Should be able to take the above image and drop it in place. Original file just edited.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ImagingDataCommons/IDC-WebApp/issues/506#issuecomment-786879446, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54OR3DBZZK6VPCWDVZVGLTBAASTANCNFSM4VE43EXQ .
In a PR. Nothing else is changed.
On Fri, Feb 26, 2021 at 12:51 PM George White george.white@isbscience.org wrote:
I can put this in now. George
On Fri, Feb 26, 2021 at 12:33 PM wlongabaugh notifications@github.com wrote:
@G-White-ISB https://github.com/G-White-ISB Should be able to take the above image and drop it in place. Original file just edited.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ImagingDataCommons/IDC-WebApp/issues/506#issuecomment-786879446, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN54OR3DBZZK6VPCWDVZVGLTBAASTANCNFSM4VE43EXQ .
I am not a 508 compliance expert, but dark blue on dark grey for the link color does not strike me as good contrast.
@fedorov We can I think make a separate ticket for addressing 508 items such as contrast, so as to minimize scope creep. The new proposed image is now live on idc-testing; does it address the ticket's original concerns?
I thought this belongs to this ticket, since we are introducing a new feature, and my comment was specifically about testing of that new feature. Again, I am not in a position to comment on 508. All I am saying is that the choice of colors in the tooltip for this specific feature implemented in this ticket is suboptimal.
@fedorov We generally try to keep 508 compliance in its own ticket or tickets, because those changes are often small tweaks which are best done en masse rather than issue by issue. (Also because we run the test as a separate pass.)
An external reviewer noted issues with the correlation between the search results graph and the search configuration box. For instance when just the Abdomen BodyPartExamined value is selected, four different values, Abdomen, Headneck, Chest, and None appear in the Body Part Examined pie chart. This behavior is known and expected. The attribute are faceted by CaseIDs, and the same CaseID may match several different values of the same attribute. Hovering over the two information icons in the panels yields some explanatory text. We realize the users could easily miss these icons or not understand they are actionable. We are exploring better ways to explain these issues to the user.