Revision as of 23:45, 1 May 2024 editAndrybak (talk | contribs)Extended confirmed users, Template editors81,143 edits →Template-protected edit request on 1 May 2024: punctuation← Previous edit | Latest revision as of 18:32, 25 December 2024 edit undoPppery (talk | contribs)Interface administrators, Administrators101,117 edits →Template-protected edit request on 15 December 2024: Re | ||
(34 intermediate revisions by 11 users not shown) | |||
Line 17: | Line 17: | ||
}} | }} | ||
== Template-protected edit request on 29 June 2024 == | |||
==Connected taxoboxes== | |||
In the article stub about ] the taxobox says it belongs to the order Platycopida, which is correct. And the taxobox in the article stub about ] says that too belongs to the order Platycopida, which is wrong. It belongs to the order Palaeocopida. But when I change the info in the taxobox to correct it, the taxobox describing Cytherellidae changes too, from Platycopida to Palaeocopida. And vice versa. The two taxoboxes are connected, so when you edit it in one of the mentioned articles, the same thing happens in the other. Is there a way to separate them? ] (]) 00:28, 30 October 2023 (UTC) | |||
:{{ping|Hipporoo}} Fixed. I'm not sure what you tried to changed or where, but you needed to change the taxonomy template for Punciidae. I changed the parent taxon in ] to Puncioidea, which was already set up correctly as part of Palaeocopida. For more on the use of the automated taxobox system see ]. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 07:15, 30 October 2023 (UTC) | |||
{{edit template-protected|Template:Taxobox/core|answered=yes}} | |||
== Deprecated vs. discouraged, and should all empty discouraged parameters be removed?<span class="anchor" id="Deprecated vs. discouraged"></span><span class="anchor" id="WPTC+"></span> == | |||
Can someone please convert {{tl|taxobox/core}} to use {{tl|infobox}}, like on the majority of other infobox templates? I converted the ] of that template to use {{tl|infobox}} to the best of my abilities three weeks ago {{diff|Template:Taxobox/core/sandbox|prev|1228241665|on revision 1228241665}}, but I couldn't figure out how to make {{tl|taxobox/species}} and {{tl|taxonomy}} look and function exactly the same on the sandbox version of that template as on the original version. ] (]; ]) 11:02, 29 June 2024 (UTC) | |||
: What advantage is there in converting to using {{tl|infobox}}? The {{tl|taxobox}} template predates the infobox system and works effectively. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 12:20, 29 June 2024 (UTC) | |||
::One potential DISadvantage is that text in infoboxes is smaller than text in the body of the article. Most text in taxoboxes is the same size as text in the body of the article, but authorities are usually rendered in smaller text (either via code in the taxobox template for parameters such as {{para|binomial_authority}}, code in other templates such as {{tl|Species list}}, or HTML <small> tags). If taxoboxes used the default smaller text of infoboxes, the authorities would be "double smalled", a size which violates accessibility guidelines. ] (]) 14:27, 29 June 2024 (UTC) | |||
::I support the proposed conversion to the infobox style for the sake of furthering visual consistency across the encyclopedia. I agree with Plantdrew that any ] issues should be resolved before such a change is implemented. — ] (]) 08:07, 25 July 2024 (UTC) | |||
:] '''Not done for now:''' Your work in the sandbox is appreciated and looks very challenging. For now, it appears that a ] needs to be established for this major change. Please garner the needed consensus ''']''' using the {{tlx|edit template-protected}} template again. Thank you very much for your work''!'' ''''']''''' , ] ] <small>14:27, 29 June 2024 (UTC)</small> | |||
There are many parameters listed as "deprecated" under ], but they appear in the template code ''and'' in the documentation, albeit with heavily caveated use cases. They are: | |||
* {{para|image_width}} | |||
* {{para|image_caption_align}} | |||
* {{para|range_map_width}} | |||
* {{para|alliance}} | |||
* {{para|variety}} | |||
* {{para|color_as}} | |||
plus their numerical counterparts, {{para|image2_width}}, etc. | |||
== Why is there no header above the second conservation status? == | |||
It would be more accurate to change these to "discouraged", since the only parameter that's ''actually'' deprecated, from what I can tell, is {{para|image_size}}, since it has been removed from the immediate (i.e. non-nested) template code and from the documentation. | |||
I don't mean there should be one, but I can't understand why the code doesn't produce one. | |||
Related question: should all empty discouraged parameters be removed? I've been removing empty {{para|image_width}} (only) ]. <b>~</b> <span style="font-family:Monotype Corsiva; font-size:16px;">] (] ⋅])</span> 14:36, 1 December 2023 (UTC) | |||
If you look at {{tl|taxobox/species}}, it generates the code for the header cell on line 2. | |||
:{{ping|Tom.Reding}} "deprecated" is one of three qualifiers for parameters allowed by ]. The others are "required" and "suggested". I've long thought there should be another qualifier for "should not normally be used, but necessary in exceptional cases" (I'm not sure how to name it in a concise way). {{para|color_as}} is an instance of "should not normally be used, but necessary in exceptional cases". I suppose {{para|image_caption_align}} may be as well, but I have never come across it being used in my time on Misplaced Pages. | |||
<syntaxhighlight lang=wikitext line start=1> | |||
{{#if:{{{2|}}}| | |||
! colspan = 2 {{!}} <div style = "text-align: center">]</div> | |||
</syntaxhighlight> | |||
This is not conditional (the #if statement in line 1 wraps the whole template), so you'd expect the header each time the template is called. | |||
:Variety is correctly deprecated; {{para|varietas}} should be used instead of {{para|variety}} Most of the parameter names for ranks are Latin not English (regnum/classis/ordo/familia, not kingdom/class/order/family with phylum/genus/species being the same in Latin and English). | |||
If you look {{tl|taxobox/core}}, the calls of {{tl|taxobox/species}} are on lines 22 and 23: | |||
:{{para|alliance}} is also English, but isn't used anywhere. I'm pretty sure I set it to "deprecated" as work-around when trying to find articles that used it and update them to recent classifications that didn't use that rank (the will show articles using a particular parameter/value when a template has few transclusions. When a template has many transclusions (over 50k, I think) the option to see which articles use a particular parameter is disabled unless that parameter is marked as deprecated). | |||
<syntaxhighlight lang=wikitext line start=21> | |||
|- style="text-align: center{{#if:{{{colour|}}}|{{;}} background-color: {{{colour}}} }}" | |||
{{#if:{{{status|}}}|{{taxobox/species|{{{status_system|}}}|{{{status|}}}|{{{status_ref|}}}|extinction_date={{{extinct|}}} }} }} | |||
|-{{#if:{{{status2|}}}|{{taxobox/species|{{{status2_system|}}}|{{{status2|}}}|{{{status2_ref|}}}|extinction_date={{{extinct|}}} }} }} | |||
</syntaxhighlight> | |||
The wikitext for the header in {{tl|taxobox/species}} is placed on a new line, but I don't think that new line is output in the wikitext, as if it was the header would appear on the second conservation status. It seems that line 23 generates the following wikitext: | |||
:The "_width" parameters are correctly deprecated. "_upright" parameters should be used instead, although I would say the "_upright" parameters also fall into "should not normally be used, but necessary in exceptional cases" (the only reason to over-ride the default image display size is when an image has an extreme aspect ratio (tall/narrow or short/wide) that makes it display very large/small). | |||
<syntaxhighlight lang=wikitext > | |||
|-! colspan = 2 {{!}} <div style = "text-align: center">]</div> | |||
</syntaxhighlight> | |||
The header doesn't appear as its wikitext doesn't start on a new line and is ignored. Two tests in edit preview (test with lion) seems to confirm this: | |||
:* Combining lines 1 and 2 of {{tl|taxobox/species}} makes no difference: | |||
<syntaxhighlight lang=wikitext line start=1> | |||
{{#if:{{{2|}}}|! colspan = 2 {{!}} <div style = "text-align: center">]</div> | |||
</syntaxhighlight> | |||
:* But adding a new line after |- in line 23 of {{tl|taxobox/core}} produces a header for the second conservation status. | |||
<syntaxhighlight lang=wikitext line start=21> | |||
|- style="text-align: center{{#if:{{{colour|}}}|{{;}} background-color: {{{colour}}} }}" | |||
{{#if:{{{status|}}}|{{taxobox/species|{{{status_system|}}}|{{{status|}}}|{{{status_ref|}}}|extinction_date={{{extinct|}}} }} }} | |||
|- | |||
{{#if:{{{status2|}}}|{{taxobox/species|{{{status2_system|}}}|{{{status2|}}}|{{{status2_ref|}}}|extinction_date={{{extinct|}}} }} }} | |||
</syntaxhighlight> | |||
Does this matter? Possibly not if it works. I only discovered this because I added a second conservation status to ], which uses {{tl|population taxobox}} that uses ], and I was surprised to see the second header. In that code I'd added the newlines to generate the proper table wikitext. The fix was to remove the new line so the header doesn't appear, which isn't entirely satisfactory. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 13:14, 13 July 2024 (UTC) | |||
:Any of the parameters you've listed should be removed when empty. Almost all the "_width" parameters should be removed even when non-empty (but the image should be checked to see if it does have an extreme aspect ratio that would merit using an "_upright" parameter instead). ] (]) 21:05, 1 December 2023 (UTC) | |||
== Protected edit request on 5 August 2024 == | |||
::{{ping|Plantdrew}} I didn't realize that about ]. Looking through the archives, I found a relevant discussion 5 years ago at ], which predicts the need for a "'''deprecated unless'''" parameter (oh, you're in that discussion too!), but to submit a bug request on {{Phab}}. I thought there'd be a much simpler solution to this, so if/when I get around to it, I'll look through phab tickets to see if something like this actually made it there, and go from there. | |||
::I think I'll stick with removing these empty parameters for now, and look for the special cases you mention after. <b>~</b> <span style="font-family:Monotype Corsiva; font-size:16px;">] (] ⋅])</span> 22:11, 1 December 2023 (UTC) | |||
{{edit protected|answered=yes}} | |||
:::{{ping|Tom.Reding}}, {{para|color}} meets your stricter definition of deprecated; it's been removed from the template code, and I just removed it from the documentation. It should definitely be removed when empty. It could be removed when non-empty, as it does not do anything. I have been slowly working through the articles with "color = lightgrey" (the only value specified now) and converting them to automatic taxoboxes. I wouldn't mind at all if you got rid of all non-empty instance {{para|color}} now, but it is something I intend to eventually achieve myself if nobody else does it. "image_width=220px" is another bugbear of mine (220 is already the default), that I'm inclined to address with automatic taxoboxes, but wouldn't mind of you went ahead and got rid of it while leaving manual taxoboxes in place. ] (]) 02:40, 2 December 2023 (UTC) | |||
:In my long template-editor experience, it is best to remove from the documentation entirely any parameters that should no longer be used at all. The fact that they still might work, until all instances of the parameter in use have been removed/replaced, is immaterial. That they still function (at least for now) will be apparent in the source code, but if they are included in the documentation, then people will use them anew, no matter what the documentation says. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 07:29, 2 December 2023 (UTC) | |||
::I agree about parameters that should not be used at all. However, the limited classification available in TemplateData does cause some problems. There are some parameters, like {{para|color_as}}, that are needed only in exceptional cases, so are "deprecated", but need to be supported indefinitely. | |||
::The <code>image_width</code> parameters are a different matter. I would like to remove them altogether. However, right now reports 3,136 uses of {{para|image_width}} (plus some for other image width parameters), which ideally would be checked first. On the other hand, these parameters don't exist in the automated taxobox templates, like {{tlx|Speciesbox}} and {{tlx|Automatic taxobox}}, so perhaps just removing them from the manual taxobox template would be ok. ] (]) 16:52, 2 December 2023 (UTC) | |||
:::Right. I meant just for the ones that are "dead" parameters to remove them from the docs and replace or remove them, as needed, from "the wild". For stuff with occasional use, it would need to remain in the docs, just really clearly documented as to what unusual cases to use them for. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 10:33, 3 December 2023 (UTC) | |||
::::I'd be fine with removing support for {{para|image_width}} from the code. None of the instances of 100px actually have an image. The remaining values range from 200px to 250px which isn't really a big enough difference from the default 220px to "fix" images with extreme aspect ratios. 234px/235px is used in fungus articles with {{tl|Mycomorphbox}} to make the taxobox display at the same width as the mycomorphbox. If different widths in taxobox and mycomorphbox is even a problem in the first place, a better solution for that would be to make mycomorphboxes display at the same width as a taxobox with a 220px image. ] (]) 16:36, 3 December 2023 (UTC) | |||
:::::It would be best to have a bot remove all the instances of {{para|image_width}} first, to avoid all the pages showing up in the taxobox error-tracking categories. ] (]) 14:05, 5 December 2023 (UTC) | |||
Invert status trackers in dark mode for legibility of black labels. | |||
== COSEWIC DD == | |||
{| class="wikitable" | |||
{{ping|Jts1882|Spacepotato|Pengo}} COSEWIC's website says DD is a valid status. We should update our graphics and taxobox to handle it. Please? :) Ijust fixed ] to correctly list COSEWIC (when it was listing a full link) and the DD turned into "invalid". - ] ] 17:17, 23 January 2024 (UTC) | |||
|+ Dark mode tests for ] 3.1 | |||
: I've added support for DD to the taxobox, but left it without an image. This would have to be created especially and is more than just adding a colour to the blank image template. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 17:38, 23 January 2024 (UTC) | |||
|- | |||
::Understood, and thanks! - ] ] 18:01, 23 January 2024 (UTC) | |||
! Status | |||
:I'd recommend using a blank COSEWIC with "Data Deficient" below: | |||
! Without inversion | |||
:] | |||
! With inversion | |||
:'''Data Deficient''' | |||
|- | |||
:which would match Misplaced Pages's IUCN DD graphic, e.g. see ] | |||
| EX | |||
:If you're wondering why it's like that for IUCN's, I deliberately left out "DD" and "NE" from the image. I'm no graphic designer, but when I made it I wanted to keep it simple and easy to glance, so I chose not to include a separate circle for IUCN's "DD" status because it would stop the circles being in order of threat status, and would make the graphic more confusing (it would be like replacing a fuel gauge with a bunch of indicator lights). Having no filled circle communicates "We don't know", and having no graphic at all communicates "Not evaluated". I should mention that when IUCN made their own graphic they did include NE and DD though (and put Extinct on the right side, making it feel like every species is in an inevitable march towards extinction). —] 23:52, 23 January 2024 (UTC) | |||
| ] | |||
::I'd have a go at fixing it but I don't want to mess up 75,000 articles today, and I have no idea how this template works any more. I'm in awe that it continues to exist. —] 00:05, 24 January 2024 (UTC) | |||
| ] | |||
::: I've followed your suggestion. The template where it is set is {{t1|taxobox/species}}, not one of the most intuitively named templates. — <span style="font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 07:02, 24 January 2024 (UTC) | |||
|- | |||
::::Y'all are the best! Much thanks! - ] ] 12:02, 24 January 2024 (UTC) | |||
| EW | |||
| ] | |||
| ] | |||
|- | |||
| CR | |||
| ] | |||
| ] | |||
|- | |||
| EN | |||
| ] | |||
| ] | |||
|- | |||
| VU | |||
| ] | |||
| ] | |||
|- | |||
| NT | |||
| ] | |||
| ] | |||
|- | |||
| LC | |||
| ] | |||
| ] | |||
|- | |||
| DD | |||
| ] | |||
| ] | |||
|- | |||
| (all highlighted) | |||
| ] | |||
| ] | |||
|} –] (]]) 06:25, 5 August 2024 (UTC) | |||
: {{ping|LaundryPizza03}} I've added <code>class=skin-invert-image</code> to the status graphics for IUCN3.1. There is an issue that the background of the image is black rather than the page background (e.g. see ], but this is an obvious improvement so I've made the change live. | |||
== TemplateStyles tag generates empty paragraph == | |||
: Am I correct to assume that this class should work for all the conservation status graphics (or even all graphics)? If so, I think the above issue can be fixed by editing {{tl|Taxobox/core/styles.css}}. But all the conservation graphics images of other status systems will need updating first. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 10:44, 5 August 2024 (UTC) | |||
:: Images updated with class and taxobox styles edited for transparent background. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 11:56, 5 August 2024 (UTC) | |||
:: {{ping|Jdlrobson}} The taxobox conservation status images have been updated with <code>class=skin-invert-image</code> as discussed above. The issue with a black background for these images has been fixed with of {{tl|Taxobox/core/styles.css}}. I suspect that line 16 might also need changing but I'm not sure where it would have effect (possibly the dark mode gadget?) so won't make a change I can't test. Could you please have a look? — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 12:03, 5 August 2024 (UTC) | |||
::: Deactivating edit request as apparently not ready to go live (and Jts1882 can do it themselves when they think it is ready). ] ] 21:58, 19 August 2024 (UTC) | |||
== Documentation inconsistency APG III/APG IV == | |||
{{reply to|Jdlrobson}} ] has an empty paragraph containing a style tag at the top because of ] adding a TemplateStyles tag to {{tlx|taxobox/core}} on an empty line before the table. One way to prevent the creation of a paragraph would be to put the style tag after the <code>|}</code> like . — ]·] 14:15, 18 April 2024 (UTC) | |||
] consensus is to use APG IV (see quote, below), but on ], APG III remains in most locations (including in a statement on the project's consensus). | |||
== Template-protected edit request on 1 May 2024 == | |||
Here is the text from the taxon template on the project page (]): | |||
{{edit template-protected|Template:Taxobox/core|answered=yes}} | |||
{{Blockquote | |||
Move <code><nowiki><templatestyles src="Template:Taxobox/core/styles.css" /></nowiki></code> from the top of the template to the bottom, immediately after <code><nowiki>|}</nowiki></code>, with no intervening characters. | |||
|For the largest group of ], the ]s ("flowering plants"), ] consensus is to use the Angiosperm Phylogeny Group's ] classification system. The APG IV system does not have formally named divisions or classes, but includes several hierarchically nested, informally named clades. The {{tl|Automatic taxobox}} employs the informal APG clades. When using the standard {{tl|Taxobox}}, the informally named clades should be presented by using parameters such as {{para|unranked_divisio}} in place of formal rank parameters. | |||
}} | |||
Does ] just need to be updated? Are there any locations in this documentation where APG III should remain? – ] <small>(tag or ping me) (])</small> 05:17, 18 November 2024 (UTC) | |||
: That's just an oversight, which I've updated. Documentation is often out of date so I've rephrased it to say uses the APG classification, currently APG IV. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 10:35, 18 November 2024 (UTC) | |||
::@], That's cool. There are five more locations in the doc where APG III is used. Can you look into those, too? I'd just change them myself, but I don't have enough experience with the differences to know if one is intentional. Note that there is a place where the major ranks are given. If that has changed, it may need to be updated in the documentation. Sorry to delegate rather than just do it, but like I said, my current knowledge is limited in this area. – ] <small>(tag or ping me) (])</small> 18:42, 18 November 2024 (UTC) | |||
== Template-protected edit request on 15 December 2024 == | |||
{{edit template-protected|Template:Taxobox|answered=yes}} | |||
Change the NZTCS (New Zealand Threat Classification System) images and parameters to the new ones adopted c. 2021/2022 (formally recommended 2019). This includes a new classification replacing 'Recovering' called 'Nationally Increasing' (where 'NI' is under 'Threatened' in the position where 'D' used to be and 'D' under 'At Risk' where 'R' used to be). I have created and uploaded the icons to Commons, and they can be found https://commons.wikimedia.org/Template:Status_NZTCS_summary here under the '2022' column. This includes NT, DD, NU, Rel, D, NI, NV, NE, NV, and EX. Please also change the corresponding image in the template documentation to https://commons.wikimedia.org/File:Status_2019_NZTCS.svg this one. Please see ] for more information on this, including a source to these changes (the 2022 manual). Colors taken from NZTCS series 40. <b>]</b> ] 21:30, 15 December 2024 (UTC) | |||
: With the different versions it might not be appropriate to replace the old graphics with new if the assessments in the taxoboxes use the old system. I'll have a look at the usage and see if this is an issue before updating the images. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 09:21, 16 December 2024 (UTC) | |||
:Just to note that the icons and other information for status codes are set in ]. I think that just as there are versions of IUCN, e.g. IUCN3.1, there need to be versions of NZTCS, e.g. NZTCS2022. ] (]) 09:40, 16 December 2024 (UTC) | |||
:: In practice, that might be hard to do retrospectively. There are around 1300 uses of {{para|status_system(2)|NZTCS}} and most are unreferenced. Many already have assessments under the new version. However, the changes are mainly cosmetic, using a more varied colour range for the categories. One category (Recovering) has been replaced (with Nationally Increading). That can continue to use the graphic for the old version. Not ideal but if we use the new graphics the other categories will just be in a different colour, so there shouldn't be any confusion. The alternative requires all the existing uses to be reevaluated to check the version used. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 12:32, 16 December 2024 (UTC) | |||
:::Do you happen to know how I might be able to retrieve a list of all the articles which presently have 'R' as their status? I don't think I would have a problem going through and updating every instance of this while properly referencing it. <b>]</b> ] 03:16, 17 December 2024 (UTC) | |||
:::: According to there were only three articles on species with Recovering status. Two had been updated to NI and the third reclassified as Relict. I've edited the articles to the new statuses. | |||
:::: Unlike the IUCN, which makes new assessments piecemeal, the NZTCS publishes a report covering all species every four to five years, so I don't see a need for retaining the old systems. I've added the NI status to {{tl|Taxobox/species}} to allow the changes above and propose that we change the images on the other categories. — <span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> ] |] </span> 09:44, 17 December 2024 (UTC) | |||
:::::One potential hiccup I'll point out: I think I've created the diagram "technically" incorrectly, because apparently, nobody actually sticks to the 2022 guidelines (and thus neither did I). For instance, if you take a report at report 43 (vascular plants 2023), they use the new system to include Nationally Increasing, but then they fall back to the Townsend 2008 system to include one species as 'Recovering'. Report 40 (indigeneous marine inverts 2021) doesn't have any which are Nationally Increasing, Relict or Recovering. Report 41 has Nationally Increasing but then uses Declining, Relict, and Naturally Uncommon. Report 42 (indigenous terrestrial gastropods 2022) acknowledges (but doesn't need to use) Nationally Increasing but then uses Declining, Relict, and Naturally Uncommon. | |||
:::::Meanwhile, though, if you take a look at the 2022 guidelines, Figure 2 on page 11 is extremely clear that the 'At Risk' section is composed of 'Declining, Uncommon, Recovering' in order of most concern to least. Something I'm also realizing is that I should've put 'Not Threatened' on the same diagram as the others, because they all fall under 'Assessed'. I didn't because I feared having to fit the word 'Threatened', but I see that the diagram for COSEWIC gets around this by abbreviating it to 'Threaten.' I'll at least do that before you add these new ones. <b>]</b> ] 17:08, 19 December 2024 (UTC) | |||
:::::I've made the changes. I've kept the categories as-is even though they contradict the 2022 manual, because otherwise, we'd end up with a case where ''we'' technically comply with the rules but none of the reports do, thus making our diagram functionally useless. However, I've added 'Not Threatened' to it, because it's clear that (unlike Data Deficient) it's on the same axis as the others. <b>]</b> ] 00:31, 20 December 2024 (UTC) | |||
Deactivating edit request as it appears to be done. If there's any specific change that needs an uninvolved template editor (as opposed to Jts1882 implementing themselves), then feel free to reactivate. ] ] 18:32, 25 December 2024 (UTC) | |||
This will prevent taxoboxes from adding an empty paragraph tag that contains an empty style tag (<code><nowiki><p><style data-mw-deduplicate="...">...</style></p></nowiki></code>) which is visible as extra space before the lede. The ExpandTemplates link in ] demonstrates that the placement right after the close of the table works. — ]·] 23:08, 1 May 2024 (UTC) | |||
:{{done}}<!-- Template:ETp -->. The effect can be seen both in ] and in the ]. For previewing the sandbox version in ], ]. —] (]) 23:45, 1 May 2024 (UTC) |
Latest revision as of 18:32, 25 December 2024
To help centralize discussions and keep related topics together, all Taxobox subpage talk pages should redirect here. |
Template:Taxobox is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases. |
This template does not require a rating on Misplaced Pages's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||
|
Archives |
|
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
Template-protected edit request on 29 June 2024
This edit request to Template:Taxobox/core has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Can someone please convert {{taxobox/core}} to use {{infobox}}, like on the majority of other infobox templates? I converted the sandbox version of that template to use {{infobox}} to the best of my abilities three weeks ago on revision 1228241665, but I couldn't figure out how to make {{taxobox/species}} and {{taxonomy}} look and function exactly the same on the sandbox version of that template as on the original version. PK2 (talk; contributions) 11:02, 29 June 2024 (UTC)
- What advantage is there in converting to using {{infobox}}? The {{taxobox}} template predates the infobox system and works effectively. — Jts1882 | talk 12:20, 29 June 2024 (UTC)
- One potential DISadvantage is that text in infoboxes is smaller than text in the body of the article. Most text in taxoboxes is the same size as text in the body of the article, but authorities are usually rendered in smaller text (either via code in the taxobox template for parameters such as
|binomial_authority=
, code in other templates such as {{Species list}}, or HTML <small> tags). If taxoboxes used the default smaller text of infoboxes, the authorities would be "double smalled", a size which violates accessibility guidelines. Plantdrew (talk) 14:27, 29 June 2024 (UTC) - I support the proposed conversion to the infobox style for the sake of furthering visual consistency across the encyclopedia. I agree with Plantdrew that any MOS:SMALL issues should be resolved before such a change is implemented. — Goszei (talk) 08:07, 25 July 2024 (UTC)
- One potential DISadvantage is that text in infoboxes is smaller than text in the body of the article. Most text in taxoboxes is the same size as text in the body of the article, but authorities are usually rendered in smaller text (either via code in the taxobox template for parameters such as
- Not done for now: Your work in the sandbox is appreciated and looks very challenging. For now, it appears that a consensus needs to be established for this major change. Please garner the needed consensus before using the
{{edit template-protected}}
template again. Thank you very much for your work! P.I. Ellsworth , ed. 14:27, 29 June 2024 (UTC)
Why is there no header above the second conservation status?
I don't mean there should be one, but I can't understand why the code doesn't produce one.
If you look at {{taxobox/species}}, it generates the code for the header cell on line 2.
{{#if:{{{2|}}}| ! colspan = 2 {{!}} <div style = "text-align: center">]</div>
This is not conditional (the #if statement in line 1 wraps the whole template), so you'd expect the header each time the template is called.
If you look {{taxobox/core}}, the calls of {{taxobox/species}} are on lines 22 and 23:
|- style="text-align: center{{#if:{{{colour|}}}|{{;}} background-color: {{{colour}}} }}" {{#if:{{{status|}}}|{{taxobox/species|{{{status_system|}}}|{{{status|}}}|{{{status_ref|}}}|extinction_date={{{extinct|}}} }} }} |-{{#if:{{{status2|}}}|{{taxobox/species|{{{status2_system|}}}|{{{status2|}}}|{{{status2_ref|}}}|extinction_date={{{extinct|}}} }} }}
The wikitext for the header in {{taxobox/species}} is placed on a new line, but I don't think that new line is output in the wikitext, as if it was the header would appear on the second conservation status. It seems that line 23 generates the following wikitext:
|-! colspan = 2 {{!}} <div style = "text-align: center">]</div>
The header doesn't appear as its wikitext doesn't start on a new line and is ignored. Two tests in edit preview (test with lion) seems to confirm this:
- Combining lines 1 and 2 of {{taxobox/species}} makes no difference:
{{#if:{{{2|}}}|! colspan = 2 {{!}} <div style = "text-align: center">]</div>
- But adding a new line after |- in line 23 of {{taxobox/core}} produces a header for the second conservation status.
|- style="text-align: center{{#if:{{{colour|}}}|{{;}} background-color: {{{colour}}} }}" {{#if:{{{status|}}}|{{taxobox/species|{{{status_system|}}}|{{{status|}}}|{{{status_ref|}}}|extinction_date={{{extinct|}}} }} }} |- {{#if:{{{status2|}}}|{{taxobox/species|{{{status2_system|}}}|{{{status2|}}}|{{{status2_ref|}}}|extinction_date={{{extinct|}}} }} }}
Does this matter? Possibly not if it works. I only discovered this because I added a second conservation status to Ungava brown bear, which uses {{population taxobox}} that uses Module:Biota infobox, and I was surprised to see the second header. In that code I'd added the newlines to generate the proper table wikitext. The fix was to remove the new line so the header doesn't appear, which isn't entirely satisfactory. — Jts1882 | talk 13:14, 13 July 2024 (UTC)
Protected edit request on 5 August 2024
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Invert status trackers in dark mode for legibility of black labels.
Status | Without inversion | With inversion |
---|---|---|
EX | ||
EW | ||
CR | ||
EN | ||
VU | ||
NT | ||
LC | ||
DD | ||
(all highlighted) |
–LaundryPizza03 (dc̄) 06:25, 5 August 2024 (UTC)
- @LaundryPizza03: I've added
class=skin-invert-image
to the status graphics for IUCN3.1. There is an issue that the background of the image is black rather than the page background (e.g. see lion, but this is an obvious improvement so I've made the change live. - Am I correct to assume that this class should work for all the conservation status graphics (or even all graphics)? If so, I think the above issue can be fixed by editing {{Taxobox/core/styles.css}}. But all the conservation graphics images of other status systems will need updating first. — Jts1882 | talk 10:44, 5 August 2024 (UTC)
- Images updated with class and taxobox styles edited for transparent background. — Jts1882 | talk 11:56, 5 August 2024 (UTC)
- @Jdlrobson: The taxobox conservation status images have been updated with
class=skin-invert-image
as discussed above. The issue with a black background for these images has been fixed with this edit to line 7 of {{Taxobox/core/styles.css}}. I suspect that line 16 might also need changing but I'm not sure where it would have effect (possibly the dark mode gadget?) so won't make a change I can't test. Could you please have a look? — Jts1882 | talk 12:03, 5 August 2024 (UTC)- Deactivating edit request as apparently not ready to go live (and Jts1882 can do it themselves when they think it is ready). * Pppery * it has begun... 21:58, 19 August 2024 (UTC)
Documentation inconsistency APG III/APG IV
WP:PLANTS consensus is to use APG IV (see quote, below), but on Template:Taxobox/doc, APG III remains in most locations (including in a statement on the project's consensus).
Here is the text from the taxon template on the project page (Misplaced Pages:WikiProject Plants/Template):
For the largest group of land plants, the angiosperms ("flowering plants"), Misplaced Pages:Wikiproject Plants consensus is to use the Angiosperm Phylogeny Group's APG IV classification system. The APG IV system does not have formally named divisions or classes, but includes several hierarchically nested, informally named clades. The {{Automatic taxobox}} employs the informal APG clades. When using the standard {{Taxobox}}, the informally named clades should be presented by using parameters such as
|unranked_divisio=
in place of formal rank parameters.
Does Template:Taxobox/doc just need to be updated? Are there any locations in this documentation where APG III should remain? – Elizabeth (Eewilson) (tag or ping me) (talk) 05:17, 18 November 2024 (UTC)
- That's just an oversight, which I've updated. Documentation is often out of date so I've rephrased it to say uses the APG classification, currently APG IV. — Jts1882 | talk 10:35, 18 November 2024 (UTC)
- @Jts1882, That's cool. There are five more locations in the doc where APG III is used. Can you look into those, too? I'd just change them myself, but I don't have enough experience with the differences to know if one is intentional. Note that there is a place where the major ranks are given. If that has changed, it may need to be updated in the documentation. Sorry to delegate rather than just do it, but like I said, my current knowledge is limited in this area. – Elizabeth (Eewilson) (tag or ping me) (talk) 18:42, 18 November 2024 (UTC)
Template-protected edit request on 15 December 2024
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Change the NZTCS (New Zealand Threat Classification System) images and parameters to the new ones adopted c. 2021/2022 (formally recommended 2019). This includes a new classification replacing 'Recovering' called 'Nationally Increasing' (where 'NI' is under 'Threatened' in the position where 'D' used to be and 'D' under 'At Risk' where 'R' used to be). I have created and uploaded the icons to Commons, and they can be found https://commons.wikimedia.org/Template:Status_NZTCS_summary here under the '2022' column. This includes NT, DD, NU, Rel, D, NI, NV, NE, NV, and EX. Please also change the corresponding image in the template documentation to https://commons.wikimedia.org/File:Status_2019_NZTCS.svg this one. Please see Misplaced Pages:Conservation_status#New_Zealand:_NZTCS for more information on this, including a source to these changes (the 2022 manual). Colors taken from NZTCS series 40. TheTechnician27 (Talk page) 21:30, 15 December 2024 (UTC)
- With the different versions it might not be appropriate to replace the old graphics with new if the assessments in the taxoboxes use the old system. I'll have a look at the usage and see if this is an issue before updating the images. — Jts1882 | talk 09:21, 16 December 2024 (UTC)
- Just to note that the icons and other information for status codes are set in Template:Taxobox/species. I think that just as there are versions of IUCN, e.g. IUCN3.1, there need to be versions of NZTCS, e.g. NZTCS2022. Peter coxhead (talk) 09:40, 16 December 2024 (UTC)
- In practice, that might be hard to do retrospectively. There are around 1300 uses of
|status_system(2)=NZTCS
and most are unreferenced. Many already have assessments under the new version. However, the changes are mainly cosmetic, using a more varied colour range for the categories. One category (Recovering) has been replaced (with Nationally Increading). That can continue to use the graphic for the old version. Not ideal but if we use the new graphics the other categories will just be in a different colour, so there shouldn't be any confusion. The alternative requires all the existing uses to be reevaluated to check the version used. — Jts1882 | talk 12:32, 16 December 2024 (UTC)- Do you happen to know how I might be able to retrieve a list of all the articles which presently have 'R' as their status? I don't think I would have a problem going through and updating every instance of this while properly referencing it. TheTechnician27 (Talk page) 03:16, 17 December 2024 (UTC)
- According to this search there were only three articles on species with Recovering status. Two had been updated to NI and the third reclassified as Relict. I've edited the articles to the new statuses.
- Unlike the IUCN, which makes new assessments piecemeal, the NZTCS publishes a report covering all species every four to five years, so I don't see a need for retaining the old systems. I've added the NI status to {{Taxobox/species}} to allow the changes above and propose that we change the images on the other categories. — Jts1882 | talk 09:44, 17 December 2024 (UTC)
- One potential hiccup I'll point out: I think I've created the diagram "technically" incorrectly, because apparently, nobody actually sticks to the 2022 guidelines (and thus neither did I). For instance, if you take a report at report 43 (vascular plants 2023), they use the new system to include Nationally Increasing, but then they fall back to the Townsend 2008 system to include one species as 'Recovering'. Report 40 (indigeneous marine inverts 2021) doesn't have any which are Nationally Increasing, Relict or Recovering. Report 41 has Nationally Increasing but then uses Declining, Relict, and Naturally Uncommon. Report 42 (indigenous terrestrial gastropods 2022) acknowledges (but doesn't need to use) Nationally Increasing but then uses Declining, Relict, and Naturally Uncommon.
- Meanwhile, though, if you take a look at the 2022 guidelines, Figure 2 on page 11 is extremely clear that the 'At Risk' section is composed of 'Declining, Uncommon, Recovering' in order of most concern to least. Something I'm also realizing is that I should've put 'Not Threatened' on the same diagram as the others, because they all fall under 'Assessed'. I didn't because I feared having to fit the word 'Threatened', but I see that the diagram for COSEWIC gets around this by abbreviating it to 'Threaten.' I'll at least do that before you add these new ones. TheTechnician27 (Talk page) 17:08, 19 December 2024 (UTC)
- I've made the changes. I've kept the categories as-is even though they contradict the 2022 manual, because otherwise, we'd end up with a case where we technically comply with the rules but none of the reports do, thus making our diagram functionally useless. However, I've added 'Not Threatened' to it, because it's clear that (unlike Data Deficient) it's on the same axis as the others. TheTechnician27 (Talk page) 00:31, 20 December 2024 (UTC)
- Do you happen to know how I might be able to retrieve a list of all the articles which presently have 'R' as their status? I don't think I would have a problem going through and updating every instance of this while properly referencing it. TheTechnician27 (Talk page) 03:16, 17 December 2024 (UTC)
- In practice, that might be hard to do retrospectively. There are around 1300 uses of
Deactivating edit request as it appears to be done. If there's any specific change that needs an uninvolved template editor (as opposed to Jts1882 implementing themselves), then feel free to reactivate. * Pppery * it has begun... 18:32, 25 December 2024 (UTC)
Categories: