29 Mar
2011
29 Mar
'11
2:31 p.m.
Ammar Yasir a écrit :
Thanks
I had a doubt (it might be silly but I thought I should ask). One
important feature of such a data visualization system is that it should
not create confusion or represent something that the data is not.
Consider the movie database example, when a user sees a plot of ratings
vs year / genre vs lanuage, a lot of data points will overlap. So a
lot of data will be hidden from the user at the first sight. What will a
user make out of it? I know we handle such conditions by providing all
the data instances when he clicks on the point but a user might not go
that far. If he is not able to understand the initial plot he might not
continue further ( like not zoom in/click data point). I am just a
little concerned about the usability part and not the functionality.
I don't think that the plot contains all that. In the example I have
seen, the X axis contained "year of release" and the Y axis was for
"popularity level from 1 to 9".
There were buttons at the bottom to select genre but this was not part
of the data points.
--
Marc Delisle
http://infomarc.info