# Wikipedia talk:Disambiguation

WikiProject Disambiguation
This page is within the scope of WikiProject Disambiguation, an attempt to structure and organize all disambiguation pages on Wikipedia. If you wish to help, you can edit the page attached to this talk page, or visit the project page, where you can join the project or contribute to the discussion.

## RfC: INTDAB links to non-dab pages

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
Despite the amount written , this RFC was only about whether redirects that end in "(disambiguation)" should be allowed to target non-disambiguation pages. While numerically there is no clear "winner", many of those opposing based their arguments solely on the fact that set-index articles or name lists are not disambiguation pages and that this might be confusing to some readers to be redirected as such. However, when challenged whether readers have previously indicated such confusion, there was no further evidence provided. Hence, the argument of "misleading", "surprise" or not "least astonishment" was not as convincing. The discussion got sidetracked quite a bit about the difference between SIA and DAB pages but without any real reason since no one actually doubted that DAB and SIA are different. Furthermore, despite multiple challenges, these opposers have not demonstrated any actual need to remove such redirects.

In the end, when considering the policy-base of the arguments for or against such redirects, one has to also remember that redirects are governed by the WP:R guideline. Judging the arguments based on WP:R#DELETE and WP:R#KEEP, the main argument made in favor of deletion could be summarized under DELETE #2, potential for confusion. However, as pointed out multiple times, the risk of confusion is minimal because the distinction between DAB, SIA and name-lists is one most readers are unlikely to know about and even if they do, confusion could only happen if they are redirected from a "(disambiguation)" page to a SIA instead of the correct DAB page. But that can be dealt with by retargeting. On the other hand, a number of users have argued that these redirects are useful, which is a reason to keep them per KEEP #5.

So to answer the question of this RFC: Consensus is (slightly) in favor of having redirects that end in "(disambiguation)" that target SIA or name lists in general, although single examples might exist where the redirect should be deleted. The question whether such redirects should be created was not part of this RFC, although there was no consensus for that amongst those who debated it nonetheless. Consensus might change if and when those opposing such redirects can provide actual examples of users being confused by such redirects. Regards SoWhy 18:02, 23 September 2018 (UTC)

Should there be Foo (disambiguation) redirects that target non-disambiguation pages that contain a list of articles, for instance where Foo is a {{Surname}} page, or {{Set index article}}, or a list article? Shhhnotsoloud (talk) 07:01, 26 June 2018 (UTC)

