Explaining Recommendations: Design and Evaluation
Explaining Recommendations: Design and Evaluation
复制标题
DOI:
10.1007/978-1-4899-7637-6_10
复制
发表时间:
2015
期刊:
影响因子:
--
通讯作者:
N. Tintarev;Judith Masthoff
中科院分区:
文献类型:
--
作者:
N. Tintarev;Judith Masthoff
In recent years, there has been an increased interest in more user-centered evaluation metrics for recommender systems such as those mentioned in [49]. It has also been recognized that many recommender systems functioned as black boxes, providing no transparency into the working of the recommendation process, nor offering any additional information to accompany the recommendations beyond the recommendations themselves [35].This chapter investigates the role of explanations, such as the one depicted in Fig. 10.1. It is sometimes erroneously assumed that explanations should always justify why items have been recommended. A popular definition of explanation is synonymous with justification. However, to explain also means “to make clear by giving a detailed description”[Oxford concise dictionary]. So, an explanation can be an item description that helps the user to understand the qualities of the item well enough to decide whether it is relevant to them or not. Explanations can serve multiple aims, out which one is transparency: aiming to expose the reasoning and data behind a recommendation. This is the case with some of the explanations hosted on Amazon, such as:“Customers Who Bought This Item Also Bought...”. Explanations can also serve other aims such as helping to inspire user trust and loyalty, increase satisfaction, make it quicker and easier for users to find what they want, and persuade them to try or purchase a recommended item. In this way, we distinguish between different explanation such as eg explaining the way the recommendation engine works (transparency), and explaining why the user may or may not want to try an item (effectiveness). An effective explanation may be