CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <base href="https://lpsn.dsmz.de/"> <title>FAQ</title> <link rel="icon" type="image/svg+xml" href="/img/lpsn_logo.svg" sizes="any"> <link rel="stylesheet" href="/css/style.css?v=15" type="text/css"/> <link rel="canonical" href="/text/faq"/> <meta name="robots" content="index,follow"> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=2.0, minimum-scale=1.0, user-scalable=yes"/> <script> var _paq = window._paq || []; /* tracker methods like "setCustomDimension" should be called before "trackPageView" */ _paq.push(["setDocumentTitle", document.domain + "/" + document.title]); _paq.push(["setCookieDomain", "*.lpsn.dsmz.de"]); _paq.push(["setDomains", ["*.lpsn.dsmz.de", "*.lpsn-dev.dsmz.de", "*.bacterio.net"]]); _paq.push(["enableCrossDomainLinking"]); _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function () { var u = "https://piwik.dsmz.de/"; _paq.push(['setTrackerUrl', u + 'matomo.php']); _paq.push(['setSiteId', '11']); var d = document, g = d.createElement('script'), s = d.getElementsByTagName('script')[0]; g.type = 'text/javascript'; g.async = true; g.defer = true; g.src = u + 'matomo.js'; s.parentNode.insertBefore(g, s); })(); </script> </head> <body>  <div class="modal"> <div class="close"><span>×</span></div> <div class="content">  <h5>Help ensuring the future of LPSN</h5> <p>Please sign and share this <a href="https://www.ipetitions.com/petition/support-the-best-of-both-worlds">petition</a> for a safe future of prokaryotic nomenclature and LPSN.</p> <div><button class="button-default">close</button></div> </div> </div>  <div class="left-col"> <div class="main-logo"> <a href="/" class="logo"></a> </div> <div id="mobile-open-menu"> <div></div> <div></div> <div></div> </div> <div class="menu-container clearfix"> <br>  <ul class="menu-cat"> <li><a href="/domain" class="color-domain ">Domain</a> </li> <li><a href="/phylum" class="color-phylum ">Phylum</a> </li> <li><a href="/class" class="color-class ">Class</a> </li> <li><a href="/order" class="color-order ">Order</a> </li> <li><a href="/family" class="color-family ">Family</a> </li> <li><a href="/genus" class="color-genus ">Genus</a> </li> <li><a href="/species" class="color-species ">Species</a> </li> <li><a href="/other-categories" class="other-categories ">Rarely used categories</a></li> </ul>  <div class="menu-cont"> <div class="custdropdown"> <button class="dropbtn">Browse by rank</button> <div class="custdropdown-content"> <a href="/domain" class="color-domain ">Domain </a> <a href="/phylum" class="color-phylum ">Phylum </a> <a href="/class" class="color-class ">Class </a> <a href="/order" class="color-order ">Order </a> <a href="/family" class="color-family ">Family </a> <a href="/genus" class="color-genus ">Genus </a> <a href="/species" class="color-species ">Species </a> <a href="/other-categories" class="other-categories ">Rarely used categories </a> </div> </div> </div> <br> <ul class="menu-cont"> <li><a href="/advanced_search">Advanced search</a></li> <li><a href="/mailinglist/subscribe">Subscribe</a></li> <li class="top10"> <a href="/text/main">Main</a> </li> <li > <a href="/text/navigation">Navigation</a> </li> <li > <a href="/text/nomenclature">Nomenclature</a> </li> <li > <a href="/text/etymology">Etymology</a> </li> <li > <a href="/text/collections">Collections</a> </li> <li > <a href="/text/copyright">Copyright</a> </li> <li > <a href="/text/faq">FAQ</a> </li> <li class="top10"><a href="/taxon-name-proposal">Submit</a></li> <li><a href="/contact">Contact</a></li> <li><a href="/statistics">Statistics</a></li> <li><a href="/downloads">Downloads</a></li> </ul> </div> <div class="icsp-logo"> <a href="https://www.the-icsp.org/" class="logo"></a> </div> <div class="gcbr-logo"> <a href="https://globalbiodata.org/" class="logo"></a> </div> </div>  <div class="main-col"> <div class="default-top-bar clearfix"> <form id="simple-search" class="" method="get" action="/search"> <input type="text" placeholder="Search taxonomy" name="word" minlength="4" autocomplete="off"><button type="submit"></button> <div class="autocomplete hide"></div> </form> </div> <div id="static-page" class="std-pad"> <h1>FAQ</h1> <button id="btn-print" title="Print page" class="button-print fl" style="float: right;" onclick="collapseAll();window.print();">   </button> <button id="btn-closeall" title="Close all panels" class="button-closeall fl" style="float: right;" onclick="collapseAll()">   </button> <button id="btn-expandall" title="Expand all panels" class="button-expandall fl" style="float: right;" onclick="expandAll()">   </button> <button id="frequently-asked-questions" class="accordion">Frequently asked questions <a href="/text/faq#frequently-asked-questions" class="anchorlink">   </a> </button> <div class="panel"> <p>Here we have compiled general answers to questions users had about LPSN. For explanations of terms and abbreviations and for information on specific topics please see the <a href="/text/glossary" class="">LPSN glossary</a>.</p> </div> <button id="is-there-an-introduction-into-lpsn" class="accordion">Is there an introduction into LPSN? <a href="/text/faq#is-there-an-introduction-into-lpsn" class="anchorlink">   </a> </button> <div class="panel"> <p>Yes, please see the LPSN <a href="/text/introduction" class="">introduction page</a>.</p> </div> <button id="who-has-contributed-to-lpsn" class="accordion">Who has contributed to LPSN? <a href="/text/faq#who-has-contributed-to-lpsn" class="anchorlink">   </a> </button> <div class="panel"> <p>Please see the LPSN <a href="/text/acknowledgements" class="">acknowledgements page</a>.</p> </div> <button id="how-should-lpsn-requests-be-made" class="accordion">How should LPSN requests be made? <a href="/text/faq#how-should-lpsn-requests-be-made" class="anchorlink">   </a> </button> <div class="panel"> <p>We are asking users to report LPSN requests <i>via</i> the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions whenever possible and <i>via</i> the <a href="/contact" class="">contact form</a> in all other cases, using an appropriate subject. Requests may be questions, error reports, feature requests or other kinds of statements. An appropriate subject assists us in properly dealing with your request. The subject categories are as follows.</p> <p><b>Graphical user interface.</b> This category should be chosen if you are satisfied with some LPSN content but you opine that this content should be displayed in a different manner, or that a distinct kind of presentation of the content should additionally be offered. These would be feature requests. Alternatively, you can send us an error report if you believe that the presentation of the content leads to misunderstandings or is unsatisfactory in some other manner.</p> <p><b>Missing taxon name.</b> You should not normally choose this category but use the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions if you fail to find a certain taxon name in LPSN. Only if the request does not fit into this form an <a href="/contact" class="">ordinary</a> LPSN request should be made. Prior to sending us an error report about a missing name, please make sure you understand which taxon names are to be expected in LPSN and since which point in time. This is explained in a separate FAQ entry. (In contrast, the taxonomic submission form can immediately be used.) Asking us for including a certain taxon name may in many cases rather be regarded a a feature request, which is also explained in a distinct FAQ entry. Requesting LPSN to prefer a certain taxonomic opinion over another one, i.e. to regard another name a the <a href="/text/glossary#correct-name" class="">☞</a> correct name, should not be assigned to the "missing taxon name" category but to one described below.</p> <p><b>Missing statement.</b> This category should be chosen if you believe some relevant information to be missing in LPSN but it is not a missing taxon name and not a missing synonymy or child-parent relationship. (The <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions should be used in these cases.) Depending on the kind of information a message in this category could be understood as error report or feature request. Please see below for information that can be temporarily missing and should thus not immediately be reported as a problem. User-defined non-mandatory statements can well be included in LPSN, usually as <a href="/text/glossary#notes-in-lpsn" class="">☞</a> notes. For instance, there is a separate FAQ entry about how we can include your publication in LPSN.</p> <p><b>Inaccurate statement.</b> This LPSN category is frequently confused with the next one. In a literature-driven database such as LPSN, virtually all statements are linked to a literature source. If an LPSN statement is linked to a literature source that does not make that statement, LPSN is inaccurate, irrespective of whether or not the linked statement is accurate. A correction of LPSN is needed in that case. If an LPSN statement is linked to a literature source that actually makes that statement, LPSN is accurate, irrespective of whether or not the linked statement is accurate. If the linked statement is inaccurate, LPSN should also be modified, of course, but in that case by adding a hint regarding the erroneous statement found in the literature. Such an explicit clarification is preferable to completely removing some inaccurate literature statement, as researchers may still independently stumble over that error in the sources. LPSN does a lot of checking but we cannot detect all errors ourselves. An error <i>in</i> LPSN is not necessarily an error <i>of</i> LPSN – although errors made by LPSN can certainly occur.</p> <p>These considerations are also of relevance for the taxonomy preferred by LPSN. The <a href="/text/glossary#prokaryotic-code" class=""> ☞</a> International Code of Nomenclature of Prokaryotes (ICNP) regulates <a href="/text/nomenclature" class="">nomenclature</a> but does not regulate <a href="/text/misunderstanding-the-bacteriological-code" class="">classification</a>. For this reason, LPSN is not forced to prefer a certain taxonomic solution over another one, as long as both are compatible with the ICNP. In particular, LPSN does not need to adopt the most recently published taxonomic arrangement. Users are urged to take this into account and to not report deviating taxonomic opinions as an inaccuracy. Instead, the next category of requests should be used in such situations.</p> <p><b>Alternative taxonomic opinion.</b> This is virtually always a feature request, as opposed to an error report. As detailed above, LPSN does not need to prefer certain taxonomic solutions over others just because they were more recently proposed. Users are encouraged to ask for modifications of the taxonomic classification used by LPSN. However, users are also asked to not confuse the occurrence of alternative taxonomic views with actual inaccuracies. LPSN preferences of certain taxonomic arrangements over others may benefit from explicit justifications. This can be done in LPSN notes and may be a valuable outcome even if the LPSN maintainers chose to not immediately modify the LPSN classification in response to a user request. Note that the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions should be used to request the inclusion of child-parent relationships and synonymy relationships whenever possible.</p> </div> <button id="why-is-a-taxon-name-missing-from-lpsn" class="accordion">Why is a taxon name missing from LPSN? <a href="/text/faq#why-is-a-taxon-name-missing-from-lpsn" class="anchorlink">   </a> </button> <div class="panel"> <p>This depends on the name and on the point in time. At a given time point a taxon name can be missing from LPSN for one of the following reasons.</p> <p><ul> <li>The name is the name of a eukaryote and thus beyond the scope of LPSN.</li> <li>The name is the name of a cyanobacterium validly published under the Botanical Code (ICNafp). Such names are of interest for LPSN although they do not belong to the core data set. Users are encouraged to <a href="/taxon-name-proposal" class="">send</a> us requests for the inclusion of such names. However, LPSN does not guarantee that such names are incorporated after a given maximum time period.</li> <li>The name is not <a href="/text/glossary#valid-publication" class=""> ☞</a> validly published under the <a href="/text/glossary#prokaryotic-code" class=""> ☞</a> ICNP and not validly published under the ICNafp. Such names are of interest for LPSN although they do not belong to the core data set. Users are encouraged to <a href="/taxon-name-proposal" class="">send</a> us requests for the inclusion of such names. However, LPSN does not guarantee that such names are incorporated after a given maximum time period.</li> <li>The name has only recently been <a href="/text/glossary#valid-publication" class=""> ☞</a> validly published under the <a href="/text/glossary#prokaryotic-code" class=""> ☞</a> ICNP. This should not normally be reported. However, the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions can be used at any time.</li> <li>The name is <a href="/text/glossary#valid-publication" class=""> ☞</a> validly published under the <a href="/text/glossary#prokaryotic-code" class=""> ☞</a> ICNP since quite some time. This may well be an error and should better be reported using the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions. (Note that we deliberately do not define here what "since quite some time" means, as this is supposed to change over time.)</li> </ul></p> <p>For including taxon names from your own publications please see the FAQ entry below.</p> </div> <button id="why-is-a-taxon-name-that-has-been-included-in-a-validation-list-marked-as-not-validly-published" class="accordion">Why is a taxon name that has been included in a Validation List marked as not validly published? <a href="/text/faq#why-is-a-taxon-name-that-has-been-included-in-a-validation-list-marked-as-not-validly-published" class="anchorlink">   </a> </button> <div class="panel"> <p>Taxon names that are validly published under the ICNP by means of inclusion in a Validation List are not marked as such until the Validation List has been imported into LPSN. If the Validation List is not mentioned on the LPSN page for the taxon name, the Validation List may simply not have been imported yet. Unless you find the same Validation List cited elsewhere on LPSN, such cases should not be reported.</p> <p>On very rare occasions, names on a Validation List are found not to be validly published. (Note that inclusion on a Validation List is a sufficient, not a necessary, condition for valid publication). If this is the case, a note will describe the situation.</p> </div> <button id="can-you-include-my-publication-in-lpsn" class="accordion">Can you include my publication in LPSN? <a href="/text/faq#can-you-include-my-publication-in-lpsn" class="anchorlink">   </a> </button> <div class="panel"> <p>Publications listed in LPSN are either original proposals of taxon names, formal <a href="/text/glossary#emendation" class="">☞</a> emendations of descriptions of taxon names, or publications related to notes. A publication with a proposal of a taxon name or emendation can be added only if:</p> <p><ul> <li>it proposed a taxon name – including <a href="/text/glossary#candidatus" class="">☞</a> <i>Candidatus</i> or any other name that is not <a href="/text/glossary#valid-publication" class="">☞</a> validly published – that is not yet listed in LPSN;</li> <li>it makes an emendation that is not yet listed in LPSN.</li> </ul></p> <p>Publications with proposals of <a href="/taxon-name-proposal" class="">taxon names</a> or emendations will be exchanged only if the wrong publication is given in LPSN.</p> <p>A publication related to a note can be added at any time provided a statement is given that can serve as an informative new note, refers to a specific taxon name and originates from that publication. If you are aware of such a publication please <a href="/contact" class="">send</a> us the taxon name, the suggested text of the note if applicable, and the DOI or a link to the PDF file of that publication.</p> <p>Note that a description of a strain that is not accompanied by the proposal of a taxon name will not be considered for inclusion. Also note that a request made <i>via</i> the <a href="/taxon-name-proposal" class="">form</a> for taxonomic submissions will be processed much faster.</p> </div> <button id="what-do-the-symbols-used-by-lpsn-mean" class="accordion">What do the symbols used by LPSN mean? <a href="/text/faq#what-do-the-symbols-used-by-lpsn-mean" class="anchorlink">   </a> </button> <div class="panel"> <p>LPSN uses symbols for each taxon name to indicate its nomenclatural status: validly published yes/no, illegitimate yes/no, and also ICNP vs. ICNafp (botanical code). Among the names not validly published, the Candidatus names have special symbols (indicating environmental samples). When you move the mouse over a symbol, a tooltip is displayed that tells you what the symbol stands for.</p> <p>There is no further description for these symbols, but you can easily get an overview by doing a simple search for e.g. <a href="/search?word=Bacillus" class=""><i>Bacillus</i></a> or <a href="/search?word=Nostoc" class=""><i>Nostoc</i></a>.</p> <p>Other symbols are used to indicate the kind of each LPSN note. These should mostly be self-explanatory and can otherwise be easily learnt by looking at a few examples.</p> </div> <button id="why-and-how-does-lpsn-assign-the-status-correct-name" class="accordion">Why and how does LPSN assign the status "correct name"? <a href="/text/faq#why-and-how-does-lpsn-assign-the-status-correct-name" class="anchorlink">   </a> </button> <div class="panel"> <p>What is the "correct name"? Some context based on the International Code of Nomenclature of Prokaryotes (ICNP) is needed to properly answer that question.</p> <p>Principle 5 of the ICNP defines that "The correct name of a taxon is based upon valid publication, legitimacy and priority of publication", whilst Principle 8 adds that "Each phylum or taxon of a lower rank with a given circumscription, position, and rank can bear only one correct name, i.e., the earliest that is in accordance with the Rules of this Code.", whilst Note 2 to the Principle defines circumscription, position and rank. Rule 23a of the ICNP states that "Each taxon above and including species, up to and including order, with a given circumscription, position, and rank can bear only one correct name, i.e., the earliest that is in accordance with the Rules of this Code."</p> <p>So how does LPSN deal with the issue of the "correct name"?</p> <p>During the previous eras of LPSN a particular name was not designated as the correct name. At that time LPSN simply displayed the series of new combinations (or, rarely, nomina nova), if any. In practice this led some users to believe that the most recent name needs to be preferred. The LPSN curator at that time then added a disclaimer, but it remains unclear how much this helped.</p> <p>Another issue was the number of species placed within a genus. This was shown on LPSN during all eras. However, is this number mainly relevant as purely nomenclatural information, indicating how many validly published species names are there within a genus? Or are users instead mainly interested in how many species are currently taxonomically placed in a genus? A purely nomenclatural count comes across each set of homotypic synonyms several times. This may not yield the information of interest.</p> <p>When establishing the current implementation of LPSN, it seemed beneficial to also provide the functionality of DSMZ’s former PNU service. PNU always selected one name as the correct name.</p> <p>As noted above, a major misconception regarding the correct name is that, among a series of homotypic synonyms, the most recent validly published and legitimate name must be selected as the correct name. Such homotypic synonyms are mostly generated by proposing new combinations for expressing the affiliation of a species to another genus. However, the ICNP does not indicate any preference whatsoever for the last name among a set of validly published and legitimate names. In contrast, the ICNP emphasizes the goal of taxonomic freedom. Hence, both Principle 8 and Rule 23a refer to a correct name being contextualized by a "given circumscription, position, and rank". Position and circumscription of a taxon are matters of taxonomic opinion, on which the ICNP does not rule. One can assign only one correct name to a taxon at a given time. However, distinct authors can choose a distinct correct name, depending on their taxonomic opinion on circumscription and position of the taxon. Thus, the name considered by one party as the correct name may not so be considered by another party and yet both parties may be in accordance with the ICNP.</p> <p>An example may illustrate this issue. Both <i>Klebsiella terrigena</i> Izard et al. 1981 and <i>Raoultella terrigena</i> (Izard et al. 1981) Drancourt et al. 2001 are validly published and legitimate names. <i>Klebsiella terrigena</i> is the correct name if the taxonomist’s opinion is that the species should be classified in the genus <i>Klebsiella</i>. However, <i>Raoultella terrigena</i> is the correct name if the taxonomist’s opinion is that the species should be classified in the genus <i>Raoultella</i>.</p> <p>Another misconception is that a validly published and legitimate name that is not regarded as correct name would be "incorrect". In fact, such a name is just a synonym. The ICNP defines validly published and not validly published names as well as legitimate and illegitimate names but it does not define incorrect names.</p> <p>One may now argue that whereas the selection of the most recent validly published and legitimate name as the correct name may not be based on the ICNP, one could still assume that later taxonomic studies were based on better data. This is often true. However, better data may not explain the difference in taxonomic opinions expressed in distinct studies. Data alone do not yield a taxonomic classification. One also needs a certain taxonomic concept. The difference between the outcomes from two subsequent taxonomic studies may just be due to a difference in the underlying taxonomic concepts.</p> <p><b>Examples</b> <ul> <li>The dissection of the genus <i>Arcobacter</i> into six genera was opposed by other researchers. The six genera appeared monophyletic in the trees inferred from genome-scale data presented in the study that proposed the dissection. However, so did the genus <i>Arcobacter</i> sensu lato. For this reason, the proposal to dissect the genus is just an example for splitting vs. lumping and not an attempt to solve an instance of non-monophyly.</li> <li>The dissection of the genus <i>Borrelia</i> into two genera was opposed by other researchers. The two genera appeared monophyletic in the trees inferred from genome-scale data presented in the study that proposed the dissection. However, so did the genus <i>Borrelia</i> sensu lato. For this reason, the proposal to dissect the genus is just an example for splitting vs. lumping and not an attempt to solve an instance of non-monophyly.</li> <li>The dissection of the genus <i>Mycobacterium</i> into five genera was opposed by other researchers. The five genera appeared monophyletic in the trees inferred from genome-scale data presented in the study that proposed the dissection. However, so did the genus <i>Mycobacterium</i> sensu lato. For this reason, the proposal to dissect the genus is just an example for splitting vs. lumping and not an attempt to solve an instance of non-monophyly.</li> </ul></p> <p>Solving non-monophyly is an attempt to reconcile the taxonomic classification with a phylogenetic tree. However, each instance of non-monophyly could be solved by either splitting or lumping. The need to repair non-monophyletic taxa is a stronger argument for a taxonomic reclassification than just a distinct view on how divergent a taxon of the considered rank should be.</p> <p>The counter-argument against any reclassification is, of course, taxonomic conservatism. Use of an older classification would not be arbitrary but just conservative (if it could also be based on a literature source, of course). Taxonomic conservatism can be overdone. For instance, the mere concern that a reclassification introduces new names is not in agreement with the ICNP.</p> <p>For this reason, the best solution may well be to be conditionally conservative, i.e. to accept most instances of reclassification but not all of them. Importantly, a certain taxonomy that is skipped at first can be reconsidered at any later time point after observing the further developments in the literature.</p> <p>The issue of consistency most likely arises anyway. LPSN applies a "concept consistency" approach. This approach aims at either incorporating a certain taxonomic concept in its entirety or not at all. In the case of a given taxonomic revision regarding a genus, all new combinations (or, rarely, nomina nova) that yielded a validly published and legitimate name are treated as correct name, or none of them. The only possible exception is the result of an even newer taxonomic revision. In that manner, taxonomic consistency is guaranteed while also taking taxonomic freedom into account.</p> <p>In addition, the LPSN liaises with the taxonomic subcommittees of the ICSP on classification matters and attempts to incorporate information from these subcommittees whenever it deems appropriate.</p> <p><b>Further reading</b> <ul><li><a href="https://doi.org/10.1099/ijsem.0.000778" class="">ICNP</a></li> <li><a href="https://doi.org/10.1099/ijsem.0.005481" class="">Judicial Opinion 122</a></li> <li><a href="https://doi.org/10.1016/j.ttbdis.2022.101994" class="">Paper criticizing last-name-wins approach</a></li> <li><a href="/text/misunderstanding-the-bacteriological-code" class="">Misunderstanding the ICNP</a> – <a href="/genus/arcobacter" class="">Arcobacter</a> – <a href="/genus/borrelia" class="">Borrelia</a> – <a href="/genus/mycobacterium" class="">Mycobacterium</a></li></ul></p> </div> <button id="why-is-the-full-information-on-the-species-within-a-genus-not-displayed-on-the-page-of-the-genus-any-more" class="accordion">Why is the full information on the species within a genus not displayed on the page of the genus any more? <a href="/text/faq#why-is-the-full-information-on-the-species-within-a-genus-not-displayed-on-the-page-of-the-genus-any-more" class="anchorlink">   </a> </button> <div class="panel"> <p>The new design was chosen to prepare for the future of LPSN and to create a sustainable structure for collecting and displaying an increasing amount of information over time. Having one page per taxon name throughout irrespective of the taxonomic category should make navigation through LPSN easier for users.</p> <p>Individual LPSN pages for genus names used to list the full information for all their species names (and subspecies names, if any). For navigation downwards one needed to scroll through potentially a lot of text. But because of past, present and future additions over time (new species in same genus, emendations of genus or species, synonyms, notes etc.) it seemed advisable to generate more pages instead of longer pages. It also appeared to be a straightforward and consistent design to create one page per taxon name throughout. Because the pages for all individual taxon names now have the same structure irrespective of the taxonomic category it should be rather easy to learn how to navigate through LPSN. However, all the species belonging to a genus are listed under the child taxa section of the genus entry.</p> <p>In addition, it is now possible to move from one species of a certain genus to another species of that genus by using the "siblings" button in the upper right corner. Having each species on its own page means more clicking but having all species of a genus on a single page would mean more scrolling. Navigation using the "parent" and "children" buttons should also be straightforward and intuitive.</p> </div> <button id="where-can-i-find-the-hierarchical-classification" class="accordion">Where can I find the hierarchical classification? <a href="/text/faq#where-can-i-find-the-hierarchical-classification" class="anchorlink">   </a> </button> <div class="panel"> <p>Information on the hierarchical classification is available as:</p> <p><ul> <li>list of parent taxa, in order, visible on the category pages (Domain to Species) if you click on the arrowhead on the left side or on "Open all lineages" (unless there is no immediate parent taxon);</li> <li>list of child taxa visible on the category pages (Domain to Species) if you click on "Show [child category] list ..." or on "Open all [child category] lists" (unless there are no child taxa);</li> <li>entry for the parent taxon on each page for a single taxon name (unless there is no parent taxon);</li> <li>list of child taxa on each page for a single taxon name (unless there are no child taxa);</li> <li>navigation option "parent" in the upper right corner on each page for a single taxon name (unless there is no parent taxon);</li> <li>navigation option "siblings" in the upper right corner on each page for a single taxon name (unless there are no sibling taxa);</li> <li>navigation option "children" in the upper right corner on each page for a single taxon name (unless there are no child taxa).</li> </ul></p> <p>See also the next entry.</p> </div> <button id="what-are-child-taxa-parent-taxa-and-siblings" class="accordion">What are "child taxa", "parent taxa", and "siblings"? <a href="/text/faq#what-are-child-taxa-parent-taxa-and-siblings" class="anchorlink">   </a> </button> <div class="panel"> <p>An in-depth explanation is provided in the <a href="/text/glossary#assignment-of-child-taxa-to-parent-taxa" class="">☞</a> LPSN glossary. In brief, the term "child taxon" means that some taxon belongs to the category below a given taxon in terms of a hierarchical classification from domain down to subspecies. So for a family, the child taxa would be its constituent genera; for a genus, the child taxa would be its constituent species, etc. Conversely, the "parent taxon" of a species would be a genus, the parent taxon of a genus would by a family, etc. The "siblings" of a species would by other species in the same genus, the siblings of a genus would be other genera in the same family, etc.</p> <p>The navigation menu at the top right of each taxon entry has "parent – siblings – children" - so, for a genus "parent" would be the link to the entry of the family to which it belongs, "siblings" would be list of links to the entries for other genera in the same family, and "children" would be the list of links to the entries for the species in that genus.</p> </div> <button id="what-does-the-formatting-on-the-category-pages-mean" class="accordion">What does the formatting on the category pages mean? <a href="/text/faq#what-does-the-formatting-on-the-category-pages-mean" class="anchorlink">   </a> </button> <div class="panel"> <p>The category pages (Domain to Species) used for browsing the hierarchical classification as well as other pages, such as the result of an <a href="/advanced_search" class="">advanced search</a>, apply various text formatting options such as bold text, quotation marks, and colouring. An in-depth explanation of the meaning of the formatting is provided in the <a href="/text/introduction" class="">introduction</a> to LPSN. Note that LPSN also uses <a href="/text/glossary#stubs-and-placeholders" class="">☞</a> stubs and placeholders in certain situations. These are enclosed in square brackets.</p> </div> <button id="where-can-i-find-the-geographic-origin-of-strains" class="accordion">Where can I find the geographic origin of strains? <a href="/text/faq#where-can-i-find-the-geographic-origin-of-strains" class="anchorlink">   </a> </button> <div class="panel"> <p>The geographic origin and other source information for strains can be found in <a href="https://bacdive.dsmz.de/advsearch" class="">Bac<i>Dive</i></a> either by searching there directly or by following the Bac<i>Dive</i> link in the LPSN species entry when available ("See detailed strain information at Bac<i>Dive</i>").</p> </div> <button id="is-it-possible-that-lpsn-genera-lack-species" class="accordion">Is it possible that LPSN genera lack species? <a href="/text/faq#is-it-possible-that-lpsn-genera-lack-species" class="anchorlink">   </a> </button> <div class="panel"> <p>Yes, temporarily. LPSN attempts to display information as soon as possible once it has achieved a certain degree of completeness and underwent a certain number of checks. This may yield entries for genera that are not yet linked to an entry for a species, families that show no genera, orders that show no families, etc. Such entries should not be read as an indication of really missing child taxa. For analogous reasons LPSN generates <a href="/text/glossary#stubs-and-placeholders" class="">☞</a> stubs or placeholders for parent taxa.</p> <p>The only alternative is to postpone the display of parent taxa until all expected child taxa can be displayed, and to postpone the display of child taxa until their parent taxa have been entered. This approach would create problems of its own.</p> </div> <button id="is-it-possible-that-lpsn-taxon-names-lack-nomenclatural-types" class="accordion">Is it possible that LPSN taxon names lack nomenclatural types? <a href="/text/faq#is-it-possible-that-lpsn-taxon-names-lack-nomenclatural-types" class="anchorlink">   </a> </button> <div class="panel"> <p>Yes. Most <a href="/text/glossary#nomenclatural-type" class="">☞</a> nomenclatural types are missing only temporarily. LPSN attempts to display information as soon as possible once it has achieved a certain degree of completeness and underwent a certain number of checks. This may yield entries for taxon names that do not yet list a nomenclatural type. Such entries should not be read as an indication of an actually missing type. If the nomenclatural type of a <a href="/text/glossary#valid-publication" class="">☞</a> validly published name is actually missing (rendering the name <a href="/text/glossary#illegitimate-names-and-epithets" class="">☞</a> illegitimate), this will be explicitly indicated. Such indications may not be made for names that are not validly published.</p> <p>The only alternative is to postpone the display of taxon names until the nomenclatural type can be displayed. This approach would create problems of its own.</p> </div> <button id="is-it-possible-that-synonyms-are-not-mentioned" class="accordion">Is it possible that synonyms are not mentioned? <a href="/text/faq#is-it-possible-that-synonyms-are-not-mentioned" class="anchorlink">   </a> </button> <div class="panel"> <p>Yes, temporarily. LPSN attempts to display information as soon as possible once it has achieved a certain degree of completeness and underwent a certain number of checks. This may yield entries for taxon names that are not yet linked to an entry for a synonym although this entry is present in LPSN. The link will usually be made in short time but may initially be missing.</p> <p>The only alternative is to postpone the display of taxon names until all synonyms have been linked. This approach would create problems of its own.</p> </div> <button id="is-it-possible-that-the-year-of-an-authority-changes" class="accordion">Is it possible that the year of an authority changes? <a href="/text/faq#is-it-possible-that-the-year-of-an-authority-changes" class="anchorlink">   </a> </button> <div class="panel"> <p>Unfortunately, yes. Two aspects are of relevance here: A change of the year of the <a href="/text/glossary#effective-publication" class="">☞</a> effective publication and a change cause by the <a href="/text/glossary#validation-lists" class="">☞</a> validation of a taxon name.</p> <p>The problem of a change of the year of the effective publication is related to "online first" or other preliminary publications that do not indicate the final volume, issue, and/or page numbers. In such cases the year of the first online publication may differ from the year of the final volume. Since the final year cannot be predicted with certainty from the first online publication, LPSN initially uses the year of the first online appearance of some paper and may later on be forced to update the year. This is annoying but in the view of the LPSN maintainers it is not a problem that is caused by LPSN. Also note that PubMed behaves in the same way, as publication years given in PubMed entries can get updated for apparently the same reason.</p> <p>The only alternative is to postpone the display of a taxon name until the final version of the citation gets published by the journal. This approach would create problems of its own.</p> <p>Such updates of publication details may also cause changes of volume, issue or page numbers. LPSN uses 0 as placeholder for volume, issue or page numbers that are as yet missing.</p> <p>For names <a href="/text/glossary#valid-publication" class="">☞</a> validly published under the <a href="/text/glossary#prokaryotic-code" class="">☞</a> ICNP, LPSN provides the year of valid publication. Among other reasons, this year determines the priority of the name. If LPSN has recorded the same name as not being validly published beforehand, the year of the authority may change upon validation in <a href="/text/glossary#international-journal-of-systematic-and-evolutionary-microbiology" class="">☞</a> IJSEM. The year of valid publication is always the year of listing the name in IJSEM, either in a Validation List or directly in an effective publication in IJSEM.</p> <p>IJSEM also publishes <a href="/text/glossary#notification-lists" class="">☞</a> Notification Lists. These do not determine the year or status of valid publication. Also note that even the inclusion in a Validation List or directly in an effective publication in IJSEM is only a necessary condition but not a sufficient condition for a name to be validly published.</p> <p>Finally, in the case of <a href="/text/glossary#emendation" class="">☞</a> emendations there is no distinction between validly published ones and others. Hence, the year given is always the year of original publication of the emendation.</p> </div> <button id="which-taxon-names-should-be-written-in-italics" class="accordion">Which taxon names should be written in italics? <a href="/text/faq#which-taxon-names-should-be-written-in-italics" class="anchorlink">   </a> </button> <div class="panel"> <p>This can be found in the 2022 revision of the ICNP in <b>Chapter 4. Advisory Notes A. Suggestions for Authors and Publishers</b>, which states that "It is recommended that scientific names be printed in a different font, e.g. italics, or by some other device to distinguish them from the rest of the text". See also Rule 33a Note 2. Thus, for prokaryotes, names in all categories are printed in italics. However, in the case of <i>Candidatus</i> names, only the word "Candidatus" is italicised (see Appendix 11 of the ICNP).</p> </div> <button id="is-it-possible-that-lpsn-does-not-write-taxon-names-in-publication-titles-or-etymologies-in-italics" class="accordion">Is it possible that LPSN does not write taxon names in publication titles or etymologies in italics? <a href="/text/faq#is-it-possible-that-lpsn-does-not-write-taxon-names-in-publication-titles-or-etymologies-in-italics" class="anchorlink">   </a> </button> <div class="panel"> <p>LPSN attempts to display information as soon as possible once it has achieved a certain degree of completeness and underwent a certain number of checks. This may yield publication titles that do not yet display taxon names in italics. The formatting will usually be made in short time but may initially be missing. The only alternative is to postpone the display of publications until all included taxon names have been formatted. This approach would create problems of its own.</p> <p>Names of non-bacterial taxa and incorrectly spelled names of bacterial taxa are deliberately not written in italics in publication titles. We believe the cost-benefit ratio of such extensive formatting attempts to be too high.</p> <p>Names of bacterial or other taxa in explanations of etymology entries are deliberately not written in italics. Here italics is reserved for the explained words.</p> </div> <button id="can-lpsn-supply-strains" class="accordion">Can LPSN supply strains? <a href="/text/faq#can-lpsn-supply-strains" class="anchorlink">   </a> </button> <div class="panel"> <p>No, LPSN cannot supply strains. (Not even DSMZ strains.) However, LPSN does list type strains of taxa and where possible links directly to those strains in culture collections that have online catalogues – strains can be ordered directly from these collections.</p> </div> <button id="what-do-the-abbreviations-in-the-lpsn-graphics-mean" class="accordion">What do the abbreviations in the LPSN graphics mean? <a href="/text/faq#what-do-the-abbreviations-in-the-lpsn-graphics-mean" class="anchorlink">   </a> </button> <div class="panel"> <p>The abbreviation "NA" ("not available") means that we could not (or not yet) resolve the country from the e-mail address of the corresponding author(s); "misc." means that we know the country (or category, etc.), but we are running out of distinguishable colours; "w/o" means "without".</p> </div> <button id="is-it-possible-that-a-type-strain-deposit-indicated-on-lpsn-is-not-accessible-any-more" class="accordion">Is it possible that a type-strain deposit indicated on LPSN is not accessible any more? <a href="/text/faq#is-it-possible-that-a-type-strain-deposit-indicated-on-lpsn-is-not-accessible-any-more" class="anchorlink">   </a> </button> <div class="panel"> <p>LPSN primarily aims at accurately representing literature data. Alleged type-strain deposits found in the literature can later on well turn out to be not viable any more, or to not correspond to the description of their species or subspecies, or to be contaminated. Fixing such issues in a proactive way is beyond the scope of LPSN (and beyond our resources, for that matter). We are happy to include information from the corresponding collection or from the scientific literature about the need to delete records of type-strain deposits. If you have proof for such cases, please let us know. This particularly holds if the lack of deposits puts a name in danger of not being validly published.</p> <p>This issue also affects the links to web pages of deposits in culture collections. If none of the links to a certain culture collection works, they should indeed be deactivated. If single deposit numbers yield a malfunctioning link, however, this may have a variety of reasons, and deactivating the number of the deposit in LPSN may be the wrong choice. For instance, the deposit number may be listed in the literature but the collection did not yet publish the web page. Alternatively, the collection may have removed the page because it does not want the strain to be ordered although the deposit is fine. Both statuses may change at any time.</p> <p>The main problem here is that the lack of a web page for a collection deposit does not indicate that the deposit is unavailable. This is unfortunate but LPSN can do little about it, even in the case of DSMZ deposits. LPSN would much prefer that all deposits in culture collections that were ever issued had a web page, even if this page just indicated that the deposit was abandoned.</p> <p>Please do not send questions about the accessibility of deposits primarily to LPSN. Instead, please first contact the corresponding collection or the authors who proposed the type strain. For instance, DSMZ provides a <a href="https://www.dsmz.de/collection/collection-experts" class="">list of curators</a> to contact about their deposits.</p> </div> <button id="why-are-leading-zeros-sometimes-missing-from-culture-collection-identifiers-in-lpsn" class="accordion">Why are leading zeros sometimes missing from culture collection identifiers in LPSN? <a href="/text/faq#why-are-leading-zeros-sometimes-missing-from-culture-collection-identifiers-in-lpsn" class="anchorlink">   </a> </button> <div class="panel"> <p>The designator of a culture collection deposit usually comprises the acronym of the <a href="/text/collections" class="">collection</a> followed by a specific identifier (ID). One needs to determine whether the ID is intended as a number or as a character string that just happens to contain only digits. If the ID is a number, the leading zeros cannot be significant and are just a matter of formatting. In such situations the sources are often inconsistent regarding leading zeros. Hence, it makes sense to standardise the display of such IDs on LPSN by removing all leading zeros.</p> </div> <button id="where-can-i-find-general-information-on-icandidatusi-names" class="accordion">Where can I find general information on <i>Candidatus</i> names? <a href="/text/faq#where-can-i-find-general-information-on-icandidatusi-names" class="anchorlink">   </a> </button> <div class="panel"> <p>In the LPSN <a href="/text/glossary#candidatus" class="">☞</a> glossary. All <i>Candidatus</i> names are accessible using the <a href="/advanced_search" class="">advanced search</a> while <i>Candidatus</i> phyla are compiled on a <a href="/text/candidatus-phyla" class="">separate page</a>.</p> </div> <button id="how-can-i-find-out-which-version-of-lpsn-i-am-using" class="accordion">How can I find out which version of LPSN I am using? <a href="/text/faq#how-can-i-find-out-which-version-of-lpsn-i-am-using" class="anchorlink">   </a> </button> <div class="panel"> <p>The date of the last update of the public LPSN database can always be found on the <a href="/text/numbers" class="">LPSN numbers page</a>. For the whole database this is almost as good as a version number. Multiple updates per day are very unlikely.</p> </div> <button id="is-there-a-list-of-taxonomic-changes-for-a-certain-year-or-of-the-overall-numbers-of-taxonomic-proposals" class="accordion">Is there a list of taxonomic changes for a certain year or of the overall numbers of taxonomic proposals? <a href="/text/faq#is-there-a-list-of-taxonomic-changes-for-a-certain-year-or-of-the-overall-numbers-of-taxonomic-proposals" class="anchorlink">   </a> </button> <div class="panel"> <p>While there is no list of "taxonomic changes" as such, one can use the <a href="/advanced_search" class="">advanced search</a> by selecting "validly published" and "correct name" and entering the year of interest into the authority field. The result comes pretty close to the list of "taxonomic changes" published in that year.</p> <p>It is important to keep in mind that there is an <a href="/text/introduction" class="">official nomenclature</a> of prokaryotes but not an official classification. The <a href="/text/glossary#prokaryotic-code" class="">☞</a> International Code of Nomenclature of Prokaryotes (ICNP) regulates which name must be applied to which taxon. However, the code does not regulate how prokaryotes are arranged into taxa. For the ICNP, apart from the occasional need to replace a name that <a href="/text/glossary#illegitimate-names-and-epithets" class="">☞</a> contravenes a Rule, there are no name changes; there are only proposals of names. It is up to the user to <a href="/text/misunderstanding-the-bacteriological-code" class="">select</a> a taxonomic arrangement, and this selection then determines the name to apply.</p> <p>The overall numbers of taxonomic proposals are found on the <a href="/text/numbers" class="">statistics</a> page. They are also accessible as user-friendly <a href="/statistics" class="">graphics</a>.</p> </div> <button id="how-does-a-name-become-validly-published" class="accordion">How does a name become validly published? <a href="/text/faq#how-does-a-name-become-validly-published" class="anchorlink">   </a> </button> <div class="panel"> <p>The <a href="/text/glossary#valid-publication" class="">☞</a> valid publication of names of species and subspecies under the <a href="/text/glossary#prokaryotic-code" class="">☞</a> International Code of Nomenclature of Prokaryotes (ICNP) requires the deposit of pure cultures of the type strain in collections in at least two distinct countries. Authors of taxon names may not be aware that valid publication of names proposed in an effective publication outside the International Journal of Systematic and Evolutionary Microbiology (IJSEM) is not automatic. Instead, a request for validation must be sent to the IJSEM office, including the proposed name, the effective publication, and evidence for the deposit of the type strain in at least two culture collections in distinct countries.</p> </div> <button id="is-there-a-way-in-the-downloadable-excel-file-to-differentiate-between-homotypic-and-heterotypic-synonyms" class="accordion">Is there a way in the downloadable excel file to differentiate between homotypic and heterotypic synonyms? <a href="/text/faq#is-there-a-way-in-the-downloadable-excel-file-to-differentiate-between-homotypic-and-heterotypic-synonyms" class="anchorlink">   </a> </button> <div class="panel"> <p>Please see the <a href="/text/lpsn-download-formats" class="">page</a> on LPSN download formats.</p> </div> <button id="how-is-lpsn-governed" class="accordion">How is LPSN governed? <a href="/text/faq#how-is-lpsn-governed" class="anchorlink">   </a> </button> <div class="panel"> <p>Please see the <a href="/text/introduction#lpsn-governance" class="">introduction to LPSN</a> for corresponding information.</p> </div>  <div class="printdate"> <span>This LPSN page was printed on 2024-11-24 16:51:12<br></span> </div> <footer> <ul> <li><a href="https://twitter.com/LPSN_DSMZ" target="_blank">Twitter</a></li> <li><a href="https://nfdi.social/@lpsn" target="_blank">Mastodon</a></li> <li><a href="https://bsky.app/profile/lpsn.bsky.social" target="_blank">Bluesky</a></li> <li>♦</li> <li><a href="https://www.dsmz.de/imprint" target="_blank">Imprint</a></li> <li><a href="https://www.dsmz.de/privacy-statement" target="_blank">Privacy Statement</a></li> <li><a href="https://hub.dsmz.de/" target="_blank">DSMZ Digital Diversity</a></li> <li><a href="https://tygs.dsmz.de/" target="_blank">TYGS</a></li> <li>♦</li> <li><a href="https://www.the-icsp.org/" target="_blank">ICSP</a></li> <li>♦</li> <li><a href="https://globalbiodata.org/" target="_blank">GBC</a></li> </ul> </footer> </div> <div id="back-to-top"></div> <script type='text/javascript' src='/js/main.js?v=15'></script> <script type='text/javascript' src='/js/accordion.js'></script> </body> </html>