Talk:AdamH Card Ratings

From DominionStrategy Wiki
(Difference between revisions)
Jump to: navigation, search
Line 12: Line 12:
  
 
Hopefully this helps explain my position.
 
Hopefully this helps explain my position.
 +
 +
---
 +
 +
Thanks for your response, AdamH. Could you elaborate on which aspects of your data gathering process make sorting inappropriate? It appears to me that since the same things were asked about each card, it naturally invites comparison. The problems with the KC/Donate example are not that it is a comparison fundamentally, but rather that their scores are so close (likely well within the margin of error) and that it uncritically assumes that higher rated <--> "better". Furthermore, comparison is extremely helpful to contextualize these numbers (what does a rating of 4.53 mean in a vacuum?). Also, there are reasons beyond comparison to want to sort the data--after editing the table to sortable, I immediately used it to check if the data had been rescaled to have the means span from 0-10 or not.
 +
 +
Perhaps a good solution could be to leave the table sortable, but with a disclaimer where you explain the pitfalls of sorting for comparison? Since (by my current understanding) it has valid uses that can improve the utility of the data to users, I am strongly inclined to leave sorting available.
 +
 +
On removal and edit wars, I'm not highly familiar with the norms of this wiki, but I think that entire thing is a more confrontational take than I'd prefer. I believe standard wiki dispute resolution protocol is something like [thoughtful discussion and attempting to reach a compromise] -> [getting outside opinions from other editors] -> [moderated dispute resolution], moving up the chain only if a satisfying solution isn't reached at each prior step, so hopefully no edit war is necessary, haha.
 +
 +
-panama

Revision as of 14:28, 31 January 2019

What is the purpose for making the list not sortable? It's a feature that was requested by multiple others immediately upon the creation of this article, it's not a performance issue, and the default sort is identical to the current arrangement. As far as I can see it's a strict improvement. -panama

---

AdamH: I'll try to explain why I don't think the data should be sortable on this page: let's say there was a button that allowed the user to replace each rating with a random number, that would misrepresent the data -- I feel that sorting cards by rating misrepresents the data in a similar way (though not quite as egregiously).

The data gathered doesn't give a ranking of cards, it gives a rating for each individual card. Comparing cards directly is not something that the data shows, so statements like "King's Court is better than Donate" don't follow from this data even though that's the first thing you see if you sort by mean. The way I gathered data was crafted for a purpose, knowing the limitations of the data, and presenting the data in a way consistent with what the data actually shows is important for its integrity -- putting a sort button in only decreases the integrity of the data.

If people are saying they want a sort button, well, frankly I think they don't understand how to read the data. As someone who is presenting the data, I feel it's my obligation to take whatever measures I can to prevent people from misreading it. Of course people can take the data and sort it using their own tools (and people have done this) and I can't stop them, but I don't want to encourage that. I'd rather make it clear what the data is for and instill an understanding in them why the data doesn't show that.

If "the community" decides that they absolutely want a sort button, of course I'm going to lose an edit war. In that case, I would like for my name to be completely removed from this page because I don't want it shown that I endorse presenting the data in this way.

Hopefully this helps explain my position.

---

Thanks for your response, AdamH. Could you elaborate on which aspects of your data gathering process make sorting inappropriate? It appears to me that since the same things were asked about each card, it naturally invites comparison. The problems with the KC/Donate example are not that it is a comparison fundamentally, but rather that their scores are so close (likely well within the margin of error) and that it uncritically assumes that higher rated <--> "better". Furthermore, comparison is extremely helpful to contextualize these numbers (what does a rating of 4.53 mean in a vacuum?). Also, there are reasons beyond comparison to want to sort the data--after editing the table to sortable, I immediately used it to check if the data had been rescaled to have the means span from 0-10 or not.

Perhaps a good solution could be to leave the table sortable, but with a disclaimer where you explain the pitfalls of sorting for comparison? Since (by my current understanding) it has valid uses that can improve the utility of the data to users, I am strongly inclined to leave sorting available.

On removal and edit wars, I'm not highly familiar with the norms of this wiki, but I think that entire thing is a more confrontational take than I'd prefer. I believe standard wiki dispute resolution protocol is something like [thoughtful discussion and attempting to reach a compromise] -> [getting outside opinions from other editors] -> [moderated dispute resolution], moving up the chain only if a satisfying solution isn't reached at each prior step, so hopefully no edit war is necessary, haha.

-panama

Personal tools
Namespaces

Variants
Views
Actions
Navigation
Toolbox