<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="methods-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.158264.2</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Method Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Using text-mining to measure the scientific impact and legacy of ELIXIR, a distributed research infrastructure for life science data</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 2; peer review: 1 approved, 1 approved with reservations]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>De Leo</surname>
                        <given-names>Francesca</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Funding Acquisition</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-0421-7699</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Balsyte</surname>
                        <given-names>Erika</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Petryszak</surname>
                        <given-names>Robert</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>D&#x2019;Ambrosio</surname>
                        <given-names>Marilena</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-7939-0504</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Bruno</surname>
                        <given-names>Chiara</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Cook</surname>
                        <given-names>Martin</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Mi&#x010d;eti&#x0107;</surname>
                        <given-names>Ivan</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-1691-8425</uri>
                    <xref ref-type="aff" rid="a4">4</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Martin</surname>
                        <given-names>Corinne S.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-5428-2766</uri>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>CNR-IBIOM, Istituto di Biomembrane Bioenergetica e Biotecnologie Molecolari Consiglio Nazionale delle Ricerche, Bari, Italy, 70126, Italy</aff>
                <aff id="a2">
                    <label>2</label>ELIXIR Hub, Wellcome Genome Campus, Hinxton, England, CB10 1SD, UK</aff>
                <aff id="a3">
                    <label>3</label>Datasome, Cambridge, UK</aff>
                <aff id="a4">
                    <label>4</label>Universita degli Studi di Padova Dipartimento di Scienze Biomediche, Padova, I-35131, Italy</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:francesca.deleo@cnr.it">francesca.deleo@cnr.it</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>3</day>
                <month>4</month>
                <year>2025</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2024</year>
            </pub-date>
            <volume>13</volume>
            <elocation-id>ELIXIR-1547</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>27</day>
                    <month>3</month>
                    <year>2025</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 De Leo F et al.</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/13-1547/pdf"/>
            <abstract>
                <sec>
                    <title>Background</title>
                    <p>ELIXIR is a pan-European public-funded research infrastructure dedicated to life science data. As such, it must demonstrate public value to its funders and stakeholders. We present methods to inventory research publications linked to ELIXIR that have received funding and support, as well as related citation metrics, used as performance metrics for these audiences.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>To overcome challenges inherent in ELIXIR&#x2019;s distributed structure, and the fact that those publishing ELIXIR-supported work are typically working part-time on ELIXIR matters, a semi-automated approach, consisting of text-mining followed by manual curation, is presented. A country-level case study (ELIXIR Italy) refines and expands the methods, notably by introducing more granularity in the curation process (e.g. considering all national-level grants, examining affiliations to report publication per institute) and by additionally looking at the scientific impact of the resources developed and operated by the Italian Node of ELIXIR.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>Overall, the methods described in this article have shown to: (1) be repeatable with acceptable levels of accuracy and consistency (notably across curators); (2) require reasonable effort in terms of curation of monthly &#x2018;harvests&#x2019; of publications (obtained by text-mining); and (3) to be well-adapted to ELIXIR&#x2019;s distributed nature.</p>
                </sec>
                <sec>
                    <title>Conclusions</title>
                    <p>Concrete examples are provided of downstream uses of the inventoried publications and their citations, both for ELIXIR as a whole and for the Italian case study. Limitations of the methods are discussed, particularly the challenges associated with using an &#x2018;Open literature&#x2019; database (Europe PMC) for the text-mining, and the constraints related to curation capacity. The methods, along with the valuable lessons learned during their development, are sufficiently generic and pragmatic enough to be readily adapted by other similar research infrastructures.</p>
                </sec>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>KPI</kwd>
                <kwd>metric</kwd>
                <kwd>funder</kwd>
                <kwd>literature</kwd>
                <kwd>bioinformatics</kwd>
                <kwd>database</kwd>
                <kwd>resource</kwd>
                <kwd>performance</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source>Italian Ministry for Universities and Research (National Recovery and Resilience Plan M4C2)</funding-source>
                    <award-id>IR0000010</award-id>
                </award-group>
                <award-group id="fund-2">
                    <funding-source>European Union (Horizon Programmes)</funding-source>
                    <award-id>871075</award-id>
                    <award-id>777563</award-id>
                    <award-id>101058728</award-id>
                </award-group>
                <award-group id="fund-3">
                    <funding-source>ELIXIR, the research infrastructure for life science data</funding-source>
                </award-group>
                <funding-statement>Italian Ministry for Universities and Research (MUR; National Recovery and Resilience Plan PNRR M4C2): ELIXIRxNextGenIT (IR0000010); ELIXIR, the research infrastructure for life science data: ELIXIR Strategic Implementation Study &#x201c;Impact evaluation at Node-level - getting it done&#x201d;, ELIXIR Commissioned Service &#x201c;People Pulse&#x201d;; European Union (Horizon Programmes): ELIXIR-CONVERGE (grant agreement number 871075), RI-PATHS (grant agreement number 777563), PathOS (grant agreement number 101058728).</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
        <notes>
            <sec sec-type="version-changes">
                <label>Revised</label>
                <title>Amendments from Version 1</title>
                <p>We have addressed the major and minor concerns of the reviewer 2 as follows: Major Concerns: Concrete Examples of EuropePMC Queries Done: We added&#x00a0;Table 2, which provides sample URLs and code snippets demonstrating how the EuropePMC API was queried and how the retrieved data were processed. This addition aims to strengthen reproducibility. Manual Whitelisting of ELIXIR-Supported Articles Done: We added&#x00a0;Table 6, clarifying why some known ELIXIR-supported articles were manually whitelisted. Specifically, we explain the limitations of the automated text-mining and how certain acknowledgments or metadata issues caused these articles to be omitted from the initial searches. Minor Concerns: Discrepancy in Citation Counts (Figure 2 vs. Text) Done: We resolved the discrepancy by ensuring that the citation count in Figure 2 (approximately 6,721) is consistent with the 5,000 mentioned in the text. The updated text and figure now align. Differences in Publication Counts (Figure 3 vs. Text) Done: We clarified that Figure 3 double-counts papers co-authored by multiple institutes, explaining why the summed total (772) differs from the 408 unique publications reported in the text. These revisions address the concerns raised by the reviewer 2 and improve the clarity and reproducibility of our manuscript.</p>
            </sec>
        </notes>
    </front>
    <body>
        <sec id="sec5" sec-type="intro">
            <title>Introduction</title>
            <p>

                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us">ELIXIR</ext-link> is a pan-European distributed research infrastructure dedicated to life science data, formally founded in 2013 and currently implementing its third five-year scientific programme (
                <xref ref-type="bibr" rid="ref5">ELIXIR, 2023</xref>). In 2016, it was recognised by the European Strategy Forum for Research Infrastructures (ESFRI), a forum for government officials focused on research infrastructure, as a &#x2018;Landmark&#x2019; (
                <xref ref-type="bibr" rid="ref7">ESFRI, 2016</xref>). Landmarks are reference research infrastructures considered pillars in the European Research Area landscape, offering not only services/resources to academic research, but also supporting development and innovation. ELIXIR currently has 21 member countries, three observer countries, plus one intergovernmental organisation, the European Molecular Biology Laboratory (EMBL), which has its own country membership (overlapping in parts with that of ELIXIR).</p>
            <p>Each ELIXIR member forms a country &#x2018;Node&#x2019;, with the European Bioinformatics Institute (EMBL-EBI) serving as the &#x2018;European&#x2019; Node of ELIXIR. Having the Open Science principle at its heart, ELIXIR comprises over 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/who-we-are/nodes">240 research institutions across Europe</ext-link>, and coordinates the 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/services">provision</ext-link>, development and 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/what-we-offer/portals">discoverability</ext-link> of more than 500 bioinformatics resources covering databases, tools, software, interoperability standards, training, and cloud computing. These resources are financed through public funds (
                <xref ref-type="bibr" rid="ref18">Smith et al., 2020</xref>) and are typically free at the point of use, for academic and industry users alike, who can hence focus on their research rather than on the development and operation of the underlying infrastructure and its resources. ELIXIR also works to streamline and integrate national-level bioinformatics infrastructures, to strengthen national training programmes, and to bring together bioinformatics experts to create 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/what-we-offer/guidelines">guidelines and best practices</ext-link>, towards ensuring the long-term sustainability of resources and infrastructure.</p>
            <p>ELIXIR must continually demonstrate public value to its national and international funders and stakeholders more broadly to ensure their ongoing support and hence the continuity of infrastructure and resource development and operation (
                <xref ref-type="bibr" rid="ref12">Martin et al., 2021</xref>). Inventories of research publications arising from the use of the infrastructure (by others than those developing/operating it) are a common source of performance metrics requested by funders and related stakeholders (
                <xref ref-type="bibr" rid="ref6">ESFRI, 2019</xref>, 
                <xref ref-type="bibr" rid="ref15">OECD, 2019</xref>, 
                <xref ref-type="bibr" rid="ref8">
European Commission, 2020</xref>). A subset of ELIXIR databases, the ELIXIR Core Data Resources (
                <xref ref-type="bibr" rid="ref4">Durinx et al., 2017</xref>), are indeed widely cited and acknowledged in thousands of research publications by life scientists across the globe (
                <xref ref-type="bibr" rid="ref3">Drysdale et al., 2020</xref>).</p>
            <p>Around 700 bioinformaticians and related professionals across Europe form the developers and operators of the ELIXIR infrastructure and resources, and are typically working part-time on ELIXIR matters, often alongside more conventional research activities. These professionals usually have research profiles and, through their daily work on ELIXIR matters, actively contribute to the generation and dissemination of new technical and scientific knowledge linked to the development and operation of the ELIXIR infrastructure and its resources. These efforts are enabled (in part or fully) by a 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/how-funded">range of funding sources</ext-link>, such as ELIXIR&#x2019;s 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/internal-projects">internally-funded projects</ext-link> (also referred to as &#x2018;Commissioned Services&#x2019;), national-level financing, and 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/how-funded/eu-projects">grant funding</ext-link> from the European Union and other international funders awarded in the name of ELIXIR. In line with the Open Science principles, this new knowledge is shared openly via ELIXIR-supported research publications (peer-reviewed, preprints), which collectively represent an additional source of performance metrics of ELIXIR&#x2019;s scientific legacy as a research infrastructure.</p>
            <p>The purpose of this article is to present the methods that have been developed and implemented to inventory research publications that have received funding and support linked to ELIXIR, as well as related citation metrics. The methods are presented for ELIXIR as a whole (lightweight, considering all Nodes) and for a particular country Node, ELIXIR Italy, itself also of 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-italy.org/about/members/">distributed nature</ext-link>. For the latter, the methods were refined thanks to greater curation capacity at the level of the Node, and also expanded to include the inventorying of research publications citing resources developed and operated by the Node. This exercise is very informative of the Node&#x2019;s scientific impact and legacy, yet it would not easily scale for the whole distributed infrastructure (in terms of curation capacity at the ELIXIR Hub, the infrastructure&#x2019;s coordinating secretariat) since the infrastructure operates hundreds of resources under the ELIXIR umbrella.</p>
            <p>A semi-automated approach, consisting of text-mining followed by manual curation, is presented, with the Italian case study going further so as to better reflect the needs and expectations of national-level funders and other (internal and external) stakeholders of the Node. Of note, the guiding principle in developing these methods was that they would not require extensive technical nor programming knowledge to be applied once in place - as a result, the methods do not involve any modelling (e.g. with training and test sets), nor do they claim to be rigorously accurate. It is hoped that the steps taken, and lessons learned (both ELIXIR-wide and at the scale of a country Node), in arriving at operational methods in the context of distributed organisational settings will be useful to other such research infrastructures and organisations, in the life sciences and other disciplines.</p>
        </sec>
        <sec id="sec6" sec-type="methods">
            <title>Methods</title>
            <sec id="sec7">
                <title>Lightweight methods for the ELIXIR infrastructure as a whole (all Nodes)</title>
                <p>

                    <bold>Main challenges</bold>
                </p>
                <p>Two intrinsic challenges that the lightweight methods needed to overcome were (1) that those publishing ELIXIR-supported work are typically working part-time on ELIXIR matters, and (2) the scale of ELIXIR&#x2019;s &#x201c;people infrastructure&#x201d; (more than 700 specialists across Europe, showing a level of staff turnover). The latter itself represented a significant barrier to manual reporting of publications. As for the former, traditional bibliometrics/scientometrics approaches centred on researchers&#x2019; unique identification numbers (e.g., ORCID, ResearcherID/Publons), and/or institutional affiliations, were deemed inadequate for identifying research works (funded and/or) supported by ELIXIR, as these approaches would result in significant amounts of &#x2018;false positives&#x2019;, i.e. publications not supported by ELIXIR. To overcome these two challenges, the lightweight methods were designed to (1) detect, through text-mining within an Open research literature database (
                    <ext-link ext-link-type="uri" xlink:href="https://europepmc.org/">EuropePMC</ext-link>, 
                    <xref ref-type="bibr" rid="ref17">Rosonovski et al., 2024</xref>), publications (peer-reviewed and preprints) in which there were acknowledgments of the support and/or funding received from ELIXIR, (2) followed by manual curation for increased accuracy.</p>
                <p>

                    <bold>Sources of ELIXIR support</bold>
                </p>
                <p>For the ELIXIR infrastructure as a whole (all Nodes), two main streams of funding and/or support were considered: (1) ELIXIR&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/internal-projects">internally-funded projects</ext-link>, i.e. Commissioned Services comprising Implementation Studies, Staff Exchange, Knowledge Exchanges and Industry days, and Travel Grants, where funding eligibility is restricted to institutes part of the ELIXIR membership, and (2) 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/how-funded/eu-projects">grant funding</ext-link> from international funders such as the European Union (notably under the Research Infrastructures Work Programmes), in which several ELIXIR institutes are beneficiaries and the purpose of the grant is to develop and/or operate the ELIXIR infrastructure.</p>
                <p>

                    <bold>Searching for relevant publications using text-mining
