<?xml version="1.0" encoding="UTF-8"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:lang="en">
  <teiHeader>
    <fileDesc>
      <titleStmt>
        <title>TYGS and LPSN: a database tandem for fast and reliable genome-based classification and nomenclature of prokaryotes</title>
        <author>Jan P. Meier‐Kolthoff</author>
        <author>J. Sarda Carbasse</author>
        <author>Rosa L Peinado-Olarte</author>
        <author>Markus Göker</author>
      </titleStmt>
      <publicationStmt>
        <p>Tag layer of the DHSS Meta-Tagging Project. The article text is reproduced from the
           staged copy named in sourceDesc and is not altered; the tags are held separately in
           standOff so that overlapping and nested spans are preserved.</p>
      </publicationStmt>
      <sourceDesc>
        <bibl>
          <title>TYGS and LPSN: a database tandem for fast and reliable genome-based classification and nomenclature of prokaryotes</title>
          <date>2022</date>
          <publisher>Nucleic Acids Research</publisher>
          <idno type="DOI">10.1093/nar/gkab902</idno>
          
          <idno type="record">meier-kolthoff2022-tygs-and-lpsn-a-database-tandem-fo</idno>
          <note type="staged-file">meier-kolthoff2022-tygs-and-lpsn-a-database-tandem-fo.txt, the project's staged copy</note>
          <note type="text-sha1">47b333b3ea234545300ec8c3c54572fd4b2b0222</note>
          <note type="rights">cc-by</note>
        </bibl>
      </sourceDesc>
    </fileDesc>
    <profileDesc>
      <textClass><keywords><term>biology</term></keywords></textClass>
      <particDesc>
        <person xml:id="paper"><p>the paper's own words</p></person>
        <person xml:id="tagger"><p>the tag layer; a sentence written by the tagger about the
          paper, always anchored to a quotation but not itself a quotation</p></person>
      </particDesc>
    </profileDesc>
    <revisionDesc>
      <change when="2026-10-06"
              who="build_paper_edition.py">61 spans located by searching the stored text for the quote's exact words, allowing any whitespace between them</change>
    </revisionDesc>
  </teiHeader>
  <standOff>
    <spanGrp type="tags">
      <span xml:id="t0" from="#a1" to="#a2" type="object_of_study" ana="#object_of_study" resp="#paper">A REGISTER OF WHICH NAMES HAVE LEGAL STANDING, PAIRED WITH A SERVICE THAT DECIDES CLASSIFICATION FROM A GENOME - the List of Prokaryotic names with Standing in Nomenclature and the Type (Strain) Genome Server, run as one interconnected pair at the DSMZ</span>
      <span xml:id="t1" from="#a3" to="#a4" type="research_question" ana="#research_question" resp="#paper">how to keep a nomenclature register and a genome-based classifier in step when names are proposed faster than they are validated and 99% of the organisms have no valid name at all</span>
      <span xml:id="t2" from="#a19" to="#a20" type="contribution" ana="#contribution" resp="#paper">an expanded LPSN that now lists names WITHOUT standing and marks them as such, an API and CSV export for both platforms, and TYGS improvements for choosing the closest type strains</span>
      <span xml:id="t3" from="#a21" to="#a22" type="claim_type" ana="#claim_type" resp="#paper">method</span>
      <span xml:id="t4" from="#a5" to="#a6" type="phenomenon" ana="#phenomenon" resp="#paper">a code under which a name either is or is not validly published, applied to a domain where the naming rate is rising, the geography of naming is shifting and the type material itself is under debate</span>
      <span xml:id="t5" from="#a21" to="#a22" type="method" ana="#method" resp="#paper">system-or-tool-building<term>system-or-tool-building</term></span>
      <span xml:id="t6" from="#a3" to="#a4" type="mechanisms" ana="#mechanisms[0]" resp="#tagger" cert="0.95">A NAME EITHER HAS LEGAL STANDING OR IT HAS NONE, AND 99% OF THE ORGANISMS HAVE NONE: `The global prokaryotic diversity is estimated to encompass 0.8-1.6 MILLION SPECIES of which currently ONLY ABOUT 1% have a name that is VALIDLY PUBLISHED under the ICNP` - and `The cornerstone of the ICNP is the status of taxon names as being validly published; other names have no claim to recognition under this code.` The corpus holds committees that vote and codes that classify; this is a code that confers a STATUS, and the status is binary</span>
      <span xml:id="t7" from="#a19" to="#a20" type="mechanisms" ana="#mechanisms[1]" resp="#tagger" cert="0.95">AND THE REGISTER NOW LISTS THE NAMES THAT HAVE NO STANDING, BECAUSE ABSENCE IS AMBIGUOUS: `An even more fundamental advantage of including not validly published names is that it adds clarity. If a name is shown on LPSN and explicitly marked as not being validly published, this leaves no doubt with regard to its status, as opposed to just not showing the name at all.` A working solution to `an empty state is not an instance` - the difference between a name that failed and a name nobody entered, made visible on the page</span>
      <span xml:id="t8" from="#a17" to="#a18" type="mechanisms" ana="#mechanisms[2]" resp="#tagger" cert="0.95">AND THEY CAMPAIGN ON IT: `The storage of not validly published names in LPSN allows for conducting campaigns to increase the rate of validation. As of July 2021, ALMOST 900 E-MAILS WERE SENT to corresponding authors to inform them about names proposed by them that as yet have no claim to recognition under the ICNP, COVERING &gt;1500 NAMES.` A register that writes to the authors of the rows it holds</span>
      <span xml:id="t9" from="#a15" to="#a16" type="mechanisms" ana="#mechanisms[3]" resp="#tagger" cert="0.95">AND STANDING CAN BE LOST RETROSPECTIVELY, AND MANY AUTHORS DO NOT KNOW IT EXISTS: `many names with an effective publication outside IJSEM are validated at a later date anyway ... Conversely, names supposed to be validly published may later on be recognized as not having met the necessary requirements. Moreover, not all taxonomist are aware of the need for validation.` The status moves in both directions and is not self-announcing</span>
      <span xml:id="t10" from="#a23" to="#a24" type="mechanisms" ana="#mechanisms[4]" resp="#tagger" cert="0.95">AND THE COUNTERFACTUAL IS PUBLISHED BESIDE THE NAME: &#x27;comments about the conditions under which a name would be regarded as the correct name if it is not currently so regarded by LPSN. The latter change is supposed to improve the understanding of the difference between nomenclature and classification, which may puzzle many microbiologists.&#x27; A field saying when a verdict would change, in the wild - the row states what would have to be true for its own verdict to change</span>
      <span xml:id="t11" from="#a9" to="#a10" type="mechanisms" ana="#mechanisms[5]" resp="#tagger" cert="0.95">AND THE NAME IS ANCHORED TO A PHYSICAL SPECIMEN, PERMANENTLY: `The nomenclatural type is the entity with which A taxon name is permanently associated. In the cases of prokaryotic species and subspecies, the nomenclatural type is the type strain. Cultures of type strains thus firmly connect taxon names and genome sequences.` Our anchors point at a span of text; theirs point at a living culture in a collection</span>
      <span xml:id="t12" from="#a31" to="#a32" type="mechanisms" ana="#mechanisms[6]" resp="#tagger" cert="0.95">AND AN ATTEMPT TO LET A GENOME BE THE ANCHOR FAILED: `While A recent attempt to modify the ICNP to allow for using genome sequences as nomenclatural type was unsuccessful, alternative solutions to the perceived underlying problem are currently actively debated.` The question of WHAT MAY SERVE AS THE ANCHOR OF A NAME, put to a vote and rejected - and the consequence is that a species with no cultivable strain cannot be named at all</span>
      <span xml:id="t13" from="#a21" to="#a22" type="mechanisms" ana="#mechanisms[7]" resp="#tagger" cert="0.95">AND THE INCLUSION CRITERION IS A RULE OF THE CODE RATHER THAN AN EDITORIAL JUDGEMENT: `a web form for submission was added to LPSN that allows for anonymous suggestions of taxon names ... The inclusion criterion is the presence of an effective publication as defined by the ICNP.` Anonymous submission with a code-defined gate: who proposes is unrestricted, what qualifies is not</span>
      <span xml:id="t14" from="#a13" to="#a14" type="mechanisms" ana="#mechanisms[8]" resp="#tagger" cert="0.95">AND ONE GROUP IS GOVERNED BY TWO CODES AT ONCE: the register adds `names of Cyanobacteria validly published under the ICN (International Code of Nomenclature for algae, fungi and plants), in anticipation of the recent changes to the ICNP` - so a name&#x27;s standing depends on which code you ask, and the register has to hold both answers</span>
      <span xml:id="t15" from="#a29" to="#a30" type="mechanisms" ana="#mechanisms[9]" resp="#tagger" cert="0.95">AND THE RIVAL INDEX IS INCONSISTENT WITH ITSELF ACROSS IMPLEMENTATIONS: `the dDDH approach was shown to OUTPERFORM the `AVERAGE NUCLEOTIDE IDENTITY` (ANI) approach ... More recently, `ANI` was found to yield results that are inconsistent across its various implementations due to a lack of standardization.` One named measure, several programs, different numbers - a species boundary that depends on which implementation you ran</span>
      <span xml:id="t16" from="#a27" to="#a28" type="mechanisms" ana="#mechanisms[10]" resp="#tagger" cert="0.95">AND A NEIGHBOURING RESOURCE&#x27;S BREADTH IS ITS HAZARD: `other platforms such as EzBioCloud may provide access to A BROADER SELECTION OF `REFERENCE GENOMES`, including non-type strains, these are to the best of our knowledge frequently confused or misinterpreted as type strains and may thus lead to taxonomic misinterpretations.` A category error made possible by a database that does not mark the distinction the code turns on</span>
      <span xml:id="t17" from="#a25" to="#a26" type="mechanisms" ana="#mechanisms[11]" resp="#tagger" cert="0.95">AND THE MACHINE-READABLE EXPORT IS SCOPED BY A SUPERSEDED SPREADSHEET: `The LPSN CSV file needed to be downwards compatible with that Excel file as far as possible, hence it was and is intended to contain only the names of genera, species and subspecies validly published under the ICNP.` So the download excludes exactly the not-validly-published names the website added for clarity - a reader sees the absence marked and a program does not, and the reason is a format from a service that no longer exists</span>
      <span xml:id="t18" from="#a21" to="#a22" type="limitations" ana="#limitations[0]" resp="#tagger" cert="0.95">THE COVERAGE OF NAMES WITHOUT STANDING CANNOT BE COMPLETE, AND THEY SAY WHY: `Because they are not centrally collected in a journal such as IJSEM, the coverage of names by LPSN that have an effective publication but are not validly published under the code cannot be expected to be complete. LPSN attempts to focus on names that are in use, i.e. are found in the literature or in other databases.` The invalid half of the register is a convenience sample of what people actually write</span>
      <span xml:id="t19" from="#a11" to="#a12" type="limitations" ana="#limitations[1]" resp="#tagger" cert="0.95">AND THE GROWTH IS IN THE DATA, NOT IN THE UNDERSTANDING: `the overall number of names that become validly published per year shows an ever-increasing trend. One of the challenges of nomenclature-related databases is apparently the sheer increase of the volume of the data to be considered` - against 1% of estimated species named at all, so the rate rises while the fraction barely moves</span>
      <span xml:id="t20" from="#a7" to="#a8" type="limitations" ana="#limitations[2]" resp="#tagger" cert="0.95">AND THE SCALE IS SMALL AGAINST THE DOMAIN: `the LPSN database provides ... &gt;26K NAMES of any category and &gt;21K SPECIES NAMES validly published under the ICNP ... the TYGS database contains &gt;15K TYPE-STRAIN GENOMES.` Twenty-one thousand named species against an estimated 0.8-1.6 million</span>
      <span xml:id="t21" from="#a1" to="#a2" type="limitations" ana="#limitations[3]" resp="#tagger" cert="0.95">AND THE TWO PLATFORMS ARE ONE INSTITUTION&#x27;S: both LPSN and TYGS are run at the Leibniz Institute DSMZ by the same four authors, and the paper&#x27;s own recommendation is to migrate users off the earlier GGDC tool onto TYGS. The register of what counts as a name and the service that supplies the evidence for classification share a roof</span>
      <span xml:id="t22" from="#a19" to="#a20" type="controls" ana="#controls[0]" resp="#tagger" cert="0.95">showing names that are NOT validly published and marking them as such, rather than omitting them<note>eliminates: the ambiguity between a name that failed the code and a name nobody entered · outcome: held</note></span>
      <span xml:id="t23" from="#a9" to="#a10" type="controls" ana="#controls[1]" resp="#tagger" cert="0.95">restricting the classification evidence to genomes of VERIFIED TYPE STRAINS rather than reference genomes<note>eliminates: a non-type genome standing in for the nomenclatural type and carrying a name it has no claim to · outcome: held</note></span>
      <span xml:id="t24" from="#a25" to="#a26" type="controls" ana="#controls[2]" resp="#tagger" cert="0.95">keeping the CSV export downwards compatible with the superseded PNU Excel file<note>eliminates: breaking existing pipelines - at the cost of excluding from the export exactly the not-validly-published names the website added for clarity · outcome: partial</note></span>
      <span xml:id="t25" from="#a1" to="#a2" type="concepts" ana="#concepts[0]" resp="#paper" cert="0.95">LPSN<term>LPSN</term></span>
      <span xml:id="t26" from="#a1" to="#a2" type="concepts" ana="#concepts[1]" resp="#paper" cert="0.95">an expert-curated authoritative resource for prokaryotic nomenclature<term>an expert-curated authoritative resource for prokaryotic nomenclature</term></span>
      <span xml:id="t27" from="#a1" to="#a2" type="concepts" ana="#concepts[2]" resp="#paper" cert="0.95">TYGS<term>TYGS</term></span>
      <span xml:id="t28" from="#a1" to="#a2" type="concepts" ana="#concepts[3]" resp="#paper" cert="0.95">a high-throughput platform for accurate genome-based taxonomy<term>a high-throughput platform for accurate genome-based taxonomy</term></span>
      <span xml:id="t29" from="#a21" to="#a22" type="concepts" ana="#concepts[4]" resp="#paper" cert="0.95">The inclusion criterion<term>The inclusion criterion</term></span>
      <span xml:id="t30" from="#a21" to="#a22" type="concepts" ana="#concepts[5]" resp="#paper" cert="0.95">the presence of an effective publication<term>the presence of an effective publication</term></span>
      <span xml:id="t31" from="#a23" to="#a24" type="concepts" ana="#concepts[6]" resp="#paper" cert="0.95">nomenclature<term>nomenclature</term></span>
      <span xml:id="t32" from="#a23" to="#a24" type="concepts" ana="#concepts[7]" resp="#paper" cert="0.95">classification<term>classification</term></span>
      <span xml:id="t33" from="#a11" to="#a12" type="concepts" ana="#concepts[8]" resp="#paper" cert="0.95">emendations<term>emendations</term></span>
      <span xml:id="t34" from="#a11" to="#a12" type="concepts" ana="#concepts[9]" resp="#paper" cert="0.95">the availability of genome sequences of type strains<term>the availability of genome sequences of type strains</term></span>
      <span xml:id="t35" from="#a5" to="#a6" type="senses" ana="#senses[0]" resp="#tagger" cert="0.95">`validly published` - the ICNP status a name either has or has not; names without it `have no claim to recognition under this code`, and the status can be granted late or withdrawn on review</span>
      <span xml:id="t36" from="#a21" to="#a22" type="senses" ana="#senses[1]" resp="#tagger" cert="0.95">`effective publication` - the weaker condition that gets a name INTO the register without standing; it is `The inclusion criterion` for LPSN, not for the code</span>
      <span xml:id="t37" from="#a9" to="#a10" type="senses" ana="#senses[2]" resp="#tagger" cert="0.95">`nomenclatural type` - `the entity with which a taxon name is permanently associated`; for prokaryotes a living type STRAIN, and an attempt to admit a genome sequence instead was rejected</span>
      <span xml:id="t38" from="#a23" to="#a24" type="senses" ana="#senses[3]" resp="#tagger" cert="0.95">`correct name` - LPSN&#x27;s current judgement, published alongside `the conditions under which a name would be regarded as the correct name if it is not currently so regarded`</span>
      <span xml:id="t39" from="#a1" to="#a2" type="claim_relations" ana="#claim_relations[0]" resp="#tagger" cert="0.95">extends → the 2020 relaunch of LPSN at the DSMZ and the original TYGS paper, both by overlapping authors - this is the joint update of the two</span>
      <span xml:id="t40" from="#a29" to="#a30" type="claim_relations" ana="#claim_relations[1]" resp="#tagger" cert="0.95">critiques → the average nucleotide identity (ANI) index, which &#x27;was found to yield results that are inconsistent across its various implementations due to a lack of standardization&#x27;</span>
      <span xml:id="t41" from="#a27" to="#a28" type="claim_relations" ana="#claim_relations[2]" resp="#tagger" cert="0.95">critiques → databases offering &#x27;reference genomes&#x27; including non-type strains, which are &#x27;frequently confused or misinterpreted as type strains&#x27;</span>
      <span xml:id="t42" from="#a1" to="#a2" type="concept_edges" ana="#concept_edges[0]" resp="#tagger" cert="0.95">LPSN —is-a→ an expert-curated authoritative resource for prokaryotic nomenclature<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: &#x27;The List of Prokaryotic names with Standing in Nomenclature (LPSN) is an expert-curated authoritative resource for prokaryotic nomenclature.&#x27; The word &#x27;authoritative&#x27; is doing work: the register does not merely record which names have standing, it is where the field looks to find out - and the same institution runs the classifier that supplies the evidence · the relation stated: LPSN is presented as the authoritative register for prokaryotic names - expert curation is part of the claim, not an implementation detail</note><term>LPSN</term><term>an expert-curated authoritative resource for prokaryotic nomenclature</term></span>
      <span xml:id="t43" from="#a1" to="#a2" type="concept_edges" ana="#concept_edges[1]" resp="#tagger" cert="0.95">TYGS —is-a→ a high-throughput platform for accurate genome-based taxonomy<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: &#x27;The Type (Strain) Genome Server (TYGS) is a high-throughput platform for accurate genome-based taxonomy.&#x27; The pairing is the point: one platform decides what a thing IS and the other decides what it may be CALLED, and the paper&#x27;s argument is that neither works well without the other · the relation stated: TYGS is the classification side of the pair - genomes in, phylogenies and species boundaries out</note><term>TYGS</term><term>a high-throughput platform for accurate genome-based taxonomy</term></span>
      <span xml:id="t44" from="#a21" to="#a22" type="concept_edges" ana="#concept_edges[2]" resp="#tagger" cert="0.95">The inclusion criterion —operationalised-as→ the presence of an effective publication<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: &#x27;a web form for submission was added to LPSN that allows for anonymous suggestions of taxon names ... The inclusion criterion is the presence of an effective publication as defined by the ICNP.&#x27; Who proposes is unrestricted; what qualifies is not. And note the two-tier design: effective publication gets a name INTO the register, valid publication gives it STANDING, and the register shows both states · the relation stated: what enters the register is decided by a condition of the ICNP, not by an editor - so anonymous submissions are accepted and the gate is the code</note><term>The inclusion criterion</term><term>the presence of an effective publication</term></span>
      <span xml:id="t45" from="#a23" to="#a24" type="concept_edges" ana="#concept_edges[3]" resp="#tagger" cert="0.95">nomenclature —distinct-from→ classification<note>the relation itself is separately evidenced · strength of the relation: 0.95 · note: &#x27;The latter change is supposed to improve the understanding of the difference between nomenclature and classification, which may puzzle many microbiologists.&#x27; The change in question is publishing, beside a name, &#x27;the conditions under which a name would be regarded as the correct name if it is not currently so regarded&#x27; - a row that states what would have to be true for its own verdict to change · the relation stated: what a taxon may be called and where a taxon sits are separate questions, and the register publishes comments specifically to keep them apart</note><term>nomenclature</term><term>classification</term></span>
      <span xml:id="t46" from="#a11" to="#a12" type="concept_edges" ana="#concept_edges[4]" resp="#tagger" cert="0.95">the availability of genome sequences of type strains —causes→ emendations<note>direction on the measure: increases · the relation itself is separately evidenced · strength of the relation: 0.95 · note: &#x27;The relative and absolute number of emendations also shows an increasing trend, caused by the availability of genome sequences of type strains.&#x27; A new instrument reaching back into names already settled - the same shape as bishop2017&#x27;s discontinuity worry and staab2017&#x27;s index terms, except here the corrections are counted per year and rising · the relation stated: genome sequences of type strains are driving a rising rate of formal corrections to already-valid names</note><term>the availability of genome sequences of type strains</term><term>emendations</term></span>
      <span xml:id="t47" from="#a3" to="#a4" type="content_tags" ana="#content_tags.findings[0]" resp="#tagger" cert="0.95">A BINARY LEGAL STATUS, AND 99% OF THE ORGANISMS DO NOT HAVE IT: `0.8-1.6 MILLION SPECIES of which currently ONLY ABOUT 1% have a name that is VALIDLY PUBLISHED`<term>A BINARY LEGAL STATUS, AND 99% OF THE ORGANISMS DO NOT HAVE IT: `0.8-1.6 MILLION SPECIES of which currently ONLY ABOUT 1% have a name that is VALIDLY PUBLISHED`</term></span>
      <span xml:id="t48" from="#a19" to="#a20" type="content_tags" ana="#content_tags.findings[1]" resp="#tagger" cert="0.95">AND THE REGISTER LISTS THE NAMES WITHOUT STANDING BECAUSE ABSENCE IS AMBIGUOUS: `If a name is shown ... and explicitly marked as not being validly published, this leaves no doubt with regard to its status, as opposed to just not showing the name at all`<term>AND THE REGISTER LISTS THE NAMES WITHOUT STANDING BECAUSE ABSENCE IS AMBIGUOUS: `If a name is shown ... and explicitly marked as not being validly published, this leaves no doubt with regard to its status, as opposed to just not showing the name at all`</term></span>
      <span xml:id="t49" from="#a23" to="#a24" type="content_tags" ana="#content_tags.findings[2]" resp="#tagger" cert="0.95">AND THE COUNTERFACTUAL IS PUBLISHED BESIDE THE NAME: `comments about the conditions under which a name would be regarded as the correct name if it is not currently so regarded`<term>AND THE COUNTERFACTUAL IS PUBLISHED BESIDE THE NAME: `comments about the conditions under which a name would be regarded as the correct name if it is not currently so regarded`</term></span>
      <span xml:id="t50" from="#a31" to="#a32" type="content_tags" ana="#content_tags.findings[3]" resp="#tagger" cert="0.95">AND AN ATTEMPT TO LET A GENOME BE THE NOMENCLATURAL TYPE FAILED: `a recent attempt to modify the ICNP to allow for using genome sequences as nomenclatural type was unsuccessful`<term>AND AN ATTEMPT TO LET A GENOME BE THE NOMENCLATURAL TYPE FAILED: `a recent attempt to modify the ICNP to allow for using genome sequences as nomenclatural type was unsuccessful`</term></span>
      <span xml:id="t51" from="#a29" to="#a30" type="content_tags" ana="#content_tags.findings[4]" resp="#tagger" cert="0.95">AND THE RIVAL INDEX DISAGREES WITH ITSELF: `ANI WAS FOUND TO YIELD RESULTS THAT ARE INCONSISTENT ACROSS ITS VARIOUS IMPLEMENTATIONS DUE TO A LACK OF STANDARDIZATION`<term>AND THE RIVAL INDEX DISAGREES WITH ITSELF: `ANI WAS FOUND TO YIELD RESULTS THAT ARE INCONSISTENT ACROSS ITS VARIOUS IMPLEMENTATIONS DUE TO A LACK OF STANDARDIZATION`</term></span>
      <span xml:id="t52" from="#a25" to="#a26" type="content_tags" ana="#content_tags.findings[5]" resp="#tagger" cert="0.95">the LPSN CSV, kept downwards compatible with a superseded Excel file, contains only validly published names<term>the LPSN CSV, kept downwards compatible with a superseded Excel file, contains only validly published names</term></span>
      <span xml:id="t53" from="#a17" to="#a18" type="content_tags" ana="#content_tags.findings[6]" resp="#tagger" cert="0.95">AND 900 EMAILS WENT OUT ABOUT 1,500 NAMES WITH NO CLAIM TO RECOGNITION - a register that writes to the authors of its own rows<term>AND 900 EMAILS WENT OUT ABOUT 1,500 NAMES WITH NO CLAIM TO RECOGNITION - a register that writes to the authors of its own rows</term></span>
      <span xml:id="t54" from="#a5" to="#a6" type="content_tags" ana="#content_tags.definitions[0]" resp="#tagger" cert="0.95">`The cornerstone of the ICNP is the status of taxon names as being validly published; other names have no claim to recognition under this code`<term>validly published</term></span>
      <span xml:id="t55" from="#a9" to="#a10" type="content_tags" ana="#content_tags.definitions[1]" resp="#tagger" cert="0.95">`the entity with which a taxon name is permanently associated` - for prokaryotic species and subspecies, the type strain<term>nomenclatural type</term></span>
      <span xml:id="t56" from="#a3" to="#a4" type="content_tags" ana="#content_tags.quantities[0]" resp="#tagger" cert="0.95">`microbial life still remains largely unknown and unconnected to the only system of nomenclature accepted by the majority of microbiologists`<term>named fraction of estimated prokaryotic diversity</term></span>
      <span xml:id="t57" from="#a7" to="#a8" type="content_tags" ana="#content_tags.quantities[1]" resp="#tagger" cert="0.95">27,000 distinct analyses by 3,700 users, involving 15 million genome comparisons<term>the two databases</term></span>
      <span xml:id="t58" from="#a17" to="#a18" type="content_tags" ana="#content_tags.quantities[2]" resp="#tagger" cert="0.95">sent to corresponding authors about names `that as yet have no claim to recognition` under the code<term>the validation campaign</term></span>
      <span xml:id="t59" from="#a29" to="#a30" type="content_tags" ana="#content_tags.statistics[0]" resp="#tagger" cert="0.95">`the dDDH approach was shown to OUTPERFORM the AVERAGE NUCLEOTIDE IDENTITY (ANI) approach, which is also frequently used ... as an alternative OGRI index. More recently, ANI WAS FOUND TO YIELD RESULTS THAT ARE INCONSISTENT ACROSS ITS VARIOUS IMPLEMENTATIONS DUE TO A LACK OF STANDARDIZATION.` One named index, several implementations, different answers - and the answer decides whether two isolates are one species<term>a species boundary that depends on which program computed it</term></span>
      <span xml:id="t60" from="#a15" to="#a16" type="content_tags" ana="#content_tags.variables[0]" resp="#tagger" cert="0.95">the binary status the whole register turns on - a name has it or it does not, it can be granted late (`many names ... are validated at a later date anyway`) and it can be withdrawn (`names supposed to be validly published may later on be recognized as not having met the necessary requirements`)<term>standing in nomenclature</term></span>
    </spanGrp>
  </standOff>
  <text>
    <body>
        <p><anchor xml:id="a0"/> 4 nar Nucleic Acids Research Nucleic Acids Res Oxford University Press PMC8728197 8728197 8728197 34634793 10.1093/nar/gkab902 TYGS and LPSN: a database tandem for fast and reliable genome-based classification and nomenclature of prokaryotes Meier-Kolthoff Jan P 1 ✉ Carbasse Joaquim Sardà 2 Peinado-Olarte Rosa L 3 Göker Markus 4 1  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany 2  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany 3  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany 4  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany ✉ To whom correspondence should be addressed. Tel: +49 531 2616 424; Email: jan.meier-kolthoff@dsmz.de</p>
        <p>11 10 2021 50 D1 D801 D801–D807 5 1 2022 © The Author(s) 2021. Published by Oxford University Press on behalf of Nucleic Acids Research. This is an Open Access article distributed under the terms of the Creative Commons Attribution License ( https://creativecommons.org/licenses/by/4.0/ ), which permits unrestricted reuse, distribution, and reproduction in any medium, provided the original work is properly cited. Abstract</p>
        <p>Microbial systematics is heavily influenced by genome-based methods and challenged by an ever increasing number of taxon names and associated sequences in public data repositories. This poses a challenge for database systems, particularly since it is obviously advantageous if such data are based on a globally recognized approach to manage names, such as the International Code of Nomenclature of Prokaryotes. The amount of data can only be handled if accurate and reliable high-throughput platforms are available that are able to both comply with this demand and to keep track of all changes in an efficient and flexible way. <anchor xml:id="a1"/>The List of Prokaryotic names with Standing in Nomenclature (LPSN) is an expert-curated authoritative resource for prokaryotic nomenclature and is available at https://lpsn.dsmz.de . The Type (Strain) Genome Server (TYGS) is a high-throughput platform for accurate genome-based taxonomy and is available at https://tygs.dsmz.de .<anchor xml:id="a2"/> We here present important updates of these two previously introduced, heavily interconnected platforms for taxonomic nomenclature and classification, including new high-level facilities providing access to bioinformatic algorithms, a considerable expansion of the database content, and new ways to easily access the data.</p>
        <p>status released display-pdf yes is-olf no is-manuscript no is-preprint no is-journal-matter no is-scanned no is-retracted no Accepted 2021 Sep 22; Revised 2021 Sep 18; Received 2021 Aug 20; Collection date 2022 Jan 7.</p>
        <p>INTRODUCTION</p>
        <p><anchor xml:id="a3"/>The global prokaryotic diversity is estimated to encompass 0.8–1.6 million species ( 1 ) of which currently only about 1% ( 2 ) have a name that is validly published under the International Code of Nomenclature of Prokaryotes (ICNP) ( 3 ). Even though these estimates are likely to fluctuate, microbial life still remains largely unknown and unconnected to the only system of nomenclature accepted by the majority of microbiologists, the ICNP.<anchor xml:id="a4"/> But a continuous and systematic understanding of this large genetic and enzymatic reservoir is necessary to further elucidate the biological mechanisms affecting important topics such as the global geochemical cycles, public health and biotechnology.</p>
        <p>For more than a century, microbial taxonomy is dedicated to the characterization, classification and nomenclature of microbial life. The data acquired through characterization ( 4 ), which presently significantly relies on genome-based approaches ( 5 ), are used to establish the classification of microbes. <anchor xml:id="a5"/>Classification in turn needs an internationally accepted system of nomenclature to unambiguously assign names to taxa ( 3 ). The cornerstone of the ICNP is the status of taxon names as being validly published; other names have no claim to recognition under this code<anchor xml:id="a6"/> ( 3 ).</p>
        <p>Due to the fast-paced changes in prokaryotic nomenclature and the continued influx of newly proposed names, expert-curated and at least partially automated database systems are needed to keep track of these processes. One of the most influential and authoritative resources in this regard is the List of Prokaryotic names with Standing in Nomenclature (LPSN), which was first introduced more than two decades ago as a manually curated database ( 6 ) and maintained over the years ( 7 ). Since 2020 LPSN is located at https://lpsn.dsmz.de at the Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures ( 2 ). The move from the previous platform to the DSMZ was accompanied by the establishment of a database infrastructure, of automated data import routines and of a database-driven web interface ( 2 ). Pages for individual taxon names were equipped with information on etymology, type-strain deposits, 16S rRNA gene sequences in FASTA format, INSDC 16S rRNA gene accession numbers, taxonomic and nomenclatural status and many notes ( 2 ).</p>
        <p>Taxonomic classification is currently strongly influenced by genome-scale data and related methods ( 8–15 ). The ever-increasing growth of genome data ( 16 ) demands technical solutions for efficient, reproducible and standardized taxonomic analyses. Comparisons with the genome sequences of type strains are mandatory when classifying novel strains ( 4 ). Hence, a reliable mapping between type strains, genome sequences and taxon names has to be established.</p>
        <p>To address these requirements, the Type (Strain) Genome Server (TYGS) was previously introduced as a large database of curated type-strain genomes combined with selected metadata and facilities for conducting truly genome-based taxonomic analyses in a high-throughput setup ( 17 ). Queries to the TYGS database, located at https://tygs.dsmz.de , are made with one to several uploaded genome sequences. The results include genome-scale phylogenies and state-of-the-art estimates for species and subspecies boundaries for both user-provided sequences and automatically determined closest type genome sequences. Metadata for these are provided to facilitate the taxonomic exploration of the outcome, including nomenclature, synonymy and associated taxonomic literature ( 17 ).</p>
        <p>In this study we present the current state of the heavily used TYGS and LPSN databases, including updates and improvements which were added since the last publications ( 2 , 17 ). The establishment of LPSN at the DSMZ allows for strongly interconnecting the two databases ( 2 , 17 ) to further increase their usability, a topic that is also addressed below.</p>
        <p>TYGS AND LPSN IN 2021</p>
        <p>The databases</p>
        <p><anchor xml:id="a7"/>As of July 2021, the LPSN database (Figure 1 ) provides a large variety of expert-curated nomenclatural data, including &gt;26k names of any category and &gt;21k species names validly published under the ICNP ( 3 ). At the time of writing, the TYGS database (Figure 1 ) contains &gt;15k type-strain genomes and was used by &gt;3.7k different users worldwide for conducting &gt;27k distinct analyses (Figure 2 ) involving 15M + genome comparisons.<anchor xml:id="a8"/></p>
        <p>Figure 1. Left, dependencies of the TYGS and LPSN platforms and relationships to the legacy GGDC platform and to the DSMZ gene phylogeny server. Right, description of the most relevant (partially shared) contents of the TYGS and LPSN databases.</p>
        <p>Figure 2. ( A ) statistics on the cumulative, non-linear growth of TYGS type-strain genome sequences per month. ( B ) non-cumulative number of TYGS job submissions per month since its establishment in 2019. Job submissions are grouped according to the top-level domain of the e-mail address included in each job submission. The top-level domain was matched to the country of origin wherever possible.</p>
        <p>The content of the TYGS and LPSN databases was introduced in previous publications ( 2 , 17 ) and is here only briefly recapitulated (Figure 1 ). The depicted database content reflects the focus of the two databases, which accordingly share many kinds of data.</p>
        <p>The authority of a taxon name reflects its original publication and thus links nomenclature and scientific literature. Synonymy of names is another key component of taxonomic information to which LPSN allows comprehensive access. <anchor xml:id="a9"/>The nomenclatural type is the entity with which a taxon name is permanently associated ( 3 ). In the cases of prokaryotic species and subspecies, the nomenclatural type is the type strain. Cultures of type strains thus firmly connect taxon names and genome sequences.</p>
        <p>Quality-checked ( 17 ) genome and proteome sequences of verified type strains are the starting point of TYGS analyses.<anchor xml:id="a10"/> Accurate intergenomic GBDP (Genome BLAST Distance Phylogeny) ( 18 ) distances and digital DNA:DNA hybridization (dDDH) values are calculated and stored in the TYGS database. Most of them are inferred well in advance of user requests to considerably accelerate the processing of these requests. The distances are used for phylogenetic inference and also form the basis for the dDDH method, one of the most widely used overall genome relatedness indices (OGRI) for in silico species delineation ( 18 , 19 ). Genome-scale and proteome-scale phylogenies, 16S rRNA gene trees and type-based clusterings at the species and subspecies levels are the data entries that represent the final step of the comprehensive genome-based taxonomic analyses available in the TYGS.</p>
        <p>Analyses on the DSMZ single-gene phylogeny server (Figure 1 ) can be triggered by the TYGS as well as via LPSN. The server calculates pairwise similarities ( 20 ), multiple sequence alignments ( 21 ) and phylogenetic trees under the maximum-likelihood ( 22 ) and maximum parsimony ( 23 ) criteria from single-gene data sets as introduced previously ( 24 ). The DSMZ single-gene phylogeny server is also contacted by the TYGS on user request to infer single-gene phylogenies from a comprehensive set of 16S rRNA gene sequences that may include closely related but not yet genome-sequenced type strains.</p>
        <p>New kinds of TYGS data and new TYGS facilities</p>
        <p>The initial release of the TYGS determined a set of type strains most closely related to a respective user sequence by using only 16S rRNA gene sequence distances ( 17 ). As not all user sequences contain an extractable 16S rRNA gene, the most closely related type-strain genomes are now also determined using intergenomic Mash distances ( 25 ), a fast initial approximation of intergenomic relatedness. The set of type-strain genomes having the smallest MASH distances among the entire TYGS database is combined with those having the smallest 16S rRNA gene distances. This approach also ensures that the most closely related type strains are chosen if the user genome sequence belongs to a group of organisms for which the 16S rRNA gene sequence does not properly resolve the phylogenetic relationships. However, the usage of 16S rRNA gene sequences remains highly relevant for detecting closely related type strains that have not yet been genome-sequenced.</p>
        <p>Mash distances are now also used to split job submissions that contain query genomes that are only remotely related. If otherwise such an analysis would result in the selection of distinct sets of closest type strain genomes and trigger taxonomically useless calculations. Subdivided submissions, if any, are accordingly indicated on the job confirmation page. This feature further improves the genome-based taxonomic analyses by determining efficient type strain selection in a variety of data situations.</p>
        <p>For very diverse datasets of strains, the average branch support even of a genome-scale phylogeny and even for a strain selection restricted as described above, might be too low when based on nucleotide sequences. We thus added the option to conduct an additional GBDP analysis using amino-acid sequences under the recommended settings ( 26 ), which automatically becomes available on the TYGS result page in case of insufficient support.</p>
        <p>It should be noted that the Genome-to-Genome Distance Calculator (GGDC) preceded the TYGS and is still one of the most popular online tools for the calculation of dDDH values for in silico (sub-)species delineation ( 18 , 19 ). Although the current GGDC version, 3.0, also incorporates several new features and optimizations from the previous years, the database-driven TYGS offers many more facilities, overall. Although GGDC and TYGS are equally reliable regarding species delineation, GGDC users are strongly advised to switch to the TYGS. In rare cases, the GGDC 3.0 can still be useful for specialized analyses but since a larger file upload cap can usually be requested via the TYGS feedback form, the TYGS is certainly the more comprehensive platform since its initial release.</p>
        <p>The series of publicly available pre-calculated TYGS result sets that can be accessed from the ‘Examples’ menu item on the TYGS main page demonstrates the new facilities listed above. All TYGS results are now also available within a compact, publication-ready PDF report.</p>
        <p>Each TYGS result usually includes links to external sites such as Bac Dive ( 27 ) and GenBank to provide further information on each used type strain. As a result of the move of LPSN to DSMZ, the preferred names of each type strain listed on the respective TYGS result page now link to the specific LPSN page of that species. Links to the Bac Dive database now point to the specific strain page whenever possible.</p>
        <p>Expansion of the scope</p>
        <p>The growth of the number of genome sequences in the TYGS database is shown in Figure 2 while the growth of the number of taxon names in the LPSN database is shown in Figure 3 . As for names validly published under the ICNP ( 3 ), the increase of names in LPSN and accordingly of type-strain genome sequences in the TYGS simply mirrors the increase of the rate of valid published names per year. <anchor xml:id="a11"/>The number of validly published names per country and year reflects the well-known shift of taxonomic activity to East Asian nations ( 28 ). The relative and absolute number of emendations also shows an increasing trend, caused by the availability of genome sequences of type strains ( 8–11 ). More importantly, the overall number of names that become validly published per year shows an ever-increasing trend. One of the challenges of nomenclature-related databases is apparently the sheer increase of the volume of the data to be considered.<anchor xml:id="a12"/></p>
        <p>Figure 3. ( A ) Number of new prokaryotic names included in LPSN grouped by year and taxonomic category and nomenclatural status (shades of blue, validly published under the ICNP; shades of red, not validly published). Left, all names; right, names currently regarded as correct name ( 3 ) in LPSN. ( B ) Number of new prokaryotic names validly published under the ICNP and number of emendations of such names included in LPSN, grouped by year and country of origin of the taxonomic study. Left, number of validly published names; right, number of emendations of such names. The country of origin of each study represents the country of origin of the author indicated as corresponding author including an e-mail address.</p>
        <p><anchor xml:id="a13"/>A major change regarding the selection of taxon names for inclusion in LPSN is the addition of names that are not validly published ( Candidatus names and other names), as well as of names of Cyanobacteria validly published under the ICN (International Code of Nomenclature for algae, fungi and plants), in anticipation of the recent changes to the ICNP ( 29 ).<anchor xml:id="a14"/> Whereas they do not have standing in nomenclature, the addition of names to LPSN that have an effective publication but are not validly published had started at an early stage ( 6 ), although the names were not linked to the hierarchical classification.</p>
        <p>An improved integration of not validly published names in LPSN reflects the inclusion of additional categories regulated under the rules of the ICNP ( 30 ) and the publication of lists of Candidatus names in the International Journal of Systematic and Evolutionary Microbiology (IJSEM) ( 31 ). This integration also has other advantages. <anchor xml:id="a15"/>For instance, many names with an effective publication outside IJSEM are validated at a later date anyway ( 3 ), hence their earlier consideration facilitates data analysis. Conversely, names supposed to be validly published may later on be recognized as not having met the necessary requirements ( 32 ). Moreover, not all taxonomist are aware of the need for validation<anchor xml:id="a16"/> ( 33 ). <anchor xml:id="a17"/>The storage of not validly published names in LPSN allows for conducting campaigns to increase the rate of validation. As of July 2021, almost 900 e-mails were sent to corresponding authors to inform them about names proposed by them that as yet have no claim to recognition under the ICNP ( 3 ), covering &gt;1500 names.<anchor xml:id="a18"/></p>
        <p><anchor xml:id="a19"/>An even more fundamental advantage of including not validly published names is that it adds clarity. If a name is shown on LPSN and explicitly marked as not being validly published, this leaves no doubt with regard to its status, as opposed to just not showing the name at all.<anchor xml:id="a20"/> Because they are not centrally collected in a journal such as IJSEM, the coverage of names by LPSN that have an effective publication but are not validly published under the code cannot be expected to be complete. LPSN attempts to focus on names that are in use, i.e. are found in the literature or in other databases. <anchor xml:id="a21"/>To improve the coverage, a web form for submission was added to LPSN that allows for anonymous suggestions of taxon names. Synonymy relationships between taxon names and assignments of child taxa to parent taxa (i.e, genera to families, families to orders etc.) can also be suggested. The inclusion criterion is the presence of an effective publication as defined by the ICNP ( 3 ).<anchor xml:id="a22"/></p>
        <p>New kinds of information on LPSN</p>
        <p>Apart from the constant addition of taxon names and associated information and the regular update of information provided by third parties, such as the risk-group assignments for species and subspecies ( 34 ), a variety of LPSN facilities and pages were established since the relaunch of the entire site at DSMZ ( 2 ). All of these pages are accessible through the LPSN navigation page.</p>
        <p>Greatly expanded and regularly updated pages on Frequently Asked Questions, nomenclature, etymology, and taxonomy and systematics provide access to the relevant literature. A variety of pages provide more specific etymological information on bacterial names. The LPSN glossary now contains more entries and more cross references; key terms related to the rules of nomenclature ( 3 ) have been augmented to explain critical issues. Special pages on Requests for an Opinion and Judicial Opinions ( 32 ) are also intended to increase nomenclatural literacy.</p>
        <p>The LPSN page on culture collections, which is augmented in parallel to the registering of type-strain deposits in LPSN, lists hundreds of biological resource centres. In addition to links and postal addresses the page now also contains country codes and WDCM (World Data Centre for Microorganisms) numbers to further ease the access to information on collections.</p>
        <p><anchor xml:id="a23"/>Comments on taxonomic terminology were added to LPSN for single taxon names where appropriate, as well as comments about the conditions under which a name would be regarded as the correct name if it is not currently so regarded by LPSN. The latter change is supposed to improve the understanding of the difference between nomenclature and classification, which may puzzle many microbiologists ( 35 ).<anchor xml:id="a24"/> LPSN now also includes a scoring based on genomic distances calculated by the TYGS ( 26 ). These comments highlight groups that may need a taxonomic revision.</p>
        <p>Improved access to the data</p>
        <p><anchor xml:id="a25"/>The LPSN CSV (comma-separated values) file became available for download once LPSN was established at DSMZ ( 2 ). An Excel file was previously offered by the PNU (Prokaryotic Nomenclature Up-to-date) service of DSMZ, which was superseded by the new LPSN. The LPSN CSV file needed to be downwards compatible with that Excel file as far as possible, hence it was and is intended to contain only the names of genera, species and subspecies validly published under the ICNP.<anchor xml:id="a26"/></p>
        <p>LPSN was augmented with an API (Application Programming Interface) to provide greater flexibility. The LPSN API is designed to be expandable in the future without creating backwards incompatibility. The LPSN API has a REST (Representational State Transfer) interface that allows for two kinds of searches and yields JSON (JavaScript Object Notation). Code examples and clients in two programming languages are provided inline.</p>
        <p>Users are advised to register for the LPSN mailing list because forthcoming changes to CSV download file or API are announced on this list in order to avoid severe incompatibilities with previous formats. The LPSN record numbers as used in the CSV files and in the API are also visible on each page to ease comparisons.</p>
        <p>The TYGS platform was similarly augmented with a REST API to allow users to download tabular results in the open interchange format JSON, phylogenetic results in either PhyloXML ( 36 ) or Newick format and scientific citations in BibTex format. Details on the API are available online and users are asked to follow the instructions on the TYGS API page on how and when to use the API.</p>
        <p>CONCLUSION</p>
        <p>This update of the TYGS and LPSN platforms again underlines the need for an expert-curated nomenclatural database and for a database of verified type strain genomes, their metadata and subsequent facilities for taxonomic analysis, as well as an improved access to the data. <anchor xml:id="a27"/>Even though other platforms such as EzBioCloud ( 37 ) may provide access to a broader selection of ‘reference genomes’, including non-type strains, these are to the best of our knowledge frequently confused or misinterpreted as type strains and may thus lead to taxonomic misinterpretations.<anchor xml:id="a28"/> TYGS and LPSN, a synergistic pair of database-driven platforms, not only cover the core fields of (genome-based) taxonomy but also provide guidance especially for non-experts in a field in which one may have difficulties in choosing between a plethora of tools and data entries.</p>
        <p>The calculation and storage of intergenomic distances and dDDH values provides for a high level of standardization within the TYGS database, with dDDH being one of the most widely used overall genome relatedness indices (OGRI) for in silico species delineation ( 18 , 19 ). <anchor xml:id="a29"/>As noted earlier, the dDDH approach was shown to outperform ( 18 , 19 ) the ‘average nucleotide identity’ (ANI) approach, which is also frequently used in scientific studies as an alternative OGRI index ( 5 ). More recently, ‘ANI’ was found to yield results that are inconsistent across its various implementations due to a lack of standardization ( 38 ).<anchor xml:id="a30"/></p>
        <p><anchor xml:id="a31"/>While a recent attempt to modify the ICNP to allow for using genome sequences as nomenclatural type was unsuccessful ( 39 ), alternative solutions to the perceived underlying problem are currently actively debated ( 40 ).<anchor xml:id="a32"/> Independent of the outcome of these discussions, the expansion of the LPSN infrastructure demonstrates that it is already capable of dealing with taxon names that have a status under distinct codes of nomenclature. As expected for these two highly interconnected platforms, the broadening of the scope of names included in LPSN automatically also broadens the scope of genome sequences found in the TYGS.</p>
        <p>DATA AVAILABILITY</p>
        <p>The provided TYGS data can be freely downloaded in various formats (e.g. CSV, XLS, JSON, PDF, SVG, PNG, PhyloXML, Newick and BibTeX) without restrictions, except that the origin of the data has to be properly cited ( 17 ) when used in other works. Information obtained from LPSN should also be properly cited ( 2 ). Registration is necessary to access the LPSN download files and the LPSN API but registration is free and easy to accomplish.</p>
        <p>ACKNOWLEDGEMENTS</p>
        <p>The work of our colleagues Lorenz C. Reimer and Julia Koblitz on the Bac Dive API, API clients and mailing list also helped establishing the according facilities for LPSN, which is gratefully acknowledged. We cordially thank the DSMZ student assistants Patrick Bergmann, Adelina Gllareva and Sanja Haake for their help in maintaining the LPSN database. The LPSN acknowledgements page lists the users who sent us LPSN-related information, feature requests or error reports, which is gratefully acknowledged. We would also like to thank the two anonymous reviewers for their helpful comments.</p>
        <p>Author contributions : J.P.M.K. and M.G. conceived, designed and implemented the TYGS. J.P.M.K. also designed and implemented the novel TYGS features. M.G. conceived LPSN and its new features, implemented the database back-end, and curated parts of the LPSN database. J.S.C. implemented the front-end of the LPSN API and the associated facilities. R.P.O. curated parts of the LPSN database. J.P.M.K. drafted the manuscript. J.P.M.K. and M.G. finalized the manuscript. All authors have read and approved the final version of the manuscript.</p>
        <p>Contributor Information</p>
        <p>Jan P Meier-Kolthoff,  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany.</p>
        <p>Joaquim Sardà Carbasse,  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany.</p>
        <p>Rosa L Peinado-Olarte,  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany.</p>
        <p>Markus Göker,  Leibniz Institute DSMZ – German Collection of Microorganisms and Cell Cultures, Department of Bioinformatics and Databases, Inhoffenstrasse 7B, 38124 Braunschweig, Germany.</p>
        <p>FUNDING</p>
        <p>Deutsche Forschungsgemeinschaft [Sonderforschungsbereich TRR 51 to J.P.M.K.]. Funding for open access charge: Deutsche Forschungsgemeinschaft [Sonderforschungsbereich TRR 51 to J.P.M.K.].</p>
        <p>Conflict of interest statement . None declared.<anchor xml:id="a33"/></p>
    </body>
  </text>
</TEI>
