Wikipedia:Deletion review

From Wikipedia, the free encyclopedia

Deletion review (DRV) is for reviewing speedy deletions and outcomes of deletion discussions. This includes appeals to delete pages kept after a prior discussion.

If you are considering a request for a deletion review, please read the "Purpose" section below to make sure that is what you wish to do. Then, follow the instructions below.

Purpose

Deletion review may be used:

  1. if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
  2. if a speedy deletion was done outside of the criteria or is otherwise disputed;
  3. if significant new information has come to light since a deletion that would justify recreating the deleted page;
  4. if a page has been wrongly deleted with no way to tell what exactly was deleted; or
  5. if there were substantial procedural errors in the deletion discussion or speedy deletion.

Deletion review should not be used:

  1. because of a disagreement with the deletion discussion's outcome that does not involve the closer's judgment (a page may be renominated after a reasonable timeframe);
  2. (This point formerly required first consulting the deleting admin if possible. As per this discussion an editor is not required to consult the closer of a deletion discussion (or the deleting admin for a speedy deletion) before starting a deletion review. However doing so is good practice, and can often save time and effort for all concerned. Notifying the closer is required.)
  3. to point out other pages that have or have not been deleted (as each page is different and stands or falls on its own merits);
  4. to challenge an article's deletion via the proposed deletion process, or to have the history of a deleted page restored behind a new, improved version of the page, called a history-only undeletion (please go to Wikipedia:Requests for undeletion for these);
  5. to repeat arguments already made in the deletion discussion;
  6. to argue technicalities (such as a deletion discussion being closed ten minutes early);
  7. to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
  8. to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed);
  9. for uncontroversial undeletions, such as undeleting a very old article where substantial new sources have subsequently arisen. Use Wikipedia:Requests for undeletion instead. (If any editor objects to the undeletion, then it is considered controversial and this forum may be used.)
  10. to ask for permission to write a new version of a page which was deleted, unless it has been protected against creation. In general you don't need anyone's permission to recreate a deleted page, if your new version does not qualify for deletion then it will not be deleted.

Copyright violating, libelous, or otherwise prohibited content will not be restored.

Instructions

Before listing a review request, please:

  1. Consider attempting to discuss the matter with the closer as this could resolve the matter more quickly. There could have been a mistake, miscommunication, or misunderstanding, and a full review may not be needed. Such discussion also gives the closer the opportunity to clarify the reasoning behind a decision.
  2. Check that it is not on the list of perennial requests. Repeated requests every time some new, tiny snippet appears on the web have a tendency to be counter-productive. It is almost always best to play the waiting game unless you can decisively overcome the issues identified at deletion.

Steps to list a new deletion review

 
1.

Click here and paste the template skeleton at the top of the discussions (but not at the top of the page). Then fill in page with the name of the page, xfd_page with the name of the deletion discussion page (leave blank for speedy deletions), and reason with the reason why the discussion result should be changed. For media files, article is the name of the article where the file was used, and it shouldn't be used for any other page. For example:

{{subst:drv2
|page=File:Foo.png
|xfd_page=Wikipedia:Files for deletion/2009 February 19#Foo.png
|article=Foo
|reason=
}} ~~~~
2.

Inform the editor who closed the deletion discussion by adding the following on their user talk page:

{{subst:DRV notice|PAGE_NAME}} ~~~~
3.

For nominations to overturn and delete a page previously kept, attach <noinclude>{{Delrev|date=2024 April 30}}</noinclude> to the top of the page under review to inform current editors about the discussion.

4.

Leave notice of the deletion review outside of and above the original deletion discussion:

  • If the deletion discussion's subpage name is the same as the deletion review's section header, use <noinclude>{{Delrevxfd|date=2024 April 30}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2024 April 30|page=SECTION HEADER AT THE DELETION REVIEW LOG}}</noinclude>
 

Commenting in a deletion review

