<?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">ParsRec: A Novel Meta-Learning Approach to Recommending Bibliographic Reference Parsers</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Dominika</forename><surname>Tkaczyk</surname></persName>
							<email>d.tkaczyk@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">ADAPT Centre</orgName>
								<orgName type="department" key="dep2">School of Computer Science and Statistics</orgName>
								<orgName type="institution">Trinity College Dublin</orgName>
								<address>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Rohit</forename><surname>Gupta</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Iconic Translation Machines Ltd</orgName>
								<address>
									<settlement>Dublin</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Riccardo</forename><surname>Cinti</surname></persName>
							<email>riccardo@iconictranslation.com</email>
							<affiliation key="aff1">
								<orgName type="institution">Iconic Translation Machines Ltd</orgName>
								<address>
									<settlement>Dublin</settlement>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Joeran</forename><surname>Beel</surname></persName>
							<email>beelj@tcd.ie</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">ADAPT Centre</orgName>
								<orgName type="department" key="dep2">School of Computer Science and Statistics</orgName>
								<orgName type="institution">Trinity College Dublin</orgName>
								<address>
									<country key="IE">Ireland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">ParsRec: A Novel Meta-Learning Approach to Recommending Bibliographic Reference Parsers</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">0C8B3068903CCB98AD47023173DF087F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T13:30+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>recommender systems</term>
					<term>meta-learning</term>
					<term>citation parsing</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Bibliographic reference parsers extract machine-readable metadata such as author names, title, journal, and year from bibliographic reference strings. To extract the metadata, the parsers apply heuristics or machine learning. However, no reference parser, and no algorithm, consistently gives the best results in every scenario. For instance, one tool may be best in extracting titles in ACM citation style, but only third best when APA is used. Another tool may be best in extracting English author names, while another one is best for noisy data (i.e. inconsistent citation styles). In this paper, which is an extended version of [1], we address the problem of reference parsing from a recommendersystems and meta-learning perspective. We propose ParsRec, a meta-learning based recommender-system that recommends the potentially most effective parser for a given reference string. ParsRec recommends one out of 10 open-source parsers: Anystyle-Parser, Biblio, CERMINE, Citation, Citation-Parser, GROBID, ParsCit, PDFSSA4MET, Reference Tagger, and Science Parse. We evaluate ParsRec on 105k references from chemistry. We propose two approaches to meta-learning recommendations. The first approach learns the best parser for an entire reference string. The second approach learns the best parser for each metadata type in a reference string. The second approach achieved a 2.6% increase in F1 (0.909 vs. 0.886) over the best single parser (GROBID), reducing the false positive rate by 20.2% (0.075 vs. 0.094), and the false negative rate by 18.9% (0.107 vs. 0.132).</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>Bibliographic reference parsing is a well-known task in scientific information extraction and document engineering. In reference parsing, the input is a single reference string, formatted in a specific bibliography style (Fig. <ref type="figure">1</ref>). The output is a machinereadable representation of the input string, typically called a parsed reference (Fig. <ref type="figure" target="#fig_0">2</ref>).</p><p>A parsed reference is a collection of metadata fields, each of which is composed of a metadata type (e.g. "year" or "conference") and value (e.g. "2018" or "AICS").</p><p>Bibliographic reference parsing is useful for identifying cited documents, also known as citation matching <ref type="bibr" target="#b1">[2]</ref>. Citation matching is required for assessing the impact of researchers <ref type="bibr" target="#b2">[3]</ref>, journals <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b4">5]</ref> and research institutions <ref type="bibr" target="#b5">[6]</ref>, and for calculating document similarity <ref type="bibr" target="#b6">[7,</ref><ref type="bibr" target="#b7">8]</ref>, in the context of academic search engines <ref type="bibr" target="#b8">[9,</ref><ref type="bibr" target="#b9">10]</ref> and recommender systems <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b11">12]</ref>. Fig. <ref type="figure">1</ref>. An example bibliographic reference string that could be the input of reference parsing. The marked metadata fields are of types: author name (2 fields), title, journal, volume, issue, year, pages. There exist many ready-to-use open-source reference parsers. Recently we compared the performance of ten open source parsers <ref type="bibr" target="#b12">[13]</ref>: Anystyle-Parser, Biblio, CERMINE, Citation, Citation-Parser, GROBID, ParsCit, PDFSSA4MET, Reference Tagger and Science Parse. The overall parsing results varied greatly, with F1 ranging from 0.27 for Citation-Parser to 0.89 for GROBID. Our results also showed that different tools have different strengths and weaknesses. For example, ParsCit is ranked 3rd in the overall ranking but is best for extracting author names. Science Parse, ranked 4th overall, is best in extracting the year. These results suggest that there is no single best parser. Instead, different parsers might give the best results for different metadata types and different reference strings. Consequently, we hypothesize that if we were able to accurately choose the best parser for a given scenario, the overall quality of the results should increase. This can be seen as a typical recommendation problem: a user (e.g. a software developer or a researcher) needs the item (reference parser) that satisfies the user's needs best (high quality of metadata fields extracted from reference strings).</p><p>In this paper we propose ParsRec, a novel meta-learning recommender system for bibliographic reference parsers. ParsRec takes as input a reference string, identifies the potentially best reference parser(s), applies the chosen parser(s), and outputs the metadata fields. ParsRec is built upon ten open-source parsers mentioned before. ParsRec uses supervised machine learning to recommend the best parser(s) for the input reference string. The novel aspects of ParsRec are: 1) considering reference parsing as a recommendation problem, 2) using a meta learning-based hybrid approach for reference parsing.</p><p>This paper is an extended version of a poster published at the 12 th ACM Conference on Recommender Systems 2018 (RecSys) <ref type="bibr" target="#b0">[1]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Related Work</head><p>Reference parsers often use regular expressions, hand-crafted rules, and template matching (Biblio [14], Citation [15], Citation-Parser <ref type="bibr" target="#b13">[16]</ref>, PDFSSA4MET <ref type="bibr" target="#b14">[17]</ref>, and BibPro <ref type="bibr" target="#b15">[18]</ref>). Typically the most effective approach for reference parsing is supervised machine learning, such as Conditional Random Fields (ParsCit <ref type="bibr" target="#b16">[19]</ref>, GROBID <ref type="bibr" target="#b17">[20]</ref>, CERMINE <ref type="bibr" target="#b18">[21]</ref>, Anystyle-Parser <ref type="bibr" target="#b19">[22]</ref>, Reference Tagger <ref type="bibr" target="#b20">[23]</ref> and Science Parse <ref type="bibr" target="#b21">[24]</ref>), or Recurrent Neural Networks combined with Conditional Random Fields (Neural ParsCit <ref type="bibr" target="#b22">[25]</ref>). To the best of our knowledge, all open-source reference parsers are based on a single technique, none of them uses any ensemble, hybrid or metalearning techniques. Some reference parsers are parts of larger systems for information extraction from scientific papers. These systems automatically extract machine-readable information, such as metadata, bibliography, logical structure, or fulltext, from unstructured documents. Examples include PDFX <ref type="bibr" target="#b23">[26]</ref>, ParsCit <ref type="bibr" target="#b24">[27]</ref>, GROBID <ref type="bibr" target="#b17">[20]</ref>, CERMINE <ref type="bibr" target="#b18">[21,</ref><ref type="bibr" target="#b25">28]</ref>, Icecite <ref type="bibr" target="#b26">[29,</ref><ref type="bibr" target="#b27">30]</ref> and Team-Beam <ref type="bibr" target="#b28">[31]</ref>.</p><p>Meta-learning is a technique often applied to the problem of algorithm selection <ref type="bibr" target="#b29">[32]</ref>. Meta-learning for algorithm selection allows the training of a model able to automatically select the best algorithm for a given scenario. Meta-learning for algorithm selection has been successfully applied to several areas in natural language processing, for example, to grammatical error correction <ref type="bibr" target="#b30">[33]</ref>, sentiment classification <ref type="bibr" target="#b31">[34]</ref>, and part-of-speech tagging <ref type="bibr" target="#b32">[35]</ref>. To the best of our knowledge, meta-learning has not been applied to reference parsing.</p><p>A very effective family of recommender approaches are hybrid-based approaches, which leverage the strengths of many different recommendation algorithms <ref type="bibr" target="#b33">[36]</ref>. A weighted hybrid combines the output of many recommenders into one final result <ref type="bibr" target="#b34">[37]</ref>. A switching hybrid chooses a single recommender best suited for a given situation <ref type="bibr" target="#b35">[38]</ref>. ParsRec can be seen as a switching hybrid of reference parsers, where the switching is controlled by machine learning.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">ParsRec Approach</head><p>A meta-learning recommender for reference parsers recommends the best parser for a given scenario. There are multiple ways to define a scenario. One aspect to consider is the granularity of the entity, for which we choose a parser. We can recommend the best parser for:</p><p>• a corpus,</p><p>• a document, i.e. its bibliography consisting of a list of reference strings,</p><p>• a single reference string,</p><p>• a metadata type in a reference string, such as title, journal name, or year.</p><p>These four parsing levels can also be combined. For example, a recommender system might recommend a parser for a combination of corpus and metadata type. In this case, one parser would be used to extract the year from all reference strings in corpus A, and another parser would be used to extract the names of the authors from all reference strings in corpus B.</p><p>In this paper, we examine two types of a meta-learning recommender being inspired by <ref type="bibr" target="#b36">[39]</ref>: ParsRecRef recommends a single parser to an entire reference string, and ParsRecField recommends a single parser to a pair of reference string and metadata type. The dataset we used for experiments does not allow for other types of the recommender.</p><p>ParsRecRef chooses one parser for a given reference string. This chosen parser is then responsible for the extraction of all metadata. ParsRecRef works in a few steps (Fig. <ref type="figure" target="#fig_1">3</ref>). First, for each of the ten parsers, ParsRecRef predicts the performance of the parser on the given reference string. Second, ParsRecRef ranks the parsers by their predicted performance. Finally, ParsRecRef chooses the parser that was ranked highest and applies it to the input reference string.</p><p>In ParsRecRef the prediction of the performance of a parser is done by a linear regression model. We train a separate regression model for every parser. Such a model takes as input the vector of features extracted from the reference string and predicts the F1 that the parser will achieve on this reference string. Table <ref type="table" target="#tab_0">1</ref> visualizes the supervised regression problem in ParsRecRef.</p><p>For the sake of the machine learning models, the reference strings have to be represented by vectors of features. The features were engineered to capture the citation style and other information that potentially affects the extraction results. We use two types of features: basic heuristics and n-grams.</p><p>The heuristics-based features include:</p><p>• reference length (1 feature),</p><p>• number and fraction of commas (2 features),</p><p>• number and fraction of dots (2 features),</p><p>• number and fraction of semicolons (2 features),</p><p>• whether the reference starts with square bracket enumeration (e.g. " <ref type="bibr" target="#b1">[2]</ref>") (1 feature), • whether the reference starts with dot enumeration (e.g. "14.") (1 feature).  ). In practice, thousands of distinct n-gram features are generated from the training set, and it is important to select the ones most helpful for the prediction. In our system, we select automatically 150 n-gram features using feature importance, calculated as part of a random forest algorithm trained on the training set <ref type="bibr" target="#b37">[40]</ref>. The response variable in the regression model in ParsRecRef is the F1 metric. F1 measures how well the metadata fields were extracted from the reference string. F1 is the harmonic mean of precision and recall, calculated by comparing the set of extract-ed metadata fields to the set of ground truth metadata fields. An extracted field is correct if both type and value are equal to one of the ground truth fields. Precision is the number of correct fields divided by the total number of extracted fields. Recall is the number of correct fields divided by the total number of ground truth fields.</p><p>ParsRecField chooses the potentially best single parser separately for each metadata type in the input reference string. All chosen parsers are then applied to the input reference string. From each parser, the system takes only those metadata fields, for which this parser was chosen. For example, for a specific reference string, ParsRecField might choose the following parsers: GROBID for extracting authors, title and journal, Science Parse for extracting the year, and CERMINE for volume, issue and pages. In this case, the final metadata fields will contain title field from GROBID, year from Science Parse, etc.</p><p>ParsRecField works in several steps (Fig. <ref type="figure" target="#fig_2">4</ref>). First, ParsRecField iterates over all pairs (parser, metadata type), and for each pair ParsRecField predicts whether the parser will correctly extract the metadata type from the input reference string. Second, for each metadata type, ParsRecField ranks the parsers based on the predicted probability of being correct and chooses the parser ranked most highly. All chosen parsers are applied to the input reference string and the fields are chosen according to the previous choice of the parser. In ParsRecField the prediction of the correctness is done by a binary classifier based on logistic regression. We train a separate classification model for each pair (parser, metadata type). Such a model takes as input the vector of features extracted from the reference string. The features are identical as in the case of ParsRecRef. The model then predicts whether the parser will extract the given metadata field correctly. Apart from a binary classification decision, the logistic regression model outputs the probability of correctness, which is used for ranking. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Methodology</head><p>For the experiments we used a closed dataset that comes from a commercial project described in more detail in <ref type="bibr" target="#b12">[13]</ref>. The dataset is composed of 371,656 reference strings and the corresponding parsed references, extracted from 9,491 documents from chemical domains. The parsed references were manually curated and contain 1.9 million metadata fields. The dataset contains 6 metadata types: author (the name of the first author), source (the source of the referenced document, this can be the name of the journal or the conference, URL or identifier such as arXiv id or DOI), year, volume, issue, and page (the first page of the pages range). Unlike the typical reference parsing task, the title of the referenced document was not required by the client of the business project and is not annotated in the data.</p><p>The data was randomly split in the following way: 40% of the documents for the training of individual parsers (the training set), 30% of the documents for the training of the parser recommender (the meta-learning set), and 30% of the documents for testing (the test set). Since the split was random, it is possible that there were some rare cases of the same reference string used for both training and testing (if it was contained by two different documents).</p><p>The training set will be used in the future for the training of single parsers, to make them work better (this is outside the scope of this paper). The meta-learning set was used for training of the meta-learning recommenders. All parsers were applied to the meta-learning set and evaluated. As a result of the evaluation, we obtained information about which individual metadata fields extracted by the parsers were correct, as well as the overall F1 of each parser on each reference string. This corresponds directly to the data needed for the training of the recommenders (Table <ref type="table" target="#tab_2">1 and Table  2</ref>). Finally, the test set was used for testing and comparisons.</p><p>We compare the proposed approach against three baselines. The first baseline is the best single parser (GROBID). The second baseline, called a hybrid baseline, uses the best parser for each metadata type (i.e. ParsCit for author, Science Parse for year, GROBID for other metadata types). The third baseline is a voting ensemble, in which the final result contains only those metadata fields, that appear in the output of at least three different parsers. We evaluate ParsRec in both versions, ParsRecRef and Pars-RecField. We report the results using precision, recall and F1 calculated for the metadata fields.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Results</head><p>The overall results are presented in Fig. <ref type="figure" target="#fig_3">5</ref>. In general, ParsRecField achieved the best results, outperforming ParsRecRef by 2% (F1 0.909 vs. 0.891). This is most likely caused by ParsRecField being more granular, i.e. it applies parsers separately for different metadata fields, while ParsRecRef treats reference parsing as a single task. 0.132). We also used Student's t-test to statistically compare the mean F1s over the documents in the test set. Both versions of ParsRec achieved statistically significant increase in mean F1 over GROBID (p = 0.0027 for ParsRecRef and p &lt; 0.001 for ParsRecField). These improvements show that the recommender indeed learns useful patterns from the data and is able to recommend parsers well. Both versions of ParsRec also outperform the voting ensemble. While ParsRecRef is only marginally better (F1 0.890 vs. 0.891), ParsRecField achieved a 2.1% increase in F1 (0.909 vs. 0.890). In the case of ParsRecRef, the increase in the mean F1 is not statistically significant. In the case of ParsRecField the increase is significant (p &lt; 0.001).</p><p>Only ParsRecField outperforms the hybrid baseline with a 1.6% increase in F1 (0.909 vs. 0.895). In this case, the increase in the mean F1 is significant (p &lt; 0.001). ParsRecRef is slightly worse than the hybrid baseline. The reason is most likely the fact that the hybrid baseline is more granular than ParsRecRef.</p><p>Fig. <ref type="figure" target="#fig_4">6</ref> shows how often each parser is chosen in each type of ParsRec. In the case of ParsRecRef, the distribution is more skewed. For example, one the two most often chosen parsers (GROBID and CERMINE) is chosen in 88% of cases in ParsRecRef and in 65% of cases in ParsRecField. Also, Science Parse, which is almost never chosen in ParsRecRef, is chosen in 8% of cases in ParsRecField. These results show that choosing a parser for different metadata types individually allows for the more effective use of parsers specializing in certain fields, and gives better results. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusions and Future Work</head><p>The promising results of our evaluation clearly show the potential of the proposed recommender system for reference parsers. Both proposed approaches outperform the best single parser and the voting ensemble, which indicates that the recommender indeed makes useful recommendations. One of the proposed approaches (ParsRecField) also outperforms the hybrid baseline.</p><p>In most cases, the increases in F1 are not large. We suspect the reason for this is not enough diversity, both in the data and among the parsers. The data comes exclusively from chemical papers, which might not include a lot of different reference styles and languages. Six out of 10 parsers use Conditional Random Fields.</p><p>Our plans for the future include training individual parsers, adding more features (related to the language or source of the reference), diversifying the dataset and adding more diverse reference parsers.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. An example of a parsed reference, i.e. a machine-readable representation of the reference string from Fig. 1.</figDesc><graphic coords="2,142.40,442.00,310.26,78.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. The workflow of ParsRecRef. First, the parsers are ranked based on predicted performance on the input reference string. Second, the parser ranked most highly is chosen and applied to the reference string.</figDesc><graphic coords="5,138.65,147.40,317.96,182.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 4 .</head><label>4</label><figDesc>Fig. 4. The workflow of ParsRecField. In this case, separate parser rankings are calculated for each metadata field. All parsers ranked most highly are then applied to the input reference string.</figDesc><graphic coords="6,135.65,387.40,323.94,227.10" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Fig. 5 .</head><label>5</label><figDesc>Fig. 5. The comparison of the results of three baselines and two variations of ParsRec. Both variations of ParsRec outperform the best single parser (GROBID). ParsRecRef achieved a 0.6% increase in F1 (0.891 vs. 0.886), reducing the false positive rate by 3.2% (0.091 vs. 0.095), and the false negative rate by 3.8% (0.127 vs. 0.132). ParsRecField achieved a 2.6% increase in F1 (0.909 vs. 0.886), reducing the false positive rate by 20.2% (0.075 vs. 0.094), and the false negative rate by 18.9% (0.107 vs.</figDesc><graphic coords="8,124.70,391.54,344.25,206.55" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 6 .</head><label>6</label><figDesc>Fig. 6. The distributions of recommended parsers in two types of ParsRec.</figDesc><graphic coords="9,124.70,399.40,345.00,207.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>The visualization of the regression problem in ParsRecRef. Each row represents a single reference string. The response variable is the expected F1 of extracted metadata fields. Each parser uses a separate table with the same features and parser-specific response</figDesc><table><row><cell>Features</cell></row></table><note>N-gram features are binary features corresponding to 3-and 4-grams extracted from the reference string. The terms in n-grams are classes of words, such as number, capitalized word, comma, etc. These features capture style-characteristic sequences of token classes. Example features include: number-comma-number (matching e.g. "3, 12"), capitalized word-comma-uppercase letter-dot (matching e.g. "Springsteen, B."), number-left parenthesis-number-right parenthesis (matching e.g. "5 (28)"</note></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2</head><label>2</label><figDesc>visualizes the classification problem in ParsRecField.</figDesc><table /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 2 .</head><label>2</label><figDesc>The classification problem in ParsRecField. Each row represents a single reference string. The response variable corresponds to "is the metadata type extracted correctly". Each pair (parser, metadata type) uses a separate table.</figDesc><table><row><cell>Features</cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgements</head><p>This research was conducted in collaboration with and part-funded by Iconic Translation Machines Ltd. with additional financial support from Science Foundation Ireland (SFI) under Grant Number 13/RC/2106. The project has also received funding from the European Union's Horizon 2020 research and innovation programme under the Marie Sklodowska-Curie grant agreement No 713567.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">ParsRec: Meta-Learning Recommendations for Bibliographic Reference Parsing</title>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Sheridan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Late-Breaking Results track part of the Twelfth ACM Conference on Recommender Systems (RecSys &apos;18)</title>
				<meeting>the Late-Breaking Results track part of the Twelfth ACM Conference on Recommender Systems (RecSys &apos;18)<address><addrLine>Vancouver, BC, Canada</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Large Scale Citation Matching Using Apache Hadoop</title>
		<author>
			<persName><forename type="first">M</forename><surname>Fedoryszak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Bolikowski</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Theory and Practice of Digital Libraries (TPDL)</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">An index to quantify an individual&apos;s scientific research output that takes into account the effect of multiple coauthorship</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Hirsch</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scientometrics</title>
		<imprint>
			<biblScope unit="volume">85</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="741" to="754" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">A Hirsch-type index for journals</title>
		<author>
			<persName><forename type="first">T</forename><surname>Braun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Glänzel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Schubert</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scientometrics</title>
		<imprint>
			<biblScope unit="volume">69</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="169" to="173" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A new approach to the metric of journals&apos; scientific prestige: The SJR indicator</title>
		<author>
			<persName><forename type="first">B</forename><surname>González-Pereira</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">P</forename><surname>Guerrero Bote</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>De Moya Anegón</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. Informetrics</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="379" to="391" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">A methodology for Institution-Field ranking based on a bidimensional analysis: the IFQ2A index</title>
		<author>
			<persName><forename type="first">D</forename><surname>Torres-Salinas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">G</forename><surname>Moreno-Torres</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">D</forename><surname>López-Cózar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Herrera</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scientometrics</title>
		<imprint>
			<biblScope unit="volume">88</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="771" to="786" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Document-document similarity approaches and science mapping: Experimental comparison of five approaches</title>
		<author>
			<persName><forename type="first">P</forename><surname>Ahlgren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Colliander</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J. Informetrics</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="49" to="63" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Virtual Citation Proximity (VCP): Calculating Co-Citation-Proximity-Based Document Relatedness for Uncited Documents with Machine Learning</title>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
	<note>Proposal</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">CiteSeerX: AI in a Digital Library Search Engine</title>
		<author>
			<persName><forename type="first">J</forename><surname>Wu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">M</forename><surname>Williams</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H.-H</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Khabsa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Caragea</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Tuarob</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ororbia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Jordan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Mitra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">L</forename><surname>Giles</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">AI Magazine</title>
		<imprint>
			<biblScope unit="volume">36</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="35" to="48" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">Explicit Semantic Ranking for Academic Search via Knowledge Graph Embedding</title>
		<author>
			<persName><forename type="first">C</forename><surname>Xiong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Power</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Callan</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>WWW</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">DLib: Recommendations-as-a-Service (RaaS) for Academia</title>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Aizawa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Breitinger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Gipp</surname></persName>
		</author>
		<author>
			<persName><surname>Mr</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>JCDL</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Research-paper recommender systems: a literature survey</title>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Gipp</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Langer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Breitinger</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Int. J. on Digital Libraries</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<biblScope unit="page" from="305" to="338" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Machine Learning vs. Rules and Out-ofthe-Box vs. Retrained: An Evaluation of Open-Source Bibliographic Reference and Citation Parsers</title>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Collins</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Sheridan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL)</title>
				<meeting>ACM/IEEE-CS Joint Conference on Digital Libraries (JCDL)</meeting>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<ptr target="https://github.com/manishbisht/Citation-Parser" />
		<title level="m">Citation-Parser</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">PDFSSA4MET</title>
		<ptr target="https://github.com/eliask/pdfssa4met" />
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">BibPro: A Citation Parser Based on Sequence Alignment</title>
		<author>
			<persName><forename type="first">C.-C</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K.-H</forename><surname>Yang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C.-L</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J.-M</forename><surname>Ho</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Trans. Knowl. Data Eng</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="236" to="250" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">ParsCit: an open-source CRF reference string parsing package</title>
		<author>
			<persName><forename type="first">I</forename><surname>Councill</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Giles</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M.-Y</forename><surname>Kan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Language Resources and Evaluation</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">GROBID: combining automatic bibliographic data recognition and term extraction for scholarship publications</title>
		<author>
			<persName><forename type="first">P</forename><surname>Lopez</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Research and Advanced Technology for Digital Libraries</title>
		<imprint>
			<biblScope unit="page" from="473" to="474" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">CERMINE: automatic extraction of structured metadata from scientific literature</title>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Szostek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Fedoryszak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Dendek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Bolikowski</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal on Document Analysis and Recognition</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="317" to="335" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Anystyle-Parser</title>
		<ptr target="https://github.com/inukshuk/anystyle-parser" />
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<monogr>
		<title level="m" type="main">Reference Tagger</title>
		<ptr target="https://github.com/rmcgibbo/reftagger" />
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<monogr>
		<ptr target="https://github.com/allenai/science-parse" />
		<title level="m">Science Parse</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Neural ParsCit: a deep learning-based reference string parser</title>
		<author>
			<persName><forename type="first">A</forename><surname>Prasad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Kaur</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M.-Y</forename><surname>Kan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal on Digital Libraries</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="323" to="337" />
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">PDFX: fully-automated pdf-to-xml conversion of scientific literature</title>
		<author>
			<persName><forename type="first">A</forename><surname>Constantin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Pettifer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Voronkov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ACM Symposium on Document Engineering</title>
				<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="page" from="177" to="180" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Scholarly Document Information Extraction using Extensible Features for Efficient Higher Order Semi-CRFs</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">V</forename><surname>Cuong</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">M</forename><surname>Kumar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M.-Y</forename><surname>Kan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">S</forename><surname>Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">JCDL</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">Extracting Contextual Information from Scientific Literature Using CERMINE System</title>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Bolikowski</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Semantic Web Evaluation Challenges -Second SemWebEval Challenge at ESWC</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">A Benchmark and Evaluation for Text Extraction from PDF</title>
		<author>
			<persName><forename type="first">H</forename><surname>Bast</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Korzen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">JCDL</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">The Icecite Research Paper Management System</title>
		<author>
			<persName><forename type="first">H</forename><surname>Bast</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Korzen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Web Information Systems Engineering</title>
				<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b28">
	<analytic>
		<title level="a" type="main">Teambeam -meta-data extraction from scientific literature</title>
		<author>
			<persName><forename type="first">R</forename><surname>Kern</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Jack</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hristakeva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Granitzer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">DLib Magazine</title>
		<imprint>
			<biblScope unit="volume">18</biblScope>
			<biblScope unit="issue">7/8</biblScope>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<analytic>
		<title level="a" type="main">Metalearning: a survey of trends and technologies</title>
		<author>
			<persName><forename type="first">C</forename><surname>Lemke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Budka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Gabrys</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence Review</title>
		<imprint>
			<biblScope unit="volume">44</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="117" to="130" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b30">
	<analytic>
		<title level="a" type="main">A Meta Learning Approach to Grammatical Error Correctio</title>
		<author>
			<persName><forename type="first">H</forename><surname>Seo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><forename type="middle">G</forename><surname>Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 50th Annual Meeting of the Association for Computational Linguistics: Short Papers -Volume 2</title>
				<meeting>the 50th Annual Meeting of the Association for Computational Linguistics: Short Papers -Volume 2<address><addrLine>Jeju Island, Korea</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b31">
	<analytic>
		<title level="a" type="main">Ensemble Learning for Sentiment Classification</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Su</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Ji</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Wang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Wu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Chinese Lexical Semantics</title>
				<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b32">
	<analytic>
		<title level="a" type="main">Simulated annealing based classifier ensemble techniques: Application to part of speech tagging</title>
		<author>
			<persName><forename type="first">A</forename><surname>Ekbal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Saha</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Fusion</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="288" to="300" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b33">
	<analytic>
		<title level="a" type="main">Hybrid Web Recommender Systems</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">D</forename><surname>Burke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Adaptive Web, Methods and Strategies of Web Personalization</title>
				<imprint>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b34">
	<analytic>
		<title level="a" type="main">Weighted hybrid recommendation for heterogeneous networks</title>
		<author>
			<persName><forename type="first">F</forename><surname>Vahedian</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">RecSys</title>
				<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b35">
	<analytic>
		<title level="a" type="main">Switching hybrid for cold-starting context-aware recommender systems</title>
		<author>
			<persName><forename type="first">M</forename><surname>Braunhofer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Codina</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Ricci</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">RecSys</title>
				<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b36">
	<analytic>
		<title level="a" type="main">One-at-a-time: A Meta-Learning Recommender-System for Recommendation-Algorithm Selection on Micro Level</title>
		<author>
			<persName><forename type="first">A</forename><surname>Collins</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Beel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Tkaczyk</surname></persName>
		</author>
		<idno>. abs/1805.12118</idno>
	</analytic>
	<monogr>
		<title level="j">CoRR</title>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b37">
	<analytic>
		<title level="a" type="main">Random Forests</title>
		<author>
			<persName><forename type="first">L</forename><surname>Breiman</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Machine Learning</title>
		<imprint>
			<biblScope unit="volume">45</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="5" to="32" />
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

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