Table of Contents
Fetching ...

On the Need for Configurable Travel Recommender Systems: A Systematic Mapping Study

Rickson Simioni Pereira, Claudio Di Sipio, Martina De Sanctis, Ludovico Iovino

TL;DR

This paper investigates whether Travel Recommender Systems are configurable across deployment contexts and how current works support provider-oriented configuration. Using a systematic mapping study, the authors analyze 40 primary TRS papers, categorizing algorithms, data types, outcomes, and configuration features, and find a dominant use of hybrid and advanced methods with limited real-time data handling and scarce provider-facing configurability. The results reveal a gap: TRSs are often built from scratch rather than as configurable product lines, hindering reuse and rapid deployment in different contexts. The authors propose directions to address this gap, including software product lines, feature models, low-code platforms, and AI-assisted tooling to enable context-aware TRS development.

Abstract

Travel Recommender Systems TRSs have been proposed to ease the burden of choice in the travel domain by providing valuable suggestions based on user preferences Despite the broad similarities in functionalities and data provided by TRSs these systems are significantly influenced by the diverse and heterogeneous contexts in which they operate This plays a crucial role in determining the accuracy and appropriateness of the travel recommendations they deliver For instance in contexts like smart cities and natural parks diverse runtime informationsuch as traffic conditions and trail status respectivelyshould be utilized to ensure the delivery of pertinent recommendations aligned with user preferences within the specific context However there is a trend to build TRSs from scratch for different contexts rather than supporting developers with configuration approaches that promote reuse minimize errors and accelerate timetomarket To illustrate this gap in this paper we conduct a systematic mapping study to examine the extent to which existing TRSs are configurable for different contexts The conducted analysis reveals the lack of configuration support assisting TRSs providers in developing TRSs closely tied to their operational context Our findings shed light on uncovered challenges in the domain thus fostering future research focused on providing new methodologies enabling providers to handle TRSs configurations

On the Need for Configurable Travel Recommender Systems: A Systematic Mapping Study

TL;DR

This paper investigates whether Travel Recommender Systems are configurable across deployment contexts and how current works support provider-oriented configuration. Using a systematic mapping study, the authors analyze 40 primary TRS papers, categorizing algorithms, data types, outcomes, and configuration features, and find a dominant use of hybrid and advanced methods with limited real-time data handling and scarce provider-facing configurability. The results reveal a gap: TRSs are often built from scratch rather than as configurable product lines, hindering reuse and rapid deployment in different contexts. The authors propose directions to address this gap, including software product lines, feature models, low-code platforms, and AI-assisted tooling to enable context-aware TRS development.

Abstract

Travel Recommender Systems TRSs have been proposed to ease the burden of choice in the travel domain by providing valuable suggestions based on user preferences Despite the broad similarities in functionalities and data provided by TRSs these systems are significantly influenced by the diverse and heterogeneous contexts in which they operate This plays a crucial role in determining the accuracy and appropriateness of the travel recommendations they deliver For instance in contexts like smart cities and natural parks diverse runtime informationsuch as traffic conditions and trail status respectivelyshould be utilized to ensure the delivery of pertinent recommendations aligned with user preferences within the specific context However there is a trend to build TRSs from scratch for different contexts rather than supporting developers with configuration approaches that promote reuse minimize errors and accelerate timetomarket To illustrate this gap in this paper we conduct a systematic mapping study to examine the extent to which existing TRSs are configurable for different contexts The conducted analysis reveals the lack of configuration support assisting TRSs providers in developing TRSs closely tied to their operational context Our findings shed light on uncovered challenges in the domain thus fostering future research focused on providing new methodologies enabling providers to handle TRSs configurations
Paper Structure (13 sections, 1 figure, 2 tables)