Extended content
• No. Such pages should not be created, and if they exist then they should be deleted unless there is a page history to preserve. Such redirects are technically incorrect and infer that the target is a disambiguation page when it is not (and therefore is not subject to dab page restrictions such as references and redlinks unsupported by bluelinks). Even if the base name page has a similar function to a disambiguation page, a (disambiguation) redirect would be an orphan, and a user is only ever going to arrive at it via the search box (in which case if it wasn't there the user would navigate to the base name), or by some sort of direct navigation, for some reason deliberately trying to avoid the base name, which would result in "Wikipedia does not have an article with this exact name." and advice to use Search. There is a balance between avoiding those (I would say unlikely) occurences versus creating/maintaining thousands of INTDAB links to non-dab pages. Shhhnotsoloud (talk) 07:31, 26 June 2018 (UTC)
I realise that you're playing devil's advocate here, but are you "proposing" just that we tolerate existing redirects, that we create a full set with no further changes, or that we divert all legitimate links via them, as we do with dab pages, to aid detection of poor wikilinks such as She beat Murphy in the final or He served on HMS Abdiel? Certes (talk) 10:46, 26 June 2018 (UTC)
Hello @Certes: don't read too much between the lines. I'm just trying to see if there can be a consensus that leads to a change in the guidance, to stop repeated discussions at RfD. If the answer is Yes then new redirects could/should be created; if the answer is No then existing redirects could be deleted via RfD unless there is a reason for an exception to guidance; neither answer infers mandatory routing. Shhhnotsoloud (talk) 18:44, 26 June 2018 (UTC)
• No. Such pages should not be created and should be deleted where they exist. If they have article history to preserve, that history should be preserved under an appropriate title (i.e., not "XXX (disambiguation)"). SIAs (including anthroponymy lists) are valid link targets. Bad links to them should be detected as with bad links to any other article. -- JHunterJ (talk) 12:13, 26 June 2018 (UTC)
• No. Per the 2017 comments of Widefox at a relevant RFD, such redirects violate the principle of least astonishment in user interface design. Users will be surprised at being redirected to a non-dab page when the redirect is has "(disambiguation)" in the title. —hike395 (talk) 13:49, 26 June 2018 (UTC)
• Do you have any evidence that anyone looking for a page that disambiguates X has ever been surprised at landing at a set index of X? I certainly never have! Indeed every single time I've found exactly what I was looking for. Thryduulf (talk) 23:34, 26 June 2018 (UTC)
That would require a user study, which has never been the standard of proof necessary for user interface decisions at Wikipedia. —hike395 (talk) 06:42, 27 June 2018 (UTC)
Is a user study really beyong our reach? Let's ask a knowledgable editor about what steps need to be taken so that for a limited period of time all (or some) wikipedia users who follow a certain kind of redirect will be asked, when arriving at the target, to answer a short questionnaire. – Uanfala (talk) 19:12, 28 June 2018 (UTC)
@Uanfala: this isn't an "easy" type of thing to do, and even more so if you want it to apply to "readers" as well (what about the ever popular mobile-only readers including mobileapp-users?). — xaosflux Talk 21:51, 28 June 2018 (UTC)
Only on an opt-in basis, kind of like WP:FRS. 20:07, 28 June 2018 (UTC)
So why are you asserting without evidence that such redirects violate the principle of surprise, particularly when there is much anecdotal evidence to the contrary? Thryduulf (talk) 10:11, 27 June 2018 (UTC)
Thryduulf, I feel like you are bludgeoning the discussion. From reading the comments, I think that JHunterJ, Widefox, Tavix and I all believe that the difference between a dab page and a set index article is evident to readers as well as editors, because of the difference in formatting and content. You (and perhaps SMcCandlish)) believe otherwise. This is an inference about readers' mind state, and hence will be difficult to prove or disprove without user studies. We cannot satisfy your demands for evidence. Is there a compromise that can be worked out? —hike395 (talk) 02:58, 28 June 2018 (UTC)
That's tautological and meaningless. Of course if the format is different, readers can see a difference. They didn't have their eyes evaporate! But it has nothing to do with the substance of the matter: If you put in "Foo (disambiguation)" looking for people surnamed "Foo", and we have a name list article of notable people by the name, that's functionally identical at least in that aspect to a DAB page and it is the page you want. It's "user-hateful" for WP to spit "Wikipedia does not have an article with this exact name. Please search for ..." at you – to effectively lie to you and tell you that WP doesn't have what you're looking for. Thryduulf is asking the same questions of multiple parties because they're all making the same weak "only thinking about the editor side and not about readers" points, and all refusing to address the substantive one. 03:17, 28 June 2018 (UTC)
User:SMcCandlish, when we have both a dab and an SIA, would you propose redirects with "..(disambiguation)" targeting both, or equally valid to target either? (depending on the primary topic) Does that common case, for example with surnames, illustrate just one unintended consequence of extending to SIAs? 08:46, 28 June 2018 (UTC)
One redir can only point to one article (unless you make some kind of ugly, manual soft-redir page), so it would naturally go to the real DAB page, which would also list the SIA page in it. We're only talking about "(disambiguation)" pages with no actual DAB to point to, but which could usefully go to an SIA or 'nymy page, at least temporarily. 10:52, 28 June 2018 (UTC)
When you say "naturally", no, it's not clear what your proposal involves apart from a general desire to extend redirects to pages that don't have a need for such a redirect. I'd use the term unnatural (or WP:ASTONISH) for a "xxx (disambiguation)" redirect to target anything other than a disambiguation page, and the term cargo cult for the concept. To help tease out, I've broken down the common scenarios of SIAs and dabs below, so we know more of what you're proposing. 15:06, 28 June 2018 (UTC)
Continual denialism of the obvious, on which you've been called out repeatedly, is not going to make anything less obvious or change anyone's mind. Please stop. 15:46, 29 June 2018 (UTC)
I'm not sure what you consider obvious (or have any idea what I've been "called out repeatedly" on, but if you explain I will reply), ...but belief isn't as convincing as reasoning. Let me be clear about the status quo - the burden is on those who wish to convince others of a change to the consensus - SIAs are not dabs. How you treat others just because they disagree with you is your choice. Graham's hierarchy useful for a more convincing argument? 21:11, 29 June 2018 (UTC)
I'm not getting frustrated with you because your opinion differs. It's because you're playing "I can't hear you" games and turning the discussion endlessly circular. It's a waste of time. Both Thryduulf and I have been over every detail of this in multiple forms, and will not be goaded further into recycling the same material (well, I guess I can only speak for myself, but am firmly predicting). Graham's doesn't apply here; there's no convincing to do, because your mind's already made up and you're transparently filibustering with argumentum ad nauseam in the face of every argument presented to you which never address and just pretend you didn't see it. 07:16, 1 July 2018 (UTC)
• No. Per reasoning above. Has the question been asked "why should they be created?" Yes, there's a reason to create them targeting dabs - to eliminate intentional incoming (say INTDAB) links from being flagged up as needing fixing. Any extension of that to other types of pages needs justification. A counter argument (ie keep old ones, irrespective of target or history) has come up at CSD (both for G6, and G8) based on one editor's desire to use the vestigial redirects to avoid primary topics or some such argument (which I confess I don't understand further than conservatism. That counter argument has made deletion controversial hence non eligible for CSD, although I believe the advocacy of a navigation hack shouldn't prevent previously uncontroversial maintenance after broader discussion/consensus.) 15:15, 26 June 2018 (UTC)
I note that Patar knight has expressed a view supporting the existence of these redirects, and want to be sure that they are aware of this RFC in case they wish to explain their position. --R'n'B (call me Russ) 17:04, 26 June 2018 (UTC)
• Yes, always for set index pages, allow but do not require for surname pages. People extensively use these links to find articles when they know or suspect that the article they are searching for is not the primary topic but do not know how it has been disambiguated. These links enable them to quickly find what they are looking for without being required to know whether we have chosen to call our list of articles a disambiguation page or a set index (the distinction is lost on almost everybody who is not a member of the disambiguation project) and without first going via a page they know they do not want (for people on slow and/or expensive connections this is a serious consideration). I'm a Wikimedian of nearly 15 years standing and I cannot predict which a given title will have, so we cannot assume readers will know or understand. I agree this was not the original purpose of (disambiguation) redirects, but it is an emergent feature of them and removing it will make things harder for the reader and thus harm the encyclopaedia. Thryduulf (talk) 21:05, 26 June 2018 (UTC)
If the title of a set index needs disambiguation as well as set indexing, both pages should exist, not be redirected to the other. Set index articles don't follow disambiguation style for a reason: disambiguation pages are navigational pages, not articles. Set index are list articles. If the set index is in the way of navigation, use navigational tools to address the problem, rather than hindering the readers needed navigation by making them use a list article for it. -- JHunterJ (talk) 12:47, 27 June 2018 (UTC)
Another straw man - if a dab page exists at Foo (disambiguation) nobody is arguing that it should be replaced with a redirect. If the base title is a dab page and there is also a set index for that title then they should both link to each other and the (disambiguation) redirect should point to whichever is the more appropriate (most likely the disambiguation page, but there might be exceptions). The style and formatting of dab pages vs set indexes is, I repeat, completely irrelevant to this discussion - they are both pages from which people navigate to other articles with similar titles, which is exactly what someone searching for a (disambiguation) title is looking for. Thryduulf (talk) 22:46, 27 June 2018 (UTC)
Yep. All this "they're formatted differently" and "they're classified differently" and "we wrote them for different reasons" argument is the tail wagging the dog. Those are editor-facing arguments that don't have anything to do with the reader experience. 23:25, 27 June 2018 (UTC)
Yes SMcCandlish, the issue is caused by the seemingly inconsistent duality in the current definition of SIAs - should they be linked to or not? Are they for navigation or not? Are they for readers or projects? References or not? They exist in this murky world between lists and dabs. Treating them as dabs with regard to extending dab redirects logically follows the presumption that they shouldn't be linked to. (I presume we all agree that linking to surname articles is OK, as the counter reality.) It would be better to fix the definition than all of us guess and extend presuming things which are incompatible with one of the dualities. Of course, we can ignore that and continue extending SIAs increasing the mess! 09:00, 28 June 2018 (UTC)
Whether a SIA is and/or should be linked to from articles is completely independent of whether (disambiguation) links should point to them - the redirects exist for the benefit of readers, allowing them to find the page they are looking for, whether or not they are linked to anywhere (which is normal for redirects, there is nothing special about these particular ones). Thryduulf (talk) 09:30, 28 June 2018 (UTC)
My understanding is that they came into existence to allow indirect linking to dabs. Please correct me if I'm wrong, as that fact should be easily verifiable. That doesn't denigrate any unintended usage, but let's be clear about the facts. 09:45, 28 June 2018 (UTC)
Yes, as I've noted elsewhere in this discussion, that was the original purpose of the (disambiguation) redirects. However they have since gained an additional purpose that is at least as valuable (for readers, arguably more so). Those who wish to restrict these redirects to only pages that meet the disambiguation page formatting rules are ignoring (or dismissing) this emergent use. Thryduulf (talk) 11:12, 28 June 2018 (UTC)
Thryduulf, when you say 1. "completely independent", but agree 2. that's the reason they exist for dabs. How can the two logically be true? What is the evidence of demand for this use case? (as I've pointed out, we're missing dab redirects that nobody seems to miss, indicating this isn't a big thing, and of course it's a hack, so hacks are great while they work but it's a big change to have hacks as supported features). 13:34, 28 June 2018 (UTC)
(edit conflict) You mean evidence other than the fact that I use them in this manner, that others commenting when they've come to RfD say they use and page view statistics showing that they get used? Not every single one is necessarily going to be used, but why does that matter? If a redirect exists when somebody tries to use it then the person using it wins and the encyclopaedia wins because someone has found what they are looking for and nobody loses. If a redirect exists and nobody uses it nobody loses. Your description of this as a "hack" turning into a "supported feature" over-eggs the pudding about the effort required - supporting them (letting them exist) actually requires less effort than not (discussing and deleting them). Thryduulf (talk) 13:52, 28 June 2018 (UTC)
re 1 and 2 both being true: It's very simple - just because (disambiguation) redirects to disambiguation pages were created for one reason doesn't mean that (disambiguation) redirects to set indexes need to be used for that same reason. It's possible to use these redirects as search targets completely independently of whether they are linked. Thryduulf (talk) 13:57, 28 June 2018 (UTC)
I'm aware from previous discussions that you strongly believe in this, being something you personally use. The above is, however, anecdotal evidence of demand. Anything stronger? Forgive me if you read "hack" to be pejorative, it's not meant so, it's worse than that - it's the cold/hard correct term in the industry, and officially supporting hacks can be a costly mistake. 21:31, 29 June 2018 (UTC)
Look at pretty much any time these redirects have been nominated at RfD and you'll find people saying they find them useful (which is an explicit reason not to delete a redirect) and there is a ton of hard data that shows only a fraction of readers edit the encyclopaedia at all (for all its downsides the article feedback tool generated many comments from people who new how to navigate Wikipedia but had never used a talk page, let alone contributed to an XfD), if you look at the page view statistics for many, maybe even most, of these redirects you will find clear evidence of human use. Whether this is anecdotal or not is debatable, but it contrasts with the complete lack of any evidence (anecdotal or otherwise) that they are in any way shape or form harmful. Thryduulf (talk) 14:40, 30 June 2018 (UTC)
A) Isn't that's an WP:OTHERSTUFF argument? B) editors at RfD need to take this broader RfC into consideration, clearly C) My definition of hard data for this proposal is, for example, %'s, click through rates, reader numbers, user surveys, use cases, usability studies, A/B testing -> none of this type of hard data has been presented on this proposal here or the handful of RfDs I've seen. There's not one of those, is there? D) In fairness, absence of evidence isn't evidence of absence, but so far as presented this is thoroughly unconvincing. 21:09, 30 June 2018 (UTC)
A) No it is not an OTHERSTUFF argument because it is using the information presented in multiple discussions about multiple individual redirects of this type to provide evidence in a discussion about the class of redirects of this type. B) that would be impossible as those RfD discussions happened before this RfC - and this RfC is not (at least yet) reflective of a wide consensus as it the only participants have been RfD regulars and those deeply involved the existing guideline. C and D) Firstly this is massively over the top, as has already been explained, use cases have been repeatedly explained, click-through rates are not relevant as that would be a measure of the utility of the target not of the redirect, I can't conceive of how A/B testing would even be possible (a redirect either exists for everybody or for nobody), and finally you are the one who is asserting these redirects are harmful and you need to provide evidence of that (which you and others have repeatedly failed to even attempt). Thryduulf (talk) 10:17, 6 July 2018 (UTC)
Thryduulf Consensus is that SIAs are not dabs per Wikipedia:SIANOTDAB. The burden is actually on anyone that wants to overturn that consensus. A redirect that has the parenthesis to something that it is explicitly not is WP:ASTONISH. I don't have to provide evidence of that, as I'm not attempting to change consensus. I have, however, been clear about that harm, so let me repeat: UI consistency harm, so harm for readers. Any proponent of using them to target SIAs needs to at least consider there's a cost, and there's no consensus on the benefit. Most/all these are redirects left after conversion of a dab to an SIA, so they have ceased having functional purpose per guideline. In that context, more pertinent than "harm" is "vestigial" (aside: I once had the pleasure to be at a lecture of Stephen Jay Gould, where alongside vestigiality, he showed many photos of elements of European cathedrals (spandrels), so that would make dabs spandrels in this analogy, the lecture comes to mind each time we discuss this). 00:08, 30 August 2018 (UTC)
Such redirects aren't always vestigial: I've sometimes seen editors creating such redirects, at least to surname SIAs. But it's probably true that most of the redirects were originally targeted at dabs – but then these are often the situations where one editor has converted the dab to a SIA and another editor is likely to be found who believes that this SIA ought to be converted back into a dab. So I wouldn't want to caryy the DAB/SIA distinction so far up the hill here. – Uanfala (talk) 00:34, 30 August 2018 (UTC)
@Widefox: As I'm sure has been pointed out many times elsewhere in this debate, that SIAs are not disambiguation pages is a technical distinction that very few readers (and not all editors) know about, even fewer care about and is not at all relevant to the question at hand. I'm also not attempting to change anything about the distinction (because it's not relevant here, as repeatedly explained). I know I have definitely explained several times why it is not astonishing in the slightest (and nobody has ever provided evidence to the contrary, despite repeated requests) to search for Foo (disambiguation) and arrive at an SIA because what someone is looking for is a list of articles related to the title "Foo", either for the list itself or because they know what they are looking for is (probably) not the primary topic but don't know what the article is titled. Thryduulf (talk) 07:26, 30 August 2018 (UTC)
@Uanfala: agree, I said most. I've flipped some myself. I'm sure we all know the raison d'etre of the redirects is to enable the mandatory linking via "(disambiguation)" to dabs. As we allow direct linking to SIAs, it's vestigial by definition when targeting an SIA. Any secondary use doesn't have consensus, but has been thin end of the wedged by hanging on to these vestigial ones. The big picture is 1. many (tens?) thousands of dabs are missing a redirect, which would be a bigger gain for proponents of the secondary use, and I see no desire to fix that low hanging fruit despite this being pointed out, 2. many (majority?) SIAs cannot have such a redirect anyhow, as there's an existing dab. This is quite perverse considering. 12:15, 30 August 2018 (UTC)
as others have said, it's not that I'm not listening, I'm not convinced. If one rejects the consensus that SIAs are not to be treated as dabs (and downplays it as a "technical distinction", and in the absence of consensus to treat them equally with respect to creation of (disambiguation) redirects (and given that dabs need the redirects to enforce linking via them, SIAs can be directly linked to), then one is left preserving vestigial redirects, which isn't a useful state of play IMHO, it's somewhat POINTY considering the low hanging fruit of creating thousands of missing redirects to existing dabs that would serve your use case better. Initially you were under the false impression they are bot created, which I've attempted to inform you many are still missing. I will assist if you wish to take up extending/fixing the bot so these are automatically created on all the missing dabs. 12:15, 30 August 2018 (UTC)
• ──────────────────────────────────────────────── @Widefox: Again with the straw men. I'm not rejecting the consensus that the SIAs and Dabs are not the same thing (it's completely irrelevant to this argument and I don't have a strong opinion about it). I'm not rejecting the consensus that dabs should be linked to only via (disambiguation) redirects (I agree with it). I'm not rejecting the consensus that SIAs can be linked to directly (I agree with it). I would like to see a bot create INTDABLINK redirects to disambiguation pages, but (a) I don't have the skills to do that and (b) it's not relevant to this discussion. This discussion is only about allowing (disambiguation) redirects to SIAs and nobody has provided any reasons why they should not be. Thryduulf (talk) 13:04, 30 August 2018 (UTC)
Rejecting or ignoring consensus WP:SIANOTDAB is a fair portrayal of your position, as underlined by you just saying "completely irrelevant to this argument". The topic is about treating them the same or similarly with respect to these redirects, a change to the consensus at WP:SIANOTDAB which you say is not relevant. I find it astonishing that much more missing redirects can be created to existing dabs than can be preserved by hanging on to vestigial redirects that now fail to target a dab. If this was such a big issue as claimed, then the low hanging fruit would be top priority. I highlight this, as it is direct evidence that there is no recognised issue cause by the missing redirects, which is direct evidence that there's no recognised problem that needs fixing from a readers perspective invalidating the secondary usage argument as proposed here. It's thoroughly unconvincing from a lack of evidence of demand. 13:27, 30 August 2018 (UTC)
No matter how many times you try to claim otherwise, I'm still not rejecting or ignoring that consensus. Allowing (disambiguation) redirects to both of them does not mean involve treating them the same, it just means that readers can find them. Thryduulf (talk) 14:10, 30 August 2018 (UTC)
It treats them the same in this regard, redirects. There would be no difference, so that's the same. Disambiguation is clear to create them, they're functional and dependent on a dab page. There's nothing in SIA about creating them, and even if created they would not provide that essential raison detre function (linking). If it is a straw man then please correct me, it is factual and logically correct statement that you disregard that functional different and replace it with a search hack to justify proposing they be treated the same with regard to a redirect. Although not explicitly disallowed in WP:SIANOTDAB, it's implicit and bolded that they are not the same, not to be treated the same (formatting etc). You may consider them as you wish, but we go by consensus. At RfD, there is more a presumption of redirects are cheap and harmless which is why we have this lack of consistency of no consensus to create, but newly contested at deletion, when it was previously uncontroversial. It feels like routine maintenance is being held hostage to a minority idea that has no consensus. I've G6 and G8ed them in the past. Maintenance should be easy, and the vast majority were happy before this became controvercial and effort. Now, of course we can change it, but this is why this is going nowhere currently, as other editor's concerns and desires to understand creation are not being addressed so far. Anyone is allowed to create redirects. The problem is there's no convincing argument per cost/benefit. A rejection of the proposal even by no consensus is status quo ante SIANOTDAB. 15:21, 30 August 2018 (UTC)
@Widefox: That's mostly just word salad - I can't understand almost all of what you are talking about, let alone provide a coherent response, so I'll just pick out the few comprehensible snippets. Yes the primary reason for "(disambiguation)" redirects existing to disambiguation pages is per WP:INTDABLINK, but that's not relevant at all (as repeatedly explained) - the secondary use for "(disambiguation)" redirects to disambiguation pages is to help readers find the content they are looking for without needing to navigate via content they know they are not looking for is equally valid to the primary use. That the same use for "(disambiguation)" redirects is the primary use when pointing at SIAs but the secondary use when pointing at dabs is true but utterly irrelevant to how useful they are. It's also not a "hack", it's an emergent use that wasn't anticipated when they were first created, but that's also totally irrelevant to everything we're discussing here. SIANOTDAB does not mention redirects at all, and even if "(disambiguation)" redirects do target both, that is not treating them the same in any way that has any impact on the differences between them. The status quo ante is that there is no consensus for or against these redirects, and no consensus that speedy deletion G6 applies to them (and by definition therefore it does not, as speedy deletion criteria only apply to pages that unambiguously meet the criteria). SIANOTDAB is not relevant to this. Thryduulf (talk) 10:28, 1 September 2018 (UTC)
Yes, I'm amazed somebody thanked you for something so incomprehensible. I may be the most vocal editor here (it seems almost everybody else has given up in the face of the IDHT and straw men), but it is not just me - look at every time that these get nominated at RfD. If it was just me challenging them (I can't remember the last time I challenged a speedy deletion) then they would still be deleted per G6. If the target page exists, even if it is irrelevant, then G8 does not apply and anyone deleting any such redirect under that criterion needs to stop it immediately. The rest of what you say has been answered multiple times already. Thryduulf (talk) 16:14, 1 September 2018 (UTC)
Clarity is good. How about this: After this RfC, but irrespective of the outcome, I can understand getting these redirects accepted as dependent pages. Then CSD would apply (whichever fits better G6 or G8). Many editors on this page agree they should be able to be deleted CSD if they fail to target a dab, as was the previous consensus. 18:42, 1 September 2018 (UTC)
• No. Set indexes are not disambiguation pages, so labeling them as such using redirects is misleading. -- Tavix (talk) 21:12, 26 June 2018 (UTC)
• How is someone being misled by arriving at a page that disambiguates articles that have or could have similar titles (which is exactly what both disambiguation pages and set indexes do) by the presence of a (disambiguation) redirect? In terms a reader will understand, what is the functional difference (i.e. ignoring what types of formatting our style guidelines permit) between a disambiguation page and a set index? Thryduulf (talk) 21:50, 26 June 2018 (UTC)
• Because a set index is not a disambiguation. -- Tavix (talk) 22:01, 26 June 2018 (UTC)
• That does not answer any of the questions I asked. What is the functional difference to a reader? How is arriving at a set index when looking for something that disambiguates misleading? Simply repeating that it is misleading does not actually make it so. Thryduulf (talk) 23:32, 26 June 2018 (UTC)
• See WP:SIANOTDAB. -- Tavix (talk) 02:43, 27 June 2018 (UTC)
• That still does not answer the questions. That page explains how the formatting differs (in some cases), but still does not explain how they are functionally different from a reader's perspective; nor does it even attempt to explain how arriving at either when looking for something that disambiguates is misleading. Thryduulf (talk) 10:11, 27 June 2018 (UTC)
• Sorry, I'm not answering your questions to your satisfaction no matter how often you ask. Stop badgering me (and others for that matter). -- Tavix (talk) 12:38, 27 June 2018 (UTC)
• You assert that (disambiguation) pages redirecting to set indexes is "misleading", asking you to explain how it is misleading could not be more relevant. Thryduulf (talk) 12:53, 27 June 2018 (UTC)
Tavix is exactly right. Set index articles do not disambiguate titles. They list elements of a particular set and they follow list article style, not disambiguation style. -- JHunterJ (talk) 12:47, 27 June 2018 (UTC)
What's the functional difference between listing articles that do or could share similar titles while being part of a particular set and listing articles that do or could share similar titles while not being part of a particular set? Style differences are irrelevant to a reader who wants to find a list of articles that do or could share similar titles to their search term. Thryduulf (talk) 12:53, 27 June 2018 (UTC)
One functions as a list. The other functions as a navigational aid. -- JHunterJ (talk) 18:14, 27 June 2018 (UTC)
One is a list of articles that people use to navigate to those articles. The other is a list of articles that people use to navigate to those articles. How are they not both navigational aids? Thryduulf (talk) 22:49, 27 June 2018 (UTC)
I agree Thryduulf, to readers SIAs and dabs would be similar or indistinguishable. To writers, especially projects, they're crucially different. Wouldn't this writer bias be better fixed at the cause - the definition of SIAs to align with readers priorities not projects?... rather than treating SIAs as dabs for this redirect aspect? (Acting as a dab is only one of SIAs dualities, the other being acting as a list, which is incompatible with the proposed extension of this redirect to target them.) 09:39, 28 June 2018 (UTC)
There is no incompatibility. SIAs and disambiguation pages both work equally well for readers for navigation purposes, the (disambiguation) redirects therefore both work equally well whether they point to a disambiguation page or a set index article. That set index articles also function as articles while dab pages do not doesn't matter - people using these redirects find the page they are looking for whichever they end up at. Thryduulf (talk) 11:19, 28 June 2018 (UTC)
What's the evidence that SIAs are dabs "both work equally well", because if they do, why do we bother putting so much effort into dabs?! The consensus surely is that dabs are the best way to navigate (and let's not forget the majority are on small mobile screens, making the design and strictness of dabs more crucial), and anything not a dab is, by definition, not as good. How much less good would need evidence, but that's logically the consensus, and logically needs a convincing argument to change. 21:46, 29 June 2018 (UTC)
This is a combination of "I don't like set index articles" and "set index articles should be converted into disambiguation pages". Even if either were relevant to this discussion (which they aren't) you do not back up any of your claims with evidence - e.g. where is this "consensus that dabs are the best way to navigate" you speak of? (and note to be valid this consensus needs to include those people who are not involved with the disambiguation project and/or disambiguation style guidelines). Disambiguation pages do one job: Navigation. Set index articles do two jobs: Navigation and information. There is no evidence presented that either functions better than the other for navigation. Thryduulf (talk) 09:00, 1 July 2018 (UTC)
I see my question about evidence isn't answered in two months, but was just turned around into my motivations and evidence. The burden is on proponents to change consensus. Please refrain from inverting the burden. Consensus is WP:SIANOTDAB. It's clear to all the history is that SIAs are allowed to diverge from strict dab formatting as they are lists not dabs. As the dab format is solely and purely for navigation, logically anything else is less optimised for navigation. The assertion that they "both work equally well" hasn't been justified, and IMHO is illogical by design. 17:19, 31 August 2018 (UTC)
• Yes, exactly as per Thryduulf, who hit every single point I would have made. Other than to respond to some of the above "labeling" and "misleading" assertions, which are fallacious. The name of Page A has no labeling effect on Page B. And there's nothing faintly confusing about looking for a disambiguation page and finding a set-index article, surname index, or other things that probably originated as a DAB page and for the average user isn't really distinguishable from one. 22:55, 26 June 2018 (UTC)
The labeling and misleading assertions are accurate. Calling articles not-articles or not-articles articles is fallacious. Disambiguation pages and SIAs serve different needs, and where both are needed, both need to exist. If the goal is really to make them indistinguishable, try getting consensus to apply disambiguation style to a storm or ship index. -- JHunterJ (talk) 12:47, 27 June 2018 (UTC)
Please demonstrate (as repeatedly requested), with evidence, how it is misleading and how having a redirect from (disambiguation) to a set index page causes the latter to become something other than a set index page. The only reason set index articles exist is that the disambiguation style guidelines are too rigid for all purposes (which is entirely irrelevant to the reader, and indeed to most editors). If this wasn't true then there would not be arguments about whether a given page is actually a disambiguation page or a set index - it would be possible to tell unambiguously in all circumstances. Your average reader (and editor) really doesn't care (or in many cases even know) whether a given page they are reading is one or the other. Thryduulf (talk) 16:48, 27 June 2018 (UTC)
Please demonstrate, with evidence, how an article is a non-article. Disambiguation pages are not articles. SIAs are articles. QED. You are right, though, the average reader doesn't care, and I didn't care before, back when we could format what would eventually become SIAs as if they were disambiguation pages. But the SIA editors wanted more and more information on those nav pages, and made them articles instead, and objected when they were edited back down with navigation in mind. They can't be both things. If they are functionally disambiguation pages, then let us format them as disambiguation pages. But they aren't, so we don't. -- JHunterJ (talk) 18:14, 27 June 2018 (UTC)
I'm not claiming that an article is a non-article so asking me to prove it is a straw man argument. Lists of articles function as pages from which people navigate to other articles, regardless of whether they are a disambiguation page or a set index. If someone searches for Foo (disambiguation) (which they do) they are looking for a page which lists articles related to foo. If a page or redirect exists at that target they will find what they are looking for, regardless of whether the target is a disambiguation page or a set index - as I keep saying the formatting is completely irrelevant. If Foo (disambiguation) doensn't exist but a page listing Foos does then we, as editors, have failed as readers will not find the content they are searching for. Thryduulf (talk) 22:40, 27 June 2018 (UTC)
• No. The sole purpose of X (disambiguation) redirects is to distinguish links which deliberately target a dab from those which should be fixed to point to one of the dab's entries. That system only works if all such links go via the redirect. I can see a case for extending that convention to name pages and set indices but, as clarified above, that is not being proposed here. Having just some of the links go via the redirect is of no benefit; they should link directly and the redirects should be deleted. Certes (talk) 23:46, 26 June 2018 (UTC)
• Your first sentence notes the original purposes of (disambiguation) redirects, but completely ignores that they have gained other uses. Your second sentence is actually an argument in favour of more (disambiguation) redirects so that everything that intends to link to a list of articles can be distinguished from those that intend to link to one specific article. Extending the (disambiguation) convention to set indexes and name pages is exactly what is being proposed here. Your final sentence doesn't make any sense. Thryduulf (talk) 10:11, 27 June 2018 (UTC)
• Can we agree on this summary?
1. All deliberate links to base-name dabs should go via (disambiguation) redirects, and (thanks to some sterling efforts) nearly all actually do so
2. Currently, a few links to name/list/SIA pages go via (disambiguation) redirects but most don't; this is not helpful and should be changed to all or none
3. There is a reasonable case for all links to name/list/SIA pages to go via (disambiguation) redirects, but the established consensus is that none should
• The last two points may also apply to a few other page types. — Certes (talk) 11:12, 27 June 2018 (UTC)
• Your point 1 is completely correct, yes, and afaiaa is not disputed.
• There is a reasonable case that all intentional links to base name SIA pages should go via (disambiguation) or List of redirects, but most currently do not.
• There is a reasonable case that intentional links to base name pages about names (surname or other types of name) should go via disambiguated redirects (name), (surname), (first name) or (disambiguation).
• Redirects ending in (disambiguation) should be allowed for all pages that disambiguate articles, whether those are disambiguation pages, set indexes or name pages, and whether or not those redirects have any incoming links. There is a reasonable case that these should be created where they do not currently exist. Thryduulf (talk) 11:33, 27 June 2018 (UTC)
Set indexes articles and anthroponymy articles do not disambiguate articles. They are functionally lists, and styled for listing things, not for navigation. -- JHunterJ (talk) 18:14, 27 June 2018 (UTC)
False dichotomy that ignores how readers actually use them and why. This is a confusion of intended purpose with the purpose to which something is commonly put. I.e., it's bureaucracy for its own sake. 23:31, 27 June 2018 (UTC)
• (the duality issues with the definition of SIAs are above, but ...) SMcCandlish - dabs are for navigation only, everything else in WP isn't, including SIAs. That's by intention and usage. There's many types of pages that may be used for navigation, including SIAs and lists but their raison d'etre isn't solely navigation. In assistance of that sole purpose, the raison d'etre for the redirects is to assist that one aim as a dependent page, which doesn't apply to all SIAs (if we hypothetically classify SIAs into those which are used essentially for navigation, and those which have other purposes). TLDR - fix SIA's definition rather than extend necessary redirects to unnecessary pages. That's bureaucracy. 09:23, 28 June 2018 (UTC)
• That's a mixture of irrelevant, incorrect and nonsense. It doesn't matter what a page's definition is, or whether it exists solely for navigation or for navigation and other purposes. The existence of a (disambiguation) redirect pointing to a page that is used for navigation does not indicate anything about it's purpose, definition or anything else. That some of these redirects are also necessary to avoid links to disambiguation pages is correct, but that is entirely unaffected by the existence of redirects that do not have that purpose. Thryduulf (talk) 11:26, 28 June 2018 (UTC)
• You may characterise it as such, but I would characterise it as an attempt at detailing the consensus. The definition of what's a dab, and SIA are the consensus. The burden is on those who wish to change the consensus, with reasoned arguments, which I haven't seen yet here, so status quo ante. 13:48, 28 June 2018 (UTC)
• The definitions are irrelevant. A set index is a set index, however that is defined, whether or not a (disambiguation) redirect points to it. A disambiguation page doesn't stop becoming a disambiguation page, however that is defined, because some (disambiguation) redirects point to pages that are not disambiguation pages. I'm not seeking to change the definition of either. Thryduulf (talk) 14:01, 28 June 2018 (UTC)
• Stating that you believe the definitions (the consensus) is irrelevant doesn't reason your argument for what change is desirable. It's in bold that SIAs are not dabs, and not to be treated as dabs, but this would conflate them, against the consensus. Go ahead. 14:57, 28 June 2018 (UTC)
• But it will not conflate dabs and SIAs at all. Nothing about the pages themselves will change. A dab will still be a dab, an SIA will stil be an SIA, neither will be treated as the other in any way shape or form, neither definition will change in any way. The only difference is that people will be able to find what they want without being required to know in advance which has been used. Thryduulf (talk) 10:47, 29 June 2018 (UTC)
• Claiming it doesn't conflate is at odds with the fact that creating "(disambiguation)" redirects to SIAs is directly, irrefutably treating the SIA as a dab with respect to the redirect. That's conflation, and ASTONISHING users, and is a UI inconsistency. Users following the link will not know if the target is a dab or SIA due to the (incorrect) conflation, for instance. Writers will have to check if the target is a dab or SIA to know if it should be linked directly or not. There will still be many SIAs with no redirect, as the term already has a dab, resulting in an inconsistency for creating redirects to SIAs. 20:49, 30 June 2018 (UTC)
• The only confusion exists in the minds of those who are opposed to this proposal as far as I can tell. Nobody has presented any evidence of anybody searching for Foo (disambiguation) and ending up at a set index of Foo being at all confused (as has been repeatedly shown elsewhere). Your argument that a redirect from a technically incorrect name somehow conflates disambiguation pages and set indexes is laughable - they will remain separarate pages with separate styles and separate guidelines, etc. nothing will change about the content of either type of page. As for your comments about linking are also irrelevant - editors currently have to know whether foo is a disambiguation page to or not to know if it should be directly linked, so absolutely nothing will change in that regard. In fact it will actually get slightly easier because while there is no requirement to link to an SIA via a redirect there is no harm in doing so, whereas linking directly to a dab page does cause (minor) harm, so if one gets changed to the other (as happens) then no links will need to be changed. Thryduulf (talk) 10:26, 6 July 2018 (UTC)
• If there's confusion, wouldn't that indicate that the argument of the proponents is too weak or confusing to gain consensus, rather than some ad hominem just because others disagree?! Absence of evidence isn't evidence of absence. I do understand the desire for SIAs to be more useful for navigation, the obvious answer is get consensus to change them! I am vocally against supporting hacks. 17:40, 31 August 2018 (UTC)
• No. RfD should not be required either since G6 already covers them (routine cleanup). Note that 99.9% of these redirects were created by bots, have no useful page history, and have never been used. —Xezbeth (talk) 12:57, 27 June 2018 (UTC)
• G6 does not very much not apply to redirects pointing to set indexes as this discussion demonstrates they have clear use - even that this discussion is happening demonstrates that deletion would not be uncontrversial. Thryduulf (talk) 14:02, 27 June 2018 (UTC)
G6 covers this routine cleanup, as this discussion demonstrates. -- JHunterJ (talk) 18:14, 27 June 2018 (UTC)
• Except it's not cleaning up anything - it's making navigation significantly harder for our readers while not benefiting anybody. Thryduulf (talk) 22:40, 27 June 2018 (UTC)
• These sort of redirects come up at RFD from time to time and from what I've seen, they've tended to split opinions, with "no consensus" closes being the most common. Maybe G6 could have been applicable in the past, but with the current environment it's difficult to imagine how one can justify speedy deleting stuff that almost always fails to achieve consensus for deletion when discussed at the venues. – Uanfala (talk) 23:33, 27 June 2018 (UTC)
• Well put. Sadly I've lost count of the number of times I've had to remind various administrators that pages may only be speedily deleted (under any criterion) when a deletion discussion of that page would stand no chance of having any outcome other than "delete". Thryduulf (talk) 09:30, 28 June 2018 (UTC)
• Xezbeth, agree, but please see my comment above - it's been challenged at G6 and G8, making this RfC important, unfortunately. 08:38, 28 June 2018 (UTC)
• Comment. There are apparently 17,712 redirects affected by this discussion (quarry:query/27886: this query, courtesy of Cryptic, lists all redirects with titles ending in `(disambiguation)` whose targets are not members of Category:All disambiguation pages). – Uanfala (talk) 23:43, 27 June 2018 (UTC)
• Thank you, that is a very useful comment - it shows that there is likely a widespread acceptance of these redirects among the community. Thryduulf (talk) 09:30, 28 June 2018 (UTC)
• It does nothing of the sort. Half of those are talk page redirects, which are even more worthless. The remainder are as useless as they have ever been. Bobko_(disambiguation) for example has been used a whopping 1 time in the last 90 days. If I didn't just link to it then I doubt anyone else would have ever visited it. —Xezbeth (talk) 10:11, 28 June 2018 (UTC)
• So? Just because one example has only been used once in 90 days (it was used 11 times last year, for comparison) doesn't mean that entire class is worthless. Should we delete all redirects from misspellings because Ode of Rememberance has only been viewed once since the start of May? Thryduulf (talk) 11:36, 28 June 2018 (UTC)
• Thryduulf not at all - that's just confirmation bias, equivalent to WP:OTHERSTUFF. 10:23, 28 June 2018 (UTC)
• The basic top-level categories contain 75,015 set index articles, 69,014 surname articles, 13,981 given name articles and 90,399 list articles. Other pages will be affected too. If 17,712 8,030 have (disambiguation) redirects, that's 7% 3% of them, which I wouldn't describe as "widespread acceptance". Those counts also highlight that we'd need to create at least 250,000 new pages. To use the (disambiguation) suffix consistently, we'd also need to edit all incoming wikilinks to those 250,000+ pages. (Updated to limit (disambiguation) count to main namespace.) Certes (talk) 10:00, 28 June 2018 (UTC)
• There's also many dabs missing "..(disambiguation)" redirects. How many missing dab redirects do we have? 20%? That would indicate this isn't some urgent, crucial, widely used and supported navigation path that needs extending to SIAs as it's not fixed for dabs even - I create missing ones all the time and I assume nobody noticed before or after! 10:23, 28 June 2018 (UTC)
• That logic doesn't track. The subway doesn't go to as many places as the streets, and the former is only very slowly being expanded despite a need for it to expand. That doesn't mean we should stop road maintenance (or eliminate the roads!) to quintuple our subway tunneling. 10:56, 28 June 2018 (UTC)
• To use that analogy, what's the point of putting road signs for subways?! Will that assist or confuse by conflation? My point being I see little evidence of demand, which that analogy doesn't address. 13:30, 28 June 2018 (UTC)
• A crucial difference is that we deprecate accidental links to disambiguation pages: over a million have been fixed, and the remaining 5,000 are actively being worked on. Dab pages with no (disambiguation) redirect are no problem unless the page has deliberate incoming links. Links to SIAs and name pages are accepted as perfectly proper, so no attempt is being made to divert them via redirects. There is no point in creating such redirects unless someone is happy to amend a lot of wikilinks (probably more than a million) to conform to a new standard. Certes (talk) 11:35, 28 June 2018 (UTC)
• I can't tell whether that is a genuine misunderstanding or a deliberate straw man, but regardless it's irrelevant. This proposal is not to link to SIAs via (disambiguation) redirects, but to allow the redirects to exist for the benefit of those who use them to search. Thryduulf (talk) 11:39, 28 June 2018 (UTC)
• It was a genuine misunderstanding. Thank you for clarifying. Now I understand that the proposal is to create 250,000 orphan pages, so that readers wanting to find a list of ships called HMS Abdiel can find HMS Abdiel (disambiguation). I don't think that's useful, so I still oppose. Certes (talk) 12:11, 28 June 2018 (UTC)
• I genuinely don't understand why you think it is a good thing to require readers to know whether HMS Abdiel is an article about a specific ship, a disambiguation page or a set index before being able to find what they are looking for - i.e. a list of articles about ships with that name because they don't know the title article they want to read but suspect it is not the primary topic. Redirects being orphans is normal, not any sort of problem, and maintaining another 250,000 redirects creates significantly less work for editors than has already been expended in this one discussion. Thryduulf (talk) 14:07, 28 June 2018 (UTC)
• Comment. Disambiguation pages are styled for navigation, not providing information. List articles (including SIAs) are styled as encyclopedic lists, providing information. Articles are not non-articles. Non-articles are not articles. Without that tautological ground to start from, this discussion is inarguable for or against. -- JHunterJ (talk) 12:19, 28 June 2018 (UTC)
• I think we can argue the question of whether certain types of page (which bear some similarity to disambiguation pages in that they also aid navigation) should have (disambiguation) redirects. It is understood that these pages differ from dabs in (a) being articles, (b) not being disambiguation pages and, following recent clarification, (c) that the proposed redirects would be orphans rather than marking deliberate links. Certes (talk) 13:53, 28 June 2018 (UTC)
• Once again, the definition is irrelevant. Redirects being orphans is irrelevant. The difference between disambigation pages and set indexes is, for the purposes of navigation, irrelevant. Thryduulf (talk) 14:12, 28 June 2018 (UTC)
• "The definition is irrelevant" is just wrong. The definitions and differences are extraordinarily relevant, and sufficient to disprove your position. -- JHunterJ (talk) 14:54, 28 June 2018 (UTC)
• Why and how is the definition relevant then? This will not change any definitions, it will not conflate the two, combine the two, remove the distinction between the two, or anything of the sort. Thryduulf (talk) 10:47, 29 June 2018 (UTC)
• The definitions are relevant because they define the things under discussion. Again, this is foundational. You cannot simply dismiss the parts of reality that do not suit you. You would like these definitions and differences to be changed, ignored, or overridden to a particular end, or you disagree with the consensus that what you would like does any of those things; nothing wrong with that. Consensus is against you (either your interpretation of whether this does anything of the sort, or whether any of those sorts of things should be done), though; it happens (and it's certainly happened to me). So we go with the consensus and continue the work of the encyclopedia. -- JHunterJ (talk) 12:44, 29 June 2018 (UTC)
• No, I explicitly do not want the definitions to be changed - as I've repeatedly stated. The definitions of disambiguation pages and set index articles are not the things under discussion. The only thing that is under discussion is whether redirects ending in (disambiguation) should be allowed to point to set index articles when there is not a disambiguation page by that name. Also, there is no consensus in this discussion against the proposal - there is either no consensus or consensus in favour depending how the closing admin regards the strength of the arguments. Thryduulf (talk) 10:31, 6 July 2018 (UTC)
• Certes, in that case, the SIA project should come up with a redirect that would be serve that purpose and not contradict reality. Like "(SIA)" or "(list article with information but also some wikilinks, like any other list article, so use this redirect if you're looking for those wikilinks only for their navigational use)". -- JHunterJ (talk) 14:54, 28 June 2018 (UTC)
This sounds like a seed for a possible compromise. If other editors found utility in redirects such as Africa (list of ships) to HMS Africa (or something similar), I would not oppose such redirects. Certainly, that is less surprising. —hike395 (talk) 15:19, 28 June 2018 (UTC)
I agree with JHunterJ. So is this a sort of "poor man's short description", along the same lines as Venus (planet)Venus for the benefit of readers who might have thought that the article was about the goddess? Certes (talk) 19:04, 28 June 2018 (UTC)
Adding "(SIA)" redirects is fine, but it will not solve the problem of people being required to know in advance whether the page they are looking for is a disambiguation page or an SIA. The only way to do that is to have a single string that users can search on that leads to every page that serves as a list of articles with similar titles. Thryduulf (talk) 10:50, 29 June 2018 (UTC)
That string already exists, and is the blank string. The exception is when it leads to a primary topic such as HMS Victory, but that convention helps far more readers than it hinders. Certes (talk) 11:12, 29 June 2018 (UTC)
Once again you've missed the entire point. The point is that people are looking for an article that is not the primary topic. For example if I'm looking for the ship called HMS Victory that was built a Deptford but don't know the title of that article, I would search for HMS Victory (disambiguation) because I know that the ship preserved at Portsmouth is the primary topic and not the one I want to read. That title is a redirect to a set index article at List of ships named HMS Victory, this page is exactly the content I was looking for and so far from ASTONISHing me, the redirect was exactly what I wanted. There is no evidence that any of the 52 other people who have used the redirect this year found anything other than what they were looking for either. Thryduulf (talk) 14:31, 29 June 2018 (UTC)
If you're searching for info about the HMS Victory built at Deptford you can search for "Hms victory deptford". DexDor (talk) 16:40, 6 July 2018 (UTC)
• (ec) Oppose. The purported "usefulness" of these redirects is akin to developers who utilize unsupported features. Yes, they might find them useful and they might actually work sometimes, but there should be no expectation that they can be relied upon consistently. There is a difference between disambiguation pages and set index articles although some editors confuse them (and to be perfectly honest, many SIAs should be converted to disambiguation pages, but that's another discussion). The only supported use of such "(disambiguation)" redirects is to mark intentional links to disambiguation pages. There were long discussions to get the practice started and to get it accepted. And even so editors need some hand-holding to understand. Allowing occasional and inconsistent redirects to non-disambiguation pages only contributes further to the confusion. olderwiser 12:33, 28 June 2018 (UTC)
Yup, agree. Proposing to "support" a search hack, let alone extend it needs careful thought - what is the cost/benefit. Where's any of that here? 13:50, 28 June 2018 (UTC)
What is the cost? Essentially zero. What is the benefit? Readers find the articles they want to read without having to navigate via the search engine or articles they don't want to read. Thryduulf (talk) 14:11, 28 June 2018 (UTC)
The cost is not zero: the tens of thousands of potential redirects would need maintenance when their targets were moved, deleted or repurposed. The benefit is only to "disambiguation-aware" users who are looking for a list of articles and who navigate directly to a (disambiguation) page title without knowing if that page title exists or not. See my possible mitigation below. Shhhnotsoloud (talk) 09:12, 29 June 2018 (UTC)
If pages are moved then bots update redirect targets as now - Additional cost: Zero.
If pages are re-purposed from a dismabig to a set index currently then (disambiguation) redirects need to be created or deleted, in future they will not be - Additional cost: Non-trivial negative (i.e. it will require less work than now)
If pages converted from a set index to an article then it is likely that a set index or disambiguation will still exist at a different title and just need to be retargetted - additional cost: tiny
If pages are deleted without replacement then the redirect will just be deleted under G8 exactly as they are for disambiguation pages now - additional cost: trivial
If redirects are discovered pointing to SIA articles then currently some users feel the need to nominate them for deletion, in future they will have to do exactly nothing - additional cost: Significant negative.
So in summary, having these redirects will on balance have less cost than the current situation, especially as the changes that add small costs are the least frequent. Thryduulf (talk) 10:38, 29 June 2018 (UTC)
Thryduulf, a fact: the bots haven't created redirects for all dabs yet. Why? I don't know, but it would take effort to see why/fix that. I don't estimate your answer immediately above as being cost free. The details of the benefits aren't clear either (to me). 19:43, 29 June 2018 (UTC)
• Question: Dab and an SIA proponents of having " (disambiguation)" target more than dabs, please detail your proposal for redirects for the common situation when there's both a dab and an SIA. There's only one title with "ambigterm (disambiguation)", so it can't target both. I believe the majority of SIAs are (surname/given) names, this is very common (anyone know the % ?). If there's no solution, then there's not even a complete proposal to cover common SIA. For example 1. WP:FURTHERDAB: Laing (surname) and Laing (disambiguation) (no primary topic), but also 2. when the primary topic is the SIA (which does also happen) and 3. when the primary topic not the SIA. 14:42, 28 June 2018 (UTC)
This was already addressed above. If there's a real DAB page, then of course "Foo (disambiguation)" would go there. And it's already standard practice for SIAs and anthroponomy lists to have entries in a DAB page. 20:08, 28 June 2018 (UTC)
It's acceptable to include a short list of disambiguation-styled entries for name-holding partial title matches on a disambiguation page, after all of the entries for the appropriate topics, until an anthroponymy list article is created. It is not acceptable to include such lists when the anthroponymy article exists. It's acceptable (and expected) that disambiguation pages list all topics (appropriately formatted for navigation) for the ambiguous title, whether those topics are also included on one or more SIAs, other lists, other articles, or anywhere else (where they'd be for encyclopedic information). If there's a dab page (the only dab pages are real dab pages), then "Foo (disambiguation)" would go there. If there's no dab page, the "Foo (disambiguation)" goes nowhere, since there's nowhere (or no real where) to go. But you're right, all this is covered above. -- JHunterJ (talk) 20:30, 28 June 2018 (UTC)
I see there's no reply to the three common SIA/dab scenarios above, so Thryduulf & SMcCandlish (please point to where you detailed how 1,2,3 works?) if there's no solution for the stated goal of Yes, always for set index pages - it is completely unworkable! If there's no proposal that describes how this is possible from the proponents, then it appears impossible even for the proponents, and is dead in the water. 13:09, 29 June 2018 (UTC)
Except that has been addressed, multiple times. 1) If there's already a DAB page, then "Foo (disambiguation)" would obviously go there; "Foo (disambiguation)" would mention "Foo (surname)" if it existed. Your premise is that SIAs are articles (that part is true but meaningless; the off-kilter half of your premise is that the sky will fall if a "Foo (disambiguation)" page points to one because its list serves the same purpose – there's zero evidence of any problem, and obvious evidence that it's helpful for readers, since they are in fact using and creating such redirects).
2) If an SIA is the primary topic, then it is not different from any other article that's a primary topic. If there are things with the same name that also have other articles (if there's not, then "primary topic" doesn't have any meaning in the context), then "Foo (disambiguation)" would not be a redirect at all but an actual disambiguation page, just like normal.
3) Your last scenario isn't distinguishable; it again would result in an actual DAB page at "Foo (disambiguation)" because the "Foo (whatever)" SIA page isn't the only page to disambiguate. None of this is new or even a question, it's standard operating procedure.
Your idea, just because no one pointed out the obvious to you, that an already-widespread actual practice that you don't like is "completely unworkable", "impossible", and "dead in the water" (with a bunch of excessive italics) is obstructionst, reality-denying, "I just don't get it", wikilawyering nonsense that is anti-collaborative and thwarts consensus formation. It's a debate tactic you need to stop whacking people in the face with. See also WP:SATISFY, WP:GASLIGHTING, and WP:RTFM. 13:57, 29 June 2018 (UTC)
SMCCandlish, you are engaging in the very obstructionst, reality-denying, "I just don't get it", wikilawyering nonsense that you're decrying. Along with an assumption of bad faith. Widefox appears to be trying to help you identify what you and Thryduulf are trying to get to, since it is currently contrary to consensus (and the definitions of the articles and nav pages in question). I'd just as soon end it here too, given the consensus for the current reality, but Widefox is putting in the effort to see what else might be done to address the hypothetical issue you and Thryduulf seem to see. -- JHunterJ (talk) 16:48, 29 June 2018 (UTC)
I'm not assuming any bad faith, just being critical of unhelpful behavior, like asking the same thing over and over again after it's already been answered multiple times. That is absolutely not "putting in the effort to see what else might be done to address" the issue or "trying to help [someone] identify what [they] are trying to get to", it's annoying pretense that we don't know and can't explain what we've already very, very clearly explained. 17:55, 29 June 2018 (UTC)
SMcCandlish, if I understand Thryduulf's proposal (please correct me if wrong), it is to create redirects targeting all SIAs. Correct? If not, not all SIAs will have a redirect (as all dabs do, in theory), then this will not be a workable, reliable method for searching! I see no proposal above for the common cases 1.2.3. . If there is none, then this needs to be recognised as completely and utterly unworkable. The burden is on the proponent to convince others of changing consensus, so please go ahead (as the answers to this so far are not unconvincing (to be polite), more of a desire to extend without having thought through the consequences for common cases, I'm afraid to say). My tip: complaining about those that try to tease out the proposal doesn't help you convince them per WP:CLUE. 19:37, 29 June 2018 (UTC)
In the probably vain hope that different formatting will make you hear something you obviously don't want to hear:
1. Laing (surname) and Laing (disambiguation) (no primary topic): The exisitng redirect would not be changed - i.e. it would go to the dismabiguation page at Laing. No existing pages with (disambiguation) in the title will change.
2. Where the SIA is the primary topic but there is also a dismabiguation page: The (disambiguation) redirect would go to the disambiguation page. No existing pages with (disambiguation) in the title will change.
3. Where there is a disambiguation page and an SIA but neither is the primary topic: The disambiguation page will remain at the (disambiguation) title. No existing pages with (disambiguation) in the title will change.
The consequences for common cases have all been thought through, and have been answered many times previous to this, in the FAQ below. Thryduulf (talk) 19:57, 29 June 2018 (UTC)
1. Thryduulf thank you for the answer (maybe I missed it above?) - so the SIA would not get a redirect. So not all SIAs would get redirects, and therefore (my point) that this isn't as you said Yes, always for set index pages. I see your !vote now has a provision ..., allow but do not require for surname pages so that just kicks the problem down the road (away from the most common SIAs!) - if not all SIAs are to have a redirect, then it's not even a simple rule like for dabs (where they're still missing). The maintenance with a rule that depends on several pages/aspects is more, especially when moving articles/dabs/SIAs move. I really don't like complex, and I vehemently disagree this is cost free to create, let alone maintain. Blurring dabs and SIAs is, IMHO, the cause of this, and this proposal exacerbates the problem, rather than being a solution to it. 22:46, 29 June 2018 (UTC)
Where both disambiguation and SIA pages exist the disambiguation page the (disambiguation) title is either the disambiguation page or a redirect to it, and the dab page links to the SIA. This means that anyone looking for an article listed on the disambiguation page has found what they want directly, and anyone who is looking for something only listed on the SIA is given a direct link there without having to know the title of the page in advance - i.e. everybody finds what they are looking for. The "allow but do not require" for surname pages is because not all surname pages are or have lists of articles about people with that name - e.g. Smith (surname), Jones (surname) (although these are not perfect examples as there are separate disambiguation pages that would remain the target of the (disambiguation) redirect - indeed in 2-3 minutes browsing I've yet to find an example of a surname page that doesn't contain a list of people where there isn't also a separate disambiguation page). You still have not provided any explanation (let alone evidence) for how these redirects would blur disambiguation pages and set index articles. Thryduulf (talk) 14:31, 30 June 2018 (UTC)
So in terms of sets of users rather than empirical data, the bounds of user numbers of such a navigation path are (in the absence of any evidence of stats)... for A) a minority of SIAs and B) for a subset of a minority of users (per typical WP:PRIMARYTOPIC more "likely than all others combined", for instance). Agreed? You must concede that A * B is niche of a niche, so the stats must be vanishingly small by those bounds alone, and as presented lacking convincing data. 21:47, 30 June 2018 (UTC)
No, that doesn't make any sense. What you are trying to saying is that because only a small number of people who use this method explicitly comment in favour of this then the correct thing to do is to make things unnecessarily difficult for everybody who uses it just because you don't personally use it and don't like the fact that other people use it - an attitude that is directly harmful to Wikipedia. Thryduulf (talk) 08:39, 1 July 2018 (UTC)
• Possible mitigation. This RfC boils down to do we support this "undocumented feature" and "search hack", or not? and must be resolved to stop frequent re-runs of the argument at RfD. There are a number of arguments against, versus an argument for to support those users looking for a list of articles and who navigate directly to a (disambiguation) page title without knowing if that page title exists or not. If we can settle on No then one compromise could be for such "disambiguation-aware" users to be advised to stop navigating like that by guidance (somewhere) that says "Users wishing to find a list of articles on a particular topic are advised not to navigate directly to titles such as Foo (disambiguation): information about various uses of Foo might be found at a disambiguation page, or list article, or other index article located at the Foo page name, and if not then a hatnote is provided to the alternative location (which might not necessarily be a disambiguation page)." Shhhnotsoloud (talk) 09:12, 29 June 2018 (UTC)
• How do you propose to advise people to change their behaviour when it is almost certainly something they have just discovered for themselves works, or have been told by others works? What benefit is there to changing the practice from: "You can find what you want at Foo, Foo (disambiguation)" to "What you want might be at Foo, List of Foo, Foo (disambiguation), Foo (SIA), Index of Foo or some other title"? How is that in any way shape of form better for anybody? Thryduulf (talk) 10:42, 29 June 2018 (UTC)
• Yeah, Shhhnotsoloud's idea is utterly impractical. Guidelines a written for editors, not readers. Our readers usually never see any of them, nor even know where to look. Even most of our "Help:" namespace pages see very, very little use relative to the size of the readerbase. 12:42, 29 June 2018 (UTC)
• No - mainly because this would further muddle the distinction between dabs and SIAs for little/no benefit. Most Wikipedia readers probably have little understanding of dab pages and SIAs, but they do understand the basics of searching for things on the internet (the more info you put into a search box the more likely it is that the thing you're looking for will be at the top of the results). So, for example, a reader interested in Portland (UK) who doesn't want to risk a slow download of the article about Portland (USA) would type "Portland uk", "Portland dorset" or similar into the searchbox - not "Portland (disambiguation)" which is more characters to type, unintuitive and guarantees that they'll have to go through another step before reaching the article they want. DexDor (talk) 12:52, 1 July 2018 (UTC)
• @DexDor: The problem with that theory is that it doesn't match the evidence of what we see in practice. Sure some people, maybe most, go via the search engine (and these people will be entirely unaffected by this proposal). If people didn't use this method then nobody would have created these redirects and they wouldn't get any page views. The difference between going via search results and going via a disambiguation page or set index is not one of the number of pages that you need to view, but of what pages you need to view - either search results that may or may not contain your query on the first page or a list of articles that almost certainly will contain the article you want on the first page. Yes, only people who are familiar with Wikipedia's naming of disambiguation pages will use this method, but very many people are familiar with that - far more than are familiar with the difference between disambiguation pages and set indexes. The question being asked by this RfC boils down to: Some people use this method, do we want to go out of our way to hinder them for no benefit to anybody? Thryduulf (talk) 10:40, 6 July 2018 (UTC)
• Yes. A string like `(disambiguation)` might have been only an obscure element of out technical infrastructure 15 years ago, but now it's a generally known term: pretty much everyone who's ever used wikipedia will know of the existence of disambiguation pages, and it's likely that many people would have figured out that if they started typing some term in the search box and one of the drop-down suggestions ends in `(disambiguation)` then they could click on it and be taken straight to the disambiguation page bypassing any primary topics. For example, a user might be looking for the town named "London" which they know is somewhere in the Americas, but they don't know whether it's in the US or Canada or somewhere else, and they know they're on wikipedia so making google-type queries like "London America" won't return anything meaningful, so of course they would go straight for London (disambiguation). This is not some search "hack", but a reasonable and obvious way to navigate the encyclopedia, which becomes especially relevant for mobile users for whom the loading of a huge page they don't want (like London) is costly.
The only question is whether this avenue should be restricted only to "actual" disambiguation pages, or whether it should extend to set index articles (SIA) or name pages. First off, the distinction between DAB and SIA articles is virtually unknown outside the dedicated core of members of the dab wikiproject, and it would be really surprising if our readers knew (or cared) about it. And really, SIAs (and to a large extent name articles) are lists of things sharing the same name: this is not encyclopedic by itself and its only function is to disambiguate between those things. These lists are functionally equivalent to dab pages. In the absence of a "proper" dab page, a user following a redirect like X (disambiguation) who lands on a page that lists things named X would have found exactly what they were looking for.
A case for deprecating such redirects can be made only if it turns out that either they aren't used at all (the evidence presented so far suggests otherwise), or that they don't get readers where they want (so far, that's not a reasonable assumption). And really, if the issue is that the targets aren't technically speaking disambiguation pages, then the redirects can be tagged with {{R from incorrect disambiguation}}; again, redirects are there to help readers and they don't need to be "correct", there are tens of thousands of perfectly good redirects in Category:Redirects from incorrect names. – Uanfala (talk) 11:50, 6 July 2018 (UTC)
• Meh Very weak yes. IMHO, both sides of this discussion have vastly overstated their positions. On one hand, it seems to me that the benefit of a "(disambiguation)" redirect to a set index article is fairly minuscule. Although some users might indeed search for the term "disambiguation" explicitly, those are likely to be a relatively small set of relatively sophisticated Wiki readers, nearly all active editors. Furthermore, the vast majority of the time, if the redirect "Random title (disambiguation)" turns out not to exist, then the article at "Random title" will provide this sophisticated reader with the guidance they were looking for. On the other hand, redirects are cheap, and no one is ever going to see these unless they have explicitly typed the word "disambiguation" into the search bar or some external search engine. So I don't think these sophisticated readers are going to be harmed in any material way if their search takes them to a SIA or list article instead of a disambiguation page, as long as it helps them find the topic they were trying to find. In fact, in writing out this comment, I've changed my mind from "couldn't care less" to a very weak support, since the proposal seems to do no harm to anyone even if it does have very little benefit. However, I only support the proposal insofar as it seeks to permit these redirects, not to require them. --R'n'B (call me Russ) 21:47, 11 July 2018 (UTC)
A couple of further points: (1) If this is accepted as a standard practice, it would be helpful to have a tracking category similar to Category:Redirects to disambiguation pages for them. Maybe Category:Redirects to set indices would work. (2) As far as I can tell from this discussion, there seems to be no disagreement that a "(disambiguation)" redirect to an article is unacceptable, and that deletion would be uncontroversial, if the target article is not a set index, a list, or something that similarly assists a reader in finding other, similarly-titled topics. --R'n'B (call me Russ) 21:49, 11 July 2018 (UTC)
I'm not sure if you're aware of how many pages could be included by that criteria. e.g. WP:TWODABS failures (e.g. no dab but two articles with hatnotes) or any page with a hatnote to another article - reductio ad absurdum a lot! I'd rather hope we'd go in the other direction - towards eliminating the dab redirects (which are a supported hack) in software / improving search. 18:05, 31 August 2018 (UTC)
• Strong yes, per the thorough arguments of Thryduulf and others. We have all sorts of redirects from "wrong" titles (misspellings, former names, etc.). Plenty of readers are aware of pages ending in "(disambiguation)" and may type that into a search bar; almost no non-editors are aware of the DAB/SIA distinction, and it's not our job to teach them about it just so they can find the article they want. The biggest complaint casual readers have about Wikipedia is its idiosyncrasy – the "insider" stuff you're expected to know if you want to make full use of the encyclopedia. Here's an opportunity to smooth a small bit of that. If a redirect has plausible value, leave it! Nothing about these redirects threatens the maintenance of the DAB/SIA distinction. —swpbT go beyond 15:49, 12 July 2018 (UTC)
• No. Eligible for WP:CSD#G8; these fit the definition of being dependent upon nonexistent pages. I do not see evidence that users use the search bar in this way, but if users are familiar enough with the interface to know that they might want to search for disambiguation pages, they should also be competent enough to know about the intitle search function. Dekimasuよ! 18:36, 15 July 2018 (UTC)
• 1) G8 explicitly does not say that: it spells out exactly the types of redirects it applies to, and these aren't among them. 2) Knowing about disambiguation implies knowing about intitle searching? That's an unsupportable and IMO implausible leap. Casual readers see "disambiguation" constantly; they never see "intitle" unless they click on "All pages with a title containing" on a dab, and then pay attention to the filled-in search bar, or they go exploring Special pages. All the non-pedians in my life know about dab pages; I'd wager 50 times as many people know about dab pages as know about intitle searching. —swpbT go beyond 12:53, 16 July 2018 (UTC)
• When a title with "(disambiguation)" redirects to something that's not a dab page, it is included in the listed examples ("such as non-existent targets... and bad titles"). Further, even were that not the case, G8 begins "Examples of this criterion include." It is not an exhaustive list of "pages dependent on a non-existent or deleted page." Dekimasuよ! 16:08, 16 July 2018 (UTC)
• "Non existent targets" means red links and so is not relevant in the slightest. There is no consensus that these redirects are "Bad titles" so speedy deletion cannot apply as that is only permitted for pages with "no practical chance of surviving discussion.". WP:CSD also notes: "[The criteria] cover only the cases specified in the rules here." (emphasis mine) and "Administrators should take care not to speedy delete pages or media except in the most obvious cases.". Thryduulf (talk) 00:40, 17 July 2018 (UTC)
Yeah, Dekimasu is just making stuff mean whatever they want it to mean. "redirecting to something that's not a dab page" is not redirecting to a non-existent target but to a existent target, by definition. It's also not a bad-title case; we get one of those when we try to title something and the system doesn't let us, with a big Bad title error (e.g. try creating an article at `[[Foo}{bar]]`). 09:52, 17 July 2018 (UTC)
• There's nothing made up about "redirecting to something that's not a dab page" when the guidelines for disambiguation and set index pages are clear that one is and one is not. That some editors want to propagate confusion between them it's another matter. olderwiser 12:17, 17 July 2018 (UTC)
• Have you actually read any of this discussion? It's been explained, repeatedly and at length, why there is no actual confusion. The entire point of this RFC is that the guideline about (disambiguation) redirects does not mesh with current practice - and even if it did a guideline does not and cannot override a policy page like CSD. Thryduulf (talk) 13:27, 17 July 2018 (UTC)
And "redirecting to something that's not a dab page" is nothing remotely like "redirecting to a non-existent target". There is no escaping that fact. "some editors want to propagate confusion between them" is just a distortion; what those "some editors" want to do is help readers find content. It doesn't confuse disambiguation pages with SIA or anthroponymy pages, it uses a redirect to get people to what they're looking for, which is why we have redirects. Bkonrad's argument isn't distinguishable from claiming that the Lord Mayor of Bristol redirect to List of mayors Bristol, a SAL page, must be deleted because it's "propagating confusion between" lists and non-lists. WP just doesn't work that way. The internal editorial classification and subclassification of page types does not wag the dog of getting readers to content. 13:47, 17 July 2018 (UTC)
That's it in a nutshell: "Dekimasu is just making stuff mean whatever they want it to mean". There is zero wiggle room in the meanings of "non-existent target" and "bad title". To engage further on that point is to be pulled deeper into a rabbit hole of bad faith. —swpbT go beyond 15:26, 17 July 2018 (UTC)
I wouldn't ascribe it to bad faith, more like single-mindedness or territorialism or WP:WINNING or forest-for-the-trees or one of our other habitual human foibles. I don't think anyone's trying to do wrong here, they just have radically different priorities (some of which should be reconsidered, given the reader-facing nature of this project). 16:20, 17 July 2018 (UTC)
This is not just "different priorities". This is doubling down on an error, by an admin, in an attempt to save face. That's bad faith. Wouldn't the project be better if that kind of behavior had a meaningful cost? —swpbT go beyond 19:34, 17 July 2018 (UTC)
I strongly agree it's doubling down on an error, but I think anyone from an anthropology background would agree with the following corollary to an old canard: Never attribute to malice or stupidity that which can be adequately explained by everyday hominid stubbornness and self-interest. >;-) No one likes to feel criticized or shown wrong, so they tend to rationalize and handwave. Admins aren't magically immune to it, though people in a position of responsibility and trust need to catch themselves and moderate this tendency, especially after they've been repeatedly called on it (including by another person of the same community-vetted trust level). 00:48, 18 July 2018 (UTC)
This page is not on my watchlist, so I didn't realize my comment created heat. If it's helpful, I am happy to concede that this is not what is meant by "bad titles", and a look through my deletion log did not immediately reveal any instance in which I have ever applied G8 (or the old R1) to this sort of redirect. Perhaps I should have just referred to G6 in my original comment, as was my original inclination. However, I reasoned that if it were self-evident that G6 applied, there would be no reason for the RfC to be taking place. Thus I substituted a reading of G8, a criterion I rarely apply except to talk pages of deleted pages, for simply expressing an opinion that this might reasonably be considered "non-controversial cleanup". I doubt there is any use to my arguing further over whether these disambiguation pages are "nonexistent" as "specified in the rules". I am not much interested in saving face and I don't think I've had someone suggest I was acting in bad faith in my 12 years here, so it's bemusing to have that happen in a discussion I'm not much invested in. Dekimasuよ! 11:05, 21 July 2018 (UTC)
To Dekimasu: You say you are "happy to concede": please show your good faith by striking your errors above, so anyone reading this thread will immediately know not to rely on them. I would also think, having your arguments so thoroughly debunked, that you might want to consider re-evaluating your "no" vote (since of course you have no personal investment here), but that's up to you. —swpbT go beyond 12:50, 27 July 2018 (UTC)
• Yes: Redirects like these are likely to help the reader to find a page which will help them get to their sought information sooner rather than later. They do no harm, and I suggest that readers will not be confused as they are unlikely to spot the difference between a dab page, a name page, and a SIA, as long as it offers them the information they need. The redirect will also alert an editor thinking of creating a new dab page, by showing them that there is already a non-dab non-article page which needs to be taken into consideration. PamD 10:05, 16 July 2018 (UTC)
"non-dab non-article page"? That's not what these are. These are non-dab article set index articles. -- JHunterJ (talk) 12:16, 16 July 2018 (UTC)
That's obviously a true correction of a some poor wording. Yet it strangely has no effect at all on the actual argument PamD presented. 14:57, 16 July 2018 (UTC)
User:PamD There's a couple of gut assumptions there 1. likely help 2. no harm. Both assumptions have been explored now. Logically, if true, wouldn't all lists and many other types of pages benefit from such a free improvement? reductio ad absurdum all pages with hatnotes etc, essentially almost all pages! (I've put a question below about the number of SIAs this fails for, do you know if the majority of name SIAs have dabs?) 09:19, 31 August 2018 (UTC)
• Slightly late to the discussion, but I was pinged earlier. In short, yes because among other reasons:
1. Wikipedia's DAB pages have existed long enough that many of our casual readers are aware that they disambiguate between topics which can be referred to by the same name (e.g. [1], [2], [3], [4], [5]).
2. SIAs also do this, but only include topics belonging to the same class. Almost no readers and only a small minority of Wikipedia users, usually those who work on DABs, are aware of the technical differences between DABs and SIAs.
3. Users sometimes do want see only a list of non-primary topics for X. If they are aware of DAB pages, specifically searching for them is reasonable, especially when the method of disambiguation can be obscure (e.g. years of battles/treaties, ship's hull numbers, people's birth years and professions).
4. An overwhelming supermajority of set indices (@ Category:Set indices) are functionally DABs, with minimal formatting or content differences. Some exceptions that are actually more developed as set index articles do exist (e.g. mountains, car models) but are the minority. So if readers are looking for a DAB about X, they will almost never be disappointed or surprised to find a set index on X instead.
5. Wikipedia should aim for consistency, so there should be one universal way to navigate to pages that allow for quick differentiation between very similarly named topics.
6. Strictly speaking, "X (disambiguation)" will get you to a page where topics named X are disambiguated if those topics belong to more than one class, no matter how few or how obscure those other topics are. However, "X (disambiguation)" will not get you to the same page, if all X topics belong to the same class, even if there is a very large number of X topics, many of which are quite prominent. This is inconsistent and arbitrary.
7. Wikipedia is meant to serve readers who not be hindered merely to strictly adhere to guidelines.
• So if we can agree that some readers will want to specifically search for DAB pages and there's no real, functional difference between most SIAs and DABs, then these redirects should be kept, and actively created (perhaps by a bot). This is without considering factors such as widespread behind the scenes categorization of SIAs as DABs and vice versa (e.g. click around in Category:Set indices on storms), not forcing people to waste data loading long primary topic articles they 100% do not want, identifying bad links to SIAs that are nearly identical to DABs (e.g. via Dab Solver), preventing people from accidentally creating duplicate DAB pages where a SIA exists (e.g. via a redlink from an edit preview), and avoiding busy work deleting "X (disambiguation)" redirects when they are technically no longer DABS. ---- Patar knight - chat/contributions 08:12, 27 July 2018 (UTC)
• Yes, per persuasive recent comments of User:Uanfala and User:Swpb, and general arguments of Thyrrdulf. These can indeed be labelled {{R to set index article in absence of disambiguation page}} or whatever, and automatically tracked in a category, for those who want to keep analyzing these. Also Swpb's point is that we have zillions of redirects from misspellings and the like... these are functional (they help many readers) and not harmful in any way. --Doncram (talk) 00:24, 28 August 2018 (UTC)
• Question - how many SIAs does this fail for? What's not obvious from this discussion is that this proposal will never work for many (most?) SIAs as there is already a dab, so a redirect will be impossible (e.g. many name SIAs). Does anyone have the numbers of SIAs with matching dabs? I do sense a desire to have SIAs be treated in some sort of a consistent way with dabs for the benefit of readers. Would the simplest way to get consistency for readers be to fix tighten the definition of SIAs to be proper lists (inclusion criteria, references) and convert the rest to dabs? Can't get to the moon by climbing a tree. SIAs are the only pages I know of that evade WP:V. This proposal layers a hack to enable a search hack without addressing the underlying inconsistency. Fixing the root cause would be consistent. 09:19, 31 August 2018 (UTC)
• "How many SIAs does this fail for?" - Zero. Any SIA with a matching disambiguation page should be listed on the disambiguation page (entirely independently of this proposal), so searching for "(disambiguation)" will land on a page that either has the content the searcher is looking for or directly links to it. Whether SIAs should exist is spectacularly further outside the scope of this discussion than the usual FUD that is being thrown, well done. Thryduulf (talk) 10:17, 1 September 2018 (UTC)
Thryduulf, I'm actually asking if anyone knows the number of SIAs that cannot have such a redirect as they have a dab. If you don't know (I don't), then your comment isn't adding light as zero is the wrong number. We cannot bot generate them all either (unlike dabs), as the creation rule would be complicated with many SIAs e.g. List of people with surname Smith are titled so far from their dab Smith that it isn't obvious that the existing redirect Smith (disambiguation) excludes creation of a redirect 14:32, 1 September 2018 (UTC)

There is a lot of repetition and misunderstanding above, this is an attempt to clarify what is actually being proposed:

What will be created?
Redirects ending in (disambiguation) that point to set index pages, but only where no disambiguation page for this title already exists.
What will happen to existing pages that end in (disambiguation)?
Nothing.
What will happen if there is a disambiguation page and a set index page for the same title?
The title with (disambiguation) will either be the disambiguation page or a redirect to it, exactly as it currently is.
Will we have to change links to set index articles to go via these links?
No. No changes to any links are required.
What changes will be made to disambiguation pages?
None. There will be no changes to disambiguation pages as a result of this proposal.
What changes will be made to set index articles?
None. There will be no changes to disambiguation pages as a result of this proposal.
How will the definitions of disambiguation pages and/or set index articles change?
They won't. No changes to any definitions are being proposed because no changes are needed.
Will this conflate disambiguation pages and set index articles?
No. No changes will be made to either sort or page.
Will this mean more work for editors who maintain disambiguation pages and/or set index articles?
No - overall it will mean less work as when disambiguation pages become set index articles or vice versa then no changes will need to be made to redirects.
Will this mean more work when creating disambiguation pages?
No. There will be no changes to this at all.
Will this mean more work when creating set index articles?
Only if you want to - you will now be allowed to create a redirect to it ending in (disambiguation), but you will not be required to do so as it can be created by another editor and/or a bot.
Will this mean more work when deleting disambiguation pages?
No. If a disambiguation page is being deleted to make way for a set index article at the same title then there will be less work as the redirect can remain. If there is a set index article at a different title, then the redirect will need to be retargeted (about the same amount of work as deleting it). In all other circumstances there will be no change.
Will this mean more work when deleting set index articles?
Yes, but only a small amount and not in all circumstances. If the set index article is being deleted to make way for a disambiguation page at the same title then there will be less work as the (disambiguation) redirect will not need to be created separately. In other cases there will be one additional redirect to speedy deletion under criterion WP:CSD#G8.
Will this mean more work when moving disambiguation pages?
Will this mean more work when moving set index articles?
A small amount in some circumstances, none in other circumstances. If there is no disambiguation page for the title involved and the move is not to make way for a new disambiguation page at the old title then one redirect will need to be retargetted, this will be done by a bot if the old title will now redirect to the new one. In other circumstances then there will be no change.

Thryduulf (talk) 14:23, 29 June 2018 (UTC)

• Oppose. There is a lot of repetition and misunderstanding on your part above too. The clarify what is actually being counter-proposed: I suggest coming up with a (SIA) or similar qualifier for this purpose, if one is needed for the hypothetical problem perceived, rather than use one that indicates the target is something it isn't. -- JHunterJ (talk) 16:52, 29 June 2018 (UTC)
Applicable reasons from the reasons for deletion on WP:RFD: #2: The redirect might cause confusion. #5 The redirect makes no sense, such as redirecting Apple to Orange. -- JHunterJ (talk) 16:54, 29 June 2018 (UTC)
Note to closing admin: The bolded oppose immediately above duplicates JHunterJ's bolded "No" !vote in the main section above. Thryduulf (talk) 19:47, 29 June 2018 (UTC)
All repetition on my part is because the same questions get asked over and over and over again and answer get ignored - as again here. (SIA) will not help at all because the entire point is that it would require people to know what sort of page it is before visiting it - this is not predictable and can change. There is no evidence presented anywhere by anybody (despite repeated requests) that these redirects actually mislead anyone or cause any confusion - rather there is evidence that they are useful: The existing redirects are frequently used (over 50 times a year in some cases), get created by many different people and every time they are nominated at RfD people state that they are useful to them. It has also been repeatedly explained above in multiple ways why this proposal does make sense - these redirects are used by people looking for a list of articles related to their search term from which they can navigate to the article they want to read, something that is the precise purpose of both disambiguation pages and set index articles. Also note I have struck your bolded oppose for two reasons: 1. this set of questions and answers isn't something you can support or oppose. 2: You have already expressed a bolded opinion above. Thryduulf (talk) 17:46, 29 June 2018 (UTC)
This is obviously a waste of time in this venue. The issue should be reformulated (and keep that FAQ with it, perhaps in a collapse box), and posed to village pump where the audience is broader. 17:58, 29 June 2018 (UTC)
Your answers are unconvincing, that's not the same as being ignored. SIAs do not have the exact purpose of disambiguation pages. If they did, they would be disambiguation pages and formatted as such, and we wouldn't be having this discussion. There is no evidence that those inaccurate redirects are more useful than the accurate (SIA) ones (if they are useful to the readership at all). Kindly do not alter my talk page comments again; I do indeed oppose what is actually being proposed. If you would like, you are welcome to strike your own comments, since you have already expressed them above too. -- JHunterJ (talk) 17:59, 29 June 2018 (UTC)
For at least the 10th time, because you are repeatedly refusing to listen to the answers, the difference between SIAs and dab pages is not relevant to the way people use these redirects. Any differences for other purposes is irrelevant - as has been explained in detail multiple times already. If you do not understand why (SIA) redirects will not solve the issue then you have completely failed to understand the entire issue and your opposition should be ignored. I'm inclined to agree with SMcCandlish that repeatedly talking to brick walls here is getting to be a waste of time, and moving to the village pump where people will actually take the time to understand what is actually being proposed (rather than throwing up straw men) would be a good move. Thryduulf (talk) 19:47, 29 June 2018 (UTC)
Your failure to convince me doesn't mean I haven't understood it. You would like to declare that (SIA) will not solve the issue. That you repeat yourself so often can just as easily be used to claim that you have completely failed to understand the problem with your proposal, despite the repeated explanations of it that you refuse to hear. But that's not it. There's a proposal here, and it has no consensus, and rather than work with that, you and SMcCandlish would rather paint everyone else as bad faith using whatever alphabet soup of WP shortcuts are handy. We disagree. -- JHunterJ (talk) 19:53, 29 June 2018 (UTC)
Quote either of us making an accusatoin of bad faith. And if you'd prefer that names of policies and guidelines be spelled out for you in long form, and their applicability spelled out to you as if you were a noob, that could be done, but I think everyone would hate it, including you. 01:13, 3 July 2018 (UTC)
Once again entire reason that (SIA) will not work because the entire point of the proposal is that there should be one string that enables users to find what they are looking for (a list of articles related to their search term) whether that list is a disambiguation page or a set index article without needing to know in advance what sort of page it is. If disambiguation pages are found via (disambiguation) and set index articles via (SIA) then one must know in advance whether the page you want is a disambiguation page or a set index article. This is extremely user unfriendly. Thryduulf (talk) 20:01, 29 June 2018 (UTC)
If someone is looking for foo, then the string to use would be foo. That is about as user friendly as one can get. -- Tavix (talk) 21:35, 29 June 2018 (UTC)
Yup Tavix, my understanding is that this is asking to support a navigation path for those that want to go against the flow of navigation per WP:PRIMARYTOPIC. Similar to adding signs for the wrong way in a one-way street, I, for one, do not think it sensible to put limited resources into discussing signage for the counter-flow. 23:13, 29 June 2018 (UTC)
Yes, that's exactly what I said already - a navigation path not per WP:PRIMARYTOPIC. ie not 1. majority: -> primary topic and not 2. minority: -> primary topic -> dab -> article), but 3. not documented (subset) of minority: -> dab -> article, so this is a subset of a minority of users. The assertion that this is a big issue is just that, by definition of primary topic this is a subset of a minority of users, with only anecdotal evidence of demand presented. WP:IDHT describes exactly this situation. 20:32, 30 June 2018 (UTC)
That is easily resolved by retargeting HMS Victory (disambiguation) to the relevant disambiguation page. I have done just that. -- Tavix (talk) 15:27, 30 June 2018 (UTC)
Agree Tavix, HMS Victory (disambiguation) is now a routine WP:INCDAB per consensus - much better than the previous invalid target of the SIA. Great example of how the common case of an SIA and dab has no need at all for incorrectly targeted redirects. If I've understood correctly, we probably all agree on that case. Thryduulf, I think the assertion that editors who work on disambiguation are trying to make navigation harder is bad faith, I certainly see no evidence of that, and as someone who's created 100x more redirects than deleted, you should really strike that. 10:33, 2 July 2018 (UTC)
It's much more likely that a reader (who has no interest in dabs/SIAs) would put something like "Hms victory 17th century" in the search box and then click on the HMS Victory (1620) result. DexDor (talk) 08:40, 1 July 2018 (UTC)
• Comment I note that what was formerly routine CSD G6 (or G8) deletion of these redirects that fail to target dab pages, has more recently been made controversial, so therefore ineligible for CSD. I assume, logically, that the result of this RfC would be binding in deciding yes/no if they can return to uncontroversial CSD G6 (routine redirects with no substantial history). 23:03, 29 June 2018 (UTC)
• (ping Xezbeth re CSD comment) 23:27, 29 June 2018 (UTC)
• Spelled out consequences for the decision here: the recent against old consensus discussions at RfD (one is linked above) that have pushed this hack have been preventing previously uncontroversial routine redirect deletions. The old consensus is clear, and the result here will either confirm or change that consensus. The limited consensus at those RfCs should be overridden as WP:LOCALCONSENSUS with this. I repeat, those pushing a hack should not WP:IDHT (which is the tone this has descended to), and get in the way of the broader consensus. 10:27, 30 June 2018 (UTC)
• Yes and no. The discussions at the RfDs have shown that there is no current consensus for or against these redirects. Whether there ever was a consensus against them (outside the local consensus of the disambiguation project) is arguable, but the status quo ante of this discussion is no consensus and that will remain unless this RfC comes to a consensus (which is looking likely given the repeated IDHT from those opposed). Thryduulf (talk) 14:43, 30 June 2018 (UTC)
• Thryduulf, there are other ways to reduce the page size/time to assist navigation generally that don't need a change to the database, and may have more general scope and use cases. For example:
• 1. Mobile client already has the option to save pages for offline, so users need not download the primary topic a second time.
• 1.1 Browsers can enable more aggressive cache revalidation generally to reduce/eliminate the need to download a primary topic that is a client cache hit (Chrome about:flags has options for that, which I use generally without issues, but haven't specifically tested this on WP server setup)
• 2.1 Specific navigation version of that
• 3. Search

Maybe some have been proposed before, I don't know. 10:10, 2 July 2018 (UTC)

Extended content
Moved to User talk:Widefox#WP:AC/DS awareness notice. 01:21, 5 July 2018 (UTC)
• Note to all participants here A WP:AC/DS awareness notice has been posted on my talk User talk:Widefox#WP:AC/DS awareness notice by User:SMcCandlish regarding this, so that applies to everyone here equally. Comments on the suitability and neutrality of that are welcome on my talk (or here). 22:26, 2 July 2018 (UTC)
Except it doesn't apply that way at all. See WP:AC/DS and the Template:Ds/alert documentation; that exact template must be delivered per-individual in user talk – despite the fact that pages like the one we're on now already have DS-related banners atop them. I've repeatedly challenged this at WT:ARBCOM and other places as ridiculous WP:BUREAUCRACY, to no avail. This is why I've opened up the "Wikipedia:Village pump (proposals)#Bot to deliver Template:Ds/alert" proposal today. Every time Ds/alert is used by anyone manually, it just leads to more drama. Consequently, hardly anyone will use the template, and DS is thus not working. 00:37, 3 July 2018 (UTC)
"Except it doesn't apply that way at all." as you are aware of the correct usage, why didn't you post it on everyone's page? What made you chose one editor you disagreed with? I have equally informed all above. Just posting to one editor's page in the knowledge it applies to all editors equally singles out one editor without treating all editors equally. Mind boggling that you do this while saying you don't agree with it. 07:22, 3 July 2018 (UTC)
This is off-topic here. Try User talk:Widefox#WP:AC/DS awareness notice. 01:21, 5 July 2018 (UTC)
• I'll repeat what I said in mid-thread above, since it got rapidly buried there: The way to resolve this is with a more clearly-formulated RfC at WP:VPPOL, our broadest-input venue for this sort of thing. Some participants here calling a WP-wide process like WP:RFD a "local consensus" then denying that the handful of editors who spend any time at all at WT:DAB isn't a local consensus but overrides repeated consensus discussions at RfD, is just not tenable. The fact that RfD discussions a long time ago were in agreement with the WT:DAB regulars but now are not isn't an indication of anything other than that consensus can change. Whether it has is an open question, and it's not going to be settled by another week of people here pretending that their questions and concerns haven't been addressed, and turning the discussion cicular. Just have proper RfC about it, in a place that anyone actually pays attention to. Ping all previous respondents. Easy-peasy. If a broader RfC that's not an echo chamber agrees with the WT:DAB crowd and against all of Thryduulf's arguments and mine (which Thryduulf beat me to and articulated better), I'll happy go along with that. But not with a tiny local consensus telling one of our WP-wide XfD processes that it is the local consensus. That's raw nonsense. 01:38, 5 July 2018 (UTC)
No other editor has stated or implied that this RfC is poorly formulated or in the wrong venue. The RfC, placed by me, asks a straightforward Yes/No question and is on the Talk page of the guidance that will be modified as a result. The RfC has attracted substantive comment from a number of editors and, in my opinion, we need to wait a little longer to make sure all interested editors have had their say before asking for a close. There has not previously been definitive guidance on this matter: a short period of quiet and calm won't do any harm. Shhhnotsoloud (talk) 07:52, 5 July 2018 (UTC)
Last I looked, I'm perfectly capable of stating and implying things on my own without someone else doing it for me first. Thanks for your concern, though. 08:00, 5 July 2018 (UTC)
As you seem to think it is needed, I endorse SMcCandlish's comments - RfD discussions are a wider consensus than WT:DAB, and this RfC is getting very circular due to a couple of WT dab regulars making it so. Thryduulf (talk) 10:45, 6 July 2018 (UTC)
Right. Your arguments were unpersuasive, and you kept repeating them when you were told they weren't convincing, and it's the audience that made you do it. OK. -- JHunterJ (talk) 12:45, 6 July 2018 (UTC)
Yes, because the "audience" as you put it, didn't say "I have heard your answers and disagree with them because XYZ" they said "but you haven't answered this question" every time it was answered and then for good measure asked it again with a few more straw men. It's absolutely classic refusal to hear what is being said. Thryduulf (talk) 13:08, 6 July 2018 (UTC)
We disagree.[6] Yes, yours is an absolute classic refusal to hear what is being said. -- JHunterJ (talk) 14:58, 6 July 2018 (UTC)
Except you aren't saying anything but repeats of arguments that have already been addressed, and asking the same questions over and over again after they've been answered. There's only one IDHT pattern happening here, and it's not coming from Thryduulf. 07:52, 9 July 2018 (UTC)
Is it surprising that there's strong opposition to treating SIAs the same as dabs (with this respect), when the consensus is in bold WP:SIANOTDAB. To me, hanging on to these vestigial redirects is just pointy. I don't buy the arguments for a minute, and they have no consensus. The fact that the redirects don't seem to be officially recognised as a dependent page is the issue. That should be fixed anyhow. It's actually quite a minor, obscure issue and as such redirects can never be created to all SIAs, this is really an example of WP:BURO or bike-shed effect considering the number of dabs missing redirects, which could be bot fixed today. 13:01, 30 August 2018 (UTC)
"Is it surprising that there's strong opposition to treating SIAs the same as dabs" yes, because for reasons repeatedly explained, having a (disambiguation) redirect to a SIA is not treating SIAs and DABs the same in any way that has any impact what so ever on any of the differences between SIAs and dabs mentioned on any page about either of them. Your "redirects can never be created to all SIAs" argument is another example of a deliberately misleading statement - for the purposes of this argument there are two categories of SIAs - ones which share their name with a dab page and ones which don't. As repeatedly explained, where there is a disambiguation page and a non-disambiguation page with the same name the title with "(disambiguation)" should be either the location of the dab page or a redirect to it - the SIA will be linked from the disambiguation page so anyone searching using "(disambiguation)" will find what they are looking for whether it is the dab or the SIA. Such redirects can easily be created by a bot. Where there is not a dab page with the same name then the "(disambiguation)" title can be created as a redirect to the SIA allowing people to find what they are looking for using "(disambiguation)" - these can also be easily created by a bot - using trivial logic once the redirects to dab pages are created (if "Foo (disambiguation)" exists, do nothing) or more complicated logic before then. Not that this has ever been about requiring such redirects, merely allowing them. Thryduulf (talk) 10:13, 1 September 2018 (UTC)
Is you proposal to create all these redirects manually? please see "Question - how many SIAs does this fail for?" there are SIAs that have titles far from the ambiguous term e.g. Smith and the SIA listing the surnames List of people with surname Smith. I don't think it's a fatal complication, but it misleads others to incorrectly state that this is a simple/zero cost like adding new redirects with a bot. A bot would create List of people with surname Smith (disambiguation). e.g. 2 Rangers F.C. (disambiguation) and SIA List of association football clubs named Rangers - what do you propose?. All dabs can have redirects (or be at that title), SIAs being different can't or wouldn't be desirable. 14:56, 1 September 2018 (UTC)
This proposal is not (and has never been) to create these redirects by bot, it is to allow them to exist however they are created. I agree that redirects like List of people with surname Smith (disambiguation) seem silly but how to determine which (if any) should be created by a bot is a question for a separate discussion after we've established that these redirects are useful in at least some cases. Thryduulf (talk) 15:49, 1 September 2018 (UTC)
My point being the concept of using redirects to discover all lists that may be used for navigation is generally unwieldy and unworkable. If it won't work generally, one can't rely on it, so it's a hack. (I'm willing to concede if SIAs were split into dab like, and list like, then the dab like ones may be useful to be considered as dabs, possibly converting them to dabs is easier. Maybe that could be achieved by tightening up on SIA - inclusion criteria / minimum length / arrangement with a matching dab - I don't know. Instead of proposing solutions, the problem needs defining IMHO.) 13:33, 16 September 2018 (UTC)

### Proposed mitigation 2

If the answer to this RfC is Yes then I propose the following guidance:

A redirect Foo (disambiguation) may target a page that is not a disambiguation page but an article that could perform a disambiguation function, such as a set index article or a list, but such a redirect is not always required. Where there is such a redirect, place an appropriate `{{redirect-notdab}}` hatnote at the target article:
`{{redirect-notdab|Foo|SIA}}` "Foo (disambiguation)" redirects here, although this page is a set index article and not a disambiguation page.
`{{redirect-notdab|Foo|list}}` "Foo (disambiguation)" redirects here, although this page is a list article and not a disambiguation page.

This mitigation is offered in the spirit of compromise, taking into account that some contributors to the discussion think users find such redirects useful, but others think they are not necessary and their existence creates confusion. Short support/oppose comments (perhaps with improvements) are welcome, without re-running the arguments above. Shhhnotsoloud (talk) 07:35, 9 July 2018 (UTC)

• Support. Seems fine to me. The goal is to get readers to the content they seek, not force them to learn nit-picks of our internal page classification system and dump them at a directly misleading "Wikipedia does not have an article ..." red-link notice. 07:52, 9 July 2018 (UTC)
• Why would a redirect that will never be used require a hatnote? Hatnotes are ugly and deface articles, they should be used sparingly and not just for the sake of it. —Xezbeth (talk) 12:09, 9 July 2018 (UTC)
Hatnotes serve multiple purposes. The fact that most of them are for disambiguatory navigation doesn't mean that's the only purpose to which they're put. See, e.g., Category:Hatnote templates for names; `{{Correct title}}`, etc. And "are ugly and deface articles" is obviously an extremist view no shared by most of the community or we would not use hatnotes. 21:21, 9 July 2018 (UTC)
• Strong oppose, that goes against the purpose of WP:HATNOTES since there is not another article we would be guiding them to. Besides, it just makes the problem worse because it suddenly becomes "reader-facing", when it wasn't before. -- Tavix (talk) 13:31, 9 July 2018 (UTC)
Not dumping readers at a directly misleading "Wikipedia does not have an article ..." red-link notice would, actually, be a net benefit. 23:45, 9 July 2018 (UTC)
• Oppose, meh, there's been many opportunities to convince of a problem, so in the absence of convincing reasoning there's no need for a solution. Consensus is clear WP:SIANOTDAB. My gut feeling is improved search is the answer, not ASTONISHING redirect hacks. 13:48, 30 August 2018 (UTC)

### Proposed mitigation 3

I propose the following guidance:

A redirect Foo (disambiguation) may only target a disambiguation page. To assist reader navigation for the issue where a qualified redirect is needed to indicate in the search box that a list of similarly-named topics exist, but that list is an article and not a disambiguation page, use Foo (set index). The savvy reader who picked up on the existence of (disambiguation) as a qualifier for disambiguation pages will also pick up on the existence of (set index) as a qualifier for set indexes. This has the benefit of maintaining the reasons for redirects: making sense and not causing confusion (see WP:RFD#DELETE) while still providing the mnemonic search box assistance provided by the current redirects. -- JHunterJ (talk) 14:24, 9 July 2018 (UTC)
• Oppose. Unlike Foo (disambiguation), Foo (set index) is unheard of. Set indexes are disambiguated by type when necessary, not due to the fact they are set indexes (eg: Foo (ship), Foo (surname)). Furthermore, unlike WP:INTDABLINK, there is no need for links to set indexes to be fixed, so there is no need for an "overarching" disambiguator for set indexes. This would result in the creation of thousands of unnecesssary redirects for very little to no benefit. -- Tavix (talk) 16:10, 9 July 2018 (UTC)
Before (disambiguation), "Foo (disambiguation)" was unheard of too. True, set indexes are disambiguated by type or better by "List of Xs named Y"; this would not be the article title, but the title of a redirect used for the readers who supposedly rely on incorrect "(disambiguation)" redirects. This would at least be "less incorrect" than targeting "(disambiguation)" redirects at non-disambiguation page list articles. I agree with you that there is little to no benefit; this mitigation is a compromise with those who claim that there is a benefit. It would also only result in the replacement of (disambiguation) redirects to set index articles, not the creation of new ones. -- JHunterJ (talk) 12:17, 10 July 2018 (UTC)
I'm confused why you feel a compromise is necessary? -- Tavix (talk) 13:18, 10 July 2018 (UTC)
To collaborate on the encyclopedia. I can agree that there is little to no benefit and then also agree to a mitigation with editors who agree there is a benefit, if one can be found that doesn't lie to the reader. There's no benefit to putting falsehoods in the encyclopedia, even if falsehoods might benefit some readers. -- JHunterJ (talk) 15:20, 10 July 2018 (UTC)
You're mistaking the argument, JHunterJ; it's not whether it's "unheard of" in titles, its that there are too few (and will remain too few) pages in the class for it to ever become "heard of". 22:03, 11 July 2018 (UTC)
As long as we're just basing the arguments on anecdotal assumptions, I've heard of it. -- JHunterJ (talk) 13:39, 12 July 2018 (UTC)
Of course you have; you're a long-term editor deeply involved in DAB and other aspects of page titling and management, not a random non-editor reader. You're the guy who works at Hatcha's Cafe in Mora, New Mexico, who's convinced that Hatcha's is famous because he's heard of it. Heh. 01:32, 13 July 2018 (UTC)
You've hit my point without realizing it. This whole hubbub is based on the anecdotal reports of someone seeking out (disambiguation) redirects to reach non-disambiguation-page set index list articles. The proposal is thus from your Hatcha's employee. Heh heh. -- JHunterJ (talk) 12:22, 13 July 2018 (UTC)
But no one has very proposed such a rationale. Users quickly learn "(disambiguation)", but they are not trying "to reach non-disambiguation-page set index list articles"; they probably don't even know those exist, because they're rare and obscure. They're trying to reach a disambiguation page. If we don't have one but do have an SIA that provides the actual topic they're looking for, the responsible and user-friendly thing is to give it to them, since SIA serve both a content and navigation purpose. It also has the side benefit of introducing them to this thing called a set-index article, probably for the first time. On the main point, consider this analogy: I need a Philips screwdriver. You have a screwdriver that has a reversible head with both Philips and flat-head. But you refuse to let me use it because I asked for a Philips one, not a reversible two-way one. See the problem? 12:29, 13 July 2018 (UTC)
• Oppose per Tavix; there are too few set index articles for "(set index)" to ever enter the awareness and memory of the average WP reader so the entire premise is faulty. I've been here over 12 years and have only run into a few SIAs; basically, no one knows about them but the small clan who work on them. 20:35, 9 July 2018 (UTC)
Right, no one knows about them yet, just as no one knew about disambiguation until Wikipedia disambiguation pages proliferated. The argument for using the incorrect disambiguation redirects is that savvy Wikipedia readers learned about them. The argument here is in agreement, that those Wikipedia readers are still savvy and would also recognize and then use the (set index) when needed. -- JHunterJ (talk) 12:17, 10 July 2018 (UTC)
• I like the first sentence. As to the rest why can't a redirect point to the type of article as in the examples provided by Tavix eg: Foo (ships), Foo (surnames)) --Bejnar (talk) 23:40, 11 July 2018 (UTC)
• Oppose This is worse than pointless - the first sentence harm the encyclopaedia by unnecessarily requiring people to know what type of page they are looking for before they have read it, meaning it is harder for people to find the content they are looking for. The rest of it offers absolutely no benefits at all (although to be fair it wont harm anything either). Thryduulf (talk) 09:13, 15 July 2018 (UTC)
• Comment meh, yes it's at least a logical solution regarding the redirect name. It's also a compromise which fits with the compromise that is SIAs. It's maybe more consistent to make it mandatory to disambiguate by type per Tavis, but in the absence of a well defined problem (like dabs not allowing direct linking which doesn't apply to SIAs, it's just a solution looking for a problem. The logic of extending (disambiguation) redirects to lists as they may also be useful is flawed, that's all I know in the absence of a simple, convincing argument. I can't help that there's vocal proponents of an unsupported hack, but let's not enshrine hacks into supported features. 13:42, 30 August 2018 (UTC)

The above discussion is preserved as an archive of the debate. Please do not modify it. No further edits should be made to this discussion.

## Without an article

Is a disambiguation page necessary if it consists of multiple entries without a Wikipedia article that is directly related to the disambiguated term? E.g. High on Life consists of multiple entries but none of which has a Wikipedia article. The editor whose username is Z0 06:51, 27 July 2018 (UTC)

Suppose you remember a song title called “High on Life”, but you don’t remember who made it or when. That page would present you with possibilities to explore, even if there is no stand-alone article on the song you’re thinking of. That’s a perfectly fine disambiguation page, as long as there’s a blue-linked article for each entry that at least mentions the disambiguated term. — Gorthian (talk) 07:33, 27 July 2018 (UTC)
@Gorthian: Sounds reasonable but that could lead to the addition of non-notable (or promotional) content. I mean if it's okay to add anything without a WP article, that's going to create a mess. In the RFD for High on Life, I brought it up but editors seem to agree with you that disambiguation pages could be created even when the entries don't consist of a correlated article. The editor whose username is Z0 09:49, 27 July 2018 (UTC)
It's not a disambiguation page, it's a redirect that has been hijacked. The redirect is under discussion at Wikipedia:Redirects for discussion/Log/2018 July 25#High on Life, please respect WP:MULTI. --Redrose64 🌹 (talk) 11:17, 27 July 2018 (UTC)
And please see MOS:DABMENTION, the part that covers those entries while prohibiting non-notable ones. -- JHunterJ (talk) 12:39, 27 July 2018 (UTC)
Is it possible for someone to clarify in the guideline page that creating a disambiguation page based on just 2-3 entries that do not have a WIkipedia article matching the term, is acceptable? Courtesy ping @Ss112: @Hayman30: @Station1: The editor whose username is Z0 08:14, 2 August 2018 (UTC)
WP:DABSTYLE: "Each bulleted entry should have a navigable (blue) link, normally as the entry itself (see the previous bullet), or in the description if the entry is red-linked or unlinked.
Rarely should a bulleted entry have more than one navigable link; including more than one link can confuse the reader." I believe that covers it. Nobody's saying or going to promote the idea that creating a disambiguation page where there is nothing navigable for any of the entries is acceptable. Ss112 08:20, 2 August 2018 (UTC)
Some editors think there should not be a dab page if there are zero articles on WP for a term, which indicates the guideline isn't clear enough. It should be amended to include a list of requirements for creating a disambiguation page just for clarity. The editor whose username is Z0 09:56, 2 August 2018 (UTC)
Yeah, that would probably be harmless and likely helpful. I would watch out that the summary does not subtly but substantively change the requirements, though (intentionally or otherwise). 04:17, 3 August 2018 (UTC)

### RFC

• Comment Should we amend the wording to state explicitly that the blue link may occur anywhere in the entry? That would clarify that items such as
• High on Life, an album by QFX
on dab High on Life do count as blue-linked entries, even though the initial words aren't linked. — Certes (talk) 12:27, 3 August 2018 (UTC)
Sounds reasonable. The editor whose username is Z0 15:00, 8 August 2018 (UTC)
Yes; that definitely qualifies. 15:51, 3 August 2018 (UTC)
• But this questions is already treated, with much more detail, in the section Wikipedia:Disambiguation#Disambiguation page or hatnotes? which is further up the page. – Uanfala (talk) 12:53, 3 August 2018 (UTC)
That section is about primary topic and suggests a disambiguation page may be created when there is no primary topic, but it does not say exactly what is needed to warrant a disambiguation page. Hence, causing some editors (1) to think a dab shouldn't be created if two or more title-matching WP articles do not exist. In some way I agree with their sentiment that non-notable entries shouldn't be added but then it could be helpful, so why not? @Uanfala: The editor whose username is Z0 14:58, 8 August 2018 (UTC)
May be better to cross-reference that section, though it doesn't actually hurt to reiterate the central matter. We have to remember that people enter these page sections via shortcut links and do not read them top-to-bottom. So, something like: "... is warranted when there are two or more entries with blue links and there is no primary topic (see § Disambiguation page or hatnotes?, above)." No need for boldfacing. 15:51, 3 August 2018 (UTC)
That could work. The editor whose username is Z0 15:01, 8 August 2018 (UTC)
• "Disambiguation in Wikipedia is the process of resolving conflicts that arise when a potential article title is ambiguous..." Non-notable topics are not potential article titles, and therefore should not appear on dab pages. Dab pages were never intended to be indexes or search engines. In fact, a bad dab page can get in the way of the search engine. DABMENTION always used to be understood to be for cases where a notable topic was covered in another article. It's only recently that a few editors have been adding non-notable songs that often are barely mentioned at all in the article, sometimes with no more info than what appears on the dab page itself. If we start adding non-notable entries, we would need to add hatnotes or dab pages for every spouse of a state legislator who happens to be mentioned in passing and shares a name with a notable person, not to mention every Main Street and every bit actor and fictional character who shows up in a cast list. I recommend we change "topic" to "notable topic" in DABMENTION. Station1 (talk) 19:27, 4 August 2018 (UTC)
That's one interpretation. But the other (and mine) is that any non-notable information should be removed from the article that mentions it. Disambiguation pages are not the place to make the value judgment of when a mention in the encyclopedia is notable and when it isn't. If any given song title were unambiguous, would it be a possible {{R from song}}? Yes. So if ambiguity exists instead, it should be listed on the disambiguation page. If it's truly non-notable, it shouldn't be mentioned (or "noted") in the encyclopedia. -- JHunterJ (talk) 12:16, 10 August 2018 (UTC)
And there is a third view, the one that's practiced by the majority of wikipedians: whether to create a redirect or add an entry to a dab page is a decision whose basis lies somewhere between the two extremes of notability ( = deserving a separate article) and noteworthiness ( = deserving a mention within an article). If we have meaningful encyclopedic content on a topic, then it doesn't matter whether the topic is treated in an article of its own, or together with other topics as part of an artile – this warrants having an entry on a dab page. Conversely, every reasonably developed article is likely to make passing mentions of a large number of entities, about which we will never have any content apart from these passing mentions – almost no-one would dream of adding these to dab pages. – Uanfala (talk) 13:07, 10 August 2018 (UTC)
I suppose that's effectively my view as well. If it could have been a redirect except for the ambiguity, then it can be on the disambiguation page with the the ambiguity, because that's the technical problem disambiguation pages exist for in the first place. The passing mentions that no one would think to add to dab pages (or think to put into the Search Wikipedia box) wouldn't be redirects or disambiguation page entries. But song on albums would be things that people with think to make redirects for (and think to put into the Search Wikipedia box), so would be things people would think to put on disambiguation pages. Certainly if no one thinks to put it on a disambiguation page, the question of whether to remove it from that disambiguation page won't come up. -- JHunterJ (talk) 15:49, 10 August 2018 (UTC)
I agree that we should use the same criterion for creating redirects as for adding dab entries. The disagreement, I guess, comes from the application: I don't think that a song that is merely mentioned in an article about an album warrants a redirect. If we don't have any meaningful content about the song, and if we can't expect out article to ever say anything about it other than the fact that it was on a certain album, then this is not the kind of thing that readers will be putting in the search box and it is not the kind of thing we would want to integrate in the encyclopedia's navigational system. – Uanfala (talk) 20:34, 10 August 2018 (UTC)
Do such redirects, when created, get deleted through RfD? (I don't know, I don't follow RfD closely, but the existence of {{R from song}} indicates to me that they're viable without expectation of going anywhere else.) -- JHunterJ (talk) 20:44, 10 August 2018 (UTC)
WP:R#PLA seems to indicate that that there should generally be content at the target but unlike WP:DABMENTION doesn't appear to mandate it. I'd suggest treating the criteria for a redirect as the same as DABMENTION. Crouch, Swale (talk) 12:57, 29 August 2018 (UTC)
• Disambiguation pages when there are only two pages is bloat. Totally unnecessary, even if there is no clear primary topic. Choose the one that was created first if you have to, but put one at the base name, and a dab link from it to the other one at disambiguated title. A dab page with two entries serves no purpose. This is what WP:TWODABS used to say, and that guidance should be restored. --В²C 18:33, 10 August 2018 (UTC)
A dab page with only two entries when neither of them is primary serves the purpose of disambiguating two topics when neither of them is primary. WP:TWODABS, when it said that, did not have consensus. -- JHunterJ (talk) 19:04, 10 August 2018 (UTC)
But User:Born2cycle is right though. It's bloat because instead of OneTopicX and OtherTopixX (2 pages) we have TopicX, TopicX (disambiguation) (an INTDAB redirect), OneTopicX and OtherTopixX (4 pages). Not only are there now twice as many pages to maintain, but every searcher is a loser. If a user searches for "TopicX" when they wanted OneTopicX, they are diverted via the dab page. If a user searches for "TopicX" when they wanted OtherTopicX, they are diverted via the dab page. 100% of searchers have to click through a dab page. Any mechanism to determine a primary topic (page views, Google hits, page creation date, toss of a coin) and the consequent use of hatnotes is better than a 2 dab page with no primary topic. (That's clearly my opinion, not what the guidance says). Shhhnotsoloud (talk) 10:20, 11 August 2018 (UTC)
But that's wrong, because it's another click but a needed click because neither topic is primary. There are twice as many pages to "maintain", but of course "maintaining" a two-entry dab and its redirect is pretty light work (until there are 3+, and then it's no longer the subject of this discussion). And every disambiguation page without a primary topic means that every searcher arriving is a "loser" in your terms; should we randomly or otherwise compel a primary topic for every title? Since we're not ready to abolish base-name disambiguation pages in the general case, there's no reason to abolish them in the two-entry case. If one of the two entries is primary, great; otherwise, there's no problem here. -- JHunterJ (talk) 12:19, 13 August 2018 (UTC)
Borderline primary topics already inconvenience readers when wikilinks to the wrong targets creep in. (For example, I recently diverted several soldiers from a company to a company (military unit), and species from a family to a family (biology).) Such errors would be more widespread if we put ambiguous topics at the base name just because there is only one other meaning. Certes (talk) 14:43, 13 August 2018 (UTC)
JHunterJ, when there are only two topics and neither is clearly primary than both are close to being primary. That is, about half the people searching with that name are seeking one or the other. An article with a hat link to the other article serves as a disambiguation function just as well as a dab page for disambiguating. The distinction between a primary topic and a nearly-primary topic is, by definition, minor. So treating either nearly-primary topic as primary should not be a big deal. But, in the general case, with more than two entries, the odds of landing someone on the sought page drops from about 50% rapidly to around 33%, 25% and lower, and now the "losers" are usually redirected to a dab page from which they have to click again to get to their desired page. That's why TWODABS was originally treated as a special case. I don't think most participants understood and appreciated this critical distinction when it was changed. Certes, yes, topics that are nearly-primary have the same problem as topics that are actually primary - the possibility of linking to the wrong topic exists when you have an article rather than a dab page at a base name. I've seen others use this as an argument to not have primary topics at all. I think the nearly-primary topic in a TWODABS case having this issue is just a minor side issue. If we tolerate it for all genuine primary topics, tolerating it for nearly primary topics as well is relatively minor. --В²C 18:16, 13 August 2018 (UTC)
Born2cycle, when there are only two topics and neither is primary (clearly primary is just primary), then both are far from being primary. That is, neither is close to being much more likely than any other single topic (the other single topic), since we just stipulated that they are close to each other. The distinction between being a primary topic and a non-primary topic (there is no such thing as "nearly primary") is, by definition, major. -- JHunterJ (talk) 18:48, 13 August 2018 (UTC)
JHunterJ, okay, point taken, but I think we need to reasonably interpret that wording in a 2-dab situation. In a 3-dab situation we could easily have a primary topic having 51% of the likelihood being hit (e.g. 51/25/24). But in a 2-dab 51/49 situation the same 51% likelihood is not good enough to be PT? I don't see how it makes sense that a topic with 51% likelihood can be primary topic if it's the only use, or one of three or more uses, but not if there are exactly two uses. Seems absurd to me.

Okay, I know, in a 3-dab 51/48/1 situation the 51 also wouldn't technically meet the PT criteria, but I really don't get the point. I mean, the whole point of primary topics is to take people directly to the article they are likely to be seeking, and to minimize those who are not immediately taken to the article they are seeking. I guess it comes down to whether one thinks being sent to a different article (with a hatnote to the article being sought) is less desirable than being taken to a dab page. I see those two results as being functionally equivalent in terms of desirability. I personally don't mind being taken to the wrong article if that article has a hat link to the article I am seeking; I mean, that's no worse than being taken to a dab page. Or, if you prefer, they are equally annoying. So I don't get the motivation to prefer sending everyone to a dab page with links to their sought articles rather than taking about half to the article they seek and the other half to an article with links to their sought articles (hatnote macros support links to multiple alternatives and thus can serve as mini dab pages at the top of any article at a base name). --В²C 20:46, 13 August 2018 (UTC)

"wouldn't technically meet the PT critera" = "wouldn't be a primary topic". "Technically" is unneeded there. See Certes' note of 14:43, 13 August 2018 (UTC) above for part of the point. -- JHunterJ (talk) 12:20, 14 August 2018 (UTC)
Yes, but we can still treat a nearly-primary topic as if it was primary and put it at the base name. As to Certes' point, I addressed that already, just above, in the latter part of my 18:16, 13 August 2018 comment. I, for one, think serving readers better is more important than making it easier to identify some very small percentage of imperfect links. Taking about half of those searching with a given term directly to the article they seek is better than taking none to the article they seek, even if it also means taking the half not seeking that article there. That half is no worse off than they would be had they been taking to a dab page; either way they are just one easy click to the article they seek, while the first half is clearly worse off at the dab page than if taken directly to the article they sought. Similarly, for the imperfect links that take a user to the wrong one of two nearly-primary topics, that user is also only one hatnote click from the right article, which is why I refer to the original link as being merely "imperfect".

More generally, why the affinity for dab pages? Any search that lands a user on a dab page is a failure in our system. Note that Google searches don't take users to dab pages because they know that's not what users are seeking. For example, enter "obama presidential campaign" at Google.com and click on feeling lucky (their equivalent of our "Go"). You don't get taken to our TWODABS dab page; you get taken to Barack Obama presidential campaign, 2012. But in WP search hitting Go on the same search string takes us to the TWODABS dab page at Barack Obama presidential campaign. Putting one of two nearly-primary topics at the ambiguous base name helps us avoid sending users unnecessarily to dab pages like this - that's a good thing. --В²C 17:29, 14 August 2018 (UTC)

There are two things that are good to avoid:
1. Unnecessarily sending users to disambiguation pages
2. Unnecessarily sending users to articles about topics they weren't seeking
The primary topic guidelines, including those for base-name two-element disambiguation pages, balance those two. Landing on a two-element disambiguation page when neither is primary is not unnecessarily landing there. -- JHunterJ (talk) 19:52, 14 August 2018 (UTC)
Landing on a two-element dab page when neither is primary is unnecessarily landing there, for at least about half of those that land there. It's unnecessarily landing there for them because if we put the one of the two articles they are seeking at the basename, they will land on the article they are seeking. As to the second half, the only alternative is also "good to avoid", unnecessarily landing on an article they're not seeking, which is no more important to avoid than unnecessarily landing on a dab page, so it's a wash from their perspective. That is, the second half is unnecessarily landing on one or the other; it's unnecessarily either way because no matter which it is, it could be the other one. However, it is necessary to land the second half on the article they are not seeking in order to improve the experience of the users in the first half, while not compromising the experience of the second half. When we can reduce the number of users unnecessarily landing somewhere good to avoid by about half of those in question, that seems like an obvious improvement to the encyclopedia user experience. After all, the users in the second half for a given topic might very well be in the first half when searching with other terms with two uses. On these encyclopedia-improving grounds, I think a strong WP:IAR argument can be made for ignoring the current wording at WP:PRIMARYTOPIC and WP:TWODABS in these two-near-primary-topic situations. Of course, it would be better to make explicit changes in the relevant policy and guidelines accordingly. --В²C 21:13, 14 August 2018 (UTC)
I suggest that sending a reader to the wrong page is worse than sending them to a dab. They may not realise that they're on the wrong page, even with a hatnote (which won't appear on all devices). Articles also tend to take more data and time to load than dabs. No one can quantify this difference and say that sending one reader to the wrong page is as bad as sending exactly 3.142 readers to a dab, but there will be some such ratio ${\displaystyle r}$ and I suggest that ${\displaystyle r>1}$. Let ${\displaystyle p}$ be the proportion of readers seeking the most popular topic (best candidate for PT). Then a primary topic page will cause no inconvenience to ${\displaystyle p}$ of the readers, and ${\displaystyle r}$ times more inconvenience than a dab for the other ${\displaystyle 1-p}$. So we should prefer a dab where ${\displaystyle r(1-p)>1}$, i.e. ${\displaystyle p<1-1/r}$. For example, if you think that ${\displaystyle r=3}$ (a number I plucked out of thin air) then we should have a dab page when we estimate that fewer than ${\displaystyle 2/3}$ of readers seek the primary topic. Of course, there may be other factors to consider when making this editorial judgement, but that logic may be useful for simple cases. Certes (talk) 00:07, 15 August 2018 (UTC)
Great analysis. Thank you! We disagree about sending a user to the wrong page being significantly worse than sending them to a dab (assuming the "wrong page" has a hat note link to the "right" page). Or, if you prefer, I think ${\displaystyle r=1.1}$ or so. But as long as ${\displaystyle r<2}$ then placing the article for either of two topics at the base name is at worst a wash if both of their ${\displaystyle p}$ values are near ${\displaystyle 0.5}$, which is the situation we're addressing, and is progressively better than a wash the lower below ${\displaystyle 2}$ the value of ${\displaystyle r}$ is, and the higher above ${\displaystyle 0.5}$ the value of ${\displaystyle p}$ is for the article placed at the base name in a given case (which it will be in most cases - both topics being exactly ${\displaystyle p=0.5}$ is highly unlikely). --В²C 17:07, 15 August 2018 (UTC)
##### two dabs history
• FWIW, WP:TWODABS "used to say" exactly this, that when neither topic was considered primary, a disambiguation page is used.[8] If someone else wants to identify whatever other language was put in there after what it used to say, we can go look to see if there was any consensus for that change. I believe there was not. -- JHunterJ (talk) 18:54, 13 August 2018 (UTC)
This change and this discussion seem relevant. Certes (talk) 19:17, 13 August 2018 (UTC)
This is what I mean by what it used to say, and what I think should be restored: "If there are two topics for a term but neither is considered the primary topic, then a disambiguation page may be used; an alternative is to set up a redirect from the term to one of the topics, and use disambiguation links only." [9] --В²C 20:58, 13 August 2018 (UTC)
Let's highlight that appropriately: "If there are two topics for a term but neither is considered the primary topic, then a disambiguation page may be used; an alternative is to set up a redirect from the term to one of the topics, and use disambiguation links only." -- JHunterJ (talk) 12:20, 14 August 2018 (UTC)
• Yes, that's the situation we are talking about: two topics neither of which is primary. What TWODABS used to say was that a dab page may (not must) be used. --В²C 16:48, 14 August 2018 (UTC)
• Hmm, the concept was apparently originally introduced at MOSDABS on July 21, 2007, and there it clearly applied only when one of the two was primary[10]. --В²C 17:00, 14 August 2018 (UTC)
• Personally per WP:2DABPRIMARY I would give a lower threshold to PT status since the DAB means readers seeking either have a click, rather than just those looking for the alternative topic. However I would note that DAB pages are easier to load and probably should be used in situations where its unclear which topic is primary. Crouch, Swale (talk) 07:30, 28 August 2018 (UTC)
##### 1

Is there consensus to make the proposed change? The editor whose username is Z0 04:49, 26 August 2018 (UTC)

What is the position on redlinks on Dab pages?
The WP:DABNOT section seems to suggest that titles shouldn't be included if there isn't an article to disambiguate from: OTOH the Urney example at WP:PRIMARYTOPIC, and WP:DABRED, say that they are fine. (Though the Urney page looks more like a set index; is there a better example?). It came up in conversation here, and I've had redlinks removed from dab pages before, “as they don't belong”, so I'm asking; are they generally OK, or are they not really a good idea? Moonraker12 (talk) 19:42, 13 August 2018 (UTC)

Moonraker12, details of when red links are allowed are at WP:DABRL. Basically, a red link is okay as long as there is also a blue link in the line to an article where it is also a red link, and (we hope) some information about it. — Gorthian (talk) 19:50, 13 August 2018 (UTC)
Gorthian: So, no problem, then? fair enough, I'd got the impression they were a bit frowned upon. Thanks for replying so quickly, Moonraker12 (talk) 19:56, 13 August 2018 (UTC)
Moonraker12: Actually,I answered a little hastily above, not realizing we were citing the same section. WP:DABRELATED says Include articles only if the term being disambiguated is actually described in the target article.. There doesn’t need to be a whole article about it, just somewhere it is “described”. (But in practice, sometimes “described” is interpreted as “mentioned”, as in songs on an album’s track list.) — Gorthian (talk) 20:03, 13 August 2018 (UTC)
Gorthian: Ah! So we are on the same page! Moonraker12 (talk) 20:18, 13 August 2018 (UTC)

Yeah, as the guidelines linked above say, redlinks are fine as long as we've got the topic covered somewhere. The emphasis here is on "topic" and "covered", rather than "term" and "mentioned": in my opinion (with which a small number of dab regulars disagree) is that if the given term is only mentioned in a target article and there isn't likelihood there will ever be any content about it beside this mention, then the term does not belong on the dab page. On the other hand – and I suspect more people will disagree with me on this point – there are situations in which we ought to add an entry even if it's not described or mentioned anywhere. For example, imagine that you're looking for an Eastern European village named "Bukovets". If you look at this version of the dab page, which lists the three villages for which we have articles, all of them in Bulgaria, you might conclude that your village is among those three and that it is located in Bulgaria. However, it happens to be the case that there are several villages with the same name in Ukraine, and even though we don't seem to have either articles or "mentions" about them anywhere yet, it nevertheless makes sense to include them on the dab page (as in this version), to make readers aware that the village they're looking for might not be among the ones we currently happen to have content about. – Uanfala (talk) 20:41, 13 August 2018 (UTC)

Since dab pages are meant to guide readers to an article, a red link with no accompanying blue link is useless. (Just the same as a hatnote pointing to a red link is useless.) That’s why the MOS is so specific about that. — Gorthian (talk) 21:36, 13 August 2018 (UTC)
What (if anything) should we do about pages full of red links which resemble a set index article as much as a dab? Maoping is a typical case but there are far worse examples. Certes (talk) 21:53, 13 August 2018 (UTC)
If the topics are notable (as they are in the case of Maoping), my preferred course of action is to take no action: the read sea will eventually turn blue. – Uanfala (talk) 21:58, 13 August 2018 (UTC)
MOS:DABRL says: A link to a non-existent article (a "red link") should only be included on a disambiguation page when a linked article (not just other disambiguation pages) also includes that red link. So the main criterion is the existence of inward links to the redlinked page. Each redlinked entry on Maoping should be considered individually. Looking at this version of the page and ignoring the bluelinks:
So the three that have been removed from the page were valid removals, the other four were correctly retained. --Redrose64 🌹 (talk) 12:11, 14 August 2018 (UTC)
The incoming links criterion is useful in weeding out potentially non-notable topics, but I don't think it's relevant here, as the notability of these populated places is inherently given. – Uanfala (talk) —Preceding undated comment added 12:32, 14 August 2018 (UTC)
Wait, what? No, incoming links to red links is relevant there. If they don't have them, we don't use the red link on disambiguation pages. The populated place might still be included on the disambiguation page if there is a blue link to an article that MOS:DABMENTIONs it. -- JHunterJ (talk) 13:49, 14 August 2018 (UTC)
Redrose64, that’s one way to find articles for blue links to match the red ones. Luckily, the editors working on Chinese places tend to be consistent with the title disambiguations, and it’s easy to check. But in other situations, one editor has chosen one disambiguated title and another editor has chosen a different one, and sometimes neither one is the one that ends up on the dab page. There was one I ran across yesterday: in one article, it was Armando González (singer), but in another it was DJ Armando González. I couldn’t even be sure it was the same person, so I finally decided against including a link on Armando González (disambiguation). In other cases, I’ll try to make all the red links consistent in all the articles. — Gorthian (talk) 20:23, 14 August 2018 (UTC)
Thank you ( one and all ) for commenting. I can see the value of having all the redlinks in on the Bukovets, Maoping and even the Urney pages: OTOH I can also see that it goes against our guidelines on the subject. But as those pages would work well (better?) as set indexes (indices?) why not simply change them (and those like them) from dab pages to SI's? Moonraker12 (talk) 22:44, 22 August 2018 (UTC)
This didn't work to notify me, so it won't have notified Uanfala, Gorthian, Certes or JHunterJ either. You need to add the user links and signature in the same post; moreover, it must be a new line, not a modification to an existing line. --Redrose64 🌹 (talk) 19:13, 23 August 2018 (UTC)
Putting a set index at the base name instead of a disambiguation page is fine, as long as all the items are elements of the same set being indexed. Alternatively, creating a "side" SIA like List of places named Bukovets would also work; the Bukovets disambiguation page would simply link to it in the See also section, and we'd keep all of the appropriate entries in both places. Either way is fine. -- JHunterJ (talk) 19:50, 23 August 2018 (UTC)
Having both a dab page and a set index covering the same topic is confusing for readers and adds unnecessarily to the maintenance burden. On the other hand, reformatting the dab page itself into a set index article is probably an option, although I don't see the point (should we turn the SIA back into a dab when all the redlinked articles get created?). I guess I would disagree with the whole premise here – that the presence of entries without links goes against the guidelines. Does it really? Not necessarily: of all guidelines, MOS:DAB is the only one that has a section dedicated to reiterating the principle "ignore all rules": Wikipedia:Manual_of_Style/Disambiguation_pages#When_to_break_Wikipedia_rules – this section is there for a reason. – Uanfala (talk) 23:07, 23 August 2018 (UTC)
• I think redlinks are fine, as long as they turn blue with a stub or an article section link within 24 hours. I think an article section is the minimum, DAB pages shouldn’t send readers to mere mentions. —SmokeyJoe (talk) 23:17, 22 August 2018 (UTC)
"mere mention" is just "mention". A mention, not an article section, is the minimum. Disambiguation pages should provide navigational aid to readers seeking things that are mentioned on Wikipedia. The existence of a page (article or disambiguation page) in the place of search results shouldn't hinder the reader's navigation. If the mention truly is too "mere" to need navigation, then it is too mere to be encyclopedic and should be removed from the mentioning article. Red links are fine as long as they also exist in articles; they don't have to turn blue within any timeframe. MOS:DABRL. -- JHunterJ (talk) 19:50, 23 August 2018 (UTC)
JHunterJ, I disagree that "mere mention" is just "mention", though I am happy for you to wordsmith a better explanation, as I think we basically agree. I think the defining line is whether the mention provides some level of definition. If the mention of "John Doe" is "On the third expedition the party was accompanied by Jane and John Doe", it is unworthy of a link, as it says nothing of any substance about John Doe, and such links would often be erroneous anyway. Any reader looking for these low level mentions should use the search function. If the mention includes an introduction, or definition, then it is more than a mere mention. I agree that an article section is above the minimum required for a DAB page link. A paragraph is sufficient, and here on discussing "mere" mentions, we are discussion the depth of mention within possibly just a single sentence. --SmokeyJoe (talk) 01:12, 8 October 2018 (UTC)
If the mention is too mere (whatever that means), then it should be removed entirely from the article. If it's present in the article with any utility at all (and so not delete-able from the article), then it is include-able on the disambiguation page. I do not think we basically agree, so I can't wordsmith it any better. A song listed on an article with no paragraph is a mention enough for inclusion on a disambiguation page. Any mention (whether within a sentence, the subject of a whole paragraph, the heading of a section, or any points in between), along with an editor who then links to the mentioning article from the disambiguation page, is good enough. -- JHunterJ (talk) 11:44, 8 October 2018 (UTC)
A song listed in the article on its album, that would be an appropriate DAB page link. A song that featured in the description of a timeline during an event, in an article on the event, that would not be an appropriate DAB page link. In the second case, this song, non-notable and not mentioned in any other article, I would not agree to removing its mention if sources mention it. SmokeyJoe (talk) 12:01, 8 October 2018 (UTC)

## What if we determined primary topic totally differently... solely from Google?

This is not a proposal, just throwing this idea out there for thought and discussion. What if we determined primary topic solely from Google?

Specifically, for a given search term, you would go to google.com and enter:

```site:en.wikipedia.org search term
```

and click on "I Feel Lucky". Whatever page it puts you on, that's our primary topic for that term. Sound crazy? Try it out! Here are some examples:

• site:en.wikipedia.org mercury
• site:en.wikipedia.org barack obama presidential campaign
• site:en.wikipedia.org paris
• site:en.wikipedia.org portland

Why do this?

1. Leverage Google's billion dollar AI technology to determine what users are mostly likely looking for on WP for a given term.
2. Increase how often users are taken to the page they are seeking.
3. No more debates about what the primary topic is.

Thoughts? --В²C 00:26, 15 August 2018 (UTC)

• Horrible. Stupid. Wikipedia is not Google. Article titles should not be sought to match google behaviours. --SmokeyJoe (talk) 10:52, 15 August 2018 (UTC)
• If taking users to where they are most likely trying to go when searching with a given term is a priority, then that's exactly what this approach facilitates. If your priority is to take users to the article or dab page you think they should be taken for a given search term based on your personal sensibilities, then this approach is one you would not favor. --В²C 16:50, 15 August 2018 (UTC)
• You confuse typing in a url with using a search engine. A good title is not necessarily a common search term. Common search terms derived from google are not reliable sources, no matter how often coincidental. —SmokeyJoe (talk) 08:12, 16 August 2018 (UTC)
• Bad idea. We already know that Wikipedia is not a reliable source. Why would you want to restrict the search domain to Wikipedia pages? Mathglot (talk) 11:07, 15 August 2018 (UTC)
• This approaches leverages Google's AI technology to identify what topic users are most likely to be seeking with a given search term as it applies to WP articles. It has nothing to do with our reliability. --В²C 16:50, 15 August 2018 (UTC)
• Do you realize that Google's algorithms are heavily weighted towards following current and local trends, so what they show varies greatly between places, persons and moments? "Google's AI technology" does not provide one topic which is the most sought for a given term. Diego (talk) 14:32, 16 August 2018 (UTC)
• Yeah, let's see how well that works.

I don't know you, but I'm getting a lot of recentism right there. I'd dare to say that Google doesn't have the same interests than us in deciding which topic to show first. Not to mention that, in a few months, those searches will likely lead to different articles, so there's no stability at all. Diego (talk) 11:34, 15 August 2018 (UTC)

Hmm, let's try a couple more examples. I'm Feeling Lucky.
• site:en.wikipedia.org Apple -> Apple Inc.. In flat contradiction of the "long-term significance" guideline at WP:PTOPIC
• site:en.wikipedia.org Luther -> Luther (TV series). So much for the Reformation, a triviality compared to a 2010 UK TV series
• site:en.wikipedia.org Mercury -> Mercury (planet). So much for chemistry and mythology
• site:en.wikipedia.org Phoenix -> Phoenix (mythology). Tough luck if you live in Arizona, your state capital is insignificant
• site:en.wikipedia.org Washington -> Washington, the DAB page. I finally got lucky
I have other worries also:
(1) I dislike PTOPICs unless the selection is clear beyond reasonable doubt. Even then, the PTOPIC will slowly but surely accumulate bad links and no bot report will ever find them. Unhelpful to readers, and bad for the project. (I check the incoming links to Tetrahedron every few months; I usually find a few which were intended for Tetrahedron.)
(2) WP:RECENTISM.
(3) Wikipedia is not WP:RS; Google search results are even less so. There are armies of SEO spammers out there trying to drive the sites which they are being paid to promote up the Google rankings. That's a cottage industry in India and Vietnam. As a former spamhunter/moderator on another site, I saw cases where spammers had got their sites up to the top Google hit. (It was standard practice to open such sites only in a sandboxed browser. I remember one which went all Tasmanian devil on me – it was trying to escape, but my sandbox and AV wouldn't let it.)
(4) Anyone who wants to find out what Google calculates as the primary meaning of a word or phrase has a very simple way to do so. It doesn't involve Wikipedia at all.
In conclusion: No. Just: No. Narky Blert (talk) 19:17, 17 August 2018 (UTC)
Narky Blert, advertisers are excluded and WP is involved because the Google search is limited to the English WP with site:en.wikipedia.org. That said, much of this depends on one's opinion about the relative benefits and risks of landing someone on a sometimes "wrong" article page vs on an always wrong dab page. You dislike PTOPICs; well, I dislike dab pages, and that's probably the biggest difference. In ambiguous cases I'd much rather sometimes be taken to the wrong but most-likely-to-be-sought article, with a hatnote link to my sought article, then always be taken to a wrong (dab) page. As to RECENTISM, as I noted below, I've always felt that's mainly to address temporary spikes in popularity of a few days or weeks, not sustained popularity that is at least many months long, if not years. I mean, if people searching with a given term are most likely looking for some article for a recent movie, and that's likely to be sustained for at least a few months, I think that's where we should take them. If the popularity is only going to spike for a few days, or a couple of weeks, yeah, that is RECENTISM, and we shouldn't bother. It all comes down to what you believe best serves our users. Getting them to the articles they are seeking through the fewest clicks, or delivering to them whatever we think they should be seeing for a given search. Personally, I'm repulsed by that latter goal. It reeks of elitism and snobbery, which is my objection to the whole "historical significance" concept. --В²C 00:02, 18 August 2018 (UTC)
Landing on a DAB page is never wrong. What exactly is the problem with one more click?
I try to look at around 200 bad links to DAB pages every day. I can usually fix about 180 of them. That is about one-third of the bad links which User:DPL bot reports every single day. The WP:DPL team has got the headline number down from 65,000 four years ago to around 5,000. If we're holding that number, it may be because I'm putting in one-third of the effort.
No bot can spot bad links to WP:PTOPIC pages. I see and fix 5 or 10 of those every day; usually when I've seen a possible bad link near a bad link to a DAB page, and because I'm inquisitive and could be bothered to look.
At a rough estimate, based on what I have seen and fixed, English Wikipedia contains several thousands or tens of thousands of links which are completely wrong.
Put in a shift or two at Disambiguation pages with links. Unless you do, I will continue to dismiss your armchair opinions, Narky Blert (talk) 01:08, 18 August 2018 (UTC)
Yes, there are far too many bad links to WP:PTOPIC pages: primates celebrating mass, fees paid in Guineas, songs by Prince and Nirvana… I fixed over 1,000 today and that's the tip of the iceberg. They would be so much easier to find if we had dabs at those base names. Certes (talk) 01:37, 18 August 2018 (UTC)
By the same token I submit that anyone who works with cleaning up bad links is going to be biased to favor making finding "bad" links easier over getting users to their sought pages more efficiently. I'll put in some time there, and give it some more thought. Thanks. --В²C 01:52, 18 August 2018 (UTC)
• That's an interesting idea but I can't support it for several reasons. It does not address the question of whether a primary topic exists at all. Google shows different results to different people: whose lucky pick do we take? Its balance of current usage and lasting importance may not be best for Wikipedia. Finally, Google is influenced by advertisers; we shouldn't move Mars bar to Mars at the whim of the chocolate firm's marketing agency. Certes (talk) 11:39, 15 August 2018 (UTC)
All good points.
• The point here is that there is always a "primary topic" when defined in this new way. It means being okay with sending users to the wrong page that is not a dab page (more on that point coming in our discussion above).
• There's a tag you can add to the URL (&pws=0) to de-personalize results, especially if used in an incognito session. I haven't figured out how to combine it with "I Feel Lucky", but you can always go with the first result in a regular Search.
• I've long held that lasting importance, to the extent that it's significant, is already inherent in how likely a topic is to be sought. No separate consideration is needed.
• I don't think advertisers influence searches limited to a particular site. Apple, Ford, and Oracle do go to the respective pages on corporations, but Trek does not. I think this accurately reflects the likely sought pages respectively.
--В²C 16:50, 15 August 2018 (UTC)
We might usefully employ the "Google test" in a related area. Topping the search results isn't sufficient to make a topic primary, but it is an argument against any other topic being primary for that term. If Wikipedia's normal process and search engines suggest different primary topics, then there may be enough confusion in the reader's mind to justify a dab. Certes (talk) 12:48, 16 August 2018 (UTC)
Of course what I'm suggesting is a radical redefinition of what it means to be a "primary topic". Topping the search results would not only be sufficient to make a topic primary, that's what would make it primary by (the new) definition, and every term would have a primary topic. Entering a term and selecting Go would take you to the article about the topic you're most likely seeking (the primary topic for that term). But just like with Google's "I'm Feeling Lucky" button, you would always have the Search alternative to see and pick from a list of results (including Search Term (disambiguation)). --В²C 20:13, 16 August 2018 (UTC)
But then what would we do for aggravation?? Herostratus (talk) 23:30, 16 August 2018 (UTC)
Move Aggravation to Aggravation (disambiguation) over redirect, and move Aggravation (law)Aggravation? Certes (talk) 00:15, 17 August 2018 (UTC)
Google is showing Aggravation (board game) first in the results for "site:en.wikipedia.org aggravation", so per that we would move that article to Aggravation. The board games is what most WP users are seeking when searching with "Aggravation", according to Google AI tech... --В²C 01:37, 17 August 2018 (UTC)
That's the same as what page views show. I bet those two metrics line up way more often than not. Station1 (talk) 02:37, 17 August 2018 (UTC)
What happens when something like Aggravation (2021 film) is released a few years down the line and gets the lion's share of searches? Do we keep looking how Google searches evolve, and shuffling all our article titles accordingly Diego (talk) 05:16, 17 August 2018 (UTC)
Oh dear. I believe that Herostratus' comment was not entirely serious, and I was replying in the same spirit. I don't think any of those pages should be moved. Certes (talk) 10:32, 17 August 2018 (UTC)
Serious or not, it's a good example of how this change would affect titles. We would be sending more people more often to the articles they are seeking. But yes, as popularity changes, we would realign accordingly, taking into account WP:RECENTISM, which says not to react to brief changes in the popularity winds. I've always taken that to mainly refer to news stories about single events that create sudden spikes in popularity. But yeah, if it's a new movie that shows sustained popularity in what our users are searching for, we should adjust our article titles accordingly. That's the price we pay for not having dynamic intelligent search processing algorithms like Google does. And, yes, Station1, Google results confined to English Wikipedia should align very well with our own page view counts. Good point. --В²C 16:00, 17 August 2018 (UTC)
I think it's a very interesting proposal. But have a look at User:Andrewa/Primary Topic RfC#Some of this is highly counter intuitive. If I'm right, it pulls the rug out from under much of the above discussion. Discuss at User talk:Andrewa/Primary Topic RfC if you think you can shed some light on it. Andrewa (talk) 01:31, 22 August 2018 (UTC)

From time to time, including currently at Talk:Nosedive_(disambiguation), I see the following sentiment expressed in RM discussions: a relatively obscure topic should not be at its basename if the basename is a commonly known word even if we don't have a topic about that word (WP:NOTADICT) nor any other topic with that name. What some people seem to prefer in these cases is that a dab page be at the basename, with links to the article about the obscure topic and to an article that is ostensibly somewhat about the common word for which we have no specific article. I'm baffled by the propensity for sending users to dab pages, but maybe I dislike them more than most.

I'm wondering how others here feel about this issue, and whether some clarification at PRIMARYTOPIC wouldn't help. I know we already have Wikipedia:Disambiguation#Not_"what_first_comes_to_(your)_mind", but that doesn't seem to be enough, perhaps because the focus there seems to be to avoid personal bias regarding "what first comes to mind". --В²C 17:28, 20 August 2018 (UTC)

• A primary topic needs long term significance, not just pageviews and click bait. This is because Wikipedia is an encyclopedia, which means it is an historiographical document. Here, as with the thread above more-so, you dislike the long term significance part, we know. Pageviews and click-counting statistics are interesting, illuminating, informing, but they cannot override long term significance. If there are no pageviews, log term significance works fine. If there is no long term significance, who cares?
The long term significance of a title is unquestionably impacted by the long term existence of a word, especially where topics are derivatively named from the word. There is nothing wrong with the WP:NOTADICT policy; Wikipedia should not attempt to host dictionary entries overlapping with the purpose of Wiktionary. However, readers cannot be expected to instinctively know the WP:NOTADICT policy and that mere simple definitions cannot have Wikipedia articles.
You may dislike dab pages more than average, but you have a point. I agree, readers should know when they are going unwantingly to a dab page. Similarly, readers wanting a dab page (it happens!) should know which is the dab page. The solution is to recognize that WP:MALPLACED was a randomly made up bad idea and should be overturned. Overturned one page at a time, not wholesale. If a page is a disambiguation page, it should *always* be suffixed with "(disambiguation)". This would make things so much easier using the "search" drop down menu that appears as you type, as well as urls that you may check before following, and mouse-over hovertext. I believe that there are number of other advantages, and no disadvantages. There is no primary topic for "nosedive", all topics derive from the word. The dab page should be at Nosedive (disambiguation), and nosedive should redirect to the disambiguation page. The disambiguation page is the natural place to find the wiktionary link, which suits perfectly the reader intent on going for the word.
The way to avoid personal bias is to look to the best quality sources, go to those sources, and see how they introduce the topic. Attempts to use the myriads of available statistics opens more doors for unconscious bias. --SmokeyJoe (talk) 07:09, 21 August 2018 (UTC)
Perfect analysis by SmokeyJoe. I agree that having disambiguation pages at base names is a culprit of making them unintuitive; if they were unambiguously labeled as navigation pages, they would be more homogeneous and simpler to understand - after using the search box, no one is surprised to find a navigation page with links to existing articles; but I agree that it may feel weird to follow an entry to a base name in the preview results of the drop-down search box, and not find an article there. Diego (talk) 07:44, 21 August 2018 (UTC)
Just a note re "malplaced". Currently, every dab page at the base title ought to have (and almost every one does have) a redirect from the corresponding title with "(disambiguation)". And if all primary topic dab pages were moved, then there would still be redirects at the base titles – in either case, if you type "X" in the search box then the drop-down suggestions will include both "X" and "X (disambiguation)". As for urls and mouse-over text of links, assuming these are within wikipedia, then they are already piped via the "(disambiguation)" redirects. – Uanfala (talk) 09:46, 21 August 2018 (UTC)
It's true that selecting the base title would still lead the user to the DAB page. But there's an important difference, which is that the target page would have a highly visible and huge header at the top saying ARTICLE TITLE (disambiguation), instead of the current DAB page title which is just ARTICLE TITLE. That alone should make it clear to the reader that they're not seeing an article about the topic. Diego (talk) 10:05, 21 August 2018 (UTC)
Do you think this makes a difference? Given that dab pages have an immediately recognisable layout that visually differentiates them from the articles, I'm not sure readers who land on a dab page will need to see the title of the page to know that they're on a dab page. – Uanfala (talk) 10:10, 21 August 2018 (UTC)
(edit conflict) P.S. And maybe, just maybe, it would also help if we changed MOS:DCAT to enforce placing the {{disambiguation}} template at the top, rather than the bottom of the page, so that it can actually be seen on long DAB pages. Diego (talk) 10:12, 21 August 2018 (UTC)
Not all readers are as used to the layout as we are. In particular, I'm not so sure that there's a clear visual difference between DAB pages and list articles, not one that an untrained eye would spot at first glance. Consider this vs this as a quick example. Diego (talk) 10:25, 21 August 2018 (UTC)
A page that begins with a paragraph describing the event should probably be a broad concept article rather than a dab. Certes (talk) 10:48, 21 August 2018 (UTC)
Yes, probably. It didn't help to the thousands of readers we were having at that DAB page that particular morning, though, which had to use what we had right then. The point is that they definitely weren't noticing that the page was a disambiguation page rather than an article, so the distinction by layout alone is not that clear to many readers. Diego (talk) 11:02, 21 August 2018 (UTC)
What do you think of it:Madonna or pl:Madonna? Certes (talk) 10:48, 21 August 2018 (UTC)
Both have something that Madonna doesn't have: a message above the fold saying that it is a disambiguation page. I like that. Their visual design (and the icons they use) stand out a bit because it's different than ours, but we wouldn't have that problem (I mean, the icon at our DAB pages is a subtle grey). Diego (talk) 11:02, 21 August 2018 (UTC)
I've made (and then reverted) this fast edit for comparison, to give us an idea how it would look with the template at the top. Or, we could have it like this, after the lead sentence with the most prominent articles. Diego (talk) 11:12, 21 August 2018 (UTC)
• A primary topic needs long term significance? How about Anne Hathaway, an example from WP:D? Long-term significance is a factor to consider, and one that I believe is implicitly and more than adequately accounted for in page view counts and by the Google test, but it's not the only consideration. I don't see why topics not covered on WP, like the dictionary meaning of nosedive, should be considered when determining whether a given title is ambiguous, much less for determining what the primary topic is for a given title. --В²C 17:06, 21 August 2018 (UTC)
• A primary topic needs long term significance? - No, but it needs that there's no other long-term-significant topic competing for primacy. Anne Hathaway is a case where consensus has determined that usage (what readers were looking for) was the main factor in determining the primary topic, and the historical significance of Shakespeare's wife was not enough to override that.
I don't see why topics not covered on WP, like the dictionary meaning of nosedive, should be considered - Because disambiguation (including primary topics) is all about navigation, i.e. leading readers to the content they're looking for, not about content structure; we have categories for that second purpose. To create effective navigation, you need to take into account what readers know, not just what content we have.
Sometimes a hint saying sorry, we don't have anything about that, but you might try the shop next door is as important to provide adequate service as breadcrumbs to existing content, as it prevents the patron from going around, lost; a good librarian should know when to guide users out and stop looking for something that is not here. Diego (talk) 09:01, 24 August 2018 (UTC)
That would make sense if we were talking about topics that users reasonably and regularly would seek here. But if we identify any topics like that, then we should create articles for them. This isn't the case of articles we should have but just haven't created yet, in which case your approach would make sense. We're talking about non-encyclopedic topics, like simple word definitions, that nobody would reasonably even look for here. Nobody is going to wonder what the history of a nosedive is. It doesn't belong here. It's not a topic. We can and should ignore it, as if it does not exist at all, because, for our intents and purposes, it doesn't exist. We should not clutter WP with dictionary content. That's the point of WP:NOTADICT. --В²C 07:13, 25 August 2018 (UTC)
How do you know what topics users "reasonably and regularly" would seek? A major problem is that we don't have good tools to understand how our readers use the website. Until you try it, you don't know whether a word has an associated article at Wikipedia or not (being a non-English native, I definitely had to look here what a "nosedive" is). Also, your reasoning would explain why we don't have an article, but not why we shouldn't make it easy finding an external link to a sister site. Diego (talk) 17:35, 25 August 2018 (UTC)

─────────────────────────BTW, we do have the Descent a article which describes the history of nosedives, and I think it would be a much better target than the current obscure episode of a recent TV series. It certainly would have served me much better than the current PRIMARYTOPIC disposition, even though I'm a regular who fully understands how to navigate our website. I dread to think how a user with lesser knowledge of English, and who hadn't heard of the series, could have found about that content and understand the concept. Diego (talk) 18:06, 25 August 2018 (UTC)

Diego Moya, you make some good points. But there is a hint saying “sorry, we don't have anything about that, but you might try the shop next door”: that’s what the {{Wiktionary}} template is for. It should be on any dab page where the ambiguous term is defined in Wiktionary. Then the dab page can concentrate on guiding readers to what Wikipedia has. — Gorthian (talk) 21:10, 25 August 2018 (UTC)
Yes, that's what I was getting at. That's a good reason to place the DAB page at a prominent place more often than not, which is what Born2cycle wants to avoid. Arriving at a DAB page when looking for the bare word shows the Wiktionary link, while placing a PRIMARYTOPIC article does not, so it's much easier in the first case for the reader to find the definition of the word, or any article related to the meaning of the word but which is placed at an article with a different name (like the nosedive case). Diego (talk) 22:25, 25 August 2018 (UTC)
, the process to determine which topics users seek "reasonably and regularly" is not perfect but nothing novel. It's about the same as determining whether we should have an article about a topic, which WPians have been doing since WP launched. It's okay to leave pointers to external sources where appropriate, but we should not rearrange our titles to make it easier to find external sources at the cost of adding more clicks to users trying to get to topics we do cover, which is exactly what considering external uses in determining primary topic does. --В²C 19:56, 27 August 2018 (UTC)
-
Also, the page view stats at Descent (aeronautics)#dives are dwarfed Nosedive stats. All of the evidence indicates the interest in the episode is far higher than in any other use. --В²C 21:05, 27 August 2018 (UTC)
That's just if you consider exclusively "recent usage" as "all of the evidence". However if you consider content published in reliable sources (which is what we do to determine notability), the aviation maneuver is prevalent. The consensus is to consider all the information published over time and not just spikes of current trendiness, because mere transient popularity is not a good proxy of overall interest, and it's too prone to bias favoring a subset of readers that would leave all the rest out of the picture (in this case, spectators of the TV series, which is targeted at a very specific demografics of western technologically educated audiences). If you cater to that subset because they're currently actively looking for the chapter and temporarily appear higher in search trends, you're making a disservice to all the other classes of readers, who will be interested in the topic with the majority of historic coverage.
We determine which topics to cover by looking at what other people has written about in a reliable way, and then excluding all the sources that we dont't think are providing an encyclopedic treatment and choosing the subset of all that information that we want to cover. But readers care about finding information, they don't care about what we want or don't want to include in the project. If we only assess the types of content that we want to include in the encyclopedia for determining primary topics, we are distorting the amount of coverage by third parties by attending to just those that write in a style we can use, and we are re-arranging our articles in a way that is detrimental to what readers want to know about, by establishing navigation according to content curated to our interests, not those of the external world.
Therefore, of course we should make it easier to find such external content that exist but we've decided not to use, yet is probably as interesting to readers as what we happen to collect; it's only fair that, if we decide to exclude some types of information from our project, at least we let our users know about that decision and guide them to other places who do cover that information. Diego (talk) 22:45, 27 August 2018 (UTC)
-
That said, we can accomodate the fact that there's a significant amount of people looking for the series article. We do that by establishing that such high interest means that there's no primary topic, because two different concepts are competing for mindshare; therefore placing a useful disambiguation page that let readers find their way, instead of just having the historical concept at the base title, as would have happened without the spike of interest for the TV show. Diego (talk) 22:51, 27 August 2018 (UTC)

### Arbitrary break

• Born2cycle is back on his drive to minimize title length for frequently viewed articles. It has been his sole ambition for his entire Wikipedian career. It necessarily means doing away with "long term significance" in favor of usage as measured by page-views. It is entirely a misguided ambition, as it has no basis in making a better product for the readers, and it is at odds with the function of an encyclopedia, which is to collect all information and to organise it in a logical fashion.
With nosedive, he has cherry picked an extreme example of contrast between long term significance and page-views. One is the highly angled forward descent of an aircraft, covered both in a section of an aeronautical article and at Wiktionary, the other is a single episode of a popular TV show. Long term significance should trump because every fan of the TV episode knows what a nosedive is, the knowledge of the meaning of the word is a prerequisite to understand the them of the episode, but of the set of people interested in the aeronautical topic only a very small proportion would be fans of the TV series or otherwise interested in the single isolate episode.
Accordingly, I think we need to define "Primary Meaning" alongside "Primary Topic", where Primary Meaning includes generic concepts and common words regardless of there being a current article on the topic. It is important to prevent astonishment to the reader when they think they are following the generic meaning of a word and are taken to an unexpected niche, albeit high page view, article. "Primary Topic" should have an exclusion where the word that would be used as the title does not match the Primary Meaning of that word.
Further, as I have frequently noted in RM discussions, without objections except by those who argue that the rules include no mention of this, commercial topics should have to meet a higher bar to be afforded Primary Topic status. The driver for this is the importance of WP:NOTPROMOTION. Commercial products are typically named with a strategy of seeking a catchy name. Commercial topics also come along with insidious Search engine optimization tricks, increasingly if not already totally, automated tricks. Wikipedia should be resistant to this. Largely, largely undocumented, it already is. It has been explicitly consider in many cases. Windows passes, and Apple fails, for example. Nosedive should definitely fail. It is a commercial product, realized with a flurry of promotion, lead episode of a series that the Netflix needs to advertise to get subscriptions, and it surely has artificially boosted ghits, millions, which accompany a burst of low brow fan hype in popular media, nothing scholarly.
I also think User:Born2cycle needs to be topic banned to prevent continued relentless agitation at obscure articles, seeking to advance his battle for algorithmic titling decisions. It is disruption. It distracts other editors from doing useful things. It is not in the interested of improving the encyclopedia.
--SmokeyJoe (talk) 01:56, 28 August 2018 (UTC)
I'm not going to engage with you, except to say you have grossly misrepresented my motivations and behavior and that commenting about such matters on a policy/guideline talk page here is a blatant violation of WP:NPA. --В²C 02:15, 28 August 2018 (UTC)
I have studied Born2cycle's actions and articulated motivations for many years, and consider much, especially User:Born2cycle#Persistence_pays, to be unashamed disruption seeking to achieve an objective through wearing down everyone else. Perhaps there is a deeper motivation underlying the algorithmic titling and title minimisation objectives that I don't understand, but I have read his userpage and usersubpages, and don't find one. This is now quite topical, PRIMARYTOPIC vs NOTADICT is a worthy discussion point, all I posted applies. It needs a discussion here, but what it does not need is petty skirmishing in isolated RM discussions. We know he believes in "change at the article level contrary to guidelines", and I submit that such an approach, litigating titling policy opinions in isolated RMs on cherry picked articles is very disruptive to editors genuinely interested in those articles. These questions, IF they are important, should be approached through an RfC, not through RM skirmishes. --SmokeyJoe (talk) 03:46, 28 August 2018 (UTC)
I don't see anything disruptive about B2C, they (like me) are obviously very interested in titles, consider this comment which is linked from their user page. However with NOTDICT, I'd consider if the subject is properly covered by WP under any title, not just a word than can be used to refer to that topic, for example Size doesn't really cover the concept of "Big" but Hurricane is an alternative word for Tropical cyclone. Crouch, Swale (talk) 07:20, 28 August 2018 (UTC)
Are you familiar with "big"? Have you read Talk:Big (film) & Wikipedia:Move_review/Log/2012_June#Big_(film)? It was a lot of fuss, and precedent setting for a big film with big page views not being the Primary Meaning of "big". Born2cycle was not happy then, and in starting this thread he is still wanting to litigate exactly the same issue. After five years, an RfC is reasonable, but carrying the battles on endlessly in RM discussions at obscure articles is not, that would be disruptive to editors of those articles. --SmokeyJoe (talk) 08:30, 28 August 2018 (UTC)
Yes I read the discussions a few years ago. The major problem was that WP doesn't really cover the concept of "Big". However since that an article on Size has been created which doesn't really cover it but is better than before. There are a number of other topic so I'd say disambiguation makes sense. As you noted Bell was opposed, though I think that is a clear PT. Crouch, Swale (talk) 08:35, 28 August 2018 (UTC)
I did not start the Nosedive RM. I just weighed in like everyone else. Then I raised the larger issue on this much broader forum, merely using Nosedive as an example because it happens to be current and is the discussion which sparked me to raise this issue here. As my user page, FAQ and each of my comments on titles should make clear, my larger motivation is article title stability, the opposite of the disruption caused by having rules that are more ambiguous than necessary and creating pointless debate where none is warranted. A point of apparent difference I have with SmokeyJoe is that I reject the notion that more descriptive titles are helpful to users by any significant degree. The name of the topic is always enough for all intents and purposes of titles on WP, including for user needs, unless disambiguation is necessary. The moment you allow adding description beyond the name of the topic you're opening a can of worms, because there is no objective means by which to determine what is "descriptive enough". Allowing for term uses not covered on WP (or covered by an obscure section on a relatively rarely visited article and therefore a relatively rarely sought topic) in deciding primary topic to disambiguate the title of the clearly most likely sought topic is not helpful to users anyway. And the result of tolerance for unnecessary description/disambiguation in titles is the disruptive never-ending RM backlog. And, yes, changes on WP tend to be made one article at a time. For better or worse, WP works bottom up, not top down. If a consensus of participants agrees to move an article against guidelines, then it is moved, and that move itself, perhaps with a few other similar moves, becomes sufficient reason to update the guideline to better reflect actual consensus. Don't shoot the messenger. --В²C 16:09, 28 August 2018 (UTC)
B2C, if you read about Information scent, Tree testing and other topics in Information architecture, you'll learn that there are objective methods to assess whether titles are descriptive enough; namely by observing people read them and counting the number and types of errors they make when trying to navigate to their targets. It's a different thing that we don't have the tools to put those methods in practice... but I don't want to start a digression; just to point out that, according to the professional experts in how to properly lay out a website, they think that merely looking at the content you have is an awful practice, and you instead must look at what people intend to do with it (which quite often might involve looking for information that is not here at all). Diego (talk) 17:18, 28 August 2018 (UTC)
I get all that. WP is unique for a number of reasons. First of all, our title decisions really amount to choosing between Just The Name and The Name (plus some description). Whichever one we choose for the title of the article, the other typically redirects to it. Another decision we make is whether to put one of several ambiguous topics at a given title, or put a dab page listing all of the ambiguous topics at that title. These are very specific contexts in which to consider how people react and respond. And we do have tools that provide considerable information about people's behavior. Page view counts tell us very accurately how often people are looking at one topic relative to others. The Google test, especially when the search is narrowed to en.wp, leverages the observational tools Google has to tell us which of our pages is mostly likely being sought for a given search term. The bottom line is that all of the tools we do have at our disposal tell us quite clearly that people searching for "nosedive" are overwhelmingly looking for the TV show episode. I've never even seen the show, much less that episode. I try to be as unbiased as I can in making title decisions, going as much as possible by what these tools tell us about actual user behavior. And there's no evidence, anywhere, that users are coming to WP to search for dictionary definitions. --В²C 18:31, 28 August 2018 (UTC)
The thing is, we don't have no evidence that users want definitions because the tools we have are inadequate to provide such evidence. Neither Google nor page views can tell us anything about how many users search for a word looking for its meaning, arrive to a disambiguation page and then go to to Wiktionary to learn the word's meaning. Page views provide a measure of popularity exclusively, but as I've said, exclusively catering to what's trendy is a terrible way to design the navigation structure without also taking into consideration other elements defining the meaning and cultural context of the term. We're not a media company, we try to be an encyclopedia, and the treatment we give to people outside of the mainstream latest craze matters; it's not OK to offer a dreadful experience to those looking for the educational yet less popular topic.
I'll confess, I know first hand that people look for definitions at the encyclopedia, because that's something I often do myself, having found that Wikipedia is a very good tool for that purpose. I use the search bar for learning the meaning of English words that I've never encountered before; and I believe it's likely that other non-native English speakers will be interested in the same usage, as well as English elementary and secondary students. Wikipedia usually provides a very good first approach to concepts that are completely unknown, by placing them in context with categories or the introductory catchphrase "In FIELD X, a NAME is...", and then the lede proceeds to illustrate the concept with examples and usage notes (which you don't get in a dictionary).
When using the encyclopedia in this way, it's a really awful experience to find the target page hijacked by some obscure pop-culture item that I've never heard before, but which happens to be slightly more popular with people across the pond than all the other minutiae sharing the same name. It's understandable and even beneficial when the pop item is really a well known landmark of the English culture, i.e. when it's really the primary topic that people undoubtedly identifies with the term even if it's not its original meaning; but not for every random music album, TV episode, low-budget movie or cleaning product brand, which is getting a slightly higher attention than the rest because of its recentism. We already have a reputation of being disseminators of products for the contemporary media and technological conglomerates; let's make sure that the only popular items occupying the base names and displacing the meanings of English words are those that deserve it. Diego (talk) 20:42, 28 August 2018 (UTC)
"Deserve" is another idea that floats around primary topic discussions. Primary-topic-ness isn't an award to deserving topics; it's a navigation service to the readers. -- JHunterJ (talk) 11:53, 29 August 2018 (UTC)
DAB pages are navigation services. PrimaryTopic status, where overzealously applied, is the opposite. Even when justified, it doesn’t help with navigation, google doesn’t rely on titles, people don’t type urls, wikilinks don’t care. PrimaryTopics, by removing clarity, precision, make the java search box autocomplete options more difficult. —SmokeyJoe (talk) 12:27, 29 August 2018 (UTC)
And of course no one is recommending overzealous application. Primary topic status is a navigation service too; when justified, it helps with navigation for the readership, which is why we do it. Putting readers at Earth (disambiguation) or Shakespeare (disambiguation) or Banana (disambiguation) instead of Earth, Shakespeare, or Banana would be the navigation disservice. -- JHunterJ (talk) 12:43, 29 August 2018 (UTC)
I think everyone opposing at Talk:Nosedive (disambiguation) is overzealously pushing for a PrimaryTopic status of a narrowly popular topic. —SmokeyJoe (talk) 13:11, 29 August 2018 (UTC)
Right. And I thing everyone supporting there is overzealously pushing for removing the primary status from the topic that would best serve the encyclopedia readership in favor of treating Wikipedia like a dictionary. -- JHunterJ (talk) 13:14, 29 August 2018 (UTC)
So which is it that makes you think Nosedive (Black Mirror) has primary status: you don't think that Dive (aviation) is a topic identified by the ambiguous term "nosedive", or you don't think it has historical weight that makes it compete with the popularity of the TV episode? I'm not as interested in your opinion as I am in the policy ramifications of your position; what I get from your position is that apparently, the topic which correspond to the common meaning of a word has its significance somehow devalued because WP:NOTDICT would apply in some way. Diego (talk) 13:53, 29 August 2018 (UTC)
You've got it backwards. Its significance in primary topic determination is not inflated because of its common meaning as a dictionary word. That is irrelevant in primary topic determination. What is relevant, especially in the context of this discussion about navigation aids for our users, is likelihood of being sought by users searching with "nosedive". --В²C 16:45, 29 August 2018 (UTC)

### Meaning of words in disambiguation

SmokeyJoe above makes an interesting point that I think merits being explored. When determining primary topic, often there are cases where either:

• the base name is a common word with some well-known meaning (what SmokeyJoe calls "primary meaning"),
• or the name of the topic with the most usage is a derivative from the topic with the most long-term significance.

As we often analyze these aspects in move discussions, I think we should acknowledge this fact and mention them in the guideline, adding them to the "aspects that editors commonly consider" (or at least the "Tools that may help to support the determination of a primary topic but are not considered absolute determining factors"); we already do this in a limited way for the second criterion. We could add some guidance on how they are used in discussions, and maybe explain the outcomes of when they've been found relevant, and how they affect decisions over what is the primary topic. Diego (talk) 09:19, 28 August 2018 (UTC)

What would people say the primary meanings of Bell, Settle, Steep, Wells, Bury, Unlikely and Bray are? Crouch, Swale (talk) 11:11, 28 August 2018 (UTC)
I don't know, but as a non-native English speaker, they are immediately useful to me, and at first sight they seem well placed. Bell is an obvious primary topic, being the direct meaning of one of the 2000 most common English words. Those which are not nouns are difficult to make primary; so if they don't have an obvious primary topic, a disambiguation page allows me to learn their meaning and overlook the list of articles we have about the term. I particularly like how Unlikely, which doesn't have a disambiguation page, gets to have the Wiktionary link right there at the top, even if we are at article space (although it makes me wonder if the album is primary over the comic, since Jeffrey Brown (cartoonist) gets more daily visits; isn't that a WP:TWODAB situation?)
And contrast Bray (a disambiguation page) with Hee Haw. In the second case we have an article with many more visits than the other articles sharing the title, and for which we don't have an article covering the common meaning; that looks like a good candidate for primary topic, unless we find a section that covers that particular onomatopoeia elsewhere. Diego (talk) 11:45, 28 August 2018 (UTC)
"Primary meaning" is a neologism for a concept for which there is no direct bearing on primary topic determination. The primary topic for a term may or may not reflect the "primary meaning" of the term. To the extent that primary meaning influences how likely users are to be looking for that meaning when searching with a given term is already accounted for in normal primary topic determination. No special consideration for "primary meaning" needs to be given. I see no reason to clutter the section with words about this. --В²C 18:18, 29 August 2018 (UTC)
But the common meaning of a word surely has historical significance, which is one of the criteria for primary topic, right? The meaning of a word as it's understood in English has historical significance unless it's a neologism. Therefore, topics covered by Wikipedia that match the meaning of dictionary words are notable topics with long-term significance, and they shouldn't be dismissed from PT assessment merely because their meaning is also found in a dictionary. Diego (talk) 18:44, 29 August 2018 (UTC)
The meaning has history, not historical significance (unless there's some encyclopedic coverage of the historical significance of etymology, philology, epistemology of the word. The topic of that meaning may or may not have historical significance, which is the criterion. Being a dictionary word is great for dictionaries, but Wikipedia is still not a dictionary. -- JHunterJ (talk) 19:25, 29 August 2018 (UTC)
And no one is suggesting that Wikipedia is a dictionary, so I still don't see how you want to make the WP:NOTDICT policy relevant to primary topic discussions. But as you've just agreed, if a meaning has a long-term history, the topic covered in Wikipedia which corresponds to that meaning may have historical significance, in special when it's a notable topic on its own; and we should assess how that history is relevant - because it makes long-term significance more likely than for topics which don't have such historicity. Diego (talk) 21:58, 29 August 2018 (UTC)
This is why I don't understand the point of long-term significance. The whole point of identifying primary topics is to arrange our titles in a manner that aids user navigation. If long-term significance causes us to send users to a page they're not seeking, we're hindering user navigation, aren't we? --В²C 01:21, 30 August 2018 (UTC)
Is it? The point of long term significance is the logic of titles. A short title implies generic coverage. For example, Science should cover the general concept, not something very specific called "science", like Science (journal). The point of titles is not to aid navigation in the ways of search engines, simulating primitive search engine functionality will work to a point but will necessarily be limited like a primitive search engine, as well as producing bad titles. Fundamentally, a title is the biggest text at the top of the page that describes the content below. If users are being sent (by what) to a page they are not seeking, then most likely they are using a poor search engine, or title are misleading, or the disambiguation page should be more prominent. Disambiguation pages would be more prominent in search engines and other lists if all disambiguation pages were suffixed with "(disambiguation)" and ambiguous basenames redirected to disambiguation pages. WP:MALPLACED was and remains a mistake, as discussed previously. --SmokeyJoe (talk) 01:41, 30 August 2018 (UTC)
WP Search works like this: You enter a term, click on Go, and, if there is an article (or dab page) with that title, it takes you there. The point of primary topics is to ensure that when users enter a term in that WP Search box and hit Go, that they're taken to the article about the topic they are most likely seeking, if the search term has one. If the search term has such a "most likely to be sought" topic, and we take them to an article about some other "historically significant" topic, or to a dab page, aren't we hindering the very user navigation we're trying to improve? If the topic they're most likely seeking is a TV episode, then it makes sense to have the name of that episode at the top of that article when we take them there, even if that title also corresponds to a common word or a topic with greater historical significance. The first few words of the intro handle that. --В²C 01:51, 30 August 2018 (UTC)
No, that is not how search works. Documentation is here: Help:Searching. I'm seeing the problem. In the default skin, there is a box containing the grey text "search Wikipedia", but it primaryily serves to autocomplete, not search. The autocomplete behaviors can be found in your account preferences under the (mistitled!) "search" tab. The Default (recommended) is: "Corrects up to two typos. Resolves close redirects"
This autocomplete is I understand a Java thing, which depending on device and connection, can be very slow and clunky. Often it is for me, so I rarely use it.
As you type, a list of possible matches drops down, initially quite a long list. Only at the very bottom, below a horizontal line, below the grey text "containing ..." can you, without explanation, invoke the real search.
I think this hiding / obscuring of the real search is really a bad idea.
But anyway, if you use the default autocomplete, it is better to have precise titles over most likely topics at basenames, because then the precise title will appear.
Nosedive, for example. If the episode were at "Nosedive (Black Mirror)", then that entry would appear in the list, even at the top or second I think. This would best serve all users. --SmokeyJoe (talk) 02:34, 30 August 2018 (UTC)
This is why I don't understand the point of long-term significance. The point is that we don't put an article at the base name merely because it gets more searches/it's more popular. It also needs to be the topic that is commonly associated with the term, with no other topic competing for the meaning, even if people are not actively seeking the other meanings at this time. That's why Madonna is a DAB, and consensus about this view is not going to change soon.
As for how this improves navigation: it's best for those seeking the historic meaning, it makes incoming wikilinks harder to miss the mark and easier to fix, and it doesn't hurt those looking for the popular topic as much as you say it does - these can nagivate it directly using Google or selecting the disambiguated title in the search box dropdown, which gives more hints as to which on of the several significant meanings is the one covered by the article. Diego (talk) 05:57, 30 August 2018 (UTC)
I think there are hints of acceptance of the notion that Madonna should be moved to Madonna (disambiguation), and Madonna redirecting to it. This would mean the the unqualified "Madonna" no longer appears in the drop down list, "(disambiguation)" would be displayed in the title line (currently whitespace), and readers won't have to guess between "Madonna" and "Madonna (entertainer)" when they are looking for the singer. --SmokeyJoe (talk) 06:19, 30 August 2018 (UTC)

### Dictionary words can impact PRIMARYTOPIC decisions

I think there is a a consensus that dictionary words *can* impact PRIMARYTOPIC decisions. NOTADICT is not a blanket rule for excluding dictionary meanings from consideration.

I think this soft wording is agreeable. Just because there is a dictionary word, it doesn't mean that there can't be a PrimaryTopic for a topic which is not the meaning of that word.

Examples from https://randomwordgenerator.com/

• Many words are not extant topics, but are defined concepts with multiple uses and derivatives, and should be disambiguation pages, eg: refund, exception, circumstance, brilliance, loop, stall. For these, the appearance of a new popular creative work, like a song, or a book, should not easily displace the DAB page.

Cases where I might support a title change:

• Examples of word searches that I found astonishing, I think they should be DAB pages, were collect, abridge,
• Examples of DAB pages where I think there is a PrimaryTopic, or the DAB page should become a DABCONCEPT: conference

--SmokeyJoe (talk) 01:54, 5 September 2018 (UTC)

All kind of crazy shit can and does impact PRIMARYTOPIC decisions. What's important however is what should affect PRIMARYTOPIC decisions, which goes back to why we even have PRIMARYTOPIC, which is of course related to why we have disambiguation and how we choose our titles. I note that SmokeyJoe cites no policy or guideline basis for his wish that dictionary words impact PRIMARYTOPIC decisions.
It's important to distinguish dictionary words for which there are encyclopedic topics considered sufficiently notable to have an article on WP from those that don't have coverage on WP. Smokey's first list of examples (reddening, et al), are mostly of dictionary words with meanings that have WP-covered topics. There is no dispute that words with dictionary meanings covered on WP should be given due consideration per the two PT criteria just like any other use on WP, assuming they are even ambiguous.
Speaking of ambiguity, most of the words in his first list are not primary topics as he claims, as they are not even ambiguous (primary topic by definition applies to ambiguous terms). Regardless, even if a dictionary word is ambiguous with other notable uses, of course its use is considered in PT determination of that term. There is no dispute about that. The dispute is about whether the dictionary word should be given weight due to being a dictionary word. In other words, should we have a third PT criteria for that? Or should we just stick with the current two?
Further, Smokey claims "words are not extant topics, but are defined concepts with multiple uses and derivatives". What does this mean? Of course words are not topics. Words refer to topics. The literal word "key" is not a topic - it refers to a variety of topics, none of which are considered primary. "Key" is not a single "defined concept". There are several defined concepts (aka topics) to which key refers, and each of those is a separate use of "key".
The bottom line is that that dictionary-word meaning of a given ambiguous term is just another use to consider in deciding which if any one of them is primary. It should be given equal consideration under the two PT criteria relative to the other use or uses. We seem to have consensus about that. --В²C 17:50, 7 September 2018 (UTC)
• "I note that SmokeyJoe cites no policy or guideline basis for his wish that dictionary words impact PRIMARYTOPIC decisions."
I note again that you seem blinkered, limited, by the wording the text on this guideline, and that this guideline has some long standing logical flaws. As a consequence, your logic is flawed.
You admit that words with associated topics count for reasons for displacing a primary topic. Good. Now consider that a reasonable reader does not know the exact line between these words, and other word that may, but do not, have coverage somewhere in some article. It is even unreasonable to expect that readers know Wikipedia should not be used for looking words. It is more reasonable to have common words, for which there may be a multitude of associated topics and subtopics, to redirect to DAB pages that include all the covered topics and subtopics plus the consistently and prominently located Wiktionary box.
Dictionary words should be given weight according to the rationalizations of editors. The guideline should reflect what editors usually decide. The guideline should not be used to contain reasonable arguments not directly couched from the guideline. Guidelines are imperfect, and this guideline has serious logical flaws.
"The bottom line is that that dictionary-word meaning of a given ambiguous term is just another use to consider in deciding which if any one of them is primary."
To my surprise, this is completely agreeable. It implies that NOTDICT is not a reason to discount another's argument, which is the reason for this thread, because that is what you have been trying to do.
"It should be given equal consideration"
Cut "equal". Human judgement is needed on levels of consideration.
"under the two PT criteria"
This is a subtly flawed reading of the guideline and its intent. The guideline does not list the criteria exhaustively. There are undocumented criteria that should and frequently do swing discussions. These include: Whether the audience of one topic is aware of the other topic; Whether one topic is etymologically derived from the other. --SmokeyJoe (talk) 01:11, 10 October 2018 (UTC)

## “John Collins” and “John H. Collins”

Anyone is welcome to opine at Talk:John H. Collins. — Gorthian (talk) 01:05, 24 August 2018 (UTC)

## Aegyptus (mythology)

An editor has recently created Aegyptus (mythology), which looks like a disambig page but it includes its own footnotes. I wonder if it should be combined with the older Aegyptus (disambiguation) or if the references would be better used in any of the connected mainspace articles. Thanks. --- 18:30, 27 August 2018 (UTC)

It's a set index article, so it should be moved to a set index title. -- JHunterJ (talk) 20:14, 27 August 2018 (UTC)
It's not an optimal situation to have a handful of entries confusingly spread across two dab pages (nevermind that one of them can (or has been) reformatted into something that some people here would say is not one). It's best to merge that into Aegyptus (disambiguation) and not worry too much about the footnotes. – Uanfala (talk) 20:43, 27 August 2018 (UTC)
Aegyptus (mythology) is the usual way of titling set index articles (they're not dab pages) about names of characters in Greek mythology. Sometimes there are more than a dozen distinct figures sharing one name. See Category:Set indices on Greek mythology or, just as one example, Clymene (mythology). There are probably hundreds of such articles. - Station1 (talk) 21:03, 27 August 2018 (UTC)
@Station1: ...and very often those WP:SIAs on Greek mythology and prehistory are a confusing-to-readers unhelpful mess. Yes, I do know about and have consulted DGRBM. Narky Blert (talk) 05:04, 30 August 2018 (UTC)
I don't disagree, but wouldn't combining them with dab pages just make things worse? Station1 (talk) 05:10, 30 August 2018 (UTC)

Based on Widefox in the section above complaining about the lack of many "(disambiguation)" redirects to disambiguation pages, I've initiated a request for this at Wikipedia:Bot requests#Create WP:INTDABLINK redirects. Thryduulf (talk) 15:17, 30 August 2018 (UTC)

Great Thryduulf! I don't think you believed me at the start, but glad we're making progress on agreed things now. Regards 15:23, 30 August 2018 (UTC)
@Widefox: It's not a question of not believing you - it's just that (disambiguation) redirects to disambiguation pages are not relevant to the discussion above. I initiated this only because you were expending complaining that nobody was fixing this problem than it would take for you to fix it. Thryduulf (talk) 10:01, 1 September 2018 (UTC)
I will still want to delete the redirects created for name articles that are currently mistagged as dab pages. There aren't many of those left but the "useful for readers" argument will not wash if the redirect is brand new. —Xezbeth (talk) 06:50, 31 August 2018 (UTC)
How many, handful or more than 100? 13:34, 31 August 2018 (UTC)
No idea, they're almost impossible to find besides just randomly stumbling across them. I'm just assuming there's not many left since I've fixed so many of them over the last ~6 years. —Xezbeth (talk) 16:17, 31 August 2018 (UTC)
This query finds 4561 pages X in Category:Surnames or Category:Given names which are the target of a redirect called X (disambiguation). 90% are surnames. If "name articles" meant something else, we can probably amend the query to find them.name Certes (talk) 16:49, 31 August 2018 (UTC)
If I just answered the wrong question, then PetScan for surnames or given names may be more useful. These lists includes many false positives, mainly real disambiguation pages having a People section amongst other meanings. Certes (talk) 16:58, 31 August 2018 (UTC)
Those aren't the ones that are hard to find. There have been many name lists with just a dab template and nothing else. —Xezbeth (talk) 19:26, 31 August 2018 (UTC)
Thanks for clarifying. If you can give any examples of such name lists, someone might be able to think of a way of searching for them. Certes (talk) 19:44, 31 August 2018 (UTC)
Xezbeth, what does "fixing" these redirects amount to? – Uanfala (talk) 20:50, 31 August 2018 (UTC)
One thing to watch out for is pages which are incorrectly tagged as {{disambig}} {{surname}} instead of {{disambig|surname}}. I've fixed dozens of those (sometimes by splitting a surname page out because the DAB page was getting unwieldy). (In my experience, {{given name}} problems are less common, by a factor of at least ten or twenty; perhaps because surnames are serious, but any fool can dream up a new given name which has never been used before and will never be used again.)
I've lost count of the number of disambig pages which I've recategorised as name pages (and vice versa, often name -> {{hndis}}). I gave up routinely WP:G6-speedying (disambiguation) redirects to pure name pages after a couple of requests were declined on the grounds that they "weren't doing any harm". I have better things to do than to try to educate WP:ADMINs (except for those few who I've reverted for creating a WP:INTDABLINK error by mis-editing a hatnote or see-also link by removing the {disambiguation) qualifier from a link).
Perhaps there is a case for a minor maintenance category? rather wordily entitled Category:Pages with (disambiguation) qualifiers which redirect to pages which are not disambiguation pages. I wouldn't search for candidate articles, but would cheerfully populate it whenever I fell across one. (I cycle through Disambiguation pages with links - 7th or 8th time through? - so I'm more likely to fall across such errors than most.) Narky Blert (talk) 02:01, 1 September 2018 (UTC)
Here is an example that I deliberately haven't fixed yet: Danesi. If a bot creates (disambiguation) redirects to every dab page, it would obviously include ones like this that shouldn't be dab pages in the first place. —Xezbeth (talk) 05:57, 1 September 2018 (UTC)
Why shouldn't that be a disambiguation page? It lists articles associated with "Danesi" - if we only had one article about someone with that name Danesi would redirect to it as {{R from surname}}, but we have multiple so disambiguation is needed. I can see the argument for replacing {{Disambig}} with {{hndisambig}} but a human name disambiguation is still a disambiguation page. Thryduulf (talk) 10:01, 1 September 2018 (UTC)
This is indication of just how fundamental the misunderstanding is. Danesi is a list of people who happen to have the same surname. A disambiguation is most emphatically NOT list of articles associated with a term. Surnames are a gray area in that in some contexts individuals are often referenced by the surname alone, hence the guidance at WP:NAMELIST. {{hndisambig}} would never be the right template to use for a list of people with the same surname (or for that matter a list of people with the same given name). Yes, to a limited extent, such lists share some similarities with disambiguation pages, but expanding the confusion between disambiguation pages and other types of pages doesn't really help anyone. olderwiser 10:21, 1 September 2018 (UTC)
The problem with that is that if I wanted to find an article about someone referred to in a source as "Danesi" with no knowledge of their first name, I would search for either "Danesi" or "Danesi (disambiguation)" if I thought it likely that the person I wanted was not going to be the primary topic - a list of people with the same surname functions as a disambiguation page. It is my experience as a reader that where there are multiple articles associated with the same term that there will be a page that disambiguates them, without noticing (or caring) whether that is technically a disambiguation page or not. Thryduulf (talk) 10:34, 1 September 2018 (UTC)
Searching for "Danesi" is sensible.Searching for "Danesi (disambiguation)" presumes some familiarity with the arcanum of Wikipedia editing. No one (except perhaps some Wikipedia gnomes) would do a Google or Bing search for "Danesi (disambiguation)". Why should we deliberately reinforce the confusion between disambiguation pages and non-disambiguation pages merely for the convenience of some experienced (but misinformed) editors? olderwiser 10:46, 1 September 2018 (UTC)
No, nobody (or at least very few people) would enter "Danesi (disambiguation)" into google, but very many people who have read Wikipedia have encountered pages ending in (disambiguation) - they're linked right at the top of many of the most popular articles for example and they do enter such search terms in the internal search engine and/or navigate directly to is (e.g. last night I navigated directly to Steve (disambiguation) when looking for Steve (atmospheric phenomenon) as I knew it wasn't the primary topic but didn't know what the article was titled) (this comes up nearly every time one is nominated at RfD, and has been explained in detail in the RfC above). I've also yet to see any evidence that this supposed confusion between dabs and SIAs or lists of people with the same name actually impeding anybody finding the article they want. What exactly is the harm caused? If someone is searching for "Danesi (disambiguation)" they are clearly looking for a list of articles associated with that title - whether that is provided by a disambiguation page, a set index article, a name page or something else doesn't matter. Thryduulf (talk) 11:39, 1 September 2018 (UTC)
Well, then the RFC is perhaps misleading. What it should be proposing is to eliminate the distinction between disambiguation pages and set indices (and perhaps other types of pages that some editors find convenient to use for purposes similar to disambiguation pages. That would entail adding the __DISAMBIG__ magic word into the other templates so that those other types of pages will show up as requiring disambiguation when links to them are inadvertently created. olderwiser 11:58, 1 September 2018 (UTC)
The RfC is explicitly not proposing to eliminate the distinction, because there is no need to do so and the distinction makes sense in at least some cases. All that is required to gain all the benefits for readers is to allow (not require) "(disambiguation)" redirects to pages that function as indexes to articles that are reasonable targets for a given search term, whether they are technically disambiguation pages or not. Thryduulf (talk) 12:28, 1 September 2018 (UTC)
No, that is the practical effect of what many supporters are arguing--that there is no functional difference between the types of pages so far as readers are concerned. So rather than dance around this, better to just be out front with it. olderwiser 12:39, 1 September 2018 (UTC)
Thryduulf Why shouldn't that be a disambiguation page? - Bkonrad is right - that is a fundamental confusion about the consensus at WP:D WP:MOSDAB and WP:SIA. Surnames are by consensus a generally tolerated invalid item on a dab page relegated to the bottom directly before the "Other uses" section and for larger numbers always split out into a surname article, such a page that is exclusively surname is never a dab. I agree with your sentiment that the distinction between SIAs and dabs may hinder navigation and addressing that would be more useful than proposing support of niche redirect search hack (by design a minority flow which is against the majority navigation route assumed by WP:PRIMARYTOPIC, so a niche search by niche users). 13:24, 1 September 2018 (UTC)
WP:PRIMARYTOPIC works exactly as it should do, doesn't need changing, and is not relevant to this search term. "(disambiguation)" searches are used (by many more people than you seem to acknowledge) when people know what they want is not (or is unlikely to be) the primary topic. With geographical place names someone searching for the city in Canada will search directly for London, Ontario rather than go via London. When other topics are consistently named, people will do the same thing - e.g. Esperanto language got over 1000 hits in August despite the article being at Esperanto. People use "(disambiguation)" though when don't know what the article is titled - I gave the example of Steve (atmospheric phenomenon) above, and see also everything in Category:Redirects from incomplete disambiguation. Yes, fewer people want to read about a book for children than a colour, but that does not mean that the non-primary topic is less valid or less encyclopaedic, that we should make it unnecessarily harder for people to find what they are looking for, force them to first view a page they know they don't want, or require them to know whether the list is a disambiguation page, an SIA or a surname page before having visited. If you want to remove the distinction between them, go ahead and get consensus for that, but be clear that this would be a completely separate discussion and is not required to resolve the navigation problems identified. Thryduulf (talk) 16:08, 1 September 2018 (UTC)
That long reply doesn't answer why you don't know disambiguation fundamentals as directly quoted (and it's pertinent - about SIAs and dabs) per WP:CLUE not in terms of rhetoric but in terms of his or her understanding of the established policies and guidelines of Wikipedia and of knowing what works and what doesn't.. 18:26, 1 September 2018 (UTC)
Danesi is correctly categorised as a {{surname}} page of interest to Wikipedia:WikiProject Anthroponymy but not to Wikipedia:WikiProject Disambiguation, along with thousands of other surname pages. I see no problem of any kind whatsoever here, except perhaps strawman in some of the preceding posts. Narky Blert (talk) 20:58, 1 September 2018 (UTC)
If set index articles have no practical difference from disambiguation pages, and if the MOS for disambiguation pages is there for the practical benefit of the readers, then set index disambiguation pages should follow the disambiguation style guidelines. The insistence on not following the style guidelines on SIAs was made because they were supposedly practically different from disambiguation pages. -- JHunterJ (talk) 12:46, 13 September 2018 (UTC)
Exactly. The elephant in the room is if some (class of) SIAs are just second class dabs. It's better to address that cause than layering a redirect hack on top of the underlying issue. 13:52, 16 September 2018 (UTC)
One of my bugbears is WP:SIA pages like Vostok (inhabited locality) (and I've seen several dozen pages similar to that). That isn't an SIA (a set of items of a specific type that also share the same (or similar) name) – that's a group of places which randomly happen to be in the same country and to have the same name (which is this case happens to be the Russian word for 'east'). That's {{geodis}} material. Springfield is a good DAB page; Springfield (inhabited locality) would be an exact parallel to Vostok (inhabited locality), and would be just plain silly. Narky Blert (talk) 20:24, 27 September 2018 (UTC)
Narky Blert Hmm, that's a longer list. There's a few of these (inhabited locality) in Russia SIAs, e.g. Pechenga (inhabited locality) is smaller, both are created by User:Ezhiki. I see no need for a short list like that to have, essentially a bad version of WP:DOUBLEDAB. It should be merged into Pechenga and thus flag up incoming links (Pechenga, Russia Konstantin Korovin). Is WP:INCDAB the way forward for these or just merge, merge started here Talk:Pechenga 12:23, 5 October 2018 (UTC)

───────────────────────── @Widefox: I agree with you on Pechenga, and have voted in support. If a DOUBLEDAB seems advisable, e.g. because a DAB page is getting too long for comfort, it should be done properly using a secondary DAB page like Pechenga, Russia (currently a redirect! with several bad incoming links) not an SIA. I've seen a lot of 'Placename, Iran' pages like that, and they work well.

I routinely add {{R from incomplete disambiguation}} and {{R from ambiguous term}} tags (among others) to redirects I fall across while fixing links to DAB pages. It only takes a second or two, and helps any future reader of those invisible pages.

If you want another horror, try Gold (compilation album), yet another member of Category:Disambiguation pages with (qualified) titles. Narky Blert (talk) 13:02, 5 October 2018 (UTC)

Yup, exactly. As for these, e.g. Vostok (inhabited locality), I'm doubtful "(inhabited locality)" is useful generally for an SIA or dab, unless there's a good argument for it? A country qualifier seems more useful in this case, and a dab rather than SIA seems more useful.
Well this is a bit perverse Gold (compilation album) (disambiguation). Suggestions? 14:04, 5 October 2018 (UTC)
That one would function better as a set index or dynamic list. It could also be merged (back?) into Gold (disambiguation) since it isn't that big. —Xezbeth (talk) 14:22, 5 October 2018 (UTC)
Agree a list, say SIA, as it's quite large for the dab. 14:44, 5 October 2018 (UTC)
Done. I requested G6 for the redirect Gold (compilation album) (disambiguation) but it was declined by User:Nyttend "The target page disambiguates several dozen compilation albums entitled "Gold")". It's an SIA. User talk:SoWhy I've just read the close #RfC: INTDAB links to non-dab pages, and I'm not sure if that close puts enough weight on the fact that the redirects are created solely as a technical dependent page per consensus at WP:DABNAME ...when a disambiguation page...This type of redirect is used to indicate any intentional links to the disambiguation page, ... (which seems more than just creation, but actual definition of this type of redirect existing to prevent erroneous links on dab pages - which never applies to SIAs, as they are lists WP:SIANOTDAB). In that context, the argument for them to be treated as a dependent page should be strong in itself, and the burden to change that on proposers. The question being if/why the redirects are/aren't explicitly marked as a dependent page, but a technicality that can and should be fixed. The close seems to invert the burden, which may be in line with the defaults for redirects, but against those defaults for dependent pages. So, given that the numbers of !votes seems slightly more for No (10?) than Yes (8/9?), I'm puzzled why the burden seems inverted and it isn't closed no consensus given the difficult balance of those two competing defaults, combined with no consensus for a new, secondary use as a search mechanism? 12:50, 8 October 2018 (UTC)

## Palaichori

What's the best resolution for new dab Palaichori? The article previously at that title has been cut and pasted to Palaichori Oreinis. The village website suggests that Palaichori is the term for the two adjacent villages (or perhaps the two parts of one village), so perhaps it should be a not-very-broad concept article rather than a dab. Suggestions or remedial action welcome. Certes (talk) 10:33, 7 September 2018 (UTC)

This history makes interesting reading. But unattributed cut and paste move of a long-standing multi-editor-edited page is not the solution. I suggest we need to revert the move and then tweak appropriately and make a proper WP:RM. PamD 13:40, 7 September 2018 (UTC)
Thanks, Pam. I've reverted and left Palaichori Oreinis as a redirect for now. The article can probably be split without too much controversy, as I've suggested to the editor. Certes (talk)

## Disambiguation in draft

I have a disambiguation page waiting review at Draft:Vantablack (disambiguation). I'm not sure if I went through the right venue to request disambiguation pages, but is someone able to review it? 2601:589:8000:2ED0:34D4:CDC1:9863:612F (talk) 21:21, 12 September 2018 (UTC)

I put it into the article space. Thanks for creating it! -- JHunterJ (talk) 12:49, 13 September 2018 (UTC)

## How many more page views constitute "more likely" and "much more likely"?

The criteria at WP:PRIMARYTOPIC includes the phrase, "much more likely than any other single topic, and more likely than all the other topics combined". One of the common ways this is determined is by looking at page views. I have three questions:

1. Given two topics, A and B, about how many more page views does A have to get than B to qualify as "much more likely" to be sought than B? I know there is resistance to specifying exact numbers (not sure why, exact though somewhat-arbitrary numbers are used successfully for much more serious issues in the real world, like speed limits, ages to drive, consent, drink, etc. - can you imagine how many more disputes there would be in the real world if real world rules were as wishy-washy as WP rules are?), but how about at least some ranges? Getting 1.1 time as many page views, for example, I think clearly does not qualify as "much more likely". But what about 1.5 times as many? Twice as many? Three times as many? At what point is it clearly "much more likely" to be sought?
2. Given a number of topics, how many more page views does one have to get than all the others combined to qualify as "more likely than all the other topics combined"? Isn't merely getting more page views (technically even just one more) than the total number of page views all the other uses get combined, sufficient to qualify as "more likely than all the other topics combined"?
3. If we can get consensus on these two questions, should we provide guidance at PT accordingly?

Thanks, --В²C 21:13, 13 September 2018 (UTC)

You need to stop obsessing about page views and start considering the other criteria. Page views are a useful way to help determine the significance of a topic, but nothing more. Apple is so obviously an apple that it doesn't matter how many page views the corporation gets. The page views are irrelevant.--Ykraps (talk) 23:10, 13 September 2018 (UTC)
In past move discussions I've used "ten times more visits" as the minimum threshold to start considering page views as a significant factor with respect to usage, and I was not the only one. The defining factor though is not the relative amount of page views with respect other pages, but the relative strength of usage with respect to the historical significance of the other articles. I.e. it's not enough that one page gets much more visits (see Madonna), it's also needed that the others don't have a competing claim of primacy by other parameters. Diego (talk) 08:45, 14 September 2018 (UTC)
Possibly unhelpful, but this is my observation: Page views don't necessarily indicate the reader found what they were looking for, there could be a multitude of people visiting the wrong page in some scenarios. If is a dab, what they click next is more significant. —cygnis insignis 08:53, 14 September 2018 (UTC)
I would usually assume "much more" would mean something like 90-95%. This came from Talk:Memphis (disambiguation)#Requested move 4 September 2018 where it has been argued that the TN city doesn't clearly meet either criteria. I would point out B2C's post here saying that where Birmingham, Alabama has been viewed 32601 times and Birmingham has been viewed 79197 times, that not being enough. But Birmingham in the West Midlands is the original and the usual "City, State" format probably deals with that and people interested in the Alabama city surely know that its named after the UK one. Thises views [[11]] show a larger margin but for Memphis being less relevant as the TN city is English speaking, unlike the city in Egypt. I would personally recommend that we change it to something like this:
• A topic is primary for a term with respect to usage if it is the subject sought 90% or more when a reader searches for that term.
• A topic is primary for a term with respect to long-term significance if it has substantially greater enduring notability and educational value than all the other topics associated with that term.

However we should take into account in situations where hatnotes would be enough, such as when there are only 2 or 3 subjects or when there are only 2 "main" topics. Crouch, Swale (talk) 08:55, 14 September 2018 (UTC)

A broad consensus is not possible. It has to be judged on a case-by-case basis, via WP:RM, WP:RFD or a talk page. Every ambiguous term has a unique set of articles with a unique set of characteristics that need to be considered. —Xezbeth (talk) 11:07, 14 September 2018 (UTC)
Yes it might be assessed up to a point on a case by case basis but a clearer guideline would reduce disputes and make assessment easier and reduce outcomes being based on who happens to be making the assessment. Crouch, Swale (talk) 11:17, 14 September 2018 (UTC)
If you think clearer titling guidelines are needed, read busywork and find something more productive to do. —SmokeyJoe (talk) 13:56, 14 September 2018 (UTC)
• Google search results are not WP:RS. Nor are page views.
"One of the common ways this is determined is by looking at page views." That statement is WP:OR, and is disqualified.
Never lose sight of why we are here! It's not about us, it's about the readers. Solutions do not need problems – especially solutions founded on over-literal over-rigid readings of the guidelines which overlook WP:IAR.
Which is worse? (1) A reader clicks and lands on a disambiguation page, and has to click again to find what they were looking for. (2) A reader clicks and lands on an ill-chosen WP:PTOPIC which confuses or misleads them.
I have an informal test for PTOPIC, which has nothing to do with ephemera like page views and search hits. How likely is it that a reader who knows of topic A also knows of topic B? If the answer is 'overwhelmingly', then B is PTOPIC; otherwise, it is not.
If you would prefer to sort out a disaster area rather than to count the angels dancing on head of a pin, I suggest that you look at the incoming links to Esplanade. Narky Blert (talk) 20:13, 17 September 2018 (UTC)
Very well put. Which is worse? (1) A reader clicks and lands on a disambiguation page, and has to click again to find what they were looking for. (2) A reader clicks and lands on an ill-chosen WP:PTOPIC which confuses or misleads them. I might cite that elsewhere.
And I also like your informal test for PTOPIC, always have, I think it's far more useful than page views, see User:Andrewa/The Problem With Page Views. But shouldn't it be symmetrical? What if it's also overwhelmingly likely that a reader who knows of topic B also knows of topic A? But if it's true one way but not the other, then agree. Which would make New York City clear P T of New York for example. Andrewa (talk) 13:56, 15 October 2018 (UTC)

## What is the purpose of WP:PRIMARYTOPIC?

What is the purpose of primary topic? We have (rather vague - see discussion just above this one) guidelines for determining primary topic, but we really don't say why any ambiguous name should ever be the title of any article. What problem does this solve? Why is this better than always have a dab page at every ambiguous base name as some seem to favor? Or is it even better?

The reason I ask is I think stating a purpose might help develop consensus about whether a primary topic exists in a given situation. So I'd like to hear what others think about the purpose of primary topic. Don't be shy about stating the obvious. Just because it's obvious to you doesn't mean it is to others. Thanks, --В²C 00:24, 2 October 2018 (UTC)

• Purpose? I think the main purpose was to make it easier on average for editors to wikilink. A thoroughly unworthy purpose in my opinion. I think nothing would be lost by any reader if Paris were located at Paris, France. --SmokeyJoe (talk) 04:15, 2 October 2018 (UTC)
• Well, that explains much. Do you believe making wikilinking easier is also the point of WP:CONCISION? —В²C 07:10, 2 October 2018 (UTC)
• No, concision is good advice for any message. It’s good for all writing. Minimise the words to convey the same information. Some go too far though, confusing concision with brevity. —SmokeyJoe (talk) 08:53, 2 October 2018 (UTC)
• I thought the main purpose was to get readers onto the article their looking for as smoothly as possible as well as avoiding surprise. Crouch, Swale (talk) 08:56, 2 October 2018 (UTC)
• Exactly. A major purpose of a primary topic is to take readers where they expect to go when they type that topic into the search box. If we moved Paris to Paris, France, what would we do with the title Paris? Redirecting to the city article that we just moved wouldn't achieve much other than changing the title displayed above the article: all wikilinks would continue to lead to their current destinations, so it's still PT by the back door. Moving Paris (disambiguation) to Paris might do more harm than good, because 90%[citation needed] of readers who type "Paris" would be ASTONISHed to land on a dab. We'd also get a plethora of links-to-dab to fix, because new editors (and those set in their ways) would continue to write "Durand was born in Paris". That's not just extra work for editors; it's inconveniencing readers until someone gets around to fixing it. I think we should use primary topics less often, and I often !vote for a dab to go at the base name when others see a PT, but they certainly have their place. Certes (talk) 09:11, 2 October 2018 (UTC)
• That’s criticism of MALPLACED, not support of PT.
“wouldn't achieve much other than changing the title displayed above the article”? That something is significant, but it is not all. It would also achieve precision in urls, hovertext, category listings, and any number of downstream uses. —SmokeyJoe (talk) 09:29, 2 October 2018 (UTC)
• SmokeyJoe, well, if the article at Paris was moved to Paris, France but Paris remained a WP:PRIMARYREDIRECT to Paris, France, that city would still be treated as the primary topic and its purpose would be served identically. The question here (in terms of your example) is what is the purpose of having the city at Paris (directly or indirectly) rather than having the dab page there? --В²C 15:37, 2 October 2018 (UTC)
• There is logic to PrimaryTopic, but getting readers to the page they want is not it. Now you are moving to a different question “where should dab pages be located”. Paris is a good example of a valid PrimaryTopic, as everyone who knows any Paris knows that Paris, France is a bigger topic, and so it is logical that the dab page should not be at the base name. —SmokeyJoe (talk) 22:21, 2 October 2018 (UTC)
• You believe getting users to the page they want is NOT what PT is about? Then how do you explain, ...much more likely than any other single topic, and more likely than all the other topics combined—to be the topic sought when a reader searches for that term? And what do you believe it IS about? Are you suggesting that for a given term X, only a topic with name X known by anyone who knows any X should qualify as the PT for X? Why does it matter whether everyone knows about it? What if everyone knows about it, but very few ever look it up? And how would you even know how many "know" about what? Using page view counts to determine how likely someone is to seek one topic relative to the others is far more useful and is completely objective. --В²C 23:30, 2 October 2018 (UTC)
• "You believe getting users to the page they want is NOT what PT is about? Then how do you explain, ...much more likely than any other single topic, and more likely than all the other topics combined—to be the topic sought when a reader searches for that term?"
I explain that as a very poor guideline. Who wrote it? Who is psychoanalysing what readers? Where is the issue of systematic bias, the fact that Americans have far easier access to fast devices and connectivity than Borneans?
"Are you suggesting that for a given term X, only a topic with name X known by anyone who knows any X should qualify as the PT for X?"
```Almost, but within reason.  Not "anyone", but "any reasonable group of readers"
```
"Why does it matter whether everyone knows about it?" Because it is not OK to be routinely ASTONISHing reasonable groups of readers with topics they have never heard of under titles that they expect to be a title for a topic they do know about.
"What if everyone knows about it, but very few ever look it up?" I think: Give up on what you think people might look up. Not only is that not reliable, it is not even data. Titles should be decided based on sources. A topic is only a local topic if the topic's sources have only local distribution.
"And how would you even know how many "know" about what?" Look at the the distribution of publications that are used as sources for the article. Give some consideration to missing sources, and add the missing sources before suggesting a new title.
"Using page view counts to determine how likely someone is to seek one topic relative to the others is far more useful and is completely objective"
No, it is not. --SmokeyJoe (talk) 00:49, 10 October 2018 (UTC)

• (edit conflict) Many topics are so clearly what 99% of readers are looking for that they will look for it at the name. 99% of people looking for information on Paris, France, will look for it at Paris because the other Parises are something people will not look for at Paris. That's why Paris has 202,628 pageviews in the last 30 days and Paris (disambiguation) has 3,303 (okay, that's 98.4% if you want to be picky). Making Paris the DAB will be a disservice to almost all readers, not to mention break thousands or millions of incoming links from external sites. Other examples needed? Okay:
Munich 104,517 views vs. Munich (disambiguation) 1,102 views
Berlin 146,025 views vs. Berlin (disambiguation) 1,405 views
Rome 150,422 views vs. Rome (disambiguation) 1796 views
etc.
As PRIMARYTOPIC makes clear, the purpose of the guideline is mainly service to the readers by providing the topic that is highly likely to be "the topic sought when a reader searches for that term". Regards SoWhy 09:24, 2 October 2018 (UTC)
What about Unlikely? are readers not more Likely to search for Probability when searching for "Unlikely", see that RM especially that related terms such as Certainly and Definitely work. Crouch, Swale (talk) 09:30, 2 October 2018 (UTC)
The number of hits to the DAB VS PTOPIC are interesting, see these views from this comment. Notice how the Lewis DAB page got only over 17x the views compared to 100x for some others. Crouch, Swale (talk) 09:36, 2 October 2018 (UTC)
The question was why do we have PTOPIC, not is PTOPIC always applied correctly. Many terms we use in guidelines and policies are necessarily vague but that doesn't mean the guideline is problematic. In the end, it's up to consensus to determine in which cases a DAB is preferable to a PT. Regards SoWhy 11:51, 2 October 2018 (UTC)
WP:PRIMARYTOPIC says:
• A topic is primary for a term with respect to usage if it is highly likely—much more likely than any other single topic, and more likely than all the other topics combined—to be the topic sought when a reader searches for that term.
I think that is sufficient. Do we really need to spell out that the reason we care what readers are seeking is that we want them to find it? PrimeHunter (talk) 16:35, 2 October 2018 (UTC)
PrimeHunter, based on the arguments I see in RM discussions almost every day that don't seem to recognize this purpose of PT, and some made above in this discussion, yes, I think we do have to spell out that the purpose of PT is to help readers get to the topics they are seeking. Not to mention how the "historical significance" criteria has muddied the waters of what you have quoted. --В²C 17:55, 2 October 2018 (UTC)

A currently active RM at Talk:Mario Beaulieu (politician)#Requested move 18 September 2018 may be relevant in that it posits that a comparison between two same-named regional (not national) politicians shows that because one has 17 times more views than the other, the one with more views should be the primary topic. Neither politician, however, has an international reputation, thus raising doubt as to whether a primary topic is called for.    Roman Spinner (talkcontribs) 19:04, 2 October 2018 (UTC)

"has international reputation" isn't a PT criterion. 17 times the views and indistinguishable historicality is a good indication of calling for a primary topic. -- JHunterJ (talk) 20:28, 2 October 2018 (UTC)
It is in practice, and it should be explicitly. An American niche fan topic, unknown outside the American fan base, should not be PrimaryTopic if there is a globally known less fanatic topic known by the same name. The fans will find their topic even if it has a slightly longer title. Page views are a good an easy indicator, but there may be reason to overlook this indicator. —SmokeyJoe (talk) 22:28, 2 October 2018 (UTC)
This gets to the heart of what I'm asking about. "An American niche fan topic, unknown outside the American fan base, should not be PrimaryTopic if there is a globally known less fanatic topic known by the same name." Why? This gets back to the purpose of PT, which is what I'm asking about. Yes, the "fans will find their topic even if it has a slightly longer title", but they will have to do so only after clicking through a dab page. Isn't that what we're trying to avoid? If not, then why have PTs at all? Why not just have a dab page there every time? See, PrimeHunter? This is why we have to spell it out. Let's not dilly dally around the apparently obvious. Let's be clear. --В²C 23:19, 2 October 2018 (UTC)
“Why?” is ASTONISH and meta:Introduction to Structurism (the encyclopaedia should have a logical structure). The fans will not need extra clicks to get to their precise (nb minimally precise) title, unless someone does something silly like follows MALPLACED and puts the dab page at a catchy basename. Where different groups may separately and reasonably think their different topics are both PrimaryTopics, it is most important that the dab page does not go at the base name. I am still yet to hear a single reason why all DAB pages are not better suffixed “(disambiguation)”. The PT discussions are distorted due to the MALPLACED policy error. An imperfect PrimaryRedirect is far less bad than to put either article under the basename title that google (and all sorts of other ways in) will take readers to the wrong page. —SmokeyJoe (talk) 23:30, 2 October 2018 (UTC)
You are also talking about a different case, at least. An American niche fan topic, unknown outside the American fan base, would still be PrimaryTopic if there is another less fanatic topic also not known globally by the same name. The case of "Mario Beaulieu" involves two topics with the same "fan base" (Canadian regional politics), one of whom vastly outstrips the other in usage. -- JHunterJ (talk) 15:49, 4 October 2018 (UTC)
JHunterJ wrote: "An American niche fan topic, unknown outside the American fan base, would still be PrimaryTopic if there is another less fanatic topic also not known globally by the same name". I disagree. If the other, less fanatic (do you mean less ghits/pageviews?), for example a Bornean niche fan topic of coincidental same name, exists, then its fans can be expected to be ASTONISHED if taken to the unrelated American topic. Hatnotes, for an example a hatnote at the American topic just for the Borneans, is an ugly solution, impacting the article, and not necessarily understood for by Borneans. If one group may be ASTONISHED, there is not PrimaryTopic. Both should be titled per PRECISION.
The Mario Beaulieus is a much less interesting case because the audience of one should be aware of the other, meaning not ASTONISH factor. However, one of them remains titled in violation of PRECISE. --SmokeyJoe (talk) 00:36, 10 October 2018 (UTC)
The titling isn't up to WP:D, but to WP:AT and the appropriate project naming conventions. And I disagree that fans of any niche topic will be astonished to discover that their niche topic isn't the primary topic for any give title, even if the primary happens to be a topic in some other niche. -- JHunterJ (talk) 12:15, 10 October 2018 (UTC)

The purpose of WP:PRIMARYTOPIC as a guideline is driving readers to an article they're likely to be looking for, but also not driving them to a topic they're unlikely to be looking for (that's why WP:ASTONISH is explicitly mentioned). That's a reason why page views is a poor indicator of primacy on its own, and why historical significance is an essential criterion to take into account.

When there are several split target audiences that may be looking for different topics, that one article is slightly more popular for one group does not provide any evidence as to what other demographic groups may be looking for. Someone recently mentioned "even if I'm not looking for the primary topic, at least I've heard of it before", and I think that's a good criterion. Diego (talk) 16:13, 4 October 2018 (UTC)

Paris? Wasn't he Helen's boyfriend? or a character in Romeo and Juliet?
IMO a WP:PTOPIC needs to be at least 90% and preferably 99% of all search requests. I see far too many WP:RM proposals based on marginal differences or on WP:RECENTISM.
Always remember why we are here. It is not to enforce rules. It is to help readers to find what they are looking for, with accuracy and certainty.
Hindu deity Krishna shares his name with Krishna (Malayalam actor) and Krishna (Telugu actor). I wonder how many of the incoming links to Krishna suggest that the deity (who, by my understanding, is dead) has starred in movies? Narky Blert (talk) 06:15, 5 October 2018 (UTC)
I'm working through those but there are probably only a few dozen bad links. Even in films, most links are to the original Krishna who is a popular character. I don't think I've yet found two with the same correct target; the first one was meant for Krishna (Kannada actor) who wasn't even on the dab. The most numerous fixes I've found in recent trawls are PresidentPresident (corporate title) (1644), Republic of ChinaRepublic of China (1912–1949) (970), AdventureAdventure film (443) and FamilyFamily (biology) (405). There are lots of bad links to Alcohol (meaning drinks rather than the type of chemical) but the best destination is controversial. Certes (talk) 10:33, 5 October 2018 (UTC)

Some very good points above. I have for some time been working on a proposal to deprecate Primary Topic, see User:Andrewa/Primary Topic RfC for my latest thoughts. In actual scenarios, it generally does more harm than good... perhaps always! Some of this is counter-intuitive, but when I actually work on examples, that's my conclusion.

I'm not ready to propose it yet, but if you'd like to help refine it, the place to go is User talk:Andrewa/P T examples and scenarios and of course User talk:Andrewa/Primary Topic RfC. Andrewa (talk) 01:00, 7 October 2018 (UTC)

This is exactly what I'm getting at. A minority but nevertheless many of the arguments I see in RM discussions imply that PT really has no purpose. This, PrimeHunter, is why I think we need clarification about the purpose of PT. The bottom line is how are readers best served when one enters an ambiguous term in the Search box and presses return, and the topic of one article is highly likely—much more likely than any other single topic, and more likely than all the other topics combined—to be the topic sought when a reader searches for that term? --В²C 20:53, 7 October 2018 (UTC)
Disagree that your bottom line is the bottom line. Also, your bottom line is far from objective, and suffers from biases.
A failing of erring on granting PT is that an ambiguous term becomes available in the autofill Go box.
A failing of MALPLACED is that it puts a DAB page on the ambiguous term. It is this MALPLACED old bad idea that I think has caused so many to want to be overzealous in grant PTs.
PRIMARYREDIRECT errors are minor compared to bad, PRECISE-failing titles. —SmokeyJoe (talk) 21:55, 7 October 2018 (UTC)
The fact that an experienced editor like you thinks the much older concept of PT is somehow supported by the much younger concept of MALPLACED is just another reason why the purpose of PT needs to be clarified. —В²C 20:21, 8 October 2018 (UTC)
Actually, I think your beef is with WP:DABNAME, upon which MALPLACED is founded. —В²C 20:29, 8 October 2018 (UTC)
Not quite, but close. There is a logic to PT, but the driver for many bad PT decisions seems to be MALPLACED / DABNAME. If the DAB page on the basename would cause people to unwanting load a DAB page, the solution is to title the DAB unambiguously. Why not? Getting people to the page they want is a reason to support more emphasis on PRECISE and RECOGNISABILITY. DAB pages on basenames fail both. —SmokeyJoe (talk) 21:29, 8 October 2018 (UTC)
There's logic to P T, but it's faulty. It's based on the assumption that having the article that the reader wants at the base name is going to make it easier for them to find it. It seems intuitively obvious that this is true, but unfortunately it's not. That's just one of the problems with P T as it is now, but if we can muster the evidence and get (I predict very grudging) consensus on that, then possibly the whole house of cards comes down.
Alternatively, there are a couple of related problems with disambiguation that could be fixed independently and the process might stir people's mental juices. Watch this space. Andrewa (talk) 22:38, 8 October 2018 (UTC)
Watching. Interesting for sure. I tend to agree that the logic for PT is flawed. Paris is a very strong contender for PT, yet no reader would be harmed if it were at Paris, France, with nothing at Paris. Google, wikilinks, autocomplete, never take readers to redlinks. If it must be blue (why?), it could redirect to Paris, France. PRIMARYREDIRECTs are fine, they don't force imprecise titles. Paris is strong for a PT because everyone multiple criteria support it. Page views. Long term signficance (which does not mean "oldest"). Does not derive from another important use. Everyone who has heard of another Paris should know of the French city. WP:PT would be much safer from astonishing anyone if ALL of these criteria were required. One, eg pagviews, others failing, is not good enough. --SmokeyJoe (talk) 00:21, 10 October 2018 (UTC)
Exactly. That would be a great improvement. But there seems no chance of it happening, we have tried many times. So my at first reluctant conclusion became, nothing lost by going for the more radical and far simpler option of deprecating the concept. But the more I developed this idea, the more attractive it became. It has surprised me how much it has going for it. And (at the risk of being boring) the most remarkable thing is, it's not to the readers' advantage to have an article at an ambiguous base name. It seems obvious that it is. But it's not. Andrewa (talk) 10:50, 13 October 2018 (UTC)
• Simplicity we could eliminate all primary topics, and use primary redirects. PT (without a redirect) is the simplest way to get a reader to the article, and similarly for writers. It's not just about navigation, but complexity. There may be reasons to increase complexity, but if search needs improving it's easier to improve search than make the structure more complex than needed (that's my gut reaction). 12:01, 9 October 2018 (UTC)
Interestingly, could be a good idea. PRIMARYREDIRECTs do not conflict with PRECISE. PTs do. --SmokeyJoe (talk) 00:24, 10 October 2018 (UTC)
Yes, it's a very good idea. It's a more complex solution than deprecating P T, and only solves half the problem IMO. But it does address an important issue, and would mean that every article was at an unambiguous name, so I'd support it.
It's actually a very good idea. It just mustn't happen. [12] Andrewa (talk) 03:22, 10 October 2018 (UTC)
Just to clarify, that wasn't a proposal, but highlighting how using primary redirects to eliminate all primary topics just makes things more complicated. It's just an unnecessary layer of indirection. I prefer simple, let alone stable namespace. Take one scenario - we shouldn't have to move Paris, just because there's a new film called Paris. Ambiguous titles are fine if we "WP:BALANCE" the probability. We trade off ambiguity for complexity. Any proposal needs to take any trade offs into account. 13:27, 12 October 2018 (UTC)

### Simplicity

Simplicity we could eliminate all primary topics, and use primary redirects. PT (without a redirect) is the simplest way to get a reader to the article, and similarly for writers. It's not just about navigation, but complexity. There may be reasons to increase complexity, but if search needs improving it's easier to improve search than make the structure more complex than needed (that's my gut reaction). [13]

As an RM regular, I can assure you that P T as it currently stands is anything but simple. See wp:NYRM for the specific example that eventually led to my wondering, is P T really worth it? Our eventual (and I hope permanent) solution was, DAB at base name. But this is arguably contrary to current policy, as New York City is probably the P T of New York. It took twelve years and some very hard work and bitter discussion just to move the state article away from the base name, despite consistent consensus that the state was not the P T. And it cost us several editors over those years. I would never have been involved myself had I known that NYRM2016 would fail as it did! It still astounds me, and was probably not in glorious hindsight worth it.

And that was the start of a journey for me. And the real breakthrough came when I finally questioned the common assumption that having an article at its base name advantages those looking for it. In fact it seems to me that the opposite is true. I'm gathering examples at User talk:Andrewa/P T examples and scenarios and it's early days yet, much analysis to be done before the RfC is ready. But input there very welcome!

In my current view, deprecating P T is a very desirable simplification! But as I said, still early days. Andrewa (talk) 19:29, 9 October 2018 (UTC)

Just in case this isn't clear - the end result is simplicity. The process to get there is a different question entirely. 21:43, 9 October 2018 (UTC)
A very important distinction, and I've phrased my post badly I guess if you see the need for that clarification. It's the end result that most interests me.
P T complicates things at all levels. But I suspect this is as counter-intuitive to others as it was to me. That's why I give the history above. Andrewa (talk) 23:45, 9 October 2018 (UTC)
OK. I was looking at PT afresh. The premise that PT complicates things needs reasoning, as using an ambiguous title for a most likely topic reduces the complexity to that when there's no ambiguity. It's pragmatic. In comparison with EB we seem to me much better organised, specifically for navigation with dabs and concise titles. From what I can understand, this the motivation comes largely from a concern about search? 12:53, 10 October 2018 (UTC)
(I've taken to using the abbreviation P T, see WP:PT for why.)
Agree that The premise that PT complicates things needs reasoning. And that's at User:Andrewa/Primary Topic RfC (and its three predecessors to which it links), and discussion at User talk:Andrewa/Primary Topic RfC would be welcome. Particularly, we might start a section there on the claim that P T simplifies things.
Done. Andrewa (talk) 21:39, 10 October 2018 (UTC)
...using an ambiguous title for a most likely topic reduces the complexity to that when there's no ambiguity... No. It simplifies things for readers who are (1) looking for that article and (2) unaware that other meanings of that title may be considered primary by others. For all other readers (including of course any who don't agree with us on what the P T is), it complicates things. Most of the damage can be addressed by redirects, as discussed elsewhere. But this isn't simplicity. The simplest method is, have a DAB (or a redirect to a more general DAB) at every ambiguous article title. But that's not necessarily the best method. Andrewa (talk) 20:04, 10 October 2018 (UTC)
The simple rule of treating all ambiguous titles equally does not lead to a simple outcome, no. We should put readers first, and PT discussions are irrelevant for readers. If the PT is wrong, then it can be fixed. The principle remains. Nope - it is right to give due weight to topics. It is that simple. Anything else is, by definition, undue weight. Equal weight is just a special case of undue weight - it guarantees that irrespective of how important the topic is, the title changes whatever new (ambiguous) article is created or retitled. That affects stability, expectation, and is the opposite of the simplicity of getting gold when inputting "gold". 11:59, 15 October 2018 (UTC)
Well put, and I'm sure others are thinking along similar lines without putting it nearly so well! It's a intuitively attractive approach, and the benefits are obvious. But what seems obvious is not always true.
Yes, it seems simple to regard some topics as more important and give them extra weight by giving them the article base names even if those are ambiguous, and disambiguating only the less important topics. It seems intuitively obvious that this is a good idea. And it worked well for the first few years of Wikipedia, when most of the articles to be written were about these important topics. But as the years have gone by, it has become problematic and not simple at all. I think this is important enough to reset the indenting. Andrewa (talk) 12:38, 15 October 2018 (UTC)

───────────────────────── Problem number one: Controversial cases in which the primary topic is not so easily determined. In the early days, these were few and far between, and a minor annoyance at worst, although we've always had some such as Macedonia. But as the years have gone by and the article count has grown, they have become more and more numerous. In a larger encyclopedia in which articles on most of the trivially primary topics (such as Mathematics and London) have already been written, it becomes more of an issue. It is no longer either the simple method or the simple outcome.

Problem number two: In glorious hindsight, it was never terribly logical. Intuition can be misleading! When we actually do some case studies, we find that having an article at an ambiguous name is not generally helpful. Intuition tells us that it's going to be easier for readers to find the article on Capitol Limited (Amtrak train) if we move it to Capitol Limited. In fact, the opposite is the case. See #A current case in point below. Andrewa (talk) 12:38, 15 October 2018 (UTC)

### Related issues

As promised. Get the brain juices going on these relatively simple proposals. And they might even give you a new perspective on P T. Andrewa (talk) 00:38, 9 October 2018 (UTC)

#### Unambiguous redirects

Whenever an article is moved from an unambiguous, disambiguated name to the base name, a redirect is created, and that is good. I'll call these unambiguous redirects.

But articles that have never been moved, that is they've always been at these ambiguous base names, typically have no such redirects. This means that, in a search results list, there may be no result that unambiguously identifies the topic to the reader. This is an obvious (or is it?) hindrance to readers. They must guess that the article that they want is at the base name, and certainly many will do this. But not everyone, particularly if there's a long results list.

We should as a matter of policy have an unambiguous redirect pointing to every article that is at an ambiguous name. (I'd prefer that we didn't have any articles at these names. But this will prevent nearly all of the damage, and at no downside that I can see.) Andrewa (talk) 00:38, 9 October 2018 (UTC)

Andrewa Titles, navigation and search are a bit of a trilemma. Redirects being a secondary issue. If the aim is to improve search, improving the software may help without having to touch titles and navigation. 10:00, 9 October 2018 (UTC)
Software modification may indeed be an alternative solution. But why would we even look for it? This proposal does not touch article titles, nor does it touch software.
Agree that Titles, navigation and search are a bit of a trilemma. Redirects being a secondary issue.
But it is a valid (but often ignored) principle of software maintenance that you fix the little problem that you understand, because then the big problem that you don't understand often magically goes away. This is a little problem. This trilemma is an enormous topic, and discussing it is unlikely to produce anything other than discussion.
So let us just fix the little problem that some readers can't see the article they want in a search results list. The problem and solution are both easily understood. The downside is...? Andrewa (talk) 15:35, 9 October 2018 (UTC)
• You're free to create {{R from unnecessary disambiguation}} redirects should you see any that should be created. You don't need to update policies or guidelines to do so, noting there are already several thousand of them (that have been categorized as such). -- Tavix (talk) 15:49, 9 October 2018 (UTC)
• Would you consider removing the bullet point from that post? It seems unnecessary, and likely to just make the stringing (Generally colons and asterisks should not be mixed) harder to follow. Andrewa (talk) 16:24, 9 October 2018 (UTC)

You're free to create {{R from unnecessary disambiguation}} redirects should you see any that should be created. You don't need to update policies or guidelines to do so... True, but misses the point. The point I'm making is that these harmless, common and useful redirects should always exist. And ensuring that they do exist does require a change of policy. Andrewa (talk) 18:47, 9 October 2018 (UTC)

No, ensuring they exist requires editors to take the time to create them. No policy or guideline is stopping them from being created. -- Tavix (talk) 18:50, 9 October 2018 (UTC)
I'm afraid I think this still misses the point. Yes, wikignomes can already create them, and will if the policy is changed, but generally won't if it remains as is.
So the issue here is, are they a good idea? And if they are, then their creation should be encouraged by the appropriate policy, and it will then happen. Not overnight, but in due course. Andrewa (talk) 19:03, 9 October 2018 (UTC)
For redirects, WP:RCATs—not "policy"—are employed to explain the reason a redirect exists. One of these RCATs, {{R from unnecessary disambiguation}}, encourages the creation of the type of redirect you describe and explains why these are helpful redirects to anyone who views the redirect. Literally the only reason that they are not ubiquitous is due to the effort it takes to create them. If you think there should be more of them, please, be bold and start creating them. This is not a "policy" issue. -- Tavix (talk) 19:17, 9 October 2018 (UTC)
Good point. If we were to update that template's documentation to explicitly encourage creation of these redirects, that would be quite sufficient.
I don't see that it does so now, in fact the very phrase redirect from unnecessary disambiguation discourages them.
The disambiguation is, in terms of current policy, unnecessary. But the point I'm making is that the redirects themselves are useful, and not just for preserving incoming external links. And that's why I called them unambiguous redirects not redirects from unnecessary disambiguation. Andrewa (talk) 00:22, 10 October 2018 (UTC)
An alternative which I hadn't thought of is to have all articles at unambiguous names, and whenever a P T is agreed to exist, make that base name into a primary redirect. Good suggestion above (but there are other parts of this post with which I don't agree, see #Simplicity). Andrewa (talk) 03:14, 10 October 2018 (UTC)

#### What does "(disambiguation)" mean anyway

We should rename every disambiguation page to something that is normal, common, easily understood English.

The qualifier (disambiguation) is Wikipediaspeak, not English. A name such as Wave, list of articles would be far more helpful, particularly to newcomers looking at either a Google or Wikipedia search results list.

And there's nothing stopping us from creating redirects from such names, except that without a consensus decision it might be seen as disruptive. Andrewa (talk) 00:38, 9 October 2018 (UTC)

PS I'm not proposing that we deprecate the term disambiguation in Wikipedia documentation etc.. Just in page names in the main namespace. Updating the doco etc to eliminate the term would be arduous, unnecessary, pointless, stupid, and a few far less flattering terms. We all know what it means. Andrewa (talk) 00:48, 9 October 2018 (UTC)

The question is "helpful" - are there any metrics or evidence for useability? Ignoring disambiguation and dabs not technically being "lists", we're free to choose a different arbitrary identifier. "(disambiguation)" is 16 characters ", list of articles" is 18. There may be shorter ones "(articles)", "(multiple)", "(ambiguous)", "(list)" / variants without brackets. Considering we're currently struggling to delete newly created invalid (disambiguation) redirects, we'd have to keep both in use, so wouldn't any alternative have to be much more than a marginal improvement for that cost? If we decoupled the titles from the MW search, they could be translated in the search into human readable, which comes back to the central question of what is the COMMONNAME of disambiguation, disambiguation would indicate it is. 11:45, 9 October 2018 (UTC)
Replying to Widefox 11:45, 9 October 2018 (UTC):
Lots of good issues here, thank you!
But if we focus on elegance as we, the contributors, see it, then we tie ourselves in knots (and we're good at that). What is elegant to some is ugly to others. We need to focus on the reader... but even that is controversial, aaargh! Another knot in which we can tie ourselves.
Agree that The question is "helpful". But do we really need metrics or evidence for useability? Is there any doubt that (disambiguation) is our own local jargon, and would be better avoided?
Agree that dabs not technically being "lists" can (and I guess will) be made an issue, does it have any downside for the reader? What in terms if WP:IAR does improve Wikipedia mean?
Agree that "(disambiguation)" is 16 characters ", list of articles" is 18. There may be shorter ones "(articles)", "(multiple)", "(ambiguous)", "(list)" / variants without brackets. Do the extra two characters really matter, compared to avoiding Wikipediaspeak in article titles? But other suggestions welcome. I considered ,index of articles and just (index). Either would do. Some of your suggestions just seem to be changing to another local jargon term.
But disagree that disambiguation would indicate it is (ie is the COMMONNAME). Disambiguation redirects to the article on Word-sense disambiguation, a topic of Computational linguistics. See also Disambiguation (disambiguation)! There's far more chance that readers will understand the term disambiguation in its Wikipediaspeak sense than as the technical term it is in computational linguistics. But even better, use a term that is common English! And disambiguation is not. Andrewa (talk) 16:35, 9 October 2018 (UTC)
"list of articles" gives no indication that it's about different meanings. "X, list of articles" sounds like a list of articles about whatever topic the reader mainly associates with X. PrimeHunter (talk) 16:47, 9 October 2018 (UTC)
But it's not about different meanings, it's just about getting the reader to the right article. If they think it's a list of articles about whatever topic the reader mainly associates with X then that's better than a term they don't understand at all... and if they're looking for another topic that they don't mainly associate with X and can't see the article they want in the search lists, won't they give it a go? Rather than something they don't understand at all? Perhaps it's still not ideal and I'm keen to hear better suggestions. Andrewa (talk) 18:00, 9 October 2018 (UTC)
But disambiguation is not "a list of articles about whatever topic the reader mainly associates with X". And disambiguation is not "a term they don't understand at all...". Just because you think someone in theory doesn't understand it (despite all the evidence given to you otherwise), doesn't mean we should introduce all these issues where there isn't one in the first place. -- Tavix (talk) 18:08, 9 October 2018 (UTC)
Yes, the discussion here has been rather waffly and opiniated. Not sure how to get it back on track. Andrewa (talk) 18:18, 9 October 2018 (UTC)
The name of a disambiguation page is also seen by readers who are not looking for a specific meaning, e.g. in searches. If they click "X, list of articles" because they are looking for articles about the main meaning of X then they have been misled if they get a single link to the main meaning and many links to unrelated meanings. And like others, I question your premise that readers generally don't know what disambiguation means. PrimeHunter (talk) 18:23, 9 October 2018 (UTC)
Thank you, that addresses the issues here well! But perhaps often would be a better description of my premise than generally. And even that's too strong. Even sometimes would be reason enough to question whether there's a better identifier for these important pages. (The question then of the process to fix it, and whether it's even worth the effort, only becomes relevant if we have consensus that there is. And I admit it is not looking good.) Andrewa (talk) 00:09, 10 October 2018 (UTC)
• Here you go. It's a proper English word with plenty of usage outside of Wikipedia. -- Tavix (talk) 15:52, 9 October 2018 (UTC)
• In esoteric circles, yes. The "disambiguation" article should educate you on the word [14]... There is actually no such article, see below. And is the bullet point really helpful? See above. Andrewa (talk) 16:35, 9 October 2018 (UTC)
• It looks like you are creating a problem where there isn't one because you refuse to acknowledge that "disambiguation" is in fact a common English word. -- Tavix (talk) 17:11, 9 October 2018 (UTC)
• I respect your opinion that it isn't a problem, and that disambiguation is a common English word. But the evidence doesn't seem to me to support these opinions. Yes, it's in wiktionary. Exactly what does that prove? Andrewa (talk) 17:39, 9 October 2018 (UTC)
• Well... that it's an English word, not "Wikipediaspeak" as you claim. It's not even like it's a cryptic word! dis- "to remove or reverse" added to ambiguous "vague or unclear", with the -tion suffix to make it a noun, forms "a removal of vagueness or unclearness", which is precisely what disambiguation does. On the other hand, what is ambiguous is the proposal to replace "disambiguation" with "list of articles", which would signify any article related to the term, not simply articles with the same name—which is distinctly different -- Tavix (talk) 17:58, 9 October 2018 (UTC)
• Accepted that it's an English word, and apologies of my term Wikipediaspeak was understood to mean it's not English. It is, and even if it weren't previously our use of it would attest to it being English now, even if it were not in Wiktionary yet, and it is. And it was previously used in other very specialised areas. But not by the general readership, that's my point.
• The proposal is to replace (disambiguation), not specifically to replace it by ,list of articles. There may well be better alternatives. Andrewa (talk) 18:09, 9 October 2018 (UTC)
• Which simply isn't the case! Do you have evidence of anybody being confused by this word to the point where they couldn't get to what they were trying to find? -- Tavix (talk) 18:12, 9 October 2018 (UTC)
• What isn't the case? Yes, it would be good to gather evidence... either way... any suggestions as to how? Andrewa (talk) 18:20, 9 October 2018 (UTC)
• Well, there is no evidence that "disambiguation" is a confusing word for anyone, let alone enough people to the point where the cost-benefit ratio would be anywhere near appealing. If you posted links to people being confused by this word, that would be evidence. Until then, a proposal to alter hundreds-of-thousands of pages due to a theoretical problem is a non-starter. -- Tavix (talk) 18:33, 9 October 2018 (UTC)
• And if we had some links that did show people being confused by this word, then we'd have a case? I'm not quite sure how to gather them, but I'll have a go... provided that they would actually make a difference. Andrewa (talk) 00:13, 10 October 2018 (UTC)
• That should now read see above following this edit (which was mainly a good idea, but I thought if I did as recommended in that edit summary it would also cause other problems of stringing). I do not know why bullet points have been introduced here, they seem to serve no purpose other than to make the stringing hard to follow. Or perhaps that is it? Naw, AGF. But the wikilink I put in to wp:stringing doesn't seem to have helped. Andrewa (talk) 17:51, 9 October 2018 (UTC)
Yes, disambiguation is a redirect, fair point, but still my question being is there a more common name, preferably more concise? "(word-sense disambiguation)" and "(WSD)" are worse. "(disambiguation)" may be ugly-useful. One could even reduce it to a prompt for the user to reinforce that selection is needed "(?)" (note we have (?)), "(*)", or just "()". I'd avoid "index" and maybe "list" completely due to already having those. Changing the identifier may bring some marginal benefit for users, especially if they type it (do they?), but it's such a disruptive change and MW would need to at least cover the redirect of all "(disambiguation)" urls to the new identifier, which could alternatively be done already in the other direction i.e. "(?)" -> "(disambiguation)". My gut reaction is that it's good enough, we're probably stuck with it like QWERTY keyboards i.e. high cost/highly established with marginal gain, and that cost means we'd want to identify the gain, yes. (SIAs on the other hand, but I digress). 18:20, 9 October 2018 (UTC)
Is it really such a disruptive change? That seems to be the unsaid assumption above. It would IMO be quite painless... except for messy discussions such as the above! Why do I bother... (;-> Andrewa (talk) 18:25, 9 October 2018 (UTC)
The pain may be worth the gain, but until the gain is identified, it's an assumption that different is better. I see growing desire to have something better for searching/navigating, and our navigation assumption about PT -> dab -> article may not be the major navigation path or that useful nowadays? Stats anyone? What's coming with MW/WMF? 18:41, 9 October 2018 (UTC)
I think I provided a case that deserves an answer and hasn't had one... although I now see that I did say Wipediaspeak not English and stand corrected on that. What I was trying to say was, to the contributors that term is fine, but to the general reader it's not obvious what it means. Is that clearer now?
And I still think that the pain is minimal. And it's not change for change's sake. There is an advantage in using page titles that the average reader understands easily, and particularly so with pages such as DABs which, by their very nature, are frequented by those who don't know what the page they really want is called. (Do I really need to look for evidence of that?) Andrewa (talk) 18:57, 9 October 2018 (UTC)
Info cf. Encyclopedia Britannica 1. doesn't have dabs 2. has only one passing mention of "disambiguation" 3. has longer titles 4. relies more on search 5. seems worse 19:33, 9 October 2018 (UTC)
Interesting. I don't think anyone was suggesting that we do away with DABs. I'm actually suggesting that we should make them easier to find. Andrewa (talk) 00:02, 10 October 2018 (UTC)
We should aim for the exact opposite - getting dabs out the way as much as possible, as they only a stepping stone to what the reader actually wants. If we had more information we wouldn't need them at all. 13:03, 10 October 2018 (UTC)

───────────────────────── Agree that we should get dabs out the way as much as possible. But disagree that this is the exact opposite. In fact my other relatively simple (famous last words) proposal aims to do exactly that... make it more probable that a reader will recognise a link to the exact article they want, and so avoid any need for them to go to the DAB.

But some readers will want to go to the DAB, for whatever reason... otherwise as you say, why have them at all? And for these readers, it's an advantage to have the DAB at a more recognisable name. Andrewa (talk) 19:33, 10 October 2018 (UTC)

I'm not really following make them easier to find and get dabs out the way as much as possible, but I presume this is a mix of search, navigation, and link recognition. In search, dabs could be used by MW to prompt users for the selection of article, thus avoiding the dab navigation step completely. Combined with auto-generation (in theory), it could be completely handled by MW, as well as adding the hatnote (for some but not all cases). 18:31, 11 October 2018 (UTC)
Well, get dabs out the way as much as possible was your suggestion.. and I took it to mean, it's far better for a reader to be able to go straight to the article they want than to need to look at a DAB first, and I agree. Did I misunderstand you?
But as I said, some people will (for the moment at least) still need the DABs (and otherwise why have them) and so (as with every other page) the more recognisable the page name is, the better... because a recognisable page name makes the page easier to find. Am I missing something?
MW I assume is MediaWiki. Yes, it could probably be improved too. But in this case that seems to me to be a messy way of going about things. Andrewa (talk) 05:24, 12 October 2018 (UTC)
I assumed that get dabs out the way as much as possible meant: Get dab pages off basenames. A DAB page on a basename is ASTONISHING to anyone using the Go box autocomplete if they think their topic is the primary topic. Even if they are mistaken. This is where some may say they need to be astonished out of their ignorance. I think the DAB page should be suffixed with "(disambiguation)", so that the autocomplete functionality tells the person that they are about to choose a disambiguation page, even if the basename redirects to the DAB page. --SmokeyJoe (talk) 05:41, 12 October 2018 (UTC)
Yes Andrewa, that's what I meant - just status quo. I agree with your sentiment, I still don't understand the proposed change. Dabs are like Schrödinger's pages, we're dealing with uncertainty, but that collapses. Yes being more explicit about a dab not being an article may be helpful, but the namespace is a totally different question to the UI.
SmokeyJoe - I did not mean "Get dab pages off basenames". I do mean status quo as in WP:MALPLACED is good. This is back to the trilemma... having all dabs as MALPLACED just to improve the Go box? Does the Go box behave differently at present with MALPLACED dabs? As I said, isn't it better to improve MW than workaround a less good interface using redirects (if that works)? I think it doesn't help to conflate/tradeoff namespace/navigation for search/Go box. I wouldn't call dabs ASTONISHING out of error (a bug in the data), but more out of design (a feature, and one that EB suffers from by not having, forcing users to search) and only when we probably don't have enough information (else they get out the way per PT). The Go box does have enough info to treat dabs differently. It literally doesn't matter what the reader assumes, only what info they give us to get them to the right place, and what we give them in an interactive way at the Go box. A dab feature is not an ASTONISHING bug. Yes we're free to have all dabs as MALPLACED, but what does that achieve? 12:34, 12 October 2018 (UTC)
I confess I'm at a loss as to what is being discussed here and why. There's no proposal to eliminate DABs, so can we stop talking as if there were? There's no case for modifying MediaWiki, that's just asking for trouble (as is using the abbreviation MW which means something else). There's a misunderstanding (not by me) of what was meant by get dabs out the way as much as possible, but that seems to be cleared up, and we seem to be unanimous that it's a good idea. Andrewa (talk) 21:44, 12 October 2018 (UTC)
I'm not sure what this is if there's only one solution, MW is to be ignored when talking about search, and the problem isn't even well defined. 12:12, 15 October 2018 (UTC)

#### Wikipedia:P T

User:Andrewa Sorry I've only just read Wikipedia:P T. Instead of me adding hatnotes (c.f. Wikipedia:PT), can you explain what it is, as I don't get it. Should it be marked an essay/possibly moved? 13:40, 12 October 2018 (UTC)

I suggest discuss at Wikipedia talk:P T, probably in the existing first section Wikipedia talk:P T#Why this page. It's not IMO an essay, as no opinions are expressed, and I'm not quite sure what moving it would achieve, or where you'd move it, or what would take its place... I guess making it a shortcut to either the guideline or the policy would be best, but that defeats part of the purpose, which was to help people to find both the policy and guideline without cluttering discussions.
But a redirect to either would still fulfill the most important function of WP:P T, which was to avoid the messiness of WP:PT, which has at various times pointed to protection templates, WikiProject Portugal, Protected titles, and of course Primary topic most recently. It has been protected and unprotected, and see this edit for something quite worrying! Andrewa (talk) 14:56, 12 October 2018 (UTC)
Discussion is probably best here Wikipedia:Miscellany_for_deletion/Wikipedia:P_T. 15:50, 12 October 2018 (UTC)
Agree, now that you have proposed it for deletion (which you have every right to do) that's the primary discussion until the MfD is closed. Andrewa (talk) 19:40, 12 October 2018 (UTC)

### Scenarios and evidence

As I said before, I'm working on an RfC to deprecate primary topic (which I like to call P T for clarity but see Wikipedia:Miscellany for deletion/Wikipedia:P T). It seems to me that its purpose and benefits are not as obvious as I once assumed, and as many still do assume.

Let me try two scenarios, and ask everyone three questions:

• What would you do in this case?
• If what you'd do is different to what I'd do, why?
• If what you'd do is the same as what I'd do, do you think that others might do something different, and if so what and why?

This is again to get the mental juices going, and to provide me with input as to whether any RfC might have a chance, and if so exactly what that RfC would be. Andrewa (talk) 10:29, 13 October 2018 (UTC)

#### Scenario one

You want an article on wave as in physics, and you find links to two pages (or more, but two that look particularly relevant), one at wave (physics) and one at wave. I would click on the link to wave (physics). What would you do? Andrewa (talk) 10:31, 13 October 2018 (UTC)

• I would get annoyed. I think I should expect that wave is a very broad concept article probably covering some physics. I know there are different sorts of waves in physics. Wave (physics) is very likely overspecific, “physics” makes me think I'll get a page of diagrams and equations, as I have seen in some articles before. I’d probably open both, if working with the luxury of a multi-tab device with fast connection. If working with difficulty, I’d be wishing for a Wave (disambiguation) option, expecting a clear list of options on a short page with no heavy images. —SmokeyJoe (talk) 01:54, 15 October 2018 (UTC)

#### Scenario two

You want an article on wave as in physics, and you find links to two pages (or more, but two look possibly relevant), one at wave (disambiguation) and one at wave. There's no link to an article at a title such as wave (physics) which you recognise as the one you want, but you don't know what disambiguation means. I would click on wave. What would you do? Andrewa (talk) 10:34, 13 October 2018 (UTC)

• the first time I saw “disambiguation” I thought it odd, but quickly deconstructed the word to work it out. Whenever unsure what title I want, I go to the disambiguation page. I find disambiguation pages to be light and very helpful, often including things I had quite forgotten, if I ever knew, and always impressively articulated. I think the premise of “you don't know what disambiguation means” is true only very briefly. —SmokeyJoe (talk) 01:59, 15 October 2018 (UTC)

#### After two days

At the risk of arguing from silence, if nobody responds I'm tempted to conclude that everyone sees my answers as reasonable, and as reflecting what most readers will do. Or, is there a better way of measuring this? Andrewa (talk) 01:16, 15 October 2018 (UTC)

• I think you make a lot of sense. I do not follow everything perfectly, so I am not jumping in to sign of as in full agreement. WP:Silence exists, as a page, as a concept, for a good and necessary reason. Go to the next step. We are watching. Talk page silence means little. Edit the guideline. If anyone disagrees the onus is on them to say so, but only after you do something tangible. Talk page posts are not quite tangible. —SmokeyJoe (talk) 02:01, 15 October 2018 (UTC)

Replying to SmokeyJoe 02:01, 15 October 2018 (UTC) and not seeing any reason for the bullet...

Your replies above are very welcome. They raise a lot of issues that hadn't occurred to me.

You mention tabs, and mobile devices. The oldest version of WP:disambiguation currently in the database is this one from 2 February 2002, and it's not very informative. It doesn't speak of disambiguation at all, and might not have been called that either... we need to look further into the history to find that out. And its edit summary indicates that it's not the first version, but that earlier versions have been deleted in a database reorg at some stage.

But some of our younger editors were not even born in 2002. The Danger Hiptop, the first smartphone to have any impact outside of Japan, was released in 2002, so mobile computing as we now know it did not yet exist; The first release of Android was still six years in the future, in September 2008. Internet Explorer didn't adopt tabs until Internet Explorer 7 in 2006, the last major browser to do so admittedly.

The point is just, in many important ways, 2002 as seen by Wikipedians was a very different world to 2018. And it would be surprising if some of our principles weren't due for a rethink in view of this. Disambiguation in general, and Primary Topic in particular, look like good candidates for this. Andrewa (talk) 07:18, 15 October 2018 (UTC)

#### The point being

OK, I'm going to assume in the absence of any disagreement...

• Most readers, facing a choice between Wave and Wave (physics) and wanting an article on wave as in physics, will click first on Wave (physics). (They may then open another tab for Wave if their device facilitates this.)
• Most readers, facing a choice between Wave and Wave (disambiguation) and not having an article title that they identify as being the one they want, will click first on Wave.

If this is true, then it seems to me that clicking on the link to Wave (physics) should take a reader straight to that article, but that clicking on the link to Wave should take them to the DAB, and that this is the best setup regardless of any consideration of primary topic.

And that is the point of these scenarios. Comments? Andrewa (talk) 07:46, 15 October 2018 (UTC)

If all page views came via WP's built-in search box then I might agree, but we need to consider other routes in which the reader never sees the option "Wave (physics)":
• via typing "Wave" and hitting Enter without reading through a list of possibilities
• via an external search engine, having searched for "Wave" without adding "(physics)"
• via a wikilink, possibly added by an editor who assumed that Wave means what we all know it means so that's what the article will be about
• via an external link to WP's "Wave" page, either one which already exists or one added later without checking where it leads (because it's obvious)
For these reasons, I think we still need primary topics, though I agree that they should be used less often. Certes (talk) 12:20, 15 October 2018 (UTC)
Very good point, and one I had already investigated at User:Andrewa/The third draft regarding avoiding primary topic#How readers find articles (and it might even have been you who suggested this to me). And it changed my approach somewhat. My conclusion was, they all benefited from moving the policy away from use of ambiguous names, if this were to be done carefully.
And that means far more carefully than I first assumed, I admit that. There's no case for moving most articles currently at ambiguous names, and probably never will be for the vast majority of them. But avoiding that is surprisingly simple.
So agree that it's not just WP's built-in search box that we need to consider. See #A current case in point for just one other route that is similarly affected.
And agree that we still need primary topics, and my latest proposal is not to eliminate them. See User:Andrewa/Primary Topic RfC#Proposal and User:Andrewa/Primary Topic RfC#Scope.
And much of the same benefit might be achieved simply by raising the bar on P T. Two problems. One, exactly how far do we raise it? Two, how do we get consensus to do so?
(But in some ways I suppose my current proposal could be seen as raising the bar I guess. Which might answer question one! Is it too much to hope it might also answer question two?)
My conclusion has been that replacing an illogical rule by a significantly less illogical one is still not the way to go! But I could be wrong. Andrewa (talk) 23:12, 15 October 2018 (UTC)

#### A current case in point

See User talk:Andrewa/P T examples and scenarios#Capitol Limited and Talk:Capitol Limited (Amtrak train)#Requested move 8 October 2018, which may have closed by the time you read this. The move seems inevitable, as it should be under current policy.

Discussion is now moved to Talk:Capitol Limited#Requested move 8 October 2018 and closed as move, as expected. Don't know why the redirect creation was suppressed. Andrewa (talk) 22:16, 15 October 2018 (UTC)

But see also http://alderspace.pbworks.com/w/page/129510039/Capitol%20Limited which is the Google results list taken before the move... it looks perfect, does it not?

How exactly does this move benefit the reader? Isn't it at best a case of our following a rather pointless rule?

Which was of course the original question that sparked this whole section. Andrewa (talk) 09:35, 15 October 2018 (UTC)

This has now (correctly according to current policy) closed as move as expected. And also as expected, a Google of "Capitol Limited" now returns only the Amtrak train. All direct mention of our article on Capitol Limited (B&O train) has vanished from Google.

(And there's not even a hatnote from the Amtrak article to Capitol Limited (B&O train), just one to Capitol Corridor, operated by Amtrak in California, which is I guess very loosely related to both but doesn't mention the B&O train, run by the Baltimore and Ohio Railroad between New York City and Chicago via Washington D.C. and Pittsburgh, at all. But that's easily fixed.)

The challenge: This has obviously made Google less useful (understatement perhaps) for those looking for the B&O train (discuss if you disagree). But exactly how has it improved Wikipedia? Apart from compliance to a rule which, in this case at least, was quite possibly counterproductive?

It has unimproved Wikipedia. And there is no benefit to counter this unimprovement. Is there? What am I missing? Andrewa (talk) 23:02, 15 October 2018 (UTC)

• The move of Capitol Limited (Amtrak train) to the basename has further obscured the old Capitol Limited (B&O train). The new article doesn't discuss the history of the name, or inform readers that there was a previous train of the same name. For someone looking for the older train, confusingly there is early mention of "the other" in the lede sentence, but referring to something else entirely. So, I added a hatnote. So, now, instead of a PRECISE title, there is a short ambiguous title with a lot of title whitespace, and more hatnoting, hatnoting that is distracting to the majority who don't care, and not even shown for many depending on their device. So Google has noticed? The old page has less prominence. Fewer will find it. Google will notice. Pageviews will decline. This is a self-reinforcing bias. I think WP:PRECISE needs a thorough thrashing. Cut the lede word "usually". Cut the off-point blather after the first sentence. Cut the trailing backward off-topic clause. Cut the unhelpdul and odd"topical". Yields: PRECISE: "Titles should be precise enough to unambiguously define the scope of the article". --SmokeyJoe (talk) 23:52, 15 October 2018 (UTC)
• (Still not sure how best to respond to your mixed indents, but otherwise) Very well put! Lots of downside. Still interested to hear of any upside. But I'm expecting a deafening silence. And it raises some other good issues.
• Support "Titles should be precise enough to unambiguously define the scope of the article". But wouldn't this bring it into direct conflict with WP:P T, and perfectly into agreement with User:Andrewa/Primary Topic RfC? Because, that's exactly what I'm proposing there, with a plan of action to achieve this with a minimum of effort and inconvenience. Or that was my intent, anyway.
• Move was a good close (in theory... it was bungled in practice, I'm discussing that with the page closer). There's no grounds for MR. None of this was raised in the discussion, I considered whether it was pointy of me not to chime in but even if I had there was consensus to move IMO. The move was based on policy, I'd have needed to invoke IAR to oppose and IMO I can't validly do that until I've demonstrated some consensus for my concerns with WP:P T. And I don't think that has happened yet, but I'm hopeful it's not too far away. Andrewa (talk) 00:23, 16 October 2018 (UTC)

## Items only in other-language Wikipedias or Wikidata

I keep running across items that link to either a non-English Wikipedia (such as Alexander Nikolayevich Golitsyn (ru) on Alexander Golitsyn) or Wikidata. What do we do with these? Do the they require a blue link in English Wikipedia, like other red links? Leschnei (talk) 18:39, 8 October 2018 (UTC)

We have links to other projects in articles so I don't generally see why not on DAB pages. However maybe we should restrict to times when the missing article is notable, but I don't see why WP:DABMENTION can't be used also. Crouch, Swale (talk) 20:31, 8 October 2018 (UTC)
No per WP:DABSISTER Disambiguation descriptions should not be created for subjects whose only articles are on pages of sister projects... and WP:WRITEITFIRST. Comment out or create a stub is what I'd do. 22:14, 8 October 2018 (UTC)
Curiously, MOS:WTLINK seems to allow sister project links for dictionary defs, which I don't think I've seen. I suggest we remove it from MOSDAB as wiktionary links seems to cover it. 22:18, 8 October 2018 (UTC)
Thanks Crouch, Swale and Widefox, WP:DABSISTER is what I was looking for but, for some reason, couldn't find. Leschnei (talk) 22:55, 8 October 2018 (UTC)
You mean, you haven't memorised WP:MOS??? I'm shocked, shocked!
Anyway, WP:MOS is inconsistent. MOS:DABOTHERLANG says, "For foreign-language terms, be sure an article exists or could be written for the word or phrase in question" (emphasis added). That implies that a DAB page entry is OK even if there isn't a WP:DABMENTION. (That guideline wording is feeble. (1) There are any number of articles on non-English Wikipedias which wouldn't survive WP:AFD if translated. (2) There are very many more non-English topics which wouldn't survive AFD in the home language. Articles could be written about any of them; whether they'd survive more than 7 days is another matter.)
IMO, WP:DABSISTER is incomplete, and WP:DABOTHERLANG is wrong. Both should be subject to WP:DABMENTION. (1) If a DAB page entry passes WP:DABMENTION, then an {{ill}} link adds information and helps other readers and editors, which is what we're here for. Among other things, it helps editors unify redlinks. (I cannot be alone in having turned redlinks into redirects to existing articles.) Alexander Nikolayevich Golitsyn (ru) is a good example. (2) If it doesn't, it points to no useful information in English Wikipedia, and should be commented out (better than deletion: it proposes a title). (I've probably broken that rule myself during multilingual searches, but plead WP:IAR.)
Wiktionary links on DAB pages should always go through {{wikt}}: any sort of piped soft link on a DAB page is just what we don't need; they're bad enough in articles. Narky Blert (talk) 19:40, 11 October 2018 (UTC)
Yes could be written isn't helpful and should be removed and replaced with WP:WRITEITFIRST, which is helpful. The full quote of MOS:DABOTHERLANG helps, as it qualifies ...Usually this means that the term has been at least partially adopted into English or is used by specialists. which implies it has to have relevance in English for en.WP. Practically, we should try to eliminate these grey areas so that editorial/notability judgement is minimised/eliminated from dabs and kept appropriately at the articles subject to WP:V etc by yes requiring a DABMENTION.
Regarding Alexander Golitsyn, I'd consider the Alexander Nikolayevich Golitsyn entry failing WP:DABRED, but easily solved by linking to House of Golitsyn which serves readers better than sending them to a sister project. Fundamentally, we must prioritise en.WP content over sisters to avoid WP:CFORK. Until a stub exists we just don't need the creep of judgement into dabs, together with the fundamental of WP:D reasonably likely. 10:25, 12 October 2018 (UTC)
Thanks for the thoughtful replies. It usually comes down to some version of 'strict adherence to the "rules" (such as they are) taking a back seat to what is best for the reader'. I should write that on the back of my hand whenever I sit down for a bit of editing. Leschnei (talk) 12:58, 12 October 2018 (UTC)
Generally MOSDAB (and WP:D) seem very handy for strict adherence which is aligned with readers. 13:34, 12 October 2018 (UTC)
I prefer the "{{ill}}; see [bluelink]" format to a redirect. Readers get the same information; and the article, being a redlink, is more likely to get written,
Deliberately writing a stub article when there's more information in another language feels like a cop-out. I've done it a couple of times; once because there were two bad links to a DAB page and the three corresponding articles in other Wikipedias were in languages which Google Translate doesn't understand. I did what I could by approximating to Russian.
Nevertheless, there is one Wikipedia which consists almost entirely of stub articles, and I applaud its editors. There are only two Wikipedias with over 5M articles, and Cebuano is one of them.
The list of Wikipedias statistics makes for some startling reading if you look at it closely. I know of one language with 830k speakers which has no Wikipedia at all (Mizo).
As for Wikidata, I consider it pestilential. Quality control is minimal, to put it mildly. DABlink problems in Wikipedia caused by blindly importing information from Wikidata are among the most difficult to solve. I know of only one editor who is able to tackle them, and it isn't me. In addition, I've had Interwiki links reverted because a Wikidata editor was unable to transliterate between the Roman and Cyrillic alphabets; and also on the ground that a WP:DAB in one language was not the same as a WP:SIA in another; even though the information overlap was huge, and despite the fact that every Wikipedia is entitled to set its own DAB and SIA rules. <sounding off /> Narky Blert (talk) 06:22, 13 October 2018 (UTC)
I believe that DABSISTER should be updated to support using {{ill}} for topics that would meet notability requirements for en-wiki. The template was created in 2013, while DABSISTER dates from 2004, when the risk would have been an interwiki bluelink to a foreign language and no redlink. 09:20, 15 October 2018 (UTC)
No - the crux is that notability question. For clearly notable a stub is easy, anything else editors should be able to WP:V in En.WP in English as that's easiest. En.WP is in a privileged position with sources, editors, readers hence articles. Those fundamentals aren't going anywhere to need DABSISTER changing, WP:WRITEITFIRST is the easiest for en.WP. This may be most clearcut with WP:BLPs and medical topics. 12:31, 15 October 2018 (UTC)