Wikipedia talk:Short description

Political persuasion

There is a bit of a discussion on dewiki and wikidata about what is suitable for a short description. It might be useful to gauge opinion on enwiki too. Is this suitable or encouraged?

• Tino Chrupalla - right wing German politician

In my opinion "right wing" is subjective and/or controversial and we should better stick with facts, e.g.

• Tino Chrupalla - German politician
• Tino Chrupalla - German politician and member of AfD party

The current one is German politician (born 1975) which seems sufficient — Martin (MSGJ · talk) 09:04, 25 June 2026 (UTC)

I agree. "[nationality] politician (birth/death range)" should (nearly?) always be sufficient to distinguish the person from other people with similar names. I imagine that there are a few instances of two politicians with the same name, but additional disambiguation can be provided in those rare cases. – Jonesey95 (talk) 17:43, 25 June 2026 (UTC)

I prefer just "German politician (born 1975)" here. "Right wing" is too opinionated rather than factual and its meaning varies significantly from country to country, and "AfD" is too jargony for anyone not familiar with German politics. Usually in surname articles (where the principle of what to include is roughly the same as for short descriptions, except for the different placement of dates) I only see "[birth and death dates] [nationality] politician" or maybe sometimes the name of the highest office they held. —David Eppstein (talk) 07:27, 26 August 2026 (UTC)

David Eppstein, presumably if a reader is trying to look up that person, they would already be somewhat familiar with German politics? — Qwerfjkltalk 18:01, 26 August 2026 (UTC)

Short descriptions are more often for when a reader is not trying to look up that person, finds them in a list of other results for whatever search they're doing, and wants to distinguish the person they're really searching for from all those other people with similar names. And if they're actually looking for Tino Chrupalla, the German politician, and see the short description "German politician" in one of their search results, it's probably specific enough to tell them it's the article they're looking for.

In short: short descriptions are for search disambiguation, not a précis of the article, per WP:SDNOTDEF. —David Eppstein (talk) 18:42, 26 August 2026 (UTC)

National Elections for Singular Offices (ex. Presidential elections)

I would like to suggest a slight shift on the suggested description for National elections, to include for a description of elections of one person-the person elected. This would go along well with the suggested scheme from earlier in the examples section (ex. the 2018 Brazilian general election was the Election of Jair Bolsonaro). It would indicate clearly what the article is about, providing a bit of disambiguation as well, since many articles are separated by a single digit in the year (pretty easy to misremember or mistype) and people may be searching for the election of a particular leader (for example many people go to 1980 United States presidential election, looking for how Reagan was elected). It would help clear up which option to pick when searching for a particular election article. Someone searching "US Presidential Election 198" not remembering the exact year of the election they look for could then easily select the 1984 election reading the SD "Re-election of President Ronald Reagan" or 1988 seeing "Election of President George H.W. Bush". Do you guys think this is a good change?FiredudeT (talk) 01:28, 26 August 2026 (UTC)

I like this idea, yes. Helpful Cat🐈‍⬛ 10:40, 30 August 2026 (UTC)

I'm going to be bold and make the change now, hopefully no one opposes it. FiredudeT (talk) 20:09, 6 September 2026 (UTC)

Should noreplace become the default?

Message intended for Template talk:Short descriptionTemplate talk:Short description, which redirects here.

Once again, a transcluded page with a short description has caused much head scratching. Is it time to make noreplace the default for short descriptions?

