This page is within the scope of WikiProject Tree of Life, a collaborative effort to improve the coverage of taxonomy and the phylogenetictree of life on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Tree of LifeWikipedia:WikiProject Tree of LifeTemplate:WikiProject Tree of Lifetaxonomic
This talk page can be used to discuss issues with the automated taxobox system that are common to the entire system, not just one of its templates. Discussions of this nature prior to 2017 can be found at Template talk:Automatic taxobox
Those familiar with the system prior to mid-2016 are advised to read Notes for "old hands".
At Template:Taxonomy/Protochlamydia I am trying to create a link of the form "Ca. Protochlamydia". However, the mighty taxobox system is insisting on italicizing the whole thing. Trying to use the template {{normal}} does not work, and a quick examination of the output HTML by inspect element shows that it's been filtered out somewhere. Trying to just type ''Ca.'' Protochlamydia or Ca. ''Protochlamydia'' gives the same result.
There are two routes (I think) to fixing this, given my limited 5-minute read of the call chain.
It's easy and tempting to just change Module:TaxonItalics, but that comes with the issue of this module not being called for anything higher than a genus – Candidatus higher taxa do exist, and even there you are supposed to italicize the Candidatus while leaving the rest alone.
The other route is to just directly do the formatting in the callers, which would require similar changes in multiple modules: Module:Autotaxobox AND Module:Automated taxobox. The caller logic would be basically changed to:
locali,j=linkText.find("^Ca(%.|ndidatus) ")ifi!=nilthenlinkText="''"..name.sub(i,j-1).."'' "..name.sub(j+1)elseifitalics=="yes"then-- now an elseif would work here, but i want to make it resemble the original a bit morelinkText=TaxonItalics.italicizeTaxonName(linkText,false,abbreviated=='yes')endend
(Because we are supposed to leave the rest alone, there will be no need to call italicizeTaxonName even for a rank that ordinarily requires italics.)
Is this something that could perhaps be handled with a parameter for Candidatus taxa in taxonomy templates? I know I haven't worked much on implementing automatic taxoboxes for bacteria because the system can't handle Candidatus status well. Plantdrew (talk) 16:50, 5 May 2025 (UTC)[reply]
@Plantdrew: Hmm, good point. A |candidatus=yes added to Template:Taxonomy/* should cover anything that uses it (so everything above species?). Speciesbox still needs its own thing. Artoria2e5🌉11:11, 20 May 2025 (UTC)[reply]
Unfortunately, I think to do it properly will be more complicated than suggested by Artoria2e5. There are several places in which a fully automated system would need to handle a candidatus name:
In an automated taxobox, in the parent taxon rows, where names are abbreviated where appropriate
In an automated taxobox, in the target taxon row, where names are not abbreviated
In an automated taxobox, in the taxobox title, generated automatically from the taxon name or page title
In the page title, which is formatted by {{Italic title}} being added for genus level ranks and below
In the right hand table when a taxonomy template is displayed
3 and 4 can of course be handled manually.
There are also various checks, e.g. titles for a monospecific genus at the genus when {{Speciesbox}} is used for the taxobox, or ensuring the link in a taxonomy template matches the title of the template; these would need to be studied to ensure that they worked correctly for candidatus names.
However, the taxobox at Protochlamydia naegleriiphila seems ok, although the page needs to be moved to "Candidatus Protochlamydia naegleriiphila" (or "Ca. Protochlamydia naegleriiphila") for consistency. So is it just the right hand table when a taxonomy template is displayed which is the problem?
Some taxonomy templates now have {{high-use}} added to them; for example Template:Taxonomy/Otophysi. However, I don't think that the warning message produced makes sense for a taxonomy template: a change can't be effectively tested in a sandbox, because it's the effect on multiple taxoboxes that matters, and it doesn't make sense to me to create a test page for a taxonomy template – how would you force the automated taxobox system to use the sandbox version in order to compare with the live version?
This template is used on approximately 9,900 pages and changes may have wide effects on taxoboxes. To avoid major disruption, changes should be made cautiously, preferably after discussion at the relevant Tree of Life project.
This may not be the best wording, but I think something like it is better than a warning that includes links to a sandbox and a test page.