<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The Unfairness of Popularity Bias in Recommendation∗</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Himan Abdollahpouri</string-name>
          <email>himan.abdollahpouri@colorado.edu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Robin Burke</string-name>
          <email>robin.burke@colorado.edu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Masoud Mansoury</string-name>
          <email>m.mansoury@tue.nl</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bamshad Mobasher</string-name>
          <email>mobasher@cs.depaul.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>DePaul University</institution>
          ,
          <addr-line>Chicago</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Eindhoven University of Technology</institution>
          ,
          <addr-line>Eindhoven</addr-line>
          ,
          <country country="NL">Netherlands</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Colorado Boulder</institution>
          ,
          <addr-line>Boulder</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Recommender systems are known to sufer from the popularity bias problem: popular (i.e. frequently rated) items get a lot of exposure while less popular ones are under-represented in the recommendations. Research in this area has been mainly focusing on finding ways to tackle this issue by increasing the number of recommended long-tail items or otherwise the overall catalog coverage. In this paper, however, we look at this problem from the users' perspective: we want to see how popularity bias causes the recommendations to deviate from what the user expects to get from the recommender system. We define three diferent groups of users according to their interest in popular items (Niche, Diverse and Blockbuster-focused) and show the impact of popularity bias on the users in each group. Our experimental results on a movie dataset show that in many recommendation algorithms the recommendations the users get are extremely concentrated on popular items even if a user is interested in long-tail and non-popular items showing an extreme bias disparity.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>Recommender systems have been widely used in a variety of
diferent domains such as movies, music, online dating etc. Their goal is
to help users find relevant items which are dificult or otherwise
time-consuming to find in the absence of such systems.</p>
      <p>Diferent types of algorithms are being used for recommendation
depending on the domain or other constraints such as the
availability of the data about users or items. One of the most widely-used
classes of algorithms for recommendation is collaborative filtering.
In these algorithms the recommendations for each user are being
generated using the rating information from other users and items.
Unlike other types of algorithms such as content-based
recommendation, collaborative algorithms do not use the content information.</p>
      <p>
        One of limitations of collaborative recommenders is the problem
of popularity bias [
        <xref ref-type="bibr" rid="ref1 ref7">1, 7</xref>
        ]: popular items are being recommended too
∗Copyright 2019 for this paper by its authors. Use permitted under Creative Commons
License Attribution 4.0 International (CC BY 4.0).
      </p>
      <p>Presented at the RMSE workshop held in conjunction with the 13th ACM Conference
on Recommender Systems (RecSys), 2019, in Copenhagen, Denmark.
frequently while the majority of other items do not get the deserved
attention.</p>
      <p>
        Popularity bias could be problematic for a variety of diferent
reasons: Long-tail (non-popular) items are important for generating
a fuller understanding of users’ preferences. Systems that use active
learning to explore each user’s profile will typically need to present
more long tail items because these are the ones that the user is less
likely to have rated, and where user’s preferences are more likely
to be diverse [
        <xref ref-type="bibr" rid="ref16 ref18">16, 18</xref>
        ].
      </p>
      <p>
        In addition, long-tail recommendation can also be understood
