<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "https://bdj.pensoft.net/nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">1</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:F9B2E808-C883-5F47-B276-6D62129E4FF4</journal-id>
      <journal-id journal-id-type="aggregator">urn:lsid:zoobank.org:pub:245B00E9-BFE5-4B4F-B76E-15C30BA74C02</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">Biodiversity Data Journal</journal-title>
        <abbrev-journal-title xml:lang="en">BDJ</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1314-2836</issn>
      <issn pub-type="epub">1314-2828</issn>
      <publisher>
        <publisher-name>Pensoft Publishers</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3897/BDJ.14.e184830</article-id>
      <article-id pub-id-type="publisher-id">184830</article-id>
      <article-id pub-id-type="manuscript">29858</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="biological_taxon">
          <subject>Animalia</subject>
          <subject>Archaea</subject>
          <subject>Bacteria</subject>
          <subject>Chromista</subject>
          <subject>Fungi</subject>
          <subject>Plantae</subject>
          <subject>Protozoa</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>Biodiversity &amp; Conservation</subject>
          <subject>Bioinformatics</subject>
          <subject>Data analysis &amp; Modelling</subject>
          <subject>Databases</subject>
          <subject>Ecology &amp; Environmental sciences</subject>
          <subject>Palaeontology</subject>
          <subject>Systematics</subject>
        </subj-group>
        <subj-group subj-group-type="geographical_area">
          <subject>World</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A user-centric framework for harmonizing scientific name usage</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Berendsohn</surname>
            <given-names>Walter G.</given-names>
          </name>
          <email xlink:type="simple">w.berendsohn@bgbm.org</email>
          <uri content-type="orcid">https://orcid.org/0000-0001-9945-7606</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Bánki</surname>
            <given-names>Olaf</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-6197-9951</uri>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Döring</surname>
            <given-names>Markus</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0001-7757-1889</uri>
          <xref ref-type="aff" rid="A2">2</xref>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Fichtmueller</surname>
            <given-names>David</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-0829-5849</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Güntsch</surname>
            <given-names>Anton</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-4325-4030</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Hyam</surname>
            <given-names>Roger</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-4581-1379</uri>
          <xref ref-type="aff" rid="A4">4</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Meeus</surname>
            <given-names>Sofie</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-0715-8647</uri>
          <xref ref-type="aff" rid="A5">5</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Müller</surname>
            <given-names>Andreas</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0003-1609-7882</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Vanhoorne</surname>
            <given-names>Bart</given-names>
          </name>
          <uri content-type="orcid">https://orcid.org/0000-0002-6642-4725</uri>
          <xref ref-type="aff" rid="A6">6</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Freie Universität Berlin, Botanic Garden and Botanical Museum, Berlin, Germany</addr-line>
        <institution>Freie Universität Berlin, Botanic Garden and Botanical Museum</institution>
        <addr-line content-type="city">Berlin</addr-line>
        <country>Germany</country>
        <uri content-type="ror">https://ror.org/046ak2485</uri>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Catalogue of Life, Amsterdam, Netherlands</addr-line>
        <institution>Catalogue of Life</institution>
        <addr-line content-type="city">Amsterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">GBIF, Copenhagen, Denmark</addr-line>
        <institution>GBIF</institution>
        <addr-line content-type="city">Copenhagen</addr-line>
        <country>Denmark</country>
      </aff>
      <aff id="A4">
        <label>4</label>
        <addr-line content-type="verbatim">Royal Botanic Garden Edinburgh, Edinburgh, United Kingdom</addr-line>
        <institution>Royal Botanic Garden Edinburgh</institution>
        <addr-line content-type="city">Edinburgh</addr-line>
        <country>United Kingdom</country>
        <uri content-type="ror">https://ror.org/0349vqz63</uri>
      </aff>
      <aff id="A5">
        <label>5</label>
        <addr-line content-type="verbatim">Meise Botanic Garden, Meise, Belgium</addr-line>
        <institution>Meise Botanic Garden</institution>
        <addr-line content-type="city">Meise</addr-line>
        <country>Belgium</country>
        <uri content-type="ror">https://ror.org/01h1jbk91</uri>
      </aff>
      <aff id="A6">
        <label>6</label>
        <addr-line content-type="verbatim">VLIZ, Oostende, Belgium</addr-line>
        <institution>VLIZ</institution>
        <addr-line content-type="city">Oostende</addr-line>
        <country>Belgium</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Walter G. Berendsohn (<email xlink:type="simple">w.berendsohn@bgbm.org</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: Dmitry Schigel</p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>27</day>
        <month>03</month>
        <year>2026</year>
      </pub-date>
      <volume>14</volume>
      <elocation-id>e184830</elocation-id>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/4742D24D-C103-5AEF-B1AC-E7C49CC18DF1">4742D24D-C103-5AEF-B1AC-E7C49CC18DF1</uri>
      <history>
        <date date-type="received">
          <day>10</day>
          <month>01</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>11</day>
          <month>03</month>
          <year>2026</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Walter G. Berendsohn, Olaf Bánki, Markus Döring, David Fichtmueller, Anton Güntsch, Roger Hyam, Sofie Meeus, Andreas Müller, Bart Vanhoorne</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="http://creativecommons.org/licenses/by/4.0/" xlink:type="simple">
          <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution License (CC BY 4.0), which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Biodiversity data linkage is a prerequisite for addressing pressing societal and research questions. Digitisation of resources has progressed rapidly, but this has led to a number of parallel approaches for datasets and services, making it difficult for users to identify the appropriate tool for their requirements. While scientific names are a key element for data linkage, they are not fully suited to this role. Many of them are not unique identifiers for taxa (such as the species that form the basic building block of a large part of biodiversity information) because taxonomic research has resulted in name changes. Likewise, usage is prone to errors like misspellings or misapplication of nomenclatural rules. This complexity and unreliability may demotivate data providers from readying their valuable datasets for integration into an interlinked landscape of biodiversity information. Correct linking of scientific names is an important element in this process of linking data from various sources. Aggregated taxonomic datasets and name-matching services are an essential infrastructure to build tools for this purpose and are increasingly using unique, resolvable and persistent name identifiers. Accessing the aggregated dataset via these identifiers can also display connections between the names within the dataset, linking, orthographic variants to correct spelling, synonyms to accepted taxon name etc. External datasets that hold valuable research and usage information as taxon-associated data can also be linked directly via these identifiers. This helps them to meet the FAIR data criteria (Findable, Accessible, Interoperable, Reusable). Name matching finds the aggregator's name identifier, adding this identifier to the local data record may help to further interconnect biodiversity information, if data providers are motivated to partake in this process of enabling data linkage. We posit that this motivation can be increased by simplifying the process of choosing the right method for their specific needs, which may vary widely. We thus propose a framework that helps users to select the optimal workflow to address these needs. This involves: (i) identifying and categorising the specific criteria that characterise different user needs; (ii) based on these criteria, defining the necessary metadata both for taxonomic datasets accessed by name-matching services and the name-matching services themselves; (iii) providing tools based on these metadata that will allow users to interactively and confidently choose the best-fit target dataset and name matching service for their specific purpose.</p>
      </abstract>
      <kwd-group>
        <label>Keywords</label>
        <kwd>name matching</kwd>
        <kwd>name-matching services</kwd>
        <kwd>taxonomic databases</kwd>
        <kwd>data linkage</kwd>
        <kwd>taxonomic datasets</kwd>
        <kwd>taxonomic aggregators</kwd>
        <kwd>taxonomy</kwd>
        <kwd>biodiversity research</kwd>
      </kwd-group>
      <funding-group>
        <funding-statement>European Union</funding-statement>
      </funding-group>
      <counts>
        <fig-count count="1"/>
        <table-count count="1"/>
        <ref-count count="79"/>
      </counts>
    </article-meta>
    <notes>
      <sec sec-type="Funding program">
        <title>Funding program</title>
        <p>Horizon Europe Research and Innovation Programme, HORIZON.2.6.2 – Biodiversity and Natural Resources</p>
      </sec>
      <sec sec-type="Grant title">
        <title>Grant title</title>
        <p>TETTRIs - Transforming European Taxonomy through Training, Research and Innovations (Grant Agreement 101081903) is funded under the European Union’s Horizon Europe Research and Innovation Programme, under the HORIZON.2.6.2 – Biodiversity and Natural Resources area.</p>
        <p>TNLS - Taxonomic Name Linking Service is a TETTRIs Satellite project. (<xref ref-type="bibr" rid="B13718653">TETTRIs 2024a</xref>)</p>
      </sec>
      <sec sec-type="">
        <title/>
        <p>Although we do not see a direct conflict of interest, it should be mentioned that some of the authors are directly involved in the services and datasets mentioned and analysed in this paper: Bánki and Döring in Catalogue of Life ChecklistBank, Hyam in World Flora Online Plant List, Müller in EU-nomen/PESI and Vanhoorne in WoRMS/Aphia and EU-nomen/PESI.</p>
      </sec>
    </notes>
  </front>
  <body>
    <sec sec-type="Background">
      <title>Background</title>
      <p>The work presented here was carried out within the TETTRIs (Transforming European Taxonomy through Training, Research and Innovations) project, with the primary objective of furthering the "integration of taxonomic resources to enable cross-domain data linkage" (<xref ref-type="bibr" rid="B13718629">TETTRIs 2022</xref>), a process that we consider a central enabler for knowledge transfer and creation in biodiversity sciences.</p>
      <sec sec-type="Biodiversity data linkage">
        <title>Biodiversity data linkage</title>
        <p>Data linkage (or record linkage, <xref ref-type="bibr" rid="B13718375">Harron (2016)</xref>) is "the aggregation of data from different sources concerning the same entity or individual" (<xref ref-type="bibr" rid="B13715688">Vaccaro and Swerts 2022</xref>). In our context, this entity is the taxon: a group of organisms sharing defined characteristics and distinguishable from other groups. Taxonomists assign names to these groups following internationally accepted rules. Taxa are generally arranged in hierarchical ranks that reflect presumed evolutionary relationships. Amongst these ranks, the species-level is most relevant in applied contexts, because species are generally regarded as concrete biological entities that can be used, are endangered, are found in a garden, possess defined ecological traits etc. Diverse data sources contain information related to the same taxa and publication as open data under open data licences is becoming the norm. In the process of data linkage, knowledge from disparate sources is brought together to characterise taxa and their interaction with themselves and with the environment (and humans). These taxa are typically identified by scientific names, though molecular sequences are increasingly used as proxies. The "Codes of Nomenclature" (<xref ref-type="bibr" rid="B13718420">ICZN 2012</xref>, <xref ref-type="bibr" rid="B13718555">Parker et al. 2019</xref>, <xref ref-type="bibr" rid="B13718412">ICTV 2024</xref>, <xref ref-type="bibr" rid="B13718671">Turland et al. 2025</xref>) provide strict rules as to the syntax of scientific names as well as requirements for their publication; animals, fungi and plants not only have to be described, but the published name has also to be explicitly tied to a single physical item, the so-called nomenclatural type (mostly a specimen). Traditionally, other information is then linked by using the taxon name as a common identifier. A practical approach to achieving this linkage for digital data is to map locally used taxon names <italic>(local data)</italic> to the names present in taxonomic aggregator databases (but see caveats pointed out below). Here, <italic>local data</italic> encompasses everything from individual researchers’ spreadsheets - such as those used in ecological studies - to national or supranational taxonomic databases. The latter may, in turn, also serve as taxonomic aggregators and targets for name matching in a local setting (see Table <xref ref-type="table" rid="T13723170">1</xref> for definitions of terms used).</p>
      </sec>
      <sec sec-type="Taxonomic aggregators">
        <title>Taxonomic aggregators</title>
        <p>Attempts to provide global checklists of organisms go back to early taxonomists like Linnaeus who were able to provide more or less comprehensive checklists of the species known to western science in the mid-18<sup>th</sup> century. The knowledge base soon exploded and later attempts were reduced to trying to cope with the publication of new names, achieved at least in some groups such as plants (e.g. the Index Kewensis, <xref ref-type="bibr" rid="B13719177">Lughadha (2004)</xref>). With the advent of computers and networking technologies, the vision of a global checklist of organisms (and their <italic>scientific names</italic>) seemed to become realistic again, but from early attempts (<xref ref-type="bibr" rid="B13717620">Bisby et al. 1994</xref>) to today, it has proven a rather difficult task that is by no means finished. In the last three decades, much progress has been made by increasing the number of digitally available described taxa (<xref ref-type="bibr" rid="B13749878">Bánki et al. 2025</xref>, <xref ref-type="bibr" rid="B13719253">WoRMS Editorial Board 2025</xref>). Still, several organism groups have data gaps, at times at both national and international scales and may even lack the necessary taxonomic experts all together (<xref ref-type="bibr" rid="B13749862">Hobern et al. 2021</xref>). Aggregating taxonomic data from diverse sources into unified datasets facilitates knowledge transfer and enables new research opportunities. For example, the specimen and observation data aggregated by the Global Biodiversity Information Facility (<xref ref-type="bibr" rid="B13718383">Heberling et al. 2021</xref>, <xref ref-type="bibr" rid="B13718302">GBIF Secretariat 2024</xref>) and the taxonomic literature aggregated by the Biodiversity Heritage Library (<xref ref-type="bibr" rid="B13717525">BHL 2007</xref>) are now indispensable tools for taxonomy and biodiversity research in general. For the names of taxa and (less controversially) scientific organism names in general, much progress has been made in the recent past. The existing nomenclatural and taxonomic online lists are heavily used. In some communities, taxonomic institutions are becoming involved in organising taxonomists to accelerate these developments; the World Flora Online (WFO) initiative with its <xref ref-type="bibr" rid="B13718723">WFO Plant List (2021-)</xref> assembled by Taxonomic Expert Networks (TENs) is a good example. The World Register of Marine Organisms (<xref ref-type="bibr" rid="B13719253">WoRMS Editorial Board 2025</xref>) sets an example for an organisation with an institution providing the organisational and technical base for a large-scale peer-level cooperation. Generally, <xref ref-type="bibr" rid="B13718503">Lien et al. (2023)</xref> found a “high degree of agreement on the need for a global list of accepted species and their names” as the results of their global survey of taxonomists, scientists from other disciplines and users of taxonomy. What is lacking is the financial support to build long-term sustainable infrastructures to support such development and maintain the momentum.</p>
      </sec>
      <sec sec-type="A way forward">
        <title>A way forward</title>
        <p>As a result, we think that <italic>local users</italic> who are motivated to improve their taxonomic data and search for on-line resources to do so are faced with a confusing picture, especially when working with a broad range of <italic>taxonomic groups</italic>. As <xref ref-type="bibr" rid="B13940392">Garnett et al. (2020)</xref> put it: "users, who may lack relevant taxonomic expertise, [are forced] to choose between competing lists and taxonomic treatments of groups even though they rarely understand the rationale why competing lists exist and are confused by the differences between alternate taxonomic concepts and classifications". We will here try to show ways how existing infrastructures could be used to help <italic>local users</italic> increase the quality of their <italic>scientific name</italic> data and, thus, enable linking their information by means of the names. In the following, we first have to point out some inherent problems associated with the use of <italic>scientific names</italic> for data linkage. We will then have a closer look at the requirements on the user side, to go on to existing <italic>aggregators</italic> and <italic>name-matching services</italic>. From that, we will suggest a number of criteria for tool selection on the user’s side and propose <italic>metadata</italic> elements that will provide the necessary information for <italic>taxonomic datasets</italic> and <italic>name-matching services</italic>. As a proof of concept, a demonstrator application for an updatable and interactive guide to solutions for individual use cases is presented.</p>
      </sec>
    </sec>
    <sec sec-type="Material and methods">
      <title>Material and methods</title>
      <p>We used systematic web searches and followed citations in literature to identify, test and document 20 <italic>name-matching services</italic> and 34 <italic>taxonomic datasets</italic> (56 dataset–service combinations - some services refer to a single <italic>taxonomic dataset</italic>, some allow to access several held in a repository). To ensure consistency, key terms used throughout this article are defined in Table <xref ref-type="table" rid="T13723170">1</xref> and written in italics throughout the article.</p>
      <p>As a contribution towards a formally defined common API (Application Programming Interface) for <italic>name-matching services</italic>, we compiled and compared the input parameters accepted by existing <italic>name-matching services</italic> and the fields they return. From this inventory, we proposed a set of common input parameters and output fields with standardised names (see <xref ref-type="bibr" rid="B13723105">Hyam et al. (2025a)</xref> for details).</p>
      <p>In the context of ongoing work, we extensively used botanical datasets (as <italic>local data</italic>) to test <italic>name-matching services</italic>. These included Euro+Med PlantBase (<xref ref-type="bibr" rid="B13723654">Euro+Med 2006-</xref>), which contains more than 150,000 names and herbarium records from a major herbarium (Madrid) and from smaller collections managed through the JACQ system (<xref ref-type="bibr" rid="B13718573">Rainer et al. 2023</xref>). We also used the names collected by the Global Biodiversity Information Facility (GBIF) for botanical occurrence records (<xref ref-type="bibr" rid="B13717505">Berendsohn et al. 2024b</xref>). In addition, several datasets were matched against botanical <italic>taxonomic datasets</italic> when preparing them as a contribution to the WFO Plant List, inter alia datasets from the <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="order">Caryophyllales</tp:taxon-name-part></tp:taxon-name> network (<xref ref-type="bibr" rid="B13718483">Korotkova 2022</xref>) and the <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="tribe">Cichorieae</tp:taxon-name-part></tp:taxon-name> dataset (<xref ref-type="bibr" rid="B13718494">Kilian and Raab-Straube 2009-</xref>). A use case spanning all organism groups was developed in collaboration with the German NFDI4Biodiversity network (<xref ref-type="bibr" rid="B13718195">Ebert et al. 2023</xref>) using long-term ecological research datasets from LTER Germany (<xref ref-type="bibr" rid="B13718277">Frenzel 2025</xref>). Zoological datasets for testing includes those obtained from Catalogue of Life ChecklistBank (<xref ref-type="bibr" rid="B13723662">Bánki et al. 2023</xref>), from the GBIF and, for example, the German freshwater fish monitoring dataset (<xref ref-type="bibr" rid="B13718285">Friedrichs-Manthey et al. 2024</xref>). This type of “taxonomic annotation” of ecological data was also addressed in detail by <xref ref-type="bibr" rid="B13718472">Islam et al. (2024)</xref> in their comprehensive case study, which highlighted the difficulties faced by non-taxonomists when performing such tasks. The potential user requirements set out in the current article were derived from Islam et al., from communications with <italic>local users</italic> providing data for testing and from our own experience as <italic>local users</italic> of <italic>name-matching services.</italic> The process was further informed by discussions held in project meetings and at international congresses (see, for example, <xref ref-type="bibr" rid="B13717226">Berendsohn (2023a)</xref>, <xref ref-type="bibr" rid="B13717263">Berendsohn (2024)</xref>, <xref ref-type="bibr" rid="B13717362">Anonymous (2024a)</xref>).</p>
      <p>We did not use procaryotic or viral names for testing, but identified major data sources (see Appendix 1).</p>
    </sec>
    <sec sec-type="Inherent caveats of the name-matching workflow">
      <title>Inherent caveats of the name-matching workflow</title>
      <sec sec-type="Scientific names as unique identifiers">
        <title><italic>Scientific names</italic> as unique identifiers</title>
        <p>Using a <italic>scientific name</italic> as the identifier of a taxon is a pragmatic approach to link cross-domain biodiversity data. The names provide a standard way to connect information about a given taxon, for example, a species. Thus, data from many different sources can be combined. For example, information on the species' uses (e.g. medicinal, cultural, construction), its morphology (appearance and form), its geographical distribution, its conservation status (e.g. threatened by extinction) and threats it poses (poison, invasive, pest). Such data have been collected by humans for millennia and recorded in persistent forms for centuries. Since the mid-1700s, this has been in connection with <italic>scientific names</italic> governed by internationally agreed rules.</p>
        <p>However, the approach entails several notable caveats. A common quality problem in the data themselves is mis-identification: an organism may be labelled with a name that represents a different taxon. Furthermore, as <xref ref-type="bibr" rid="B13723105">Hyam et al. (2025a)</xref> point out, homonyms and isonyms can lead to false positive matches; non-matches can be caused by variations in the orthography of the <italic>canonical name</italic> or (often!) in the author/year string, which may arise from changes in the rules, human error, transliteration or OCR mistakes; and names found in recent literature or databases may be the result of generative AI hallucinations (<xref ref-type="bibr" rid="B13718393">Hyam 2024</xref>), a phenomenon that can undermine efforts to build dependable taxonomic datasets.</p>
        <p>Beyond these issues, <italic>scientific names</italic> present inherent issues that can affect the quality of <italic>data linkages</italic>: the international rules of nomenclature that govern <italic>scientific names</italic> can require that the name of a taxon be changed. Such nomenclatural name changes can be handled automatically if a <italic>taxonomic dataset</italic> encompasses the necessary information on the nomenclatural and taxonomic relationships of the name in question. However, the rules may also result in the same name referring to taxa differently circumscribed at different times or by different experts. This is where the concept problem arises, which we have to address in some detail before returning to the core subject of name matching.</p>
      </sec>
      <sec sec-type="The concept problem">
        <title>The concept problem</title>
        <p>A far more complex issue is that <italic>scientific names</italic> are essentially pointers to a concept of a taxon, for example, that of a species. These concepts are scientific hypotheses about the descent and boundaries of the taxon and, as new research on species evolution accumulates, hypotheses may change. This means that taxa formerly treated as separate may be merged, rendering some names synonyms; conversely, a taxon long regarded as single may be split into multiple taxa following careful investigation.</p>
        <p>Every synonym should refer to the accepted name of a taxon. However, because names are not necessarily changed when a taxon’s circumscription changes (following the rules of nomenclature), taxonomic expertise is sometimes required to decide whether data provided under a particular taxon name from different sources actually refer to the same currently accepted taxon. To complicate matters further, the same name can sometimes refer to different accepted taxa because the naming occurred under different codes of nomenclature (see Checking the names of cyanobacteria in Appendix 1). “<italic>In practice, many people provide taxonomic names in their datasets or publications but not a source specifying a usage. The information needed to map the relationships between names and usages in taxonomic monographs or revisions is typically not presented in a machine-readable format</italic>” (<xref ref-type="bibr" rid="B13718619">Sterner et al. 2020</xref>). <xref ref-type="bibr" rid="B13718610">Remsen (2016)</xref> provides a thorough analysis and calls for “<italic>comprehensive taxonomic thesauri ... to model the relationships between names and taxa</italic>” to come to grips with it. This gets to the core of the problem. Attempts have been made to address it by distinguishing taxon concepts and labelling them with non-nomenclatural identifiers. However, applying this approach to all or large groups of organisms would require an enormous expansion of the knowledge base. Consequently, such data currently exist only for a few model datasets and, “<italic>in practice, aggregators have made fundamental design choices […] by excluding taxonomic conflict as an aspect of biodiversity knowledge worthy of being preserved</italic>” (<xref ref-type="bibr" rid="B13718268">Franz and Sterner 2018</xref>). <xref ref-type="bibr" rid="B13718619">Sterner et al. (2020)</xref> also note that “<italic>New approaches are making progress on these obstacles. Theoretical advances in the representation of taxonomic intelligence have made it increasingly possible to implement efficient querying and reasoning methods on name-usage relationships</italic> (<xref ref-type="bibr" rid="B13717888">Chen et al. 2014</xref>, <italic><xref ref-type="bibr" rid="B13718257">Franz et al. 2015</xref></italic>, <xref ref-type="bibr" rid="B13717791">Chawuthai et al. 2016</xref>). <italic>Perhaps most importantly, growing efforts to produce name-usage mappings on a medium scale by data providers and taxonomic authorities suggest an all-or-nothing approach is not required”.</italic> We agree with the latter statement, but view the progress so far as not usable in real-world contexts.</p>
        <p>A more practical approach may be to enable communication of changes once a linkage between a set of <italic>local data</italic> and an aggregator's <italic>taxonomic dataset</italic> has been established by name matching and subsequent storage of aggregator <italic>name IDs</italic> locally. The idea of a "Concept subscription service" (<xref ref-type="bibr" rid="B13717263">Berendsohn 2024</xref>) was developed into a technical specification of a "Taxonomic activity notification service" by <xref ref-type="bibr" rid="B13718401">Hyam et al. (2025b)</xref> and could be implemented as an additional aggregator service. This requires further research into the categories of changes in the content of taxonomic databases that influence the taxonomic concept behind a <italic>scientific name</italic> (see <xref ref-type="bibr" rid="B13723675">TETTRIs (2024b)</xref>). However, a functional workflow for name matching remains a prerequisite for using such a service and, to be truly useful, it depends on the availability of comprehensive datasets covering names across all <italic>taxonomic groups</italic>.</p>
      </sec>
      <sec sec-type="Proliferation of identifiers">
        <title>Proliferation of identifiers</title>
        <p>While name matching and subsequent correction or harmonisation of names can help to link data via the name strings themselves, data integration across biodiversity information systems becomes much more efficient when persistent <italic>name IDs</italic> are used (<xref ref-type="bibr" rid="B13718597">Rambold et al. 2017</xref>, but see caveats below). To serve that function, clear rules and transparent policies for assigning identifiers to name records are essential. The current situation, however, is marked by a proliferation of so-called “taxon identifiers”: for example, GBIF lists 64 different “taxon identifiers” for the sunflower genus <italic>(Helianthus)</italic> citing Wikidata (Fig. <xref ref-type="fig" rid="F13723683">1</xref>). Taxonomic communities are, therefore, urged to ensure the availability of well-documented truly stable <italic>name identifiers</italic> in their domain, independent of the taxonomic acceptance of the individual name. This also enables machine interoperability and forms an important step towards the shift to a data engineering approach as deemed essential for a successful global data infrastructure, for example, by the WorldFAIR project (<xref ref-type="bibr" rid="B13940383">Hodson and Gregory 2024</xref>).</p>
        <p>This proliferation raises practical concerns for users who must, or choose to, add <italic>name IDs</italic> to their data during “taxonomic annotation”. A common question is how stable these identifiers really are in practice: “<italic>Can my sunflower turn into a bug tomorrow</italic>?” (F. Zander, pers. comm.) - i.e may the found <italic>name ID</italic> be reused for another name at a later stage? Part of the confusion stems from conflating <italic>name IDs</italic> and taxon identifiers. A name is governed by the Codes of Nomenclature and is, therefore, comparatively stable; a taxon is a conceptual entity not governed by such codes, making its identifiers intrinsically less stable (see the taxon concept discussion above) and the actual name the taxon identifier resolves to may change, pointing to the accepted <italic>scientific name</italic> for the taxon. Consequently, using the term “taxonID” for name records is potentially misleading, since taxa are always associated with an accepted name. However, this term has become thoroughly established by its use in standards like Darwin Core (<xref ref-type="bibr" rid="B13718731">Wieczorek et al. 2012</xref>) and should, thus, not be touched.</p>
        <p>The need for durable, unique and resolvable <italic>name IDs</italic> arises from the requirement to verify how a given name is treated in aggregated datasets. Ideally, identifiers should resolve names (including synonyms, but also orthographic variants, isonyms and other nomenclaturally invalid designations) both to their nomenclatural background (e.g. correct spelling) and to their taxonomic usage (i.e. current accepted name). <italic>Nomenclators</italic> and authoritative name lists are best placed to provide such <italic>name IDs</italic>, but even these rarely publish explicit policies on how identifiers behave in cases of name changes, orthographic corrections, authorship revisions or adjustments to nomenclatural citations. Few <italic>taxonomic datasets</italic> make such policies transparent (see <xref ref-type="bibr" rid="B13723706">TETTRIs (2025)</xref>).</p>
      </sec>
      <sec sec-type="The illusion of precision">
        <title>The illusion of precision</title>
        <p>Linked Data methods can improve data precision, but if the underlying semantic resources are unstable or inconsistent, they may reduce data quality and re-usability. Scientific names are not fixed references to clearly defined taxonomic concepts. Converting names in source data into persistent, resolvable identifiers tied to a particular taxonomic dataset can create a false sense of accuracy. In practice, this often remains a time-bound, deterministic mapping of a text string to a presumed concept defined within that dataset. During this process, noise and errors may be smoothed away, leaving future users with unwarranted confidence in the results. What follows from this? First, <italic>local users</italic> should treat name-matching as part of their research workflow and apply it critically, following good scientific practice, especially when using fuzzy matching (<xref ref-type="bibr" rid="B13718347">Grenié et al. 2022</xref>). <italic>Local users</italic> that are actually aggregators of research data (such as repositories of ecological data) should preserve original, unmodified source data after applying such services, so that matching can be repeated for specific purposes. There are actually two issues here - depending on the policies of the responsibles for the <italic>taxonomic aggregator, scientific names</italic> may be modified in the <italic>taxonomic dataset</italic>, so that, for example, the previously matched names now match differently. A second issue (not really focused on in the context of this article) are changes in the taxonomy, i.e. what accepted name or higher taxon in the aggregator's classification the matched name (or its <italic>name-ID</italic>) now leads to. We hope that our framework supports informed service selection for the core <italic>name matching</italic> process. For <italic>taxonomic aggregators</italic>, this underlines the need for a shared and harmonised strategy for managing <italic>name IDs</italic> and documenting <italic>taxonomic datasets</italic> and <italic>name-matching services</italic>.</p>
      </sec>
    </sec>
    <sec sec-type="The user side: matching and linking">
      <title>The user side: matching and linking</title>
      <sec sec-type="Who are (potential) users?">
        <title>Who are (potential) users?</title>
        <p>We examined a range of use cases across different research areas. At a basic level, the distinction between name matching and searching can be blurred (see <xref ref-type="bibr" rid="B13718393">Hyam (2024)</xref>). On-line searching is often carried out to obtain taxon-<italic>associated data</italic>, for example, its uses, ecological traits, or conservation status. Such searches are very common. In this article, however, we do not consider searches whose primary aim is retrieving <italic>associated data</italic>. Instead, our goal is to improve linkage of <italic>associated data</italic> by improving name-based data integration. We therefore focus on <italic>local users</italic> who perform name matching to verify correct name spelling, nomenclatural validity, taxonomic acceptance or systematic placement (e.g. family assignment) in the target <italic>taxonomic dataset.</italic> Ideally, this produces a persistent link between the name in the aggregator and the user’s name. Potential users in this context are anyone who creates or works with datasets that include <italic>scientific names.</italic> This spans many disciplines: biodiversity, ecology and environmental sciences; conservation biology; agriculture, forestry and fisheries; marine sciences; geology; public health and epidemiology; forensics; archaeology; legal, commercial and administrative domains; bioinformatics; art; and citizen science. Relevant <italic>local data</italic> may include observation or measurement records (traits, abundances, biomass, successional stages or long-term monitoring series). Included are also lists of labels (taxonomic annotations) for images, molecular sequences, natural-history specimens, sediment or forensic samples or commercial and pharmaceutical products. <italic>Local data</italic> may also document organismal relationships, such as pollination, pest–host interactions, disease associations, food chains or parasitism. Ecosystem assessments, based on indicator species, palaeontological material or historical age determinations, are included as well. Other examples are specialised taxonomic lists (e.g. Red Lists, CITES appendices, Natura 2000 species, SUDs - Special Use Designations) and commercial designations. Core taxonomic resources, such as monographs, checklists, floras, faunas and mycotas, also fall within this scope.</p>
      </sec>
      <sec sec-type="User motivation">
        <title>User motivation</title>
        <p>Name matching as a means of <italic>data linkage</italic> requires effort from users.</p>
        <p>For those compiling core taxonomic datasets as <italic>local data</italic>, this effort comes naturally, because name matching directly improves their product. Assuming good data quality at the aggregator side, name matching can reveal orthographic errors, improve adherence to standards (e.g. author abbreviation in botanical names), detect homonyms and expose discrepancies in name acceptance for nomenclatural or taxonomic reasons. Differences in taxonomic structure or opinion may be revealed and spark discussion (see, for example, debate on species aggregates in <xref ref-type="bibr" rid="B13718532">Malekmohammadi et al. (2024)</xref>).</p>
        <p>Researchers who do not primarily focus on taxonomy may require additional motivation to perform name matching. Encouraging data creators to produce FAIR-compliant results (<xref ref-type="bibr" rid="B13718744">Wilkinson et al. 2016</xref>) should be part of general scientific practice. Motivations for applying name matching can be grouped into two broad types: intrinsic scientific motivation and external or mandated motivation. Intrinsic scientific motivation is driven by the pursuit of high-quality scientific data: ensuring correct name orthography, accurate citation of a taxon’s classification (e.g. family assignment) and, when taxa are the study objects, efficient retrieval and integration of all relevant information, including data linked to synonymous or related names.</p>
        <p>External motivation comes from institutional, legal, infrastructural or publishing requirements. Examples include funder-imposed conditions (e.g. BEXIS-2 project requirements in Germany, <xref ref-type="bibr" rid="B13717772">Chamanara et al. (2021)</xref>), name registration for electronic publication in zoology and mycology or regulatory frameworks (e.g. country reporting under the EU Flora Fauna Habitat Directive, <xref ref-type="bibr" rid="B13718223">EU (1992)</xref>). EU-nomen (a.k.a. PESI, <xref ref-type="bibr" rid="B13718048">de Jong et al. (2015)</xref>) is explicitly recommended as a reference list for species names in the technical guidance document on how species distributions under the INSPIRE directive of the EU Commission might be implemented by EU Member States (<xref ref-type="bibr" rid="B13718249">European Commission 2024</xref>). Catalogue of Life (<xref ref-type="bibr" rid="B13749878">Bánki et al. 2025</xref>) is used as the taxonomic reference for the EUNIS system (<ext-link ext-link-type="uri" xlink:href="https://eunis.eea.europa.eu/about">https://eunis.eea.europa.eu/about</ext-link>), harmonising the species reporting by Member States under the EU Birds, Habitats and Invasive Species Directives and is the taxonomic reference for the Global Biodiversity Information Facility. The World Register of Marine Species (<xref ref-type="bibr" rid="B13719253">WoRMS Editorial Board 2025</xref>) is the taxonomic reference for the Ocean Biodiversity Information System (OBIS, https://obis.org). The World Flora Online (<xref ref-type="bibr" rid="B13718723">WFO Plant List 2021-</xref>) contributes to the Global Plant Conservation Strategy. Some journals already require citing <italic>name IDs</italic>, at least for new organism names, for example, some PLOS journals require the IPNI LSID (<xref ref-type="bibr" rid="B13718337">Govaerts et al. 2022</xref>) for new botanical names. For electronic-only publication of new zoological names, registration and citation of a ZooBank LSID are mandatory (<xref ref-type="bibr" rid="B13718420">ICZN 2012</xref>); for fungal names, all publications must cite the <italic>name ID</italic> issued by one of the recognised repositories (<xref ref-type="bibr" rid="B13718671">Turland et al. 2025</xref>). AlgaeBase (<xref ref-type="bibr" rid="B13719245">Guiry and Guiry 2025</xref>) requires a PhycoBank ID for new names. Journals that support the authoring process are beginning to link <italic>scientific names</italic> automatically and display identifiers — for example, Pensoft's ARPHA writing tool now uses Global Names Recognition and Discovery Services (<xref ref-type="bibr" rid="B13723725">Mozzherin and Shorthouse 2019</xref>) and Catalogue of Life ChecklistBank (<xref ref-type="bibr" rid="B13723662">Bánki et al. 2023</xref>) to obtain identifiers (T. Georgiev and L. Penev, pers. comm.). These requirements can already increase the fairness of research data, since links to persistent identifiers may be added where data are deposited. Some taxonomic databases import those registrations and identifiers semi-automatically (e.g. Catalogue of Life ChecklistBank via Plazi TreatmentBank - <xref ref-type="bibr" rid="B13723733">Plazi (2021)</xref>; WoRMS via Pensoft - <xref ref-type="bibr" rid="B13723741">Van Maldeghem et al. (2022)</xref>).</p>
        <p>The institutional environment also influences uptake. Where biodiversity informatics research is carried out, FAIR principles are more likely to become part of the research workflow. Today, open data are an essential prerequisite for the work of taxonomists and for biodiversity research in general. Institutions producing taxonomic outputs (revisions, checklists, <italic>nomenclators</italic>) tend to appreciate the need for data sharing and may participate in Taxonomic Expert Networks (TENs) as aggregators or do host <italic>nomenclators</italic>, provided technical expertise and support are available.</p>
        <p>Nevertheless, even people responsible for helping users map names face a fragmented and sometimes confusing landscape of overlapping <italic>taxonomic datasets</italic> and <italic>name-matching services</italic> (<xref ref-type="bibr" rid="B13718347">Grenié et al. 2022</xref>). <italic>Name-matching services</italic> differ in features and can produce different results when matching the same pair of datasets. Clarifying terminology used to characterise service processes (e.g. “fuzzy matching”) and data labels (“scientific name”) is needed (<xref ref-type="bibr" rid="B13718472">Islam et al. 2024</xref>). We posit that <italic>local users</italic> also need guidance on which <italic>taxonomic dataset</italic> best suits their purpose; to provide this, we must define parameters for user needs and represent them as searchable <italic>metadata</italic> on the aggregator side.</p>
      </sec>
    </sec>
    <sec sec-type="Taxonomic aggregators: datasets and services">
      <title>Taxonomic aggregators: datasets and services</title>
      <p>To bring greater transparency to an otherwise confusing landscape, we have fixed the terminology we use in this article in the context of name matching. In Table <xref ref-type="table" rid="T13723170">1</xref>, we defined <italic>taxonomic aggregators</italic> as online-accessible databases that host <italic>taxonomic datasets</italic>, i.e. structured lists of <italic>scientific names</italic>. Our focus here is on <italic>taxonomic aggregators</italic> that offer <italic>name-matching services</italic>. However, it proved useful to distinguish between the <italic>taxonomic datasets</italic> used by these services and the services themselves, even though these often go hand in hand. Some <italic>taxonomic aggregators</italic> do not offer their own <italic>name-matching services</italic> and some provide only an API (Application Programming Interface) for programmatic access without offering a readily available service for non-technical users. We also distinguish between <italic>taxonomic aggregators</italic> that function as dataset repositories and those that rely on a single aggregated <italic>taxonomic dataset</italic>.</p>
      <sec sec-type="Taxonomic datasets">
        <title>Taxonomic datasets</title>
        <p><italic>Taxonomic datasets</italic> typically present a hierarchical, tree-like taxonomy in which each taxon constitutes a node. Each <italic>scientific name</italic> is either assigned as the accepted name of a taxon or treated as a synonym (except in cases where the name exists, but cannot currently be resolved). As an exception from this definition, we include <italic>nomenclators</italic> as a special class of datasets. They systematically catalogue <italic>scientific names</italic> along with their authorship, publication date and references, nomenclatural status and (sometimes) type information and focus on nomenclatural accuracy, such as on correct spelling and nomenclatural validity rather than providing taxonomic opinion or classification.</p>
        <p>Such taxonomic datasets aim to provide comprehensive coverage for particular organism groups, either globally or internationally (e.g. at a European scale). The Catalogue of Life monthly and annual editions are currently the only datasets attempting to unite all biota into a single global dataset (<xref ref-type="bibr" rid="B13749862">Hobern et al. 2021</xref>, <xref ref-type="bibr" rid="B13749878">Bánki et al. 2025</xref>). At the European level, PESI/EU-nomen (<xref ref-type="bibr" rid="B13718048">de Jong et al. 2015</xref>) serves a similar function for European taxa.</p>
        <p>Data sources for the compilation of <italic>taxonomic datasets</italic> may include scientific literature, smaller <italic>taxonomic aggregators</italic>, data from publications or, in some cases, even original unpublished data. An important consideration regarding <italic>taxonomic datasets</italic> is the extent to which they are driven by and used by the respective taxonomic community.</p>
        <p>The boundary between <italic>local data</italic> and the aggregator's <italic>taxonomic dataset</italic> may depend on context. For example, the Euro+Med PlantBase team, as a <italic>local user</italic>, has extensively used World Flora Online services for name matching to optimise EU-nomen processes (<xref ref-type="bibr" rid="B13723755">Müller and Güntsch 2025</xref>), with the aim of improving the <italic>local data</italic> and enabling the delivery of content data (primarily geographic distribution and common names) to the World Flora Online portal. Conversely, the Euro+Med taxonomic dataset (<xref ref-type="bibr" rid="B13723654">Euro+Med 2006-</xref>) forms part of the PESI/EU-nomen <italic>taxonomic dataset</italic> and <italic>name-matching service</italic>.</p>
        <sec sec-type="Categorising taxonomic datasets">
          <title>Categorising taxonomic datasets</title>
          <p>To characterise datasets, a few basic parameters may be used:</p>
          <p><list list-type="bullet">
            <list-item>
              <p>Taxonomic scope: Revision-scale (Genus, small family); Large <italic>taxonomic group</italic> (Plants, <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name>, Lichens, Butterflies, Mammals, Birds, ...); All organisms;</p>
            </list-item>
            <list-item>
              <p>Geographic scope: Local, State, National, Regional (supranational), Global;</p>
            </list-item>
            <list-item>
              <p>Thematic scope: pests, alien, Red List, marine species, …etc.;</p>
            </list-item>
            <list-item>
              <p>Completeness (for a given scope);</p>
            </list-item>
            <list-item>
              <p>Community scope: Broadly anchored and used dataset/database, Broadly used +/- individual contribution;</p>
            </list-item>
            <list-item>
              <p>Activity: Continuously updated; Static;</p>
            </list-item>
            <list-item>
              <p>Sustainability;</p>
            </list-item>
            <list-item>
              <p>Accessibility (open access);</p>
            </list-item>
            <list-item>
              <p>Linkability (persistent and resolvable identifiers).</p>
            </list-item>
          </list></p>
          <p>Some of these properties are key criteria for users when selecting a dataset for their name-matching efforts.</p>
        </sec>
      </sec>
      <sec sec-type="Name-matching services">
        <title>Name-matching services</title>
        <p>We distinguish four main types of name-matching processes:</p>
        <p><list list-type="order">
          <list-item>
            <p>Direct use of the <italic>name-matching service</italic>: using the on-line user interface provided by the service (see Appendix 2);</p>
          </list-item>
          <list-item>
            <p>Using third-party tools: Leveraging tools such as OpenRefine (an open-source tool for data cleaning and transformation), that access the <italic>name-matching</italic> services (see <xref ref-type="bibr" rid="B13718546">Mozzherin et al. (2024)</xref>, also Appendix 3);</p>
          </list-item>
          <list-item>
            <p>Using a web-accessible API or a programming package to access the <italic>name-matching services</italic> (see Appendix 4);</p>
          </list-item>
          <list-item>
            <p>Using local tools: downloading the dataset and using local tools to perform the matching.</p>
          </list-item>
        </list></p>
        <p>The choice of method depends mainly on the expected outcome, the number of records to be matched and the technical expertise available. Type 3 or 4 typically requires biodiversity-informatics expertise and even type 2 may not be attractive to non-technical users.</p>
        <p>Data input depends on the chosen process. For type 1, a list of names may be pasted into a web interface or uploaded as a file in tabular form. For type 2, the <italic>local data</italic> must be loaded into the external tool. Type 3 and 4 processes depend on the form of local processing.</p>
        <p>Results for process types 1 and 2 are provided as lists of exact matches and (for some services) lists of possible candidates. Some type 1 services offer interactive selection and acceptance of candidates as matches; this is also a feature of OpenRefine (type 2).</p>
        <p><italic>Name-matching services</italic> offered by <italic>taxonomic aggregators</italic> may rely on a single <italic>taxonomic dataset</italic> or the aggregator may act as a repository for multiple independent <italic>taxonomic datasets</italic> (COL-GBIF ChecklistBank, Global Names, TNRS, see Appendix 2). In the latter case, services can be configured to operate across all or selected datasets. When restricted to a single dataset, users can generally expect a taxonomically coherent outcome, otherwise they may use the matching to discover conflicting information. Existing <italic>name-matching services</italic> differ in their features and different services may even produce different results when matching the same two datasets, for example, when one service bases exact matches on <italic>canonical names</italic>, while another does not.</p>
        <p>Beyond identifying exact matches between the input name and entries in the selected taxonomic dataset (matching in the strict sense, <xref ref-type="bibr" rid="B13718393">Hyam (2024)</xref>), a key functionality of <italic>name-matching services</italic> is their ability to suggest potential matches (candidates) for names that cannot be matched exactly. Various strategies address this challenge. For instance, some matching services restrict comparison to the <italic>canonical name</italic>, disregarding author citations or publication years. Another common strategy is fuzzy matching, which identifies similar names, based on minor character differences. <xref ref-type="bibr" rid="B13718347">Grenié et al. (2022)</xref> provide an overview of fuzzy-matching techniques and associated risks.</p>
        <p>With respect to input and output for the <italic>name-matching services</italic>, we compiled a list of the input parameters and output fields of a number of services. From this, a kind of minimal common denominator for such services has been defined and a common vocabulary proposed (<xref ref-type="bibr" rid="B13723105">Hyam et al. 2025a</xref>). We also formulated a wish list of desired properties, based on use case studies, which may help to improve the services themselves or at least provide more transparency with regard to the methods used for matching and fuzzy matching (<xref ref-type="bibr" rid="B13723771">Berendsohn 2023b</xref>).</p>
        <p>By analysing the challenges faced by <italic>local users</italic>, we first formulated a set of general recommendations across <italic>taxonomic groups</italic> (Appendix 1), providing an overview that already helps some <italic>local users</italic> identify suitable services and datasets. However, we recognised that this approach is insufficient, as more specific (and more general) user needs remain unmet. Additional guidance is provided through listings of the characteristics of available <italic>name-matching services</italic> (Appendix 2) and references to tools requiring technical expertise (Appendices 3 and 4). Yet, establishing a general workflow that systematically guides users towards an optimal dataset–service combination requires a more formalised approach. To this end, we sought to distill user requirements into a minimal set of questions that can be linked to <italic>metadata</italic> describing the services, datasets and their possible combinations. By prompting users to answer these questions, the workflow should help identify the most suitable dataset–service combination for their specific needs.</p>
      </sec>
    </sec>
    <sec sec-type="A framework to harmonise name usage by name matching">
      <title>A framework to harmonise name usage by name matching</title>
      <sec sec-type="The workflow for mapping local data to taxonomic datasets">
        <title>The workflow for mapping <italic>local data</italic> to <italic>taxonomic datasets</italic></title>
        <p>The core element of this workflow is the name-matching process. However, we observed significant variation in user requirements regarding the resulting mapping, i.e. the integration and linkage of <italic>local data</italic> with <italic>taxonomic aggregators</italic>. This variability also characterises the range of available <italic>name-matching services</italic> and their underlying <italic>taxonomic datasets</italic>, which may or may not meet specific user needs. Consequently, no single, universally applicable workflow exists.</p>
        <p>Facilitating and streamlining the use of <italic>name-matching services</italic> may help to lower barriers and, thereby, increase linkages between taxonomic and non-taxonomic data that rely on names as the (initial) linking element.</p>
        <p>There are six main steps in the workflow for mapping name usage in <italic>local data</italic> to <italic>taxonomic datasets</italic>, with steps 3-5 representing the name-matching process itself:</p>
        <p><list list-type="order">
          <list-item>
            <p>Defining the purpose of the mapping exercise;</p>
          </list-item>
          <list-item>
            <p>Selecting the target aggregator (including the dataset and the associated name matching service);</p>
          </list-item>
          <list-item>
            <p>Preparing the data: A list of names is required, which can be created from a textual table column or a database table. Each name should appear on a separate line. For file uploads, specific formats (column titles, delimiters) may be required;</p>
          </list-item>
          <list-item>
            <p>Entering the data: This depends on the chosen type of checking process: pasting a list of names into a web interface, uploading a table or loading the data into a local tool;</p>
          </list-item>
          <list-item>
            <p>Obtaining and interpreting the results: Online services and OpenRefine provide the results as lists of exact matches and possible candidates. Interpretation involves assessing these candidates and selecting the appropriate match;</p>
          </list-item>
          <list-item>
            <p>Incorporating the results locally: This involves making local corrections, based on the matching results. Ideally, it also includes integrating the <italic>taxonomic dataset's name ID</italic> into the <italic>local data</italic>, enabling linkage and potential future interaction with the <italic>taxonomic aggregator</italic>.</p>
          </list-item>
        </list></p>
        <p>We propose a simple set of user-orientated criteria to support step (1) and define <italic>metadata</italic> to support these criteria in the selection of relevant datasets and services for step (2).</p>
        <p>Data preparation (step 3) largely consists of producing standardised name strings before a list of names can be used in the service. Some database systems offer such lists as exports in standard formats such as DwC (Darwin Core; <xref ref-type="bibr" rid="B13718731">Wieczorek et al. (2012)</xref>), ColDP (Catalogue of Life Data Package; <xref ref-type="bibr" rid="B13718205">Döring and Ower (2019)</xref>) or as flat-file exports (e.g. from the herbarium collection system JACQ; <xref ref-type="bibr" rid="B13718573">Rainer et al. (2023)</xref>). However, specific transformations may still be necessary to conform to the respective name-matching service. For example, the Catalogue of Life ChecklistBank tool requires standard column titles for uploaded tables. While DwC provides these directly, in JACQ the relevant field for the name is called NameAuthorYearString. Most services recognise only a single column - only in Catalogue of Life's ChecklistBank <italic>canonical name</italic> and author/year string may be provided separately, allowing users to obtain canonical and full-name matches in a single run. Some services allow users to interactively identify the column that contains names if it exists under another label in the uploaded table (e.g. WFO Plant List matching). A specific delimiter between column values (comma, tabulator) may be required or it may be detected automatically. We suggest that standardising these features would benefit users, beginning with a set of common input parameters and output fields (<xref ref-type="bibr" rid="B13723105">Hyam et al. 2025a</xref>), named in accordance with community standards.</p>
        <p>The specific workflows implemented by each <italic>name-matching service</italic> (steps 3–5) are typically documented (some in more detail than others) by the service providers. We provide links to these resources to support users in effectively accessing and applying the services in Appendix 2.</p>
        <p>The final part of the workflow (step 6) concerns how <italic>local users</italic> apply the matching results. This is highly dependent on users’ underlying motivations (see section on motivation above). Actions may range from correcting a misspelled name or fixing an erroneous classification, to incorporating a resolvable identifier from the <italic>taxonomic dataset</italic> or even to actively tracking changes in taxonomic concepts through a (yet-to-be-implemented) “Concept Subscription Service” (<xref ref-type="bibr" rid="B13718401">Hyam et al. 2025b</xref>).</p>
        <p>To address the challenges posed by steps 1 and 2, we sought to demonstrate how an application, based on user requirements and metadata, can assist users in identifying a <italic>name-matching service</italic> suited to their particular needs. As a proof of concept, we developed a simple prototype (<xref ref-type="bibr" rid="B13745307">Fichtmüller et al. 2025</xref>).</p>
      </sec>
      <sec sec-type="Characterising user requirements">
        <title>Characterising user requirements</title>
        <p>We examine user requirements from the taxonomic name-matching perspective, as detailed under User motivation above, with the aim of defining <italic>metadata</italic> needed to match requirements with combinations of services and datasets. While some services may provide additional taxon information – such as geographic distribution, descriptions or images – name matching specifically to find such content is beyond this article's scope. The main selection criteria are classified as follows (combinations possible).</p>
        <p>Organism group: Multiple or unknown groups OR one or more of the following: Animals, Plants, <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="above-family">Algae</tp:taxon-name-part></tp:taxon-name>, <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name>, Bluegreen <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="above-family">Algae</tp:taxon-name-part></tp:taxon-name> (<tp:taxon-name><tp:taxon-name-part taxon-name-part-type="phylum">Cyanobacteria</tp:taxon-name-part></tp:taxon-name>), <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="division">Bacteria</tp:taxon-name-part></tp:taxon-name>, Virus (this list should be extended whenever a reasonably complete checklist for a large subgroup becomes available for name matching).</p>
        <p>Geographic scope: Global; Continent or Macroregion; specific countries.</p>
        <p>Thematic scope: Pests, invasives, marine, fossils etc. (marine species and fossils are available in the current prototype).</p>
        <p>Number of names to be checked simultaneously: (choose one) up to 5000 or &gt; 5000 (this is necessary because web interfaces for pasting names and certain file uploads restrict the number of names processed).</p>
        <p>Target and purpose of name matching - I want to check (choose at least one):</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Orthography of <italic>canonical name</italic> (name without author / year);</p>
          </list-item>
          <list-item>
            <p>Orthography of full name (including author abbreviations and year);</p>
          </list-item>
          <list-item>
            <p>Acceptance (whether it is an accepted taxon name, a synonym of another name or taxonomically unresolved);</p>
          </list-item>
          <list-item>
            <p>Classification (list of higher taxa the name belongs to within the hierarchy of the aggregator's taxonomic dataset).</p>
          </list-item>
        </list></p>
        <p>Data linkage requirements (choose one):</p>
        <p><list list-type="bullet">
          <list-item>
            <p>I am not interested in identifiers and links for the name;</p>
          </list-item>
          <list-item>
            <p>I want a persistent identifier for the name in the aggregator's <italic>taxonomic dataset</italic>;</p>
          </list-item>
          <list-item>
            <p>I want a persistent resolvable identifier for that name;</p>
          </list-item>
          <list-item>
            <p>I want a persistent identifier for the taxon (accepted name) corresponding to the name I provide;</p>
          </list-item>
          <list-item>
            <p>I want a persistent resolvable identifier for that taxon.</p>
          </list-item>
        </list></p>
        <p>Technical requirement - I want to (choose any):</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Enter or paste names into a web interface (usually limited number);</p>
          </list-item>
          <list-item>
            <p>Upload a list or table and receive the result as table or tables;</p>
          </list-item>
          <list-item>
            <p>Use OpenRefine as the name matching tool interface;</p>
          </list-item>
          <list-item>
            <p>Download an R package to perform name matching;</p>
          </list-item>
          <list-item>
            <p>Programme name matching using the aggregator's on-line API;</p>
          </list-item>
          <list-item>
            <p>Install the name matching service on my server;</p>
          </list-item>
          <list-item>
            <p>Download the data and perform matching within my own database.</p>
          </list-item>
        </list></p>
      </sec>
      <sec sec-type="Metadata to the rescue">
        <title><italic>Metadata</italic> to the rescue</title>
        <p>To identify the appropriate <italic>taxonomic dataset</italic> and <italic>name-matching service</italic> meeting user expectations, corresponding <italic>metadata</italic> for datasets and services must be defined.</p>
        <p><bold><italic>Metadata</italic> for <italic>taxonomic datasets</italic></bold>:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Dataset ID – a unique (in future preferably resolvable) identifier for the entire dataset, used to relate to services;</p>
          </list-item>
          <list-item>
            <p>Dataset title and version: For implementation, this may be divided into short title, full title and version;</p>
          </list-item>
          <list-item>
            <p>Dataset homepage URL;</p>
          </list-item>
          <list-item>
            <p>Dataset description: As text and/or (preferably) with a URL to a page on the dataset's website;</p>
          </list-item>
          <list-item>
            <p>Content: Organism group(s), nomenclatural code(s); thematic scope; geographic scope (regions and countries, as a delimited list or individual flags);</p>
          </list-item>
          <list-item>
            <p>IDs and data linkage: has stable name ID*; has stable resolvable name ID*; name ID attribute (column) name; name ID resolved at URI; name ID resolves to taxon*; name ID resolves to name*; name ID caveats and notes;</p>
          </list-item>
          <list-item>
            <p>Downloads and searches: Full download from dataset website possible*; partial download possible*; download website URL; download formats; query URL;</p>
          </list-item>
          <list-item>
            <p>Access conditions: Open access*; licence or licence waiver; access conditions;</p>
          </list-item>
          <list-item>
            <p>Programming: Has API*; API-documentation URL.</p>
          </list-item>
        </list></p>
        <p>* marks flags (Yes/No attributes).</p>
        <p><bold><italic>Metadata</italic> for <italic>name-matching services</italic></bold>:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Service ID: A unique identifier for the service (to be used to relate to datasets);</p>
          </list-item>
          <list-item>
            <p>Service name, version, supporting organisation or institution;</p>
          </list-item>
          <list-item>
            <p>Service description: As text and/or (preferably) a URL to a page on the service website;</p>
          </list-item>
          <list-item>
            <p>Service user interface features: Has direct matching interface*; direct matching interface URL; direct matching restriction (number of name records); direct matching is interactive*; file upload for matching possible*; file upload URL; file upload format(s);</p>
          </list-item>
          <list-item>
            <p>Service processing features: Nomenclatural code (specification to avoid homonyms issues etc.); matching-process description; matching-process parameters; matching input to multiple datasets possible*; ignore terms (a list of common non-nomenclatural additions to the name, for example, “sp.”, “aff.”);</p>
          </list-item>
          <list-item>
            <p>Service output features: Output includes input columns*; output includes candidates*; output includes aggregator's name ID*; output file format(s);</p>
          </list-item>
          <list-item>
            <p>Programming: API with public access*; API documentation URL; API endpoint URL; is R-package*; OpenRefine reconciliation interface*; OpenRefine reconciliation interface URL; OpenRefine documentation URL; local installation possible*.</p>
          </list-item>
        </list></p>
        <p>* marks flags (Yes/No attributes).</p>
        <p><bold><italic>Metadata</italic> for dataset/service combination</bold>:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Caveats and notes;</p>
          </list-item>
          <list-item>
            <p>Full name checked*;</p>
          </list-item>
          <list-item>
            <p>Output includes: Taxonomic status*, nomenclatural status*, classification*, persistent ID*; persistent resolvable ID*;</p>
          </list-item>
          <list-item>
            <p>Dataset can be downloaded from service provider*.</p>
          </list-item>
        </list></p>
        <p>* marks flags (Yes/No attributes).</p>
      </sec>
      <sec sec-type="Proof of concept">
        <title>Proof of concept</title>
        <p>Based on the <italic>metadata</italic> and user‑requirements described above, we have built a prototype web‑application that helps biodiversity‑data curators to select <italic>name‑matching services</italic> that best fit their particular needs. It is openly accessible at <ext-link ext-link-type="uri" xlink:href="https://cetaf-eu.github.io/CheckMyName/">https://cetaf-eu.github.io/CheckMyName/</ext-link>. A complete description of its architecture and usage is provided by <xref ref-type="bibr" rid="B13745307">Fichtmüller et al. (2025)</xref> .</p>
        <p>Tools that rely on <italic>metadata</italic> can become outdated rapidly because the underlying resources are continuously developed and their availability may change. One way to mitigate this problem is to enable community‑driven updating of the underlying tables (e.g. through a version‑controlled spreadsheet or a simple web‑form), but this often results in a rather patchy data coverage. Another, complementary approach is to involve data‑aggregators directly: if aggregators publish structured <italic>metadata</italic> about their <italic>taxonomic datasets</italic> and the <italic>name‑matching services</italic> they host, the guide could ingest this information automatically. At present, the <italic>metadata</italic> supplied by the Catalogue of Life’s ChecklistBank (<ext-link ext-link-type="uri" xlink:href="https://github.com/CatalogueOfLife/coldp/blob/master/README.md#metadata">see description on </ext-link><ext-link ext-link-type="uri" xlink:href="https://github.com/CatalogueOfLife/coldp/blob/master/README.md#metadata">github</ext-link>) are mainly directed at document-type properties (dataset name, authors and editors, rights, abstract etc.), but also describe the taxonomic, geographic and temporal scope of each dataset. For the datasets stored, these fields may be empty; additional details must be extracted from the free‑text descriptions. Global Names, by contrast, provides only a textual description of each dataset (see the “i” icons under <italic>Advanced options</italic> at <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">https://verifier.globalnames.org/</ext-link>).</p>
        <p>A more robust solution would be for repositories such as ChecklistBank and Global Names to add a lightweight API or adopt a machine‑readable <italic>metadata</italic> schema that documents the properties of the <italic>name‑matching service</italic>. Single-dataset services could do the same. This would allow the guide to incorporate new resources without manual intervention.</p>
      </sec>
      <sec sec-type="Outlook">
        <title>Outlook</title>
        <p>The fundamental technical infrastructure required for the proposed framework already exists. The main obstacles that must be addressed before the framework can achieve widespread adoption are:</p>
        <p><list list-type="order">
          <list-item>
            <p>Data availability – Important resources (e.g. country‑level checklists) are still missing from <italic>name‑matching services</italic>, at least in some cases caused by access restrictions imposed by data contributors. This is limiting the guide’s relevance for many users; </p>
          </list-item>
          <list-item>
            <p>Standardised <italic>metadata</italic> – No community‑agreed schema presently captures both the scope of a dataset and the characteristics of the associated matching service. Without such a standard, automatic aggregation and comparison of services remain difficult;</p>
          </list-item>
          <list-item>
            <p>Ongoing curation – Keeping metadata up to date demands a modest, but continuous editorial effort and close coordination with data providers;</p>
          </list-item>
          <list-item>
            <p>User awareness and uptake – Tools that are not widely known or perceived as useful are unlikely to be sustained.</p>
          </list-item>
        </list></p>
        <p>Addressing these points will require:</p>
        <p><list list-type="order">
          <list-item>
            <p>Outreach to national biodiversity agencies and other data owners to encourage deposition of their checklists as open data in platforms such as Catalogue of Life's ChecklistBank or Global Names;</p>
          </list-item>
          <list-item>
            <p>Development and endorsement of a community‑driven metadata standard (building on existing TDWG/GBIF specifications);</p>
          </list-item>
          <list-item>
            <p>Implementation of a simple, web‑based interface for community contributions and routine updates;</p>
          </list-item>
          <list-item>
            <p>Targeted promotion (e.g. tutorials, webinars, case‑study papers) to demonstrate the guide’s value to the different user communities.</p>
          </list-item>
        </list></p>
      </sec>
    </sec>
    <sec sec-type="Conclusions">
      <title>Conclusions</title>
      <p>We have identified the matching process for scientific organism names as the core element for integrating datasets containing <italic>scientific names</italic> of organisms across the internet and for enabling science-based semantic linking of organism-related data. We found wide variation in user requirements as well as in the offered functionalities for this process. As a consequence, a single, universally applicable workflow does not exist, but rather a number of approaches that depend on the specific user interest. We posit that the basic technical mechanisms are essentially there, the necessary base data for taxon names and their interrelations are also becoming increasingly available (though with strong differences amongst organism groups and, in many cases, with questionable sustainability). Therefore, the biodiversity informatics infrastructure seems to be ready for a unified approach. Building on existing infrastructures to implement a user-centric approach to name matching can help to improve <italic>data linkage</italic> in biodiversity science and thus to address major problems in biodiversity research and conservation.</p>
    </sec>
    <sec sec-type="Appendix 1: General recommendations for specific taxonomic groups">
      <title>Appendix 1: General recommendations for specific <italic>taxonomic groups</italic></title>
      <p>Some general recommendations can be given for specific <italic>taxonomic groups.</italic> Our focus here is on high-level organism groups (such as plants or animals) and, with respect to geographical representation, we focus on global coverage. A wider scope of sources is covered by Grenié &amp; al. (2022).</p>
      <p>Checking the names of animals</p>
      <p>Although the zoological code of nomenclature (<xref ref-type="bibr" rid="B13719216">ICZN 1999</xref>) governs the application of names of animals, the vast zoological domain has resulted in multiple sub-communities treating specific taxa, some of them with comparatively huge species numbers, some of them of specific interest to the public (e.g. groups of vertebrates). Therefore, if users are interested specifically in, for example, fishes or birds, they are probably best served using bird or fish specific datasets. For example, name matching via <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/">Catalogue of Life’s ChecklistBank</ext-link> or <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">Global Names Verifier</ext-link> is possible whenever the respective datasets have been deposited there, for example, FishBase (<xref ref-type="bibr" rid="B13718294">Froese and Pauly 2025</xref>), <xref ref-type="bibr" rid="B13718358">HBW and BirdLife International (2024)</xref> or the IOC World Bird List (<xref ref-type="bibr" rid="B13718310">Gill et al. 2025</xref>).</p>
      <p>Checking the names of plants</p>
      <p>Measured by species numbers, plants are a comparatively small group. However, even here specialised datasets exist, for example, for vascular plants, ferns and fern-allies and mosses (in the wide sense). <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name> and partly also algae, although mostly covered by the same code of nomenclature (in the past: the “botanical” code), are not considered plants here. Fortunately, botanical institutions have formed the World Flora Online (WFO) initiative (<xref ref-type="bibr" rid="B13718802">Wyse Jackson and Miller 2015</xref>, <xref ref-type="bibr" rid="B13717682">Borsch et al. 2020</xref>) that is incorporating various of these individual datasets (as the result of the work of Taxonomic Expert Networks). The<ext-link ext-link-type="uri" xlink:href="https://wfoplantlist.org/"> WFO Plant List</ext-link> is increasingly becoming the normative source for a consensus classification of all plant names, closely collaborating with initiatives like the International Plant Name Index (<xref ref-type="bibr" rid="B13718455">IPNI 2000</xref>), the World Checklist of Vascular Plants (<xref ref-type="bibr" rid="B13718318">Govaerts et al. 2021</xref>) and Bryonames (<xref ref-type="bibr" rid="B13717724">Brinda and Atwood 2025</xref>). As it is providing stable and resolvable name IDs also for orthographic variants of names and other invalid designations used in a taxonomic context, we recommend using that dataset for plant name matching.</p>
      <p>Checking the names of fungi</p>
      <p>The mycological community has been building <italic>scientific name</italic> resources for decades and, since 1 January 2013, is requiring registration of new names (<xref ref-type="bibr" rid="B13718671">Turland et al. 2025</xref>). The registration identifier used by the three recognised registration centres for new names: <ext-link ext-link-type="uri" xlink:href="https://www.indexfungorum.org/">IF</ext-link> (<xref ref-type="bibr" rid="B13718463">Index Fungorum 2009-</xref>), <ext-link ext-link-type="uri" xlink:href="https://www.mycobank.org/">MycoBank</ext-link> (<xref ref-type="bibr" rid="B13718002">Crous et al. 2004</xref>) and <ext-link ext-link-type="uri" xlink:href="https://nmdc.cn/fungalnames/">Fungal Names</ext-link> (<xref ref-type="bibr" rid="B13718704">Wang et al. 2022</xref>) has also been applied to all pre-existing names, so that a consistent <italic>name ID</italic> exists for all fungal names. The repositories continuously synchronise their name holdings so that name matching against any of the repositories gives the same results in terms of name and identifier, with the exception of potentially different instances of taxon concepts and classifications of the names. The International Commission on the Taxonomy of <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name> (ICTF) is working on a consensus classification to be adopted by the three repositories. For name matching, Index Fungorum and Mycobank are available through <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/">Catalogue of Life’s ChecklistBank</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">Global Names Verifier</ext-link>; Fungal Names only through Global Names.</p>
      <p>Checking the names of eukaryotic algae</p>
      <p>AlgaeBase (<xref ref-type="bibr" rid="B13719245">Guiry and Guiry 2025</xref>) is integrated into the <ext-link ext-link-type="uri" xlink:href="https://www.marinespecies.org/">World Register of Marine Species</ext-link> (<xref ref-type="bibr" rid="B13719253">WoRMS Editorial Board 2025</xref>), with the exception of diatoms, which are managed in <ext-link ext-link-type="uri" xlink:href="https://www.diatombase.org/">DiatomBase</ext-link> (<xref ref-type="bibr" rid="B13719261">Kociolek et al. 2025</xref>), also part of WoRMS/Aphia. Integration into WoRMS is made possible by the payment of an annual access fee by Lifewatch Flanders to support the content development within AlgaeBase. The dataset is not available for download through WoRMS due to licence conditions, but it can be queried through the WoRMS API. The AlgaeBase website does not offer a <italic>name matching service</italic>, but this is available in the context of the <ext-link ext-link-type="uri" xlink:href="https://www.lifewatch.be/e-lab/">LifeWatch eLab TaxonMatch services</ext-link>. The service is currently restricted to exact matches due to the design of the AlgaeBase API. AlgaeBase is also available in an outdated version through <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">Global Names Verifier</ext-link>. <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="above-family">Algae</tp:taxon-name-part></tp:taxon-name> are presently only incompletely covered by Catalogue of Life, because only data sources with either a CC-0 or CC-BY data license can be integrated. Further sources for algal names: <ext-link ext-link-type="uri" xlink:href="http://www.phycobank.org">Phycobank</ext-link> (<xref ref-type="bibr" rid="B13719285">Kusber et al. 2019</xref>) is a recognised repository for the registration of new names (not yet obligatory); <ext-link ext-link-type="uri" xlink:href="https://www.algaterra.org/">AlgaTerra</ext-link> focuses on eukaryotic micro-algae; <ext-link ext-link-type="uri" xlink:href="https://ucjeps.berkeley.edu/INA.html">Index Nominum Algarum</ext-link> is a nomenclator comprising &gt; 200,000 algal names compiled from index cards; the <ext-link ext-link-type="uri" xlink:href="https://researcharchive.calacademy.org/research/diatoms/names/index.asp">Catalogue of Diatom Names</ext-link> is a database not updated since 2011, but since 2018, it has been transformed into DiatomBase (see above). Of the latter resources, both DiatomBase (via its own Aphia matching service) and Index Nominum Algarum (through <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/">Catalogue of Life’s ChecklistBank</ext-link>) are currently accessible for name matching.</p>
      <p>Checking the names of cyanobacteria (blue-green algae)</p>
      <p><tp:taxon-name><tp:taxon-name-part taxon-name-part-type="phylum">Cyanobacteria</tp:taxon-name-part></tp:taxon-name> present a special case because they have traditionally been treated as algae and their name, thus, was governed by the International Code of Nomenclature for <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="above-family">Algae</tp:taxon-name-part></tp:taxon-name>, <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name> and Plants (ICNAFP, <xref ref-type="bibr" rid="B13718671">Turland et al. (2025)</xref>). However, they are prokaryotic organisms and thus, today, many cyanobacteria are named in accordance with the rules of the International Code of Nomenclature of Prokaryotes (ICNP, <xref ref-type="bibr" rid="B13718555">Parker et al. (2019)</xref>). This dual treatment may result in some names being valid under ICNAFP and not under ICNP. As a consequence, the choice of dataset (and related service) may depend on your research context. The <ext-link ext-link-type="uri" xlink:href="https://lpsn.dsmz.de">LPSN (List of Prokaryotic names with Standing in Nomenclature)</ext-link> covers validly published names of cyanobacteria under the ICNP. This is most useful in a prokaryote-microbiological context and it is available in <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/">Catalogue of Life’s ChecklistBank</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">Global Names Verifier</ext-link>. AlgaeBase (see above) covers cyanobacterial names published under the ICNAFP in a phycological/botanical context, relevant, for example, for ecological research. <ext-link ext-link-type="uri" xlink:href="https://www.ncbi.nlm.nih.gov/taxonomy">NCBI Taxonomy</ext-link> (National Center for Biotechnology Information) includes (under bacteria) cyanobacterial names covered by ICNP and ICNAFP, but does not provide an accepted name for synonyms and does not claim to be an authoritative source for nomenclature or classification.</p>
      <p>Checking names of Virus and Viroids</p>
      <p>The internationally agreed dataset is the<ext-link ext-link-type="uri" xlink:href="https://ictv.global/taxonomy"> ICTV Master Species List</ext-link> (ICTV 2024) that provides the current taxonomic status of viral names and their classification. The website allows searching for individual viral names, but apparently, there is no bulk upload possible for name checking. No API is offered for machine access to the database at the ICTV website, but the dataset is included in <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/">Catalogue of Life’s ChecklistBank</ext-link>, <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/">Global Names Verifier</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://www.marinespecies.org/">WoRMS</ext-link> (marine only).</p>
    </sec>
    <sec sec-type="Appendix 2: Online name-matching services">
      <title>Appendix 2: Online <italic>name-matching services</italic></title>
      <p>Services may provide application programming interfaces (APIs) that often extend the possibilities of name matching or include further functions not provided by the interactive sites. This is also true for the R-packages listed in <xref ref-type="bibr" rid="B13718347">Grenié et al. (2022)</xref>, see also Appendix 4. Undoubtedly these provide methods that can be highly useful for technically versed users; however, we refrained from testing anything that requires programming on the user’s side, with the sole exception of some simple coding used in the context of OpenRefine (see Appendix 3).</p>
      <p>We distinguish between <italic>name-matching services</italic> that act upon repositories of <italic>taxonomic datasets</italic> and single-dataset services. The unfiltered user interface of the prototype https://cetaf-eu.github.io/CheckMyName/ provides a simplified table of service properties given in detail below.</p>
      <sec sec-type="Repository services">
        <title>Repository services</title>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/tools/name-match"><underline>Checklist Bank (GBIF &amp; Catalogue of Life)</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: All taxa or specific groups depending on the target dataset chosen. <bold>Geographic scope</bold>: Global or specific areas, depending on the target dataset chosen. <bold>Software updated</bold>: current (last checked 26 September 2025). <bold>Codebase/Documentation</bold>: <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/about/API"><underline>https://www.checklistbank.org/about/API</underline></ext-link>. <bold>Data updated</bold>: depending on target dataset. <bold>Limitation</bold>: Direct input of list limited to 6000 names (with file upload for asynchronous response not limited). <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES - in download only. <bold>Interactive mode for partial matches</bold>: NO. <bold>OpenRefine reconciliation API</bold>: NO (but for OpenRefine possible with REST services). <bold>Other</bold>: Login with GBIF account is recommended, required for file upload (self-registration at <ext-link ext-link-type="uri" xlink:href="https://www.gbif.org/user/profile"><underline>https://www.gbif.org/user/profile</underline></ext-link>). <bold>Other</bold>: Offers the possibility to match datasets in repository against other such datasets. <bold>Other</bold>: API available</p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/"><underline>Global Names Verifier</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: All taxa or specific groups depending on the target dataset chosen<bold>. Geographic scope</bold>: global (cross datasets or with global datasets) or restricted by choice of dataset. <bold>Software updated</bold>: current (last checked 26 September 2025)<bold>. Codebase/Documentation</bold>: <ext-link ext-link-type="uri" xlink:href="https://github.com/gnames"><underline>https://github.com/gnames</underline></ext-link> and <ext-link ext-link-type="uri" xlink:href="https://resolver.globalnames.org/api"><underline>https://resolver.globalnames.org/api</underline></ext-link><bold>. Data updated</bold>: Differs for stored datasets<bold>. Limitation</bold>: 5000 names, at least in interactive mode<bold>. Local ID input returned</bold>: NO<bold>. Local Name input returned</bold>: YES<bold>. Aggregator name ID returned</bold>: YES (may be a taxon ID)<bold>. Interactive mode for partial matches</bold>: NO<bold>. OpenRefine reconciliation API</bold>: YES, with step-by-step documentation including a video tutorial: <ext-link ext-link-type="uri" xlink:href="https://github.com/gnames/gnverifier/wiki/OpenRefine-readme"> <underline>https://github.com/gnames/gnverifier/wiki/OpenRefine-readme</underline></ext-link>. <bold>Other</bold>: Offers a kind of query language that seems to be very flexible<bold>. Other</bold>: API and R package available</p>
        <p><ext-link ext-link-type="uri" xlink:href="https://tnrs.biendata.org/"><underline>TNRS Taxonomic Name Resolution Service</underline> </ext-link> <bold>also</bold>: <ext-link ext-link-type="uri" xlink:href="http://tnrs.iplantcollaborative.org/"> <underline>http://tnrs.iplantcollaborative.org/</underline> </ext-link></p>
        <p><bold>Taxonomic scope</bold>: Plants, WFO; vascular plants WCVP - potentially more datasets could be included<bold>. Geographic scope</bold>: Global. <bold>Software updated</bold>: v. 5.0, 24 Feb 2021. <bold>Codebase/Documentation</bold>: <ext-link ext-link-type="uri" xlink:href="https://github.com/ojalaquellueva/TNRSapi"><underline>https://github.com/ojalaquellueva/TNRSapi</underline> </ext-link>and <ext-link ext-link-type="uri" xlink:href="https://github.com/iPlantCollaborativeOpenSource/TNRS/"> <underline>https://github.com/iPlantCollaborativeOpenSource/TNRS/</underline></ext-link>. <bold>Data updated</bold>: 2023/2024 [14 Dec 2025]<bold>. Limitation</bold>: Pasting 5000 names; API-processing unlimited (in batches of 5000). <bold>Local ID input returned</bold>: NO. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: NO<bold>. Interactive mode for partial matches</bold>: YES. <bold>OpenRefine reconciliation API</bold>: NO<bold>. Other</bold>: API and R package available.</p>
      </sec>
      <sec sec-type="Single-dataset name-matching services">
        <title>Single-dataset <italic>name-matching services</italic></title>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://www.anbg.gov.au/apni/"><underline>Australian Plant Name Index</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: Plants. <bold>Geographic scope</bold>: Australia. <bold>Software updated</bold>: ? <bold>Codebase/Documentation</bold>: ? <bold>Data updated</bold>: Current. <bold>Limitation</bold>: result set limited to 100 matches, large uploads (1000 names) now blocked by Cloudflare [14 Dec 2025]: check with nearly 21,000 names ended in server error [May 2024]. <bold>Local ID input returned</bold>: NO. <bold>Local Name input returned</bold>: NO. <bold>Aggregator name ID returned</bold>: NO. <bold>Interactive mode for partial matches</bold>: NO. <bold>OpenRefine reconciliation API</bold>: NO. <bold>Other</bold>: <ext-link ext-link-type="uri" xlink:href="https://www.biorxiv.org/content/10.1101/2024.02.02.578715v1"><underline>APCalign: an R package workflow and app for aligning and updating flora names to the Australian Plant Census</underline> </ext-link></p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://www.gbif.org/tools/species-lookup"><underline>GBIF Taxonomic Backbone</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: All taxa. <bold>Geographic scope</bold>: global. <bold>Software updated</bold>: current. <bold>Codebase/Documentation</bold>: see <ext-link ext-link-type="uri" xlink:href="https://www.gbif.org/developer/species"> <underline>Species API</underline></ext-link>. <bold>Data updated</bold>: 28 August 2023 (no further updates, but will stay online; superseded by COL eXtended Release). <bold>Limitation</bold>: 6000 records. <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: NO. <bold>Interactive mode for partial matches</bold>: NO. <bold>OpenRefine reconciliation API</bold>: NO. <bold>Other</bold>: "Multi-taxonomy" mode available - allows to match against other, selected taxonomies (currently only the COL eXtended Release). <bold>Other</bold>: Matching Service including data is downloadable as a Docker image. <bold>Other</bold>: API available</p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="http://namematch.science.kew.org/"><underline>International Plant Name Index (IPNI)</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: Vascular plants (source: POWO; IPNI offered but not working). <bold>Geographic scope</bold>: Global. Software updated: ? <bold>Codebase/Documentation</bold> ? <bold>Data updated</bold>: current. <bold>Limitation</bold>: Not found - tested with 144.000 records. <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES: IPNI-LSID. <bold>Interactive mode for partial matches</bold>: NO. <bold>OpenRefine reconciliation API</bold>: YES - documentation: <ext-link ext-link-type="uri" xlink:href="https://data1.kew.org/reconciliation/help"> <underline>https://data1.kew.org/reconciliation/help</underline></ext-link>.</p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://www.eu-nomen.eu/portal/taxamatch.php"><underline>PESI / EU-nomen</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: All taxa. <bold>Geographic scope</bold>: Europe. <bold>Software updated</bold>: 2025. <bold>Codebase/Documentation</bold>: By reference to components used (Taxamatch algorithm and scientific name parser). <bold>Data updated</bold>: 2014 (update under way). <bold>Limitation</bold>: 1,000 names. <bold>Local ID input returned</bold>: YES (as an “extra” non-mapped column). <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES (as provided by the primary aggregator). <bold>Interactive mode for partial matches</bold>: YES. <bold>OpenRefine reconciliation API</bold>: YES, via REST, see <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3897/BDJ.2.e4221">https://doi.org/10.3897/BDJ.2.e4221</ext-link>.</p>
        <p>
          <bold>
            <xref ref-type="bibr" rid="B13718663">TROPICOS (1986-)</xref>
          </bold>
        </p>
        <p><bold>Taxonomic scope</bold>: Plants. <bold>Geographic scope</bold>: Global. <bold>Software updated</bold>: Name matching more than 10 years ago. <bold>Codebase/Documentation</bold>: No. <bold>Data updated</bold>: Current. <bold>Limitation</bold>: File size cannot exceed 2,048,576 KB. <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES: Tropicos-ID. <bold>Interactive mode for partial matches</bold>: NO. <bold>OpenRefine reconciliation API</bold>: NO.</p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/matching.php"><underline>World Flora Online WFO Plant List</underline> </ext-link>
        </p>
        <p><bold>Taxonomic scope</bold>: Plants. <bold>Geographic scope</bold>: Global. <bold>Software updated</bold>: ongoing October 2025 (not stated on website). <bold>Codebase/Documentation</bold>: <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/gql_index.php"> <underline>GraphQL API</underline></ext-link>, <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/matching_rest.php"> <underline>Name Matching REST API</underline></ext-link>, <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/reconcile_index.php"> <underline>Reconciliation API</underline></ext-link>. <bold>Data updated</bold>: June 2025 (semi-annual edition). <bold>Limitation</bold>: Not found - tested with 144.000 records. <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES: WFO-ID. <bold>Interactive mode for partial matches</bold>: YES. <bold>OpenRefine reconciliation API</bold>: YES: <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/reconcile_index.php"> <underline>https://list.worldfloraonline.org/reconcile_index.php</underline></ext-link>. <bold>Other</bold>: Service can be installed as local copy. <bold>Other</bold>: R-Package World Flora - see <ext-link ext-link-type="uri" xlink:href="https://cran.r-project.org/web/packages/WorldFlora/index.html"> <underline>https://cran.r-project.org/web/packages/WorldFlora/index.html</underline></ext-link>. <bold>Other</bold>: API available.</p>
        <p>
          <ext-link ext-link-type="uri" xlink:href="https://www.marinespecies.org/aphia.php?p=match"><underline>WoRMS (World Register of Marine Species)</underline> </ext-link>
        </p>
        <p><bold>Scope</bold>: Marine species (global). <bold>Software updated</bold>: daily basis. <bold>Codebase/Documentation</bold>: in-house. <bold>Data updated</bold>: current. <bold>Limitation</bold>: limited to 1500 names. <bold>Local ID input returned</bold>: YES. <bold>Local Name input returned</bold>: YES. <bold>Aggregator name ID returned</bold>: YES: AphiaID. <bold>Interactive mode for partial matches</bold>: YES. <bold>OpenRefine reconciliation API</bold>: See Appendix 3. <bold>Other</bold>: API available.</p>
      </sec>
    </sec>
    <sec sec-type="Appendix 3: OpenRefine reconciliation interfaces">
      <title>Appendix 3: OpenRefine reconciliation interfaces</title>
      <p><ext-link ext-link-type="uri" xlink:href="https://openrefine.org/">OpenRefine</ext-link> is a powerful desktop application for cleaning and transforming data. A <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/OpenRefine">concise overview</ext-link> is available on Wikipedia. <xref ref-type="bibr" rid="B13718546">Mozzherin et al. (2024)</xref> present a compelling case for adopting OpenRefine reconciliation as a standard approach for <italic>name-matching services</italic>.</p>
      <p>In the context of name matching, OpenRefine’s key feature is the ability to connect to external reconciliation services, i.e. APIs that match data entries against external sources. A reconciliation service can be used to match a column of <italic>scientific names</italic> in a table against the taxonomy provided by an aggregator service. The reconciliation services conform to the <ext-link ext-link-type="uri" xlink:href="https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.2-20230410/">Reconciliation Service API</ext-link>, a specification developed by the W3C community.</p>
      <p>Users normally install OpenRefine locally; installation packages are available for major operating systems, including a straightforward installer for Windows. Once installed, the desired name-matching service can be configured and connected to OpenRefine for repeated use.</p>
      <p>To perform name matching, users load their tabular data into OpenRefine and initiate the reconciliation process on the column containing <italic>scientific names</italic>. In an additional new column, the service returns either exact matches or, when no exact match is found, a list of possible candidates (if any). Users can then review and select the appropriate match for each entry. Once reconciliation is complete, the enriched dataset including the new column containing the matched results can be exported for further use.</p>
      <p>The following name-matching reconciliation services are available:</p>
      <p>Global Names Verifier:</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Datasets: covering all datasets that have been imported into Global Names;</p>
        </list-item>
        <list-item>
          <p>Homepage (including an excellent step-by-step documentation for OpenRefine and a video tutorial): <ext-link ext-link-type="uri" xlink:href="https://github.com/gnames/gnverifier/wiki/OpenRefine-readme">https://github.com/gnames/gnverifier/wiki/OpenRefine-readme;</ext-link> </p>
        </list-item>
        <list-item>
          <p>OpenRefine reconciliation endpoint: <ext-link ext-link-type="uri" xlink:href="https://verifier.globalnames.org/api/v1/reconcile">https://verifier.globalnames.org/api/v1/reconcile.</ext-link> </p>
        </list-item>
      </list></p>
      <p>International Plant Name Index (IPNI):</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Dataset: IPNI;</p>
        </list-item>
        <list-item>
          <p>Homepage: <ext-link ext-link-type="uri" xlink:href="https://data1.kew.org/reconciliation/about/IpniName">https://data1.kew.org/reconciliation/about/IpniName; </ext-link></p>
        </list-item>
        <list-item>
          <p>OpenRefine reconciliation endpoint: <ext-link ext-link-type="uri" xlink:href="http://data1.kew.org/reconciliation/reconcile/IpniName">http://data1.kew.org/reconciliation/reconcile/IpniName.</ext-link></p>
        </list-item>
      </list></p>
      <p>Wikidata Reconciliation Service:</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Datasets: the entirety of Wikidata, but can be restricted to items that are instances of (P31) Taxon (Q16521) for better matches and faster processing;</p>
        </list-item>
        <list-item>
          <p>Homepage: <ext-link ext-link-type="uri" xlink:href="https://wikidata.reconci.link/">https://wikidata.reconci.link/; </ext-link></p>
        </list-item>
        <list-item>
          <p>OpenRefine reconciliation endpoint: <ext-link ext-link-type="uri" xlink:href="https://wikidata.reconci.link/en/api">https://wikidata.reconci.link/en/api. </ext-link></p>
        </list-item>
      </list></p>
      <p>World Flora Online:</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Dataset: WFO Plant List (latest semiannual version);</p>
        </list-item>
        <list-item>
          <p>Homepage: <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/reconcile_index.php">https://list.worldfloraonline.org/reconcile_index.php;</ext-link> </p>
        </list-item>
        <list-item>
          <p>OpenRefine reconciliation endpoint: <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/reconcile">https://list.worldfloraonline.org/reconcile.</ext-link></p>
        </list-item>
      </list></p>
      <p>Indirect access:</p>
      <p>Catalogue of Life ChecklistBank:</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Developers recognised the need to implement a reconciliation API, but it is not yet available (see <ext-link ext-link-type="uri" xlink:href="https://github.com/CatalogueOfLife/backend/issues/1265">https://github.com/CatalogueOfLife/backend/issues/1265</ext-link>). Access can be implemented programmatically using the API.</p>
        </list-item>
      </list></p>
      <p>WoRMS:</p>
      <p><list list-type="bullet">
        <list-item>
          <p>Dataset: current;</p>
        </list-item>
        <list-item>
          <p>Homepage: <ext-link ext-link-type="uri" xlink:href="https://github.com/SIB-Colombia/data-quality-open-refine"><underline>https://github.com/SIB-Colombia/data-quality-open-refine;</underline></ext-link></p>
        </list-item>
        <list-item>
          <p>OpenRefine instructions: <ext-link ext-link-type="uri" xlink:href="https://github.com/SIB-Colombia/data-quality-open-refine/blob/master/ValTaxonomicAPIWoRMS_ValTaxonomicaAPIWoRMS.txt"><underline>https://github.com/SIB-Colombia/data-quality-open-refine/blob/master/ValTaxonomicAPIWoRMS_ValTaxonomicaAPIWoRMS.txt.</underline></ext-link></p>
        </list-item>
      </list></p>
    </sec>
    <sec sec-type="Appendix 4: Programming tools for name matching">
      <title>Appendix 4: Programming tools for name matching</title>
      <sec sec-type="R-packages">
        <title>R-packages</title>
        <p>R packages are prepackaged collections of code, data and documentation that extend the functionality of the R programming language. <xref ref-type="bibr" rid="B13718347">Grenié et al. (2022)</xref> cover this subject in detail, identifying 59 packages providing direct access to online taxonomic databases. They also point to an application (<ext-link ext-link-type="uri" xlink:href="https://mgrenie.shinyapps.io/taxharmonizexplorer/">taxharmonizeexplorer</ext-link>) that should aid R-users to select tools and datasets. The website for the app lists and graphically depicts the relationship between taxonomic datasets and R-packages (as of end of November 2025, it covers 68 packages and 53 datasets). If this tool continues to be updated, it should be the primary source for R-programmers to identify useful packages for name matching and apply these in a workflow detailed in Grenié &amp; al.’s paper.</p>
      </sec>
      <sec sec-type="Application programming interfaces (APIs)">
        <title>Application programming interfaces (APIs)</title>
        <p>The following <italic>name-matching services</italic> offer a publicly accessible API:</p>
        <p><list list-type="bullet">
          <list-item>
            <p>Catalogue of Life’s ChecklistBank Name Match - <ext-link ext-link-type="uri" xlink:href="https://www.checklistbank.org/about/API">https://www.checklistbank.org/about/API</ext-link>;</p>
          </list-item>
          <list-item>
            <p>GBIF Species Matcher - <ext-link ext-link-type="uri" xlink:href="https://techdocs.gbif.org/en/openapi/v1/species">https://techdocs.gbif.org/en/openapi/v1/species;</ext-link> </p>
          </list-item>
          <list-item>
            <p>Global Names Verifier - <ext-link ext-link-type="uri" xlink:href="https://resolver.globalnames.org/api">https://resolver.globalnames.org/api;</ext-link> </p>
          </list-item>
          <list-item>
            <p>Taxonomic Name Resolution Service (TNRS) - <ext-link ext-link-type="uri" xlink:href="https://github.com/ojalaquellueva/TNRSapi?tab=readme-ov-file#readme">https://github.com/ojalaquellueva/TNRSapi?tab=readme-ov-file#readme;</ext-link> </p>
          </list-item>
          <list-item>
            <p>World Flora Online Plant List - <ext-link ext-link-type="uri" xlink:href="https://list.worldfloraonline.org/matching_rest.php">https://list.worldfloraonline.org/matching_rest.php;</ext-link> </p>
          </list-item>
          <list-item>
            <p>WoRMS Taxon Match - <ext-link ext-link-type="uri" xlink:href="https://www.marinespecies.org/aphia.php?p=webservice">https://www.marinespecies.org/aphia.php?p=webservice. </ext-link></p>
          </list-item>
        </list></p>
      </sec>
      <sec sec-type="Others">
        <title>Others</title>
        <p><list list-type="bullet">
          <list-item>
            <p>Pytaxon: A Python software package for the identification and correction of errors in the taxonomic data of biodiversity species (<xref ref-type="bibr" rid="B13718564">Proença Neto and De Sousa 2025</xref>) - <ext-link ext-link-type="uri" xlink:href="https://github.com/pytaxon/pytaxon-cli">https://github.com/pytaxon/pytaxon-cli</ext-link> and <ext-link ext-link-type="uri" xlink:href="https://zenodo.org/records/14538804"> <underline>https://zenodo.org/records/14538804.</underline></ext-link></p>
          </list-item>
        </list></p>
      </sec>
    </sec>
  </body>
  <back>
    <ack>
      <title>Acknowledgements</title>
      <p>We are thankful to Donald Hobern for the thorough review and constructive feedback. The publication was supported by Open Access Funds of Freie Universität Berlin.</p>
    </ack>
    <sec sec-type="Conflicts of interest">
      <title>Conflicts of interest</title>
      <p>Although we do not see a direct conflict of interest, it should be mentioned that some of the authors are directly involved in the services and datasets mentioned and analysed in this paper: Bánki and Döring in Catalogue of Life ChecklistBank, Hyam in World Flora Online Plant List, Müller in EU-nomen/PESI and Vanhoorne in WoRMS/Aphia and EU-nomen/PESI.</p>
      <p>I want to declare a conflict of interest</p>
      <p>Disclaimer: This article is (co-)authored by any of the Editors-in-Chief, Managing Editors or their deputies in this journal.</p>
    </sec>
    <ref-list>
      <title>References</title>
      <ref id="B13723662">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bánki</surname>
              <given-names>Olaf</given-names>
            </name>
            <name name-style="western">
              <surname>Hobern</surname>
              <given-names>Donald</given-names>
            </name>
            <name name-style="western">
              <surname>Döring</surname>
              <given-names>Markus</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Building on the functionalities of GBIF-COL ChecklistBank</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>7</volume>
          <issue>e111668</issue>
          <pub-id pub-id-type="doi">10.3897/biss.7.111668</pub-id>
        </element-citation>
      </ref>
      <ref id="B13749878">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bánki</surname>
              <given-names>O.</given-names>
            </name>
            <name name-style="western">
              <surname>Roskov</surname>
              <given-names>Y.</given-names>
            </name>
            <name name-style="western">
              <surname>Döring</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ower</surname>
              <given-names>G.</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez</surname>
              <given-names>D.</given-names>
            </name>
            <name name-style="western">
              <surname>Plata</surname>
              <given-names>C.</given-names>
            </name>
            <etal/>
          </person-group>
          <year>2025</year>
          <article-title>Catalogue of Life</article-title>
          <publisher-name>Catalogue of Life Foundation, Amsterdam, The Netherlands</publisher-name>
          <pub-id pub-id-type="doi">10.48580/dgvbl</pub-id>
          <comment content-type="Version">2025-11-16-XR</comment>
        </element-citation>
      </ref>
      <ref id="B13717226">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Use cases for scientific name identifiers and name matching: Progress report from the TETTRIs project</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>7</volume>
          <pub-id pub-id-type="doi">10.3897/biss.7.109666</pub-id>
        </element-citation>
      </ref>
      <ref id="B13723771">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
          </person-group>
          <article-title>Wish list for name-matching services</article-title>
          <uri>https://wiki.bgbm.org/tettriswiki/index.php/Wish_list_for_name_matching_services</uri>
          <date-in-citation content-type="access-date">2025-11-30T00:48:11+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13717263">
        <element-citation publication-type="conference-preoceeding">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <source>Harmonizing dynamic botanical knowledge at the source: infrastructures for resolvable IDs and taxon concept subscriptions. In: Book of Abstracts. Oral Presentations</source>
          <conf-name>XX International Botanical Congress</conf-name>
          <conf-loc>Madrid</conf-loc>
          <conf-date>July 21st - 27th, 2024</conf-date>
          <publisher-name>Fase 20 Ediciones</publisher-name>
          <publisher-loc>Madrid</publisher-loc>
          <uri>https://ibcmadrid2024.com/index.php?seccion=scientificArea&amp;subSeccion=detailAbstract&amp;id=1558</uri>
          <isbn>ISBN: 978-84-09-63655-6</isbn>
        </element-citation>
      </ref>
      <ref id="B13717362">
        <element-citation publication-type="conference-paper">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
            <name name-style="western">
              <surname>Döring</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Dillen</surname>
              <given-names>Mathias</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <person-group person-group-type="editor">
            <anonymous/>
          </person-group>
          <article-title>Globally Linking Taxonomies: Use cases and latest developments</article-title>
          <source>Session Abstracts</source>
          <conf-name>TDWG 2024</conf-name>
          <conf-loc>Okinawa</conf-loc>
          <conf-date>2-6 September 2024</conf-date>
          <publisher-name>tdwg.org</publisher-name>
          <uri>https://www.tdwg.org/conferences/2024/sessions/#sym18</uri>
        </element-citation>
      </ref>
      <ref id="B13717505">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter</given-names>
            </name>
            <name name-style="western">
              <surname>Lusa Bernal</surname>
              <given-names>Silvia</given-names>
            </name>
            <name name-style="western">
              <surname>Falcón Hidalgo</surname>
              <given-names>Banessa</given-names>
            </name>
            <name name-style="western">
              <surname>Rodríguez Delcid</surname>
              <given-names>Dagoberto</given-names>
            </name>
            <name name-style="western">
              <surname>Moonlight</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Engledow</surname>
              <given-names>Henry</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Enhancing herbarium systems using name matching mechanisms</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>8</volume>
          <pub-id pub-id-type="doi">10.3897/biss.8.137867</pub-id>
        </element-citation>
      </ref>
      <ref id="B13717525">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>BHL</surname>
            </name>
          </person-group>
          <article-title>Biodiversity Heritage Library</article-title>
          <uri>https://www.biodiversitylibrary.org</uri>
          <date-in-citation content-type="access-date">2025-09-26T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13717620">
        <element-citation publication-type="book">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Bisby</surname>
              <given-names>Frank A.</given-names>
            </name>
            <name name-style="western">
              <surname>Russell</surname>
              <given-names>G. F.</given-names>
            </name>
            <name name-style="western">
              <surname>Pankhurst</surname>
              <given-names>Richard J.</given-names>
            </name>
          </person-group>
          <year>1994</year>
          <source>Designs for a Global Plant Species Information System</source>
          <publisher-name>Oxford Academic Press</publisher-name>
          <publisher-loc>Oxford</publisher-loc>
          <pub-id pub-id-type="doi">10.1093/oso/9780198577607.001.0001</pub-id>
        </element-citation>
      </ref>
      <ref id="B13717682">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Borsch</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter</given-names>
            </name>
            <name name-style="western">
              <surname>Dalcin</surname>
              <given-names>Eduardo</given-names>
            </name>
            <name name-style="western">
              <surname>Delmas</surname>
              <given-names>Maïté</given-names>
            </name>
            <name name-style="western">
              <surname>Demissew</surname>
              <given-names>Sebsebe</given-names>
            </name>
            <name name-style="western">
              <surname>Elliott</surname>
              <given-names>Alan</given-names>
            </name>
            <name name-style="western">
              <surname>Fritsch</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Fuchs</surname>
              <given-names>Anne</given-names>
            </name>
            <name name-style="western">
              <surname>Geltman</surname>
              <given-names>Dmitry</given-names>
            </name>
            <name name-style="western">
              <surname>Güner</surname>
              <given-names>Adil</given-names>
            </name>
            <name name-style="western">
              <surname>Haevermans</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Knapp</surname>
              <given-names>Sandra</given-names>
            </name>
            <name name-style="western">
              <surname>le Roux</surname>
              <given-names>M. Marianne</given-names>
            </name>
            <name name-style="western">
              <surname>Loizeau</surname>
              <given-names>Pierre‐André</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Chuck</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>James</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Joseph T.</given-names>
            </name>
            <name name-style="western">
              <surname>Palese</surname>
              <given-names>Raoul</given-names>
            </name>
            <name name-style="western">
              <surname>Paton</surname>
              <given-names>Alan</given-names>
            </name>
            <name name-style="western">
              <surname>Parnell</surname>
              <given-names>John</given-names>
            </name>
            <name name-style="western">
              <surname>Pendry</surname>
              <given-names>Colin</given-names>
            </name>
            <name name-style="western">
              <surname>Qin</surname>
              <given-names>Hai‐Ning</given-names>
            </name>
            <name name-style="western">
              <surname>Sosa</surname>
              <given-names>Victoria</given-names>
            </name>
            <name name-style="western">
              <surname>Sosef</surname>
              <given-names>Marc</given-names>
            </name>
            <name name-style="western">
              <surname>von Raab‐Straube</surname>
              <given-names>Eckhard</given-names>
            </name>
            <name name-style="western">
              <surname>Ranwashe</surname>
              <given-names>Fhatani</given-names>
            </name>
            <name name-style="western">
              <surname>Raz</surname>
              <given-names>Lauren</given-names>
            </name>
            <name name-style="western">
              <surname>Salimov</surname>
              <given-names>Rashad</given-names>
            </name>
            <name name-style="western">
              <surname>Smets</surname>
              <given-names>Erik</given-names>
            </name>
            <name name-style="western">
              <surname>Thiers</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>Wayt</given-names>
            </name>
            <name name-style="western">
              <surname>Tulig</surname>
              <given-names>Melissa</given-names>
            </name>
            <name name-style="western">
              <surname>Ulate</surname>
              <given-names>William</given-names>
            </name>
            <name name-style="western">
              <surname>Ung</surname>
              <given-names>Visotheary</given-names>
            </name>
            <name name-style="western">
              <surname>Watson</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>Jackson</surname>
              <given-names>Peter Wyse</given-names>
            </name>
            <name name-style="western">
              <surname>Zamora</surname>
              <given-names>Nelson</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>World Flora Online: Placing taxonomists at the heart of a definitive and comprehensive global resource on the world's plants</article-title>
          <source>Taxon</source>
          <volume>69</volume>
          <issue>6</issue>
          <fpage>1311</fpage>
          <lpage>1341</lpage>
          <pub-id pub-id-type="doi">10.1002/tax.12373</pub-id>
        </element-citation>
      </ref>
      <ref id="B13717724">
        <element-citation publication-type="website">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Brinda</surname>
              <given-names>J. C.</given-names>
            </name>
            <name name-style="western">
              <surname>Atwood</surname>
              <given-names>J. J.</given-names>
            </name>
          </person-group>
          <article-title>The Bryophyte Nomenclator</article-title>
          <uri>https://www.bryonames.org/</uri>
          <date-in-citation content-type="access-date">2025-10-29T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13717772">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chamanara</surname>
              <given-names>Javad</given-names>
            </name>
            <name name-style="western">
              <surname>Gaikwad</surname>
              <given-names>Jitendra</given-names>
            </name>
            <name name-style="western">
              <surname>Gerlach</surname>
              <given-names>Roman</given-names>
            </name>
            <name name-style="western">
              <surname>Algergawy</surname>
              <given-names>Alsayed</given-names>
            </name>
            <name name-style="western">
              <surname>Ostrowski</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>König-Ries</surname>
              <given-names>Birgitta</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>BEXIS2: A FAIR-aligned data management system for biodiversity, ecology and environmental data</article-title>
          <source>Biodiversity Data Journal</source>
          <volume>9</volume>
          <pub-id pub-id-type="doi">10.3897/bdj.9.e72901</pub-id>
        </element-citation>
      </ref>
      <ref id="B13717791">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chawuthai</surname>
              <given-names>Rathachai</given-names>
            </name>
            <name name-style="western">
              <surname>Takeda</surname>
              <given-names>Hideaki</given-names>
            </name>
            <name name-style="western">
              <surname>Wuwongse</surname>
              <given-names>Vilas</given-names>
            </name>
            <name name-style="western">
              <surname>Jinbo</surname>
              <given-names>Utsugi</given-names>
            </name>
          </person-group>
          <year>2016</year>
          <article-title>Presenting and preserving the change in taxonomic knowledge for linked data</article-title>
          <source>Semantic Web</source>
          <volume>7</volume>
          <issue>6</issue>
          <fpage>589</fpage>
          <lpage>616</lpage>
          <pub-id pub-id-type="doi">10.3233/sw-150192</pub-id>
        </element-citation>
      </ref>
      <ref id="B13717888">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Mingmin</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Shizhuo</given-names>
            </name>
            <name name-style="western">
              <surname>Franz</surname>
              <given-names>Nico</given-names>
            </name>
            <name name-style="western">
              <surname>Bowers</surname>
              <given-names>Shawn</given-names>
            </name>
            <name name-style="western">
              <surname>Ludäscher</surname>
              <given-names>Bertram</given-names>
            </name>
          </person-group>
          <year>2014</year>
          <article-title>Euler/X: A toolkit for logic-based taxonomy integration</article-title>
          <source>arXiv</source>
          <volume>1992</volume>
          <issue>1402</issue>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <uri>https://arxiv.org/abs/1402.1992</uri>
          <pub-id pub-id-type="doi">10.48550/arXiv.1402.1992</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718002">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Crous</surname>
              <given-names>P. W.</given-names>
            </name>
            <name name-style="western">
              <surname>Gams</surname>
              <given-names>W.</given-names>
            </name>
            <name name-style="western">
              <surname>Stalpers</surname>
              <given-names>J. A.</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>V.</given-names>
            </name>
            <name name-style="western">
              <surname>Stegehuis</surname>
              <given-names>G.</given-names>
            </name>
          </person-group>
          <year>2004</year>
          <article-title>MycoBank: an online initiative to launch mycology into the 21st century</article-title>
          <source>Studies in Mycology</source>
          <volume>50</volume>
          <fpage>19</fpage>
          <lpage>22</lpage>
          <uri>https://edepot.wur.nl/31039</uri>
        </element-citation>
      </ref>
      <ref id="B13718048">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>de Jong</surname>
              <given-names>Yde</given-names>
            </name>
            <name name-style="western">
              <surname>Kouwenberg</surname>
              <given-names>Juliana</given-names>
            </name>
            <name name-style="western">
              <surname>Boumans</surname>
              <given-names>Louis</given-names>
            </name>
            <name name-style="western">
              <surname>Hussey</surname>
              <given-names>Charles</given-names>
            </name>
            <name name-style="western">
              <surname>Hyam</surname>
              <given-names>Roger</given-names>
            </name>
            <name name-style="western">
              <surname>Nicolson</surname>
              <given-names>Nicola</given-names>
            </name>
            <name name-style="western">
              <surname>Kirk</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Paton</surname>
              <given-names>Alan</given-names>
            </name>
            <name name-style="western">
              <surname>Michel</surname>
              <given-names>Ellinor</given-names>
            </name>
            <name name-style="western">
              <surname>Guiry</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Boegh</surname>
              <given-names>Phillip</given-names>
            </name>
            <name name-style="western">
              <surname>Pedersen</surname>
              <given-names>Henrik</given-names>
            </name>
            <name name-style="western">
              <surname>Enghoff</surname>
              <given-names>Henrik</given-names>
            </name>
            <name name-style="western">
              <surname>von Raab-Straube</surname>
              <given-names>Eckhard</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
            <name name-style="western">
              <surname>Geoffroy</surname>
              <given-names>Marc</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Kohlbecker</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter</given-names>
            </name>
            <name name-style="western">
              <surname>Appeltans</surname>
              <given-names>Ward</given-names>
            </name>
            <name name-style="western">
              <surname>Arvanitidis</surname>
              <given-names>Christos</given-names>
            </name>
            <name name-style="western">
              <surname>Vanhoorne</surname>
              <given-names>Bart</given-names>
            </name>
            <name name-style="western">
              <surname>Declerck</surname>
              <given-names>Joram</given-names>
            </name>
            <name name-style="western">
              <surname>Vandepitte</surname>
              <given-names>Leen</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez</surname>
              <given-names>Francisco</given-names>
            </name>
            <name name-style="western">
              <surname>Nash</surname>
              <given-names>Róisín</given-names>
            </name>
            <name name-style="western">
              <surname>Costello</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>Ouvrard</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Bezard-Falgas</surname>
              <given-names>Pascale</given-names>
            </name>
            <name name-style="western">
              <surname>Bourgoin</surname>
              <given-names>Thierry</given-names>
            </name>
            <name name-style="western">
              <surname>Wetzel</surname>
              <given-names>Florian</given-names>
            </name>
            <name name-style="western">
              <surname>Glöckler</surname>
              <given-names>Falko</given-names>
            </name>
            <name name-style="western">
              <surname>Korb</surname>
              <given-names>Günther</given-names>
            </name>
            <name name-style="western">
              <surname>Ring</surname>
              <given-names>Caroline</given-names>
            </name>
            <name name-style="western">
              <surname>Hagedorn</surname>
              <given-names>Gregor</given-names>
            </name>
            <name name-style="western">
              <surname>Häuser</surname>
              <given-names>Christoph</given-names>
            </name>
            <name name-style="western">
              <surname>Aktaç</surname>
              <given-names>Nihat</given-names>
            </name>
            <name name-style="western">
              <surname>Asan</surname>
              <given-names>Ahmet</given-names>
            </name>
            <name name-style="western">
              <surname>Ardelean</surname>
              <given-names>Adorian</given-names>
            </name>
            <name name-style="western">
              <surname>Borges</surname>
              <given-names>Paulo</given-names>
            </name>
            <name name-style="western">
              <surname>Dhora</surname>
              <given-names>Dhimiter</given-names>
            </name>
            <name name-style="western">
              <surname>Khachatryan</surname>
              <given-names>Hasmik</given-names>
            </name>
            <name name-style="western">
              <surname>Malicky</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Ibrahimov</surname>
              <given-names>Shaig</given-names>
            </name>
            <name name-style="western">
              <surname>Tuzikov</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>De Wever</surname>
              <given-names>Aaike</given-names>
            </name>
            <name name-style="western">
              <surname>Moncheva</surname>
              <given-names>Snejana</given-names>
            </name>
            <name name-style="western">
              <surname>Spassov</surname>
              <given-names>Nikolai</given-names>
            </name>
            <name name-style="western">
              <surname>Chobot</surname>
              <given-names>Karel</given-names>
            </name>
            <name name-style="western">
              <surname>Popov</surname>
              <given-names>Alexi</given-names>
            </name>
            <name name-style="western">
              <surname>Boršić</surname>
              <given-names>Igor</given-names>
            </name>
            <name name-style="western">
              <surname>Sfenthourakis</surname>
              <given-names>Spyros</given-names>
            </name>
            <name name-style="western">
              <surname>Kõljalg</surname>
              <given-names>Urmas</given-names>
            </name>
            <name name-style="western">
              <surname>Uotila</surname>
              <given-names>Pertti</given-names>
            </name>
            <name name-style="western">
              <surname>Gargominy</surname>
              <given-names>Olivier</given-names>
            </name>
            <name name-style="western">
              <surname>Dauvin</surname>
              <given-names>Jean-Claude</given-names>
            </name>
            <name name-style="western">
              <surname>Tarkhnishvili</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Chaladze</surname>
              <given-names>Giorgi</given-names>
            </name>
            <name name-style="western">
              <surname>Tuerkay</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Legakis</surname>
              <given-names>Anastasios</given-names>
            </name>
            <name name-style="western">
              <surname>Peregovits</surname>
              <given-names>László</given-names>
            </name>
            <name name-style="western">
              <surname>Gudmundsson</surname>
              <given-names>Gudmundur</given-names>
            </name>
            <name name-style="western">
              <surname>Ólafsson</surname>
              <given-names>Erling</given-names>
            </name>
            <name name-style="western">
              <surname>Lysaght</surname>
              <given-names>Liam</given-names>
            </name>
            <name name-style="western">
              <surname>Galil</surname>
              <given-names>Bella</given-names>
            </name>
            <name name-style="western">
              <surname>Raimondo</surname>
              <given-names>Francesco</given-names>
            </name>
            <name name-style="western">
              <surname>Domina</surname>
              <given-names>Gianniantonio</given-names>
            </name>
            <name name-style="western">
              <surname>Stoch</surname>
              <given-names>Fabio</given-names>
            </name>
            <name name-style="western">
              <surname>Minelli</surname>
              <given-names>Alessandro</given-names>
            </name>
            <name name-style="western">
              <surname>Spungis</surname>
              <given-names>Voldermars</given-names>
            </name>
            <name name-style="western">
              <surname>Budrys</surname>
              <given-names>Eduardas</given-names>
            </name>
            <name name-style="western">
              <surname>Olenin</surname>
              <given-names>Sergej</given-names>
            </name>
            <name name-style="western">
              <surname>Turpel</surname>
              <given-names>Armand</given-names>
            </name>
            <name name-style="western">
              <surname>Walisch</surname>
              <given-names>Tania</given-names>
            </name>
            <name name-style="western">
              <surname>Krpach</surname>
              <given-names>Vladimir</given-names>
            </name>
            <name name-style="western">
              <surname>Gambin</surname>
              <given-names>Marie</given-names>
            </name>
            <name name-style="western">
              <surname>Ungureanu</surname>
              <given-names>Laurentia</given-names>
            </name>
            <name name-style="western">
              <surname>Karaman</surname>
              <given-names>Gordan</given-names>
            </name>
            <name name-style="western">
              <surname>Kleukers</surname>
              <given-names>Roy</given-names>
            </name>
            <name name-style="western">
              <surname>Stur</surname>
              <given-names>Elisabeth</given-names>
            </name>
            <name name-style="western">
              <surname>Aagaard</surname>
              <given-names>Kaare</given-names>
            </name>
            <name name-style="western">
              <surname>Valland</surname>
              <given-names>Nils</given-names>
            </name>
            <name name-style="western">
              <surname>Moen</surname>
              <given-names>Toril</given-names>
            </name>
            <name name-style="western">
              <surname>Bogdanowicz</surname>
              <given-names>Wieslaw</given-names>
            </name>
            <name name-style="western">
              <surname>Tykarski</surname>
              <given-names>Piotr</given-names>
            </name>
            <name name-style="western">
              <surname>Węsławski</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Kędra</surname>
              <given-names>Monika</given-names>
            </name>
            <name name-style="western">
              <surname>M. de Frias Martins</surname>
              <given-names>Antonio</given-names>
            </name>
            <name name-style="western">
              <surname>Abreu</surname>
              <given-names>António</given-names>
            </name>
            <name name-style="western">
              <surname>Silva</surname>
              <given-names>Ricardo</given-names>
            </name>
            <name name-style="western">
              <surname>Medvedev</surname>
              <given-names>Sergei</given-names>
            </name>
            <name name-style="western">
              <surname>Ryss</surname>
              <given-names>Alexander</given-names>
            </name>
            <name name-style="western">
              <surname>Šimić</surname>
              <given-names>Smiljka</given-names>
            </name>
            <name name-style="western">
              <surname>Marhold</surname>
              <given-names>Karol</given-names>
            </name>
            <name name-style="western">
              <surname>Stloukal</surname>
              <given-names>Eduard</given-names>
            </name>
            <name name-style="western">
              <surname>Tome</surname>
              <given-names>Davorin</given-names>
            </name>
            <name name-style="western">
              <surname>Ramos</surname>
              <given-names>Marian</given-names>
            </name>
            <name name-style="western">
              <surname>Valdés</surname>
              <given-names>Benito</given-names>
            </name>
            <name name-style="western">
              <surname>Pina</surname>
              <given-names>Francisco</given-names>
            </name>
            <name name-style="western">
              <surname>Kullander</surname>
              <given-names>Sven</given-names>
            </name>
            <name name-style="western">
              <surname>Telenius</surname>
              <given-names>Anders</given-names>
            </name>
            <name name-style="western">
              <surname>Gonseth</surname>
              <given-names>Yves</given-names>
            </name>
            <name name-style="western">
              <surname>Tschudin</surname>
              <given-names>Pascal</given-names>
            </name>
            <name name-style="western">
              <surname>Sergeyeva</surname>
              <given-names>Oleksandra</given-names>
            </name>
            <name name-style="western">
              <surname>Vladymyrov</surname>
              <given-names>Volodymyr</given-names>
            </name>
            <name name-style="western">
              <surname>Rizun</surname>
              <given-names>Volodymyr</given-names>
            </name>
            <name name-style="western">
              <surname>Raper</surname>
              <given-names>Chris</given-names>
            </name>
            <name name-style="western">
              <surname>Lear</surname>
              <given-names>Dan</given-names>
            </name>
            <name name-style="western">
              <surname>Stoev</surname>
              <given-names>Pavel</given-names>
            </name>
            <name name-style="western">
              <surname>Penev</surname>
              <given-names>Lyubomir</given-names>
            </name>
            <name name-style="western">
              <surname>Rubio</surname>
              <given-names>Ana</given-names>
            </name>
            <name name-style="western">
              <surname>Backeljau</surname>
              <given-names>Thierry</given-names>
            </name>
            <name name-style="western">
              <surname>Saarenmaa</surname>
              <given-names>Hannu</given-names>
            </name>
            <name name-style="western">
              <surname>Ulenberg</surname>
              <given-names>Sandrine</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <article-title>PESI - a taxonomic backbone for Europe</article-title>
          <source>Biodiversity Data Journal</source>
          <volume>3</volume>
          <pub-id pub-id-type="doi">10.3897/bdj.3.e5848</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718205">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Döring</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Ower</surname>
              <given-names>Geoffrey</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>The Catalogue of Life Data Package - A new format for exchanging nomenclatural and taxonomic information</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>3</volume>
          <pub-id pub-id-type="doi">10.3897/biss.3.38771</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718195">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ebert</surname>
              <given-names>Barbara</given-names>
            </name>
            <name name-style="western">
              <surname>Engel</surname>
              <given-names>Judith Sophie</given-names>
            </name>
            <name name-style="western">
              <surname>Kostadinov</surname>
              <given-names>Ivaylo</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
            <name name-style="western">
              <surname>Glöckner</surname>
              <given-names>Frank Oliver</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Connecting National and International Data Infrastructures in Biodiversity Research</article-title>
          <source>Proceedings of the Conference on Research Data Infrastructure</source>
          <volume>1</volume>
          <pub-id pub-id-type="doi">10.52825/cordi.v1i.346</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718223">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>EU</surname>
            </name>
          </person-group>
          <year>1992</year>
          <article-title>Council Directive 92/43/EEC of 21 May 1992 on the conservation of natural habitats and of wild fauna and flora</article-title>
          <publisher-name>European Commission</publisher-name>
          <uri>http://data.europa.eu/eli/dir/1992/43/2025-07-14</uri>
        </element-citation>
      </ref>
      <ref id="B13723654">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Euro+Med</surname>
            </name>
          </person-group>
          <year>2006-</year>
          <article-title>Euro+Med Plant base, the information resource for Euro-Mediterranean plant diversity</article-title>
          <publisher-name>Euro+Med Secretariat, Berlin</publisher-name>
          <uri>http://ww2.bgbm.org/EuroPlusMed/</uri>
        </element-citation>
      </ref>
      <ref id="B13718249">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Commission</surname>
              <given-names>European</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>INSPIRE Data Specification for the spatial data theme Species Distribution</article-title>
          <publisher-name>INSPIRE Maintenance and Implementation Group (MIG). Brussels</publisher-name>
          <uri>https://knowledge-base.inspire.ec.europa.eu/publications/inspire-data-specification-species-distribution-technical-guidelines_en</uri>
        </element-citation>
      </ref>
      <ref id="B13745307">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fichtmüller</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>CheckMyName Service Description (v. 1.1)</article-title>
          <publisher-name>Zenodo</publisher-name>
          <uri>https://zenodo.org/records/17987067</uri>
          <pub-id pub-id-type="doi">10.5281/zenodo.17987065</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718257">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Franz</surname>
              <given-names>Nico M.</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Mingmin</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Shizhuo</given-names>
            </name>
            <name name-style="western">
              <surname>Kianmajd</surname>
              <given-names>Parisa</given-names>
            </name>
            <name name-style="western">
              <surname>Bowers</surname>
              <given-names>Shawn</given-names>
            </name>
            <name name-style="western">
              <surname>Ludäscher</surname>
              <given-names>Bertram</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <article-title>Reasoning over Taxonomic Change: Exploring Alignments for the Perelleschus Use Case</article-title>
          <source>PLOS ONE</source>
          <volume>10</volume>
          <issue>2</issue>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0118247</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718268">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Franz</surname>
              <given-names>Nico M</given-names>
            </name>
            <name name-style="western">
              <surname>Sterner</surname>
              <given-names>Beckett W</given-names>
            </name>
          </person-group>
          <year>2018</year>
          <article-title>To increase trust, change the social design behind aggregated biodiversity data</article-title>
          <source>Database</source>
          <volume>2018</volume>
          <pub-id pub-id-type="doi">10.1093/database/bax100</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718277">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Frenzel</surname>
              <given-names>M.</given-names>
            </name>
          </person-group>
          <article-title>LTER-D - das deutsche Netzwerk für ökologisch-ökosystemare Langzeitforschung</article-title>
          <uri>https://www.ufz.de/lter-d/</uri>
          <date-in-citation content-type="access-date">2025-09-26T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718285">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Friedrichs-Manthey</surname>
              <given-names>Martin</given-names>
            </name>
            <name name-style="western">
              <surname>Bowler</surname>
              <given-names>Diana E.</given-names>
            </name>
            <name name-style="western">
              <surname>Freyhof</surname>
              <given-names>Jörg</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Freshwater fish in mid and northern German rivers – Long-term trends and associated species traits</article-title>
          <source>Science of The Total Environment</source>
          <volume>957</volume>
          <pub-id pub-id-type="doi">10.1016/j.scitotenv.2024.177759</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718294">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Froese</surname>
              <given-names>Rainer</given-names>
            </name>
            <name name-style="western">
              <surname>Pauly</surname>
              <given-names>D.</given-names>
            </name>
          </person-group>
          <article-title>FishBase. World Wide Web electronic publication.</article-title>
          <uri>www.fishbase.org</uri>
          <date-in-citation content-type="access-date">2025-07-27T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13940392">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garnett</surname>
              <given-names>Stephen T.</given-names>
            </name>
            <name name-style="western">
              <surname>Christidis</surname>
              <given-names>Les</given-names>
            </name>
            <name name-style="western">
              <surname>Conix</surname>
              <given-names>Stijn</given-names>
            </name>
            <name name-style="western">
              <surname>Costello</surname>
              <given-names>Mark J.</given-names>
            </name>
            <name name-style="western">
              <surname>Zachos</surname>
              <given-names>Frank E.</given-names>
            </name>
            <name name-style="western">
              <surname>Bánki</surname>
              <given-names>Olaf S.</given-names>
            </name>
            <name name-style="western">
              <surname>Bao</surname>
              <given-names>Yiming</given-names>
            </name>
            <name name-style="western">
              <surname>Barik</surname>
              <given-names>Saroj K.</given-names>
            </name>
            <name name-style="western">
              <surname>Buckeridge</surname>
              <given-names>John S.</given-names>
            </name>
            <name name-style="western">
              <surname>Hobern</surname>
              <given-names>Donald</given-names>
            </name>
            <name name-style="western">
              <surname>Lien</surname>
              <given-names>Aaron</given-names>
            </name>
            <name name-style="western">
              <surname>Montgomery</surname>
              <given-names>Narelle</given-names>
            </name>
            <name name-style="western">
              <surname>Nikolaeva</surname>
              <given-names>Svetlana</given-names>
            </name>
            <name name-style="western">
              <surname>Pyle</surname>
              <given-names>Richard L.</given-names>
            </name>
            <name name-style="western">
              <surname>Thomson</surname>
              <given-names>Scott A.</given-names>
            </name>
            <name name-style="western">
              <surname>van Dijk</surname>
              <given-names>Peter Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Whalen</surname>
              <given-names>Anthony</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Zhi-Qiang</given-names>
            </name>
            <name name-style="western">
              <surname>Thiele</surname>
              <given-names>Kevin R.</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Principles for creating a single authoritative list of the world’s species</article-title>
          <source>PLOS Biology</source>
          <volume>18</volume>
          <issue>7</issue>
          <pub-id pub-id-type="doi">10.1371/journal.pbio.3000736</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718302">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Secretariat</surname>
              <given-names>GBIF</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>GBIF Science Review No. 11</article-title>
          <publisher-name>Global Biodiversity Information Facility</publisher-name>
          <pub-id pub-id-type="doi">10.35035/d9pk-1162</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718310">
        <element-citation publication-type="website">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Gill</surname>
              <given-names>F.</given-names>
            </name>
            <name name-style="western">
              <surname>Donsker</surname>
              <given-names>D.</given-names>
            </name>
            <name name-style="western">
              <surname>Rasmussen</surname>
              <given-names>P.</given-names>
            </name>
          </person-group>
          <article-title>IOC World Bird List (v15.1)</article-title>
          <uri>https://www.worldbirdnames.org</uri>
          <date-in-citation content-type="access-date">2025-06-27T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718318">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Govaerts</surname>
              <given-names>Rafaël</given-names>
            </name>
            <name name-style="western">
              <surname>Nic Lughadha</surname>
              <given-names>Eimear</given-names>
            </name>
            <name name-style="western">
              <surname>Black</surname>
              <given-names>Nicholas</given-names>
            </name>
            <name name-style="western">
              <surname>Turner</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Paton</surname>
              <given-names>Alan</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>The World Checklist of Vascular Plants, a continuously updated resource for exploring global plant diversity</article-title>
          <source>Scientific Data</source>
          <volume>8</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1038/s41597-021-00997-6</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718337">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Govaerts</surname>
              <given-names>Rafaël</given-names>
            </name>
            <name name-style="western">
              <surname>Monro</surname>
              <given-names>Anna</given-names>
            </name>
            <name name-style="western">
              <surname>Wrankmore</surname>
              <given-names>Emma</given-names>
            </name>
            <name name-style="western">
              <surname>Krieger</surname>
              <given-names>Jonathan</given-names>
            </name>
            <name name-style="western">
              <surname>Hartley</surname>
              <given-names>Helen</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>New registration system for vascular plant names</article-title>
          <source>TAXON</source>
          <volume>71</volume>
          <issue>6</issue>
          <fpage>1361</fpage>
          <lpage>1364</lpage>
          <pub-id pub-id-type="doi">10.1002/tax.12833</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718347">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Grenié</surname>
              <given-names>Matthias</given-names>
            </name>
            <name name-style="western">
              <surname>Berti</surname>
              <given-names>Emilio</given-names>
            </name>
            <name name-style="western">
              <surname>Carvajal‐Quintero</surname>
              <given-names>Juan</given-names>
            </name>
            <name name-style="western">
              <surname>Dädlow</surname>
              <given-names>Gala Mona Louise</given-names>
            </name>
            <name name-style="western">
              <surname>Sagouis</surname>
              <given-names>Alban</given-names>
            </name>
            <name name-style="western">
              <surname>Winter</surname>
              <given-names>Marten</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Harmonizing taxon names in biodiversity data: A review of tools, databases and best practices</article-title>
          <source>Methods in Ecology and Evolution</source>
          <volume>14</volume>
          <issue>1</issue>
          <fpage>12</fpage>
          <lpage>25</lpage>
          <pub-id pub-id-type="doi">10.1111/2041-210x.13802</pub-id>
        </element-citation>
      </ref>
      <ref id="B13719245">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Guiry</surname>
              <given-names>M. D.</given-names>
            </name>
            <name name-style="western">
              <surname>Guiry</surname>
              <given-names>G. M.</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Algaebase. World-wide electronic publication</article-title>
          <publisher-name>University of Galway</publisher-name>
          <uri>https://www.algaebase.org</uri>
        </element-citation>
      </ref>
      <ref id="B13718375">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Harron</surname>
              <given-names>K.</given-names>
            </name>
          </person-group>
          <year>2016</year>
          <source>An introduction to data linkage</source>
          <publisher-name>ADRN Publications, University of Essex</publisher-name>
          <publisher-loc>Wivenhoe Park, UK</publisher-loc>
          <uri>https://eprints.ncrm.ac.uk/id/eprint/4282/1/Guide%20to%20data%20linkage.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13718358">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>HBW</surname>
            </name>
            <name name-style="western">
              <surname>International</surname>
              <given-names>BirdLife</given-names>
            </name>
          </person-group>
          <article-title>Handbook of the birds of the world and BirdLife International digital checklist of the birds of the world. Version 9</article-title>
          <uri>http://datazone.birdlife.org/userfiles/file/Species/Taxonomy/HBW-BirdLife_Checklist_v9_Oct24.zip</uri>
          <date-in-citation content-type="access-date">2025-07-27T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718383">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Heberling</surname>
              <given-names>J. Mason</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>Joseph T.</given-names>
            </name>
            <name name-style="western">
              <surname>Noesgaard</surname>
              <given-names>Daniel</given-names>
            </name>
            <name name-style="western">
              <surname>Weingart</surname>
              <given-names>Scott B.</given-names>
            </name>
            <name name-style="western">
              <surname>Schigel</surname>
              <given-names>Dmitry</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Data integration enables global biodiversity synthesis</article-title>
          <source>Proceedings of the National Academy of Sciences</source>
          <volume>118</volume>
          <issue>6</issue>
          <pub-id pub-id-type="doi">10.1073/pnas.2018093118</pub-id>
        </element-citation>
      </ref>
      <ref id="B13749862">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hobern</surname>
              <given-names>Donald</given-names>
            </name>
            <name name-style="western">
              <surname>Barik</surname>
              <given-names>Saroj K.</given-names>
            </name>
            <name name-style="western">
              <surname>Christidis</surname>
              <given-names>Les</given-names>
            </name>
            <name name-style="western">
              <surname>T.Garnett</surname>
              <given-names>Stephen</given-names>
            </name>
            <name name-style="western">
              <surname>Kirk</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Orrell</surname>
              <given-names>Thomas M.</given-names>
            </name>
            <name name-style="western">
              <surname>Pape</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Pyle</surname>
              <given-names>Richard L.</given-names>
            </name>
            <name name-style="western">
              <surname>Thiele</surname>
              <given-names>Kevin R.</given-names>
            </name>
            <name name-style="western">
              <surname>Zachos</surname>
              <given-names>Frank E.</given-names>
            </name>
            <name name-style="western">
              <surname>Bánki</surname>
              <given-names>Olaf</given-names>
            </name>
          </person-group>
          <year>2021</year>
          <article-title>Towards a global list of accepted species VI: The catalogue of life checklist</article-title>
          <source>Organisms Diversity &amp; Evolution</source>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>677</fpage>
          <lpage>690</lpage>
          <pub-id pub-id-type="doi">10.1007/s13127-021-00516-w</pub-id>
        </element-citation>
      </ref>
      <ref id="B13940383">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hodson</surname>
              <given-names>Simon</given-names>
            </name>
            <name name-style="western">
              <surname>Gregory</surname>
              <given-names>Arofan</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>WorldFAIR Final Policy Brief: Enabling Global FAIR Data - Recommendations for Research Infrastructures</article-title>
          <source>Zenodo</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.14236140</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718393">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hyam</surname>
              <given-names>Roger</given-names>
            </name>
          </person-group>
          <article-title>What is name matching</article-title>
          <uri>https://wiki.bgbm.org/tettris/What_is_name_matching%3F</uri>
          <date-in-citation content-type="access-date">2025-07-26T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13723105">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hyam</surname>
              <given-names>Roger</given-names>
            </name>
            <name name-style="western">
              <surname>Vanhoorne</surname>
              <given-names>Bart</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter Günther</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Lyssens</surname>
              <given-names>Liesbeth</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>TNLS: Common name matching specification</article-title>
          <source>Royal Botanic Garden Edinburgh (RBGE); Flanders Marine Institute (VLIZ)</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.17670578</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718401">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hyam</surname>
              <given-names>Roger</given-names>
            </name>
            <name name-style="western">
              <surname>Vanhoorne</surname>
              <given-names>Bart</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter Günther</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Lamote</surname>
              <given-names>Milan</given-names>
            </name>
            <name name-style="western">
              <surname>De Paepe</surname>
              <given-names>Bart</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>TNLS: Taxonomic activity notification service</article-title>
          <source>Royal Botanic Garden Edinburgh (RBGE); Flanders Marine Institute (VLIZ)</source>
          <pub-id pub-id-type="doi">10.5281/zenodo.17588931</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718412">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>ICTV</surname>
            </name>
          </person-group>
          <article-title>International Committee on Taxonomy of VIruses Master Species List</article-title>
          <uri>https://ictv.global/msl/current</uri>
          <date-in-citation content-type="access-date">2025-07-27T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13719216">
        <element-citation publication-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>ICZN</surname>
            </name>
          </person-group>
          <year>1999</year>
          <source>International Commission on Zoological Nomenclature. International Code of Zoological Nomenclature</source>
          <edition>4th Edition</edition>
          <publisher-name>The International Trust for Zoological Nomenclature</publisher-name>
          <publisher-loc>London</publisher-loc>
          <uri>https://www.biodiversitylibrary.org/page/34423691</uri>
          <pub-id pub-id-type="doi">10.5962/bhl.title.50608</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718420">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>ICZN</surname>
            </name>
          </person-group>
          <year>2012</year>
          <article-title>Amendment of Articles 8, 9, 10, 21 and 78 of the International Code of Zoological Nomenclature to expand and refine methods of publication</article-title>
          <source>ZooKeys</source>
          <volume>219</volume>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.3897/zookeys.219.3944</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718463">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fungorum</surname>
              <given-names>Index</given-names>
            </name>
          </person-group>
          <year>2009-</year>
          <article-title>Index Fungorum</article-title>
          <publisher-name>Royal Botanic Gardens Kew Mycology Section, Landcare Research-NZ Mycology Group, Institute of Microbiology, Chinese Academy of Science (the custodians)</publisher-name>
          <uri>https://www.indexfungorum.org/</uri>
        </element-citation>
      </ref>
      <ref id="B13718455">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>IPNI</surname>
            </name>
          </person-group>
          <year>2000</year>
          <article-title>International Plant Name Index</article-title>
          <publisher-name>Royal Botanic Gardens, Kew, Harvard University Herbaria &amp; Libraries and Australian National Herbarium</publisher-name>
          <uri>http://www.ipni.org</uri>
        </element-citation>
      </ref>
      <ref id="B13718472">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Islam</surname>
              <given-names>Sharif</given-names>
            </name>
            <name name-style="western">
              <surname>Papale</surname>
              <given-names>Dario</given-names>
            </name>
            <name name-style="western">
              <surname>Vaira</surname>
              <given-names>Lucia</given-names>
            </name>
            <name name-style="western">
              <surname>Rosati</surname>
              <given-names>Ilaria</given-names>
            </name>
            <name name-style="western">
              <surname>Peterseil</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Pichot</surname>
              <given-names>Christian</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Navigating taxonomic complexity: A use-case report on FAIR scientific name-matching service usage in ENVRI Research Infrastructures</article-title>
          <source>Research Ideas and Outcomes</source>
          <volume>10</volume>
          <pub-id pub-id-type="doi">10.3897/rio.10.e121871</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718494">
        <element-citation publication-type="other">
          <person-group person-group-type="editor">
            <name name-style="western">
              <surname>Kilian</surname>
              <given-names>Norbert</given-names>
            </name>
            <name name-style="western">
              <surname>Raab-Straube</surname>
              <given-names>Eckhard von</given-names>
            </name>
          </person-group>
          <year>2009-</year>
          <article-title>Cichorieae systematics portal</article-title>
          <publisher-name>Botanical Garden and Botanical Museum Berlin</publisher-name>
          <uri>http://cichorieae.e-taxonomy.net/portal/</uri>
        </element-citation>
      </ref>
      <ref id="B13719261">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kociolek</surname>
              <given-names>J. P.</given-names>
            </name>
            <name name-style="western">
              <surname>Blanco</surname>
              <given-names>S.</given-names>
            </name>
            <name name-style="western">
              <surname>Coste</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Ector</surname>
              <given-names>L.</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Y.</given-names>
            </name>
            <name name-style="western">
              <surname>Karthick</surname>
              <given-names>B.</given-names>
            </name>
            <name name-style="western">
              <surname>Kulikovskiy</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Lundholm</surname>
              <given-names>N.</given-names>
            </name>
            <name name-style="western">
              <surname>Ludwig</surname>
              <given-names>T.</given-names>
            </name>
            <name name-style="western">
              <surname>Potapova</surname>
              <given-names>M.</given-names>
            </name>
            <name name-style="western">
              <surname>Rimet</surname>
              <given-names>F.</given-names>
            </name>
            <name name-style="western">
              <surname>Sabbe</surname>
              <given-names>K.</given-names>
            </name>
            <name name-style="western">
              <surname>Sale</surname>
              <given-names>S.</given-names>
            </name>
            <name name-style="western">
              <surname>Sar</surname>
              <given-names>E.</given-names>
            </name>
            <name name-style="western">
              <surname>Taylor</surname>
              <given-names>J.</given-names>
            </name>
            <name name-style="western">
              <surname>Vijver</surname>
              <given-names>B. Van de</given-names>
            </name>
            <name name-style="western">
              <surname>Wetzel</surname>
              <given-names>C. E.</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>D. M.</given-names>
            </name>
            <name name-style="western">
              <surname>Witkowski</surname>
              <given-names>A.</given-names>
            </name>
            <name name-style="western">
              <surname>Witkowski</surname>
              <given-names>J.</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>DiatomBase</article-title>
          <publisher-name>VLIZ</publisher-name>
          <uri>https://www.diatombase.org</uri>
          <pub-id pub-id-type="doi">10.14284/504</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718483">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Korotkova</surname>
              <given-names>Nadja</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Organizing and maintaining a taxonomic expert network: Lessons from the <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="order">Caryophyllales</tp:taxon-name-part></tp:taxon-name> TEN</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>6</volume>
          <pub-id pub-id-type="doi">10.3897/biss.6.91113</pub-id>
        </element-citation>
      </ref>
      <ref id="B13719285">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kusber</surname>
              <given-names>Wolf-Henning</given-names>
            </name>
            <name name-style="western">
              <surname>Kohlbecker</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Mohamad</surname>
              <given-names>Heba</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
            <name name-style="western">
              <surname>Jahn</surname>
              <given-names>Regine</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Registration of algal novelties in Phycobank: Serving the scientific community and filling gaps in the global names backbone</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>3</volume>
          <issue>e37285</issue>
          <pub-id pub-id-type="doi">10.3897/biss.3.37285</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718503">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lien</surname>
              <given-names>Aaron M.</given-names>
            </name>
            <name name-style="western">
              <surname>Banki</surname>
              <given-names>Olaf</given-names>
            </name>
            <name name-style="western">
              <surname>Barik</surname>
              <given-names>Saroj K.</given-names>
            </name>
            <name name-style="western">
              <surname>Buckeridge</surname>
              <given-names>John S.</given-names>
            </name>
            <name name-style="western">
              <surname>Christidis</surname>
              <given-names>Les</given-names>
            </name>
            <name name-style="western">
              <surname>Cigliano</surname>
              <given-names>María Marta</given-names>
            </name>
            <name name-style="western">
              <surname>Conix</surname>
              <given-names>Stijn</given-names>
            </name>
            <name name-style="western">
              <surname>Costello</surname>
              <given-names>Mark John</given-names>
            </name>
            <name name-style="western">
              <surname>Hobern</surname>
              <given-names>Donald</given-names>
            </name>
            <name name-style="western">
              <surname>Kirk</surname>
              <given-names>Paul M.</given-names>
            </name>
            <name name-style="western">
              <surname>Kroh</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Montgomery</surname>
              <given-names>Narelle</given-names>
            </name>
            <name name-style="western">
              <surname>Nikolaeva</surname>
              <given-names>Svetlana</given-names>
            </name>
            <name name-style="western">
              <surname>Orrell</surname>
              <given-names>Thomas M.</given-names>
            </name>
            <name name-style="western">
              <surname>Pyle</surname>
              <given-names>Richard L.</given-names>
            </name>
            <name name-style="western">
              <surname>Raz</surname>
              <given-names>Lauren</given-names>
            </name>
            <name name-style="western">
              <surname>Thiele</surname>
              <given-names>Kevin</given-names>
            </name>
            <name name-style="western">
              <surname>Thomson</surname>
              <given-names>Scott A.</given-names>
            </name>
            <name name-style="western">
              <surname>van Dijk</surname>
              <given-names>Peter Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Wambiji</surname>
              <given-names>Nina</given-names>
            </name>
            <name name-style="western">
              <surname>Whalen</surname>
              <given-names>Anthony</given-names>
            </name>
            <name name-style="western">
              <surname>Zachos</surname>
              <given-names>Frank E.</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Zhi-Qiang</given-names>
            </name>
            <name name-style="western">
              <surname>Garnett</surname>
              <given-names>Stephen T.</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Widespread support for a global species list with a formal governance system</article-title>
          <source>Proceedings of the National Academy of Sciences</source>
          <volume>120</volume>
          <issue>45</issue>
          <pub-id pub-id-type="doi">10.1073/pnas.2306899120</pub-id>
        </element-citation>
      </ref>
      <ref id="B13719177">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lughadha</surname>
              <given-names>Eimear Nic</given-names>
            </name>
          </person-group>
          <year>2004</year>
          <article-title>Towards a working list of all known plant species</article-title>
          <source>Philosophical Transactions of the Royal Society of London. Series B: Biological Sciences</source>
          <volume>359</volume>
          <issue>1444</issue>
          <fpage>681</fpage>
          <lpage>687</lpage>
          <pub-id pub-id-type="doi">10.1098/rstb.2003.1446</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718532">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Malekmohammadi</surname>
              <given-names>Maryam</given-names>
            </name>
            <name name-style="western">
              <surname>Koutroumpa</surname>
              <given-names>Konstantina</given-names>
            </name>
            <name name-style="western">
              <surname>Crespo</surname>
              <given-names>Manuel B.</given-names>
            </name>
            <name name-style="western">
              <surname>Domina</surname>
              <given-names>Gianniantonio</given-names>
            </name>
            <name name-style="western">
              <surname>Korotkova</surname>
              <given-names>Nadja</given-names>
            </name>
            <name name-style="western">
              <surname>Akhani</surname>
              <given-names>Hossein</given-names>
            </name>
            <name name-style="western">
              <surname>von Mering</surname>
              <given-names>Sabine</given-names>
            </name>
            <name name-style="western">
              <surname>Borsch</surname>
              <given-names>Thomas</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter G.</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>A taxonomic backbone for the <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="family">Plumbaginaceae</tp:taxon-name-part></tp:taxon-name> (<tp:taxon-name><tp:taxon-name-part taxon-name-part-type="order">Caryophyllales</tp:taxon-name-part></tp:taxon-name>)</article-title>
          <source>PhytoKeys</source>
          <volume>243</volume>
          <fpage>67</fpage>
          <lpage>103</lpage>
          <pub-id pub-id-type="doi">10.3897/phytokeys.243.122784</pub-id>
        </element-citation>
      </ref>
      <ref id="B13723725">
        <element-citation publication-type="software">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mozzherin</surname>
              <given-names>Dmitry</given-names>
            </name>
            <name name-style="western">
              <surname>Shorthouse</surname>
              <given-names>David P</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>Global Names Recognition and Discovery (GNRD)</article-title>
          <publisher-name>Zenodo.org</publisher-name>
          <date-in-citation content-type="released">2019-12-10T00:52:08+00:00</date-in-citation>
          <pub-id pub-id-type="doi">10.5281/zenodo.3569619</pub-id>
          <comment content-type="Version">0.9.0</comment>
        </element-citation>
      </ref>
      <ref id="B13718546">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mozzherin</surname>
              <given-names>Dmitry</given-names>
            </name>
            <name name-style="western">
              <surname>Paul</surname>
              <given-names>Deborah</given-names>
            </name>
            <name name-style="western">
              <surname>Whitmire</surname>
              <given-names>Amanda</given-names>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>Can we standardize name reconciliaton via OpenRefine?</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>8</volume>
          <pub-id pub-id-type="doi">10.3897/biss.8.134910</pub-id>
        </element-citation>
      </ref>
      <ref id="B13723755">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Güntsch</surname>
              <given-names>Anton</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Functional optimised EU Nomen Processes and services up and running</article-title>
          <publisher-name>TETTRIs</publisher-name>
          <uri>https://tettris.eu/wp-content/uploads/2025/12/TETTRIs-D2.1-Functional-optimised-EU-Nomen-processes-and-services-up-and-running.pdf</uri>
        </element-citation>
      </ref>
      <ref id="B13718555">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>C. T.</given-names>
            </name>
            <name name-style="western">
              <surname>Tindall</surname>
              <given-names>B. J.</given-names>
            </name>
            <name name-style="western">
              <surname>Garrity</surname>
              <given-names>G. M.</given-names>
            </name>
          </person-group>
          <year>2019</year>
          <article-title>International Code of Nomenclature of Prokaryotes</article-title>
          <source>International Journal of Systematic and Evolutionary Microbiology</source>
          <volume>69</volume>
          <pub-id pub-id-type="doi">10.1099/ijsem.0.000778</pub-id>
        </element-citation>
      </ref>
      <ref id="B13723733">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Plazi</surname>
            </name>
          </person-group>
          <article-title>TreatmentBank</article-title>
          <uri>https://plazi.org/treatmentbank/</uri>
          <date-in-citation content-type="access-date">2025-11-30T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718564">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Proença Neto</surname>
              <given-names>Marco</given-names>
            </name>
            <name name-style="western">
              <surname>De Sousa</surname>
              <given-names>Marcos</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>Pytaxon: A Python software for resolving and correcting taxonomic names in biodiversity data</article-title>
          <source>Biodiversity Data Journal</source>
          <volume>13</volume>
          <pub-id pub-id-type="doi">10.3897/bdj.13.e138257</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718573">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rainer</surname>
              <given-names>Heimo</given-names>
            </name>
            <name name-style="western">
              <surname>Berger</surname>
              <given-names>Andreas</given-names>
            </name>
            <name name-style="western">
              <surname>Schuster</surname>
              <given-names>Tanja</given-names>
            </name>
            <name name-style="western">
              <surname>Walter</surname>
              <given-names>Johannes</given-names>
            </name>
            <name name-style="western">
              <surname>Reich</surname>
              <given-names>Dieter</given-names>
            </name>
            <name name-style="western">
              <surname>Zernig</surname>
              <given-names>Kurt</given-names>
            </name>
            <name name-style="western">
              <surname>Danihelka</surname>
              <given-names>Jiří</given-names>
            </name>
            <name name-style="western">
              <surname>Galušková</surname>
              <given-names>Hana</given-names>
            </name>
            <name name-style="western">
              <surname>Mráz</surname>
              <given-names>Patrik</given-names>
            </name>
            <name name-style="western">
              <surname>Tkach</surname>
              <given-names>Natalia</given-names>
            </name>
            <name name-style="western">
              <surname>Hentschel</surname>
              <given-names>Jörn</given-names>
            </name>
            <name name-style="western">
              <surname>Müller</surname>
              <given-names>Jochen</given-names>
            </name>
            <name name-style="western">
              <surname>Wagner</surname>
              <given-names>Sarah</given-names>
            </name>
            <name name-style="western">
              <surname>Berendsohn</surname>
              <given-names>Walter</given-names>
            </name>
            <name name-style="western">
              <surname>Lücking</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Vogt</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Pignotti</surname>
              <given-names>Lia</given-names>
            </name>
            <name name-style="western">
              <surname>Roma-Marzio</surname>
              <given-names>Francesco</given-names>
            </name>
            <name name-style="western">
              <surname>Peruzzi</surname>
              <given-names>Lorenzo</given-names>
            </name>
          </person-group>
          <year>2023</year>
          <article-title>Community curation of nomenclatural and taxonomic information in the context of the collection management system JACQ</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>7</volume>
          <pub-id pub-id-type="doi">10.3897/biss.7.112571</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718597">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rambold</surname>
              <given-names>Gerhard</given-names>
            </name>
            <name name-style="western">
              <surname>Bensch</surname>
              <given-names>Konstanze</given-names>
            </name>
            <name name-style="western">
              <surname>Kirk</surname>
              <given-names>Paul M.</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>Yi-Jian</given-names>
            </name>
            <name name-style="western">
              <surname>Robert</surname>
              <given-names>Vincent</given-names>
            </name>
            <name name-style="western">
              <surname>Sanz</surname>
              <given-names>Veronica</given-names>
            </name>
            <name name-style="western">
              <surname>Triebel</surname>
              <given-names>Dagmar</given-names>
            </name>
          </person-group>
          <year>2017</year>
          <article-title>Citation of a taxon name identifier issued by the ICN‐recognized registration repositories instead of taxon name author citation</article-title>
          <source>Taxon</source>
          <volume>66</volume>
          <issue>5</issue>
          <fpage>1200</fpage>
          <lpage>1203</lpage>
          <pub-id pub-id-type="doi">10.12705/665.12</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718610">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Remsen</surname>
              <given-names>David</given-names>
            </name>
          </person-group>
          <year>2016</year>
          <article-title>The use and limits of scientific names in biological informatics</article-title>
          <source>ZooKeys</source>
          <volume>550</volume>
          <fpage>207</fpage>
          <lpage>223</lpage>
          <pub-id pub-id-type="doi">10.3897/zookeys.550.9546</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718619">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sterner</surname>
              <given-names>Beckett</given-names>
            </name>
            <name name-style="western">
              <surname>Upham</surname>
              <given-names>Nathan</given-names>
            </name>
            <name name-style="western">
              <surname>Sen</surname>
              <given-names>Atriya</given-names>
            </name>
            <name name-style="western">
              <surname>Franz</surname>
              <given-names>Nico</given-names>
            </name>
          </person-group>
          <year>2020</year>
          <article-title>Avenues into Integration: Communicating taxonomic intelligence from sender to recipient</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>4</volume>
          <pub-id pub-id-type="doi">10.3897/biss.4.59006</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718629">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>TETTRIs</surname>
            </name>
          </person-group>
          <article-title>Transforming European Taxonomy through Training, Research and Innovations - TETTRIs Website</article-title>
          <uri>https://tettris.eu/the-project/</uri>
          <date-in-citation content-type="access-date">2025-11-24T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718653">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>TETTRIs</surname>
            </name>
          </person-group>
          <year>2024</year>
          <article-title>TNLS: a new taxonomic name matching system in the age of Big Data</article-title>
          <publisher-name>TETTRIs project news</publisher-name>
          <uri>https://tettris.eu/2024/10/18/tnls-a-new-taxonomic-name-matching-system-in-the-age-of-big-data/</uri>
        </element-citation>
      </ref>
      <ref id="B13723675">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>TETTRIs</surname>
            </name>
          </person-group>
          <article-title>Database content changes affecting the taxonomic standing of a scientific name</article-title>
          <uri>https://wiki.bgbm.org/tettris/Database_content_changes_affecting_the_taxonomic_standing_of_a_scientific_name</uri>
          <date-in-citation content-type="access-date">2025-11-30T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13723706">
        <element-citation publication-type="website">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>TETTRIs</surname>
            </name>
          </person-group>
          <article-title>Taxonomic datasets</article-title>
          <uri>https://wiki.bgbm.org/tettris/Taxonomic_datasets</uri>
          <date-in-citation content-type="access-date">2025-11-30T00:52:08+00:00</date-in-citation>
        </element-citation>
      </ref>
      <ref id="B13718663">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>TROPICOS</surname>
            </name>
          </person-group>
          <year>1986-</year>
          <article-title>Tropicos.org</article-title>
          <publisher-name>Missouri Botanical Garden</publisher-name>
          <uri>http://www.tropicos.org</uri>
        </element-citation>
      </ref>
      <ref id="B13718671">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Turland</surname>
              <given-names>Nicholas J.</given-names>
            </name>
            <name name-style="western">
              <surname>Wiersema</surname>
              <given-names>John H.</given-names>
            </name>
            <name name-style="western">
              <surname>Barrie</surname>
              <given-names>Fred R.</given-names>
            </name>
            <name name-style="western">
              <surname>Gandhi</surname>
              <given-names>Kanchi N.</given-names>
            </name>
            <name name-style="western">
              <surname>Gravendyck</surname>
              <given-names>Julia</given-names>
            </name>
            <name name-style="western">
              <surname>Greuter</surname>
              <given-names>Werner</given-names>
            </name>
            <name name-style="western">
              <surname>Hawksworth</surname>
              <given-names>David L.</given-names>
            </name>
            <name name-style="western">
              <surname>Herendeen</surname>
              <given-names>Patrick S.</given-names>
            </name>
            <name name-style="western">
              <surname>Klopper</surname>
              <given-names>Ronell R.</given-names>
            </name>
            <name name-style="western">
              <surname>Knapp</surname>
              <given-names>Sandra</given-names>
            </name>
            <name name-style="western">
              <surname>Kusber</surname>
              <given-names>Wolf-Henning</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>De-Zhu</given-names>
            </name>
            <name name-style="western">
              <surname>May</surname>
              <given-names>Tom W.</given-names>
            </name>
            <name name-style="western">
              <surname>Monro</surname>
              <given-names>Anna M.</given-names>
            </name>
            <name name-style="western">
              <surname>Prado</surname>
              <given-names>Jefferson</given-names>
            </name>
            <name name-style="western">
              <surname>Price</surname>
              <given-names>Michelle J.</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>Gideon F.</given-names>
            </name>
            <name name-style="western">
              <surname>Señoret</surname>
              <given-names>Juan Carlos Zamora</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>International Code of Nomenclature for <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="above-family">Algae</tp:taxon-name-part></tp:taxon-name>, <tp:taxon-name><tp:taxon-name-part taxon-name-part-type="kingdom">Fungi</tp:taxon-name-part></tp:taxon-name>, and Plants</article-title>
          <source>Regnum Vegetabile</source>
          <volume>162</volume>
          <pub-id pub-id-type="doi">10.7208/chicago/9780226839479.001.0001</pub-id>
        </element-citation>
      </ref>
      <ref id="B13715688">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vaccaro</surname>
              <given-names>Giannina</given-names>
            </name>
            <name name-style="western">
              <surname>Swerts</surname>
              <given-names>Elfie</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Data Linkage</article-title>
          <source>FORS – Swiss Centre of Expertise in the Social Sciences</source>
          <pub-id pub-id-type="doi">10.24449/fg-2022-00018</pub-id>
        </element-citation>
      </ref>
      <ref id="B13723741">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Van Maldeghem</surname>
              <given-names>Laurian</given-names>
            </name>
            <name name-style="western">
              <surname>Portier</surname>
              <given-names>Marc</given-names>
            </name>
            <name name-style="western">
              <surname>Vandepitte</surname>
              <given-names>Leen</given-names>
            </name>
            <name name-style="western">
              <surname>Lonneville</surname>
              <given-names>Britt</given-names>
            </name>
            <name name-style="western">
              <surname>Vanhoorne</surname>
              <given-names>Bart</given-names>
            </name>
            <name name-style="western">
              <surname>Tyberghein</surname>
              <given-names>Lennert</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Linked data publishing of the World Register of Marine Species (WoRMS) as a basis for uniformly linking-up resources to accepted taxon names</article-title>
          <source>Biodiversity Information Science and Standards</source>
          <volume>6</volume>
          <issue>e94903</issue>
          <pub-id pub-id-type="doi">10.3897/biss.6.94903</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718704">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Fang</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Ke</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Lei</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Mingjun</given-names>
            </name>
            <name name-style="western">
              <surname>Kirk</surname>
              <given-names>Paul M</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>Guomei</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Qinglan</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Bo</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Shuai</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Zhengfei</given-names>
            </name>
            <name name-style="western">
              <surname>Han</surname>
              <given-names>Dong</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>Juncai</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Linhuan</given-names>
            </name>
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>Yijian</given-names>
            </name>
          </person-group>
          <year>2022</year>
          <article-title>Fungal names: a comprehensive nomenclatural repository and knowledge base for fungal taxonomy</article-title>
          <source>Nucleic Acids Research</source>
          <volume>51</volume>
          <pub-id pub-id-type="doi">10.1093/nar/gkac926</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718723">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>List</surname>
              <given-names>WFO Plant</given-names>
            </name>
          </person-group>
          <year>2021-</year>
          <article-title>World Flora Online Plant List - a snapshot of the WFO taxonomic backbone</article-title>
          <publisher-name>World Flora Online initiative, Geneva</publisher-name>
          <uri>https://wfoplantlist.org/</uri>
        </element-citation>
      </ref>
      <ref id="B13718731">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wieczorek</surname>
              <given-names>John</given-names>
            </name>
            <name name-style="western">
              <surname>Bloom</surname>
              <given-names>David</given-names>
            </name>
            <name name-style="western">
              <surname>Guralnick</surname>
              <given-names>Robert</given-names>
            </name>
            <name name-style="western">
              <surname>Blum</surname>
              <given-names>Stan</given-names>
            </name>
            <name name-style="western">
              <surname>Döring</surname>
              <given-names>Markus</given-names>
            </name>
            <name name-style="western">
              <surname>Giovanni</surname>
              <given-names>Renato</given-names>
            </name>
            <name name-style="western">
              <surname>Robertson</surname>
              <given-names>Tim</given-names>
            </name>
            <name name-style="western">
              <surname>Vieglais</surname>
              <given-names>David</given-names>
            </name>
          </person-group>
          <year>2012</year>
          <article-title>Darwin Core: An evolving community-developed biodiversity data standard</article-title>
          <source>PLOS One</source>
          <volume>7</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0029715</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718744">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wilkinson</surname>
              <given-names>Mark D.</given-names>
            </name>
            <name name-style="western">
              <surname>Dumontier</surname>
              <given-names>Michel</given-names>
            </name>
            <name name-style="western">
              <surname>Aalbersberg</surname>
              <given-names>IJsbrand Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Appleton</surname>
              <given-names>Gabrielle</given-names>
            </name>
            <name name-style="western">
              <surname>Axton</surname>
              <given-names>Myles</given-names>
            </name>
            <name name-style="western">
              <surname>Baak</surname>
              <given-names>Arie</given-names>
            </name>
            <name name-style="western">
              <surname>Blomberg</surname>
              <given-names>Niklas</given-names>
            </name>
            <name name-style="western">
              <surname>Boiten</surname>
              <given-names>Jan-Willem</given-names>
            </name>
            <name name-style="western">
              <surname>da Silva Santos</surname>
              <given-names>Luiz Bonino</given-names>
            </name>
            <name name-style="western">
              <surname>Bourne</surname>
              <given-names>Philip E.</given-names>
            </name>
            <name name-style="western">
              <surname>Bouwman</surname>
              <given-names>Jildau</given-names>
            </name>
            <name name-style="western">
              <surname>Brookes</surname>
              <given-names>Anthony J.</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>Tim</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>Mercè</given-names>
            </name>
            <name name-style="western">
              <surname>Dillo</surname>
              <given-names>Ingrid</given-names>
            </name>
            <name name-style="western">
              <surname>Dumon</surname>
              <given-names>Olivier</given-names>
            </name>
            <name name-style="western">
              <surname>Edmunds</surname>
              <given-names>Scott</given-names>
            </name>
            <name name-style="western">
              <surname>Evelo</surname>
              <given-names>Chris T.</given-names>
            </name>
            <name name-style="western">
              <surname>Finkers</surname>
              <given-names>Richard</given-names>
            </name>
            <name name-style="western">
              <surname>Gonzalez-Beltran</surname>
              <given-names>Alejandra</given-names>
            </name>
            <name name-style="western">
              <surname>Gray</surname>
              <given-names>Alasdair J. G.</given-names>
            </name>
            <name name-style="western">
              <surname>Groth</surname>
              <given-names>Paul</given-names>
            </name>
            <name name-style="western">
              <surname>Goble</surname>
              <given-names>Carole</given-names>
            </name>
            <name name-style="western">
              <surname>Grethe</surname>
              <given-names>Jeffrey S.</given-names>
            </name>
            <name name-style="western">
              <surname>Heringa</surname>
              <given-names>Jaap</given-names>
            </name>
            <name name-style="western">
              <surname>’t Hoen</surname>
              <given-names>Peter A. C</given-names>
            </name>
            <name name-style="western">
              <surname>Hooft</surname>
              <given-names>Rob</given-names>
            </name>
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>Tobias</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>Ruben</given-names>
            </name>
            <name name-style="western">
              <surname>Kok</surname>
              <given-names>Joost</given-names>
            </name>
            <name name-style="western">
              <surname>Lusher</surname>
              <given-names>Scott J.</given-names>
            </name>
            <name name-style="western">
              <surname>Martone</surname>
              <given-names>Maryann E.</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Albert</given-names>
            </name>
            <name name-style="western">
              <surname>Packer</surname>
              <given-names>Abel L.</given-names>
            </name>
            <name name-style="western">
              <surname>Persson</surname>
              <given-names>Bengt</given-names>
            </name>
            <name name-style="western">
              <surname>Rocca-Serra</surname>
              <given-names>Philippe</given-names>
            </name>
            <name name-style="western">
              <surname>Roos</surname>
              <given-names>Marco</given-names>
            </name>
            <name name-style="western">
              <surname>van Schaik</surname>
              <given-names>Rene</given-names>
            </name>
            <name name-style="western">
              <surname>Sansone</surname>
              <given-names>Susanna-Assunta</given-names>
            </name>
            <name name-style="western">
              <surname>Schultes</surname>
              <given-names>Erik</given-names>
            </name>
            <name name-style="western">
              <surname>Sengstag</surname>
              <given-names>Thierry</given-names>
            </name>
            <name name-style="western">
              <surname>Slater</surname>
              <given-names>Ted</given-names>
            </name>
            <name name-style="western">
              <surname>Strawn</surname>
              <given-names>George</given-names>
            </name>
            <name name-style="western">
              <surname>Swertz</surname>
              <given-names>Morris A.</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>Mark</given-names>
            </name>
            <name name-style="western">
              <surname>van der Lei</surname>
              <given-names>Johan</given-names>
            </name>
            <name name-style="western">
              <surname>van Mulligen</surname>
              <given-names>Erik</given-names>
            </name>
            <name name-style="western">
              <surname>Velterop</surname>
              <given-names>Jan</given-names>
            </name>
            <name name-style="western">
              <surname>Waagmeester</surname>
              <given-names>Andra</given-names>
            </name>
            <name name-style="western">
              <surname>Wittenburg</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Wolstencroft</surname>
              <given-names>Katherine</given-names>
            </name>
            <name name-style="western">
              <surname>Zhao</surname>
              <given-names>Jun</given-names>
            </name>
            <name name-style="western">
              <surname>Mons</surname>
              <given-names>Barend</given-names>
            </name>
          </person-group>
          <year>2016</year>
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          <source>Scientific Data</source>
          <volume>3</volume>
          <issue>1</issue>
          <pub-id pub-id-type="doi">10.1038/sdata.2016.18</pub-id>
        </element-citation>
      </ref>
      <ref id="B13719253">
        <element-citation publication-type="other">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Board</surname>
              <given-names>WoRMS Editorial</given-names>
            </name>
          </person-group>
          <year>2025</year>
          <article-title>World Register of Marine Species</article-title>
          <publisher-name>Oostende: Flanders Marine Institute (VLIZ)</publisher-name>
          <uri>https://www.marinespecies.org</uri>
          <pub-id pub-id-type="doi">10.14284/170</pub-id>
        </element-citation>
      </ref>
      <ref id="B13718802">
        <element-citation publication-type="article">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wyse Jackson</surname>
              <given-names>Peter</given-names>
            </name>
            <name name-style="western">
              <surname>Miller</surname>
              <given-names>James S.</given-names>
            </name>
          </person-group>
          <year>2015</year>
          <article-title>Developing a World Flora Online - a 2020 challenge to the world's botanists from the international community</article-title>
          <source>Rodriguésia</source>
          <volume>66</volume>
          <issue>4</issue>
          <fpage>939</fpage>
          <lpage>946</lpage>
          <pub-id pub-id-type="doi">10.1590/2175-7860201566402</pub-id>
        </element-citation>
      </ref>
    </ref-list>
  </back>
  <floats-group>
    <fig id="F13723683" position="float" orientation="portrait">
      <object-id content-type="arpha">67D69687-B5A6-5595-AC5E-D5A1188E496E</object-id>
      <object-id content-type="doi">10.3897/BDJ.14.e184830.figure1</object-id>
      <label>Figure 1.</label>
      <caption>
        <p>“Taxon Identifiers”. Source: <italic>Helianthus</italic> L. in GBIF Secretariat (2023). GBIF Backbone Taxonomy. Checklist dataset <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.15468/39omei">https://doi.org/10.15468/39omei</ext-link> accessed via GBIF.org on 28-09-2025 (Source of data: Wikidata <ext-link ext-link-type="uri" xlink:href="https://www.wikidata.org/wiki/Q26949"><underline>https://www.wikidata.org/wiki/Q26949</underline></ext-link>).</p>
      </caption>
      <graphic xlink:href="bdj-14-e184830-g001.png" position="float" id="oo_1480847.png" orientation="portrait" xlink:type="simple">
        <uri content-type="original_file">https://binary.pensoft.net/fig/1480847</uri>
      </graphic>
    </fig>
    <table-wrap id="T13723170" position="float" orientation="portrait">
      <label>Table 1.</label>
      <caption>
        <p>Definition of terms as used in this article.</p>
      </caption>
      <table rules="all" border="0">
        <tbody>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Aggregator</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">
              <bold>See</bold>
              <italic>Taxonomic aggregator</italic>
            </td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Aggregator services</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Online accessible services (interactive or as endpoints for computer-to-computer communication) provided by <italic>taxonomic aggregators</italic>. Here focused on <italic>name-matching services</italic>.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Associated data</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Data from a research or usage context that are linked to a <italic>scientific name</italic>.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Canonical name</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A <italic>scientific name</italic> without the corresponding author or author-year citation.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Data linkage</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Data linkage (or record linkage, <xref ref-type="bibr" rid="B13718375">Harron (2016)</xref>) is "the aggregation of data from different sources concerning the same entity or individual" (<xref ref-type="bibr" rid="B13715688">Vaccaro and Swerts 2022</xref>).</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Fuzzy matching</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A method to match scientific names that differ by some characters (<xref ref-type="bibr" rid="B13718347">Grenié et al. 2022</xref>).</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Local data</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A set of taxonomic names that a user wants to match against a <italic>taxonomic dataset</italic> using a <italic>name-matching service</italic>. The client side of name matching.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Local user</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">The person or team using a <italic>name-matching service</italic>.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Metadata</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Data items that describe the content of datasets and the functionality of matching services, so that filters can be used to select them.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Name-ID</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Name-Identifier: A number or code that is assigned to a scientific name in a taxonomic dataset, independent of its nomenclatural or taxonomic acceptance, for example, “wfo-0000481185”. A name-ID becomes resolvable if it includes or can be paired with a protocol to access an Internet resource (e.g. <ext-link ext-link-type="uri" xlink:href="http://www.worldfloraonline.org/taxon/wfo-0000481185">http://www.worldfloraonline.org/taxon/wfo-0000481185</ext-link>). A "persistent" identifier is designed to remain stable over time.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Name matching</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">The process of aligning a <italic>scientific name</italic> string with one in a <italic>taxonomic dataset</italic>, resulting in either an exact match or a candidate list of similar names (fuzzy matching).</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Name-matching service</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">An <italic>aggregator service</italic> that allows to match scientific name strings from <italic>local data</italic> to one or more taxonomic datasets.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Nomenclator</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A <italic>taxonomic dataset</italic> that is restricted to information about the <italic>scientific name</italic> itself, for example, its correct spelling or validity according to rules fixed in the international codes of nomenclature. The designation “taxonomic” for a dataset that is essentially only referring to nomenclature is used here for convenience.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Scientific name</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A name formed in accordance with the international rules of nomenclature (for animals, for algae, fungi and plants, for bacteria and for viruses different codes apply).</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Synonym</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A <italic>scientific name</italic> that is not accepted for a taxon, but recognised as belonging to one. Non-acceptance may have nomenclatural reasons (species now in a different genus, older name has same type specimen, name was not adhering to the rules when published). Or a name may have been the name of a taxon that taxonomists now consider to fall into the circumscription of another (accepted) taxon.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Taxonomic aggregator</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Here: Online accessible databases that compile taxonomic information from multiple sources into a <italic>taxonomic dataset</italic> or act as a repository hosting <italic>taxonomic datasets</italic> from multiple sources.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Taxonomic dataset</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">Here: structured lists of <italic>scientific names</italic> hosted by a <italic>taxonomic aggregator</italic>. With the exception of <italic>nomenclators</italic>, they typically present a hierarchical, tree-like taxonomy (classification) in which each taxon represents a node and each <italic>scientific name</italic> is either assigned as the accepted name of a taxon or treated as a synonym (except in cases where the name exists, but cannot currently be resolved). This term largely corresponds to the term Taxonomic Database used by <xref ref-type="bibr" rid="B13718347">Grenié et al. 2022</xref>.</td>
          </tr>
          <tr>
            <td rowspan="1" colspan="1">
              <italic>
                <bold>Taxonomic group</bold>
              </italic>
            </td>
            <td rowspan="1" colspan="1">A broad term to describe a group of taxa or taxonomic ranks at which people work (<xref ref-type="bibr" rid="B13718347">Grenié et al. 2022</xref>), for example, plants, fungi, animals.</td>
          </tr>
        </tbody>
      </table>
    </table-wrap>
  </floats-group>
</article>