Any editor may express their opinion about an article or file being considered for deletion review. In the deletion review discussion, please type one of the following opinions preceded by an asterisk (*) and surrounded by three apostrophes (''') on either side. If you have additional thoughts to share, you may type this after the opinion. Place four tildes (~~~~) at the end of your entry, which should be placed below the entries of any previous editors:

  • Endorse the original closing decision; or
  • Relist on the relevant deletion forum (usually Articles for deletion); or
  • List, if the page was speedy deleted outside of the established criteria and you believe it needs a full discussion at the appropriate forum to decide if it should be deleted; or
  • Overturn the original decision and optionally an (action) per the Guide to deletion. For a keep decision, the default action associated with overturning is delete and vice versa. If an editor desires some action other than the default, they should make this clear; or
  • Allow recreation of the page if new information is presented and deemed sufficient to permit recreation.
  • Some consider it a courtesy, to other DRV participants, to indicate your prior involvements with the deletion discussion or the topic.

Remember that deletion review is not an opportunity to (re-)express your opinion on the content in question. It is an opportunity to correct errors in process (in the absence of significant new information), and thus the action specified should be the editor's feeling of the correct interpretation of the debate.

The presentation of new information about the content should be prefaced by Relist, rather than Overturn and (action). This information can then be more fully evaluated in its proper deletion discussion forum. Allow recreation is an alternative in such cases.

Temporary undeletion

Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{TempUndelete}} template, leaving the history for review by everyone. However, copyright violations and violations of the policy on biographies of living persons should not be restored.

Closing reviews

A nominated page should remain on deletion review for at least seven days, unless the nomination was a proposed deletion. After seven days, an administrator will determine whether a consensus exists. If that consensus is to undelete, the admin should follow the instructions at Wikipedia:Deletion review/Administrator instructions. If the consensus was to relist, the page should be relisted at the appropriate forum. If the consensus was that the deletion was endorsed, the discussion should be closed with the consensus documented.

If the administrator closes the deletion review as no consensus, the outcome should generally be the same as if the decision was endorsed. However:

  • If the decision under appeal was a speedy deletion, the page(s) in question should be restored, as it indicates the deletion was not uncontroversial. The closer, or any editor, may then proceed to nominate the page at the appropriate deletion discussion forum, if they so choose.
  • If the decision under appeal was an XfD close, the closer may, at their discretion, relist the page(s) at the relevant XfD.

Ideally all closes should be made by an administrator to ensure that what is effectively the final appeal is applied consistently and fairly but in cases where the outcome is patently obvious or where a discussion has not been closed in good time it is permissible for a non-admin (ideally a DRV regular) to close discussions. Non-consensus closes should be avoided by non-admins unless they are absolutely unavoidable and the closer is sufficiently experienced at DRV to make that call. (Hint: if you are not sure that you have enough DRV experience then you don't.)

Speedy closes

  • Objections to a proposed deletion can be processed immediately as though they were a request at Wikipedia:Requests for undeletion
  • Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
  • Where the nominator of a DRV wishes to withdraw their nomination, and nobody else has recommended any outcome other than endorse, the nominator may speedily close as "endorse" (or ask someone else to do so on their behalf).
  • Certain discussions may be closed without result if there is no prospect of success (e.g. disruptive nominations, if the nominator is repeatedly nominating the same page, or the page is listed at WP:DEEPER). These will usually be marked as "administrative close".



30 April 2024

Fathima Thahiliya

Fathima Thahiliya (talk|edit|history|logs|links|watch) (XfD|restore)

Who previously created this page and other editors who shared it in the deletion discussion did not have the quality pass to retain it, so this page has been removed, and as of today, this page is eligible for a new political position WP:NPOL or (officeholder), WP:GNG. category, which should be moved to draft to be edited and moved to the main page ~~ Spworld2 talk 01:03, 30 April 2024 (UTC)[reply]

  • Endorse AfD, which is three years old. Did you ask @Daniel: for a draft? It's unclear why we're here when there's no protection limiting a new article from being created. Star Mississippi 11:59, 30 April 2024 (UTC)[reply]
    • Hi SM, thanks for the ping - this is the first time I'm aware of this DRV. It definitely was not discussed with me prior (noting that this is 'optional', although definitely encouraged by Wikipedia:Deletion review#Instructions). That being said, what isn't optional is the notification to the XfD closer, which is mandatory and required per step 2 of 'Steps to list a new deletion review'. Unfortunately, this wasn't done by the applicant. Daniel (talk) 19:39, 30 April 2024 (UTC)[reply]
  • Endorse original AfD as closed. I'm not sure what the appellant means by, should be moved to draft. Our policies have a long list of cases when an article should generally not be draftified, and some when it can, but no case where it should. If the subject's status has changed such that it now meets our notability guidelines, an article can be created, either in mainspace or in draft, and no one is stopping the appellant from doing so. If the subject's status has not changed since the AfD, draftifying is a waste of time. Owen× 12:41, 30 April 2024 (UTC)[reply]
  • Endorse the 3-year-old close. We get a number of requests to restore a deleted article to draft, possibly because the requester wants to start with something rather than from scratch. When the original article was found not to meet notability or not to be based on significant coverage, sometimes it really is better to start from scratch. Robert McClenon (talk) 15:41, 30 April 2024 (UTC)[reply]

Template:Historical American Documents

Template:Historical American Documents (talk|edit|history|logs|links|watch) (XfD|restore)

Consensus for splitting was clear and was initially given by closing editor here and in previous discussion Wikipedia:Templates for discussion/Log/2024 March 12#Template:Signers of the U.S. Declaration of Independence, yet refusal to accept this consensus and consistent WP:BLUDGEONING by a certain editor at Template talk:Historical American Documents seems to have overturned and derailed the correct outcome --woodensuperman 06:42, 30 April 2024 (UTC)[reply]

  • Please note that the nominator did not first discuss the closer's decision with the closer, which is listed as a required step before a review. Procedural close? Randy Kryn (talk) 12:04, 30 April 2024 (UTC)[reply]
    It seemed pointless, as you'd already convinced them to change their close against consensus. Needed to be seen on a wider forum. --woodensuperman 12:11, 30 April 2024 (UTC)[reply]
  • Endorse Keep, While the discussion, on a quick glance, seems to be a consensus to split, in reading it carefully - as the closer eventually did before reversing their response - that falls apart quickly. Split arguments included 1) that the navbox is too large (incorrect, there are hundreds if not thousands of navboxes which are broken up into sections, and this one has four easily understood and distinct sections), 2) that the navbox includes duplication (incorrect, each of the four sections lists individuals who drafted a particular document. That some were active in two events is akin to sportspeople playing two seasons of a sport, a sport which formed a 250 year old nation), 3) that other navboxes exist (there are signatory navboxes for each document, which are used in place of adding the central navbox to each signer) and 4) that there is a basis for splitting because of a previous discussion (incorrect, the rational fails when realizing that although this navbox was used as an example in an earlier discussion there were no notification tag placed - not on the navbox, not on its talk page, not on the pages of its topic structure, and not on the talk page of its creator). This collapsed and typically sectioned navbox actually saves space, has an accurate visible title ("Founding documents of the United States") and has been carefully edited and maintained since 2010. Randy Kryn (talk) 11:31, 30 April 2024 (UTC)[reply]
    Other than the two "keep" !votes, both converstaions were practically unanimously in favour of a split. --woodensuperman 12:12, 30 April 2024 (UTC)[reply]
    You missed some editors, more than two. There was only one conversation involved in this request, the first only used the navbox as an example without notifying anybody that it was being scrutinized. I address the split above (please remember that these decisions are not made by counting heads). Randy Kryn (talk) 12:16, 30 April 2024 (UTC)[reply]
    Nope, only yourself and Gwillhickers advocated for "keep". --woodensuperman 12:20, 30 April 2024 (UTC)[reply]
  • Speedy vacate and leave for an admin, Toadette is not ready to be closing XFD's, especially contentious ones where there's clearly a split in opinion as is evident here. I'm not familiar enough with templates or I'd have done it myself. Star Mississippi 12:01, 30 April 2024 (UTC)[reply]
  • Star Mississippi, the discussion may tend to confuse inexperienced closers, as it did initially for Toadette who, when asked, took another read and came to what I view as the correct conclusion. Hopefully an admin will take a good long look at this one, grab some coffee, view the "Founding documents of the United States" navbox, and create a solid mental map of the two "sides" before completing their analysis. Thanks. Randy Kryn (talk) 12:12, 30 April 2024 (UTC)[reply]
  • information Administrator note: @Woodensuperman and Randy Kryn: you have both commented verbosely and continuously at all venues related to this discussion. I would kindly ask that you cease commenting and let uninvolved editors discuss the matter. Primefac (talk) 12:19, 30 April 2024 (UTC)[reply]
  • Speedy vacate and revert on sight any other BADNACs by this out-of-control editor. Every few days we have to undo another BADNAC from this one editor. Enough already. Owen× 14:03, 30 April 2024 (UTC)[reply]
  • Vacate per User:Star Mississippi. I don't see a guideline for Speedy Vacates. Should there be one, or do these editors just mean that it is obvious that the close should be vacated? The original close of Split was a valid close, and did not need to be changed, and changing it did not reflect consensus, so much as an argument from one of the two editors who has been bludgeoning this discussion. Robert McClenon (talk) 15:31, 30 April 2024 (UTC)[reply]
    Perhaps "summarily" would have been a better term than "speedy". I (and, I'm guessing, Star Mississippi) believe this DRV can be closed by any uninvolved admin without waiting the statutory seven days. Owen× 15:47, 30 April 2024 (UTC)[reply]
    Procedurally speaking, Deletion-related closes may only be reopened by the closer themselves; by an uninvolved administrator in their individual capacity... or by consensus at deletion review, which is somewhat ambiguous about whether one can re-open as an individual admin action while a DRV is progressing, but does not expressly forbid it like some other wordings I've seen. Primefac (talk) 16:06, 30 April 2024 (UTC)[reply]
    Fair point. I read prongs #2 and #3 of that policy to imply that if there's a rough consensus to summarily vacate, any uninvolved admin may close the DRV and revert the XfD closure, without waiting for the DRV to run its course. Leaving this here for seven days isn't a disaster, but I also see no benefit to doing so if there's a consensus to vacate. Owen× 16:19, 30 April 2024 (UTC)[reply]
  • Comment - As per User:Primefac, can User:Randy Kryn and User:Woodensuperman stop bludgeoning this discussion? I hope that we don't need to go to WP:ANI to ask for a one-comment-per-24-hours limit on these two editors (but we probably do, unless they will really back off voluntarily). Robert McClenon (talk) 15:31, 30 April 2024 (UTC)[reply]
  • Primefac, Robert McClenon I was sort of shocked to find that after the closing at decision to keep, woodensuperman went to the Template:Historical American Documents and tagged the template for deletion. IMO, this was nothing more than a vindictive reaction from someone disgruntled over ToadetteEdit 's decision and closure. Because of the developments that occurred here the tag has been (was) reverted, just for the record.
    Additional note: Initially there was indeed a clear consensus to split, and only split, the template, but once it became evident that one editor was not content with just splitting but wanted to further make edits to the would be separate templates, and kept making one point of contention after another, even many of the notified editors didn't bother to pursue a never ending discussion, so it's perfectly debatable as to whether all the involved editors still wish to split. IMO,Toadette.'s decision, all things considered, was certainly called for.
    Latest: As I write, Woodensuperman has just restored the tag for deletion. Could someone please deal with this editor? -- Gwillhickers (talk) 20:25, 30 April 2024 (UTC)[reply]
    @Gwillhickers: the only tag I see there is the DELREV tag, linking to this review here, as required by policy. Am I missing something? Owen× 20:58, 30 April 2024 (UTC)[reply]
Yes, a tag for deletion review. In any case, we can let the tag ride, because it seems this nomination, also, isn't going anywhere. I bowed out of the original and belabored discussion days ago. Opting to outright delete the entire template simply because a nomination to split didn't go as expected, is an overkill request and completely uncalled for. -- Gwillhickers (talk) 21:11, 30 April 2024 (UTC)[reply]
The tag is to notify people of this discussion, not to delete anything. Deletion review is simply where you go to appeal a closed decision. SportingFlyer T·C 21:31, 30 April 2024 (UTC)[reply]
  • Overturn to Split. There's only one way to close that discussion. It was also poorly closed, so I don't care if the BADNAC is simply undone and re-closed by an administrator. I think we're also close to handing out topic bans. SportingFlyer T·C 21:01, 30 April 2024 (UTC)[reply]

Saira Shah Halim

Saira Shah Halim (talk|edit|history|logs|links|watch) (XfD|restore)

The deletion discussion was taken without any proper discussion based on policy happening. The article had enough reliable sources with significant coverage over a wide period of time. I provided a wide list of sources. Two participants simply did not see anything and made vague comments, one of them was a brand new account and the other's only objection was that it was edited by sockpuppet. One more participant later came and after some discussion he accepted that the coverage was fine but he did not consider the topic notable because the topic didn't meet WP:NPOL ignoring WP:BASIC and also WP:GNG itself which the coverage meets. There was no other participation. Therefore it must have been no consensus or keep, not delete.

P.S, there was one more participant who concurred but didn't give a (vote) and wanted to see some more sources over a wider period of time which I showed but she didn't come back to it. It should be counted too. MrMkG (talk) 01:03, 30 April 2024 (UTC)[reply]

  • Endorse the original AfD, since everyone except the DRV nominator supported deletion so it couldn't have been closed any other way. Overturn the A7 since I think being a political candidate is a CCS even if it isn't evidence of notability, but re-delete that as a G4. And salt * Pppery * it has begun... 02:22, 30 April 2024 (UTC)[reply]
  • Endorse the original AFD as Delete. As per Pppery, Overturn the A7. I haven't seen the reposted article, but having seen the history, I concur with salting. Robert McClenon (talk) 02:33, 30 April 2024 (UTC)[reply]
  • For the benefit of non-admins, the A7'd version stated in its entirety "Saira Shah Halim is the CPI(M) candidate of South Kolkata Lok Sabha." (No sources.) Arguably it's more of a G4 than an A7. Extraordinary Writ (talk) 02:44, 30 April 2024 (UTC)[reply]
    @Extraordinary Writ I am confused. Did someone create the article again with that single sentence after the article was deleted in AfD recently and is that what all the admins are seeing?
    I would request them to see the article that was created by me and deleted in the 2nd AfD nomination and see the conversations in the 2nd AfD nomination. It was a proper article, multiple paragraphs long divided into multiple sections with multiple sources.
    This DRV is about that. It shouldn't be deleted just because some sockpuppet or whatever is active around it too. MrMkG (talk) 04:08, 30 April 2024 (UTC)[reply]
    Yes, that's what happened. I think everyone here is aware that you're talking about the second AfD (which people are calling "the original AfD"); they just have comments on the deletion of the single-sentence version too. Extraordinary Writ (talk) 05:08, 30 April 2024 (UTC)[reply]
  • The AFD-deleted article was thousands of bytes, with multiple sections and eight references. The speedy-deleted article, as you see from Extraordinary Writ's comment, was one sentence. It's obviously not a repost, and obviously not a G4 candidate. Anyone can be a candidate for political office; it's not at all a claim of importance merely to be a candidate. Nyttend (talk) 02:53, 30 April 2024 (UTC)[reply]
  • Comment - It's not about the original AfD, that was in 2016. Its about the second AfD. (Wikipedia:Articles for deletion/Saira Shah Halim (2nd nomination)) MrMkG (talk) 03:50, 30 April 2024 (UTC)[reply]
See the conversation on User talk:OwenX#Wikipedia:Articles for deletion/Saira Shah Halim (2nd nomination) too. Over there User:Amakuru is also making the point, I am making. MrMkG (talk) 03:59, 30 April 2024 (UTC)[reply]
  • Comment The AfD was poorly argued. Even though numerical consensus was against the appellant, statements like Extensive coverage of a non-notable person doesn't help. are not policy based, and demonstrate a bias against failed political candidates, as if that somehow eliminated their GNG compliance. Of course, that GNG compliance itself is challenged by the general unreliability of Indian news sources overall. Neither G4 nor A7 applied to the recreation. In short? This is a big mess, and I'm not sure deletion is a better outcome than no consensus, given the amount of uncertainty and poor policy argumentation in play. Jclemens (talk) 05:37, 30 April 2024 (UTC)[reply]
    Indian news sources are not overall unreliable. How can we create any article if that is so? There are many bad sources but I did use the best sources. Two of them (Indian Express, The Wire) are green marked on the page WP:RSPS and none of the others are yellow or red marked. MrMkG (talk) 16:05, 30 April 2024 (UTC)[reply]
  • Comment - G4 should be clarified that it applies when the page in question is a subset of the deleted page, and, in the meantime, should be interpreted as applying when the page in question is a subset of the deleted page. The recreation after the AFD was a stupid subset of the deleted page. Robert McClenon (talk) 14:21, 30 April 2024 (UTC)[reply]

29 April 2024

2024 Alaska Democratic presidential caucuses (closed)

  • 2024 Alaska Democratic presidential caucuses – This is pretty clearly a "close call [or] controversial decision", which "are better left to admins" (WP:NACD). This should definitely have been closed by an administrator given this, and may also benefit from an extra 7 days to continue to flesh out the arguments within the debate. I would note that strict vote-counting is not how consensus is evaluated, but there was no rationale provided here by the closer as to how they weighed the !votes which can be considered. I therefore vacate and overturn this BADNAC "by an uninvolved administrator in their individual capacity, giving their reasoning". I will relist on today's log for further discussion. Daniel (talk) 01:00, 30 April 2024 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
2024 Alaska Democratic presidential caucuses (talk|edit|history|logs|links|watch) (XfD|restore)

Closed by a non-admin with a merge/redirect decision even though there was no outright or majority consensus to redirect/merge the article. There was a tie vote of keep and redirect/merge with eight each. A tie vote here would mean there is no consensus to remove the article. The article not only met notability requirements but also had enough reliable sources on an election that happened making all the information necessary to have its own article.

All those that voted to redirect/merge mainly opposed because they felt since there was only one candidate, that in itself didn't make it less notable and they provided no evidence to their arguments other than what they felt and said all the sources were routine coverage. Yet, the so-called routine coverage were from reliable sources. The nominator of the Afd even tried to pass off an unreliable source from a right-wing publication as evidence of "in-depth coverage". Routine coverage does not apply to those sources. Elections are not routine coverage even if there is only one candidate on the ballot. And none of these had passing mentions. Yet an election still occurred where votes were cast for the incumbent and were not immediately awarded to the sole candidate by his political party which unlike in previous years where the incumbent president is running for reelection, the primaries wouldn't be held and all the delegates would be awarded to them. The vote this year unlike in Delaware and Florida, was not canceled in Alaska despite there being one candidate.

If this article has to be redirected because there is only one candidate, then all the Republican primary articles for primaries happening in May and June will have to be redirected to the main 2024 presidential election articles for each state. As would contests that already happened such as the 2024 Wyoming Republican presidential caucuses, 2024 American Samoa Republican presidential caucuses, and Democratic contests for Indiana, Nebraska, Montana, and the U.S. Virgin Islands that are happening in May and June. --WikiCleanerMan (talk) 23:23, 29 April 2024 (UTC)[reply]

  • Vacate and enjoin this editor from closing any more AfDs until they've shown they understand WP:BADNAC. This is the second improper closing we've seen from this editor in three days. Not exactly the best way to win the community's trust for their RfA. Owen× 23:38, 29 April 2024 (UTC)[reply]
  • (involved) Leaning relist. I totally disagree with WikiCleanerMan's rationale, I nominated the article for deletion. I think this request for a deleion review stems mostly from WP:ILIKEIT. However, I agree that there is not a clear consensus in the discussion and a relist will hopefully allow more voices to be heard. Esolo5002 (talk) 00:37, 30 April 2024 (UTC)[reply]
If I provided sources to improve the article, and added information to add depth to the article. If I did, then it's not an I like it scenario. It's called improving the article which you hadn't done at all. You redirected it at first, then moved to Afd without starting a discussion on the talk page. You're now casting aspersions on an another editor who provided evidence to his argument. You didn't provide evidence of what made the article not notable and you were cherrypicking various guidlines without making a correct arguments. It is your I didn't like it because you felt some sources weren't up to your standard. Your personal view on sources is not how you should edit. It would appear you still stand by providing an unreliable far-right article to support your argument. A relist is not necessary as it has reached the one week point since the the last relist and it should be closed as no consensus. --WikiCleanerMan (talk) 00:50, 30 April 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.

28 April 2024

Open Book Collective

Open Book Collective (talk|edit|history|logs|links|watch) (XfD|restore)

This was admittedly a low-quorum discussion, but I don't think the arguments against redirection were any good at all. This article was created directly in mainspace by Flavoursofopen, a disclosed COI editor, against the WP:COIEDIT guideline (which I'm assuming they were unaware of). Of the two "keep" votes

  1. Myotus blindly asserts that it appears notable enough without linking any sources
  2. Flavoursofopen's argument for keeping the article is that the OBC is legally separate from the possible redirect target (true, but irrelevant, a redirect would be kept at redirects for discussion).

Mach61 22:31, 28 April 2024 (UTC)[reply]

Pinging @BoraVoro: Mach61 22:42, 28 April 2024 (UTC)[reply]
  • Overturn. WP:BADNAC clearly states: A non-admin closure is not appropriate in any of the following situations: [...] The outcome is a close call [...] or likely to be controversial. Almost any No-consensus closure is bound to be a BADNAC. Whether the proposed redirect is a suitable ATD is something the re-closing admin should determine. Owen× 22:52, 28 April 2024 (UTC)[reply]
  • Vacate per above.—Alalch E. 23:22, 28 April 2024 (UTC)[reply]
  • Overturn – As an editor who was citicized for closing AfDs, it should have been redirected rather than being closed as a no consensus. I do not see this as a "close call" and I do not understand what it is, but I do know that the closure was unjustified. It is better to wait for the closer to be online to question them about the reason for their closure. ToadetteEdit! 10:17, 29 April 2024 (UTC)[reply]
    • "It is better to wait for the closer to be online to question them about the reason for their closure" - question, did you check to see the timeline here before making this statement? The applicant enquired at the closer's talk page at 02:16, 27 April 2024, then waited nearly 48 hours before initiating the DRV at 22:32, 28 April 2024. No issue with Shadow311 not being available (we are all NA for periods at times), but to suggest that Mach61 should have waited longer here before coming to DRV or done something different, as your comment points to, is not accurate or fair in my opinion. Daniel (talk) 17:37, 29 April 2024 (UTC)[reply]
  • Overturn to (soft) redirect. This is a WP:BADNAC, as is just about any no consensus closure or any closure on a relisted discussion, as it is obviously a “close call.” In this particular discussion there is the nom and one redirect !vote based in policy against two keep !votes. One is a well-meaning COI account and the other is a baseless claim of notability. As there is not a quorum, this must be a soft redirect which can be spun back at any time for any good-faith reason without the prospect of re-redirecting without further discussion. I consider vacating for an admin to re-close an acceptable option as well per OwenX though that is my second preference. Frank Anchor 12:23, 29 April 2024 (UTC)[reply]
I only saw the request to revert the close today, sorry. It appears I can't revert the close anymore since the deletion review is happening. Shadow311 (talk) 13:12, 29 April 2024 (UTC)[reply]
You can still reverse your close. Per DRV rules, Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, [...]. Just revert the AFD close, re-add it to the AFD log, and close this DRV with language along the lines of "speedy overturn with consent of AFD closer." (or have an admin do so on your behalf). Frank Anchor 13:22, 29 April 2024 (UTC)[reply]
  • Revert the BADNAC. —SmokeyJoe (talk) 14:23, 29 April 2024 (UTC)[reply]
  • Vacate the WP:BADNAC but endorse outcome per WP:NOQUORUM. -- King of ♥ 18:58, 29 April 2024 (UTC)[reply]
    @King of Hearts This should allow for speedy nomination, right? Mach61 19:08, 29 April 2024 (UTC)[reply]
    Yes, per WP:NPASR. -- King of ♥ 19:59, 29 April 2024 (UTC)[reply]
  • Vacate per WP:BADNAC. No other comment on how this should be closed, but considering this leaned not-keep it should be closed by someone who can implement the full range of closes. SportingFlyer T·C 23:12, 29 April 2024 (UTC)[reply]
  • Vacate - I would Endorse the close if it were closed by an admin, as a valid closure, but I concur with the previous statements that this should have been left for an admin. Robert McClenon (talk) 02:29, 30 April 2024 (UTC)[reply]
  • Comment How "sticky" is a COI? Article creator declares a COI on COPIM, COPIM is directly related to this article... but is that sufficient connection to assume that the original article creator has a COI with respect to this article? It seems plausible, but not incontrovertible, so where do we draw a line? Jclemens (talk) 05:42, 30 April 2024 (UTC)[reply]

25 April 2024

Candidates of the next Australian federal election

Candidates of the next Australian federal election (talk|edit|history|logs|links|watch) (XfD|restore)

Closer erred by draftifying an article about an upcoming event which already contains content about the event and which does not violate WP:CRYSTAL/WP:TOOSOON, and selected an arbitrary time for the article to be moved back into mainspace. Draft space is not a place for currently notable articles, and I believe the keep !votes were disregarded. Asking for this to be overturned to no consensus or keep so the article can be moved back from draftspace. SportingFlyer T·C 05:37, 25 April 2024 (UTC)[reply]

  • I have absolutely no idea how I screwed the template up this badly and every attempt I make to fix it makes it worse. SportingFlyer T·C 05:37, 25 April 2024 (UTC)[reply]
  • Overturn to merge to next Australian federal election as a more sensible outcome all round. Stifle (talk) 08:43, 25 April 2024 (UTC)[reply]
    While Merge may have been a reasonable proposal, it was clearly not supported by a consensus of discussion participants. Onetwothreeip (talk) 09:58, 26 April 2024 (UTC)[reply]
  • Overturn to no consensus (and restore full article) as there were solid arguments made for keep, draftify, and merge. I strongly disagree with J2m5's comment that a no-consensus close should lead to re-draftifying. The April version of the article was substantially different than the version that was draftified in January, thus the draftify result on the January AFD has no bearing on the recent AFD. A merge discussion may be appropriate and can take place on the article talk page. Frank Anchor 12:23, 25 April 2024 (UTC)[reply]
  • Overturn to no consensus (involved) - A neutral closer would find reasonable arguments on both sides (Draft and Keep), relatively similar popularity between the two sides, the contributions to the article during the discussion, and the trend towards Keep against Draft strengthening as the discussion progressed. The closer in this instance did not assess or attempt to assess these elements, and did not provide a reason to find there was a consensus for Draft despite all this; the closure comment looked more like a vote for one side than an assessment of the discussion. The article should therefore be restored, without prejudice to any further deletion or merger discussions. Onetwothreeip (talk) 21:22, 25 April 2024 (UTC)[reply]
  • Overturn to no consensus. Editors did not agree on whether WP:CRYSTAL applies. As the nominator notes, the closer appears to have selected an ad hoc criterion for the article to be moved back into mainspace, an invented criterion of inclusion that is not supported by policy and is contradicted by the nature of drafting being optional. The closer's idea about when the draft should be moved back is the closer's editorial idea, but other editors might have different ideas about when to move back. AfD closer can't prevent good-faith bold mainspacing other than through salting, and salting would have been clearly inappropriate. —Alalch E. 08:39, 26 April 2024 (UTC)[reply]
  • Endorse (involved) Being notable does not mean ready for mainspace which a number of editors made a convincing argument for. That the article continues to have predominantly blank spaces where the future candidates will be speaks volumes. If it is the case that consensus here finds overturn to no consensus then it should still be moved to draft because of the article creator moving it back to mainspace merely three months after the first deletion discussion when there was no substantive difference to the article. I could for all intents and purposes probably have slapped it with a CSD G4 rather than nominating it for the second deletion discussion and my speedy would have been in all likelyhood been accepted. TarnishedPathtalk 09:09, 26 April 2024 (UTC)[reply]
The version of the article is substantially different than the one discussed in January. Therefore a no consensus close MUST result in the article being restored (without prejudice to renomination), and not default to an outdated discussion involving five participants. Likewise, G4 would not have applied for the same reasons.Frank Anchor 11:02, 26 April 2024 (UTC)[reply]
At the time of taking it out of draft into mainspace, merely three months after the first AfD, the only substantial difference (refer to https://en.wikipedia.org/w/index.php?title=Draft%3ACandidates_of_the_next_Australian_federal_election&diff=1217634391&oldid=1199169820 for differences between being put into draft as consequence of the first AfD and being put back into mainspace) was the additional of a number of empty tables to be filled at a later date when candidates appeared. Notably those tables are almost completely empty. TarnishedPathtalk 12:07, 26 April 2024 (UTC)[reply]
  • Endorse good close. Wikipedia-notability does not guarantee the topic a page in mainspace, WP:Consensus May merge a notable topic. Merging may be done from draftspace. The draftified page is very drafty looking. —SmokeyJoe (talk) 14:00, 28 April 2024 (UTC)[reply]
    There was no consensus behind the WP:CRYSTAL rationale and if there's no consensus that there's a barrier to mainspace retention for policy-compliance reasons, there's no objective barrier to overcome to know when to mainspace, and, knowing this, the closer improvised a criterion upon which to allow returning to mainspace, but there's no force behind the improvised criterion, just creating tension, and that tension needs to be resolved by letting this harmless page harmlessly sit in mainspace where it will slowly be improved like any other article. —Alalch E. 23:36, 28 April 2024 (UTC)[reply]
    You have an implied argument that it being in draft will result in it not being improved. That argument is simply not born out by experience. As it stands now we have a article which claims to be about the candidates for the next Australian federal election which has absolutely no idea who the vast majority of those candidates are. That is evidenced by the vast amount of empty space found in the tables contained in the article. TarnishedPathtalk 04:16, 29 April 2024 (UTC)[reply]
  • Endorse close, promote to mainspace as new information has been added since the AFD nomination This is a fair reading of the discussion, and I cannot find obvious error in the top line close. As SmokeyJoe says above, passing WP:N does not necessarily mean a stand-alone page is warranted. That said, looking at the draft page, there does seem to be multiple nominees already determined, so I believe that whatever the result here, this page will be in the mainspace soon. --Enos733 (talk) 02:33, 29 April 2024 (UTC)[reply]
    The majority of the edits since the last move the draft have been small. The only substantial edit was one I preformed adding in archived links to existing references which is not what I would call a change to content. TarnishedPathtalk 04:21, 29 April 2024 (UTC)[reply]
    They are referring to changes made since the article was nominated for deletion, not since the article was moved to draft. Onetwothreeip (talk) 06:16, 29 April 2024 (UTC)[reply]
    That is the scope of the problem - because there are multiple reliably sourced nominees, the topic is no longer TOOSOON and is ready to be moved into mainspace. SportingFlyer T·C 04:34, 29 April 2024 (UTC)[reply]
  • Endorse (involved) there is a premise here that this information is needed now. But looking at Next Australian federal election the election is very unlikely to be called before 3rd of August. Additionally, the redistribution will not be finalised to Q3 or Q4 of this year. So Sept/Oct is a more reasonable time to review draft status. The article is trying to publish too much. Looking at this alternate draft User:J2m5/draft6 we see only 34 potential candidates so far for 150 seats. But the tabular format of this article reserves space for approx 600 to 700 potential candidates, many who will never actually appear. Now senate potnetial candidates have been added, but these are the last to be pre-selected as they only represent a state and not a single electorate. Hence the unbalanced look of largely empty tables. It also has too much conjecture. The seat of North Sydney may well be abolished, so better to wait for the redistrubtion than list speculative pre-selected candidates. The issue of party pre-selection ballots were deemed as inappropriate and often unsourced in an earlier article Wikipedia:Articles for deletion/2023–24 Liberal Party of Australia preselections, but they have appeared again in this article, contrary to an AfD decision. A entry is made for an attempt by 2 candidates to share a seat in Higgins in Victoria. But this is an impossibility as only a single name can appear on the candidate nomination form. This non-encylopedic approach should be cleared up before this article can be considered for mainspace. Teraplane (talk) 07:04, 29 April 2024 (UTC)[reply]
    But the tabular format of this article reserves space for approx 600 to 700 potential candidates, many who will never actually appear. This is completely untrue, the tables contain spaces for parties which contest all the seats. Regardless, this discussion isn't to determine whether the article should be deleted, but whether the closure of the deletion discussion was adequately representative of the discussion. Onetwothreeip (talk) 09:57, 29 April 2024 (UTC)[reply]
  • Endorse as a valid close. The question at DRV is whether the close was a valid close, not whether another close would have been valid. Robert McClenon (talk) 14:09, 30 April 2024 (UTC)[reply]


22 April 2024

The following is an archived debate of the deletion review of the page above. Please do not modify it.
Nadia Naji (talk|edit|history|logs|links|watch) (XfD|restore)

I believe my rationale for delete carried more weight than those of the other two editors who voted to keep. I pinged Randykitty to know the rationale for 'No consensus' where they said there were policy-based arguments for and against deletion., but I do not see any policy based keep votes on the AfD apart from the IP's final comment. Jeraxmoira🐉 (talk) 20:08, 22 April 2024 (UTC)[reply]

  • Endorse the keep votes are weakly justified, the delete vote stands alone, there's plainly no consensus for any kind of action. BrigadierG (talk) 20:16, 22 April 2024 (UTC)[reply]
    I don't think standing alone matters here, rather what's important is the deletion rationale, as AfDs are not based on votes. Please see bullet points #6, #7 and #12 on WP:DISCUSSAFD. Jeraxmoira🐉 (talk) 20:37, 22 April 2024 (UTC)[reply]
  • Endorse. Despite the AFD being listed for a month, there is not a WP:QUORUM to delete the article, no matter how weak the "keep" votes are. While a soft delete could be possible without a quorum, the article would need to be fully restored upon any good-faith request (e.g. the "keep" votes in the AFD). Therefore, no consensus is clearly the correct result. Frank Anchor 20:33, 22 April 2024 (UTC)[reply]
    This was not the reason the closing admin gave on their talk page. Even if the closer's rationale was based on WP:QUORUM, I believe the three other common outcomes listed on WP:NOQUORUM apart from relisting would have been more suitable here. Jeraxmoira🐉 (talk) 20:54, 22 April 2024 (UTC)[reply]
    The end result is the most important aspect. The end result was correct. Frank Anchor 22:46, 22 April 2024 (UTC)[reply]
  • Endorse There is simply no consensus to delete that article. I've been in frustratingly similar situations before considering I don't necessarily see clear good sources. No reason you can't wait six months and try again. SportingFlyer T·C 22:13, 22 April 2024 (UTC)[reply]
  • Endorse. Even if there were no Keep views at all, the most the appellant could hope for is a soft delete, to be instantly restored at the first good-faith request, as Frank Anchor explained. With any opposition at all to deletion, no matter how weak, we won't delete based on a solitary !vote. Jeraxmoira, you've been here long enough to know that. Treat this a contested PROD, and move on. Owen× 22:45, 22 April 2024 (UTC)[reply]
  • Endorse. There was no consensus to be found from the limited participation. Just because you disagree with their opinion doesn't mean they weren't policy based. FWIW, an editorial discussion might find an ATD such as Groen_(political_party)#Party_chairperson if that's of interest. Honestly I think minor European political parties are of relatively little interest here. Star Mississippi 01:39, 23 April 2024 (UTC)[reply]
  • Comment Addressing the comments above, I find it interesting how everyone interprets the policies to suit the AFD outcome. What's the point of waiting 6 months when the IP arguments were based on WP:IAR, automatic notability and The number of sources is only going to rapidly increase over the coming weeks and months. Regarding everyone's argument about the AFD receiving no quorum, the common outcomes at WP:NOQUORUM are:
  • closing as "no consensus" with "no prejudice against speedy renomination" (NPASR)
  • closing in favour of the nominator's stated proposal
  • soft deleting the article.
I believe NPASR would have been more suitable here considering the format of AFD clearly mentions "Unregistered or new users are welcome to contribute to the discussion, but their recommendations may be discounted if they seem to be made in bad faith (for example, if they misrepresent their reasons). Conversely, the opinions of logged in users whose accounts predate the article's AfD nomination may be given more weight when determining consensus.". PamD's keep did not have WP:THREE, so I feel this AFD was gamed into no consensus by the IP editor. FWIW, I was okay with ATD-I and ATD-R as mentioned in my AFD comment.
I rest my case at this point as I can see that many of the arguments are solely based on WP:QUORUM, but the surprise is how none of you wanted to argue the common outcomes that is also listed on WP:QUORUM. Cheers Jeraxmoira🐉 (talk) 06:20, 23 April 2024 (UTC)[reply]
The first part of your comment seems to show concern that @Randykitty didn't follow the letter of NOQUORUM as you read it, but then you cite THREE which isn't even a guideline but an editor's opinion. It really isn't possible to have it both ways when AfDs will almost always come down to some subjectivity. You believe NPASR would be suitable, but that's a N/C which you're contesting here. I ask with no sarcasm, you realize the ability to renominate isn't contingent on the closer typing exactly that acronym, right? You still retain that right because you can cite limited participation. Star Mississippi 11:40, 23 April 2024 (UTC)[reply]
Randykitty did not close the AfD citing WP:QUORUM. Only the editors here argued that there was no quorum to achieve consensus, for which I highlighted the common outcomes. And no, I did not know that we can cite limited participation and work around what's on WP:2MONTHS. If that is the case, then this DRV can be closed as withdrawn. Jeraxmoira🐉 (talk) 15:26, 23 April 2024 (UTC)[reply]
  • Endorse, could not possibly have been closed any other way. Stifle (talk) 07:25, 23 April 2024 (UTC)[reply]
  • Endorse. There's no policy grounds on which to simply discount the keeps. Weak-ish argument =/= discountable !vote.—Alalch E. 13:49, 23 April 2024 (UTC)[reply]
  • Endorse - The appellant is asking to overturn to Delete, but, if the closer had said Delete, we would be overturning that to No Consensus. Robert McClenon (talk) 14:35, 23 April 2024 (UTC)[reply]
  • Overturn to keep Nom admits there are two RS in the discussion, asks for a third: Thank you, that makes two sources. If you can share one more, I'll be happy to withdraw my nomination. That's 3-0 keep, even if the nom isn't inclined to admit that 'multiple' includes the number two. Jclemens (talk) 16:09, 23 April 2024 (UTC)[reply]
    Touché! I'm still happy with no consensus, but yours is indeed an apt response to this type of vexatious relitigation. Owen× 17:33, 23 April 2024 (UTC)[reply]
    OwenX: Would you mind explaining how this is a type of vexatious relitigation? If not, please retract your statement. Jeraxmoira🐉 (talk) 18:01, 23 April 2024 (UTC)[reply]
    Everyone in this DRV has already explained to you, in every possible way, how there was nothing close to a consensus to delete in the AfD. And yet, you persist in your demand, because you feel the language used by the closing admin did not adequately validate your nomination, nor properly discard the Keep views. Once again: even without the Keep !votes altogether, there was still no consensus to delete, except as a soft delete, which is clearly contested. And since you admit to the existence of two sources providing significant coverage, even your solitary delete !vote loses its basis. The only respectable thing for you to do at this point is to promptly and unconditionally withdraw your appeal, and request a speedy close to this pointless waste of time. Owen× 18:32, 23 April 2024 (UTC)[reply]
    I did not persist in my demand. My final argument was made here and I only replied to Star Mississippi after that. I never made any arguments to the other endorsers who voted after my final comment, so if you still feel it was a type of vexatious relitigation, then I cant help it. And I did not realize my above withdraw statement was a conditional one until you highlighted it now. This DRV can be speedy closed as withdrawn unconditionally by any editor/admin. Jeraxmoira🐉 (talk) 19:24, 23 April 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.

20 April 2024

The following is an archived debate of the deletion review of the page above. Please do not modify it.
Indian Motortcycle Manufacturing Company (talk|edit|history|logs|links|watch) (article|restore)

Plausible typo ("R" and "T" are next to one another on a QWERTY keyboard) which was speedy deleted without proper discussion. --Jax 0677 (talk) 15:23, 20 April 2024 (UTC)[reply]

  • Reply - "Indian Motortcycle Manufacturing Company" was speedy deleted, and that is the term being contested. Any resulting double redirects will likely be fixed by a bot. Also, your signature is on a different line than your response. --Jax 0677 (talk) 21:50, 20 April 2024 (UTC)[reply]
    Sorry, to be clear, @Zzuuzz: moved it without a redirect-essentially a deletion and @Deb: speedied it. I wasn't sure which of the two actions you were contesting. Star Mississippi 01:49, 21 April 2024 (UTC)[reply]
  • In practice, very few typos can escape an R3, as opposed to misspellings and misnomers - typically only common typos are kept. Even more so when it's part of a longer title - while "motortcycle" gets a surprising number of ghits, the phrase "Indian Motortcycle Manufacturing Company" appears nowhere on the Internet except Wikipedia and its mirrors. Gripping hand, I'd be more sympathetic to this if motortcycle had ever been created. A typo does not become plausible just because you made it once. —Cryptic 02:46, 21 April 2024 (UTC)[reply]
  • Weak Endorse as per Cryptic. If a typo only happened once, that means that it was possible, but not that it was plausible. Robert McClenon (talk) 05:31, 21 April 2024 (UTC)[reply]
  • Comment Well... It's a CSD contested by an editor in good standing, so I guess the by-the-book answer would be send it to RfD, but it sounds like there's a better/alternative way forward per Star Mississippi. I agree that possible and plausible are a pretty far stretch here, but that's for RfD, rather than a CSD or DRV. Jclemens (talk) 03:34, 22 April 2024 (UTC)[reply]
  • Comment I feel like people are overlooking how easy it is to accidentally create a redirect without really intending to, as it's obvious the creator of this redirect did. This particular typo can only happen when someone presses two keys simultaneously, not when someone accidentally presses the wrong key. How many people are likely to do that? Deb (talk) 10:06, 22 April 2024 (UTC)[reply]
  • I would say that the typo version was the one I deleted (or suppressed-redirect) at this title. The recreation of the redirect was a deliberate reconstruction of that typo (likely because it was linked from ANI). Incidentally I speedy-deleted Indian Mototcycle Manufacturing Company (with the 't' but without the 'r') in the same session as I did this redirect-suppress, which I see no one is complaining about. My own view is that the deletion was legitimate, and it should be endorsed without prejudice to recreation. -- zzuuzz (talk) 12:19, 22 April 2024 (UTC)[reply]
  • Reply - It is not as rare as you might think. In any event, per procedure, this likely does need to go through WP:RFD. --Jax 0677 (talk) 12:24, 22 April 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.

17 April 2024

The following is an archived debate of the deletion review of the page above. Please do not modify it.
Quantum economics (talk|edit|history|logs|links|watch) (XfD|restore)

The article was proposed for deletion, I contested it but a decision was made, without consensus or further discussion, to merge with another article Econophysics. As explained on the Econophysics talk page, this is not an appropriate merger. I therefore ask that the decision be postponed until there has been a suitable discussion period. Sjm3 (talk) 12:47, 17 April 2024 (UTC)[reply]

  • Endorse. The appellant is incorrect in all their claims. There was a full week of discussion, as required, and there was clear consensus. All agreed to the merge, except the appellant, who is also the author of the page, and whose 113 edits on en-wiki are almost all related to that article. A classic case of WP:SPA who is WP:NOTHERE to improve an encyclopedia, but likely to promote their own research. Owen× 13:03, 17 April 2024 (UTC)[reply]
    The claims I am making are that (a) there was no further discussion, and (b) this is not an appropriate merger. For (a) the editor says there was a full week of discussion, but there was no reply to my comment. This therefore seems a narrow definition of discussion, and in particular there was no further discussion of my comment. Further to the remark about my editing history, a decision about maintaining a page should surely be based on the content of the article. Note also that the article cites work by some 20 researchers. For (b), this is not an appropriate merger because quantum economics is not considered to be a branch of econophysics. The merge decision appears to be based on a single paper (and the only one published in the last five years) which mentions "quantum econophysics" in the title (Arioli and Valente, 2021). That 2021 paper in turn seems to have got the name "quantum econophysics" either from an unpublished paper from 2007 (Guevara, 2007) or a chapter in a 2014 book (Schinckus, 2014). More recent works do not appear to use this phrase. Quantum economics is distinct from econophysics because it does not focus exclusively on things like financial statistics and time series, but also considers broader effects from quantum social science such as quantum cognition and quantum game theory. Sjm3 (talk) 14:52, 17 April 2024 (UTC)[reply]
  • Endorse - The discussion was open for the requisite period of time and the closure as merge is in line with the consensus. where one of the keep !votes agreed that a merge was also okay. -- Whpq (talk) 15:05, 17 April 2024 (UTC)[reply]
    Please see my reply to the previous comment. The consensus excluded the author and there was no attempt to discuss with the author. I find it hard to understand how it is okay to merge one article with another when the author is giving specific reasons why the merge of the two subjects is inappropriate. Sjm3 (talk) 15:22, 17 April 2024 (UTC)[reply]
    You seem to be under the impression that the author of an article gets a veto on anything done with that article. I'm sorry, but that is not how Wikipedia works. There is no WP:OWNERship of pages here. Your opinion about that article carries as much weight as the opinion of anyone else about it. Or possibly less, seeing as you are woefully unaware of our policies and guidelines, and seem to be here solely to promote the subject matter of that article. Owen× 15:29, 17 April 2024 (UTC)[reply]
    Please read my reply again. I am not claiming that authors should get a veto. I am saying it is inappropriate to merge an article with another, without further discussion, when the author is giving valid reasons why the fields are not the same. For the statements that I am "solely here to promote the subject" and not "to improve an encyclopedia", and so on, please note that the article is written in good faith, and also that Wikipedia benefits from the input of both specialists and generalists. Sjm3 (talk) 15:39, 17 April 2024 (UTC)[reply]
  • Endorse per the above, with no prejudice against it being split out again when sufficient reliable sources have been identified such that it will no longer fit (either based on size or topic attributes) with the recently-targeted article. Jclemens (talk) 15:32, 17 April 2024 (UTC)[reply]
    Again, I have given reasons why the field is distinct from econophysics, here and on the page itself. What I had expected from the discussion process was that I would be told why the article was being deleted, and would be given a chance to address these concerns by answering comments and improving the manuscript. Instead a decision was simply made to merge with a page suggested by one of the editors. Rather than immediately merge the article with something inappropriate, I would therefore request the editors tell me what the article needs in order to work as a stand-alone article, and give me a reasonable opportunity to make those changes and additions. Further to "sufficient reliable sources" note that I have now added several, including some from a new journal Quantum Economics and Finance from Sage Publications. Sjm3 (talk) 16:06, 17 April 2024 (UTC)[reply]
  • Endorse as a valid closure and as the correct result:
      • Either Merge or Relist would have been valid conclusions by the closer.
      • The appellant says that the decision to Merge was made without consensus or further discussion. There was consensus. The reason that there was no further discussion is that the originator responded on day 6 out of the usual 7 days for discussion. The closer was not required to Relist because the originator only edits sporadically.
      • I'm a chemist, not an econophysicist, so I read the original article and the article that it was merged into. I concur with User:XOR'easter (who is a physicist) that quantum economics and econophysics are a variety of different related topics, and that there is no need for a separate article for each of them. So I would have !voted Merge if I had taken part in the AFD.
      • In other words, it is a valid merge. Econophysics is very much a mixed bag, and quantum economics is another element to go in the mixed bag.
      • DRV is not AFD Round 2, but the appellant is using DRV as AFD Round 2, and so is getting the further discussion that they requested (even if this is a misuse of DRV). So we have reason to know what a Relist would have done, which is to support the Merge. Robert McClenon (talk) 18:31, 17 April 2024 (UTC)[reply]
  • Endorse as participant. A consensus was arrived at in the ordinary way and correctly evaluated. We're done here. XOR'easter (talk) 18:53, 17 April 2024 (UTC)[reply]
  • Endorse was very clearly a merge result here. SportingFlyer T·C 21:06, 17 April 2024 (UTC)[reply]
  • Endorse . Content headed for merger from an AfD can be rejected at the target article as an editorial decision. AfD can't decree insertion of unwanted content into an article if the consensus of editors on that article's talk page is to reject the addition. Therefore, this should be resolved editorially, and a deletion review is not needed. The consensus was to merge, but the practical outcome could be simple redirection. It is worth noting that this is one of the problems with using AfD to merge and with AFD merge outcomes. It's not a problem with the real and true merger process because that process considers the target article and is normally conducted on the target article's talk page (for this reason), while "merge AfDs" almost never seriously consider the target articles, as there is too strong of a focus on deletion/retention of the nominated article and it's difficult for participants to adopt the correct perspective that merging is keeping content.Alalch E. 01:13, 18 April 2024 (UTC)[reply]
  • Endorse consensus was clear to merge. However, relisting would have also been acceptable due to reasonable keep votes being present and relatively low attendance. What specific content is to be merged can be discussed at the target’s talk page. Frank Anchor 12:33, 18 April 2024 (UTC)[reply]
  • Endorse. The discussion has already happened; DRV is not AFD round 2. Stifle (talk) 14:46, 22 April 2024 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Archives, by year and month
Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2024 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2023 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2022 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2021 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2020 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2019 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2018 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2017 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2016 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2015 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2013 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2012 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2011 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2010 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2008 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2007 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec