<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="6.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">F. Harper</style></author><author><style face="normal" font="default" size="100%">D. Raban</style></author><author><style face="normal" font="default" size="100%">S. Rafaeli</style></author><author><style face="normal" font="default" size="100%">J. Konstan</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Predictors of Answer Quality in Online Q&amp;A Sites</style></title><secondary-title><style face="normal" font="default" size="100%">ACM SIGCHI Conference on Human Factors in Computing Systems</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2008</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">http://doi.acm.org/10.1145/1357054.1357191</style></url></web-urls></urls><abstract><style face="normal" font="default" size="100%">&lt;p&gt;Question and answer (Q&amp;amp;A) sites such as Yahoo! Answers are places where users ask questions and others answer them. In this paper, we investigate predictors of answer quality through a comparative, controlled field study of responses provided across several online Q&amp;amp;A sites. Along with several quantitative results concerning the effects of factors such as question topic and rhetorical strategy, we present two high-level messages. First, you get what you pay for in Q&amp;amp;A sites. Answer quality was typically higher in Google Answers (a fee-based site) than in the free sites we studied, and paying more money for an answer led to better outcomes. Second, we find that a Q&amp;amp;A site’s community of users contributes to its success. Yahoo! Answers, a Q&amp;amp;A site where anybody can answer questions, outperformed sites that depend on specific individuals to answer questions, such as library reference services.&lt;/p&gt;</style></abstract></record></records></xml>