</bold>
                </p>
                <p>EuropePMC&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://europepmc.org/RestfulWebService">Application Programming Interface</ext-link> (API) was used to search for relevant publications (technical documentation), as well as their citations in the Open literature (technical documentation), considering all years for which ELIXIR existed, even as a concept (
                    <italic toggle="yes">circa</italic> 2011), with a cut-off date of December 2023 (for the purpose of this article). Search configuration parameters (
                    <xref ref-type="table" rid="T1">
Table 1</xref>), i.e. &#x2018;search terms&#x2019; for short, comprised unique grant identification numbers and names, names and short codes of countries that are members of ELIXIR (e.g. ELIXIR Norway, ELIXIR NO), as well as &#x201c;boiler-plate&#x201d; text strings relating to ELIXIR support and/or funding including for &#x2018;signature&#x2019; events (e.g. the ELIXIR-convened Biohackathon Europe) and technical workshops/meetings. For use in EuropePMC&#x2019;s API, the search terms (query parameters) were first URL encoded using the online utility 
                    <ext-link ext-link-type="uri" xlink:href="https://www.url-encode-decode.com/">URL Encode/Decode</ext-link>, provided free, courtesy of 
                    <ext-link ext-link-type="uri" xlink:href="https://www.danstools.com/">Dan&#x2019;s Tools</ext-link>: for example, the EU funded project ELIXIR-CONVERGE would be encoded as &#x201c;ELIXIR%2DCONVERGE&#x201d;. Of note, EuropePMC is case insensitive, meaning that it is not necessary to provide search terms in both lower/upper cases. For the lightweight methods, acknowledgement of the use of the infrastructure and its resources was deemed beyond scope due to the mismatch between curation capacity at the ELIXIR Hub and the several hundreds of resources operated under the ELIXIR umbrella.</p>
                <table-wrap id="T1" orientation="portrait" position="float">
                    <label>
