<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Smart Book Recommender: A Semantic Recommendation Engine for Editorial Products</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Francesco</forename><surname>Osborne</surname></persName>
							<email>francesco.osborne@open.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Knowledge Media Institute</orgName>
								<orgName type="institution">The Open University</orgName>
								<address>
									<addrLine>MK7</addrLine>
									<postCode>6AA</postCode>
									<settlement>Milton Keynes</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Thiviyan</forename><surname>Thanapalasingam</surname></persName>
							<email>thiviyan.thanapalasingam@open.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Knowledge Media Institute</orgName>
								<orgName type="institution">The Open University</orgName>
								<address>
									<addrLine>MK7</addrLine>
									<postCode>6AA</postCode>
									<settlement>Milton Keynes</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Angelo</forename><surname>Salatino</surname></persName>
							<email>angelo.salatino@open.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Knowledge Media Institute</orgName>
								<orgName type="institution">The Open University</orgName>
								<address>
									<addrLine>MK7</addrLine>
									<postCode>6AA</postCode>
									<settlement>Milton Keynes</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Aliaksandr</forename><surname>Birukou</surname></persName>
							<email>aliaksandr.birukou@springer.com</email>
							<affiliation key="aff1">
								<orgName type="department">Springer-Verlag GmbH</orgName>
								<address>
									<addrLine>Tiergartenstrasse 17</addrLine>
									<postCode>69121</postCode>
									<settlement>Heidelberg</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Enrico</forename><surname>Motta</surname></persName>
							<email>enrico.motta@open.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Knowledge Media Institute</orgName>
								<orgName type="institution">The Open University</orgName>
								<address>
									<addrLine>MK7</addrLine>
									<postCode>6AA</postCode>
									<settlement>Milton Keynes</settlement>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Smart Book Recommender: A Semantic Recommendation Engine for Editorial Products</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">DFE0E7281A2D5368B9E429668E590A2F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T06:11+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Scholarly Data</term>
					<term>Recommendation Systems</term>
					<term>Ontology</term>
					<term>Bibliographic Data</term>
					<term>Scholarly Ontologies</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Academic publishers, such as Springer Nature, need to constantly make informed decisions about how and where to market their editorial products. In the field of Computer Science (CS), it is particularly critical to assess which books will be of interest to the attendees of a conference. Typically, these items are manually chosen by publishing editors, on the basis of their personal experience. To make this process both faster and more robust we have developed the Smart Book Recommender (SBR), a semantic application designed to support the Springer Nature editorial team in promoting their publications at CS venues. SBR takes as input the proceedings of a conference and suggests books, journals, and other conference proceedings which are likely to be relevant to the attendees of the conference in question. It does so by taking advantage of a semantic representation of topics, which builds on a very large ontology of Computer Science topics; characterizing Springer Nature books as distributions of semantic topics; and approaching the problem as one of semantic matching between such distributions of semantic topics.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Academic publishers need to constantly make timely and data-driven decisions to ensure that they are showcasing their editorial products to their target market. In the field of Computer Science, it is particularly critical to assess which books, journal, or proceedings will be of interest for the attendees of a conference. Typically, these items are manually chosen by publishing editors, on the basis of their personal experience. As the number of publications grows, there is an increasing need for automated and data-driven methods that can support this complex and time-consuming task by analysing large-scale data about editorial products.</p><p>In what follows we present the Smart Book Recommender (SBR), a web application developed in collaboration with Springer Nature, which recommends books, journals and conference proceedings that are likely to be relevant to the attendees of a given conference. This work stems from the ongoing collaboration between Springer Nature and the Knowledge Media Institute (KMi) of the Open University, which has produced a number of other innovative solutions, including Smart Topic Miner (STM) <ref type="bibr" target="#b0">[1]</ref>, a semantic framework for classifying academic documents, and its API, the Smart Topic API.</p><p>Since January 2017, STM is being routinely used by the SN Computer Science editorial team, halving the time for classifying conference proceeding. Similarly, SBR is in line to be adopted to support SN editors in selecting the best set of books to market to the participants of a conference. A demo of the SBR prototype is available at http://rexplore.kmi.open.ac.uk/SBR-demo. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Smart Book Recommender</head><p>SBR takes as input the title of a SN book, usually the proceedings of a conference, and returns a list of books, journals, and proceedings which address topics that are likely to be relevant to the participants of the conference in question. To do so, it represents SN books in Computer Science as distributions of semantically-characterized topics, which are drawn from a large-scale ontology of Computer Science, and then computes their pairwise similarity. SBR offers a simple web interface, shown in Figure <ref type="figure" target="#fig_0">1</ref>, to allow editors to filter the results and share their feedback. It is thus complementary, but very different in scope, to Reccomended<ref type="foot" target="#foot_0">1</ref> , the SN recommender system, which suggest books to users on the basis of their last 100 papers read on online platforms.</p><p>SBR relies on the following background knowledge: a large database of SN book metadata and the Computer Science Ontology (CSO). The database of metadata contains titles, abstracts, keywords and other information describing the chapters of about 27K books and 270 journals in the field of Computer Science. In the case of conference proceedings and journals, each chapter is usually a research paper. CSO is a large scale and granular ontology of research topics that has been created automatically by running the Klink-2 algorithm <ref type="bibr" target="#b1">[2]</ref> on the Rexplore dataset <ref type="bibr" target="#b2">[3]</ref>, which consists of about 16 million publications in the field of Computer Science. It is an extension<ref type="foot" target="#foot_1">2</ref> of the BIBO ontology 3 which in turn builds on SKOS. The current version of CSO includes about 17K topics, which are linked by 70K semantic relationships.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Architecture</head><p>Figure <ref type="figure" target="#fig_1">2</ref> shows the architecture of SBR. The computation of the pairwise similarity between SN books is performed offline. The Recommendation Engine iterates on journals, conference proceedings, and other books, and retrieves for each of them the relevant set of chapters/papers. It then sends this metadata to the Smart Topic API, which extracts frequent terms from abstracts, titles and keywords, maps them to the CSO ontology concepts, and prunes the resulting topics with a set-covering algorithm as detailed in <ref type="bibr" target="#b0">[1]</ref>. The mappings from terms to concepts take into account both synonyms and sub-areas of a topic -e.g., all documents associated to terms such as "semantic technologies", "linked data", "RDF", "OWL" will be also tagged with the topic "Semantic Web". The result of this process is a distribution of topics from CSO, in which each topic is associated with the number of chapters/papers addressing it. The recommendation engine uses this representation for pre-computing and storing in the database the similarity scores. Presently, the prototype uses the cosine similarity of the topic vectors, but we are testing other similarity metrics. Since computing the cosine similarity of all the books in the dataset is computationallyheavy, we consider only promising pairs which obtain a jaccard similarity of at least 0.125. A data analysis revealed that this heuristic halves the number of candidate pairs while still producing very good results.</p><p>When the user submits an input book to the SBR web interface, the relevant ID and user settings are sent as JSON to the background API via a GET query. The API queries the database for selecting the most similar books and returns their descriptions. Both the API and the recommendation engine are realized in Python.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">The Web Interface</head><p>The user can select specific conference proceedings by typing their name in an autocomplete field. The recommendation results are displayed in order of descending similarity scores and they can be filtered according to document types (journals, books, conference proceedings) and year range. Figure <ref type="figure" target="#fig_2">3</ref> shows an example of proceedings suggested by SBR. For simplicity, proceedings of different editions of the same conferences are grouped together. Each proceedings volume is described according to its title, year and the top fifteen topics. SBR also highlights in blue the topics which are among the top fifty topics of the input book. The user has the option to provide feedback about each item using emoticons buttons. When the user clicks either button, the feedback is sent to the API and recorded in the database. These data will be used to determine the quality of different similarity metrics and further enhance the recommendation process. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Conclusions</head><p>In this demo paper, we presented the prototype of SBR, a novel system for identifying related editorial products and facilitating the marketing process at SN.</p><p>As next steps, we intend to improve the recommendation process using other features (e.g., sales figures) and to conduct a formal evaluation with a group of SN editors. We are also planning to design a more advanced user interface for comparing the topics of different books and to implement a new version of the system for assisting researchers in identifying books and conferences which are relevant to their work.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 .</head><label>1</label><figDesc>Figure 1. The SBR interface.</figDesc><graphic coords="2,119.76,198.24,355.92,181.44" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 .</head><label>2</label><figDesc>Figure 2. The architecture of SBR.</figDesc><graphic coords="3,131.04,322.32,333.36,89.52" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 .</head><label>3</label><figDesc>Figure 3. Example of suggested conference proceedings.</figDesc><graphic coords="4,116.16,163.68,364.80,268.32" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://recommended.springernature.com/recommended/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">http://kmi.open.ac.uk/technologies/rexplore/ontologies/BiboExtension.owl</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">http://purl.org/ontology/bibo/</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Automatic Classification of Springer Nature Proceedings with Smart Topic Miner</title>
		<author>
			<persName><forename type="first">F</forename><surname>Osborne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Salatino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Birukou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Motta</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016">2016. 2016</date>
			<biblScope unit="page" from="383" to="399" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Klink-2: integrating multiple web sources to generate semantic topic networks</title>
		<author>
			<persName><forename type="first">F</forename><surname>Osborne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Motta</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2015">2015. 2015</date>
			<biblScope unit="page" from="408" to="424" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Exploring scholarly data with Rexplore</title>
		<author>
			<persName><forename type="first">F</forename><surname>Osborne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Motta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Mulholland</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Semantic Web Conference</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2013">2013. 2013</date>
			<biblScope unit="page" from="460" to="477" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
