Jump to content

Wikipedia:Requested moves

Page semi-protected
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:Move request)

For the current list of potentially controversial requested moves, see § Current discussions.
"Wikipedia:RM" redirects here. For other uses, see Wikipedia:RM (disambiguation).
For detailed guidance on how and when to move a page, see Wikipedia:Moving a page.
Click here to purge this page
Shortcuts

Requested moves is a process for requesting the retitling (moving) of an article, template, or project page on Wikipedia. For retitling files, categories and other items, see When not to use this page.

Please read the article titling policy and the guideline regarding primary topics before moving a page or requesting a page move.

Any autoconfirmed user can use the Move function to perform most moves (see Help:How to move a page). If you have no reason to expect a dispute concerning a move, be bold and move the page. However, it may not always be possible or desirable to do this:

  • Technical reasons may prevent a move; for example, a page may already exist at the target title and require deletion, or the page may be protected from moves. See: § Requesting technical moves.
  • Requests to revert recent, undiscussed, controversial moves may be made at WP:RM/TR. If the new name has not become the stable title, the undiscussed move will be reverted. If the new name has become the stable title, a requested move will be needed to determine the article's proper location.
  • A title may be disputed, and discussion may be necessary to reach consensus: see § Requesting controversial and potentially controversial moves. The requested moves process is not mandatory, and sometimes an informal discussion at the article's talk page can help reach consensus.
  • A page should not be moved and a new move discussion should not be opened when there is already an open move request on a talk page. Instead, please participate in the open discussion.
  • Unregistered and new (not yet autoconfirmed) users are unable to move pages.

Requests are generally processed after seven days. If consensus to move the page is reached at or after this time, a reviewer will carry out the request. If there is a consensus not to move the page, the request will be closed as "not moved". When consensus remains unclear, the request may be relisted to allow more time for consensus to develop, or the discussion may be closed as "no consensus". See Wikipedia:Requested moves/Closing instructions for more details on the process.

Wikipedia:Move review can be used to contest the outcome of a move request as long as all steps are followed. If a discussion on the closer's talk page does not resolve an issue, then a move review will evaluate the close of the move discussion to determine whether or not the contested close was reasonable and consistent with the spirit and intent of common practice, policies, and guidelines.

When not to use this page

Shortcuts

Separate processes exist for moving certain types of pages, and for changes other than page moves:

Undiscussed moves

Shortcuts

Autoconfirmed editors may move a page without discussion if all of the following apply:

  • No article exists at the new target title;
  • There has been no previous discussion about the title of the page that expressed any objection to a new title; and
  • It seems unlikely that anyone would reasonably disagree with the move.

If you disagree with a prior bold move, and the new title has not been in place for a long time, you may revert the move yourself. If you cannot revert the move for technical reasons, then you may request a technical move.

Move wars are disruptive, so if you make a bold move and it is reverted, do not make the move again. Instead, follow the procedures laid out in § Requesting controversial and potentially controversial moves.

Requesting technical moves

Shortcuts
Shortcuts

If you are unable to complete a move for technical reasons, you can request technical help below. This is the correct method if you tried to move a page, but you got an error message saying something like "You do not have permission to move this page, for the following reasons:..." or "The/This page could not be moved, for the following reason:..."

  • To list a technical request: edit the Uncontroversial technical requests subsection and insert the following code at the bottom of the list, filling in pages and reason: 
    {{subst:RMassist|current page title|new title|reason=edit summary for the move}}
    This will automatically insert a bullet and include your signature. Please do not edit the article's talk page.
  • If you object to a proposal listed in the uncontroversial technical requests section, please move the request to the Contested technical requests section, append a note on the request elaborating on why, and sign with ~~~~. Consider pinging the requester to let them know about the objection.
  • If your technical request is contested, or if a contested request is left untouched without reply, create a requested move on the article talk and remove the request from the section here. The fastest and easiest way is to click the "discuss" button at the request, save the talk page, and remove the entry on this page.

Technical requests

Uncontroversial technical requests

More info may be needed here. This musician and his brother both have articles: Amaan Ali Khan (this one) and Ayaan Ali Khan, but the text in the two articles use "Khan" and "Bangash" in haphazard ways so it's tough to decipher birth names, stage names, matronyms, patronyms, or whichever is more relevant. Also, if this request is granted we would have to do the same for his brother too. ---DOOMSDAYER520 (TALK|CONTRIBS) 12:57, 29 October 2024 (UTC)[reply]

Requests to revert undiscussed moves

Contested technical requests

@Tazelaar Contesting as this likely needs a discussion to move forward. This wiki prefers English titles when possible, and we use the WP:COMMONNAME which is the name reported by majority of sources (again, preferably English sources, which are typically going to favor an English translation) - as for the translation, if the official translation is incorrect, it might be borderline editorializing if we try to correct it unless the correction we go with is also supported by majority of RS. At the very least, we would need to see sources or evidence of which title is the common name to move forward (and that would be most productive in a discussion where editors can bring forward opposing evidence that may have been missed.) ASUKITE 14:46, 25 October 2024 (UTC)[reply]
I concede that the content of the translation is a circumstantial argument, but an argument nonetheless. Tazelaar (talk) 13:01, 26 October 2024 (UTC)[reply]
Another circumstantial argument is that: "El patrón del mal" is a better recognisable title. Pablo Escobar was a drug lord, so the title could be used normally in a sentence. "El patrón del mal" is a unique title, more distinguishing from the "Pablo Escobar" article and Google results. Tazelaar (talk) 13:16, 26 October 2024 (UTC)[reply]
@Tazelaar; your technical request has been contested. If you wish to continue with the request, please use the "discuss" link in your request to open a full RM. Sennecaster (Chat) 19:28, 27 October 2024 (UTC)[reply]
@Jean-de-Nivelle It appears that Bedroom farce has about twice the pageviews of the play, so more likely, the alternative capitalization of Bedroom Farce should redirect to Bedroom farce instead. Raladic (talk) 21:27, 27 October 2024 (UTC)[reply]
@Raladic That's a good point, but wikinav analysis ([1][2]) shows that only 13% of "Bedroom farce"'s traffic is from search results, the majority coming from internal links, while over 60% of "Bedroom Farce (play)"'s traffic is from "other search" - if I'm interpreting the results correctly. Worth an RM, or would WP:RFD be a better course? Jean-de-Nivelle (talk) 10:57, 28 October 2024 (UTC)[reply]
Since I believe you'd still like to move Bedroom Farce (play) to Bedroom Farce, I'd say a RM is probably best to answer both the question of if it should be moved, or if not, if Bedroom Farce should instead redirect to Bedroom farce as a redirect from alternative capitalization and then just post a note at the lowercase article to let people watching that article know about the RM. Raladic (talk) 00:19, 29 October 2024 (UTC)[reply]
  • The Mexican → The Mexican (film) (currently a redirect back to The Mexican) (move · discuss) – The title should clarify that this is a film as per WP:PARENDIS. According to WP standards, parenthetical disambiguation is needed because the standard use of Mexican is not for a film, but a person from Mexico. Currently, there is a backward redirect MexFin (talk) 06:22, 28 October 2024 (UTC)[reply]
    Currently the 2001 film is set as the WP:PRIMARYTOPIC for the term The Mexican, which seems reasonable as it has a large lead in page views over the other four topics from the Mexican disambiguation page which are called The Mexican. I'm guessing the OP is suggesting perhaps the generic use of Mexican as defined by the other usages on that disambiguation page should be considered for The Mexican too, but we don't normally regard such titles as ambiguous if there's a clear primary topic for the exact term as specified. @MexFin: please start a full RM discussion if you wish to proceed. Thanks  — Amakuru (talk) 11:15, 28 October 2024 (UTC)[reply]
    Partial disambiguation of films is never uncontroversial. "The Mexican" is not the same as "Mexican". —⁠ ⁠BarrelProof (talk) 23:31, 29 October 2024 (UTC)[reply]
  • Thyia of Thessaly → Thyia (daughter of Deucalion) (currently a redirect back to Thyia of Thessaly) (move · discuss) – No sources call her "Thyia of Thessaly". Best to use the disambiguator "daughter of Deucalion", per sources such as Gantz's Early Greek Myth, p. 909, and Hard's Routledge Handbook of Greek Mythology, p. 741. Michael Aurel (talk) 14:35, 28 October 2024 (UTC)[reply]
    This is just standard naming for princesses and suchlike - <Name> of <Location>. I don't see a strong need to change it and the current tittle is WP:NATURALDIS.  — Amakuru (talk) 15:23, 28 October 2024 (UTC)[reply]
    I'm not aware of any source calling her a princess, so I don't know why we would use standard naming for royalty. Her only real significance is genealogical. In addition, as I said, I don't think there is any source which calls her "Thyia of Thessaly", so I don't see how WP:NATDIS applies, since the phrase is not what she is commonly called in English reliable sources. – Michael Aurel (talk) 17:05, 28 October 2024 (UTC)[reply]
  • FWD Tower → PCP Tower (move · discuss) – The building in question is actually known as Pacific Century Place. As written on the official website https://pcp-jakarta.com there is no record of the building ever being referred to as FWD Tower. This incorrect information is misleading and could cause confusion among users. Andres Arie Wibowo (talk) 09:26, 29 October 2024 (UTC)[reply]
    You say "PCP Tower" is the proper name but the article itself and sources you mention make no mention of "Tower"... they say either "Pacific Century Place" or "PCP Jakarta". Keep in mind Pacific Century Place Marunouchi also exists so maybe "Pacific Century Place Jakarta" is the best option and then Pacific Century Place as a disambiguation page; either way this should probably go to an RM. RachelTensions (talk) 14:48, 29 October 2024 (UTC)[reply]