Table 1. </label>
                    <caption>
                        <title>Search configuration for lightweight methods across the ELIXIR infrastructure as a whole.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Type</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Search terms (examples)</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Unique grant identification numbers</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">730941; 654248; 825575; 676559; 824087; 739563; etc</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Grant names</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR-EXCELERATE; ELIXIR-CONVERGE; EOSC life; FAIRplus; etc</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Names and short codes of countries that are members of ELIXIR</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR BE; ELIXIR Belgium; Belgian ELIXIR Node; ELIXIR GR; ELIXIR Greece; Greek ELIXIR Node; Hellenic ELIXIR Node; EMBL-EBI; etc</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">&#x201c;Boiler-plate&#x201d; text strings</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">This work was funded by ELIXIR, the research infrastructure for life science data; European life sciences Infrastructure; ELIXIR Implementation Study; ELIXIR Implementation Studies; ELIXIR Commissioned Service; ELIXIR Travel Grant; ELIXIR Staff Exchange; ELIXIR BioHackathon; Biohackathon Europe</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Generic search terms</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR Europe; ELIXIR Node; funded by ELIXIR; funded partially by ELIXIR; supported by ELIXIR; ELIXIR Core funding; funding from ELIXIR</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>An initial set of search terms were entered in a Google Sheet, and retrieved from there via a specific 
                    <ext-link ext-link-type="uri" xlink:href="https://developers.google.com/sheets/api/reference/rest">Google Sheets API</ext-link>. This allowed for the subsequent dynamic configuration of the search queries when new grants were awarded to ELIXIR. The Google Sheet interacted with the EuropePMC API based on the retrieved search configuration, and the text-mining process resulted in the generation of tab-delimited text files listing potentially relevant publications comprising a mix of ELIXIR-related works (&#x2018;true positives&#x2019;) and false positives. A complete list of API examples for the data retrieval in EuropePMC is illustrated in 
                    <xref ref-type="table" rid="T2">Table 2</xref>.</p>
                <table-wrap id="T2" orientation="portrait" position="float">
                    <label>
Table 2. </label>
                    <caption>
                        <title>API call examples for data retrieval from EuropePMC.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">A search for grant id: 730941</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <ext-link ext-link-type="uri" xlink:href="https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=GRANT_ID:730941">https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=GRANT_ID:730941</ext-link> AND (FIRST_PDATE:[2007-01-01 TO 2025-02-27])&amp;resultType=core&amp;format=json&amp;pageSize=1000</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <ext-link ext-link-type="uri" xlink:href="https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=ACK_FUND:730941">https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=ACK_FUND:"730941"</ext-link> AND (FIRST_PDATE:[2007-01-01 TO 2025-02-27]) AND NOT (Elixir Pharmaceuticals)&amp;resultType=core&amp;format=json&amp;pageSize=1000</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Search for a general search token: FAIRplus</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <ext-link ext-link-type="uri" xlink:href="https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=FAIRplus">https://www.ebi.ac.uk/europepmc/webservices/rest/search?query="FAIRplus"</ext-link> AND (FIRST_PDATE:[2007-01-01 TO 2025-02-27])&amp;resultType=core&amp;format=json&amp;pageSize=1000</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Search for citations of PMID: 30254736</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <ext-link ext-link-type="uri" xlink:href="https://www.ebi.ac.uk/europepmc/webservices/rest/MED/34791415/citations?page=1&amp;pageSize=1000&amp;format=json">https://www.ebi.ac.uk/europepmc/webservices/rest/MED/34791415/citations?page=1&amp;pageSize=1000&amp;format=json</ext-link>
</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>

                    <bold>Manual curation and search optimisation</bold>
                </p>
                <p>Manual identification of false positives was carried out using the tab-delimited text files, one column of which collated the triggers relevant to each returned publication. Triggers represented the search terms that had been detected in the publications and were found to guide curation very effectively. False positives were blacklisted for future searches. To ensure consistency, reproducibility and the lowest subjectivity possible in curation decisions, curation efforts were carried out by a small team of two ELIXIR Hub staff who kept a record of difficult and/or unclear cases, and of the decisions taken. They were supported on an ad-hoc basis by additional ELIXIR Hub staff who had more extensive knowledge and understanding of ELIXIR&#x2019;s activities in certain thematic and technical areas.</p>
                <p>During the initial development of the methods, iterative searches and manual curation rounds were undertaken to test and refine the set of search terms, and to identify which sections of EuropePMC entries (for each publication) were the most informative to target by text-mining - these were found to be the title, first author, funding statement, and acknowledgments. The initial text-mining runs naturally returned large backlogs of potentially relevant publications since they covered the years 2011 to 2019: although this made the curation effort significant at the time, it also provided a rich list of results to optimise the searches, notably to identify which sections (
                    <xref ref-type="table" rid="T3">
Table 3</xref>) of the publications ought to be extracted to the tab-delimited text files used during manual curation and any downstream visualisations.</p>
                <table-wrap id="T3" orientation="portrait" position="float">
                    <label>
Table 3. </label>
                    <caption>
                        <title>Extracted publication sections from EuropePMC, used for manual curation and downstream visualisations.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Sections of the publications</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Harvest month</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Triggers identified</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Unique EuropePMC identification number</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Digital Object Identifier (DOI)</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Title</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Journal name</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Publication year</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">First author name</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">First author affiliation</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Last author name</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Last author affiliation</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Funding statement</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Acknowledgements
</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>A set of known ELIXIR-supported publications was useful for fine-tuning the approach, as they would be expected to be returned by the searches. If this was not the case, underlying reasons would be investigated and, where possible, solutions found - if no solution was found, these publications were added (via their unique EuropePMC identification number) to a whitelist that would be pulled to the tab-delimited text file, regardless. Later on, once the methods were operational (
                    <italic toggle="yes">circa</italic> early 2020), the text-mining &#x201c;harvests&#x201d; (i.e. searches) followed by curation ended up being carried out on a monthly basis, to identify recently published and/or recently indexed publications, based on the latest set of search terms.</p>
                <p>Search terms returning very high numbers of false positives for very few true positives were gradually excluded from searches. This was for instance the case of &#x201c;ELIXIR&#x201d; as a standalone term (misunderstood for the word &#x201c;elixir&#x201d;), &#x201c;implementation study&#x201d; (rather than the more precise &#x201c;ELIXIR implementation study&#x201d;), and the project name &#x201c;BY-COVID&#x201d; (incorrectly read as the very common text string &#x201c;[infected] 
                    <bold>by COVID-19</bold>&#x201d;). This was to strike a balance between accuracy (i.e. not missing any relevant publication) and overwhelming curators. Rather, it was deemed more useful to arrive at manageable monthly text-mining harvests and curation workloads moving forwards (approximately 3 to 4 hours per monthly harvest), since the intention was to arrive at operational performance metrics that could be monitored in the long-term, rather than a very accurate one-off exercise.</p>
            </sec>
            <sec id="sec8">
                <title>Case study: refined and expanded methods focusing on a single Node (ELIXIR Italy)</title>
                <p>Unless otherwise specified, the methods for the Italian case study are identical to the lightweight one described above (for ELIXIR as a whole).</p>
                <p>

                    <bold>Sources of ELIXIR Italy support</bold>
                </p>
                <p>Building on the experience of the ELIXIR Hub effort, the Italian case study began at the end of 2022 and was focused on the period January 2015 (the year when Italy became an ELIXIR member country) to December 2023 (cut-off date for the purpose of this article). The main three sources of funding and/or support considered in the Italian case study were (1) those ELIXIR internally funded projects in which one or more of the institutes of the Italian Node were involved, (2) ditto for grant funding from international funders, and (3) national-level grants awarded to the Node to develop and/or operate its infrastructure and resources.</p>
                <p>

                    <bold>Searching for relevant publications using text-mining
</bold>
                </p>
                <p>For the Italian case study, the &#x2018;ELIXIR as a whole&#x2019; set of search terms was refined to remove terms not relevant to the Node, e.g. if the Italian Node was not a beneficiary of a given grant. Additional search terms were introduced (e.g. national-level grants) along with other terms (e.g. Italian Node of ELIXIR, often used instead of ELIXIR-IT or ELIXIR IIB) that were known to be mentioned in publications acknowledging support and/or funding by ELIXIR Italy (
                    <xref ref-type="table" rid="T4">
Table 4</xref>).</p>
                <table-wrap id="T4" orientation="portrait" position="float">
                    <label>
