<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd">
<article article-type="research-article" dtd-version="3.0" xml:lang="en" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
	
	<front>
		
		<journal-meta>
			<journal-id journal-id-type="publisher-id">REDC</journal-id>
			<journal-title-group>
				<journal-title>Revista Espa&#x00F1;ola de Documentaci&#x00F3;n Cient&#x00ED;fica</journal-title>
				<abbrev-journal-title>Rev. Esp. Doc. Cient.</abbrev-journal-title>
			</journal-title-group>
			<issn pub-type="ppub">0210-0614</issn>
			<issn pub-type="epub">1988-4621</issn>
			<publisher>
				<publisher-name>Consejo Superior de Investigaciones Cient&#x00ED;ficas</publisher-name>
			</publisher>
		</journal-meta>
		
		<article-meta>
			<article-id pub-id-type="publisher-id">redc.2017.4.1500</article-id>
			<article-id pub-id-type="doi">10.3989/redc.2017.4.1500</article-id>
			
			<article-categories>
				<subj-group subj-group-type="heading">
				<subject>ESTUDIOS / RESEARCH STUDIES</subject>
				</subj-group>
			</article-categories>
			
			<title-group>
				<article-title>Google Scholar as a source for scholarly evaluation: a bibliographic review of database errors</article-title>
				<trans-title-group xml:lang="es">
				<trans-title>Google Scholar como una fuente de evaluaci&#x00F3;n cient&#x00ED;fica: una revisi&#x00F3;n bibliogr&#x00E1;fica sobre errores de la base de datos</trans-title>
				</trans-title-group>
				<alt-title alt-title-type="running-head">Google Scholar as a source for scholarly evaluation: a bibliographic review of database errors</alt-title>
			</title-group>
			
			<contrib-group>
		
				<contrib contrib-type="author" corresp="yes">
					<name>
					 <surname>Orduna-Malea</surname>
					 <given-names>Enrique</given-names>
					</name>
					<xref ref-type="aff" rid="U1"/>
					<xref ref-type="corresp" rid="cor1"/>
				</contrib>
				
				<contrib contrib-type="author" corresp="yes">
					<name>
					 <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					 <given-names>Alberto</given-names>
					</name>
					<xref ref-type="aff" rid="U2"/>
					<xref ref-type="corresp" rid="cor2"/>
				</contrib>
				
				<contrib contrib-type="author" corresp="yes">
					<name>
					 <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					 <given-names>Emilio</given-names>
					</name>
					<xref ref-type="aff" rid="U3"/>
					<xref ref-type="corresp" rid="cor3"/>
				</contrib>
			
			</contrib-group>
			
			<aff id="U1">Universitat Polit&#x00E8;cnica de Val&#x00E8;ncia</aff>
			<aff id="U2">Facultad de Comunicaci&#x00F3;n y Documentaci&#x00F3;n. Universidad de Granada</aff>
			<aff id="U3">Facultad de Comunicaci&#x00F3;n y Documentaci&#x00F3;n. Universidad de Granada</aff>
			
			<author-notes>
				<corresp id="cor1">e-mail: <email xlink:href="enorma@upv.es">enorma@upv.es</email>
					ORCID iD: <ext-link ext-link-type="uri" xlink:href="http://orcid.org/0000-0002-1989-8477">http://orcid.org/0000-0002-1989-8477</ext-link>
				</corresp>
				
				<corresp id="cor2">e-mail: <email xlink:href="albertomartin@ugr.es">albertomartin@ugr.es</email>
					ORCID iD: <ext-link ext-link-type="uri" xlink:href="http://orcid.org/0000-0002-0360-186X">http://orcid.org/0000-0002-0360-186X</ext-link>
				</corresp>
				
				<corresp id="cor3">e-mail: <email xlink:href="edelgado@ugr.es">edelgado@ugr.es</email>
					ORCID iD: <ext-link ext-link-type="uri" xlink:href="http://orcid.org/0000-0002-8184-551X">http://orcid.org/0000-0002-8184-551X</ext-link>
				</corresp>
			</author-notes>
			
			<pub-date pub-type="epub">
				<day>31</day>
				<month>12</month>
				<year>2017</year>
			</pub-date>
			
			<pub-date pub-type="collection">
			<year>2017</year>
			</pub-date>
			
			<volume>40</volume>
			<issue>4</issue>
		
			<elocation-id>e185</elocation-id>
		
			<history>
			
				<date date-type="received">
					<day>17</day>
					<month>07</month>
					<year>2017</year>
				</date>

				<date date-type="accepted">
					<day>08</day>
					<month>09</month>
					<year>2017</year>
				</date>
			</history>
		 
			<permissions>
				<copyright-statement>&#x00A9; 2017 CSIC</copyright-statement>
				<copyright-year>2017</copyright-year>
				<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/3.0/es/deed.en">
					<license-p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY) Spain 3.0.</license-p>
				</license>
			</permissions>
		
			
			<abstract xml:lang="en">
			<title>ABSTRACT</title>
			<p>Google Scholar (GS) is an academic search engine and discovery tool launched by Google (now Alphabet) in November 2004. The fact that GS provides the number of citations received by each article from all other indexed articles (regardless of their source) has led to its use in bibliometric analysis and academic assessment tasks, especially in social sciences and humanities. However, the existence of errors, sometimes of great magnitude, has provoked criticism from the academic community. The aim of this article is to carry out an exhaustive bibliographical review of all studies that provide either specific or incidental empirical evidence of the errors found in Google Scholar. The results indicate that the bibliographic corpus dedicated to errors in Google Scholar is still very limited (n= 49), excessively fragmented, and diffuse; the findings have not been based on any systematic methodology or on units that are comparable to each other, so they cannot be quantified, or their impact analysed, with any precision. Certain limitations of the search engine itself (time required for data cleaning, limit on citations per search result and hits per query) may be the cause of this absence of empirical studies.</p>
			</abstract>
						
			<trans-abstract xml:lang="es">
			<title>RESUMEN</title>
			<p>Google Scholar es un motor de b&#x00FA;squeda acad&#x00E9;mico y herramienta de descubrimiento lanzada por Google (ahora Alphabet) en noviembre de 2004. El hecho de que para cada registro bibliogr&#x00E1;fico se proporcione informaci&#x00F3;n acerca del n&#x00FA;mero de citas recibidas por dicho registro desde el resto de registros indizados en el sistema (independientemente de su fuente) ha propiciado su utilizaci&#x00F3;n en an&#x00E1;lisis bibliom&#x00E9;tricos y en procesos de evaluaci&#x00F3;n de la actividad acad&#x00E9;mica, especialmente en Ciencias Sociales y Humanidades. No obstante, la existencia de errores, en ocasiones de gran magnitud, ha provocado su rechazo y cr&#x00ED;tica por una parte de la comunidad cient&#x00ED;fica. Este trabajo pretende precisamente realizar una revisi&#x00F3;n bibliogr&#x00E1;fica exhaustiva de todos los estudios que de forma monogr&#x00E1;fica o colateral proporcionan alguna evidencia emp&#x00ED;rica sobre cu&#x00E1;les son los errores cometidos por Google Scholar (y productos derivados, como Google Scholar Metrics y Google Scholar Citations). Los resultados indican que el corpus bibliogr&#x00E1;fico dedicado a los errores en Google Scholar es todav&#x00ED;a escaso (n= 49), excesivamente fragmentado, disperso, con resultados obtenidos sin metodolog&#x00ED;as sistem&#x00E1;ticas y en unidades no comparables entre s&#x00ED;, por lo que su cuantificaci&#x00F3;n y su efecto real no pueden ser caracterizados con precisi&#x00F3;n. Ciertas limitaciones del propio buscador (tiempo requerido de limpieza de datos, l&#x00ED;mite de citas por registro y resultados por consulta) podr&#x00ED;an ser la causa de esta ausencia de trabajos emp&#x00ED;ricos.</p>
			</trans-abstract>
			
			<kwd-group xml:lang="en">
				<title>KEYWORDS</title> 
				<kwd>Google Scholar</kwd>
				<kwd>Academic search engines</kwd>
				<kwd>Bibliographic databases</kwd>
				<kwd>Errors</kwd>
				<kwd>Quality</kwd>
			</kwd-group>
			
			<kwd-group xml:lang="es"> 
				<title>PALABRAS CLAVE</title> 
				<kwd>Google Scholar</kwd>
				<kwd>Motores de b&#x00FA;squeda acad&#x00E9;micos</kwd>
				<kwd>Bases de datos bibliogr&#x00E1;ficas</kwd>
				<kwd>Errores</kwd>
				<kwd>Calidad</kwd>
			</kwd-group>
		
		</article-meta>
	</front>
	
	<body>

		<sec id="S1">
			<title>1. INTRODUCTION</title>

			<sec id="S1.1">
			<title>The launch of a new tool </title>

			<p>Google Scholar (GS) is an academic search engine created by Google Inc. (now Alphabet) on 18 November 2004, and its main purpose is to provide “a simple way to broadly search for scholarly literature” and to help users to “find relevant work across the world of scholarly research”.<xref ref-type="fn" rid="NOTE1">1</xref></p>

			<p>The way it functions is similar to the general Google search engine in that it is a system based on providing the best possible results to user queries entered into a stripped-down search box (Ortega, <xref ref-type="bibr" rid="CIT71">2014</xref>). In the case of GS, it returns results for millions of academic documents (abstracts, articles, theses, books, book chapters, conference papers, technical reports or their drafts, pre-prints, post-prints, patents and court opinions) that the Google Scholar crawlers automatically locate in the academic web space: from academic publishers, universities, scientific and professional societies, to any website containing academic material (Orduna-Malea et al., <xref ref-type="bibr" rid="CIT69">2016</xref>).</p>

			<p>As with Google, the results retrieved for a particular query are ranked by an algorithm that takes into account a large number of variables (where it was published, who it was written by, how often and how recently it has been cited in other scholarly literature, etc.), although the exact components of this algorithm and the weight of each variable is unknown, for industrial property reasons. However, several empirical studies have demonstrated that the number of citations received by a document is one of the key ranking factors (Beel and Gipp, <xref ref-type="bibr" rid="CIT11">2009</xref>; Mart&#x00ED;n-Mart&#x00ED;n et al., <xref ref-type="bibr" rid="CIT60">2017</xref>). Another essential feature of Google Scholar is that the entire process is automated, without any human intervention, from the location of documents (crawling) to the bibliographic description (metadata parsing) and the extraction of the bibliographic references (reference parsing) that are used to compute the number of citations received by each retrieved document from all other documents.</p>

			<p>Google Scholar was not the first tool of this type; other pioneering systems had already appeared on the scene (Citeseer, the first version of which dates from 1997, is considered the first academic search engine). However, the fact that it was developed under the umbrella of a company like Google, and used part of its technology, led to immediate acceptance by a significant proportion of the academic publishing world and by some professionals and researchers, a fact that was widely criticised by Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT36">2006a</xref>), who openly mocked this new state of affairs (“As Google wandered into the territory by launching Google Scholar (GS) at the end of 2004, the topic is expected to appear in the ultra-light morning television chat shows run by ultra-light TV personalities who are meant to light up our mornings”).</p>

			<p>Given the characteristics of Google Scholar, it can and should be studied from two complementary but different angles (not only its characteristics but also its effects and consequences). Firstly, GS may be evaluated as a discovery tool (Breeding, <xref ref-type="bibr" rid="CIT15">2015</xref>), that is, a search engine the purpose of which is to provide the best results to each query and a pleasant user experience based on usability, ease of use and, above all, speed (Bosman et al., <xref ref-type="bibr" rid="CIT14">2006</xref>). Secondly, Google Scholar may be analysed as a tool that can be used to evaluate scholarly activity. This use, which came about due to it providing citation figures for each document indexed by the system, has led to the increasing use of Google Scholar by users (teachers, researchers, students) and professionals (companies, assessment bodies) as a bibliometric tool for various evaluation processes (authors, journals, universities), although it was not designed with this purpose in mind and lacked the required basic functions (Torres-Salinas et al., <xref ref-type="bibr" rid="CIT84">2009</xref>). It is precisely this aspect (Google Scholar as a valid tool for carrying out bibliometric studies) that the objectives of this bibliographic review will be based on.</p>

			</sec>
			
			<sec id="S1.2">
			<title>The launch of a new debate </title>

			<p>The debate about the advantages and disadvantages of using Google Scholar began immediately after it first appeared (November 2004), giving rise to good and bad criticism in equal measure, as Giles (<xref ref-type="bibr" rid="CIT24">2005</xref>) pointed out in his column in <italic>Nature</italic>. The first analyses of Google Scholar came from technology blogs and websites, such as Sullivan’s (<xref ref-type="bibr" rid="CIT81">2004</xref>) more neutral and informative piece for <italic>Search Engine Watch</italic> (<ext-link ext-link-type="uri" xlink:href="https://searchenginewatch.com">https://searchenginewatch.com</ext-link>), or Kennedy and Price’s (<xref ref-type="bibr" rid="CIT49">2004</xref>) more sensationalist piece for the now-defunct <italic>Resource Shelf</italic>, affirming that “as you’ve read here many times, Google is brilliant (that is, ingenious at marketing and trying new things), and this is yet another example of their savvy”. These messages propagated fast on the internet.</p>

			<p>In spite of the general enthusiasm, critical voices soon made themselves heard, one of whom was P&#x00E9;ter Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT32">2004</xref>), who tested the search engine between 18 and 27 November 2004, publishing his findings informally on a blog.<xref ref-type="fn" rid="NOTE2">2</xref> In his study, Professor Jacs&#x00F3;, a specialist on database evaluation with extensive experience, conducted an analysis of the general coverage of various publishers on Google Scholar using the “site” command, and identified a number of important limitations, leading him to conclude that “Google Scholar needs much refinement in collecting, filtering, processing and presenting this valuable data” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT32">2004</xref>). The issues identified by Jacs&#x00F3; included unfriendly search syntax, little or no information about the features of the search engine, and inconsistent results. He found specific errors, such as the way in which it displayed results in which there were changes in the word order of the title, or generated completely erroneous bibliographic descriptions (the book, <italic>Computers and Intractability</italic>, by Garey and Johnson, detected errors and inconsistencies in the title, subtitle, author names, publisher’s names, locations and years). He also noted a wide range of additional errors like inflated hit counts, inflated citedness, full-text links pointing to erroneous documents and unmerged document versions.</p>

			<p>At that precise moment, and in the wake of Jacso’s criticism, a wave of criticism was directed against the general drawbacks of Google Scholar (Price, <xref ref-type="bibr" rid="CIT76">2004</xref>; Goodman, <xref ref-type="bibr" rid="CIT25">2004</xref>; Abram, <xref ref-type="bibr" rid="CIT01">2005</xref>; Gardner and Eng, <xref ref-type="bibr" rid="CIT23">2005</xref>; Notess, <xref ref-type="bibr" rid="CIT65">2005</xref>; Ojala, <xref ref-type="bibr" rid="CIT68">2005</xref>; Vine, <xref ref-type="bibr" rid="CIT88">2005</xref>; Wleklinski, <xref ref-type="bibr" rid="CIT91">2005</xref>; Adlington and Benda, <xref ref-type="bibr" rid="CIT02">2006</xref>; White, <xref ref-type="bibr" rid="CIT90">2006</xref>), alongside more neutral articles, such as the study published by Noruzi (<xref ref-type="bibr" rid="CIT64">2005</xref>), that, while acknowledging its many drawbacks, also pointed to its potential benefits and possible improvements. At the same time, other articles adopted a markedly neutral attitude towards GS. These included the columns by Butler (<xref ref-type="bibr" rid="CIT16">2004</xref>) in <italic>Nature</italic> and Leslie (<xref ref-type="bibr" rid="CIT50">2004</xref>) in <italic>Science</italic>, brief news features that did not discuss or even mention critical aspects, perhaps due in part to the fact that both the Nature Publishing Group and the American Association for the Advancement of Science (AAAS), the publishers of <italic>Nature</italic> and <italic>Science</italic>, respectively, had reached agreements to provide access to the full text of their publications to Google Scholar crawlers.</p>

			<p>On the other hand, the paper published by Belew (<xref ref-type="bibr" rid="CIT12">2005</xref>) was a significant departure in the debate about the value of Google Scholar. This author analysed a corpus of 203 publications concluding that, surprisingly, there was a high correlation between the citations received by these documents according to Google Scholar and to ISI (the author did not indicate what exact database he used or the discipline to which the documents belonged, simply that six authors from the same interdisciplinary department had been chosen at random; in any case, the use of WoS may be surmised in the area of computer science). Similarly, Pauly and Stergiou (<xref ref-type="bibr" rid="CIT73">2005</xref>) conducted a citation analysis on a corpus of 114 articles from a wide range of disciplines (mathematics, chemistry, physics, computing sciences, molecular biology, ecology, fisheries, oceanography, geosciences, economics, and psychology), and also observed a high correlation (R<sup>2</sup> = 0.994 for articles published from 2000 to 2004), which led them to affirm that “GS can substitute for ISI”, and that “GS may gradually outperform ISI given its potentially broader base of citing articles”. Finally, that same year, the seminal article by Bauer and Bakkalbasi (<xref ref-type="bibr" rid="CIT10">2005</xref>) appeared, an analysis published in D-Lib in which they compared “the citation counts provided by WoS, Scopus, and Google Scholar for articles from the <italic>Journal of the American Society for Information Science and Technology</italic> (<italic>JASIST</italic>) published in 1985 and in 2000”. This study concluded that for articles published in 2000, Google Scholar provided statistically significant higher citation counts than either Web of Science or Scopus, and was significant because the authors brought to light the importance that citation analysis had acquired, not only for crawling academic publications or measuring their impact, but also for justifying tenure and funding decisions, underlining the future role that GS could play in this complex matter. Indeed, in the light of Bauer and Bakkalbasi’s article, <italic>The Scientist</italic> devoted an article to the future of citation analysis and the role that the web in general and GS in particular could play in bibliometric analysis (Perkel, <xref ref-type="bibr" rid="CIT74">2005</xref>).</p>

			<p>Jacs&#x00F3;’s response to these articles was not long in coming; he lambasted them in a column published in <italic>Online Information Review</italic> (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT36">2006a</xref>). First, he declared his utter disagreement with Butler, claiming that he did not seem to have understood his illustrative examples of Google Scholar’s errors, “even if my examples were as much tailor-made for <italic>Nature</italic> as bespoke suits by Savile Row tailors for the ultra rich”. Second, he warned readers not to limit their reading to Belew’s work. Third, with respect to Pauly and Stergiou, he openly criticised their claim that GS can replace ISI, particularly since their claim was arrived at by “handpicking” only a few articles, without filtering or even cleaning them up, and they contained numerous errors in the form of inflated and phantom citation counts. Two years later, Harzing and Van der Wal (<xref ref-type="bibr" rid="CIT30">2008</xref>) criticised Jacs&#x00F3; for his criticisms of Pauly and Stergiou in a seminal article published in the same journal in which these authors published their earlier article (<italic>Ethics in Science and Environmental Politics</italic>). They accused Jacs&#x00F3; of also “handpicking” examples of errors, with few and unrepresentative samples, and while they did acknowledge the errors pointed out by Jacs&#x00F3;, these errors were basically inconsistencies in the results for specific queries.</p>

			<p>Lastly, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT36">2006a</xref>) acknowledged the validity of Bauer and Bakkalbasi’s findings, although he recommended that readers take a critical look at the volume of citations not only in the 2000 sample (where GS was superior to WoS), but also in the 1985 sample (where WoS outperformed GS), data that seemed to have been overlooked by the academic community, which was more interested in highlighting only the positive aspects of GS and hiding or minimising its limitations, according to Jacs&#x00F3;.</p>

			<p>From that moment, and in the same column in <italic>Online Information Review</italic> (called <italic>Savvy Searching</italic>), P&#x00E9;ter Jacs&#x00F3; published a series of articles from 2006 to 2012 aimed at identifying, describing, categorising and denouncing the many errors and limitations of Google Scholar (listed in Appendix I, along with various data related to the errors identified and samples used in each study). Much of his research was also published on his personal website (www.jacso.info), as a way of archiving the evidence.</p>

			<p>In spite of the strong and harsh criticism that he then fired off from his platform on <italic>Online Information Review</italic> (some of his most vehement remarks are listed in <xref ref-type="table" rid="T1">Table I</xref>), and which will be described in detail in the following sections, Jacs&#x00F3; was always rigorous, admitting that Google Scholar is an excellent tool for locating documents that might not be accessible through traditional databases, as well as for accessing full texts (i.e. as a discovery tool). However, “using it for bibliometric or scientometric purposes, such as for determining the h-index of a person or a journal, is another question” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT40">2008c</xref>). This fact led him to criticise colleagues that used Google Scholar for said purposes even if they did admit the limitations of the database. For example, Bar-Ilan (<xref ref-type="bibr" rid="CIT08">2008</xref>), in her study of highly-cited Israeli authors, admitted that “the sources and the validity of the citations in GS were not examined in this study”. In the light of this observation, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) raised his dissenting voice, although he did qualify his position with an understanding that it is sometimes not only tedious but impossible to verify the origin and validity of the citations due to the system’s significant limitations, laconically concluding, “I cannot blame her and others who accept the citation counts as reported by GS”.</p>
			
						<fig id="T1">
							<label>Table I</label>
							<caption>
								<title>Mythical quotes by P&#x00E9;ter Jacs&#x00F3; in the column “Savvy Searching” in Online Information Review</title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T1.jpg"/>
						</fig>

			<p>The debate came to a head in 2012 when a controversial article published by Jerome K. Vanclay (<xref ref-type="bibr" rid="CIT85">2012</xref>) in the journal <italic>Scientometrics</italic> strongly criticised the Impact Factor and advocated the use of alternative sources for the evaluation of journals, including Google Scholar. The controversy was heightened all the more by the tone employed by Vanclay. Therefore, Tibor Braun (the founder and editor-in-chief of <italic>Scientometrics</italic> at the time) invited Jacs&#x00F3; to reply (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT46">2012b</xref>). Jacso’s criticisms were extremely strong (“utterly demagogue rhetoric, featuring false accusations, misleading statements, claims and comparisons, delusional ideas, arrogance and ignorance in the Vanclay-set”), so much so that he even questioned the review and publication process (“part of a mock-up scenario to test how poorly researched, prejudiced, biased, duplicate papers using ‘flawed methodology’, ignorant arguments, erroneous calculations, loaded rhetoric, and misleading examples can get through the current quality filters of editorial preview and peer reviews”).</p>

			<p>The ideas of Vanclay (<xref ref-type="bibr" rid="CIT85">2012</xref>) were equally criticised by Butler (<xref ref-type="bibr" rid="CIT17">2011</xref>) and by Bensman (<xref ref-type="bibr" rid="CIT13">2012</xref>), who highlighted Vanclay’s lack of knowledge about the workings and purposes of the WoS and JCR databases, and his excessive idealism in the “promise of a far better assessment of research/publication performance through the h-index based on GS”.</p>

			<p>Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT46">2012b</xref>) once again reiterated that his criticism of Google Scholar was not directed towards its undoubted advantages for thematic searches, but towards its serious limitations, which make it inappropriate for bibliometric analysis (“extremely lenient citation matching algorithm”), an aspect with which Aguillo (<xref ref-type="bibr" rid="CIT05">2012</xref>) also concurred. In particular, Jacs&#x00F3; argued that the adulation shown by the bibliometric community towards Google Scholar is due in part to the fact that it retrieves a greater number of publications and citations and, consequently, a higher h-index than many researchers would deserve. This may have a perverse effect on the evaluation of the quantity and quality of publications in “decisions related to tenure, promotion and grant applications of individual researchers and research groups, as well as in journal subscriptions and cancellations” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT47">2012c</xref>).</p>

			</sec>
			
			<sec id="S1.3">
			<title>The evolution of an – already old – debate</title>

			<p>Between 2004 and 2008, criticism of Google Scholar was largely sustained by Jacs&#x00F3;’s articles. However, other authors also expressed their reservations about this search engine, particularly because of the lack of improvements and updates, as Gregg Notess in 2008 noted in the forum <italic>Search Engine Showdown</italic>.<xref ref-type="fn" rid="NOTE3">3</xref> At around the same time, a report by the consulting firm comScore, published by the prestigious technology blog <italic>Techcrunch</italic>,<xref ref-type="fn" rid="NOTE4">4</xref> reported a fall in the number of unique visitors to Google Scholar during the November 2006 to November 2007 period. This news was picked up on by Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>), although there was no mention of the fact that the Google Scholar team seemed to have declared unofficially that these numbers were not correct (a fact that was mentioned by Notess, 2008). In any case, it seems that there was some decline in the initial euphoria amongst various experts about the potential of Google Scholar. A notable example was Dean Giustini, who had started a blog dedicated to Google Scholar<xref ref-type="fn" rid="NOTE5">5</xref>, and who admitted that “Scholar is not as useful as promised” (cited by Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>), in reference to the inability of Google Scholar to resolve the limitations that had existed since its launch in 2004. Giustini went on to state that “unless it changes its course, GS will go the way of the dodo bird eventually”. Google Scholar did indeed change.</p>

			<p>The evolution of Google Scholar was slow, especially during its first years of existence. This may have been due to the fact that the team at the beginning was made up of only two people (Orduna-Malea et al., <xref ref-type="bibr" rid="CIT69">2016</xref>). In fact, some of the limitations or criticisms that it received in its early days, such as coverage and speed of indexation (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT33">2005a</xref>), were later transformed into strengths (Moed et al., <xref ref-type="bibr" rid="CIT62">2016</xref>; Thelwall and Kousha, <xref ref-type="bibr" rid="CIT82">2017</xref>, in press).</p>

			<p>In 2008, some of the Google Scholar errors that had led to erroneous results and citations, or large-scale duplication thereof, were corrected, “which is the appropriate reaction to the criticism” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT40">2008c</xref>). A number of other errors could also no longer be reproduced, although many others of a similar magnitude still remained after an apparent cleaning-up of the data. This seemed to indicate that when bad practice was exposed in the press, Google Scholar fixed it so that users could no longer find the exact examples that were reported; they therefore tended to think that the issues had been resolved, although this was not entirely true (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT43">2010</xref>). Not only did they persist, but all Google Scholar-based evaluations that had been conducted previously would have irreparably harmed both the individuals and journals that were evaluated.</p>

			<p>Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT43">2010</xref>) also complained of the lack of gratitude shown by the Google Scholar team for his and other authors’ contributions to correcting the errors, something that had in fact occurred in the case of the Google Books team, which publicly thanked Nunberg (<xref ref-type="bibr" rid="CIT66">2009</xref>) for contributing to the improvement of that tool with his criticism. Another significant complaint was related to Google Scholar’s tendency to blame its errors on publisher metadata rather than its own parser, similar to the Google Books team’s excuses for errors as reported by Nunberg, as described by Oder (<xref ref-type="bibr" rid="CIT67">2009</xref>), who reproduced the letter from Google in response to the query about the errors detected: “Without good metadata, effective search is impossible”.</p>

			<p>However, Google Scholar continued to evolve and to grow until, on its fifth anniversary (2009) it eliminated the “beta” tag that it had retained since its launch (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT43">2010</xref>), and many of its systematic errors were fixed (corrected or deleted). Subsequently, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT44">2011</xref>) reported that the Google Scholar parser had improved, such that tests carried out in mid-November 2010 did not detect some of the previous errors, and many others were reduced significantly, although he did continue to warn that it was not yet reliable enough to be used to calculate bibliometric indicators in the evaluation of research activity. Finally, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT45">2012a</xref>) recognised that the volume of errors was insignificant when compared to the errors identified at the beginning, although the affected authors would not be of the same opinion. A few years later, in Jacs&#x00F3;’s prologue to <italic>La revoluci&#x00F3;n Google Scholar: la caja de Pandora acad&#x00E9;mica</italic> (Orduna-Malea et al., <xref ref-type="bibr" rid="CIT69">2016</xref>), he contended that the reduction in the number of errors, even when positive, was manifestly insufficient since errors persist due to functional issues with the system that have not been resolved.</p>

			<p>Indeed, despite the fact that 2011/2012 was a milestone in the history of Google Scholar with the emergence of the related services Google Scholar Citations (aimed at authors) and Google Scholar Metrics (aimed at journals), and definitive growth in its coverage and speed of indexation, many of the errors reported during the 2004 to 2012 period still persist today.</p>

			</sec>
			
			<sec id="S1.4">
			<title>Rationale and objectives</title>

			<p>Given the growing use of Google Scholar not only as a gateway to searching for academic literature, but as a bibliometric tool, the identification, classification and quantification of its errors and limitations when calculating bibliometric indicators is of paramount importance.</p>

			<p>However, scholarly literature dedicated to this matter has not been systematic. With the exception of Jacs&#x00F3;, few authors have directly sought to detect, describe or gauge the influence of errors in Google Scholar. Occasionally, these limitations have been given passing mention in certain publications, but they have received scant attention in the way of description or explanation or have been quite simply overlooked.</p>

			<p>Moreover, in many cases these limitations have been mistaken for errors, when they are in fact related but different aspects. The limitations of Google Scholar are related to certain services or features that prevent it being used as a bibliometric analysis tool. These limitations include not being able to sort the results by the number of citations or the year of publication, the absence of an API (Application Programming Interface), the maximum of 1,000 results per search or limited capabilities for exporting search results, to give only a few illustrative examples. The objective and purpose of Google Scholar is not bibliometric analysis but searching for scholarly literature. Therefore, if such analysis is tedious, we should mark it down as a mere limitation but not as an error.</p>

			<p>Conversely, an error arises in relation to features that Google Scholar should provide or execute correctly if is to fulfil the goals and tasks that it officially declares itself to offer. For example, the system claims to report the number of citations received by a publication from the other publications indexed on Google Scholar. Therefore, if this number is incorrect, we have located an error. Since these functional errors directly affect the calculation of bibliometric indicators, knowing what types of errors exist, and to what extent, are important challenges in present-day bibliometrics.</p>

			<p>This study is therefore a first step along this line of research. Its main objective is to carry out an exhaustive bibliographic review of what has been said and done about errors in Google Scholar, to then categorise the findings of the studies that we have included in our review.</p>

			</sec>
		</sec>
			
		<sec id="S2">
			<title>2. METHOD</title>

			<p>The bibliographic review of errors in Google Scholar was conducted over three consecutive phases. First, empirical studies on Google Scholar were compiled. Second, the studies that addressed errors in Google Scholar, either directly (as part of the objectives) or indirectly (errors were listed or described even if they were not part of the main objectives), were selected. Finally, the selected studies were qualitatively analysed in order to group them according to error type.</p>

			<p>The first phase (compilation of empirical studies) was carried out as part of the objectives of a nationally funded research project (HAR2011-30383-C02-02). For this purpose, an online information and bibliographic review service was created, called Google Scholar’s Digest (<ext-link ext-link-type="uri" xlink:href="http://googlescholardigest.blogspot.com.es">http://googlescholardigest.blogspot.com.es</ext-link>), which has been compiling all empirical studies that provide data on Google Scholar since 2014, offering critical reviews (digests) of the most relevant studies.</p>

			<p>This service was put together from systematic searches of the main bibliographic databases (WoS, Scopus and Google Scholar itself) and is constantly fed by a technological monitoring and alerts system, using RSS technology, a Twitter account (@GSDigest), and the Google Scholar alerts system. To date, 271 publications have been compiled, including journal articles, books, book chapters, conference papers, reports and working papers, among other document types.</p>

			<p>This system was designed in part because of the complexity of finding academic literature with empirical data on Google Scholar, since searches limited to the term &lt;Google Scholar&gt; in the title, keywords or abstract are insufficient.</p>

			<p>The second phase (selecting the studies on errors in Google Scholar) consisted of a qualitative analysis of the 271 publications in the Google Scholar’s Digest bibliography. The studies were separated into two distinct corpuses. On the one hand, the work of P&#x00E9;ter Jacs&#x00F3; (Corpus A, comprising 16 works, see <xref ref-type="table" rid="A1">Appendix I</xref>) and, on the other hand, other studies with data or comments on errors in the functioning of Google Scholar (Corpus B, comprising 34 works, see <xref ref-type="table" rid="A2">Appendix II</xref>).</p>

			<p>The third phase (categorisation of errors) consisted in the reading, analysis and manual classification of each of the studies in the two bibliographic corpuses, in order to identify both the different currents in the literature on errors and the main types of errors studied to date.</p>

			<p>To this end, we decided to apply a general taxonomy of errors (<xref ref-type="table" rid="T2">Table II</xref>), in order to classify the studies according to the type of error addressed (note: a study may, of course, contain information on several types of errors).</p>
			
						<fig id="T2">
							<label>Table II</label>
							<caption>
								<title>Broad taxonomy of errors in Google Scholar database</title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T2.jpg"/>
						</fig>

			<p>Phase I was carried out from 2014 to May 2017, while phases II and III were carried out in parallel between January and May 2017.</p>

		</sec>
		
		<sec id="S3">
			<title>3. RESULTS</title>

			<p>This section is divided into four main blocks. First, a descriptive analysis of the bibliographic corpus is carried out. Second, studies focusing on the identification and description of errors in Google Scholar are examined. Third, publications that have focused their interest on errors in filtered or structured environments – either official services (Google Scholar Citations, Google Scholar Metrics) or existing tools in the market (Publish or Perish) – are looked at. Finally, the publications that have proposed Google Scholar error type categories are singled out.</p>

			<sec id="S3.1">
			<title>3.1. Descriptive analysis of the bibliographic corpus </title>

			<p>As mentioned previously, the literature that has dealt with errors in Google Scholar was divided into two bibliographic corpuses. The first (corpus A) comprising the work of Jacs&#x00F3; (16 publications, Appendix I), and the second (corpus B) comprising other publications that have addressed, directly or indirectly, the issue of errors in this database (33 publications, <xref ref-type="table" rid="A2">Appendix II</xref>), forming in total a corpus of 49 publications.</p>

			<p>Of the total number of publications, 40% (20) are concentrated in the period 2005 to 2008, corresponding to the launching of the search engine and the bulk of the articles published by Jacs&#x00F3;, who after then authored an annual review for his column in <italic>Online Information Review</italic> (2009-2011). 2012 is an exception (four works by Jacs&#x00F3;), coinciding both with the update of the search engine and the birth of Google Scholar Citations and Google Scholar Metrics. From then on, P&#x00E9;ter Jacs&#x00F3; ceased his fertile output dedicated to Google Scholar. Corpus B, for its part, developed strongly during the first years, although no remarkable pattern is observed. One possible reason for this is that a significant proportion of these publications did not focus on the errors of Google Scholar, which nevertheless appeared during their development; the errors were then only reviewed in passing (in varying levels of detail). In any case, the number of publications grew in 2016 (five in total).</p>

			<p>With regard to thematic coverage, 53% of all the publications (corpus A and B) focus on specific disciplines while the remaining 47% are multidisciplinary studies. These data are influenced by Jacs&#x00F3;’s work, as 12 of his 16 studies (75%) cannot be ascribed to any disciplinary area, since they are based on the testing of different search options through general queries. As far as geographic coverage is concerned, 76% (37) of the publications are international in scope, while only 24% (12) focus on specific countries. Again, Jacs&#x00F3;’s work influences this distribution since all his articles have an international approach (or rather, they have no geographical restrictions). Finally, most of the publications have analysed authors (41% of the total), followed by journals (25%) and documents (17%). <xref ref-type="fig" rid="F1">Figure 1</xref> gives a summary of the descriptive data of the analysed bibliographic corpus.</p>
			
						<fig id="F1">
							<label>Figure 1</label>
							<caption>
								<title>Descriptive analysis of the bibliographic corpus on Google Scholar errors (a) annual output; (b) unit of analysis; (c) thematic coverage; (d) geographical coverage </title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/F1.jpg"/>
						</fig>

			</sec>
			
			<sec id="S3.2">
			<title>3.2. Errors in Google Scholar </title>

			<p>Following the scheme proposed in <xref ref-type="table" rid="T2">Table II</xref>, contributions were classified into those that identify errors related to coverage, parsing, matching and searching.</p>

			<sec id="S3.2.1">
			<title>3.2.1. Coverage</title>

			<p>Given the scarce – at times, inexistent – information on the sources that feed Google Scholar (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT47">2012c</xref>; Orduna-Malea et al., <xref ref-type="bibr" rid="CIT69">2016</xref>), critical literature on its coverage was particularly fertile during the early years of its existence. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT33">2005a</xref>), from the outset, reproached it for the fact that the results for any query were made up of a mixture of document genres (journal paper, conference paper, or book) and paper types (research paper, review paper, brief communication) from a multitude of sources, including not only educational websites but also non-scholarly sources, like promotional pages, table of contents pages, course reading lists (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT36">2006a</xref>).</p>

			<p>The academic literature has sometimes treated this as an error when in fact we are faced with a limitation for conducting certain bibliometric analyses. Moreover, it is not even globally accepted as such because many specialists consider that the varied nature of the citing documents is not necessarily a limitation in itself.</p>

			<p>However, having performed several tests to verify the validity of the system with such an amalgam of citing documents, several errors related to coverage were discovered incidentally:</p>
			
							<list list-type="bullet">
								<list-item>
									<p>Massive content omissions when searching for journals (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT35">2005c</xref>): this even occurred with the journals of publishing houses that had agreements in place with Google Scholar to display the full text of the contents (<italic>Nature</italic>, <italic>Science</italic>, <italic>PNAS</italic>).</p>
								</list-item>
								
								<list-item>
									<p>Indexing limits (Price, <xref ref-type="bibr" rid="CIT76">2004</xref>; Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT35">2005c</xref>): limits were detected in the indexing of files, set at the first 100 to 120 KB of the text, such that, if the terms of a query appeared in the text beyond that limit, a result might not be returned and, therefore, the corresponding hit would not be counted.</p>
								</list-item>
								
								<list-item>
									<p>Mistaken inclusion of excluded document types (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT38">2008a</xref>): sometimes a book review was mistaken for the book itself. Apart from the errors made due to wrongly classified document types, the coverage policy of Google Scholar was also brought under scrutiny: “Content such as news or magazine articles, book reviews, and editorials is not appropriate for Google Scholar”<xref ref-type="fn" rid="NOTE6">6</xref>.</p>
								</list-item>
								
								<list-item>
									<p>Inclusion of excluded document types due to mass indexing (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT47">2012c</xref>): when Google Scholar considered a web domain for inclusion (for example, .edu), it indiscriminately indexed all the files hosted in that web domain that were apparently academic, which led to the indexing of many document types that in principle, according to its rules and criteria, were not appropriate for the database.</p>
								</list-item>
							</list>

			</sec>
			
			<sec id="S3.2.2">
			<title>3.2.2. Parsing</title>

			<p>Parsing errors are one of the most important areas of this study, as their occurrence causes a chain reaction that is capable of generating and transmitting new errors to other documents on an extremely large scale. Parsing is a process that enables strings of symbols to be analysed according to predetermined formal grammatical rules. Hence an application can identify the different parts of a bibliographic record (author, title, source, volume, number, pagination) of both a citing document (metadata) and a cited document (bibliographic reference contained in the bibliography section of an academic work).</p>

			<p>Belew (<xref ref-type="bibr" rid="CIT12">2005</xref>) had already indicated that certain character encodings, such as ASCII, can generate problems and errors (inconsistencies in author names and erroneous attribution of citations) in WoS and Google Scholar, especially for authors whose names are written in non-Latin characters. However, Bar-Ilan (<xref ref-type="bibr" rid="CIT07">2006</xref>) expressed surprise when, in performing a bibliometric analysis of the scholarly output of mathematician Michael Rabin, she discovered that there were recurring errors (erroneous attribution of citations and authors) in articles published by the IEEE (Institute of Electrical and Electronic Engineers), even though Google Scholar − supposedly − based much of its data on the information provided by publishers. In reality, the main problem with Google Scholar was related to the fact that it programmed its own parsers instead of relying on the information provided by the metadata prepared by publishers, an approach that may make sense with unstructured masses of web pages, but not with scholarly documents (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT34">2005b</xref>; Jacs&#x00F3; <xref ref-type="bibr" rid="CIT47">2012c</xref>), leading it to generate enormous amounts of errors during the process of scanning and parsing the various elements of a bibliographic record. This fact led to the discovery that the author “I Introduction” was the most prolific according to Google Scholar, with more than 40,000 publications (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT36">2006a</xref>) or that “F Password” was the most cited (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>). The faulty functioning of the parsers led to segments of the International Standard Serial Number (ISSN) being mistaken for the year of publication (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT38">2008a</xref>), and menu options, section headings and journal name logos for author names (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT41">2009a</xref>), due to the complete lack of quality controls (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT43">2010</xref>), distorting the bibliometric indicators at individual, corporate and journal levels (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT47">2012c</xref>).</p>

			<p>As an illustrative example, and in response to Vanclay (<xref ref-type="bibr" rid="CIT85">2012</xref>), Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT46">2012b</xref>) showed a result obtained by Google Scholar for the article “Vision 2020−the palm oil phenomenon”, in which the system deleted the second author (MA Simeh), showed “Growth” as the publication source (when in fact it was the <italic>Oil Palm Industry Economic Journal</italic>), and “2015” as year of publication (when it was actually 2005). <xref ref-type="fig" rid="F2">Figure 2</xref> shows the current result for this article with its corrected bibliographical data.</p>
			
						<fig id="F2">
							<label>Figure 2</label>
							<caption>
								<title>Correction of the bibliographic description of results in Google Scholar </title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/F2.jpg"/>
						</fig>

			<p>Within the parsing errors, the literature has dealt with each of the elements of a bibliographic record, although errors related to author names have undoubtedly been the most widely studied. For that reason, we shall now look at author studies separately from the other bibliographic elements.</p>

			<sec id="S3.2.2.1">
			<title>a) Absurd authors </title>

			<p>P&#x00E9;ter Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT32">2004</xref>) denounced the irregular and deficient behaviour of the Google Scholar parsers from the outset, especially when identifying author names, which were confused with other content (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT38">2008a</xref>). Marydee Ojala (<xref ref-type="bibr" rid="CIT68">2005</xref>) expressed similar sentiments in a brief text included in the article by Wleklinski (<xref ref-type="bibr" rid="CIT91">2005</xref>), published in the journal <italic>Online</italic>. Harzing and Van der Wal (<xref ref-type="bibr" rid="CIT30">2008</xref>) also contended that Google Scholar would not find publications if the author’s name included a sequence of characters that was not in a traditional typeset or if the author had used LaTeX (a document preparation system).</p>

			<p>On occasion, a “misspelled author” error was generated, whereby names such as “Julie M Still” became “Julie M” or P&#x00E9;ter Jacs&#x00F3; himself became “Peter J”, such that the first letter of the surname became the first initial of the forename (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>).</p>

			<p>On other occasions, nonexistent names were generated. Jacs&#x00F3; managed to identify a large number of these, such as: Payment Options, Please Login, Strategic Plan, I Background and II Objectives, Forgot Password, I Introduction and R Subscribe, among many others (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>; <xref ref-type="bibr" rid="CIT40">2008c</xref>; <xref ref-type="bibr" rid="CIT43">2010</xref>; <xref ref-type="bibr" rid="CIT44">2011</xref>). These errors were sometimes concentrated in the publications of certain publishers, such as Emerald (Jacs&#x00F3; <xref ref-type="bibr" rid="CIT39">2008b</xref>), or journals such as <italic>The Lancet</italic> (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT43">2010</xref>), where parsers sometimes created author names from the MeSH terms (Medical Subject Headings) assigned to the documents. Even though Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT43">2010</xref>; <xref ref-type="bibr" rid="CIT44">2011</xref>) acknowledged that in some cases these names may be legitimate (notably the case of Raymond and Linda Measures), most of the time they were large-scale errors: V. Cart corresponded on most occasions to View Cart, and not to Veronica Cart (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT40">2008c</xref>).</p>

			<p><xref ref-type="table" rid="T3">Table III</xref> provides a comparison of the results obtained (number of hits returned) for a query by absurd author (example: &lt;author:“F Password”&gt;) in Google Scholar in the different publications that have addressed the subject, including the results obtained in 2017 for the purposes of this study.</p>
			
						<fig id="T3">
							<label>Table III</label>
							<caption>
								<title>Test search on absurd authors</title>
								<p>* Note: the unusually low value compared to the rest may be due to the query performed (using the &lt;author&gt;; command or not)</p>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T3.jpg"/>
						</fig>

			<p>As has already been mentioned, sometimes these terms were real (Jenice L View) and other times they were parsing errors, which substitute (VIEW, TPO, from VIEW, TIONAL POINT OF) or modify (KALINGA, AVF, from KALINGA, A View From) or add (Image, PVVS, from Physically-Valid View Synthesis by Image). These absurd authors still exist as of 2017.</p>

			<p>Finally, on other occasions co-authors (real or absurd) were added. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) denounced the fact that in the bibliographic record corresponding to the seminal article on h-index published by Jorge Hirsch (<xref ref-type="bibr" rid="CIT31">2005</xref>), Google Scholar had added three co-authors (Louie, Jackiw and Wilczek), who were the researchers that Hirsch used as examples in his article within an enumerative list (this result has been updated and is now correct). Jacs&#x00F3; himself also fell afoul of this quirk in the search results, appearing in the company of “MA Sicilia” as co-author of his article “Deflated, inflated and phantom citation counts” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT36">2006a</xref>). Curiously, this erroneous information only appeared in what was considered to be the main version, but was correctly recorded in the other versions (<xref ref-type="fig" rid="F3">Figure 3</xref>).</p>
			
			
					<fig id="F3">
						<label>Figura 3</label>
						<caption>
							<title>The addition of a phantom co-author to a bibliographic record in Google Scholar</title>
						</caption>
						<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/F3.jpg"/>
					</fig>
						
						

			</sec>
			
			<sec id="S3.2.2.2">
			<title>b) Other bibliographic fields </title>

			<p>Within this area, we may highlight the publications that reflect errors in titles and bibliographic information (mainly, name of journal, volume, number and pagination):</p>
			
						<list list-type="bullet">
							<list-item>
								<p>With regard to the document title, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT34">2005b</xref>) contended that it was sometimes mistaken for sections or subtitles (“Short Communication”, “Original Article” or “Special Invitation”). These elements could be added to the original title or replace it completely. The reason for this error lay in the fact that Google Scholar ignored the metadata and focused on detecting sequences of characters with some special emphasis (boldface, larger font size, etc.). Walters (<xref ref-type="bibr" rid="CIT89">2007</xref>) is one of the few authors that has given a figure to this type of error, after evaluating 155 articles and detecting that 15.5% (24 documents) of them had incomplete titles. However, it would seem that he used the snippet provided under each result to perform this analysis. Walters then stated that GS did not include more than 4 authors and no more than 99 characters (in reality, GS uses a line to include these data, and the author can now access the complete reference by clicking on the “cite” option), so we may assume that the error rate that he obtained was an overestimation. For this reason the title is sometimes shortened, as shown by Bar-Ilan (<xref ref-type="bibr" rid="CIT08">2008</xref>) in her analysis of the publications of the American Physical Society, in which she identified inconsistencies in the publication dates.</p>
							</list-item>
							
							<list-item>
								<p>With regard to the publication date, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) discovered errors because the parsers identified any chain of 4 digits as a potential publication date, including page numbers or area codes or street addresses in author affiliation. For example, the volume number was sometimes used to designate the publication date, as Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT43">2010</xref>) pointed out in the case of the “Proceedings of SPIE”, or the year of the latest edition of a book was mistaken for its publication date (Dilger and M&#x00FC;ller, <xref ref-type="bibr" rid="CIT19">2013</xref>; Mart&#x00ED;n-Mart&#x00ED;n et al., <xref ref-type="bibr" rid="CIT60">2017</xref>). On other occasions, there was simply no date of publication (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT43">2010</xref>), a fact that was also reported by Maia et al. (<xref ref-type="bibr" rid="CIT54">2016</xref>), who, after analysing 2,400 documents in the area of “Strategy as Practice”, noted that 15% of the documents had no publication date on Google Scholar. These errors led the system to absurd situations in which some documents had future publication dates (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT40">2008c</xref>), which in turn caused “future” documents to have already been cited by other documents. Nevertheless, these publications are small samples that were compiled in the Google Scholar’s developing years. In a later study (Mart&#x00ED;n-Mart&#x00ED;n et al., <xref ref-type="bibr" rid="CIT60">2017</xref>) of a sample of 32,680 highly-cited documents, the authors confirmed that there is agreement between the publication dates reported by Google Scholar and Web of Science for 96.7% of documents. Although WoS is not error-free, the fact that it is a supervised database gives us certain guarantees regarding the quality of Google Scholar data today.</p>
							</list-item>
							
							<list-item>
								<p>The document source is another field that has been explored by the literature. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT34">2005b</xref>) had already indicated that there were results that did not provide information about the source, even when they originated from Medline. Subsequently, Maia et al. (<xref ref-type="bibr" rid="CIT54">2016</xref>), who worked with a sample of 633 records, indicated that 27%​ of them contained no mention of their source.</p>
							</list-item>
							
							<list-item>
								<p>These parsing errors do not only affect source or citing documents, but also documents cited by them. Meho and Yang (<xref ref-type="bibr" rid="CIT61">2007</xref>) analysed citations received by 25 professors from Indiana University-Bloomington, demonstrating that 475 citations from Google Scholar did not have complete bibliographic information, although it should be noted that these citations came from unusual document types (presentations, grant and research proposals, doctoral qualifying examinations, submitted manuscripts, syllabi, term papers, working papers, Web documents, preprints, and student portfolios). Similarly, Noll (<xref ref-type="bibr" rid="CIT63">2008</xref>) studied the coverage of Google Scholar in the area of art history literature, highlighting the existence of errors in the cited references, which lacked information on the volume, number and pagination.</p>
							</list-item>
						</list>

			<p>The reasons for which the Google Scholar parsers commit these flagrant errors have been very little studied, beyond the work of Jacs&#x00F3;. One such study that merits our attention is that published by Haddaway et al. (<xref ref-type="bibr" rid="CIT26">2015</xref>), who, after investigating the usefulness of Google Scholar as a database in systematic reviews and grey literature, calculated a total rate of duplicate records due to parsing errors of around 5%, because of the following factors:</p>
			
						<list list-type="bullet">
							<list-item>
								<p>Typographical errors introduced by manual transcription (15% of title records).</p>
							</list-item>
							
							<list-item>
								<p>Differences in formatting and punctuation (18% of duplicates).</p>
							</list-item>
							
							<list-item>
								<p>Capitalisation (36% of duplicates).</p>
							</list-item>
							
							<list-item>
								<p>Incomplete titles (15% of duplicates).</p>
							</list-item>
							
							<list-item>
								<p>Automated text detection (3% of duplicates).</p>
							</list-item>
							
							<list-item>
								<p>Scanning of citations within references of selected included literature, and the presence of both citations and the articles themselves (13% of duplication).</p>
							</list-item>
						</list>

			</sec>
			</sec>
			
			<sec id="S3.2.3">
			<title>3.2.3. Matching</title>

			<p>In most cases, matching errors are derived from parsing errors, since small variations in a reference can lead to duplicate records (Harzing and Alakangas, <xref ref-type="bibr" rid="CIT29">2016</xref>), although they are sometimes errors in themselves. In any case, the consequences of these errors for bibliometric analysis are enormous, especially because of the fact that they generate a mass of inflated document citations. As an illustrative example, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) analysed his own article “Google Scholar: the pros and the cons”, which at that time had received 57 citations according to the Google Scholar result. However, after exhaustive filtering of the data, Jacs&#x00F3; found that this figure was highly inflated. First, the number of estimated hits was 55, of which the interface actually displayed 53 (this is occasionally due to desynchronisation caused by a database update). Of these, there was no way to access four of them (their veracity could not therefore be verified), six were duplicates and four others were erroneous (citing document did not mention the cited document).</p>

			<p>This example alone would suggest to the reader that there is a wide variety of interconnected errors, both in matching and browsing (see next section). Although the errors should be studied in terms of their cause-effect relationships, the literature has generally treated them separately, distinguishing between matching errors between different versions, on the one hand, and matching errors between citing and cited documents, on the other.</p>

			<sec id="S3.2.3.1">
			<title>a) Matching versions</title>

			<p>Duplicate versions of records are an issue that have been brought to light by the literature practically since the launch of Google Scholar. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT34">2005b</xref>) illustrated the existence of different versions of the same document that were not correctly linked and how this caused dispersion in the citations received by a document, which ultimately affected the position in which that document appeared in the results.<xref ref-type="fn" rid="NOTE7">7</xref> Yang and Meho (<xref ref-type="bibr" rid="CIT92">2006</xref>) also commented on how a citation from two versions of the same document (preprint and the version of the article published in a journal) would be counted twice. However, studies that have provided exact figures that quantify the magnitude of these errors in a particular sample or in Google Scholar in general are very scarce, and with completely different results due to the enormous differences in the samples used. Noll (<xref ref-type="bibr" rid="CIT63">2008</xref>) detected 23% of duplicates and multiple versions that contributed to the number of citations received by a set of 12 preselected art historians. Rosentreich and Wooliscroft (<xref ref-type="bibr" rid="CIT78">2009</xref>), after calculating the g-index for a set of 34 accounting journals, detected a duplicate rate of around 3%. Thor and Bornmann (<xref ref-type="bibr" rid="CIT83">2011</xref>) described how, in the case of a specific search (&lt;allintitle: merge purge large&gt;), they obtained eight results in Google Scholar, and all referred to the exact same document, which ironically dealt with the automatic identification of duplicates.</p>

			<p>However, it should be noted that the system for automatically identifying versions has improved substantially over time, an aspect to which Google has dedicated technological resources, as can be seen through the publication of a patent that describes the automatic identification of different versions of the same document (Verstak and Acharya, <xref ref-type="bibr" rid="CIT87">2013</xref>).</p>

			<p>The article by Pitol and De Groote (<xref ref-type="bibr" rid="CIT75">2014</xref>) was the first dedicated exclusively to the issue of versions in Google Scholar. The authors analysed 982 articles, concluding that only 6.1% of them (60) had duplicate versions, which was taken to mean that they were documents that the system had not merged. Moed et al. (<xref ref-type="bibr" rid="CIT62">2016</xref>) also indicated that duplicates, in the strict sense (with identical metadata), were rare (0.2%) in their study of a limited set of articles (1200) published in 12 journals. Even so, this percentage depends on the document type analysed, increasing significantly in the case of monographs. Mart&#x00ED;n-Mart&#x00ED;n et al. (<xref ref-type="bibr" rid="CIT60">2017</xref>) analysed the article “Mathematical Theory of Communication”, for which they detected up to 165 versions that were not correctly linked.</p>

			</sec>
			
			<sec id="S3.2.3.2">
			<title>b) Matching citing/cited documents</title>

			<p>Another source of error is the matching of citing (source) and cited (target) documents. Although citations are prone to many forms of error (e.g. typographical errors in the source document because authors or journal editors have incorrectly transcribed a bibliographic reference), other problems are caused by the Google Scholar parsing process, especially when non-standard reference formats are used (Harzing and Van der Wal, <xref ref-type="bibr" rid="CIT30">2008</xref>) or when the document has a complex structure (Meho and Yang, <xref ref-type="bibr" rid="CIT61">2007</xref>), or simply when the parsing process fails. In the words of Vaughan and Shaw (<xref ref-type="bibr" rid="CIT86">2008</xref>), “citing and cited papers are confused”.</p>

			<p>The Google Scholar automatic citation system functions correctly when a bibliographic reference exactly matches a master record (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT41">2009a</xref>). In that case, it is rewarded with a new received citation. However, it may be that there is no such match because the parsing has generated variants or duplicates, both of the reference and the master record (or both). If the version-linking technology (mentioned above) worked correctly, many of the errors would be resolved, although this regrettably is not the case.</p>

			<p>Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT34">2005b</xref>) was the first to write about the notorious inability of Google Scholar to correctly link citing/cited documents, resulting in an inflation/deflation effect in the cited documents (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT38">2008a</xref>), due to either receiving citations that do not exist or not receiving existing citations. For example, Jacs&#x00F3; noted that the most-cited article in <italic>The Scientist</italic> was a document with 7,390 citations received which, in reality, corresponded in large measure to an article published in the <italic>Journal of Crystallography</italic>. Subsequently, Harzing and Van der Wal (<xref ref-type="bibr" rid="CIT30">2008</xref>) were not able to reproduce this search, and they noted that the most-cited article was another (which received only 137 citations), from which it follows that Google Scholar was able to correct this error.</p>

			<p>In spite of this, the reporting of errors in empirical studies is notable. Meho and Yang (<xref ref-type="bibr" rid="CIT61">2007</xref>) observed that Google Scholar missed 40.4% of the citations listed in both WoS and Scopus for 25 professors, and Bar-Ilan (<xref ref-type="bibr" rid="CIT08">2008</xref>) noted that the article “Probabilistic Encryption”, cited 915 times, had been attributed incorrectly to Avi Wigderson. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) pointed out that most of the citations received by an article published in the <italic>Journal of Forestry Ecology &amp; Management</italic> actually cited a technical report, yearly updated, that had part of the same title as the journal article. Which meant that “GS lumps together a series of technical reports and a journal article, awarding the citations to the journal” (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>).</p>

			<p>At other times, the matching error stems from an earlier parsing error. For example, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) reported that the authorship of an article published in <italic>Online Information Review</italic> was attributed to “M Profile” when in fact it was co-authored by Hong Iris Xie and Collen Cool. Since this article had received 10 citations, the two authors had been deprived of these citations. If “I Introduction” had been the author of around 6,000 articles in Google Scholar (see Table III), the number of citations that the actual authors did not receive could be in the millions; it is as impossible to calculate as the number of wrongly attributed authors. The direct consequence is that the citation/matching algorithm is as unreliable as the parsing algorithm. These errors, even if they have been minimised, still exist. For example, Moed et al. (<xref ref-type="bibr" rid="CIT62">2016</xref>) indicated that one of the most-cited articles in the <italic>Journal of Virology</italic>, according to Google Scholar (270 citations), received most of these citations (180) erroneously.</p>

			</sec>
			</sec>
			
			<sec id="S3.2.4">
			<title>3.2.4. Searching &amp; Browsing</title>

			<p>The last aspect that remains to be described is general errors associated with the search and browsing processes in the Google Scholar environment. This type of error has sometimes been confused with or placed alongside search limitations. In this case, we shall only highlight those contributions that look specifically at errors.</p>

			<p>From the qualitative analysis of the bibliographic corpuses of errors in Google Scholar, we separated out the contributions that report errors in the advanced search due to a lack of authority control, in the number of hits for a query, and errors in the full-text link.</p>

			<sec id="S3.2.4.1">
			<title>a) Advanced search </title>

			<p>As might be expected, the pioneer in this field was Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT33">2005a</xref>). When he conducted a bibliometric analysis of Garfield’s work to coincide with his 80th birthday, he discovered a series of deficiencies due mainly to the absolute lack of authority control (Bar-Ilan, <xref ref-type="bibr" rid="CIT08">2008</xref>), which generated errors in searches by author (the system combined the publications of E Garfield and RE Garfield, for example) and by journal (the system combined all articles published in <italic>Current Science</italic> with those of other publications in which the same character string appeared, such as “Current Directions in Psychological Science” or “Current Trends in Theoretical Computer Science”) (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT33">2005a</xref>). This is an error in the sense that the database was unable to return the articles published by a particular author or journal, which is the service that had been promised to the user. At present, at least for <italic>Current Science</italic>, this error seems to have been resolved, although authority control is still lacking (a search for “revista espa&#x00F1;ola” (“Spanish journal”) will retrieve articles published by <italic>Revista Espa&#x00F1;ola de Ling&#x00FC;&#x00ED;stica Aplicada</italic>, <italic>Revista Espa&#x00F1;ola de Pedagog&#x00ED;a</italic>, <italic>Revista Espa&#x00F1;ola de Documentaci&#x00F3;n Cient&#x00ED;fica</italic>, etc.) and is complicated by the existence of abbreviations and variants (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT37">2006b</xref>), a problem that still occurs.</p>

			<p>In its beginnings, Google Scholar provided an advanced search function to look for documents according to their discipline. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT38">2008a</xref>) revealed this to be an absurd function, since a search not restricted by subject generated 85% more results than adding up the results for each of the categories.</p>

			</sec>
			<sec id="S3.2.4.2">
			<title>b) Hit estimate errors</title>

			<p>Within the errors in hit estimates, the literature has mainly dealt with errors based on queries using Boolean logic, the duplication of hits, and advanced search publication date.</p>

			<sec id="S3.2.4.2.1">
			<title>Boolean problems</title>

			<p>This type of problem was a classic example in Jacso’s work. They are problems related to absurd or inconsistent numbers of results according to the query. For example, the search for “protein” returned 8,390,000 results, the search “proteins” 4,270,000, and finally the search for “protein OR proteins” 1,630,000 (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT33">2005a</xref>). Based on this study, we have compiled all the examples provided throughout the work of P&#x00E9;ter Jacs&#x00F3; and recalculated these data for the present day (<xref ref-type="table" rid="T4">Table IV</xref>). In this way, we may see how the errors not only persist but, in some cases, have even increased.</p>
			
						<fig id="T4">
							<label>Table IV</label>
							<caption>
								<title>Test search on absurd Boolean hit counts</title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T4.jpg"/>
						</fig>

			</sec>
			
			<sec id="S3.2.4.2.2">
			<title>Duplicate hits</title>

			<p>The generation of repeated hits has also been a recurrent issue in the Google Scholar literature (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT33">2005a</xref>; <xref ref-type="bibr" rid="CIT37">2006b</xref>; <xref ref-type="bibr" rid="CIT39">2008b</xref>; Shultz, <xref ref-type="bibr" rid="CIT80">2007</xref>): the existence of duplicate records in Google Scholar results due to parsing and matching errors (versions). It should be mentioned, however, that much of the literature uses erroneous terms when referring to the concept “hit” (results for a specific search), because sometimes they use it as a synonym for “citation” (citations aggregated under a master record), although they are related but different concepts (Levine-Clark and Gil, <xref ref-type="bibr" rid="CIT51">2009</xref>). It is therefore difficult at times to follow or appropriately contextualise many of the findings and conclusions. Of the few publications in which specific figures are given, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT39">2008b</xref>) reported how, after analysing the number of articles published in <italic>Online Information Review</italic> indexed by Google Scholar, he obtained a total of 513 records (thus hits). Of these, approximately 38% (195) were duplicates, with the added problem that this figure (513) varied depending on the Search Engine Result Page (SERP) that the user was on at any given moment.</p>

			</sec>
			
			<sec id="S3.2.4.2.3">
			<title>Year range</title>

			<p>If parsing errors are assumed in the publication dates, we could not expect an advanced search by publication date to be error-free. <xref ref-type="table" rid="T5">Table V</xref> compiles all the examples provided by Jacs&#x00F3; with a reconstruction of the searches for 2017 conducted for this bibliographic review of errors. As can be seen, inconsistencies still persist.</p>
			
						<fig id="T5">
							<label>Table V</label>
							<caption>
								<title>Test search on absurd time range hit counts</title>
								<p>* Note: these results are coherent with Boolean algebra although quite implausible</p>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T5.jpg"/>
						</fig>

			</sec>
			</sec>
			
			<sec id="S3.2.4.3">
			<title>c) Erroneous full text links</title>

			<p>Finally, the literature has identified errors in the links in the master records that provide access to the full text of the article, where this is possible. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT33">2005a</xref>) found that by clicking on the link to an article published in 2005 on Infection and Immunity, the system took him to the full text of another article published 25 years before in <italic>PNAS</italic>. Likewise, Shultz (<xref ref-type="bibr" rid="CIT80">2007</xref>) discovered the existence of broken links or dysfunctional links. Later, Mart&#x00ED;n-Mart&#x00ED;n et al. (<xref ref-type="bibr" rid="CIT58">2016b</xref>), after conducting an exhaustive case study into the article “Mathematical theory of communication” on Google Scholar, detected 830 versions linked to the master record. Of these, Google Scholar only returned 763, of which 21.1% (161) presented some kind of error. In particular, 86 had a broken link to the full text.</p>

			</sec>
			</sec>
			
			<sec id="S3.2.5">
			<title>3.2.5. Global error propagation</title>

			<p>The errors identified by the scholarly literature analysed in this study have barely been quantified, and most of the time they are merely mentioned or reported. Despite the absence of error percentages, the deficiencies were sufficiently voluminous for Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT40">2008c</xref>) to conclude that the citations reported by Google Scholar were not acceptable, not even as a starting point, for the evaluation of the scholarly activity of researchers, since the volume of citations was “inflated” and “untraceable”, which had similar repercussions for the calculation of derived indicators such as the h-index (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT41">2009a</xref>; <xref ref-type="bibr" rid="CIT47">2012c</xref>).</p>

			<p>To illustrate these shortcomings, the literature has carried out several analyses that have revealed the combined occurrence of several types of errors that distort the overall results, among which the following publications stand out:</p>
			
						<list list-type="bullet">
							<list-item>
								<p>Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT41">2009a</xref>): analysed the book <italic>Managing the Multinationals: an International Study of Control Mechanisms</italic> (Harzing). Seven (unlinked) versions were detected, each with its own received citations (citation dispersion), and one result corresponded to a book review that was erroneously attributed to Harzing.</p>
							</list-item>
							
							<list-item>
								<p>Bar-Ilan (<xref ref-type="bibr" rid="CIT09">2010</xref>): analysed the book <italic>Introduction to Informetrics</italic> (Egghe and Rousseau). 358 documents referring to the article were detected, of which 24 (6.7%) were duplicates, 17 contained title variants, and 5 had authorship errors. After removing the duplicates and other errors, only 307 documents actually cited the book (total error of 14.2%).</p>
							</list-item>
							
							<list-item>
								<p>Garc&#x00ED;a-P&#x00E9;rez (<xref ref-type="bibr" rid="CIT22">2010</xref>): analysed a corpus of 380 publications by 4 authors in the field of psychology. 16.5% of the citations were erroneous (phantom citations, duplicate links, unlinked versions and errors in the estimation of hits).</p>
							</list-item>
							
							<list-item>
								<p>Adriaanse and Rensleigh (<xref ref-type="bibr" rid="CIT03">2011</xref>): analysed the content of 9 environmental science journals in South Africa, identifying a total of 448 inconsistencies in the records (14%) as well as duplications (a total of 185) due to “citation” hits in Google Scholar. Note: In this case, hits are counted as citations (citation hits).</p>
							</list-item>
							
							<list-item>
								<p>Mart&#x00ED;n-Mart&#x00ED;n et al. (<xref ref-type="bibr" rid="CIT56">2014b</xref>): analysed a corpus of 64,000 highly-cited documents between 1950 and 2013. The following errors were identified: full-text links that did not work or did not correspond to the master record, GS-WoS linking failures,<xref ref-type="fn" rid="NOTE8">8</xref> unlinked versions, incorrect attribution of citations to documents, incorrect attribution of documents to authors, phantom citations, phantom authors, incorrect identification of titles, duplicate citations and publications.</p>
							</list-item>
						</list>

			<p>As can be seen, the broader the samples, the greater the quantity and variety of errors found. This is due, as already mentioned, to the interconnection between different types of errors: a parsing error can generate a duplicate which, if the version control system does not group them correctly, can generate a duplicate citation.</p>

			</sec>
			</sec>
			
			<sec id="S3.3">
			<title>3.3. Errors in filtered environments</title>

			<p>All of the studies reviewed above operate in the Google Scholar environment. However, there are platforms, both external and linked to this service, designed for working with more filtered and structured data, which may in some cases help to fix some of the errors seen in the previous sections, although they may similarly introduce new errors.</p>

			<sec id="S3.3.1">
			<title>a) External products </title>

			<p>One of the more notable external products is Publish or Perish (PoP) (Harzing, <xref ref-type="bibr" rid="CIT27">2010</xref>), a desktop application that provides a user-friendly interface for searching Google Scholar directly and, especially, for working with results in such a way that allows users not only to work with the retrieved documents (sort them according to various criteria, merge duplicates, etc.) but also to obtain a wide variety of bibliometric indicators calculated from the retrieved documents. This application, which is free to download and use,<xref ref-type="fn" rid="NOTE9">9</xref> has undoubtedly contributed to the democratisation and popularisation of bibliometrics.</p>

			<p>Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT41">2009a</xref>) analysed the first versions of the tool, confirming its potential to facilitate the discovery of erroneous information and correct it. However, since the application works directly with Google Scholar results, it inherited certain errors (e.g. typography errors in author names or errors in the title, phantom authors, phantom citations) and limitations (e.g. a maximum of 1,000 results per query) that cannot be directly corrected or resolved. The ability of PoP to export the results obtained to a spreadsheet can mitigate, but not solve, some of the problems.</p>

			<p>Baneyx (<xref ref-type="bibr" rid="CIT06">2008</xref>) developed a complement to PoP called CleanPoP, which works with the results provided by PoP to improve their quality. Its capabilities include the automatic detection and merging of duplicate articles and variants of the author name. As a sample, Baneyx analysed 12 French researchers. Focusing on one of them (R. Br), PoP located 3,707 citations that, after using CleanPoP, were reduced to 526, so the author concluded that about 86% of the citations provided by PoP were incorrect.</p>

			</sec>
			
			<sec id="S3.3.2">
			<title>b) Internal tools</title>

			<p>The Google Scholar team, fully aware of the errors and limitations of their database, developed and launched two new services between 2011 and 2012 that directly draw on the Google Scholar database. First, Google Scholar Citations (GSC),<xref ref-type="fn" rid="NOTE10">10</xref> and, second, Google Scholar Metrics (GSM),<xref ref-type="fn" rid="NOTE11">11</xref> oriented towards the management of authors and journals, respectively.</p>

			<p>First impressions of Google Scholar Citations (from an errors point of view) were positive. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT45">2012a</xref>) admitted that this platform “apparently managed to separate – if not all, but most – of the wheat from the chaff”, since a large number of duplicates were identified and corrected. In addition, the fact that it allowed the authors themselves to correct and edit the descriptive metadata of their articles could help in the medium and long term to improve the quality of the data, so the system was seen as promising. However, many inherited errors were still present (some of which the authors themselves could not correct, for instance separating versions of documents that had been incorrectly merged by the system).</p>

			<p>Moreover, Google Scholar Citations has its own errors. For example, in the automatic generation of co-authors, Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT45">2012a</xref>) criticised the fact that in his own list there were authors with whom he had not published: “most of them I have not heard of, let al.one known or worked with”. At present, this process has improved considerably, although many of the errors are the result of actions, deliberate or not, of the authors themselves, who, through interest, negligence or incompetence may have incorrectly filled in the various personal information fields or edited the description of a document. The number of citations received per document is a value automatically calculated by Google Scholar, in which authors can not intervene. Even so, there are errors in the processes that are performed automatically. For example, Doğan et al. (<xref ref-type="bibr" rid="CIT20">2016</xref>), after analysing the profiles of 10 researchers from the Department of Information Management at Hacettepe University, estimated that 55% of their contributions (135) had received duplicate citations, representing approximately 12% of the total number of citations received. Mart&#x00ED;n-Mart&#x00ED;n et al. (<xref ref-type="bibr" rid="CIT59">2016c</xref>) also detected duplicate documents, incorrectly merged documents and incorrect titles when analysing the GSM profiles for 814 bibliometrics researchers. Subsequently, Orduna-Malea et al. (<xref ref-type="bibr" rid="CIT70">2017</xref>) detected and classified errors in the automatic linking of authors with their institutional affiliations, in the case of the Spanish university system (wrong by normalised names, disambiguation problems, incorrect linking, multiple official academic web domains, errors with complex, multiple and internal affiliations).</p>

			<p>With regard to Google Scholar Metrics, impressions were similar. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT48">2012d</xref>) described the service as a potentially useful and complementary tool for journals, although he also acknowledged that the information provided, while it is an improvement, is only “plastic surgery”, and that “the parsing and citation matching components require brain surgery to qualify GSM for bibliometric purposes at the journal level”.</p>

			<p>Apart from the errors inherited from Google Scholar, GSM also has errors of its own making, such as linking articles to the wrong journals. Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT48">2012d</xref>) was surprised that GS occasionally provided correct data but that, subsequently, GSM attributed an article to the wrong journal. These attribution errors consequently caused errors in the attribution of the h5-index of publications.</p>

			<p>Also noteworthy are the annual reports from the EC3 Research Group on the release of each new version of GSM (Mart&#x00ED;n-Mart&#x00ED;n et al. <xref ref-type="bibr" rid="CIT55">2014a</xref>; <xref ref-type="bibr" rid="CIT57">2016a</xref>). These reports have enabled us to explore a wider variety of errors, particularly those related to normalisation problems (unification of journal titles, problems in the linking of documents, and problems in the search and retrieval of publication titles).</p>

			</sec>
			</sec>
			
			<sec id="S3.4">
			<title>3.4. Classification of errors </title>

			<p>The last body of publications on Google Scholar errors has tried to categorise and classify existing errors. However, it should be pointed out that these classifications are not only incomplete (not reflecting all types of errors), but were carried out in a way that complemented or supplemented the original work, the main objectives of which were not to create or construct a taxonomy of errors. For example, the most detailed classification (although it mainly focuses on parsing aspects) is found in the work of Adriaanse and Rensleigh (<xref ref-type="bibr" rid="CIT04">2013</xref>), whose analysis was based on a sample of only 14 South African environment journals.</p>

			<p>In any case, and given their interest, <xref ref-type="table" rid="T6">Table VI</xref> is a compilation of the main types of errors published to date, the article in which they appeared, and their main items.</p>
			
						<fig id="T6">
							<label>Table VI</label>
							<caption>
								<title>Error Classifications in Google Scholar </title>
							</caption>
							<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/T6.jpg"/>
						</fig>

			</sec>
		</sec>
		
		<sec id="S4">
			<title>4. DISCUSSION AND CONCLUSIONS</title>

			<p>The results of our qualitative analysis reveal that the bibliographical corpus on errors in Google Scholar is still limited. The bibliographic review process yielded a total of 49 publications, of which only a small percentage deals in any depth with the concept of errors and even fewer contribute empirical data.</p>

			<p>With the exception of P&#x00E9;ter Jacs&#x00F3;’s work, we can only point to two articles written with the goal of directly ascertaining how errors in Google Scholar function and what their impact is: Doğan et al. (<xref ref-type="bibr" rid="CIT20">2016</xref>) and Orduna-Malea et al. (<xref ref-type="bibr" rid="CIT70">2017</xref>). Other works of great interest, such as those by Harzing and Van der Wal (<xref ref-type="bibr" rid="CIT30">2008</xref>), Baneyx (<xref ref-type="bibr" rid="CIT06">2008</xref>), Li et al. (<xref ref-type="bibr" rid="CIT52">2010</xref>), Adriaanse and Rensleigh (<xref ref-type="bibr" rid="CIT03">2011</xref>; <xref ref-type="bibr" rid="CIT04">2013</xref>), and De Winter et al. (<xref ref-type="bibr" rid="CIT18">2014</xref>), in spite of their contributions to the knowledge of errors in Google Scholar, have addressed this issue in an indirect, circumstantial, secondary or at worst incidental way.</p>

			<p>This means that, in general terms, scholarly literature about errors in Google Scholar, particularly articles focusing on the use of this tool in bibliometric analysis, is scarce, excessively fragmented and diffuse. There are no studies in which research designs have been specifically developed not only to identify but also to quantify the errors and evaluate their consequences. Studies that do touch on the question of errors were designed with other objectives in mind, and when they address the issue, they often arrive at conclusions that are all too apparent (that there are errors is obvious). In addition, the few studies that provide empirical evidence (albeit indirectly) are not comparable because they deal with completely different samples with different units and research objectives.</p>

			<p>Given the importance of quantifying and evaluating the consequences of errors in Google Scholar, since this database is widely used in both bibliometric analysis and in academic evaluation processes (whether we like it or not), it is quite remarkable that the bibliometric community has not undertaken more studies of this nature. The experts that have been most critical of Google Scholar, with the exception of Jacs&#x00F3;, have criticised the database on the basis of its errors, but have not studied their true impact on bibliometric analysis, especially in the context of a big data system that is forcibly transforming the postulates on which many bibliometric studies have been based. These studies are limited – for better or for worse – by the capabilities of the available bibliographic sources, which to date have been controlled and supervised.</p>

			<p>One of the possible reasons is the recognised difficulty in evaluating the errors themselves, due to certain substantial limitations (limit of 1,000 search results, limit of 1,000 citing documents per result, with hardly any options for ordering the results, etc.). This is something that has been strongly criticised by Jacs&#x00F3; (<xref ref-type="bibr" rid="CIT36">2006a</xref>; <xref ref-type="bibr" rid="CIT40">2008c</xref>; <xref ref-type="bibr" rid="CIT46">2012b</xref>), while Meho and Yang (<xref ref-type="bibr" rid="CIT61">2007</xref>) have already criticised the excessive time required to clean up the data.</p>

			<p>For this reason, few studies have shed light on the real effects of existing errors. Sanderson (<xref ref-type="bibr" rid="CIT79">2008</xref>), who calculated the h-index in detail for 3 British researchers, concluded that, after correcting the errors, the h-index had been underestimated by 5-10%. Li et al. (<xref ref-type="bibr" rid="CIT52">2010</xref>), who also acknowledged the excessive data processing time required by Google Scholar, showed that data cleaning processes have, after all, little effect on results, something that had already been partially demonstrated by Baneyx (2008), albeit with very small samples. Doğan et al. (<xref ref-type="bibr" rid="CIT20">2016</xref>) were the first to systematically calculate various indicators before and after cleaning the data (in this case in Google Scholar Metrics). Although the authors concluded that the differences in the calculation of the h-index and the i10-index before and after eliminating duplicates (of both records and received citations) were statistically significant, an analysis of their results leads us to question their conclusion, since the differences, even when they exist, are not so significant. In fact, the h-index does not change for any of the authors after deleting the duplicate records, although it does change slightly after deleting duplicate citations (the most extreme case falls from 16 to 13). In these cases, the level of profile editing and maintenance (even possible manipulation) by the authors themselves has a direct influence on these differences.</p>

			<p>Lastly, as regards Jacs&#x00F3;’s work, his quite considerable body of work identifying, discovering, testing and disseminating the errors and limitations of Google Scholar are worthy of recognition. Undoubtedly, he is the author who has most contributed to the serious, rigorous and non-opinionated analysis of this database, so that it may be used for bibliometric purposes. Nevertheless, we would venture to mention some limitations or shortcomings in his extensive scholarly output. Regrettably, Jacs&#x00F3;’s work does not reveal all the errors in Google Scholar, although it does expose the most notorious and flagrant, a fact that has led to an improved service. Many of the errors are perhaps repeated excessively throughout his work as practical examples and, beyond the self-explanatory screenshots, greater detail would not have gone amiss in some of the methodological aspects, which are sometimes lacking or only partly sketched out. The design of an exhaustive systematic classification of errors, as well as an estimation of the overall magnitude of these errors, beyond simple exemplification, is also lacking. This has become particularly relevant since 2012 (when P&#x00E9;ter Jacs&#x00F3;’s contributions ceased and GSC and GSM appeared on the scene).</p>

			<p>The evolution of Google Scholar (both in coverage and data quality) must be continually evaluated because of the speed at which its database is updated. Nevertheless, the tests performed in the course of this study have shown that most of the errors reported by Jacs&#x00F3; (especially parsing and searching errors) are still present today. However, the calculation of bibliometric indicators (citations received, h-index) has improved, thanks in no small measure to the development and evolution of GSM and GSC (predicted by Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT45">2012a</xref>). Only the calculation of error rates (by type of error), with large samples and by discipline, will allow us to rigorously appraise the suitability of the system for use as a complement to the evaluation of academic impact.</p>					
		</sec>
			

	</body>

	<back>
	
		<ack>
			<title>ACKNOWLEDGEMENTS</title>

			<p>Alberto Mart&#x00ED;n-Mart&#x00ED;n is on a four-year doctoral fellowship (FPU2013/05863) granted by the Ministerio de Educaci&#x00F3;n, Cultura y Deportes (Spain). Enrique Orduna-Malea holds a postdoctoral fellowship (PAID-10-14), from the Polytechnic University of Valencia (Spain). This manuscript has been translated  by professional native translator Charles Balfour.</p>
			
			<p><bold>AGRADECIMIENTOS</bold></p>

			<p>Alberto Mart&#x00ED;n-Mart&#x00ED;n est&#x00E1; en cuarto a&#x00F1;o de la beca de doctorado (FPU2013/05863) otorgada por el Ministerio de educaci&#x00F3;n Cultura y Deportes (espa&#x00F1;a). Enrique Ordu&#x00F1;a-Malea es becario postdoctoral (PAID-10-14) de la Universidad Polit&#x00E9;cnica de Valencia. (Espa&#x00F1;a). Este art&#x00ED;culo ha sido traducido por el traductor profesional Charles Balfour.</p>
			
		</ack>
	
		<sec id="notas">
			<title>NOTES</title>
		
			<fn-group>
		
				<fn id="NOTE1"><label>1</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://scholar.google.com/intl/en/scholar/about.html">https://scholar.google.com/intl/en/scholar/about.html</ext-link>.</p>
				</fn>
				
				<fn id="NOTE2"><label>2</label>
					<p>Like many informal articles published about Google Scholar between 2004 and 2005, this document is no longer available online, and has been retrieved from the Wayback Machine (archive.org). See bibliography.</p>
				</fn>
				
				<fn id="NOTE3"><label>3</label>
					<p><ext-link ext-link-type="uri" xlink:href="http://www.searchengineshowdown.com/blog/2008/01/scholar_down_books_up.shtml">http://www.searchengineshowdown.com/blog/2008/01/scholar_down_books_up.shtml</ext-link></p>
				</fn>
				
				<fn id="NOTE4"><label>4</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://techcrunch.com/2007/12/22/2007-in-numbers-igoogle-googles-homegrown-star-performer-this-year/">https://techcrunch.com/2007/12/22/2007-in-numbers-igoogle-googles-homegrown-star-performer-this-year/</ext-link></p>
				</fn>
				
				<fn id="NOTE5"><label>5</label>
					<p>Google Scholar Blog, available at: <ext-link ext-link-type="uri" xlink:href="http://weblogs.elearning.ubc.ca/googlescholar/">http://weblogs.elearning.ubc.ca/googlescholar/</ext-link></p>
				</fn>
				
				<fn id="NOTE6"><label>6</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://scholar.google.com/intl/en/scholar/inclusion.html#content">https://scholar.google.com/intl/en/scholar/inclusion.html#content</ext-link></p>
				</fn>
				
				<fn id="NOTE7"><label>7</label>
					<p>It should be remembered that the number of citations was the criterion used by Google Scholar to rank the results (Jacs&#x00F3;, <xref ref-type="bibr" rid="CIT39">2008b</xref>). As of 2007/2008, new ranking criteria (<ext-link ext-link-type="uri" xlink:href="http://scholar.google.com/intl/en/scholar/about.html">http://scholar.google.com/intl/en/scholar/about.html</ext-link>) were introduced, of which citations is only one, though important, criterion (Mart&#x00ED;n-Mart&#x00ED;n et al., <xref ref-type="bibr" rid="CIT60">2017</xref>).</p>
				</fn>
				
				<fn id="NOTE8"><label>8</label>
					<p><ext-link ext-link-type="uri" xlink:href="http://wokinfo.com/googlescholar/">http://wokinfo.com/googlescholar/</ext-link></p>
				</fn>
				
				<fn id="NOTE9"><label>9</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://www.harzing.com/resources/publish-or-perish">https://www.harzing.com/resources/publish-or-perish</ext-link></p>
				</fn>
				
				<fn id="NOTE10"><label>10</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://scholar.googleblog.com/2011/11/google-scholar-citations-open-to-all.html">https://scholar.googleblog.com/2011/11/google-scholar-citations-open-to-all.html</ext-link></p>
				</fn>
				
				<fn id="NOTE11"><label>11</label>
					<p><ext-link ext-link-type="uri" xlink:href="https://scholar.googleblog.com/2012/04/google-scholar-metrics-for-publications.html">https://scholar.googleblog.com/2012/04/google-scholar-metrics-for-publications.html</ext-link></p>
				</fn>
			</fn-group>
		</sec>
	
	
	
		<ref-list>
			<title>REFERENCES</title>

			<ref id="CIT01">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Abram</surname>
					  <given-names>S.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Google Scholar: thin edge of the wedge?</article-title>
			  <source>Information Outlook</source>
			  <volume>9</volume>
			  <issue>1</issue>
			  <fpage>44</fpage>
			  <lpage>46</lpage>
			</element-citation>
			</ref>

			<ref id="CIT02">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Adlington</surname>
					  <given-names>J.</given-names>	  
				  </name>
				  <name>
					  <surname>Benda</surname>
					  <given-names>C.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006</year>
			  <article-title>Checking under the hood: evaluating Google scholar for reference use</article-title>
			  <source>Internet Reference Services Quarterly</source>
			  <volume>10</volume>
			  <issue>3/4</issue>
			  <fpage>135</fpage>
			  <lpage>148</lpage>
			</element-citation>
			</ref>

			<ref id="CIT03">
			<element-citation publication-type="conf-proc">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Adriaanse</surname>
					  <given-names>L.</given-names>	  
				  </name>
				  <name>
					  <surname>Rensleigh</surname>
					  <given-names>C.</given-names>	  
				  </name>
			  </person-group>
			  <year>2011</year>
			  <article-title>Content versus quality: a Web of Science, Scopus and Google Scholar comparison</article-title>
			  <conf-name>13th Annual Conference on World Wide Web applications</conf-name>
			  <publisher-loc>Johannesburg, South Africa</publisher-loc>
			  <publisher-name>Cape Peninsula University of Technology</publisher-name>
			  <fpage>5</fpage>
			  <lpage>18</lpage>
			</element-citation>
			</ref>

			<ref id="CIT04">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Adriaanse</surname>
					  <given-names>L.</given-names>	  
				  </name>
				   <name>
					  <surname>Rensleigh</surname>
					  <given-names>C.</given-names>	  
				  </name>
			  </person-group>
			  <year>2013</year>
			  <article-title>Web of Science, Scopus and Google Scholar: A content comprehensiveness comparison</article-title>
			  <source>The Electronic Library</source>
			  <volume>31</volume>
			  <issue>6</issue>
			  <fpage>727</fpage>
			  <lpage>744</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/el-12-2011-0174">https://doi.org/10.1108/el-12-2011-0174</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT05">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Aguillo</surname>
					  <given-names>Isidro F.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012</year>
			  <article-title>Is Google Scholar useful for bibliometrics? A webometric analysis</article-title>
			  <source>Scientometrics</source>
			  <volume>91</volume>
			  <issue>2</issue>
			  <fpage>343</fpage>
			  <lpage>351</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1007/s11192-011-0582-8">http://dx.doi.org/10.1007/s11192-011-0582-8</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT06">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Baneyx</surname>
					  <given-names>A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <article-title>"Publish or Perish" as citation metrics used to analyze scientific output in the humanities: International case studies in Economics, Geography, Social Sciences, Philosophy, and History</article-title>
			  <source>Archivium Immunologiae et Therapiae Experimentalis</source>
			  <volume>56</volume>
			  <issue>6</issue>
			  <fpage>363</fpage>
			  <lpage>371</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s00005-008-0043-0">https://doi.org/10.1007/s00005-008-0043-0</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT07">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bar-Ilan</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006</year>
			  <article-title>An ego-centric citation analysis of the works of Michael O. Rabin based on multiple citation indexes</article-title>
			  <source>Information Processing &amp; Management</source>
			  <volume>42</volume>
			  <issue>6</issue>
			  <fpage>1553</fpage>
			  <lpage>1566</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.ipm.2006.03.019">https://doi.org/10.1016/j.ipm.2006.03.019</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT08">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bar-Ilan</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <article-title>Which h-index?-A comparison of WoS, Scopus and Google Scholar</article-title>
			  <source>Scientometrics</source>
			  <volume>74</volume>
			  <issue>2</issue>
			  <fpage>257</fpage>
			  <lpage>271</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-008-0216-y">https://doi.org/10.1007/s11192-008-0216-y</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT09">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bar-Ilan</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2010</year>
			  <article-title>Citations to the "Introduction to informetrics" indexed by WOS, Scopus and Google Scholar</article-title>
			  <source>Scientometrics</source>
			  <volume>82</volume>
			  <issue>3</issue>
			  <fpage>495</fpage>
			  <lpage>506</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-010-0185-9">https://doi.org/10.1007/s11192-010-0185-9</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT10"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bauer</surname>
					  <given-names>K.</given-names>	  
				  </name>
				  <name>
					  <surname>Bakkalbasi</surname>
					  <given-names>N.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>An examination of citation counts in a new scholarly communication environment</article-title>
			  <source>D-Lib magazine</source>
			  <volume>11</volume>
			  <issue>9</issue>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1045/september2005-bauer">https://doi.org/10.1045/september2005-bauer</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT11">
			<element-citation publication-type="conf-proc">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Beel</surname>
					  <given-names>J.</given-names>	  
				  </name>
				  <name>
					  <surname>Gipp</surname>
					  <given-names>B.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>Google Scholar's ranking algorithm: an introductory overview</article-title>
			  <conf-name>Proceedings of the 12th international conference on scientometrics and informetrics</conf-name>
			  <conf-loc>Rio de Janeiro, Brazil</conf-loc>
			  <publisher-name>ISSI</publisher-name>
			  <fpage>230</fpage>
			  <lpage>241</lpage>
			</element-citation>
			</ref>

			<ref id="CIT12">
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Belew</surname>
					  <given-names>R.K.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Scientific impact quantity and quality: analysis of two sources of bibliographic data</article-title>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://www.cogsci.ucsd.edu/~rik/papers/belew05-iqq.pdf">http://www.cogsci.ucsd.edu/~rik/papers/belew05-iqq.pdf</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT13">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bensman</surname>
					  <given-names>S.J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012</year>
			  <article-title>The impact factor: its place in Garfield's thought, in science evaluation, and in library collection management</article-title>
			  <source>Scientometrics</source>
			  <volume>92</volume>
			  <issue>2</issue>
			  <fpage>263</fpage>
			  <lpage>275</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-011-0601-9">https://doi.org/10.1007/s11192-011-0601-9</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT14">
			<element-citation publication-type="report">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Bosman</surname>
					  <given-names>J.</given-names>	  
				  </name>
				  <name>
					  <surname>Mourik</surname>
					  <given-names>I.</given-names>	  
				  </name>
				  <name>
					  <surname>Van Rasch</surname>
					  <given-names>M.</given-names>	  
				  </name>
				  <name>
					  <surname>Sieverts</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Verhoeff</surname>
					  <given-names>H.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006</year>
			  <source>Scopus reviewed and compared. The coverage and functionality of the citation database Scopus, including comparisons with Web of Science and Google Scholar</source>
			  <publisher-name>Utrecht University Library</publisher-name>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://dspace.library.uu.nl/handle/1874/18247">https://dspace.library.uu.nl/handle/1874/18247</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT15">
			<element-citation publication-type="report">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Breeding</surname>
					  <given-names>M.</given-names>
				  </name>		  
			  </person-group>
			  <year>2015</year>
			  <source>The future of library resource discovery</source>
			  <series>NISO Whitepapers</series>
			  <publisher-loc>Baltimore, United States</publisher-loc>
			  <publisher-name>NISO</publisher-name>  
			</element-citation>
			</ref>

			<ref id="CIT16">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Butler</surname>
					  <given-names>D.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>Science searches shift up a gear as Google starts Scholar Engine</article-title>
			  <source>Nature</source>
			  <volume>432</volume>
			  <fpage>423</fpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1038/432423a">https://doi.org/10.1038/432423a</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT17">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Butler</surname>
					  <given-names>L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2011</year>
			  <article-title>The devil is in the detail: Concerns about Vanclay's analysis of Australian journal rankings</article-title>
			  <source>Journal of Informetrics</source>
			  <volume>5</volume>
			  <issue>4</issue>
			  <fpage>693</fpage>
			  <lpage>694</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.joi.2011.04.001">https://doi.org/10.1016/j.joi.2011.04.001</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT18">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>De Winter</surname>
					  <given-names>J.C.</given-names>	  
				  </name>
				  <name>
					  <surname>Zadpoor</surname>
					  <given-names>A.A.</given-names>	  
				  </name>
				  <name>
					  <surname>Dodou</surname>
					  <given-names>D.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014</year>
			  <article-title>The expansion of Google Scholar versus Web of Science: a longitudinal study</article-title>
			  <source>Scientometrics</source>
			  <volume>98</volume>
			  <issue>2</issue>
			  <fpage>1547</fpage>
			  <lpage>1565</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-013-1089-2">https://doi.org/10.1007/s11192-013-1089-2</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT19">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Dilger</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>M&#x00FC;ller</surname>
					  <given-names>H.</given-names>	  
				  </name>
			  </person-group>
			  <year>2013</year>
			  <article-title>A citation-based ranking of German-speaking researchers in business administration with data of Google Scholar</article-title>
			  <source>European Journal of Higher Education</source>
			  <volume>3</volume>
			  <issue>2</issue>
			  <fpage>140</fpage>
			  <lpage>150</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1080/21568235.2013.779464">https://doi.org/10.1080/21568235.2013.779464</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT20">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Doğan</surname>
					  <given-names>G.</given-names>	  
				  </name>
				  <name>
					  <surname>Şencan</surname>
					  <given-names>İ.</given-names>	  
				  </name>
				  <name>
					  <surname>Tonta</surname>
					  <given-names>Y.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016</year>
			  <article-title>Does dirty data affect google scholar citations?</article-title>
			  <source>Proceedings of the Association for Information Science and Technology</source>
			  <volume>53</volume>
			  <issue>1</issue>
			  <fpage>1</fpage>
			  <lpage>4</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/pra2.2016.14505301098">https://doi.org/10.1002/pra2.2016.14505301098</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT21">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Felter</surname>
					  <given-names>L.M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>The better mousetrap: Google Scholar, Scirus, and the Scholarly Search Revolution</article-title>
			  <source>Searcher</source>
			  <volume>13</volume>
			  <issue>2</issue>
			  <fpage>43</fpage>
			  <lpage>48</lpage>
			</element-citation>
			</ref>

			<ref id="CIT22"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Garc&#x00ED;a-P&#x00E9;rez</surname>
					  <given-names>M.A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2010</year>
			  <article-title>Accuracy and completeness of publication and citation records in the Web of Science, PsycINFO, and Google Scholar: A case study for the computation of h indices in Psychology</article-title>
			  <source>Journal of the Association for Information Science and Technology</source>
			  <volume>61</volume>
			  <issue>10</issue>
			  <fpage>2070</fpage>
			  <lpage>2085</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/asi.21372">https://doi.org/10.1002/asi.21372</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT23">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Gardner</surname>
					  <given-names>S.</given-names>	  
				  </name>
				  <name>
					  <surname>Eng</surname>
					  <given-names>S.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Gaga over Google? Scholar in the social sciences</article-title>
			  <source>Library Hi Tech News</source>
			  <volume>22</volume>
			  <issue>8</issue>
			  <fpage>42</fpage>
			  <lpage>45</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/07419050510633952">https://doi.org/10.1108/07419050510633952</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT24">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Giles</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Science in the web age: Start your engines</article-title>
			  <source>Nature</source>
			  <volume>438</volume>
			  <issue>7068</issue>
			  <fpage>554</fpage>
			  <lpage>555</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1038/438554a">https://doi.org/10.1038/438554a</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT25"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Goodman</surname>
					  <given-names>A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>Google Scholar vs. Real Scholarship</article-title>
			  <source>Traffic</source>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://www.traffick.com/2004/11/google-scholar-vs-real-scholarship.asp">http://www.traffick.com/2004/11/google-scholar-vs-real-scholarship.asp</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT26">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Haddaway</surname>
					  <given-names>N.R.</given-names>	  
				  </name>
				  <name>
					  <surname>Collins</surname>
					  <given-names>A.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Coughlin</surname>
					  <given-names>D.</given-names>	  
				  </name>
				  <name>
					  <surname>Kirk</surname>
					  <given-names>S.</given-names>	  
				  </name>
			  </person-group>
			  <year>2015</year>
			  <article-title>The role of Google Scholar in evidence reviews and its applicability to grey literature searching</article-title>
			  <source>PloS one</source>
			  <volume>10</volume>
			  <issue>9</issue>
			  <fpage>e0138237</fpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1371/journal.pone.0138237">https://doi.org/10.1371/journal.pone.0138237</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT27">
			<element-citation publication-type="book">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Harzing</surname>
					  <given-names>A.W.</given-names>	  
				  </name>
			  </person-group>
			  <year>2010</year>
			  <source>The publish or perish book</source> 
			  <publisher-loc>Melbourne</publisher-loc>
			  <publisher-name>Tarma software research</publisher-name>  
			</element-citation>
			</ref>

			<ref id="CIT28">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Harzing</surname>
					  <given-names>A.W.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014</year>
			  <article-title>A longitudinal study of Google Scholar coverage between 2012 and 2013</article-title>
			  <source>Scientometrics</source>
			  <volume>98</volume>
			  <issue>1</issue>
			  <fpage>565</fpage>
			  <lpage>575</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-013-0975-y">https://doi.org/10.1007/s11192-013-0975-y</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT29">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Harzing</surname>
					  <given-names>A-W.</given-names>	  
				  </name>
				  <name>
					  <surname>Alakangas</surname>
					  <given-names>S.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016</year>
			  <article-title>Google Scholar, Scopus and the Web of Science: a longitudinal and cross-disciplinary comparison</article-title>
			  <source>Scientometrics</source>
			  <volume>106</volume>
			  <issue>2</issue>
			  <fpage>787</fpage>
			  <lpage>804</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-015-1798-9">https://doi.org/10.1007/s11192-015-1798-9</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT30"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Harzing</surname>
					  <given-names>A.W.</given-names>	  
				  </name>
				  <name>
					  <surname>Van der Wal</surname>
					  <given-names>R.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <article-title>Google Scholar as a new source for citation analysis</article-title>
			  <source>Ethics in science and environmental politics</source>
			  <volume>8</volume>
			  <issue>1</issue>
			  <fpage>61</fpage>
			  <lpage>73</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3354/esep00076">https://doi.org/10.3354/esep00076</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT31">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Hirsch</surname>
					  <given-names>J.E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>An index to quantify an individual’s scientific research output</article-title>
			  <source>Proceedings of the National academy of Sciences of the United States of America</source>
			  <volume>102</volume>
			  <issue>46</issue>
			  <fpage>16569</fpage>
			  <lpage>16572</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1073/pnas.0507655102">https://doi.org/10.1073/pnas.0507655102</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT32">
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>P&#x00E9;ter’s digital ready reference shelf</article-title>
			  <comment>(web-only document). Available at: <ext-link ext-link-type="uri" xlink:href="​https://goo.gl/zFygFd">​https://goo.gl/zFygFd</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT33">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005a</year>
			  <article-title>As we may search: Comparison of major features of the Web of Science, Scopus, and Google Scholar citation-based and citation-enhanced databases</article-title>
			  <source>Current science</source>
			  <volume>89</volume>
			  <issue>9</issue>
			  <fpage>1537</fpage>
			  <lpage>1547</lpage>
			</element-citation>
			</ref>

			<ref id="CIT34">
			<element-citation publication-type="conf-proc">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005b</year>
			  <article-title>Comparison and analysis of the citedness scores in Web of Science and Google Scholar</article-title>
			  <conf-name>International Conference on Asian Digital Libraries</conf-name>
			  <publisher-loc>Berlin; Heidelberg, Germany</publisher-loc>
			  <publisher-name>Springer</publisher-name>
			  <fpage>360</fpage>
			  <lpage>369</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/11599517_41">https://doi.org/10.1007/11599517_41</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT35">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005c</year>
			  <article-title>Google Scholar: the pros and the cons</article-title>
			  <source>Online information review</source>
			  <volume>29</volume>
			  <issue>2</issue>
			  <fpage>208</fpage>
			  <lpage>214</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1108/14684520510598066">http://dx.doi.org/10.1108/14684520510598066</ext-link></comment>
			</element-citation>
			</ref>
		
			<ref id="CIT36">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006a</year>
			  <article-title>Deflated, inflated, and phantom citation counts</article-title>
			  <source>Online Information Review</source>
			  <volume>30</volume>
			  <issue>3</issue>
			  <fpage>297</fpage>
			  <lpage>309</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1108/14684520610675816">http://dx.doi.org/10.1108/14684520610675816</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT37"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006b</year>
			  <article-title>Dubious hit counts and cuckoo’s eggs</article-title>
			  <source>Online Information Review</source>
			  <volume>30</volume>
			  <issue>2</issue>
			  <fpage>188</fpage>
			  <lpage>193</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684520610659201">https://doi.org/10.1108/14684520610659201</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT38"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008a</year>
			  <article-title>Google scholar revisited</article-title>
			  <source>Online Information Review</source>
			  <volume>32</volume>
			  <issue>1</issue>
			  <fpage>102</fpage>
			  <lpage>114</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684520810866010">https://doi.org/10.1108/14684520810866010</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT39"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008b</year>
			  <article-title>The pros and cons of computing the h-index using Google Scholar</article-title>
			  <source>Online Information Review</source>
			  <volume>32</volume>
			  <issue>3</issue>
			  <fpage>437</fpage>
			  <lpage>452</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1108/14684520810889718">http://dx.doi.org/10.1108/14684520810889718</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT40">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008c</year>
			  <article-title>Testing the calculation of a realistic h-index in Google Scholar, Scopus, and Web of Science for F.W. Lancaster</article-title>
			  <source>Library Trends</source>
			  <volume>56</volume>
			  <issue>4</issue>
			  <fpage>784</fpage>
			  <lpage>815</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1353/lib.0.0011">https://doi.org/10.1353/lib.0.0011</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT41">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009a</year>
			  <article-title>Calculating the h-index and other bibliometric and scientometric indicators from Google Scholar with the Publish or Perish software</article-title>
			  <source>Online Information Review</source>
			  <volume>33</volume>
			  <issue>6</issue>
			  <fpage>1189</fpage>
			  <lpage>1200</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684520911011070">https://doi.org/10.1108/14684520911011070</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT42">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009b</year>
			  <article-title>Google Scholar’s Ghost Authors</article-title>
			  <source>Library Journal</source>
			  <volume>134</volume>
			  <issue>18</issue>
			  <fpage>26</fpage>
			  <lpage>27</lpage>
			</element-citation>
			</ref>

			<ref id="CIT43">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2010</year>
			  <article-title>Metadata mega mess in Google Scholar</article-title>
			  <source>Online Information Review</source>
			  <volume>34</volume>
			  <issue>1</issue>
			  <fpage>175</fpage>
			  <lpage>191</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684521011024191">https://doi.org/10.1108/14684521011024191</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT44">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2011</year>
			  <article-title>Google Scholar duped and deduped–the aura of “robometrics”</article-title>
			  <source>Online Information Review</source>
			  <volume>35</volume>
			  <issue>1</issue>
			  <fpage>154</fpage>
			  <lpage>160</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684521111113632">https://doi.org/10.1108/14684521111113632</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT45">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012a</year>
			  <article-title>Google Scholar Author Citation Tracker: is it too little, too late?</article-title>
			  <source>Online Information Review</source>
			  <volume>36</volume>
			  <issue>1</issue>
			  <fpage>126</fpage>
			  <lpage>141</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684521211209581">https://doi.org/10.1108/14684521211209581</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT46">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012b</year>
			  <article-title>Grim tales about the impact factor and the h-index in the Web of Science and the Journal Citation Reports databases: Reflections on Vanclay’s criticism</article-title>
			  <source>Scientometrics</source>
			  <volume>92</volume>
			  <issue>2</issue>
			  <fpage>325</fpage>
			  <lpage>354</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-012-0769-7">https://doi.org/10.1007/s11192-012-0769-7</ext-link></comment>
			</element-citation>
			</ref>
	
			<ref id="CIT47">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012c</year>
			  <article-title>Using Google Scholar for journal impact factors and the h-index in nationwide publishing assessments in academia – siren songs and air-raid sirens</article-title>
			  <source>Online Information Review</source>
			  <volume>36</volume>
			  <issue>3</issue>
			  <fpage>462</fpage>
			  <lpage>478</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1108/14684521211241503">http://dx.doi.org/10.1108/14684521211241503</ext-link></comment>
			</element-citation>
			</ref>
					
			<ref id="CIT48">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Jacs&#x00F3;</surname>
					  <given-names>P.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012d</year>
			  <article-title>Google Scholar Metrics for Publications: The software and content features of a new open access bibliometric service</article-title>
			  <source>Online Information Review</source>
			  <volume>36</volume>
			  <issue>4</issue>
			  <fpage>604</fpage>
			  <lpage>619</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684521211254121">https://doi.org/10.1108/14684521211254121</ext-link></comment>
			</element-citation>
			</ref>
	
			<ref id="CIT49">
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Kennedy</surname>
					  <given-names>S.</given-names>	  
				  </name>
				  <name>
					  <surname>Price</surname>
					  <given-names>G.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>Big News: “Google Scholar” is Born</article-title>
			  <source>Resourceshelf</source>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://web.resourceshelf.com/go/resourceblog/40511">http://web.resourceshelf.com/go/resourceblog/40511</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT50">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Leslie</surname>
					  <given-names>M.A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>A Google for academia</article-title>
			  <source>Science</source>
			  <volume>306</volume>
			  <issue>5702</issue>
			  <fpage>1661</fpage>
			  <lpage>1663</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1126/science.306.5702.1661c">https://doi.org/10.1126/science.306.5702.1661c</ext-link></comment>
			</element-citation>
			</ref>
		
			<ref id="CIT51">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Levine-Clark</surname>
					  <given-names>M.</given-names>	  
				  </name>
				  <name>
					  <surname>Gil</surname>
					  <given-names>E.L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>A comparative citation analysis of Web of Science, Scopus and Google Scholar</article-title>
			  <source>Journal of Business and Finance Librarianship</source>
			  <volume>14</volume>
			  <issue>1</issue>
			  <fpage>32</fpage>
			  <lpage>46</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1080/08963560802176348">https://doi.org/10.1080/08963560802176348</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT52">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Li</surname>
					  <given-names>J.</given-names>	  
				  </name>
				  <name>
					  <surname>Sanderson</surname>
					  <given-names>M.</given-names>	  
				  </name>
				  <name>
					  <surname>Willett</surname>
					  <given-names>P.</given-names>	  
				  </name>
				  <name>
					  <surname>Norris</surname>
					  <given-names>M.</given-names>	  
				  </name>
				  <name>
					  <surname>Oppenheim</surname>
					  <given-names>C.</given-names>	  
				  </name>
			  </person-group>
			  <year>2010</year>
			  <article-title>Ranking of library and information science researchers: Comparison of data sources for correlating citation data, and expert judgments</article-title>
			  <source>Journal of Informetrics</source>
			  <volume>4</volume>
			  <issue>4</issue>
			  <fpage>554</fpage>
			  <lpage>563</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.joi.2010.06.005">https://doi.org/10.1016/j.joi.2010.06.005</ext-link></comment>
			</element-citation>
			</ref>
		
			<ref id="CIT53">
			<element-citation publication-type="book">
			  <collab>London School of Economics and Political Science</collab>
			  <year>2011</year>
			  <source>Maximizing the impacts of your research: A handbook for social scientists</source> 
			  <publisher-loc>UK</publisher-loc>
			  <publisher-name>LSE</publisher-name> 
			<comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://www2.lse.ac.uk/government/research/resgroups/LSEPublicPolicy/Docs/LSE_Impact_Handbook_April_2011.pdf">http://www2.lse.ac.uk/government/research/resgroups/LSEPublicPolicy/Docs/LSE_Impact_Handbook_April_2011.pdf</ext-link></comment>			  
			</element-citation>
			</ref>
		
			<ref id="CIT54">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Maia</surname>
					  <given-names>J.L.</given-names>	  
				  </name>
				  <name>
					  <surname>Di Serio</surname>
					  <given-names>L.C.</given-names>	  
				  </name>
				  <name>
					  <surname>Alves Filho</surname>
					  <given-names>A.G.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016</year>
			  <article-title>Bibliometric research on strategy as practice: exploratory results and source comparison</article-title>
			  <source>Sistemas &amp; Gest&#x00E3;o</source>
			  <volume>10</volume>
			  <issue>4</issue>
			  <fpage>654</fpage>
			  <lpage>669</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.20985/1980-5160.2015.v10n4.662">https://doi.org/10.20985/1980-5160.2015.v10n4.662</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT55">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014a</year>
			  <article-title>Google Scholar Metrics 2014: a low cost bibliometric tool</article-title>
			  <source>EC3 Working Papers</source>
			  <volume>17</volume>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1407.2827">https://arxiv.org/abs/1407.2827</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT56">
			<element-citation publication-type="paper">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014b</year>
			  <article-title>Does Google Scholar contain all highly cited documents (1950-2013)?</article-title>
			  <source>EC3 Working Papers</source>
			  <volume>19</volume>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1410.8464">https://arxiv.org/abs/1410.8464</ext-link></comment>
			</element-citation>
			</ref>
			
			<ref id="CIT57">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016a</year>
			  <article-title>2016 Google Scholar Metrics released: a matter of languages... and something else</article-title>
			  <source>EC3 Working Papers</source>
			  <volume>22</volume>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1607.06260">https://arxiv.org/abs/1607.06260</ext-link></comment>
			</element-citation>
			</ref>
		
			<ref id="CIT58">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016b</year>
			  <article-title>A two-sided academic landscape: snapshot of highly-cited documents in Google Scholar (1950-2013)</article-title>
			  <source>Revista Espa&#x00F1;ola de Documentaci&#x00F3;n Cient&#x00ED;fica</source>
			  <volume>39</volume>
			  <issue>4</issue>
			  <comment><ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.3989/redc.2016.4.1405">http://dx.doi.org/10.3989/redc.2016.4.1405</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT59">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016c</year>
			  <article-title>The counting house: measuring those who count. Presence of Bibliometrics, Scientometrics, Informetrics, Webometrics and Altmetrics in the Google Scholar Citations, ResearcherID, ResearchGate, Mendeley &amp; Twitter</article-title>
			  <source>EC3 Working Papers</source>
			  <volume>21</volume>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://arxiv.org/abs/1602.02412">https://arxiv.org/abs/1602.02412</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT60">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Harzing</surname>
					  <given-names>A.W.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2017</year>
			  <article-title>Can we use Google Scholar to identify highly-cited documents?</article-title>
			  <source>Journal of Informetrics</source>
			  <volume>11</volume>
			  <issue>1</issue>
			  <fpage>152</fpage>
			  <lpage>163</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.joi.2016.11.008">https://doi.org/10.1016/j.joi.2016.11.008</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT61">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Meho</surname>
					  <given-names>L.I.</given-names>	  
				  </name>
				  <name>
					  <surname>Yang</surname>
					  <given-names>K.</given-names>	  
				  </name>
			  </person-group>
			  <year>2007</year>
			  <article-title>Impact of data sources on citation counts and rankings of LIS faculty: Web of Science versus Scopus and Google Scholar</article-title>
			  <source>Journal of the American Society for Information Science and Technology</source>
			  <volume>58</volume>
			  <issue>13</issue>
			  <fpage>2105</fpage>
			  <lpage>2125</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/asi.20677">https://doi.org/10.1002/asi.20677</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT62">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Moed</surname>
					  <given-names>H.F.</given-names>	  
				  </name>
				  <name>
					  <surname>Bar-Ilan</surname>
					  <given-names>J.</given-names>	  
				  </name>
				  <name>
					  <surname>Halevi</surname>
					  <given-names>G.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016</year>
			  <article-title>A new methodology for comparing Google Scholar and Scopus</article-title>
			  <source>Journal of Informetrics</source>
			  <volume>10</volume>
			  <issue>2</issue>
			  <fpage>533</fpage>
			  <lpage>551</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.joi.2016.04.017">https://doi.org/10.1016/j.joi.2016.04.017</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT63">
			<element-citation publication-type="thesis">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Noll</surname>
					  <given-names>H.M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <source>Where Google Scholar Stands on Art: An Evaluation of Content Coverage in Online Databases</source>
			  <publisher-loc>North Carolina</publisher-loc>
			  <publisher-name>University of North Carolina at Chapel Hill</publisher-name>
			  <comment>[Master Thesis]</comment>
			</element-citation>
			</ref>

			<ref id="CIT64">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Noruzi</surname>
					  <given-names>A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Google Scholar: the new generation of citation indexes</article-title>
			  <source>Libri</source>
			  <volume>55</volume>
			  <issue>4</issue>
			  <fpage>170</fpage>
			  <lpage>180</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1515/libr.2005.170">https://doi.org/10.1515/libr.2005.170</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT65">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Notess</surname>
					  <given-names>G.R.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Scholarly web searching: Google Scholar and Scirus</article-title>
			  <source>Online</source>
			  <volume>29</volume>
			  <issue>4</issue>
			  <fpage>39</fpage>
			  <lpage>41</lpage>
			</element-citation>
			</ref>

			<ref id="CIT66"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Nunberg</surname>
					  <given-names>G.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>Google’s book search: A disaster for scholars</article-title>
			  <source>The chronicle of higher education</source>
			  <volume>31</volume>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://www.chronicle.com/article/Googles-Book-Search-A/48245">http://www.chronicle.com/article/Googles-Book-Search-A/48245</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT67">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Oder</surname>
					  <given-names>N.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>Google, ‘the last library’, and millions of metadata mistakes</article-title>
			  <source>Library Journal Academic Newswire</source>
			  <volume>3</volume>
			</element-citation>
			</ref>

			<ref id="CIT68">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Ojala</surname>
					  <given-names>M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Scholarly mistakes</article-title>
			  <source>Online</source>
			  <volume>29</volume>
			  <issue>3</issue>
			  <fpage>26</fpage>
			</element-citation>
			</ref>

			<ref id="CIT69">
			<element-citation publication-type="book">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2016</year>
			  <source>La revoluci&#x00F3;n Google Scholar. Destapando la caja de Pandora acad&#x00E9;mica</source> 
			  <publisher-loc>Granada</publisher-loc>
			  <publisher-name>UNE (Uni&#x00F3;n de Editoriales Universitarias Espa&#x00F1;olas)</publisher-name>  
			</element-citation>
			</ref>

			<ref id="CIT70">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Orduna-Malea</surname>
					  <given-names>E.</given-names>	  
				  </name>
				  <name>
					  <surname>Ayll&#x00F3;n</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
				  <name>
					  <surname>Mart&#x00ED;n-Mart&#x00ED;n</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2017</year>
			  <article-title>The lost academic home: institutional affiliation links in Google Scholar Citations</article-title>
			  <source>Online Information Review</source>
			  <volume>41</volume>
			  <issue>6</issue>
			  <fpage>762</fpage>
			  <lpage>781</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/OIR-10-2016-0302">https://doi.org/10.1108/OIR-10-2016-0302</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT71">
			<element-citation publication-type="book">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Ortega</surname>
					  <given-names>J. L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014</year>
			  <source>Academic search engines: A quantitative outlook</source> 
			  <publisher-loc>Oxford</publisher-loc>
			  <publisher-name>Elsevier</publisher-name> 
			  <comment><ext-link ext-link-type="uri" xlink:href="http://www.sciencedirect.com/science/book/9781843347910">http://www.sciencedirect.com/science/book/9781843347910</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT72">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Ortega</surname>
					  <given-names>J. L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2015</year>
			  <article-title>Relationship between altmetric and bibliometric indicators across academic social sites: The case of CSIC’s members</article-title>
			  <source>Journal of Informetrics</source>
			  <volume>9</volume>
			  <issue>1</issue>
			  <fpage>39</fpage>
			  <lpage>49</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.joi.2014.11.004">https://doi.org/10.1016/j.joi.2014.11.004</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT73">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Pauly</surname>
					  <given-names>D.</given-names>	  
				  </name>
				  <name>
					  <surname>Stergiou</surname>
					  <given-names>K.I.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Equivalence of results from two citation analyses: Thomson ISI’s Citation Index and Google’s Scholar service</article-title>
			  <source>Ethics in Science and Environmental Politics</source>
			  <volume>9</volume>
			  <fpage>33</fpage>
			  <lpage>35</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3354/esep005033">https://doi.org/10.3354/esep005033</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT74">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Perkel</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>The future of citation analysis</article-title>
			  <source>The Scientist</source>
			  <volume>19</volume>
			  <issue>20</issue>
			  <fpage>24</fpage>
			</element-citation>
			</ref>

			<ref id="CIT75">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Pitol</surname>
					  <given-names>S.P.</given-names>	  
				  </name>
				  <name>
					  <surname>De Groote</surname>
					  <given-names>S.L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2014</year>
			  <article-title>Google Scholar versions: do more versions of an article mean greater impact?</article-title>
			  <source>Library Hi Tech</source>
			  <volume>32</volume>
			  <issue>4</issue>
			  <fpage>594</fpage>
			  <lpage>611</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/lht-05-2014-0039">https://doi.org/10.1108/lht-05-2014-0039</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT76">
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Price</surname>
					  <given-names>G.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>Google Scholar documentation and large PDF files</article-title>
			  <source>Search Engine Watch</source>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://searchenginewatch.com/sew/news/2063361/google-scholar-documentation-large-pdf-files">https://searchenginewatch.com/sew/news/2063361/google-scholar-documentation-large-pdf-files</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT77">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Robinson</surname>
					  <given-names>M.L.</given-names>	  
				  </name>
				  <name>
					  <surname>Wusteman</surname>
					  <given-names>J.</given-names>	  
				  </name>
			  </person-group>
			  <year>2007</year>
			  <article-title>Putting Google Scholar to the test: A preliminary study</article-title>
			  <source>Program</source>
			  <volume>41</volume>
			  <issue>1</issue>
			  <fpage>71</fpage>
			  <lpage>80</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/00330330710724908">https://doi.org/10.1108/00330330710724908</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT78"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Rosenstreich</surname>
					  <given-names>D.</given-names>	  
				  </name>
				  <name>
					  <surname>Wooliscroft</surname>
					  <given-names>B.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>Measuring the impact of accounting journals using Google Scholar and the g-index</article-title>
			  <source>The British Accounting Review</source>
			  <volume>41</volume>
			  <issue>4</issue>
			  <fpage>227</fpage>
			  <lpage>239</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.bar.2009.10.002">https://doi.org/10.1016/j.bar.2009.10.002</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT79">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Sanderson</surname>
					  <given-names>M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <article-title>Revisiting h measured on UK LIS and IR academics</article-title>
			  <source>Journal of the American Society for Information Science and Technology</source>
			  <volume>59</volume>
			  <issue>7</issue>
			  <fpage>1184</fpage>
			  <lpage>1190</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/asi.20771">https://doi.org/10.1002/asi.20771</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT80">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Shultz</surname>
					  <given-names>M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2007</year>
			  <article-title>Comparing test searches in PubMed and Google Scholar</article-title>
			  <source>Journal of the Medical Library Association</source>
			  <volume>95</volume>
			  <issue>4</issue>
			  <fpage>442</fpage>
			  <lpage>445</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3163/1536-5050.95.4.442">https://doi.org/10.3163/1536-5050.95.4.442</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT81"> 
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Sullivan</surname>
					  <given-names>D.</given-names>	  
				  </name>
			  </person-group>
			  <year>2004</year>
			  <article-title>Google Scholar Offers Access to Academic Information</article-title>
			  <source>Search Engine Watch</source>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://searchenginewatch.com/sew/news/2048646/google-scholar-offers-access-to-academic-information">https://searchenginewatch.com/sew/news/2048646/google-scholar-offers-access-to-academic-information</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT82">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Thelwall</surname>
					  <given-names>M.</given-names>	  
				  </name>
				  <name>
					  <surname>Kousha</surname>
					  <given-names>K.</given-names>	  
				  </name>
			  </person-group>
			  <year>2017</year>
			  <article-title>ResearchGate versus Google Scholar: Which finds more early citations?</article-title>
			  <source>Scientometrics</source>
			  <volume>112</volume>
			  <issue>2</issue>
			  <fpage>1125</fpage>
			  <lpage>1131</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-017-2400-4">https://doi.org/10.1007/s11192-017-2400-4</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT83">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Thor</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Bornmann</surname>
					  <given-names>L.</given-names>	  
				  </name>
			  </person-group>
			  <year>2011</year>
			  <article-title>The calculation of the single publication h index and related performance measures: A web application based on Google Scholar data</article-title>
			  <source>Online Information Review</source>
			  <volume>35</volume>
			  <issue>2</issue>
			  <fpage>291</fpage>
			  <lpage>300</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1108/14684521111128050">https://doi.org/10.1108/14684521111128050</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT84">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Torres-Salinas</surname>
					  <given-names>D.</given-names>	  
				  </name>
				  <name>
					  <surname>Ruiz-P&#x00E9;rez</surname>
					  <given-names>R.</given-names>	  
				  </name>
				  <name>
					  <surname>Delgado-L&#x00F3;pez-C&#x00F3;zar</surname>
					  <given-names>E.</given-names>	  
				  </name>
			  </person-group>
			  <year>2009</year>
			  <article-title>Google Scholar como herramienta para la evaluaci&#x00F3;n cient&#x00ED;fica</article-title>
			  <source>El profesional de la informaci&#x00F3;n</source>
			  <volume>18</volume>
			  <issue>5</issue>
			  <fpage>501</fpage>
			  <lpage>510</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3145/epi.2009.sep.03">https://doi.org/10.3145/epi.2009.sep.03</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT85">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Vanclay</surname>
					  <given-names>J.K.</given-names>	  
				  </name>
			  </person-group>
			  <year>2012</year>
			  <article-title>Impact factor: outdated artefact or stepping-stone to journal certification?</article-title>
			  <source>Scientometrics</source>
			  <volume>92</volume>
			  <issue>2</issue>
			  <fpage>211</fpage>
			  <lpage>238</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-011-0561-0">https://doi.org/10.1007/s11192-011-0561-0</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT86"> 
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Vaughan</surname>
					  <given-names>L.</given-names>	  
				  </name>
				  <name>
					  <surname>Shaw</surname>
					  <given-names>D.</given-names>	  
				  </name>
			  </person-group>
			  <year>2008</year>
			  <article-title>A New Look at Evidence of Scholarly Citations in Citation Indexes and From Web Sources</article-title>
			  <source>Scientometrics</source>
			  <volume>74</volume>
			  <issue>2</issue>
			  <fpage>317</fpage>
			  <lpage>330</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1007/s11192-008-0220-2">https://doi.org/10.1007/s11192-008-0220-2</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT87">
			<element-citation publication-type="patent">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Verstak</surname>
					  <given-names>A.</given-names>	  
				  </name>
				  <name>
					  <surname>Acharya</surname>
					  <given-names>A.</given-names>	  
				  </name>
			  </person-group>
			  <year>2013</year>
			  <article-title>Identifying multiple versions of documents</article-title>
			  <source>US Patents</source>
			  <patent country="US">US8589784 B1</patent>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://www.google.com/patents/US8589784">https://www.google.com/patents/US8589784</ext-link></comment>
			</element-citation>
			</ref>
	
			<ref id="CIT88">
			<element-citation publication-type="webpage">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Vine</surname>
					  <given-names>R.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Google Scholar is a full year late indexing Pubmed content</article-title>
			  <source>SiteLines: ideas about searching</source>
			  <comment>Available at: <ext-link ext-link-type="uri" xlink:href="http://web.archive.org/web/20060716085124/http://www.workingfaster.com/sitelines/archives/2005_02.html">http://web.archive.org/web/20060716085124/http://www.workingfaster.com/sitelines/archives/2005_02.html</ext-link></comment>
			</element-citation>
			</ref>
		
			<ref id="CIT89">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Walters</surname>
					  <given-names>W.H.</given-names>	  
				  </name>
			  </person-group>
			  <year>2007</year>
			  <article-title>Google Scholar coverage of a multidisciplinary field</article-title>
			  <source>Information Processing &amp; Management</source>
			  <volume>43</volume>
			  <issue>4</issue>
			  <fpage>1121</fpage>
			  <lpage>1132</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1016/j.ipm.2006.08.006">https://doi.org/10.1016/j.ipm.2006.08.006</ext-link></comment>
			</element-citation>
			</ref>

			<ref id="CIT90">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>White</surname>
					  <given-names>B.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006</year>
			  <article-title>Examining the claims of Google Scholar as a serious information source</article-title>
			  <source>New Zealand Library &amp; Information Management Journal</source>
			  <volume>50</volume>
			  <issue>1</issue>
			  <fpage>11</fpage>
			  <lpage>24</lpage>
			</element-citation>
			</ref>
			
			<ref id="CIT91">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Wleklinski</surname>
					  <given-names>J.M.</given-names>	  
				  </name>
			  </person-group>
			  <year>2005</year>
			  <article-title>Studying Google Scholar: wall to wall coverage?</article-title>
			  <source>Online</source>
			  <volume>29</volume>
			  <issue>3</issue>
			  <fpage>22</fpage>
			  <lpage>26</lpage>
			</element-citation>
			</ref>
		
			<ref id="CIT92">
			<element-citation publication-type="journal">
			  <person-group person-group-type="author">
				  <name>
					  <surname>Yang</surname>
					  <given-names>K.</given-names>	  
				  </name>
				  <name>
					  <surname>Meho</surname>
					  <given-names>L.I.</given-names>	  
				  </name>
			  </person-group>
			  <year>2006</year>
			  <article-title>Citation analysis: a comparison of Google Scholar, Scopus, and Web of Science</article-title>
			  <source>Proceedings of the American Society for information science and technology</source>
			  <volume>43</volume>
			  <issue>1</issue>
			  <fpage>1</fpage>
			  <lpage>15</lpage>
			  <comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/meet.14504301185">https://doi.org/10.1002/meet.14504301185</ext-link></comment>
			</element-citation>
			</ref>

		</ref-list>


		
		<app-group>
			<app>
				<title>APPENDIX</title>
				
					<fig id="A1">
						<label>APPENDIX I</label>
						<caption>
							<title>P&#x00E9;ter Jacs&#x00F3;’s work on Google Scholar</title>
						</caption>
						<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/A1.jpg"/>
					</fig>
				
					<fig id="A2">
						<label>APPENDIX II</label>
						<caption>
							<title>Compilation of studies that directly or indirectly address errors in Google Scholar</title>
						</caption>
						<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="../images/A2.jpg"/>
					</fig>
			</app>
		</app-group>
			
			
		
	</back>
</article>