When multiple short descriptions appear in an article, we almost always have a carefully hand-crafted SD on line 1 followed by generic efforts generated via transclusions (normally of templates, but sometimes of article leads). Line 1 usually has the best SD (and should be improved or removed if it doesn't). The only use case I can see for replacing by default is when article A includes firstly the lead from article B and secondly a template: in this case, article B's SD may be so specific as to be wrong, so the generic template SD is better. However, almost all templates which produce SDs use noreplace anyway, so the current default does not help.

I think the best (and only?) place to change the default is in {{Short description}}. This template currently passes its second parameter (which is noreplace or absent) through to the SHORTDESC: magic word. Instead, Template:Short description would add |2=noreplace to the magic word by default but would accept a new optional parameter |2=replace (for which I can think of no use case) to suppress that behaviour.

• {{Short description|Type of foo}} → {{SHORTDESC:Type of foo|noreplace}} (second output parameter is new)
• {{Short description|Type of foo|noreplace}} → {{SHORTDESC:Type of foo|noreplace}} (as before)
• {{Short description|Type of foo|replace}} → {{SHORTDESC:Type of foo}} (second input parameter is new)

I believe that the only change of behaviour would occur when one page has or transcludes more than one {{short description}} without noreplace. The first such SD is usually on line 1 and is the one we want. Other SD(s) are either accidentally buried further down the page or in some transcluded page, and are unlikely to be better than the line 1 SD. Of course, the vast majority of later SDs are in templates which already use noreplace and would continue to be correctly skipped, this change having no effect on them. Certes (talk) 15:37, 1 September 2026 (UTC)

After a brief bit of testing, I think this might be a good idea. I put two short descriptions with "noreplace" in my sandbox, and the first one was chosen, as expected. I suspect that this might have unexpected side effects, and that adding the "replace" option (if there is a real use case) will require MediaWiki developers to make changes to the code. Other editors here might be able to predict some side effects. Reading the background at T193857 as well as MOS:ORDER discussions from 2018 and 2019 might help explain why the current situation exists. – Jonesey95 (talk) 19:38, 1 September 2026 (UTC)

The code might be more elegant if this proposal were implemented in MediaWiki rather than {{Short description}}, but it wouldn't require MediaWiki developers. The template code change may be as simple as replacing {{{2|}}} by {{#ifeq:{{{2|}}}|replace||noreplace}} (not tested). Certes (talk) 22:48, 1 September 2026 (UTC)

The effect of SHORTDESC:, if I understand correctly, is:

if there is any SD without noreplace

use the last SD without noreplace

else if there is any SD with noreplace

use the first SD with noreplace

else

there is no SD

The current effect of {{Short description}} is the same, as it just passes parameter 2 through to SHORTDESC:. If the proposal were implemented, it would become:

if there is any SD with replace (a very unusual occurrence)

use the last SD with replace

else if there is any SD without replace

use the first SD without replace

else

there is no SD

That seems like an improvement, as it will result in the line 1 SD taking priority unless something explicitly replaces it. Certes (talk) 22:59, 1 September 2026 (UTC)

I think that there is a danger of overthinking this. The Wonky transclusion problem was a problem with the transclusion, not really a SD issue. The current SD magic word behaviour is derived from the standard behaviour of other magic words. Where a magic word is repeated, the last one wins. Articles should always have their own SD in the first line, or none at all. Any templates (infoboxes or other stuff) should then always set a SD with noreplace so that the article one wins. This is what we have now and generally it works. Having the first SD win might be the technically better solution, but the time to make changes to the way the magic word works or redefine the behaviour of the SD template was probably in 2017 before the magic word was implemented in early 2018. — GhostInTheMachine ^{talk to me} 14:33, 2 September 2026 (UTC)

But we didn't fix it then, and it could be fixed now. Something being suboptimal for years does not mean that it should never be improved. Also, the above proposal does not change the way that any magic words work. The last transclusion without noreplace still "wins". – Jonesey95 (talk) 14:56, 2 September 2026 (UTC)

I think it is more a case of "probably we should have defined it differently back in 2017". However, we didn't and we have have made it work since. I don't really see anything to fix at this point. The last use without noreplace currently does win, because there will only ever be one use without noreplace. — GhostInTheMachine ^{talk to me} 15:20, 2 September 2026 (UTC)

I'll phrase it in a different way: What is the downside of making this proposed change? Will anything break? What, specifically? – Jonesey95 (talk) 16:16, 2 September 2026 (UTC)

I am trying, honest, but I am still having difficulty seeing an actual proposal addressing an actual need. As Certes says ... a new optional parameter |2=replace (for which I can think of no use case). If there is no use case, why add a new parameter? I don't see we have something to fix. The Wonky transclusion problem was a problem with the transclusions and was easily fixed. Maybe a sandbox with the modified SD template could illustrate the point? — GhostInTheMachine ^{talk to me} 19:01, 2 September 2026 (UTC)

I mentioned the possibility of adding a |2=replace as a counter to any possible objections that we would be losing functionality here. The change which may have no use case is that precaution, not the entire proposal. I think it's still beneficial to have noreplace as a default rather than having to remember to add it to every template which provides a backup SD and to every other page with an SD which might get transcluded in whole or part. Certes (talk) 19:12, 2 September 2026 (UTC)

The use case for the new code proposed above is evident in the VPT thread that originated this proposal. Two lead sections were included in an article, and a short description from one of the leads was inadvertently saved as the short description for that article. That would not have happened under this new proposal. The new code would also prevent an infobox or other template's embedded short description template from replacing an article's local short description if an editor forgot to use noreplace in the template. I see only advantages, and I haven't seen a counterexample (but I am very much open to the idea that one exists). This change would specifically fix the problem that we created in 2017–2018 when we decided to place the SD at the top of the page and codified that guidance in MOS:ORDER. – Jonesey95 (talk) 20:07, 2 September 2026 (UTC)

Fair, but adding a replace parameter really is an unnecessary step. If we limit ourselves to altering the SD template to treat noreplace as the default, then we effectively have first-use-wins for the magic word. That seems to be a fairly cheap way of avoiding the (admittedly rare) template issues. That would also serve to fix (but also mask) issues with unnamed transclusions, but I think that they should be hunted down and fixed as a separate issue — GhostInTheMachine ^{talk to me} 20:14, 2 September 2026 (UTC)

Certes has provided proposed code above. What is your proposed code for doing what you suggest? – Jonesey95 (talk) 21:38, 2 September 2026 (UTC)

If I've understood correctly, treating noreplace as the "default" without introducing a |2=replace option simply means mandating noreplace everywhere. That's as simple as replacing {{{2|}}} by a hard-coded noreplace, so parameter 2 is always ignored and becomes deprecated. This loses functionality (the ability to replace an earlier SD), but perhaps that's functionality we never use and never will use. I'm just concerned that someone may find a use case for it, and its absence may come back to bite us later. Certes (talk) 10:23, 3 September 2026 (UTC)

I think that your concern is inherently honourable, but as neither of us can think of a valid use case for the replace parameter, I feel that we should kick that can down the road somewhat. Making any overall change will take a moment, (agreeing to, not the code itself) so if somebody does think of a valid use case we can debate that when it happens. — GhostInTheMachine ^{talk to me} 12:36, 3 September 2026 (UTC)

New day. Reboot. Summarise

Let us consider the possibility that the SD template is changed to ignore any noreplace parameter (this is a thought experiment so just ignore the parameter for now, we can deprecate it and expunge it later) and always pass noreplace to the magic word.

This will give us the first-use-wins behaviour that could (should?) have been coded in back in 2017. Coupled with the current policy of always putting any SD template at the start of an article, this seems to give us everything we need:

• Articles should only ever have one SD template and so, if it does have one, it is at the start, is the first-use, so wins and continues to provide the SD for the article.
• Articles without an explicit SD template, devolve the setting of their SD to the infobox or some other general template.
• Infoboxes should only ever set one SD and so it will be used as the default whenever an article fails (or choses) not to have a SD of its own.
• Should an Infobox call other templates that also set a SD, then the infobox wins if it sets the SD at the start. (This is current standard behaviour.)
• Articles using transclusion to import text from other articles will not suffer any issues from importing too much stuff such as the SD from the target.
• Since the magic word is always being fed noreplace, the MW API will always return the same SD as the article itself.
• If a SD has been set in the article itself, the SD gadget always displays the correct SD.

Possible failure modes:

• An article has two (or more) SD templates. This is evil already, but our modified SD template defaults to the correct behaviour. The first SD template wins and any others have no effect.
• An article has an explicit SD template placed after the infobox. The infobox SD wins, whereas currently the article SD wins. We already judge this situation to be evil, so it still being evil in the new world does not worry me much. We might be able to set a tracking category if the SD template is used after the first line (first few lines??) of the article. I expect that the handling of that would generate an "expensive" template call. Not very worrying as the infoboxes often already cache the page source...

Big wins:

• Code in infoboxes that wants to set a SD no longer needs to perform the expensive "is there already a SD template" test.

Is the above a fair summary of the effects? Have I missed anything? — GhostInTheMachine ^{talk to me} 12:27, 3 September 2026 (UTC)

I think that you have summarized it well. We haven't been able to think of a use case for suppressing "noreplace". Presumably, if one exists, it will crop up after we deploy this change, and we can use some variant of Certes's code to handle it. – Jonesey95 (talk) 12:46, 3 September 2026 (UTC)

Thanks. That's a useful summary which matches my understanding too, except that I don't quite understand the "big win". Do you mean that templates can stop using {{Has short description}} or similar, which expensively reads the article wikitext? If so, and the purpose of that check is to prioritise the article's explicit SD, then the proposed change won't help (or hinder) that process. If the article's explicit SD comes before the template call then we can already prioritise it by using noreplace in the template. If the article's SD comes after the template call, which is unusual and violates MOS:ORDER, then the expensive check is still needed... unless, of course, we suppress noreplace in the article! Could that be the elusive use case for |2=replace? Certes (talk) 13:55, 3 September 2026 (UTC)

Enthusiastic as I am about this proposal, I do feel obliged to report some bad news. I was disappointed to find that we have several thousand articles, even GAs like Angata, where the SD is hidden away at the end of the page. This proposed change potentially has a negative effect there, as their explicit SDs stop replacing template-generated ones. Certes (talk) 14:22, 3 September 2026 (UTC)

Grumble mutter... that is why infoboxen need the {{Has short description}} call. Since we already regard putting the SD at the end of the article as "evil", we should fix those evil articles first.

I tried cooking a search, but searches generally do not have an awareness of the location of a match. "Infobox then SD" as a regex found some 1400 matches. {{#invoke:Is infobox in lead|main}} searches for the SD before any "==". I tried that as a regex and it timed out with 251 results. What search did you use? — GhostInTheMachine ^{talk to me} 15:20, 3 September 2026 (UTC)

I used this search to check for infoboxes before SD: 447 articles beginning with A. Some like Assynt also have a SD on line 1 just for good measure, which will of course be sneakily replaced by the one hidden near the bottom, no doubt leading to more scratching of heads. Certes (talk) 15:34, 3 September 2026 (UTC)

Good catch. Someone (or some bot) using AWB could presumably clean those up to make them compliant with MOS:ORDER. If one of you has AWB access, does running genfixes on one of these pages move the SD to the top? A bot/AWB run would probably get us at least 90% of the way to being able to implement this change. Having worked on Wikipedia for a while, I remain 98% confident that there are other edge cases that we will find only by implementing this beneficial change. – Jonesey95 (talk) 15:57, 3 September 2026 (UTC)

(ec) I'm digressing again but 42 A articles have two or more explicit SDs. Some pages like Aitebaar have the second SD on line 2, just to make sure, but the bonus SD could appear anywhere. This looks like an AWB task, with perhaps a Check Wikipedia report to catch new miscreants. Certes (talk) 15:58, 3 September 2026 (UTC)

Hunting articles with 2 (or more!) SD templates is part of my standard monthly routine. Sadly, I am a little behind on that - I have just used a canned search to add 93 such articles to my TODO list. Adding your search should keep me busy a while longer, but I think we should aim to fix these articles. They are breaking MOS:ORDER, so we should not be basing our plans around coping with them. — GhostInTheMachine ^{talk to me} 16:02, 3 September 2026 (UTC)

Thanks for your sterling work. I've fixed a few too. I think all the multiple SDs are now gone, though of course more will appear. Certes (talk) 22:19, 5 September 2026 (UTC)

Some are sure to return. I have altered my scanner so that it checks every day — GhostInTheMachine ^{talk to me} 16:36, 6 September 2026 (UTC)

Genfixes didn't seem to do anything to Angata or Assynt but I'm an AWB novice and may have pressed the wrong buttons. (I edit regularly with JWB but it doesn't do genfixes.) It should be easy (though tedious) to seek and destroy these cases with AWB or JWB. I'm not sure I'd trust a bot: a SD in the wrong position may have other problems, and picking the better of two (or more?) SDs certainly needs a human. Certes (talk) 16:13, 3 September 2026 (UTC)

I've just fixed the articles beginning with Z as a test, so the rest should be feasible in AWB/JWB. Perhaps the multiple SDs should be done first as they need more care; there should be about a thousand.

Here's another useful search which finds SDs after the bold text marker found in almost all article leads (and the AfD template, which I've excluded). Certes (talk) 16:43, 3 September 2026 (UTC)

I use AWB for all sorts of things, but the SD problems are often a symptom of further issues, so I have been doing them all manually. Heavy metal music at a high volume seems to help. — GhostInTheMachine ^{talk to me} 16:30, 3 September 2026 (UTC)

Yes, I've found one editor copying the article title into the SD, revised their contributions and had a word. A daily report catches SDs which match the title exactly (amongst other errors), but not variations. Certes (talk) 22:23, 5 September 2026 (UTC)

Restarting again: we now have few or no articles with multiple SDs, but 10,000+ with SDs a significant distance from the top of the page. Making noreplace the default could affect those articles: a generic SD generated by an infobox would override an explicit SD hiding later in the article. This may or may not be a good thing. Is it time to deploy a bot or AWB to move the SDs to the top, or would that fall foul of WP:COSMETICBOT or be undesirable in other ways? Certes (talk) 16:16, 15 September 2026 (UTC)

Since the SD should be at the top, asking a bot to move it should be OK. If there are then issues with articles, then there were probably issues with them before. Perhaps the bot can log the SD before and after it edits. Most changes should be from the infobox default to the moved SD value. We could then check the log to deduce patterns and maybe spawn misc clean-ups. I cannot think of a circumstance for which the bot introduces a real problem. — GhostInTheMachine ^{talk to me} 17:32, 15 September 2026 (UTC)

Do we know whether there are many examples of articles whose SD is deliberately later as a workaround for this transclusion issue? A bot move would break all of those, if they exist. —David Eppstein (talk) 17:56, 15 September 2026 (UTC)

I cannot think of any examples, or any realistic logic for doing that — GhostInTheMachine ^{talk to me} 18:41, 15 September 2026 (UTC)

It's conceivable that Ann Artiste#Some Album might transclude the lead of Some Album, unwisely including its SD, and someone has moved or copied Ann Artiste's SD down below so she gets described as a singer rather than an album. Moving SDs to the top would undo that kludge, but making noreplace the default would fix the problem properly and make the workaround unnecessary. Certes (talk) 20:33, 16 September 2026 (UTC)

Intentionally blank for list of works by person

Most list of works by a person are set to "none" by default. Beginning in 2022, that replaces "Wikipedia bibliography" or "Bibliography" are to be set by "none". For example in Steven Spielberg filmography or BTS videography, which is set to "none" and its not a definition. ~2026-57729-63 (talk) 00:34, 29 October 2026 (UTC)

Did you have a question? – Jonesey95 (talk) 01:32, 29 October 2026 (UTC)

BTS videography isn't a bibliography, because they haven't written any books. There is an argument for explaining who BTS are to help readers unfamiliar with pop culture, who might guess that the article lists behind-the-scenes documentaries or the films of Broadcast Television Systems Inc.. Otherwise, having no description is better than having a misleading one. Certes (talk) 09:18, 29 October 2026 (UTC)