Table 4. </label>
                    <caption>
                        <title>Search configuration for methods focused on a single country Node (Italy).</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Type</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Search terms (all)</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Unique grant identification numbers</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">951724; 101046203; PIR01_00017; 871075; IR0000010; 824087; 857650; 825575; 101057388; 676559; 101003551; 101017549; 653549; 956137; 862658; 101016167; 778247; 823886; 654008; 634486; 952334; 101081813</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Grant names</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">BEYOND 1M GENOME; BY-COVID; CnrBiomics; ELIXIR-Converge; ELIXIRNextGenIT; EOSC-Life; EOSC-Pillar; European Join Programme On Rare Diseases; EuroScienceGateway; EXCELERATE; Exscalate4Cov; Genomed4All; INDIGO DataCloud; IDPfun; NewTechAqua</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Generic search terms</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR IIB; ELIXIR-IIB; ELIXIR ITA; elixir iib; elixir-iib; Italian Node of ELIXIR; ELIXIR-IT</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>The major expansion of the methods followed 
                    <xref ref-type="bibr" rid="ref3">Drysdale et al. (2020)</xref> and their focus on citations of &#x2018;key articles&#x2019; describing the Node&#x2019;s resources. This additional search effort was approached by using the Digital Object Identifier (DOI) of these &#x2018;key articles&#x2019; to collate citation data and use this as proxy for the scientific impact of the Node&#x2019;s resources. For example, the resource PatSearch was first described in 
                    <xref ref-type="bibr" rid="ref16">Pesole et al. (2000)</xref> and an improved version of it was described in 
                    <xref ref-type="bibr" rid="ref9">Grillo et al. (2003)</xref> - these are considered the resource&#x2019;s &#x2018;key articles&#x2019;. The list of ELIXIR Italy resources was based on the 2023 version of the Node&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/services/list">Service Delivery Plan</ext-link> under the ELIXIR umbrella, and the DOIs were sourced from the 
                    <ext-link ext-link-type="uri" xlink:href="https://bio.tools">bio.tools registry</ext-link> (
                    <xref ref-type="bibr" rid="ref11">Ison et al., 2019</xref>). For the 65 resources developed and operated by ELIXIR Italy in 2023, a total of 124 DOIs were hence collated, representing the &#x2018;key articles&#x2019; describing initial and improved versions of these resources.</p>
                <p>

                    <bold>Manual curation and search optimisation</bold>
                </p>
                <p>Curation in the context of the case study was a very similar process to that described above but carried out by ELIXIR Italy staff with knowledge of the Node&#x2019;s activities. Author affiliations were additionally scrutinised and encoded to obtain a more granular view of dissemination efforts and scientific impact at the level of the Node&#x2019;s institutes (30 in total at the time of writing). Sources of false positives were like that described above, e.g. project names such as &#x201c;ORCHESTRA&#x201d; (understood as the word &#x201c;orchestra&#x201d; or other projects called as such). As above, a balance was struck between accuracy and curation capacity by excluding problematic search terms (those returning high levels of false positives).</p>
            </sec>
        </sec>
        <sec id="sec9" sec-type="results">
            <title>Results</title>
            <sec id="sec10">
                <title>ELIXIR infrastructure as a whole (all Nodes)</title>
                <p>For the period 2011 to 2023, 972 publications supported by ELIXIR (as a whole) were identified, and these were collectively cited over 31,000 times (
                    <xref ref-type="fig" rid="f1">
Figure 1</xref>). The curated inventory of publications and their citations in the Open literature were used to create 
                    <ext-link ext-link-type="uri" xlink:href="https://public.tableau.com/app/profile/elixir/viz/ELIXIRArticlesinEuropePMC-SummaryNEW/ElixirArticlesinEPMCSummary">visualisations</ext-link> in Tableau software, which were themselves featured on 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/impact">ELIXIR&#x2019;s impact dashboard</ext-link>, among other indicators relating to ELIXIR. On this dashboard, the page showing ELIXIR&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/impact/publications">scientific legacy</ext-link> as a research infrastructure received nearly 600 unique visitors from over 40 countries in just 12 months (December 2022 to November 2023).</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>