@Andres Arie Wibowo There seems to be a reasonably large amount of RS calling it the "FWD tower", so this should probably be discussed in a full RM. Even the indonesian Wikipedia has had this as the name for many also known as names until some user decided to quietly change it. We go by what is the WP:COMMONNAME for article titles, this may not always be what the "official name" is for a place. Raladic (talk) 14:50, 29 October 2024 (UTC)[reply]

Administrator needed

Requesting controversial and potentially controversial moves

Shortcuts

The discussion process is used for potentially controversial moves. A move is potentially controversial if either of the following applies:

  • there has been any past debate about the best title for the page;
  • someone could reasonably disagree with the move.

Use this process if there is any reason to believe a move would be contested. For technical move requests, such as to correct obvious typographical errors, see Requesting technical moves. The technical moves procedure can also be used for uncontroversial moves when the requested title is occupied by an existing article.

Do not create a new move request when one is already open on the same talk page. Instead, consider contributing to the open discussion if you would like to propose another alternative. Multiple closed move requests may be on the same page, but each should have a unique section heading.

Do not create a move request to rename one or more redirects. Redirects cannot be used as current titles in requested moves.

Requesting a single page move

Shortcut

To request a single page move, click on the "New section" (or "Add topic") tab of the talk page of the article you want moved, without adding a new subject/header, inserting this code: 

{{subst:requested move|New name|reason=Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. You don't need to add your signature at the end, as this template will do so automatically.}}

Replace New name with the requested new name of the page (or with a simple question mark, if you want more than one possible new name to be considered). The template will automatically create the heading "Requested move 30 October 2024" and sign the post for you.

There is no need to edit the article in question. Once the above code is added to the Talk page, a bot will automatically add the following notification at the top of the affected page:

Unlike other request processes on Wikipedia, such as Requests for comment, nominations need not be neutral. Make your point as best you can; use evidence (such as Google Ngrams and pageview statistics) and refer to applicable policies and guidelines, especially our article titling policy and the guideline on disambiguation and primary topics.

WikiProjects may subscribe to Article alerts to receive RM notifications. For example, Wikipedia:WikiProject Biography/Article alerts/Requested moves is transcluded to Wikipedia talk:WikiProject Biography. RMCD bot notifies many of the other Wikiprojects listed on the talk page of the article to be moved to invite project members to participate in the RM discussion. Requesters should feel free to notify any other Wikiproject or noticeboard that might be interested in the move request, as long as this notification is neutral.

Single page move on a different talk page

Occasionally, a move request must be made on a talk page other than the talk page of the page to be moved. For example, a request to rename Wikipedia:WikiProject Articles for creation/Resources to Wikipedia:WikiProject Articles for creation/Reviewing and templates would need to take place at Wikipedia talk:WikiProject Articles for creation because the talk page of the project page to be moved, Wikipedia talk:WikiProject Articles for creation/Resources, is a redirect to that centralized discussion page. In this type of case, the requested move should be made using the following code: 

{{subst:requested move|reason=(the reason for the page move goes here).|current1=(present title of page to be renamed)|new1=(proposed title of page)}}

The |1= unnamed parameter is not used. The |current1= and |new1= parameters are used similar to multiple page moves described below.

Requesting multiple page moves

Shortcut

A single template may be used to request multiple related moves. On one of the talk pages of the affected pages, create a request and format it as below. A sample request for three page moves is shown here (for two page moves, omit the lines for current3 and new3). For four page moves, add lines for current4 and new4, and so on. There is no technical limit on the number of multiple move requests, but before requesting very large multi-moves, consider whether a naming convention should be changed first. Discuss that change on the talk page for the naming convention, e.g., Wikipedia talk:Naming conventions (sportspeople).

To request a multiple page move, edit at the bottom of the talk page of the article you chose for your request, without adding a new header, inserting this code: 

{{subst:requested move
| current1 = Current title of page 1 (this parameter can be omitted for discussions hosted on a page that is proposed to be moved)
| new1     = New title for page 1 with the talk page hosting this discussion
| current2 = Current title of page 2
| new2     = New title for page 2
| current3 = Current title of page 3
| new3     = New title for page 3
| reason   = Place here your rationale for the proposed page name change, ideally referring to applicable naming convention policies and guidelines, and providing evidence in support where appropriate. If your reasoning includes search engine results, please prioritize searches limited to reliable sources (e.g. books, news, scholarly papers) over other web results. You don't need to add your signature at the end, as this template will do so automatically.
}}
See also: Template:Requested move/extended blank

For example, to propose moving the articles Wikipedia and Wiki, put this template on Talk:Wikipedia with current1 set to Wikipedia and current2 set to Wiki. The discussion for all affected articles is held on the talk page of the article where the template is placed (Talk:Wikipedia). Do not sign the request with ~~~~, since the template does this automatically (so if you sign it yourself there will be two copies of your signature at the end of the request). Do not skip pairs of numbers.

RMCD bot automatically places a notice section on the talk page of all pages that are included in your request except the one hosting the discussion, to call attention to the move discussion that is in progress and to suggest that all discussion for all of the pages included in the request should take place at that one hosting location.

For multi-move discussions hosted on a page which is itself proposed to be moved, it is not necessary to include the |current1=Current title of page 1 for the page hosting the discussion, as its current title can be inferred automatically. Occasionally the discussions for significant multi-move requests may be hosted on WikiProject talk pages or other pages in Project namespace, in which case it is necessary to include |current1= to indicate the first article to be moved.

Request all associated moves explicitly

Shortcut

Please list every move that you wish to have made in your request. For example, if you wish to move Cricket (disambiguation) to Cricket because you do not believe the sport is the primary topic for the search term "Cricket", then you actually want to move two pages, both Cricket (disambiguation) and Cricket. Thus you must list proposed titles for each page affected by your request. For example, you might propose:

If a new title is not proposed for the sport, it is more difficult to achieve consensus for a new title for that article. A move request that does not show what to do with the material at its proposed target, such as:

is incomplete. Such requests may be completed as a request to decide the best new title by discussion.

If a disambiguation page is in the way of a move, the request may be completed as proposing to add (disambiguation).

Template usage examples and notes
Talk page tag Text that will be shown (and usage notes)
{{subst:Requested move|new|reason=why}}
links talk edit
Requested move 30 October 2024

Wikipedia:Requested moves → New – why Example (talk) 01:12, 30 October 2024 (UTC)[reply]

Use when the proposed new title is given.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move|?|reason=why}}
Requested move 30 October 2024