as a social good. A market that sufers from popularity bias will
lack opportunities to discover more obscure products and will be,
by definition, dominated by a few large brands or well-known
artists [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Such a market will be more homogeneous and ofer
fewer opportunities for innovation and creativity.
      </p>
      <p>In this paper, however, we look at the popularity bias from a
diferent perspective: the users’. Look at figure 1 for example: the
user has rated 30 long-tail (non-popular) items and 70 popular items.
So it is reasonable to expect the recommendations to keep the same
ratio of popular and non-popular items. However, most of the
recommendation algorithms produce a list of recommendations that is
over-concentrated on popular items (often it is even close to 100%
popular items). In this paper, we show how diferent
recommendation algorithms are propagating this bias diferently for diferent
users. In particular, we define three groups of users according to
their degree of interest towards popular items and show the bias
propagation for some groups is higher than the others. For instance,
the niche users (users with the lowest degree of interest towards
popular items) are afected the most by this bias. We also show these
niche users and, in general users with lower interest in popular
items, are more active (they have rated more items) in the system
and therefore they should be considered as important stakeholders
whose needs should be addressed properly by the recommender
system. However, looking at several recommendation algorithms,
we see these users are not getting the type of recommendations that
they expect to get. In summary, here are the important research
questions we would like to answer in this paper:
• RQ1: How much are diferent individuals or groups of users
interested in popular items?
• RQ2: How do algorithms’ popularity biases impact users
with diferent degrees of interest in popular items?
To answer these questions we look at the movieLens 1M dataset
and analyze the users’ profiles in terms of their rating behavior. We
also compare several recommendation algorithms with respect to
their general popularity bias propagation and the extent to which
this bias propagation is afecting diferent users.
2</p>
    </sec>
    <sec id="sec-2">
      <title>RELATED WORK</title>
      <p>
        The problem of popularity bias and the challenges it creates for the
recommender system has been well studied by other researchers
[
        <xref ref-type="bibr" rid="ref17 ref6 ref8">6, 8, 17</xref>
        ]. Authors in the mentioned works have mainly explored the
overall accuracy of the recommendations in the presence of
longtail distribution in rating data. Moreover, some other researchers
have proposed algorithms that can control this bias and give more
chance to long-tail items to be recommended [
        <xref ref-type="bibr" rid="ref14 ref3 ref4 ref5">3–5, 14</xref>
        ].
      </p>
      <p>
        In this work, however, we focus on the fairness of
recommendations with respect to users’ expectations. That is, we want to see
how popularity bias in the input data is causing the
recommendations to deviate from the actual interests of users with respect to
how many popular items they expect to see in the recommended list.
We call this deviation unfair because it is caused by the existing bias
in data and also the algorithmic bias in some of the recommendation
algorithms. A similar work to ours is [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] where author proposed
the idea of calibration: the recommendations should be consistent
with the spectrum of items a user has rated. For example, if a user
has rated 70% action movies and 30% romance, it is expected to see
the same pattern in the recommendations. Our work is diferent
as we do not use content information to see how diferent
algorithms are calibrated. In fact, Our work could be considered as an
explanation for the problem discussed relative to genre calibration,
namely that genre distortion in recommendations could be caused
by diferent levels of popularity across genres.
      </p>
      <p>
        Moreover, the concept of fairness in recommendation has been
also gaining a lot of attention recently [
        <xref ref-type="bibr" rid="ref13 ref20">13, 20</xref>
        ]. For example, finding
solutions that removes algorithmic discrimination against users
belong to a certain demographic information [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] or making sure
items from diferent categories (e.g. long tail items or items belong
to diferent providers)[
        <xref ref-type="bibr" rid="ref15 ref9">9, 15</xref>
        ] are getting a fair exposure in the
recommendations. Our definition of fairness in this paper is more
related to the calibration fairness [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] which means users should
get the recommendations that are close to what they are expecting
to get based on the type of items they have rated.
      </p>
      <p>
        And finally, Jennach et al. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] compared diferent
recommendation algorithms in terms of accuracy and popularity bias. In that
paper they observed some algorithms concentrate more on popular
items than the others. In our work, we are mainly interested in
seeing the popularity bias from the users’ expectations perspective.
      </p>
    </sec>
    <sec id="sec-3">
      <title>POPULARITY BIAS IN DATA</title>
      <p>
        For all of the following sections we use the MovieLens 1M dataset
