<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""><span class="" style="font-family: LucidaGrande;"><b class="">SECOND CALL FOR PAPERS</b></span>
<div class=""><br class="">
</div>
<div class=""><b class="" style="font-family: LucidaGrande;">4th Workshop on Recommendation in Complex Environments (ComplexRec 2020)</b><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Co-located with RecSys 2020, Rio de Janeiro, Brazil</span><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">September 25, 2020</span><br class="" style="font-family: LucidaGrande;">
<br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Website: </span><font face="LucidaGrande" class=""><a href="http://complexrec2020.aau.dk/" class="">http://complexrec2020.aau.dk/</a></font></div>
<div class=""><br class="">
</div>
<div class=""><b class="">IMPORTANT:</b> ComplexRec 2020 (along with all other RecSys 2020 events) will take place online due to the current Covid-19 pandemic.<br class="" style="font-family: LucidaGrande;">
<br class="">
<br class="" style="font-family: LucidaGrande;">
<b class="" style="font-family: LucidaGrande;">***Important dates***<br class="">
</b><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Paper submission deadline: July 8, 2020</span><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Notification of paper acceptance: August 1, 2020</span><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Camera-ready version deadline: August 31, 2020</span><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">Workshop (at RecSys 2020): September 25-26, 2020</span><br class="" style="font-family: LucidaGrande;">
<br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class=""> </span><br class="" style="font-family: LucidaGrande;">
<b class="" style="font-family: LucidaGrande;">***Description & Objectives***<br class="">
</b><br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">During the past decade, recommender systems have rapidly become an indispensable element of websites, apps, and other platforms that are looking to provide personalized interaction to their users. As recommendation
technologies are applied to an ever-growing array of non-standard problems and scenarios, researchers and practitioners are also increasingly faced with challenges of dealing with greater variety and complexity in the inputs to those recommender systems. For
example, there has been more reliance on fine-grained user signals as inputs rather than simple ratings or likes. Many applications also require more complex domain-specific constraints on inputs to the recommender systems. The outputs of recommender systems
are also moving towards more complex composite items, such as package or sequence recommendations. This increasing complexity requires smarter recommender algorithms that can deal with this diversity in inputs and outputs.</span><br class="" style="font-family: LucidaGrande;">
<br class="" style="font-family: LucidaGrande;">
<span style="font-family: LucidaGrande;" class="">For the past three years, the ComplexRec workshop series has offered an interactive venue for discussing approaches to recommendation in complex environments that have no simple one-size-fits-all solution. For
the fourth edition of ComplexRec we have narrowed the focus of the workshop and contributions to the workshop about topics related to one of the two main themes on complex recommendation: complex inputs and complex outputs. </span><br class="" style="font-family: LucidaGrande;">
<br class="" style="font-family: LucidaGrande;">
<br class="" style="font-family: LucidaGrande;">
<b class="" style="font-family: LucidaGrande;">***Complex inputs***<br class="">
</b><br class="" style="font-family: LucidaGrande;">
<div class="" style="font-family: LucidaGrande;">An important source of complexity comes from the various types of inputs to the system beyond users and items, such as features, queries and constraints. There are active user inputs (interaction), implicit user
inputs (task, context, preferences), item inputs (features or attributes) and domain inputs (eligibility, availability). In group-based recommendation, the user input can be a combination of inputs for multiple individual users as well as group aspects such
as the composition of the group and how well they know each other. <br class="">
An additional challenge is providing users with ways to have control over the inputs. For instance by selecting and weighting or ranking user and item features, providing interactive queries to steer the recommendation, or deal with longer narrative statements
that require natural language understanding. <br class="">
<br class="">
<br class="">
<b class="">***Complex outputs***</b></div>
<div class="" style="font-family: LucidaGrande;"><br class="">
</div>
<div class="" style="font-family: LucidaGrande;">Another type of complexity that we wish to focus on in ComplexRec 2020 is the complexity of the outputs of a recommender system to move away from a straightforward ranked list of items as output. An example of
such complex output is package recommendation: suggesting a set or combination of items that go well together and are complementary on dimensions that matter to the user. In many domains the sequence in which items are recommended is also important. Moreover,
different users may want different information about items, so the output complexity goes beyond ranking and also manifests itself in how the interface should allow the user to view the type of information that is most relevant to them. Another example of
complexity in recommender systems output are environments where the system’s goal is to create new, composite items that must satisfy certain constraints (such as menu recommendation, or recommendations for product designs). <br class="">
<br class="">
<br class="">
<b class="">***Topics of interest***<br class="">
</b><br class="">
We plan to invite contributions that address the challenges associated with constructing recommender systems that must handle complex inputs and/or outputs. The topics of interest for the workshop include, but are not limited to:<br class="">
<br class="">
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Recommenders with novel complex inputs<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Recommenders with interesting combinations of inputs<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Constraint-driven recommender systems <br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Novel knowledge-based recommender systems<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Novel modes of user interactions with complex inputs<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Query-driven and interactive recommender systems<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Algorithms and models that effectively integrate complex inputs<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Recommending complex items, such as packages and sequences<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Recommending composite items with complex feature interactions<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Algorithms for generating personalized items based on feature preferences<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Novel NLP approaches for dealing with complex inputs and outputs<br class="">
</div>
<br class="">
<br class="">
<b class="">***Submissions***<br class="">
</b><br class="">
We encourage authors to submit short papers and position papers of 4-8 pages in length (excluding references) dedicated to any aspect of recommendation in complex environments.<br class="">
<br class="">
Accepted submissions will then be invited for short presentations. Evaluation criteria for acceptance will include novelty, diversity, significance for theory/practice, quality of presentation, and the potential for sparking interesting discussion at the workshop.
All submitted papers will be reviewed by the Program Committee. At least one author of each accepted paper must attend the workshop.<br class="">
<br class="">
All submissions should be in English and should not have been published or submitted for publication elsewhere. Papers should be formatted in the ACM Proceedings Style and submitted via EasyChair (<a href="https://easychair.org/conferences/?conf=complexrec2020" class="">https://easychair.org/conferences/?conf=complexrec2020</a>).
Submissions will be published in the workshop proceedings.<br class="">
Similar to the main RecSys conference, all authors should submit manuscripts for review in a single-column format. Instructions for Word and LaTeX authors are given below:<br class="">
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* Microsoft Word: Write your paper using the Submission Template (<a href="https://www.acm.org/binaries/content/assets/publications/taps/acm_submission_template.docx" class="">https://www.acm.org/binaries/content/assets/publications/taps/acm_submission_template.docx</a>).
Follow the embedded instructions to apply the paragraph styles to your various text elements. The text is in single-column format at this stage and no additional formatting is required at this point.<br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>* LaTeX: Please use the latest version of the Master Article Template – LaTeX (<a href="https://www.acm.org/binaries/content/assets/publications/consolidated-tex-template/acmart-master.zip" class="">https://www.acm.org/binaries/content/assets/publications/consolidated-tex-template/acmart-master.zip</a>)
to create your submission. You must use the “manuscript" option with the \documentclass[manuscript]{acmart} command to generate the output in a single-column format which is required for review. Please see the LaTeX documentation (<a href="https://www.acm.org/binaries/content/assets/publications/consolidated-tex-template/acmart.pdf" class="">https://www.acm.org/binaries/content/assets/publications/consolidated-tex-template/acmart.pdf</a>)
and ACM’s LaTeX best practices guide (<a href="https://www.acm.org/publications/taps/latex-best-practices" class="">https://www.acm.org/publications/taps/latex-best-practices</a>) for further instructions.<br class="">
</div>
<br class="">
<br class="">
<br class="">
<b class="">***Organizers***</b><br class="">
<br class="">
Toine Bogers (<a href="mailto:toine@hum.aau.dk" class="">toine@hum.aau.dk</a>), Aalborg University Copenhagen, Denmark<br class="">
Marijn Koolen (<a href="mailto:marijn.koolen@di.huc.knaw.nl" class="">marijn.koolen@di.huc.knaw.nl</a>), Royal Netherlands Academy of Arts and Sciences, the Netherlands<br class="">
Bamshad Mobasher (<a href="mailto:mobasher@cs.depaul.edu" class="">mobasher@cs.depaul.edu</a>), DePaul University, USA<br class="">
Casper Petersen (<a href="mailto:casper.ptrsn@gmail.com" class="">casper.ptrsn@gmail.com</a>), Sampension, Denmark<br class="">
Alexander Tuzhilin (<a href="mailto:atuzhili@stern.nyu.edu" class="">atuzhili@stern.nyu.edu</a>), New York University, USA<br class="">
<br class="">
<a href="http://complexrec2020.aau.dk/" class="">http://complexrec2020.aau.dk/</a><br class="">
<br class="">
For further questions, please contact a member of the organizing committee.</div>
</div>
</div>
</body>
</html>