<!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>Democratizing Travel Personalization via Central Recommendation Platform</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Chana Ross</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tomer Ovadia</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jake Mooney</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Amit Meitin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eytan Kabilou</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mush Kabalo</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dmitri Goldenberg</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Booking.com</institution>
          ,
          <addr-line>Tel Aviv</addr-line>
          ,
          <country country="IL">Israel</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Recommender systems play a crucial role in e-commerce platforms, reducing the information overload problem by providing and prioritizing relevant information based on a user's implicit and explicit preferences. Large e-commerce platforms often rely on a multitude of machine learning models at the same time to optimize the many aspects of the site that can be improved. Occasionally there are duplicate recommender systems that solve a similar or even the same recommendation task, a situation often caused by evolving business objectives, use-case constraints or even just a lack of synchronicity between teams of a large organization. In this work we demonstrate a centralized Recommendation Platform at Booking.com - one of the world's leading online travel platforms. The system is created to reduce the duplication of work, provide utilities for authors of new recommendation models, increase impact by accelerating adoption of better solutions to common recommendation problems, and serve as a single, trusted point of access for recommendations across the website. It allows us to democratize the usage of recommendations across the company and ease the development of new sophisticated models. This, in turn, allows standardization of recommendations tasks and increases the adoption of recommendation systems by various product teams, to bring a personalized experience to each of our customers.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Personalization</kwd>
        <kwd>Travel</kwd>
        <kwd>Recommender Systems</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Online travel platforms ofer a vast variety of products that serve diferent needs of travelers.
