<!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>
      <journal-title-group>
        <journal-title>ACM Conference on Recommender Systems (RecSys),
September</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>“One Size Doesn't Fit All": Helping Users Find Events from Multiple Perspectives</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sean MacLachlan &amp; Stacey Donohue</string-name>
          <email>sean@releventcity.com</email>
          <email>stacey@releventcity.com</email>
          <email>{sean,stacey}@releventcity.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nevena Dragovic &amp; Maria Soledad Pera</string-name>
          <email>ndragovic@boisestate.edu</email>
          <email>solepera@boisestate.edu</email>
          <email>{ndragovic,solepera}@boisestate.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Dept. of Computer Science, Boise State University</institution>
          ,
          <addr-line>Boise, ID</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>relEVENTcity</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2016</year>
      </pub-date>
      <volume>15</volume>
      <issue>2016</issue>
      <abstract>
        <p>In this demo, we showcase a novel mobile application that o ers various ways to present recommendations to users. While the majority of the existing applications in the tourism domain either focus on event recommendation or event browsing, our mobile application acknowledges the fact that users have di erent interests at di erent times and for di erent occasions. Consequently, while suggested events are ltered and ranked by proximity and date ranges to ensure they suit users' needs, each user is allowed to choose how to access these suggestions in one of four ways: search, categorized browsing, following, and traditional recommendations.</p>
      </abstract>
      <kwd-group>
        <kwd>Event recommendations</kwd>
        <kwd>user perspectives</kwd>
        <kwd>mobile application</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        As de ned in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], recommendation strategies in the tourism