Wikipedia:Requested moves → ? – why Example (talk) 01:12, 30 October 2024 (UTC)[reply]

Use when the proposed new title is not known.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:.
This tag should be placed at the beginning of the section containing the relevant discussion.

{{subst:Requested move|new|reason=why|talk=yes}}
Requested move 30 October 2024

Wikipedia:Requested moves → New – why Example (talk) 01:12, 30 October 2024‎ (UTC)[reply]

Survey
Feel free to state your position on the renaming proposal by beginning a new line in this subsection with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's policy on article titles.
Discussion
Any additional comments:



This template adds subsections for survey and discussion.
Do not sign this template—this tag is auto-signed when substituted. Be sure to use the subst:
Click the "New Section" tab on the talk page and leave the Subject/headline blank, as the template by default automatically creates the heading.

{{subst:Requested move|new1=x|current2=y|new2=z|reason=why}}
Requested move 30 October 2024

– why Example (talk) 01:12, 30 October 2024 (UTC)[reply]

Do not sign this template—this tag is auto-signed when substituted.
Be sure to use the subst: and place this tag at the beginning of the section containing the relevant discussion.
Add additional related move requests in pairs (|current3= and |new3=, |current4= and |new4=, etc.).

{{subst:Requested move|new1=?|current2=y|new2=?|reason=why}}
Requested move 30 October 2024

– why Example (talk) 01:12, 30 October 2024 (UTC)[reply]


Commenting on a requested move

Shortcut

All editors are welcome to contribute to the discussion regarding a requested page move. There are a number of standards that Wikipedians should practice in such discussions:

  • When editors recommend a course of action, they write Support or Oppose in bold text, which is done by surrounding the word with three single quotes on each side, e.g. '''Support'''.
  • Comments or recommendations are added on a new bulleted line (that is, starting with *) and signed by adding ~~~~ to the end. Responses to another editor are threaded and indented using multiple bullets.
  • The article itself should be reviewed before any recommendation is made; do not base recommendations solely on the information supplied by other editors. It may also help to look at the article's edit history. However, please read the earlier comments and recommendations, as well as prior move requests. They may contain relevant arguments and useful information.
  • Vested interests in the article should be disclosed per Wikipedia:Conflict of interest § How to disclose a COI.

When participating, please consider the following:

  • Editors should make themselves familiar with the article titling policy at Wikipedia:Article titles.
  • Other important guidelines that set forth community norms for article titles include Wikipedia:Disambiguation, specific naming conventions, and the manual of style.
  • The debate is not a vote; please do not make recommendations that are not sustained by arguments.
  • Explain how the proposed article title meets or contravenes policy and guidelines rather than merely stating that it does so.
  • Nomination already implies that the nominator supports the name change, and nominators should refrain from repeating this recommendation on a separate bulleted line.[a]
  • Do not make conflicting recommendations. If you change your mind, use strike-through to retract your previous statement by enclosing it between <s> and </s> after the bullets, and de-bold the struck words, as in "• Support Oppose".

Please remember that reasonable editors will sometimes disagree, but that arguments based in policy, guidelines, and evidence have more weight than unsupported statements. When an editor offers an argument that does not explain how the move request is consistent with policies and guidelines, a reminder to engage in constructive, on-topic discussion may be useful. On the other hand, a pattern of responding to requests with groundless opinion, proof by assertion, and ignoring content guidelines may become disruptive. If a pattern of disruptive behavior persists after efforts are made to correct the situation through dialogue, please consider using a dispute resolution process.

Closing a requested move

Any uninvolved editor in good standing may close a move request. Please read the closing instructions for information on how to close a move request. The Simple guide to closing RM discussions details how to actually close a requested move discussion.

Relisting a requested move

Shortcut

Relisting a discussion moves the request out of the backlog up to the current day in order to encourage further input. The decision to relist a discussion is best left to uninvolved experienced editors upon considering, but declining, to close the discussion. In general, discussions should not be relisted more than once before properly closing.[b] Users relisting a debate which has already been relisted, or relisting a debate with a substantial discussion, should write a short explanation on why they did not consider the debate sufficient to close. While there is no consensus forbidding participation in a requested move discussion after relisting it, many editors consider it an inadvisable form of supervote. If you want to relist a discussion and then participate in it, be prepared to explain why you think it was appropriate.

Relisting should be done using {{subst:RM relist}}, which automatically includes the relister's signature, and which must be placed at the very end of the initial request after the move requester's signature (and subsequent relisters' signatures).

When a relisted discussion reaches a resolution, it may be closed at any time according to the closing instructions; there is no required length of time to wait before closing a relisted discussion.

If discussion has become stale, or it seems that discussion would benefit from more input of editors versed in the subject area, consider more widely publicizing the discussion, such as by notifying WikiProjects of the discussion using the template {{RM notification}}. Banners placed at the top of the talk page hosting the move request can often be used to identify WikiProjects suitable for notification.

Notes

  1. ^ A nominator making a procedural nomination with which they may not agree is free to add a bulleted line explaining their actual position. Additional detail, such as sources, may also be provided in an additional bullet point if its inclusion in the nomination statement would make the statement unwieldy. Please remember that the entire nomination statement appears on the list on this page.
  2. ^ Despite this, discussions are occasionally relisted more than once.

Current discussions

Shortcut
This section lists all requests filed or identified as potentially controversial which are currently under discussion.

This list is also available in a page-link-first format and in table format. 65 discussions have been relisted.

October 30, 2024

  • (Discuss) – Wood Boulden → Wood Bouldin – All the sources I've consulted (including the FFV genealogy volumes I have not cited) spell his name "Bouldin" I came across this problem in 2020 during covid shutdowns but did not so anything about it. Tokyogirl placed a redirect, so I cannot just do the move. The original editor has not edited in a long time. And no one has done anything about this talk page. Jweaver28 (talk) 23:52, 22 October 2024 (UTC) — Relisting. Safari ScribeEdits! Talk! 00:39, 30 October 2024 (UTC)[reply]

October 29, 2024

  • (Discuss) – Stadion Střelnice → Střelnice Stadium – According to the guideline WP:UE on the English Wikipedia, article titles should prioritize widely recognized English names, especially when available. Using English titles aids accessibility and comprehension, as English is the primary language of the platform, while languages with limited global reach, such as Czech, may be less understood by the general readership. In cases where an official English name does not exist, a direct and accurate translation into English should be used to best convey the meaning and context of the original name. Paradygmaty (talk) 22:27, 29 October 2024 (UTC)[reply]
  • (Discuss) – Letní stadion, Chomutov → Chomutov Summer Stadium – According to the guideline WP:UE on the English Wikipedia, article titles should prioritize widely recognized English names, especially when available. Using English titles aids accessibility and comprehension, as English is the primary language of the platform, while languages with limited global reach, such as Czech, may be less understood by the general readership. In cases where an official English name does not exist, a direct and accurate translation into English should be used to best convey the meaning and context of the original name. Paradygmaty (talk) 22:26, 29 October 2024 (UTC)[reply]
  • (Discuss) – Louisville International Airport → Louisville Muhammad Ali International Airport – The airport was officially renamed 'Louisville Muhammad Ali International Airport' in 2019. Although there was previously a move discussion in 2019 where it was argued that this name was not yet commonly recognized. But the name 'Louisville Muhammad Ali International Airport' is now well established and widely used in official sources, media, and public. Moving the page to reflect the official, widely recognized name aligns with Wikipedia’s naming conventions for commonly used and official names. Cerium4B (talk) 21:09, 29 October 2024 (UTC)[reply]
  • (Discuss) – Fischer random chess → Chess 960 – "Chess 960" is the WP:COMMONNAME for this chess variant, based on press coverage (newspapers.com articles found from the last 20 years: 82 mentioning "Chess 960" and 65 mentioning Fischer Random Chess, many mentioning both), major chess sites including chess.com and lichess.org, recent books, and chess organizations. Other Wikipedias have also started to move away from "Fischer" in the title with 20 out of 39 using "960" in the title instead. While Fischer Random Chess is still often used as a term, it is no longer the most common name. In recent years, "Fischer Random Chess" is typically mentioned only once in reliable sources, often parenthetically or as a secondary term, with "Chess 960" used for the remainder of the article, book, etc. While the article does discuss several other variants, the focus of the article is Chess 960 and it makes sense to keep the article history connected to Chess 960 as a topic. As to "Chess 960" vs. "Chess960", including the space seems to be more frequent based on newspapers.com and Google searches, but both are often used. Daniel Quinlan (talk) 00:37, 29 October 2024 (UTC)[reply]
  • (Discuss) – John Reilly (actor, born 1934) → John Reilly (soap opera actor) – Year of birth is not preferable to this more natural modifier. According to WP:NCPDAB, failing a practical single qualifier, the disambiguator can be expanded with a second qualifier ... Years of birth and death are not normally used as disambiguators, as readers are more likely to be seeking this information than to already know it. Most of his obituaries introduce him as something like "veteran soap opera actor" or "longtime soap star". (I would alternatively support moving back to John Reilly (actor); the page was boldly moved to the current title in 2021, ostensibly to disambiguate from John C. Reilly, who is always credited with a middle initial.) Hameltion (talk | contribs) 20:11, 7 October 2024 (UTC) — Relisting. Alpha3031 (t • c) 15:15, 21 October 2024 (UTC) — Relisting. Raladic (talk) 00:31, 29 October 2024 (UTC)[reply]
  • (Discuss) – Hasmah Mohamad Ali → Siti Hasmah Mohamad Ali – The article in question was originally titled 'Siti Hasmah Mohamad Ali'. An editor renamed the title to 'Hasmah Mohamad Ali' without any previous discussion. The BLP's name change has yet to gain currency in the reliable mainstream sources. The old name/title should be maintaind in the meantime.
    Shortcut
    Perusal of government record as far as 1975 also shows 'Dr. (Puan) Siti Hasmah binti Haji Mohd Ali'. [1]

References

  1. ^ https://www.istiadat.gov.my/semakan-penerima-darjah-kebesaran-bintang-dan-pingat/
Sreeking (talk) 00:08, 29 October 2024 (UTC) Sreeking (talk) 00:08, 29 October 2024 (UTC)[reply]

October 28, 2024

  • (Discuss) – BBC Look North (Yorkshire and North Midlands) → ? – WP:NCTV problem that's unresolvable without discussion. Officially, NCTV permits television programs to be disambiguated by country, by year and/or with a genre tag on top of year or country when necessary for added clarity, and deprecates anything else — but in this case, what we have is three regional newscasts in the same country, which are disambiguated by region and thus tagged with the "Television incorrect naming style" template for "attention".
    But it's unclear what NCTV-compliant alternative names would even be possible here — country won't work at all, and disambiguating them by their own individual years of premiere would be utterly opaque and useless since they're concurrently-running newscasts. So I really see disambiguating them by region as the only viable option here, though I'm all ears if somebody's got some brilliant new alternative idea.
    There have been instances (e.g. Big Brother (Quebec TV series) as the only viable way to effectively disambiguate it from Big Brother Canada, etc.) where consensus has landed on "permit special-case variation here", but that requires a discussion to establish a consensus, and I can't just unilaterally decree that.
    And the only other solution I can think of would be to merge them all into one article that covered all three shows in the same place, and thus could have their disambiguators totally wiped out, but that's also not a solution I'm prepared to implement arbitrarily either.
    But there's no point in just leaving them tagged for "incorrect naming style" in perpetuity — one way or another, we need to figure out how to get the pages out of the "naming problems that need to be fixed" queue, since there's no value in just leaving them there forever. Bearcat (talk) 20:13, 28 October 2024 (UTC)[reply]
  • (Discuss) – Crown Office → Crown Office in Chancery – This name can refer to either the Crown Office in Chancery (central UK Government) or the Crown Office & Procurator Fiscal Service (devolved Scottish Government). Currently Crown Office refers to the London institution with Crown Office in Chancery being a redirect to it. I would prefer that these be swapped around so that Crown Office in Chancery becomes the name of the article and Crown Office becomes a disambiguation page. Robin S. Taylor (talk) 11:28, 27 October 2024 (UTC) This is a contested technical request (permalink). estar8806 (talk) ★ 19:30, 28 October 2024 (UTC)[reply]
  • (Discuss) – Tajiks of Xinjiang → Chinese Tajiks – In previous discussions over a decade and a half ago, the main points of contention were: "Which name(s) is more commonly used in reliable sources (i.e. WP:COMMONNAME)?" and "Which name(s) is appropriate, given that 'Tajik' is a misnomer because the group is actually ethnic Pamiris?" Since the discussions in 2009, scholarly articles and books have generally been split in usage of "Tajiks of Xinjiang" and "Chinese Tajiks". Neither name solves the second problem, and adding "Pamiris" in parentheses isn't necessary, in my opinion. The group itself has a distinct history and culture, and it is not merely a situation of Pamiris being on a different side of an international border (i.e. not Tajikistan). The Chinese government uses the term "Chinese Tajiks" in English to distinguish the group from Tajiks and Tajikistanis in China. It's also worth noting that members of this ethnic group have travelled and made homes elsewhere in China, so it doesn't make sense to have an article title that limits them to one specific part of the country. This article isn't about Tajiks or Pamiris who live in Xinjiang, but a distinct ethnicity that originated from the region. The article should therefore be renamed and moved to "Chinese Tajiks". Yue🌙 01:42, 28 October 2024 (UTC)[reply]

October 27, 2024

  • (Discuss) – Air Inter Flight 148 → Air Inter Flight 5148 – With the FAA's entry now referring to the accident with its callsign "ITF 148 DA": [12] from "Flight 148": [13], and none of the references in this article or the French article (or any reliable source for that matter) referring to the flight as "Flight 148" makes me reopen this move. WP:COMMONNAME requires reliable secondary sources to determine the subject's most commonly used name. In the case of this article, a search of the current title [14] brings up nothing more than either a bunch of social media links or a handful of self-published sources, neither of which can be considered as "reliable" sources, and should not outline what the common name of the topic should be. In contrast, reliable English news articles (as determined by WP:RSPSS): [15], [16], [17], all refer to the accident as "flight IT-5148" which per WP:AVINAME should be referred to as Flight 5148 in the title. Other reasons are discussed in the previous section of this talk page. GalacticOrbits (talk) 11:01, 27 October 2024 (UTC)[reply]

October 26, 2024

  • (Discuss) – Nimzowitsch-Larsen Attack → Nimzowitsch–Larsen Attack – Per MOS:DASH. Reverted by Amakuru (who did not notify me) so opening an RM. It does not seem like there were too strong opinions in the previous discussion regarding this, but it has been mentioned as a concern multiple times, and counter-arguments like this is what people are actually going to type when they're searching for the article or hyphenated in absolutely all sources known to humanity do not apply since the former can be resolved by redirects while the MOS is just a typographic convention used on Wikipedia which is imposed specifically to introduce consistency into titles where the typography of the original sources vary. 1234qwer1234qwer4 16:45, 26 October 2024 (UTC)[reply]
  • (Discuss) – Protagonist (Persona 3) → Makoto Yuki – I understand that this request has been made a few times in the past, but in 2024 I think it's by now indisputable that the Persona 3 protagonist's name is Makoto Yuki. This is the default name in both recent ports of Persona 3 Portable and this year's Persona 3 Reload. Characters with customizable names like Cloud Strife and Byleth are titled by their canon names and even the Persona 4 protagonist is titled Yu Narukami despite having a different manga name. The existence of the female protagonist may raise an issue, but I think the protagonist can canonically be considered male given the fact that the female option was a later addition. The option is also absent from Reload and even the official Wikipedia page for Persona 3 refers to the protagonist with male pronouns. However, if we decide we want to acknowledge both we could have a dual title in the same boat as Alexios and Kassandra. Still, I'd discourage this since the female protagonist's default name in Portable is only used in the stage play otherwise. ThanatosApprentice (talk) 04:48, 19 October 2024 (UTC) — Relisting. Reading Beans, Duke of Rivia 09:50, 26 October 2024 (UTC)[reply]
  • (Discuss) – Knull (character) → Knull – Based on WikiNav statistics and article pageviews analysis, this article on the character is the WP:PRIMARYTOPIC of the term "Knull" and provides a WP:NATURAL title. Even though the character was introduced in 2018 and recently appeared in the new Venom film, the amount of viewership going to this article as opposed to other similarly titled ones far outweighs WP:RECENTISM. The redirect Knull, which points to the German mountain range fully known as "Knüllgebirge" (the article was moved to the shorthand name in 2017 with no rationale and the German Wikipedia entry uses the full name) has seen a spike in recent weeks, likely from readers attempting to locate this character article. That German mountain range should move back to the full name with this becoming the primary topic, as the redirect without diacritics is being sought after for the character and not the full name anyway. There is also Knull, Idaho, which is adequately disambiguated. The character is far more likely to have significant usage than these two locations. Trailblazer101 (talk) 06:29, 26 October 2024 (UTC)[reply]

October 25, 2024

  • (Discuss) – List of organizations that self-identify as Native American tribes → List of groups not recognized by the United States as tribes – In reviewing the previous discussion on the list title, I noticed significant confusion and disorganization. So to review the previously proposed titles: * List of Native American heritage groups * List of unrecognized Indigenous nations * List of unrecognized Native American tribes * List of unrecognized tribes in the United States * List of corporations posing as Indigenous nations * List of corporations self-identifying as Indigenous nations * List of groups that self-identify as Native American tribes * List of organizations self-identifying as Native American tribes * List of unrecognized organizations identifying as Native American tribes * List of unrecognized organizations that self-identify as Native American tribes In summary, the proposed variations: * The main noun: groups, nations, tribes, organizations, corporations * The descriptor: "Indigenous", "Native American", "in the United States" * The qualifier: "posing as", "identifying as" "self-identifying as", "that self-identify as" "unrecognized", "heritage" Now the stated purpose of the move was WP:CONCISE, WP:PRECISE. These principles emphasize that titles should be no longer than necessary yet descriptive and precise enough to convey the topic clearly to those familiar with the subject matter. However, these principles weren't directly addressed in the discussion and appeared only as boilerplate guidance in the move dialog. Let's evaluate the proposals based on concision and precision: * Main noun: On the basis of concision, "groups" and "tribes" are the best options. In fact, it was noted that "groups" was less wordy. Yet instead an argument was made based on WP:CONSISTENCY, identifying WikiProject Organizations, which is not even a mainspace page. A search of mainspace shows that both groups and organizations are used, with about 736 group lists vs. 528 organization lists. As such, consistency, to the extent there is any when it is so close to 50/50, agrees with concision in using the shorter choice "groups". * Descriptor: While calling these groups "tribes" is controversial, labeling them as "self-identified Native American tribes" is also problematic. For example, the Cherokee Nation identifies itself as a tribe, but including it on this list would be inappropriate. Additionally, "Indigenous" raises broader issues related to colonialism. Descriptions limited to "United States" are more neutral, although not without controversy, as seen in discussions on topics like secessionists and the sovereign citizen movement, but currently those positions are considered WP:FRINGE so it seems safe to use. * Qualifier: "Heritage" is the most concise, as it doesn't require an "as" clause, but it was mentioned that some organizations claim Native American heritage without identifying as having tribal status. A title like "List of United States heritage groups" makes clear that this word does not capture the scope of the desired list. "Unrecognized" is clear and concise - in the previous discussion, it was left out as it made the title "slightly shorter and simpler", but I would argue it is necessary. "Identify" and "self-identify" are not precise enough to distinguish federally recognized tribes from unrecognized tribes. As for "posing", it seems clear it would be a separate list from the current one under discussion. Although, there was the statement that "reliable sources on legitimacy are not 'very scarce'. It really isn't 'muddy' if you're familiar with the field", so perhaps this list will split in the future into "list of legitimate unrecognized tribes" and "list of posers". So this leaves us with the words "groups", "tribes", "United States", and "unrecognized". Plug those through the title generator and... out comes "List of groups not recognized by the United States as tribes". This title seems clear, neutral, and concise in adherence with Wikipedia's guidelines. To compare lengths: * Previous: List of unrecognized tribes in the United States, 48 chars * Current: List of organizations that self-identify as Native American tribes, 66 chars * Proposed: List of groups not recognized as tribes by the United States, 60 chars The proposed title is similar to the previous one but avoids the appearance of potential bias. In a similar discussion, it was determined that the title "List of organizations designated by the Southern Poverty Law Center as hate groups" was necessary over the shorter alternative "List of hate groups designated by the Southern Poverty Law Center" for clarity and neutrality. And the proposed title here is both more concise and precise than the current option. Other variations would be: * List of Native American groups not recognized by the United States as tribes, 76 chars * List of groups the United States does not recognize as tribes, 61 chars * List of groups unrecognized as tribes by the United States, 58 chars However, these alternatives are either longer or use awkward phrasing. Mathnerd314159 (talk) 17:17, 25 October 2024 (UTC)[reply]
  • (Discuss) – Neopanax colensoi → Pseudopanax colensoi – WP:COMMONNAME and WP:FLORA - overwhelming usage within recent scientific papers, despite mixed use in taxonomic databases. Without a clear scientific basis for a preference of one name over the other, MOS:ENGVAR/MOS:TIES: that there is a clear consensus among New Zealand scientific sources for a clade of plants endemic to New Zealand. *Neopanax and Pseudopanax together form a clade. Currently there are three morphological forms of the species within this clade - two are always described as Pseudopanax, while one (the more basal form) is sometimes described as Neopanax and sometimes Pseudopanax. page 52 of this thesis has a useful graph showing phylogenetic relationships within the group. Neopanax was synonymised with Pseudopanax in the 20th century, re-established as a genus in 2004, but the justification of this was disputed in 2009. The distinction appears to be one based on conventions rather than a clear scientific justification (i.e. less based on whether or not Neopanax is a distinct clade within Pseudopanax, and more based on whether it's justified to use a different name for this clade, or to continue to use the pre-2004 convention). This issue was previously discussed at WikiProject Plants. *Different taxonomical databases use different preferred names. Pseudopanax is overwhelmingly used by New Zealand databases. **Pseudopanax preferred: NZ Flora, Biota of New Zealand, IUCN, iNaturalist, NZOR and NZTCS **Neopanax preferred: CoL, EoL, GBIF, IRMNG, NCBI, OTOL, POWO *Recent scientific sources outside of taxonomic databases overwhelmingly prefer Pseudopanax. Looking at Post-2020 Google Scholar results for species within the Neopanax clade:

Prosperosity (talk) 00:57, 6 October 2024 (UTC) — Relisting. Reading Beans 08:05, 13 October 2024 (UTC) — Relisting. FOARP (talk) 14:44, 25 October 2024 (UTC)[reply]

  • (Discuss) – Swedish Brother's Feud → ? – The current title is perhaps a partial translation of Den andra brödrastriden (no source is given), but as far as I know, the conflict doesn't have an established name. Since Wikipedia's scope is global and it covers all time periods, this short title seems somewhat weird. Also, it should be Swedish brothers' feud, with plural brothers and without capitalization, since it is not really a proper name but a descriptive phrase. I suggest two alternatives, between which I am quite undecided: * Conflict between Birger Magnusson and his brothers, based on the title of Jerker Rosén's dissertation "Striden mellan Birger Magnusson och hans bröder : studier i nordisk politisk historia 1302-1319". * Inter-Nordic conflict of 1302–1319, based on Sverre Bagge's article Aims and means in the inter‐Nordic conflicts 1302–1319 (I don't think the plural is absolutely necessary, and using it might suggest that the article is a list). The latter title would make the focus of the article a bit wider. This would help avoid duplicating content, since the strife between Magnussons is already covered in their biographies. However, going into detail about the power-play between different kingdoms (See Bagge's article) might be a distraction in the biographies, but could be discussed here. Sundberg 2010 calls this Kampen mellan Birger och hans bröder 1304–1310. Sundberg's time limits are explained by his focus on armed conflict. However, I think Rosén's and Bagge's temporal limits make more sense, since the political conflict already starts when Birger becomes of age 1302, and ends in 1319 to his deposition. — Jähmefyysikko (talk) 07:10, 15 October 2024 (UTC) — Relisting. FOARP (talk) 14:43, 25 October 2024 (UTC)[reply]
  • ^ Shuham, Matt (2024-08-02). "'ELIMINATED': Israel Brags Of Killing Noted Al Jazeera Journalist In Gaza". HuffPost. Archived from the original on 2024-08-02. Retrieved 2024-08-04.
  • ^ "Israel Defense Force on X". Twitter. 1 August 2024. Archived from the original on 4 August 2024. Retrieved 12 August 2024.

    • 95.183.203.226 (talk) 14:25, 25 October 2024 (UTC)[reply]

    • (Discuss) – Special Ops: Lioness → Lioness (American TV series) – The original title of Special Ops: Lioness from Paramount+ was Lioness. So an article named Lioness (American TV series) was created in Wikipedia. Then the marketing department of Paramount+ renamed it. However as part of it's season 2 renewal it was renamed once again back to Lioness. People new to this series may not know that it was previously known as Special Ops: Lioness, At this juncture when a person enters Lioness they are directed to a disambiguation page. There is no indication that Special Ops: Lioness is indeed what they are searching for. It's described as "...a spy thriller series (2023 onwards)". We could move the article back to Lioness (American TV series) or move it to Lioness ( TV series). An alternative solution would be to edit the disambiguation page description of Special Ops: Lioness from "...a spy thriller series (2023 onwards)" to "a 2023 spy thriller TV series renamed in 2024 to Lioness". I would argue that this would be just a clumsy excuse not to move it at all. KnighsTalker (talk) 07:57, 25 October 2024 (UTC) This is a contested technical request (permalink). knighstalker (talk) 11:11, 25 October 2024 (UTC)[reply]

    October 24, 2024

    • (Discuss) – Man-eater → Man-eating animal – There are multiple equally primary meanings, namely cannibalism, femme fatales and Man-eating plant. Maneater is already a DAB page despite the two titles being essentially interchangeable. I propose this move given it is urgently needed and better than the alternative. The original title can then be redirected to the DAB page. While I personally oppose the slang term "man-eater" being used over "animal attack", the more scientific term for it, I think it's best not to rock the boat given the previous failed proposals and have something people should be able to agree on. ᴢxᴄᴠʙɴᴍ (ᴛ) 02:16, 17 October 2024 (UTC) — Relisting. Raladic (talk) 20:07, 24 October 2024 (UTC)[reply]
    • (Discuss) – Gun show loophole → Private sale of firearms in the United States – I have been reading the comments between a number of editors over the past few weeks and I have been engaged in the discussion around what to do with this GSL article name. At this point, the discussion clearly looks like a new title is needed and that the best neutral title is "Private sale of firearms in the United States" according to common usage and the aggregate of best reliable sources. Any other changes to the article can be dealt with separately, this discussion should just be over whether or not to re-title the article to "Private sale of firearms in the United States" instead of "Gun show loophole". Iljhgtn (talk) 15:39, 24 October 2024 (UTC)[reply]
    • (Discuss) – Minnesota Fats → Minnesota Fats (character) – Why isn't the article at Minnesota Fats? That is by far the most common name used here to refer to him. Every source in the article uses Minnesota Fats, to the point even his NYT obit called him that and not Rudolph Wanderone, and the word "Wanderone" is hardly used in the text of the article instead of "Fats". Sure, he named himself after a fictional character, but inbound links and page views suggest most people looking for "Minnesota Fats" are looking for the pool player and not the character. It's blatantly obvious Wanderone's legacy has far outlasted that of the fictional character from whom he derived his name. This seems a crystal-clear violation of WP:COMMONNAME to have his article at "Rudolph Wanderone", and to me, it's like if we arbitrarily decided to move Lady Gaga's article to "Stefani Germanotta". I'm genuinely shocked no one else has even considered this issue in the past ten years. Previous discussion in 2014 had everyone pulling a different direction, and me in a more hostile mood, so I'm hoping to get a consensus this time with a clearer focus from both me and others. Ten Pound Hammer • (What did I screw up now?) 20:08, 16 October 2024 (UTC) — Relisting. Charlotte (Queen of Hearts • talk) 00:23, 24 October 2024 (UTC)[reply]

    October 23, 2024

    References

    1. ^ Vandergrift GW, Hessels AJ, Palaty J, Krogh ET, Gill CG (April 2018). "Paper spray mass spectrometry for the direct, semi-quantitative measurement of fentanyl and norfentanyl in complex matrices". Clinical Biochemistry. 54: 106–111. doi:10.1016/j.clinbiochem.2018.02.005. PMID 29432758.
    2. ^ "Fentanyl DrugFacts". National Institute on Drug Abuse. 1 June 2021. Archived from the original on 11 May 2023. Retrieved 20 February 2023.
    𝚈𝚘𝚟𝚝 (𝚝𝚊𝚕𝚔𝚟𝚝) 20:17, 23 October 2024 (UTC)[reply]
    • (Discuss) – Hiawatha (train) → Hiawatha (Milwaukee Road train) – These paranthetical names aren't quite as clear and precise as they can be since multiple other trains have used these names throughout their history. The simple parenthetical "(train)" isn't really enough to distinguish these different trains from each other. The first article is solely about the multiple trains operated by the Milwaukee Road which predate the current Amtrak train along the corridor of the same name. The name could be changed to "trains" to indicate the multitude of different trains covered in the article. The Amtrak/Via Maple Leaf isn't the only named train with a termini in Toronto, especially the historical Lehigh Valley Railroad train, which also ran to New York City, albeit with a different alignment. The name of the article could also be changed to maybe "Amtrak/Via", but the train from my understanding is moreso grouped with Amtrak. The Amtrak Palmetto is the successor of the ACL train of the same name. The fourth article is about a completely unrelated historical ATSF train operating in California separate from the current Amtrak train. The Wolverine is also the name of a historical New York Central Railroad train. Nonetheless, I don't necessarily believe in these names as final as I want them to be subject to change, and not all of them need to be implemented. I will say that if we decide that the simple parenthetical of "(train)" is sufficient in describing the articles in question, then perhaps instead the article titles for the Amtrak Pere Marquette, Silver Star, and Valley Flyer could have "Amtrak" dropped from their parentheticals for naming consistency across all Amtrak train articles. Thoughts? OrdinaryScarlett (talk) 06:21, 23 October 2024 (UTC)[reply]

    Elapsed listings

    Shortcut
    The 7-day listing period has elapsed. Items below may be closed if there's a consensus, or if discussion has run its course and consensus could not be achieved.
    • (Discuss) – EP → EP (disambiguation) – This will probably be an interesting discussion... proposing moving "EP" to "EP (disambiguation)", and then redirecting EP to Extended play for the following reason: WikiNav clickstream data shows that the majority of visitors to EP are intending to visit Extended play. Of the destination pages that WikiNav shows data on, Extended play receives 97% of the outgoing traffic. Almost all other destinations from EP receive such little click traffic that they are not detailed by WikiNav. That means that, while Extended play received 471 clicks from the disambiguation page in the month of September, any other article received less than 10. I could see maybe some arguments to keep EP where it is because of European Parliament, which is colloquially shortened to "EP", but the data doesn't support that people are commonly ending up at the "EP" disambiguation on Wikipedia and expecting to be at the article for European Parliament... again, less than 10 clicks. Interested to see how this plays out. RachelTensions (talk) 13:39, 22 October 2024 (UTC)[reply]
    • (Discuss) – Juan Fageda → Joan Fageda – His birth certificate may well say the Castilian name Juan and he would have been forced into that name for the first 40 years of his life, but personal preferences and modern sources strongly prefer the Catalan name Joan. Going by WP:OFFICIALNAME we would have William Clinton and Anthony Blair. Fageda's website is joanfageda.com and this letter on it is signed as Joan [30]. Third-party sources in Castilian are using Joan [31] even the conservative El Mundo [32] and the nationalist OKDiario [33] so this is not editorial Catalanism, something that the subject as a People's Party politician is exceedingly unlikely to support Unknown Temptation (talk) 14:16, 5 October 2024 (UTC) — Relisting. Quadrantal (talk) 04:02, 15 October 2024 (UTC) — Relisting. Reading Beans, Duke of Rivia 06:58, 22 October 2024 (UTC)[reply]

    Backlog

    Shortcut
    Elapsed listings fall into the backlog after 24 hours. Consider relisting 8-day-old discussions with minimal participation.
    • (Discuss) – Moel-y-Parc transmitting station → Moel y Parc transmitting station – The name used for the mast appears to have changed over the years (possibly to mirror the hill). Looking through the references in the article to web pages for organisations, Moel-y-Parc is used on the one from 1966[1], whereas Moel y Parc is used in ones from 2009[2], 2019[3][4] and 2020[5]. The latter spelling is used on current pages from Ofcom[6], Freeview[7] and Flintshire County Council[8] use for the transmitter. Some independent web sites use Moel-y-Parc now, but I don't know their reasons. They could even have taken it from Wikipedia.

    References

    1. ^ "BAND III TRANSMITTING AERIAL FOR THE MOEL-Y-PARC V.U.F. TELEVISION STATION" (PDF). BBC. October 1966.
    2. ^ "Digital UK advises Granada TV viewers over Welsh channels problem". 2009-12-24. Archived from the original on 1 August 2012. Retrieved 2010-08-19.
    3. ^ "Table of Broadcasting Stations for Multiplex L" (PDF). Ofcom. 2019-03-27. Retrieved 2020-08-20.
    4. ^ "Trade and Industry Information, 700MHz Clearance Events, Wales Region" (PDF). Digital UK. Retrieved 8 July 2020.
    5. ^ "Trade and Industry Information, 700MHz Clearance Events, Wales Region" (PDF). Freeview. Retrieved 12 August 2020.
    6. ^ "700-plan-clearance.xlsx". Ofcom. Retrieved 21 October 2024.
    7. ^ "Freeview Detailed Coverage Checker". Freeview. Retrieved 21 October 2024.
    8. ^ "Business Rates Liabilities". Flintshire County Council. Retrieved 20 October 2024.
    Aoeuidhtns (talk) 22:43, 21 October 2024 (UTC)[reply]
    • (Discuss) – Fort Takapuna → Fort Takapuna O Peretu – I am proposing that the name is returned to Fort Takapuna O Peretu, in line with the naming conventions of Heritage New Zealand register for it as a category one historic place. [1]. This location and the structures upon it have been known by many names over the years, as can be seen from this New Zealand Herald article announcing the opening of the Department of Conservation Historic Reserve in 2000.[2] While O Peretu refers to the headland specifically, Fort Takapuna has been used to refer quite narrowly to the 1886 fort building and also broadly to the structures across the headland including the current Naval base that is not part of the historic reserve. Rather than removing O Peretu from the title, I propose including a section about the changing names of this location, its structures, and earlier histories of the headland. I would also like to note that O Peretu Fort Takapuna or Fort Takapuna O Peretu is being used increasingly frequently to refer to the reserve, e.g. [3] Thanks, Ewhite31 (talk) 20:58, 21 October 2024 (UTC)[reply]
    • (Discuss) – Nationality law of North Macedonia → North Macedonian nationality law – All in line with WP:CONSISTENT, the page should be moved as it is the only page in Category:Nationality_law that does not follow the "Country-Adjective nationality law" format. After the name change in 2019, the Wikipedia community did the 2019-RFC and based on a long list of reliable sources approved on a wider scale, it decided to use the adjective "North Macedonian" for State-associated and other public entities. I quote the decision here:  ::# State-associated and other public entities: What term should be used when referring to state-associated entities, including governmental organisations and official ranks, as well as other public entities from North Macedonia as specified in Prespa agreement?  ::#: Option B: Both "North Macedonian" and "... of North Macedonia", where a similar form would be used for other countries. e.g. the North Macedonian Government or the Government of North Macedonia.  ::#: The closing panel agrees that there is consensus for Option B. Furthermore, noting the fact that public entities are being retitled per Prespa agreement, newer sources find "North Macedonia"-related terminology more common, and we have the existing policies of WP:NAMECHANGES and WP:COMMONNAME. Therefore, according to the Consensus established in the RFC (and until there is a new RFC on a wider scale), the correct title for this page is "North Macedonian nationality law" because this is the format used for other countries as explicitly written in the conclusion of the RFC. The comment of the closing panel at the top of the 2019-RFC tells us: There is new consensus in this RfC that we have to accept as a community The page was moved to the current name on 23 February 2019 (immediately after the country was renamed to North Macedonia) but before the final decision of the 2019-RFC that was made on 11 April 2019. Therefore, the decision of the Wikipedia Community of the 2019-RFC was mistakenly not applied to this page. Open Free Eye (talk) 19:21, 21 October 2024 (UTC)[reply]
    • (Discuss) – Suga → Suga (musician) – The musician does not meet the criteria for determining primary topic per WP:PT1: 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. Looking at the list of articles in the "Suga may also refer to" section at Suga (disambiguation), the musician's article does not meet WP:PT1 because it is not clear that the usage of the term "Suga" to refer to the musician is more likely than any other single topic; in fact, Sean O'Malley (fighter), who is also commonly referred to as "Suga", seems to receive significantly (almost 3x) more monthly average pageviews than the musician: pageview stats In addition, as a common Japanese surname, there are at least 17 other articles that "Suga" could reasonably refer to, most notably former Japanese prime minister Yoshihide Suga. Clickstream data shows a not insignificant amount of people visit Suga (disambiguation) with the intention of continuing on to Yoshihide Suga. Clickstream stats Previous move history for this article shows:
      October 2021 proposal: Suga (rapper) → Suga - failed, no consensus
      July 2023 proposal: Suga (rapper) → Suga (musician) - successful
      August 2023 proposal: Suga (musician) → Suga - successful RachelTensions (talk) 18:34, 21 October 2024 (UTC)[reply]
    • (Discuss) – Tropical Storm Conson (2021) → Tropical Storm Conson – Can this page be moved to just Tropical Storm Conson? As Daniel boxs stated above, the name was retired after the 2021 Pacific typhoon season. While there was a more notable iteration of Conson last 2010, it was a typhoon. This is the only page that is named "Tropical Storm Conson"— the 2004 and 2010 iterations were typhoons, and the 2016 iteration redirects you to the 2016 typhoon page, so it's a little distinctive compared to the previous Conson iterations. Bugnawfang (talk) 08:28, 8 September 2024 (UTC) Bugnawfang (talk) 08:32, 8 September 2024 (UTC) — Relisting. Bobby Cohn (talk) 12:27, 15 September 2024 (UTC) — Relisting. asilvering (talk) 00:25, 21 October 2024 (UTC)[reply]
    • (Discuss) – Siege of Gerona (disambiguation) → Sieges of Gerona – Several issues I hope to address with these proposed moves. First, it makes little sense to have the "second" and "third" sieges as titles but to call the first event a battle; of the three is was the most like a battle, but the distinction is confusing in this case. It does seem that [ordinal] siege of Gerona is the most common manner of disambiguating the various events. If the first segment were to carry the WP:COMMONNAME "Battle" then it should not carry a parenthetical qualifier, being already WP:NATURALly disambiguated and the primary topic for the term; the base name Battle of Girona already redirects there and is WP:MISPLACED. Second, when used alone without additional context, "Siege of Gerona" does seem to refer to the successful final siege as a primary topic, and currently redirects there. I am proposing to leave this as a primary redirect and turn the disambiguation page into a set index at the plural, but I would also support having the set index in place of the redirect at the singular. Third, while I personally feel "Siege" in these titles is part of the proper noun, use in sources is mixed, and most "siege" articles on enwiki do not take siege as part of the proper noun (in contrast to "Battle of..." which is almost always part of the proper noun; I don't see the distinction) and WP:MILCAPS is vague, so for now let's go for being the most consistent. Lastly, as for the Girona vs. Gerona issue, there has been past move reversions and discussion about this (e.g. Talk:Third siege of Girona#Girona/Gerona), and we should reach consensus here. I am open to either spelling, but am proposing a return to Gerona because it does seem a majority of reliable sources use this spelling, and that is the criterion upon which we should base our choice. On the other hand, the modern spelling of the city is the Catalan spelling. Regardless, the set index/disambiguation page should use the same spelling as the articles. Overall, I am open to discussing and considering any and all variations of this proposal, but the status quo should not be kept. Mdewman6 (talk) 04:03, 1 October 2024 (UTC) — Relisting. Vanderwaalforces (talk) 22:07, 10 October 2024 (UTC)[reply]
    • (Discuss) – AIM-174B → AIM-174 – Might as well eliminitae the "B" per WP:CONCISE -- the "AIM-174B" is *technically* a specific variant of the AIM-174. Also allows for future variants (a hypothetical AIM-174C, for instance) to be added with no issue. Attempted to move myself, cannot; re-direct exists. MWFwiki (talk) 00:44, 20 September 2024 (UTC) — Relisting. RodRabelo7 (talk) 01:33, 27 September 2024 (UTC) — Relisting.  ASUKITE 21:04, 4 October 2024 (UTC)[reply]

    Malformed requests

    See "Bot considerations"

    Possibly incomplete requests

    See "Request all associated moves explicitly"

    References

    References generally should not appear here. Use {{reflist-talk}} in the talk page section with the requested move to show references there.


    See also

    The current Wikipedia time is:
    01:12, Wednesday, 30 October 2024 (UTC)
    To update time purge the cache!
      Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requested_moves&oldid=1251715537"