Such platforms often rely on recommender systems to assist various customer decisions, seeking
to help narrow down diverse oferings by suggesting well-fit options in a personalized manner
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Such platforms often rely on a cascade of diferent recommender systems [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] resolving
various personalization tasks across the customer journey [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Planning a trip is a particularly complex task requiring important and often expensive
decisions by the customers, within limited time and information. Availability, information gaps,
budget, timing, preferences and even weather constraints introduce non-negligible complexity
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. While some travelers have an exact plan in mind, others have some degree of
openmindedness. Customers are likely to benefit from travel recommendations diferently in diferent
contexts. Because customers are not used to expressing their travel intent explicitly when
interacting with online travel platforms, recommender systems need to be able to interpret a
full spectrum using implicit cues as inputs, including cues set by user context. Therefore, the
work on recommendation tasks often involves multiple teams in the same company, developing
complementary and even parallel models to resolves various recommendations tasks. This
causes a need in a centralized platform for recommendations to allow fast development of
recommender systems on the one hand, and democratize their usage across multiple product
teams on the other hand.
      </p>
      <p>
        In this work we present the Recommendation Platform at Booking.com, serving various
recommendation tasks within a single system. We demonstrate the system through the use-case
of destinations recommendations [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] which requires a complex consideration of available context
data [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], customer needs and recommendation purpose. Recommending travel destinations
presents unique challenges including, but not limited to, continuous cold-start [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], seasonality,
timing of recommendation and delayed feedback [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. These challenges necessitate employing
sophisticated modeling approaches, such as sequential learning [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], combining diferent feature
types within the model [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], and introducing online adaptive algorithms. We present the system
design and the work flow of our centralized Recommendation Platform and explain its benefits
in the multi-contextual use cases of destination recommendations at Booking.com.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. System Overview</title>
      <sec id="sec-2-1">
        <title>2.1. Centralized Platform</title>
        <p>
          Similarly to other data-driven centralized platforms at Booking.com, such as the experimentation
[
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and the machine learning [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] platforms, our goal is to simplify both the development and
the consuming process of new and existing recommender systems in the company. The platform
allows to quickly integrate new models and provide the needed input features, while at the same
time provides a simple API to customer facing systems, that consume these recommendations.
        </p>
        <p>The Recommendation platform is a central ML-driven system for enabling a personalized
customer experience from one source, recommending destinations, properties, attractions
and other trip products to another. The system is able to serve the customer on all possible
connection points such as web, mobile or direct marketing. This ensures consistent and relevant
recommendations across products and customer journey moments. Those recommendations
are expected to be relevant, engaging and insightful based on the customer segment preferences,
search and reservations history and the customer stage in the booking funnel. In addition, the
platform provides a set of tools and services for reducing the friction of recommendation models
development and enriching models with relevant features. Models are monitored, continuously
optimized, and compared with one another for maximizing business impact. Recommendations
and enrichment features are centrally accessible to consume at scale.</p>
        <sec id="sec-2-1-1">
          <title>Simplified Architecture for Recsys Demo Paper</title>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Architecture</title>
        <p>A standard flow of the system (Figure 1) will start with the customer accessing a relevant page
(whether it is on a web platform or a mobile device) designed to display recommendations. At
this point an HTTP request will be sent to the Recommendation Platform via our GraphQL layer
or alternatively via REST API which acts as the main Gateway. The request will include context
about the intent and recommendation type, user, platform, tracking, geo data etc. From there
a central module in the system will manage the significant decision making for what type of
recommendations should be retrieved and then for gathering the information and making it</p>
        <sec id="sec-2-2-1">
          <title>Client</title>
          <p>accessible back to the customer. First the system fills in some additional information about
the user (User Profile Enrichment, complying with applicable privacy laws and regulations
when collecting and using this information). Once the user information is available, the system
chooses a mocudstomeelrs whiIcntehracts"wbithest" fits the current use-case. The term "best" here is relative to each
Booking.com</p>
          <p>website or app
use-case and is dependent on required performance, latency and what available information</p>
          <p>Requests
exists at inferencucstoemertime. In most cases, the further down the funnel a customer is, the more
recommend</p>
          <p>ations Request Response(s)
information we have artecoommenudatrion_dtypie:s"pneaorbys",al to feed intodetsthinaetionsm:[{odel chosen. Our platform accesses the
location_id: 900000000, -2152921,
location_name": "Jerusalem", -2156256,
based on a matching s cliomit:r1e0, .t..he model gives each }i,t..e.]m and cust o-21m54382e,r).</p>
          <p>
            ...
user_id: 44, avg_price: "€ 227", "destinations": [
language_code: "en", image_url: "..x.jpg", -2140479,
relevant mode/delstiwnatioint/lhist thceountrry_ecoqde: u"nli"r,ed payload and ret unumr_of_prsoperttihes:e100t7,op N-215d240e3, stinations (these are chosen
n
currency_code: "EUR",
/destination/cards location_id": -2140479,
]
The system is integrated with the relevanrReetcosumltsmswenitdhp-ply, ML serving [
            <xref ref-type="bibr" rid="ref2">2</xref>
            ], experimentation [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ],
u
ations list
pricing, and content services. After getting the list we enrich the needed content about the
destination (Destination Info Enrichment), such as: pricing/visual image/translated content/etc,
Recommendation Platform
[Software System]
and eliminate options we find as less relevant according to some business rules. Once we have
the final list and the content associated with it the system sends this content back in an API
response to the user in order for them to take care of rendering the results for the client.
          </p>
          <p>Recommendation Platform
[Software System]</p>
          <p>User Profile Data
Enrichment
Complete profile
information and user
preferences</p>
          <p>Destination Recommendations</p>
          <p>Service
Manages decision making and</p>
          <p>information gathering
Destination Info Enrichment
Populates al the required
information about destination</p>
          <p>REST API
[Container: Java Service]
Serves as main gateway
Destination Predictions
Picks ML Model and col ects</p>
          <p>suggested
recommendations</p>
          <p>Requests
customer
recommendations</p>
          <p>Tracks served
recommendations &amp;
server events</p>
          <p>Interacts with
website or app
Web page / mobile</p>
          <p>back-end
Renders page or app</p>
          <p>screen
Executes ML Model</p>
          <p>Booking.com
customers
Tracks client
side behavior
and experiment
Experiment Tool
[Software system]
Experimentation and</p>
          <p>Reporting
Customer Data Tracker
[Software system]
Col ects customer
behavior data</p>
          <p>Data collection
and reporting systems
User Account Service
[Software system]</p>
          <p>User Session Service
[Software system]</p>
          <p>User previous activity
Dependencies for destination recommendations serving</p>
          <p>Image Service
[Software system]</p>
          <p>Pricing &amp; Availability</p>
          <p>Service
[Software system]</p>
          <p>Geo Content
[Software system]
Translated content for
display</p>
          <p>ML Service
[Software system]</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Destination recommendations Use-Case</title>
      <p>
        Destination recommendations are one of the key use-cases for the recommendation platform
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. We consider a set of recommender systems distributed across our website, each of which
is tailored to specific stages of the traveller’s booking journey. They can be described by a
funnel-like structure as follows:
• Inspirational: The goal of these recommendations is to trigger inspirational
recommendations to travelers who have expressed no intent at all, such as via email campaigns to
customers who signed up in the past.
• Cold Start: Travelers visiting our platform without showing intent on where to travel.
      </p>
      <p>These recommendations are displayed in the index page of our web pages and mobile
apps.
• Alternative: For travelers browsing a specific destination, our platform can ofer
alternative options. There are several flavours such as Nearby Destinations aiming at expanding
the availability of the current choice and Similar Destinations aiming to ofer an alternative
plan with a similar experience.
• Complementary: After completing a reservation in a specific destination, our system
recommends the next destination to visit in order to extend the trip.</p>
      <p>
        The recommendations are powered by more than 50 machine learning models, sometimes
simultaneously. The algorithms used to power the use case, could difer according to the task:
The variety of solutions ranges from simple lookup-table models context-aware recommenders,
sequential models [
        <xref ref-type="bibr" rid="ref10 ref12 ref9">9, 10, 12</xref>
        ] and online exploration algorithms.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. Playground</title>
      <p>The platform provides an interactive playground (see Figure 2) for teams within Booking.com to
experience and get a "feel" for the diferent models the system has to ofer, based on their chosen
inputs. This playground can be used by all types of recommendation consumers (machine
learning scientists, developers and even product managers trying to understand the algorithm).
In a case of destination recommendations, a practitioner can quickly test various models and
feature inputs, to perform a "sanity check" and test the model fitness for the selected use-case.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Model Evaluator</title>
      <p>While the playground functionality allows a quick sanity check of models, and make the model
selection process accessible for non-technical practitioners, it may bias the selection process
towards cherry-picked and un-generalized results. Therefore, as a part of the model comparison
suite, the recommendation platform provides a model evaluation tool. This component allows
to compare the empirical performance (such as Accuracy @ TopK) of several models, given
the same set of features and selected input trafic. Such comparison allows to quickly generate
candidates for online experimentation, while at the same time performs a seasonal monitoring
of existing deployed solutions.</p>
      <p>Figure 3 demonstrates an example comparison of three destination recommendations models
in an "Alternative destination" scenario. The charts plots the Accuracy @ Top 10 performance
of a personalized model, compared to simple "Nearby" and "Domestic" recommends. It is worth
mentioning that all three models are already deployed in several pages across the website. We
observe that the personalized model is losing its predictability during COVID-19 period and
recovering back to the leading position afterwards. At the same time, the two "basic models"
demonstrate a relatively consistent performance. Moreover, the two models are providing
practically the same recommendations, suggesting a valid consideration to decommission one
of them and reduce redundancy.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Discussion</title>
      <p>Our paper demonstrates the main architecture used in Booking.com for destinations
recommendations. In addition, we show how this system is displayed in a playground allowing others
in the company to investigate their models and better understand the results and enhanced
information received from the platform. The system can be used during and after the model is
built for testing and building future models. The main benefit of our platform is the comparison
and flexibility it provides scientists in the company to test their model throughout the website
and user journey. Unlike most models which need specific work for each entry point in the
website, we enhance the features needed for the model based on the context of the user entered
(number of rooms for example) and the searched destination.</p>
      <p>50</p>
      <p>Personalizedmodel
Domesticmodel
Nearbymodel
2019-09
2020-01
2020-05
2020-09
2021-01</p>
      <p>Month
2021-05
2021-09
2022-01
2022-05
2022-09</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Goldenberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kofman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Albert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mizrachi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Horowitz</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Teinemaa</surname>
          </string-name>
          ,
          <article-title>Personalization in practice: Methods and applications</article-title>
          ,
          <source>in: Proceedings of the 14th ACM International Conference on Web Search and Data Mining</source>
          , WSDM '21,
          <string-name>
            <surname>Association</surname>
          </string-name>
          for Computing Machinery, New York, NY, USA,
          <year>2021</year>
          , p.
          <fpage>1123</fpage>
          -
          <lpage>1126</lpage>
          . URL: https://doi.org/10.1145/3437963. 3441657. doi:
          <volume>10</volume>
          .1145/3437963.3441657.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>L.</given-names>
            <surname>Bernardi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mavridis</surname>
          </string-name>
          , P. Estevez,
          <article-title>150 successful machine learning models: 6 lessons learned at booking</article-title>
          .com,
          <source>in: Proceedings of the 25th ACM SIGKDD International Conference on Knowledge Discovery &amp; Data Mining</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>1743</fpage>
          -
          <lpage>1751</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>I.</given-names>
            <surname>Kangas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schwoerer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. J.</given-names>
            <surname>Bernardi</surname>
          </string-name>
          ,
          <article-title>Recommender systems for personalized user experience: Lessons learned at booking</article-title>
          . com,
          <source>in: Fifteenth ACM Conference on Recommender Systems</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>583</fpage>
          -
          <lpage>586</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>T. H. N.</given-names>
            <surname>Do</surname>
          </string-name>
          , W. Shih,
          <article-title>Destination decision-making process based on a hybrid mcdm model combining dematel and anp: The case of vietnam as a destination, Modern Economy 7 (</article-title>
          <year>2016</year>
          )
          <fpage>966</fpage>
          -
          <lpage>983</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>D.</given-names>
            <surname>Goldenberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mizrachi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Horowitz</surname>
          </string-name>
          , I. Kangas,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schwoerer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mozzato</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ferretti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Panagiotis</surname>
          </string-name>
          ,
          <string-name>
            <surname>L. Bernardi,</surname>
          </string-name>
          <article-title>I know what you did next summer: Challenges in travel destination recommendation (</article-title>
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kiseleva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Mueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Bernardi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Davis</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Kovacek</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. Stafseng</given-names>
            <surname>Einarsen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kamps</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tuzhilin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hiemstra</surname>
          </string-name>
          ,
          <article-title>Where to go on your next trip? optimizing travel destinations based on user preferences</article-title>
          ,
          <source>in: Proceedings of the 38th International ACM SIGIR Conference on Research and Development in Information Retrieval</source>
          ,
          <year>2015</year>
          , pp.
          <fpage>1097</fpage>
          -
          <lpage>1100</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>L.</given-names>
            <surname>Bernardi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kamps</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Kiseleva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Müller</surname>
          </string-name>
          ,
          <article-title>The continuous cold start problem in e-commerce recommender systems</article-title>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>T.</given-names>
            <surname>Mavridis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Hausl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mende</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pagano</surname>
          </string-name>
          , Beyond algorithms: Ranking at scale at booking. com,
          <source>in: Proceedings of the Fourth Workshop on Recommendation in Complex Scenarios. CEUR-WS</source>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>D.</given-names>
            <surname>Goldenberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Levin</surname>
          </string-name>
          , Booking.
          <article-title>com multi-destination trips dataset</article-title>
          ,
          <source>in: Proceedings of the 44th International ACM SIGIR Conference on Research and Development in Information Retrieval</source>
          , SIGIR '21,
          <string-name>
            <surname>Association</surname>
          </string-name>
          for Computing Machinery, New York, NY, USA,
          <year>2021</year>
          , p.
          <fpage>2457</fpage>
          -
          <lpage>2462</lpage>
          . URL: https://doi.org/10.1145/3404835.3463240. doi:
          <volume>10</volume>
          .1145/ 3404835.3463240.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>S.</given-names>
            <surname>Mizrachi</surname>
          </string-name>
          , P. Levin,
          <article-title>Combining context features in sequence-aware recommender systems</article-title>
          .,
          <source>in: Late-Breaking Results of the 13th ACM Conference on Recommender Systems, RecSys '19</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R. L</given-names>
            . Kaufman, J.
            <surname>Pitchforth</surname>
          </string-name>
          , L. Vermeer,
          <article-title>Democratizing online controlled experiments at booking</article-title>
          . com,
          <source>arXiv preprint arXiv:1710.08217</source>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>B.</given-names>
            <surname>Schiferer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Deotte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-F.</given-names>
            <surname>Puget</surname>
          </string-name>
          , G. d. S. Pereira Moreira, G. Titericz, J. Liu,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ak</surname>
          </string-name>
          ,
          <article-title>Using deep learning to win the booking.com wsdm webtour21 challenge on sequential recommendations</article-title>
          ,
          <source>in: Proceedings of the ACM WSDM Workshop on Web Tourism (WSDM Webtour '21)</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>