domain can help users, i.e., visitors, nd unique and
interesting information about a particular travel destination that
match their preferences and their current context.
      </p>
      <p>
        A recent survey on recommenders in the tourist domain [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
highlights the fact that the majority of the mobile
applications focused on helping visitors create routes or tour plans,
which often involved suggestions primarily focused on Points
of Interest [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and locations. Unlike points of interests, which
are locations or places that people tend to nd interesting,
such as a museum, theater, or historical site, events
occurring around town often have a short time-span, information
(reviews and ratings) about them is usually limited, and they
rarely reoccur. For example, the Ei el tower is a well-known
and popular tourist location with few restrictions besides the
visiting hours and distance (which impacts transportation).
Events, however, are more complicated. A concert or dinner
event will also have time and location constraints, but the
limited duration of the event combined with the lack of any
historical data such as reviews or rating (because events
often do not repeat) makes event recommendations much
more challenging. Even after addressing the challenges
inherent to event recommendation strategies, the application still
needs to address the fact that di erent users have di erent
preferences in terms of how they receive recommendations.
      </p>
      <p>Based on our user analysis, we noticed that users not only
di er in terms of the type of recommendations they favor,
they can also prefer di erent types of recommendations
depending on the circumstances (time of day, day of the week,
weather, current mode, etc.). In the end, providing lists of
\things to do", even if they all appeal and are tailored to
individual users is not enough. Context plays a key role, and it
is the duty of the recommender to both narrow down choices
and provide enough exibility to cater to users' diverse needs.
With this in mind, we present RelEVENT, a mobile
application that o ers di erent recommendation styles, thus
allowing users to choose the one that best ts their current,
but likely to change, information retrieval preference. Our
analysis revealed four di erent groups of users: (i) the ones
that consider only suggestions provided by the app and do
not feel the need for further exploring, (ii) the ones that are
interested in events their friends are going, or their favorite
band is organizing, (iii) the ones that are only interested in
one type of event at time (Friday for dinners, Saturday for
sports), and (iv) the ones that are already aware of events
they would like to visit but they need more information about
them.
2.</p>
    </sec>
    <sec id="sec-2">
      <title>OVERVIEW</title>
      <p>In this section we discuss each RelEVENT's strategies
to provide recommendations targeted to users' needs.
Traditional Recommendations. The main contribution of
RelEVENT is providing personalized event suggestions for
each individual user. The algorithm running in the
background matches users' preferences, demographical
information and historical data (such as, ratings, reviews, likes), with
available metadata of each candidate event happening in a
given city (Figure 1a). Based on our recommendation
strategy, each user is provided with top-N suggestions from which
to choose. Users who like receiving diverse (sometimes even
unexpected) suggestions, prefer this type of
recommendation. An ancillary bene t to this approach is that it doesn't
require any e ort from the user in order to receive credible
(a) Traditional Recommendation
(b) Follow
(c) Category
(d) Search
recommendations. Therefore, a signi cant group of users
prefers this type of recommendation delivery method.</p>
      <p>Follow. Based on our empirical study conducted to detect
preferred styles of recommendations, we noticed that another
group of users are interested in knowing about the events their
friends like (e.g., movie that is currently playing in the nearby
theater), are interested in (e.g., concert that will happen
in 3 months) or already attended (e.g., museum exhibit).
Since these users prefer seeing this type of recommendation,
RelEVENT (as shown at Figure 1b) provides suggestions
based on the people they follow. In addition to following
a person, we added a feature that allows users to follow a
speci c event. For example, the Cannes movie festival occurs
every year and has a wide variety of movie screenings. By
following the event, users can keep up to date about changes
in the festival lineup or smaller events happening within the
bigger event (e.g., of director roundtables associated with
the lm screenings).</p>
      <p>Category. Based on our study, we concluded that users
often prefer one category of events over another at a speci c
point of time (e.g., time of day, day of week, or month).
During the football season, we noticed some of the users are
more interested in the sports category on Sundays, while
on Friday night users preferred events related to movies
and dinners. In order to provide suitable recommendations
related to speci c category, RelEVENT provides users the
ability to search and lter suggestions based on the current
category of interest as shown in Figure 1c. The suggestions
in each category will still be ranked based on the speci c
interest of a user (e.g., football fans will nd the Seahawks
game ranked rst in the sport sections).</p>
      <p>Search. The last group contains users who already know
what type of events they would like to attend. RelEVENT
enables them to nd information about di erent types of
events by doing a basic keyword search. In doing so, users
can submit to the app speci c constraints and still retrieve
events that are relevant to their speci cations, yet they
are sorted, i.e., recommended, based on what RelEVENT
knows this user favors (in terms of location, budget, etc).
As shown in the Figure 1d, if a user is interested in going
to an event related to \beer" he can type that keyword and
RelEVENT will locate events that refer to \beer" in their
archived metadata, lter and personalize the identi ed events,
and provide suitable and relevant suggestions to the user.
3.</p>
    </sec>
    <sec id="sec-3">
      <title>CONCLUSIONS</title>
      <p>
        We have introduced a mobile application that allows users
to discover interesting events from multiple perspectives.
While, as stated in [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], context-aware venue suggestion is still
a challenge for the RecSys and Information retrieval
communities, by o ering exploratory and traditional avenues for
recommendations to ease users' decision making process and
therefore represents a step forward. Based on data collected
using the mobile application presented in this demo, we will
conduct the necessary empirical analysis to validate and
quantify the degree to which o ering multiple perspectives
can increase user satisfaction in the recommendation process
and allow them to take better advantage of the events a new
destination o ers visitors.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Borras</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Moreno</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Valls</surname>
          </string-name>
          .
          <article-title>Intelligent tourism recommender systems: A survey</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>41</volume>
          (
          <issue>16</issue>
          ):
          <volume>7370</volume>
          {
          <fpage>7389</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Deveaud</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.-D. Albakour</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Manotumruksa</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Macdonald</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <string-name>
            <surname>Ounis</surname>
          </string-name>
          , et al.
          <article-title>Smartvenues: Recommending popular and personalised venues in a city</article-title>
          .
          <source>In ACM CIKM</source>
          , pages
          <year>2078</year>
          {
          <year>2080</year>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Y.-T.</given-names>
            <surname>Zheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.-J.</given-names>
            <surname>Zha</surname>
          </string-name>
          , and T.-S. Chua.
          <article-title>Mining travel patterns from geotagged photos</article-title>
          .
          <source>ACM TIST</source>
          ,
          <volume>3</volume>
          (
          <issue>3</issue>
          ):
          <fpage>56</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>