Figure 1. </label>
                    <caption>
                        <title>Publications and citations supported by ELIXIR (2011&#x2013;2023) in Open literature (EuropePMC).</title>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/178964/5ddf1f7e-1055-4979-b14a-c7e212f77eb6_figure1.gif"/>
                </fig>
            </sec>
            <sec id="sec11">
                <title>Case study: ELIXIR Italy</title>
                <p>For the period 2015 to 2023, 408 publications supported by ELIXIR Italy were identified, which were collectively cited almost 5,000 times (
                    <xref ref-type="fig" rid="f2">
Figure 2</xref>). The distribution of publications across Node institutes (
                    <xref ref-type="fig" rid="f3">
Figure 3</xref>) is double-counted due to papers co-authored by multiple institutes; furthermore it highlights the disproportionate contribution of the National Research Council (NRC), though unsurprising given its role as the coordinating institute of ELIXIR Italy. Associated visualisations can be accessed on 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-italy.org/impact-publications/?">ELIXIR Italy&#x2019;s impact dashboard</ext-link> which, for a 24 month period (January 2022 to December 2023), received over 5,000 unique visitors from 10 countries. In terms of the impact of resources developed and operated by ELIXIR Italy (
                    <xref ref-type="table" rid="T5">
Table 5</xref>), citations of their &#x2018;key articles&#x2019; amounted to 8,700, across the five 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/platforms">ELIXIR Platforms</ext-link>, which are the technical domains of implementation of the infrastructure.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>
Figure 2. </label>
                    <caption>
                        <title>Publications and citations supported by ELIXIR Italy (2011&#x2013;2023) in Open literature (EuropePMC).</title>
                    </caption>
                    <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/178964/5ddf1f7e-1055-4979-b14a-c7e212f77eb6_figure2.gif"/>
                </fig>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>
Figure 3. </label>
                    <caption>
                        <title>Distribution of ELIXIR Italy publications (double counted) across its Node institutes.</title>
                        <p>Acronyms: see 
                            <ext-link ext-link-type="uri" xlink:href="https://elixir-italy.org/about/members/">https://elixir-italy.org/about/members/</ext-link>.</p>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/178964/5ddf1f7e-1055-4979-b14a-c7e212f77eb6_figure3.gif"/>
                </fig>
                <table-wrap id="T5" orientation="portrait" position="float">
                    <label>
Table 5. </label>
                    <caption>
                        <title>Citations of ELIXIR Italy's resources via DOIs of their &#x2018;key (descriptive) articles&#x2019;.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Year</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2015</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2016</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2017</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2018</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2019</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2020</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2021</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">2022</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">
2023</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Tools Platform</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">327</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">424</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">476</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">450</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">456</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">571</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">713</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">805</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">703</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Data Platform</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">304</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">311</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">289</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">342</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">339</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">398</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">557</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">570</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">461</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Compute Platform</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">14</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">12</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">10</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">4</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">15</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">15</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">26</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">19</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">19</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Interoperability Platform</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">0</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">0</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">0</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">1</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">2</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">0</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">6</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">32</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">29</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Total citations per year</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">645</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">747</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">775</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">797</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">812</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">984</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">1,302</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">1,426</td>
                                <td align="left" colspan="1" rowspan="1" valign="middle">1,212</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="middle">Total citations</td>
                                <td align="left" colspan="9" rowspan="1" valign="middle">8,700</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
        </sec>
        <sec id="sec12" sec-type="discussion">
            <title>Discussion</title>
            <p>In almost four years of implementation, the methods have been found to be adequately performant at identifying publications supported by ELIXIR, if the relevant triggers were present (and correctly spelled) in the publications. Since the inception (in 2020) of a dedicated &#x201c;How to acknowledge ELIXIR funding and support&#x201d; 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/publications/how-acknowledge">page</ext-link> on the ELIXIR website (with the analogous one on the 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-italy.org/impact-publications/">ELIXIR Italy site</ext-link>, bottom part), curators have noticed clear improvements in how ELIXIR&#x2019;s contribution is acknowledged.</p>
            <p>The upward trend in citation numbers for both the lightweight and case study methods suggested long-term scientific impact of these publications, a reminder that impact is slow to develop. It is not just citations that take time to appear: large-scale projects such as ELIXIR-EXCELERATE which involved 47 partners from 17 countries (
                <xref ref-type="bibr" rid="ref10">Harrow et al., 2021</xref>; &#x20ac;19 million, 2014-2019) were found to be still acknowledged in publications years after their completions, This is not solely due to delayed indexing but also to the enduring legacy of their support for research activities within teams connected to the project.</p>
            <p>Overall, the methods described in this article have shown to: (1) be repeatable with acceptable levels of accuracy and consistency (notably across curators); (2) require reasonable effort in terms of curation of monthly harvests (in contrast to running an ELIXIR wide manual reporting process); and (3) to be well-adapted to ELIXIR&#x2019;s distributed nature (including at Node-level in the Italian case study).</p>
            <p>While the text-mining component can be operated with minimal ELIXIR expertise, it is true that the curation component requires a deeper awareness and understanding of the organisation&#x2019;s activities. One example is when ELIXIR was involved in large &#x201c;cluster&#x201d; grants (e.g. 
                <ext-link ext-link-type="uri" xlink:href="https://www.eosc-life.eu/">EOSC-life
</ext-link>) in which many life science research infrastructures were also funded, meaning that not all publications acknowledging EOSC-life&#x2019;s grant would be relevant to ELIXIR, despite ELIXIR coordinating the project.</p>
            <p>The Italian case study highlighted the usefulness of national-level granularity in the search terms. Whilst it is true that the lightweight &#x2018;ELIXIR as a whole&#x2019; methods do include a few national-level grants in its search terms, this is far from being fully implemented. Their inclusion was exploratory at best and, based on this experience, there is insufficient appetite at the ELIXIR Hub to fully implement national-level search terms due to capacity constraints in terms of curation and limited knowledge of ELIXIR activities at Node level.</p>
            <sec id="sec13">
                <title>Limitations of the methods linked to using an &#x2018;Open literature&#x2019; database (EuropePMC)</title>
                <p>One main limitation of the methods is linked to EuropePMC being used as the central source of publication data - only the publications indexed in this literature database, focused on life sciences, can be returned by the searches. At the time of writing, specialised journals such as 
                    <ext-link ext-link-type="uri" xlink:href="https://datascience.codata.org/">Data Science Journal</ext-link> and 
                    <ext-link ext-link-type="uri" xlink:href="https://direct.mit.edu/dint">Data Intelligence</ext-link> were not yet indexed due to perceived low demand of these in the user base of EuropePMC. However, based on user feedback, EuropePMC started indexing 
                    <ext-link ext-link-type="uri" xlink:href="https://biohackrxiv.org/">BioHackrXiv</ext-link> in 2021, especially as it is the recommended preprint server for outcomes of the ELIXIR-convened 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/events/biohackathon-europe">Biohackathon Europe series</ext-link> (
                    <xref ref-type="bibr" rid="ref2">Castro et al., 2021</xref>).</p>
                <p>Although research funders are increasingly requesting that the work they fund is openly accessible, it was found that certain ELIXIR-relevant publications were behind paywalls. This meant that EuropePMC was not able to fully &#x201c;ingest&#x201d; the text of certain sections of the source text, e.g. funding statement, which made text-mining efforts fail, despite the publication having a presence in EuropePMC and the right trigger being present. This was manually solved on an ad-hoc basis by whitelisting these publications using their unique EuropePMC identification number. (
                    <xref ref-type="table" rid="T6">