for our analysis which contains 1,000,209 anonymous ratings of
approximately 3,900 movies made by 6,040 MovieLens users [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>Rating data is generally skewed towards more popular items–
there are a few popular items with thousands of ratings and the
other majority of the items combined have fewer ratings than those
few popular ones. Figure 2 shows the long-tail distribution of item
popularity in the famous MovieLens 1M dataset but the same
distribution can be seen in other datasets as well.</p>
      <p>Due to this imbalance property of the rating data, often
algorithms inherit this bias and, in many cases, increase it by
overrecommending the popular items and, therefore, giving them a
higher opportunity of being rated by more users and, as a result,
making them rated by more users and this goes on again and again–
the rich get richer and the poor get poorer.</p>
      <p>
        That by itself is very problematic and needs to be addressed
using proper algorithms. However, what is often ignored is the
fact that there are many users who are actually interested in
nonpopular items and they expect to get recommendations beyond
some extremely popular items and blockbusters. What is worth
noting is that users in a recommender system platform all should
be considered as diferent stakeholders and their satisfaction should
be taken care of by the algorithm [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. An algorithm that is only
capable of addressing the needs of a certain group of users (those
whose interest is primarily concentrated on popular items) will be
in the risk of losing the interest of the rest of the users if their needs
are not taken care of.
      </p>
      <p>In this paper we compare several recommendation algorithms
and see how they perform in terms of keeping the ratio of popular
and non-popular items according to what the users expect from
the recommendations (i.e. the same ratio in their profile)
3.1</p>
    </sec>
    <sec id="sec-4">
      <title>User Propensity for Popular Items</title>
      <p>As we mentioned earlier, there might be users who are interested
in non-popular items and therefore the recommender algorithm
should be able to address the needs of those users as well. In this
section, we analyze the degree of interest that diferent types of
users have towards popular items. Figure 3 shows the ratio of
popular items in the users’ profiles.</p>
      <p>The users have been sorted first based on the ratio of popular
items in their profile then the data has been plotted. We can see
that more than 4000 users are actually interested in at least 20%
non-popular items (from x-axis 0 to 4000). Even the other 2000
users also have some interest in non-popular items as the ratio of
popular items, except for a dozen of users, is still between 80% and
100% meaning there is around 10-20% non-popular items in their
profile.
3.2</p>
    </sec>
    <sec id="sec-5">
      <title>Users Profile Size and Popularity Bias</title>
      <p>Before going any further, we want to see if a user’s profile size
has any correlation with the number of popular items she has
in her profile. In this paper, we define an item to be popular if
its popularity value falls within the top 20% of item popularities.
Figure 4-a shows a strong correlation between profile size and the
number of popular items in users’ profile which is kind of obvious
due to the fact that having more items in a user’s profile increases
the likelihood of observing a popular item in it. So, we also show
the correlation between the ratio of popular items in users’ profiles
and the profile size. Figure 4-b shows this correlation is negative
meaning the larger the profile size, the smaller the ratio of popular
items is in a user’s profile. This efect is to be expected. There are
a small number of popular items. As a user’s profile gets larger,
they will eventually run out of popular items to rate and therefore
must include more and more non-popular items. Figure 4-c shows
another perspective of popularity of the rated items in users’ profile
which is the average popularity of the rated items by each user. The
popularity of each item is simply the ratio of users who have rated
that item. Again in this figure we can see a negative correlation
between prolfie size and the average popularity of rated items by a
user indicating the more items a user has rated (larger profile size)
the smaller the average popularity of her rated items is.</p>
      <p>These results provide interesting insights about users with lower
propensity to rate popular items: these users also tend to interact
with the system more and provide more ratings. Therefore, they
tend to have a more profound efect on the performance of the
recommender system and their contributions should not be ignored.
(a) Correlation of profile size and the number of popular items
in user profile
(b) Correlation of profile size and the ratio of popular items
in user profile
(c) Correlation of profile size and the average popularity of
items in user profile</p>
    </sec>
    <sec id="sec-6">
      <title>DIFFERENT GROUPS OF USERS IN TERMS</title>
    </sec>
    <sec id="sec-7">
      <title>OF PROPENSITY FOR POPULARITY</title>
      <p>In this section, we want to define three groups of users based on
the ratio of popular items in their profile. That is, how interested
they are in popular items.</p>
      <p>• Niche Users (N): These are the bottom 20% of users in terms
of the ratio of popular items in their profile. For these users,
More than half of their profile consists of non-popular
(longtail) items.</p>
      <p>(a) The number of users in each group
(b) The average profile size in diferent user groups
• Blockbuster-focused Users (B): These are the top 20% of
users in terms of the ratio of popular items in their profile.
These users, on average, have more than 85% popular items
in their profile.
• Diverse Users (D): These are the users that are not Niche
neither are they Blockbuster-focused. So the rest of the users
fall within this category.</p>
    </sec>
    <sec id="sec-8">
      <title>ALGORITHMIC PROPAGATION OF</title>
    </sec>
    <sec id="sec-9">
      <title>POPULARITY BIAS</title>
      <p>As we observed in previous section, there is a bias in the rating data:
certain items are rated very frequently while many others are rated
by fewer users. In this section, we show how diferent
recommendation algorithms propagate this bias into their recommendations.
We first look at their general performance without paying attention
to how they perform for diferent users or groups of users. We
tested several algorithms including User KNN, Item KNN, SVD++
and Biased Matrix factorization for our experiments. For all these
algorithms we set aside 80% of the rating data as training set and
the remaining 20% as the test set. For each user in test set, a list
of 10 items are recommended. Moreover, we tuned all these
algorithms so they can achieve a similar precision (around 0.1) for a fair
comparison of their popularity bias propagation. In addition, we
also used two simple Most popular and Random algorithms. Figure 6
shows the correlation between the number of times an item is rated
and the number of times it is recommended by diferent algorithms.</p>
      <p>It can be seen that in all algorithms except for the random there
are many items that are almost never recommended (the items
fall on the horizontal tail of the scatter plot). In addition, the Most
popular algorithm seems to have the strongest correlation between
the number of times an item is being rated and the number of times
it is recommended, as it was expected, followed by User KNN and
Item KNN which also have a strong correlation. Looking at the
plot for the Biased MF algorithm, it seems there is not a significant
correlation between how often an item is rated and how often it is
recommended. Nevertheless, its very sparse scatter plot shows the
number of recommended items is still low. In this algorithm there
are a lot of items that are recommended very rarely (even some of
the ones that are rated more frequently) while some few items are
being recommended more frequently. SVD++ also shows a positive
correlation between the number of times an item is rated and is
recommened. The random algorithm obviously does not show any
correlation between the number of times an item is rated and the
number of times it is recommended. For each point on the scatter
plot, you can also see the average rating for the corresponding item
to illustrate the quality of these recommended items using each
algorithm.
5.1</p>
    </sec>
    <sec id="sec-10">
      <title>Popularity Bias of Recommendations in</title>
    </sec>
    <sec id="sec-11">
      <title>Diferent User Groups</title>
      <p>In this part, we want to look at how these diferent algorithms
perform in terms of keeping the right ratio of popular and
nonpopular items recommended to diferent user groups according to
their expected value of such ratio.</p>
      <p>Figure 7 shows the ratio of popular items in the profiles of users
in diferent groups versus the ratio of popular items in their
recommendations. As you can see, for all algorithms except for random,
the ratio of popular items in the recommendations is significantly
increased for all user groups confirming how these algorithms
impose popularity on users. Specifically, the Niche users are seeing
the largest discrepancy of such ratio imposed by the algorithms.
However, the recommendations generated by SVD++ seem to be
more consistent with what the users expect to get in terms of the
right ratio of popular and non-popular items.
(a) Biased MF
(b) SVD++
(c) Item KNN
(d) User KNN
(e) Random
(f) Pop</p>
      <p>In addition, we define the Group Average Popularity (GAP (g))
metric that measures the average popularity of items in the profiles
of users in a certain group g or their recommendation lists. If we
look at the recommendations given to a group of users then GAP
measures the average popularity of the recommended items to the
users in that group. On the other hand, if we look at the users’
profiles, then GAP measures the average popularity of the items
rated by the users in that group.</p>
      <p>GAP (д) =</p>
      <p>Pu ∈д</p>
      <p>Pi∈pu ϕ(i)</p>
      <p>|pu |
|д|
were g is the group of users (in our case it is either N, D or B).
ϕ(.) is the popularity of a certain item (i.e. the number of times it is
rated divided by the total number of users) and pu is the list of items
in the profile of user u. We represent the GAP value in user profiles
as GAPp and the GAP for recommendations by GAPr . For each
recommendation algorithm, We measure the change in GAP which
is the amount of unwanted popularity in the recommendations
imposed by the algorithms to each group. The value of ∆ GAP = 0
means a fair representation of users’ preferences towards item
popularity in the recommendations.</p>
      <p>∆ GAP (д) =</p>
      <p>GAP (д)r − GAP (д)p</p>
      <p>GAP (д)p</p>
      <p>Figure 8 shows the change in the group average popularity
(∆ GAP ) in diferent groups using diferent algorithms. Most popular
algorithm imposes the highest positive change in GAP followed
by item KNN. Random has negative ∆ GAP meaning the
recommendations on average are less popular compared to the average
popularity of users profiles in each group. We can also see that the
niche users have the largest ∆ GAP for all algorithms.</p>
      <p>These results show the unfair nature of popularity bias in the
recommendations and how its efect on diferent users varies based
on how interested the users are in popular items.</p>
    </sec>
    <sec id="sec-12">
      <title>6 DISCUSSION</title>
      <p>In this section we would like to summarize the answers we found
to the research questions we listed in section 1.
(1)
(2)
• Answer to RQ1: Our analysis showed that indeed not
everyone has the same level of interest in popular items. We
found that there are large number of users who are also
interested in non-popular items and expecting to get some
of those as recommendations. We showed that users with
larger profiles are typically less likely to have exclusively
rated popular items and they do have some interest in
longtail or non-popular items.
• Answer to RQ2: Our results showed that the
recommendations generated by all the algorithms were extremely unfair
to users with lesser interest in popular items as almost all the
recommendations they received were popular items. That
showed not every user is afected by the popularity bias the
same as other users.</p>
    </sec>
    <sec id="sec-13">
      <title>7 CONCLUSION AND FUTURE WORK</title>
      <p>Due to the popularity bias in rating data, many recommendation
algorithms propagate this bias even further by recommending
popular items more frequently while not giving enough exposure to
less popular ones. In this paper, we investigated the popularity bias
from a diferent point of view: the user’s perspective. We showed
that even though there are many users who are interested in getting
some non-popular items, they almost do any get any of those in
their recommendations. We further defined three groups of users
(niche, diverse and Blockbuster-focused) based on the level of their
interest towards popular items. We observed that all algorithms
recommend items that are much more popular than what the users
in those groups have rated. Especially the niche users get really
inappropriate recommendations when the level of popularity of
the recommendations is compared to what they are interested in.
For future work, we will use more datasets for our analysis. We
also want to investigate other measures of satisfaction for diferent
user groups such as how relevant their recommendations are, how
diverse they are etc.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Himan</given-names>
            <surname>Abdollahpouri</surname>
          </string-name>
          .
          <year>2019</year>
          .
          <article-title>Popularity Bias in Ranking and Recommendation</article-title>
          . In In AAAI/ACM Conference on AI,
          <string-name>
            <surname>Ethics</surname>
          </string-name>
          , and
          <string-name>
            <surname>Society</surname>
          </string-name>
          (AIES'19)
          <string-name>
            <surname>January</surname>
          </string-name>
          27-
          <issue>28</issue>
          ,
          <year>2019</year>
          , Honolulu,
          <string-name>
            <surname>HI</surname>
          </string-name>
          , USA. ACM.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Himan</given-names>
            <surname>Abdollahpouri</surname>
          </string-name>
          , Gediminas Adomavicius, Robin Burke, Ido Guy, Dietmar Jannach, Toshihiro Kamishima, Jan Krasnodebski, and
          <string-name>
            <given-names>Luiz</given-names>
            <surname>Pizzato</surname>
          </string-name>
          .
          <year>2019</year>
          . Beyond Personalization: Research Directions in Multistakeholder Recommendation. arXiv preprint arXiv:
          <year>1905</year>
          .
          <year>01986</year>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Himan</given-names>
            <surname>Abdollahpouri</surname>
          </string-name>
          , Robin Burke, and
          <string-name>
            <given-names>Bamshad</given-names>
            <surname>Mobasher</surname>
          </string-name>
          .
          <year>2017</year>
          .
          <article-title>Controlling Popularity Bias in Learning to Rank Recommendation</article-title>
          .
          <source>In Proceedings of the 11th ACM conference on Recommender systems. ACM</source>
          ,
          <volume>42</volume>
          -
          <fpage>46</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Himan</given-names>
            <surname>Abdollahpouri</surname>
          </string-name>
          , Robin Burke, and
          <string-name>
            <given-names>Bamshad</given-names>
            <surname>Mobasher</surname>
          </string-name>
          .
          <year>2019</year>
          .
          <article-title>Managing Popularity Bias in Recommender Systems with Personalized Re-ranking.</article-title>
          .
          <source>In Florida AI Research Symposium (FLAIRS)</source>
          . ACM, To appear.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Gediminas</given-names>
            <surname>Adomavicius and YoungOk Kwon</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Improving Aggregate Recommendation Diversity Using Ranking-Based Techniques</article-title>
          .
          <source>IEEE Transactions on Knowledge and Data Engineering</source>
          <volume>24</volume>
          ,
          <issue>5</issue>
          (
          <year>2012</year>
          ),
          <fpage>896</fpage>
          -
          <lpage>911</lpage>
          . https://doi.org/10.1109/ TKDE.
          <year>2011</year>
          .15
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Chris</given-names>
            <surname>Anderson</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>The long tail: Why the future of business is selling more for less</article-title>
          .
          <source>Hyperion.</source>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Erik</given-names>
            <surname>Brynjolfsson</surname>
          </string-name>
          , Yu Jefrey Hu, and
          <string-name>
            <given-names>Michael D</given-names>
            <surname>Smith</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>From niches to riches: Anatomy of the long tail</article-title>
          .
          <source>Sloan Management Review</source>
          <volume>47</volume>
          ,
          <issue>4</issue>
          (
          <year>2006</year>
          ),
          <fpage>67</fpage>
          -
          <lpage>71</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Erik</given-names>
            <surname>Brynjolfsson</surname>
          </string-name>
          , Yu Jefrey Hu, and
          <string-name>
            <given-names>Michael D</given-names>
            <surname>Smith</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>From niches to riches: Anatomy of the long tail</article-title>
          .
          <source>Sloan Management Review</source>
          (
          <year>2006</year>
          ),
          <fpage>67</fpage>
          -
          <lpage>71</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Robin</given-names>
            <surname>Burke</surname>
          </string-name>
          , Nasim Sonboli, Masoud Mansoury, and
          <string-name>
            <surname>Aldo</surname>
          </string-name>
          Ordoñez-Gauger.
          <year>2017</year>
          .
          <article-title>Balanced Neighborhoods for Fairness-aware Collaborative Recommendation</article-title>
          . In Workshop on Responsible Recommendation (FATRec).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Òscar</given-names>
            <surname>Celma</surname>
          </string-name>
          and
          <string-name>
            <given-names>Pedro</given-names>
            <surname>Cano</surname>
          </string-name>
          .
          <year>2008</year>
          .
          <article-title>From hits to niches?: or how popular artists can bias music recommendation and discovery</article-title>
          .
          <source>In Proceedings of the 2nd KDD Workshop on Large-Scale Recommender Systems and the Netflix Prize Competition . ACM</source>
          ,
          <volume>5</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>F Maxwell</given-names>
            <surname>Harper and Joseph A Konstan</surname>
          </string-name>
          .
          <year>2015</year>
          .
          <article-title>The MovieLens Datasets: History and Context</article-title>
          .
          <source>ACM Transactions on Interactive Intelligent Systems (TiiS) 5</source>
          ,
          <issue>4</issue>
          (
          <year>2015</year>
          ),
          <fpage>19</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Dietmar</surname>
            <given-names>Jannach</given-names>
          </string-name>
          , Lukas Lerche, Iman Kamehkhosh, and
          <string-name>
            <given-names>Michael</given-names>
            <surname>Jugovac</surname>
          </string-name>
          .
          <year>2015</year>
          .
          <article-title>What recommenders recommend: an analysis of recommendation biases and possible countermeasures</article-title>
          .
          <source>User Modeling and User-Adapted Interaction 25</source>
          ,
          <issue>5</issue>
          (
          <year>2015</year>
          ),
          <fpage>427</fpage>
          -
          <lpage>491</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Toshihiro</surname>
            <given-names>Kamishima</given-names>
          </string-name>
          , Shotaro Akaho, Hideki Asoh, and
          <string-name>
            <given-names>Jun</given-names>
            <surname>Sakuma</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>Fairness-aware Classifier with Prejudice Remover Regularizer</article-title>
          .
          <source>In Proc. of the ECML PKDD</source>
          <year>2012</year>
          ,
          <string-name>
            <surname>Part</surname>
            <given-names>II</given-names>
          </string-name>
          .
          <fpage>35</fpage>
          -
          <lpage>50</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Toshihiro</surname>
            <given-names>Kamishima</given-names>
          </string-name>
          , Shotaro Akaho, Hideki Asoh, and
          <string-name>
            <given-names>Jun</given-names>
            <surname>Sakuma</surname>
          </string-name>
          .
          <year>2014</year>
          .
          <article-title>Correcting Popularity Bias by Enhancing Recommendation Neutrality</article-title>
          .
          <source>In Poster Proceedings of the 8th ACM Conference on Recommender Systems, RecSys</source>
          <year>2014</year>
          ,
          <string-name>
            <given-names>Foster</given-names>
            <surname>City</surname>
          </string-name>
          , Silicon Valley, CA, USA, October 6-
          <issue>10</issue>
          ,
          <year>2014</year>
          . http://ceur-ws.
          <source>org/</source>
          Vol-
          <volume>1247</volume>
          / recsys14_poster10.pdf
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>Weiwen</given-names>
            <surname>Liu</surname>
          </string-name>
          and
          <string-name>
            <given-names>Robin</given-names>
            <surname>Burke</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <article-title>Personalizing Fairness-aware Re-ranking</article-title>
          . arXiv preprint arXiv:
          <year>1809</year>
          .
          <volume>02921</volume>
          (
          <year>2018</year>
          ).
          <source>Presented at the 2nd FATRec Workshop held at RecSys</source>
          <year>2018</year>
          , Vancouver, CA.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>Tien</surname>
            <given-names>T Nguyen</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pik-Mai Hui</surname>
            ,
            <given-names>F Maxwell</given-names>
          </string-name>
          <string-name>
            <surname>Harper</surname>
          </string-name>
          ,
          <source>Loren Terveen, and Joseph A Konstan</source>
          .
          <year>2014</year>
          .
          <article-title>Exploring the filter bubble: the efect of using recommender systems on content diversity</article-title>
          .
          <source>In Proceedings of the 23rd international conference on World wide web. ACM</source>
          ,
          <volume>677</volume>
          -
          <fpage>686</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Yoon-Joo Park</surname>
            and
            <given-names>Alexander</given-names>
          </string-name>
          <string-name>
            <surname>Tuzhilin</surname>
          </string-name>
          .
          <year>2008</year>
          .
          <article-title>The long tail of recommender systems and how to leverage it</article-title>
          .
          <source>In Proceedings of the 2008 ACM conference on Recommender systems. ACM</source>
          ,
          <volume>11</volume>
          -
          <fpage>18</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>Paul</given-names>
            <surname>Resnick</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R Kelly</given-names>
            <surname>Garrett</surname>
          </string-name>
          , Travis Kriplean,
          <article-title>Sean A Munson,</article-title>
          and Natalie Jomini Stroud.
          <year>2013</year>
          .
          <article-title>Bursting your (filter) bubble: strategies for promoting diverse exposure</article-title>
          .
          <source>In Proceedings of the 2013 conference on Computer supported cooperative work companion. ACM</source>
          ,
          <volume>95</volume>
          -
          <fpage>100</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Harald</given-names>
            <surname>Steck</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <article-title>Calibrated recommendations</article-title>
          .
          <source>In Proceedings of the 12th ACM Conference on Recommender Systems. ACM</source>
          ,
          <volume>154</volume>
          -
          <fpage>162</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>Sirui</given-names>
            <surname>Yao</surname>
          </string-name>
          and
          <string-name>
            <given-names>Bert</given-names>
            <surname>Huang</surname>
          </string-name>
          .
          <year>2017</year>
          .
          <article-title>Beyond Parity: Fairness Objectives for Collaborative Filtering</article-title>
          .
          <source>CoRR abs/1705</source>
          .08804 (
          <year>2017</year>
          ). http://arxiv.org/abs/1705.08804
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Ziwei</surname>
            <given-names>Zhu</given-names>
          </string-name>
          , Xia Hu, and
          <string-name>
            <given-names>James</given-names>
            <surname>Caverlee</surname>
          </string-name>
          .
          <year>2018</year>
          .
          <article-title>Fairness-Aware Tensor-Based Recommendation</article-title>
          .
          <source>In Proceedings of the 27th ACM International Conference on Information and Knowledge Management. ACM</source>
          ,
          <volume>1153</volume>
          -
          <fpage>1162</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>