Anthere wrote:
I totally see the benefit of seeing who has voted what
on a specific
article.
I am more dubious of a sort of reporting set to define how an editor is
generally voting.
There is no way to seperate one from another. In the end, one could
extract the data from the sql-dump (if provided) or extract it from the
web pages and include.
So we are actually talking about "How much frustration is obfuscation
creating?" (apart from: how much work is it to implement
[[Special:Validationcontribution/username]] ?)
* if we report all the articles on which an editor has
been voting :
this allow you to follow how active and beneficial he is to the
community as a "rater" (:-)); it is mostly a measurement of activity and
quite the equivalent of the contribution list.
Right.
* if we give his average voting rate : What is the
benefit of it ? What
information does that bring to you ? Would you consider an editor is
good in his ratings because he gives good notes ? Or would he be good
because he gives bad notes ? He might be one who tries to focus on good
articles to increase their visibility... or he might be one who tries to
focus on bad articles to invite editors to improve them. The information
about his average rate is not an indicator of how good he is in rating
articles
Detecting a systemic bias might indicate issues within the context.
Let's assume one validation topic would be "foo" and user a would always
rate 4/4 where the average rating of that article by all the other users
were significant lower, this might indicate that there was some need for
clearification. Or it might indicate that this user has a different
level of standard. This is nothing bad, it would just be nice to know.
This is actually a feature which does not have to be implemented by
Magnus in the Code itself. Just give an SQL dump every week and someone
might take the data and play with it. You never know.
Hence my interest in asking what will be exactly
displayed.
I would be happy if just the raw data would be provided.
user | revision | timestamp | topic_1_rating | topic_1_comment
topic_2_rating | topic_2_comment
Magnus: This data is stored in the database anyway, right?
Mathias