Table 6</xref> lists such whitelisted publications examples) Additionally, this method can effectively identify ELIXIR-related publications that are non-compliant with open access policies and funder requirements.</p>
                <table-wrap id="T6" orientation="portrait" position="float">
                    <label>
Table 6. </label>
                    <caption>
                        <title>Examples of whitelisted ELIXIR-supported publications and reasons for being whitelisted thereof.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Article ID in EuropePMC (publication&#x2019;s DOI)</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Whitelisting reason</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">28713550 (
                                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.12688/f1000research.11751.1">10.12688/f1000research.11751.1</ext-link>) </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">uses &#x201c;ELIXIR Implementation Project&#x201d; (instead of "ELIXIR Implementation Study")</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top"/>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <ext-link ext-link-type="uri" xlink:href="https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=ACK_FUND:730941">https://www.ebi.ac.uk/europepmc/webservices/rest/search?query=ACK_FUND:"730941"</ext-link> AND (FIRST_PDATE:[2007-01-01 TO 2025-02-27]) AND NOT (Elixir Pharmaceuticals)&amp;resultType=core&amp;format=json&amp;pageSize=1000</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">28445123 (
                                    <ext-link ext-link-type="uri" xlink:href="https://elifesciences.org/articles/22175">https://elifesciences.org/articles/22175</ext-link>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">mis-spells grant name (ELIXIR-Excellerate instead of ELIXIR-EXCELERATE)</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">29036529 (
                                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1093/nar/gkx855">10.1093/nar/gkx855</ext-link>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">mis-spells grant unique ID (67559 instead of 676559)</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">29967506 (
                                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1038/s41592-018-0046-7">10.1038/s41592-018-0046-7</ext-link>)</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">uses very unique text to acknowledge ELIXIR, plus most of its text is not ingested by EuropePMC despite it being open access</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>Looking forward, EuropePMC continues to work closely with scientific publishers to agree and implement standards so that ingestion of information from the publishers&#x2019; sites to EuropePMC is more effective. This is an on-going and quite a considerable task, and additional sources of text-mining failures included conflicts in metadata, embargoed works in paywalled journals, as well as citations being limited to the Open literature, the latter leading to underestimated scientific impact.</p>
            </sec>
            <sec id="sec14">
                <title>Uses of the curated inventories of publications as source of performance metrics</title>
                <p>The intention behind this work was to arrive at operational performance metrics that could be easily monitored in the long-term, in contrast to a rigorous and hence heavy-duty process requiring significant resources, likely to be carried out once or twice at best. The curated inventories of publications, including their citations, have so far been used as input into 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/publications">ELIXIR&#x2019;s annual reports</ext-link>, ELIXIR newsletters and social media posts (under the heading &#x201c;Recommended reading&#x201d;), technical reporting to funders, as well as ELIXIR&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/news/ESFRImonitoring">monitoring report to ESFRI</ext-link> and a growing number of requests for information from national funders, such as Sweden (
                    <xref ref-type="bibr" rid="ref19">Swedish Research Council, 2021</xref>), Finland (
                    <xref ref-type="bibr" rid="ref1">Academy of Finland, 2023</xref>) and the Netherlands (
                    <xref ref-type="bibr" rid="ref14">NWO, 2023</xref>).</p>
                <p>Similar to ELIXIR, ELIXIR Italy has used the curated inventories of publications and their citations for a range of internal and external monitoring activities, as required by various stakeholders, for example periodic Node reviews and presentations for ELIXIR&#x2019;s 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/governance/board">Board of funders</ext-link>, 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/about-us/governance/sab">Scientific Advisory Board</ext-link> and 
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/industry/advisory-committee">Industry Advisory Committee</ext-link>. The information has also been used to report to ELIXIR Italy&#x2019;s own Scientific Advisory Board, as well as for the Node&#x2019;s general assembly and monthly newsletters. Finally, the information has been used to report to ELIXIR&#x2019;s Italy&#x2019;s main funder, the Italian Ministry for Universities and Research (MUR)), notably as part of 
                    <ext-link ext-link-type="uri" xlink:href="https://www.anvur.it/attivita/vqr/vqr-2020-2024/gev/interdisciplinare-infrastrutture-di-ricerca/">evaluation processes</ext-link> and of national-level grant funding for research infrastructures.</p>
            </sec>
        </sec>
        <sec id="sec15" sec-type="conclusions">
            <title>Conclusions</title>
            <p>As illustrated by the Italian case study, these methods represent the first step of potentially many exciting downstream analyses using the curated inventories as starting materials. Their citations would shed light on the impact of these works, through their use by others. Yet these inventories alone have proved to be useful already, in terms of communicating performance and impact of both ELIXIR activities (as a whole and for a country Node) and the use of a Node&#x2019;s resources. The Italian case study also demonstrated the value of knowledge sharing within an organisation, in the spirit of Open Science, with the country Node leveraging the experience of the ELIXIR Hub, building on and enhancing it.</p>
            <p>The methods&#x2019; main strength lies in its relative ease of implementation, especially in the context of a distributed life science research infrastructure staffed with highly qualified and research-active personnel: many will have the programming skills required to operationalise the methods, whilst no such technical skill is required for the curation part of the methods. If not, external assistance can be sought in the form of consulting, to get the approach off the ground. Another strength of the methods is its versatility as new funding streams become available and resources are further developed.</p>
            <p>The methods, along with the valuable lessons learned during their development, are generic and pragmatic enough to be readily adapted by other similar research infrastructures. This extends its potential application beyond life sciences to encompass physical sciences, social sciences, and the humanities.</p>
            <sec id="sec16">
                <title>Ethical considerations</title>
                <p>Ethical approval and consent were not required.</p>
            </sec>
        </sec>
    </body>
    <back>
        <sec id="sec20" sec-type="data-availability">
            <title>Data availability</title>
            <sec id="sec21">
                <title>Underlying data</title>
                <p>EuropePMC (
                    <xref ref-type="bibr" rid="ref17">Rosonovski et al., 2024</xref>; 
                    <ext-link ext-link-type="uri" xlink:href="https://europepmc.org/">https://europepmc.org/</ext-link>), an Open research literature database, was used as the source for the underlying data (publications in the life sciences) used in the methods described in the article.</p>
            </sec>
            <sec id="sec22">
                <title>Extended data</title>
                <p>The extended data created as a result of applying the methods are curated inventories of publications that have received funding and support from ELIXIR. They have been deposited in Zenodo (
                    <xref ref-type="bibr" rid="ref13">Martin et al., 2024</xref>; 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.14136249">https://doi.org/10.5281/zenodo.14136249</ext-link>) under a Creative Commons Attribution 4.0 International license, so that others can access them for illustrative and verification purposes.</p>
            </sec>
            <sec id="sec17">
                <title>Reporting guidelines</title>
                <p>N/A.</p>
            </sec>
        </sec>
        <ack>
            <title>Acknowledgements</title>
            <p>The authors express their appreciation to Andrew Smith and Niklas Blomberg for initiating this effort, unlocking the necessary internal resources, and providing institutional support throughout. The authors would like to thank the following ELIXIR Hub colleagues who took part in the May 2019 workshop where the scope and methods were first discussed: Susanna Repo, John Hancock, David Lloyd, and Jerry Lanfear. Additional thanks go to the following ELIXIR Hub colleagues who helped with unclear cases during curation efforts: Giselle Kerry, Gary Saunders, Rachel Drysdale, Katharina Lauer, Serena Scollen, Jonathan Tedds, and Jen Harrow. Finally, the authors would like to express their gratitude to Graziano Pesole (Head of the Italian Node of ELIXIR) and Federico Zambelli (Technical Coordinator of the Italian Node of ELIXIR) for their institutional support throughout the project and their collaboration in defining the methodology and identifying needs.</p>
        </ack>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <mixed-citation publication-type="other">
                    <collab>Academy of Finland</collab>:
                    <article-title>Assessment of benefits of international Research Infrastructure memberships for Finland 2020-2021.</article-title>
                    <source>

                        <italic toggle="yes">Questionnaire results.</italic>
</source>
                    <year>2023</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.aka.fi/globalassets/1-tutkimusrahoitus/4-ohjelmat-ja-muut-rahoitusmuodot/4-tutkimusinfrastruktuurit/int-ris-and-finland-survey-results.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Castro</surname>
                            <given-names>LJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Martin</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lazarov</surname>
                            <given-names>G</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Measuring outcome and impacts from the BioHackathon Europe.</article-title>
                    <year>2021</year>.
                    <pub-id pub-id-type="doi">10.37044/osf.io/3dxhg</pub-id>
                    <ext-link ext-link-type="uri" xlink:href="http://BioHackrXiv.org">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Drysdale</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cook</surname>
                            <given-names>CE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Petryszak</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The ELIXIR Core Data Resources: fundamental infrastructure for the life sciences.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>2020</year>;<volume>36</volume>(<issue>8</issue>):<fpage>2636</fpage>&#x2013;<lpage>2642</lpage>.
                    <pub-id pub-id-type="pmid">31950984</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/btz959</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7446027</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Durinx</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>McEntyre</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Appel</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Identifying ELIXIR core data resources.</article-title>
                    <source>

                        <italic toggle="yes">F1000Res.</italic>
</source>
                    <year>2017</year>;<volume>5</volume>:<fpage>2422</fpage>.
                    <pub-id pub-id-type="pmid">27803796</pub-id>
                    <pub-id pub-id-type="doi">10.12688/f1000research.9656.2</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5070591</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <mixed-citation publication-type="other">
                    <collab>ELIXIR</collab>:
                    <article-title>ELIXIR Scientific Programme, 2024-2028.</article-title>
                    <year>2023</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/sites/default/files/documents/elixir-programme-24-28-full.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <mixed-citation publication-type="other">
                    <collab>ESFRI</collab>:
                    <article-title>Monitoring of research infrastructures performance.</article-title>
                    <year>2019</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.esfri.eu/sites/default/files/ESFRI_WG_Monitoring_Report.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <mixed-citation publication-type="other">
                    <collab>ESFRI</collab>:
                    <article-title>Strategy Report on Research Infrastructures.</article-title>
                    <year>2016</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.esfri.eu/sites/default/files/20160308_ROADMAP_single_page_LIGHT.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <mixed-citation publication-type="book">
                    <collab>European Commission</collab>:
                    <source>

                        <italic toggle="yes">Supporting the transformative impact of research infrastructures on European research: report of the High-Level Expert Group to assess the progress of ESFRI and other world class research infrastructures towards implementation and long-term sustainability.</italic>
</source>
                    <publisher-name>Director General for Research and Innovation, Publications Office of the European Union</publisher-name>;<year>2020</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://research-and-innovation.ec.europa.eu/document/download/17d20668-5f34-4320-8697-61dadbc82187_en">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Grillo</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Licciulli</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liuni</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>PatSearch: a program for the detection of patterns and structural motifs in nucleotide sequences.</article-title>
                    <source>

                        <italic toggle="yes">Nucleic Acids Res.</italic>
</source>
                    <year>2003</year>;<volume>31</volume>(<issue>13</issue>):<fpage>3608</fpage>&#x2013;<lpage>3612</lpage>.
                    <pub-id pub-id-type="pmid">12824377</pub-id>
                    <pub-id pub-id-type="doi">10.1093/nar/gkg548</pub-id>
                    <pub-id pub-id-type="pmcid">PMC168955</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Harrow</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hancock</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Blomberg</surname>
                            <given-names>N</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>ELIXIR-EXCELERATE: establishing Europe&#x2019;s data infrastructure for the life science research of the future.</article-title>
                    <source>

                        <italic toggle="yes">EMBO J.</italic>
</source>
                    <year>2021</year>;<volume>40</volume>(<issue>6</issue>):<fpage>e107409</fpage>.
                    <pub-id pub-id-type="pmid">33565128</pub-id>
                    <pub-id pub-id-type="doi">10.15252/embj.2020107409</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7957415</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ison</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ienasescu</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Chmura</surname>
                            <given-names>P</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The bio.tools registry of software tools and data resources for the life sciences.</article-title>
                    <source>

                        <italic toggle="yes">Genome Biol.</italic>
</source>
                    <year>2019</year>;<volume>20</volume>(<issue>1</issue>):<fpage>164</fpage>.
                    <pub-id pub-id-type="pmid">31405382</pub-id>
                    <pub-id pub-id-type="doi">10.1186/s13059-019-1772-6</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6691543</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref12">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Martin</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Repo</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>M&#x00e1;rquez</surname>
                            <given-names>JA</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Demonstrating public value to funders and other stakeholders&#x2014;the journey of ELIXIR, a virtual and distributed research infrastructure for life science data.</article-title>
                    <source>

                        <italic toggle="yes">Ann. Public Coop. Econ.</italic>
</source>
                    <year>2021</year>;<volume>92</volume>(<issue>3</issue>):<fpage>497</fpage>&#x2013;<lpage>510</lpage>.
                    <pub-id pub-id-type="doi">10.1111/apce.12328</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Martin</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>De Leo</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>D&#x2019;Ambrosio</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Publications Supported by ELIXIR and ELIXIR Italy (during the Periods 2011-2023 and 2015-2023).</article-title>
                    <source>

                        <italic toggle="yes">Zenodo.</italic>
</source>
                    <year>2024; 13 November 2024</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.14136249</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <mixed-citation publication-type="other">
                    <collab>NWO</collab>:
                    <article-title>Analysis of the Dutch participation in international research infrastructures.</article-title>
                    <year>2023</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.nwo.nl/sites/nwo/files/media-files/analysis_of_the_dutch_participation_in_international_research_infrastructures_december2023_web.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <mixed-citation publication-type="journal">
                    <collab>OECD</collab>:
                    <article-title>Reference framework for assessing the scientific and socio-economic impact of research infrastructures.</article-title>
                    <source>

                        <italic toggle="yes">OECD Science, Technology and Industry Policy Papers.</italic>
</source>
                    <year>2019</year>.
                    <pub-id pub-id-type="doi">10.1787/3ffee43b-en</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Pesole</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Liuni</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>D&#x2019;Souza</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>PatSearch: a pattern matcher software that finds functional elements in nucleotide and protein sequences and assesses their statistical significance.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>2000</year>;<volume>16</volume>(<issue>5</issue>):<fpage>439</fpage>&#x2013;<lpage>450</lpage>.
                    <pub-id pub-id-type="pmid">10871266</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/16.5.439</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Rosonovski</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Levchenko</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Bhatnagar</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Europe PMC in 2023.</article-title>
                    <source>

                        <italic toggle="yes">Nucleic Acids Res.</italic>
</source>
                    <year>2024</year>;<volume>52</volume>(<issue>D1</issue>):<fpage>D1668</fpage>&#x2013;<lpage>D1676</lpage>.
                    <pub-id pub-id-type="pmid">37994696</pub-id>
                    <pub-id pub-id-type="doi">10.1093/nar/gkad1085</pub-id>
                    <pub-id pub-id-type="pmcid">PMC10767826</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref18">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Smith</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Martin</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Blomberg</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>ELIXIR position paper on suitable business models for open data.</article-title>
                    <source>

                        <italic toggle="yes">F1000Res.</italic>
</source>
                    <year>2020</year>;<volume>9</volume>:<fpage>65</fpage>.
                    <pub-id pub-id-type="doi">10.7490/f1000research.1117782.1</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref19">
                <mixed-citation publication-type="other">
                    <collab>Swedish Research Council</collab>:
                    <article-title>National benefits from Swedish membership of international research infrastructures 2016-2019.</article-title>
                    <year>2021</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.vr.se/download/18.7b65b60f17b8a8f26a8513/1632316683047/National%20return%20RI%202016-2019.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report375436">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.178964.r375436</article-id>
            <title-group>
                <article-title>Reviewer response for version 2</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Kawashima</surname>
                        <given-names>Shuichi</given-names>
                    </name>
                    <xref ref-type="aff" rid="r375436a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r375436a1">
                    <label>1</label>Database Center for Life Science, Chiba, Japan</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>14</day>
                <month>4</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Kawashima S</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport375436" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.158264.2"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>I appreciate the authors' efforts to revise the manuscript in response to my previous comments. Most of my concerns have been appropriately addressed, and the manuscript is significantly improved in terms of clarity and reproducibility.</p>
            <p> </p>
            <p> Remaining Issue &#x2013; Citation Count Discrepancy (Figure 2 vs. Text):</p>
            <p> The authors state that they have resolved the discrepancy between Figure 2 and the corresponding citation count in the text. However, upon reviewing the current version of the manuscript and figure, I was unable to identify any changes from the originally submitted version. Both the text and Figure 2 appear unchanged, and the inconsistency (i.e., the text referring to ~5,000 citations vs. the figure showing ~6,721) remains unresolved. I would appreciate clarification on this point&#x2014;specifically, whether an update was made but not reflected in the posted version, or whether the discrepancy remains due to another reason.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the method technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Partly</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>bioinformatics, semantic web, database</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report354532">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.173833.r354532</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Kawashima</surname>
                        <given-names>Shuichi</given-names>
                    </name>
                    <xref ref-type="aff" rid="r354532a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r354532a1">
                    <label>1</label>Database Center for Life Science, Chiba, Japan</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>27</day>
                <month>2</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Kawashima S</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport354532" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.158264.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This manuscript presents an approach to identifying and measuring the scientific impact of ELIXIR-supported publications, employing text-mining of EuropePMC alongside manual curation. It offers valuable insights into the output and influence of a distributed research infrastructure, with an in-depth case study of ELIXIR Italy. The methodology is generally sound and relevant; however, several clarifications are needed to ensure transparency and reproducibility.</p>
            <p> </p>
            <p> 
                <bold>Major Concerns:</bold>
            </p>
            <p> *&#x00a0;The authors should include concrete examples (e.g., sample URLs or code snippets) illustrating how EuropePMC&#x2019;s API was queried and how retrieved data were processed. This addition would strengthen reproducibility.</p>
            <p> *&#x00a0;A subset of known ELIXIR-supported articles had to be manually whitelisted, suggesting certain limitations in the automated text-mining. The authors are encouraged to explain why these articles failed to appear in the initial searches (e.g., unusual acknowledgments or missing metadata), as such detail would be instructive for others employing similar methods.</p>
            <p> </p>
            <p> 
                <bold>Minor concerns:</bold>
            </p>
            <p> * The figure 2 indicates ~6,721 citations, whereas the text mentions 5,000. This discrepancy should be resolved for clarity.</p>
            <p> *&#x00a0;According to the text, 408 unique publications were supported by ELIXIR Italy from 2015 to 2023.&#x00a0;Figure 3 shows the distribution of these publications across the Node&#x2019;s institutes. If one sums the values for all institutes in Figure 3, the total appears to be 772, which does not match 408.&#x00a0;The authors should clarify whether Figure 3 double-counts papers co-authored by multiple institutes or if other factors account for the difference.</p>
            <p> </p>
            <p> The manuscript is well-structured, and the research offers a promising approach for tracking the impact of distributed infrastructures. Addressing the concerns above will strengthen the paper&#x2019;s clarity and transparency. I recommend minor revision prior to acceptance.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the method technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Partly</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>bioinformatics, semantic web, database</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report354530">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.173833.r354530</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Berman</surname>
                        <given-names>Helen M.</given-names>
                    </name>
                    <xref ref-type="aff" rid="r354530a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r354530a1">
                    <label>1</label>Chemistry and Chemical Biology, Rutgers, The State University of New Jersey, Piscataway, NJ, USA</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>6</day>
                <month>1</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Berman HM</copyright-statement>
                <copyright-year>2025</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport354530" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.158264.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This article describes a method to assess the impact of ELIXIR supported research. This was done by using text mining to search for relevant articles contained in EuropePMC. This procedure was used for all ELIXIR nodes and for ELIXIR Italy. In the latter case the search terms were modified to be appropriate for that node. In the first step specific search terms were used to search sections of articles. This automated procedure was followed by manual curation.</p>
            <p> </p>
            <p> It is important to have quantitative methods to analyze impact of the ELIXIR infrastructure and this is a good first step. The paper is well written, and the limitations of the approach are adequately described. For example, the EuropePMC does not index all the journals that describe projects funded under the ELIXIR umbrella. It is also disturbing that some articles are published in journals that are behind paywalls.</p>
            <p> </p>
            <p> Although the curated datasets are put into Zenodo, the authors might consider making a website that would allow authors to submit and curate their ELIXIR related articles.</p>
            <p>Is the rationale for developing the new method (or application) clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the method technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions about the method and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>If any results are presented, are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Are sufficient details provided to allow replication of the method development and its use by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Structural bioinformatics, structural biology</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
</article>
