Jump to content

Wikipedia:Deletion review

From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:DRV)

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, and 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=2025 June 22}}</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=2025 June 22}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2025 June 22|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.

Examples of opinions for an article that had been deleted:

  • *'''Endorse''' The original closing decision looks like it was sound, no reason shown here to overturn it. ~~~~
  • *'''Relist''' A new discussion at AfD should bring a more thorough discussion, given the new information shown here. ~~~~
  • *'''Allow recreation''' The new information provided looks like it justifies recreation of the article from scratch if there is anyone willing to do the work. ~~~~
  • *'''List''' Article was speedied without discussion, criteria given did not match the problem, full discussion at AfD looks warranted. ~~~~
  • *'''Overturn and merge''' The article is a content fork, should have been merged into existing article on this topic rather than deleted. ~~~~
  • *'''Overturn and userfy''' Needs more development in userspace before being published again, but the subject meets our notability criteria. ~~~~
  • *'''Overturn''' Original deletion decision was not consistent with current policies. ~~~~

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. Deletion review is facilitated by succinct discussions of policies and guidelines; long or repeated arguments are not generally helpful. Rather, editors should set out the key policies and guidelines supporting their preferred outcome.

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 or sockpuppet 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".
Template:Transl (talk|edit|history|logs|links|watch) (XfD|restore)

The RfD closure failed to account for the fact that Template:Transl, unlike the other redirects bundled in that nomination, was the long-standing name of Template:Transliteration since 2007, which was moved away from that title only in 2022. Although replacement by bot was mandated, deletion still broke a lot of historical references. While there may have been consensus to delete the three other redirects, several participants !voted specifically to keep Template:Transl, and I do not believe consensus was in support of deleting it. --Paul_012 (talk) 09:01, 22 June 2025 (UTC)[reply]

  • Issue raised with closer DMacks here. Note that the closure was also challenged by jlwoodwa here and by jacobolus here. --Paul_012 (talk) 09:06, 22 June 2025 (UTC)[reply]
  • Indeed, this was a serious mistake of discussion closure which substituted the closer's personal preference for community consensus, and caused (and will continue to cause) harm to Wikipedia, especially since our software has never properly handled transclusions when viewing historical versions of pages, so now almost 2 decades of historical permalinks are going to have broken transliterations on them. –jacobolus (t) 11:01, 22 June 2025 (UTC)[reply]
  • I stand by my closure (I think I responded to each concern raised on my talkpage there, with specificity...can find the links later if needed). While it's definitely true that not all four involved templates had equally strong support, I saw the general concern did apply to all of them and was more supported than not by the guidelines and their weighting of pros/cons/etc mentioned. I have not been involved in this template-area and do not feel I raised new concerns or other judgement of my own on the issues beyond evaluating what others stated. As I have said, I made no prejudice against non-ambiguous forms. I'm having trouble finding where preserving the original/complete viewability of historial revisions is mentioned (and prefereably pointing to a policy or guideline) by a comment in the DRV. DMacks (talk) 11:33, 22 June 2025 (UTC)[reply]
    • The harm in deleting such redirects is, I believe, described by the second main consideration under WP:R#HARMFUL. Such deletions aren't prohibited, but should only be considered when the concerns are demonstrably outweighed by the harm caused by the existence of the redirect. --Paul_012 (talk) 12:40, 22 June 2025 (UTC)[reply]
    • Regarding the talk page responses, I already linked the archived discussions above. Apologies on my part for not responding further before starting the DRV, but the discussion had already been archived and given our conflicting opinions I don't think further discussion could have preempted the need for DRV. --Paul_012 (talk) 12:48, 22 June 2025 (UTC)[reply]
Manchester Freedom (talk|edit|history|logs|links|watch) (XfD|restore)

Discussion was left open for nearly a month and only commenter stated things about the article's references that patently inaccurate. Close was a no consensus. If there were no commenters at all, that may be appropriate but the inaccurate comment should have been taken into account in the closing and it may have persuaded others not to participate in the discussion. I ask for a relisting to obtain at least one pertinent viewpoint. Royal Autumn Crest (talk) 17:19, 21 June 2025 (UTC)[reply]

  • Endorse as the right closure - No Consensus is always unsatisfying, but is sometimes really the lack of a consensus. The appellant/nominator requests another relist, but it was already relisted three times. The appellant disagrees with the Keep voter about the references; that disagreement is a lack of a consensus. Any other closure or another Relist would have been erroneous. Robert McClenon (talk) 17:34, 21 June 2025 (UTC)[reply]
  • Endorse I can't remember when a discussion was relisted four times. More discussion would have been better, but closers must only act with the information that is provided. --Enos733 (talk) 22:01, 21 June 2025 (UTC)[reply]
  • Endorse Simply enough, and as frustrating as it might be, I cannot advocate for overturning a discussion to delete when no one apart from the nominator agreed it should be deleted, and there was more than one participant. I'd also mention that if anyone wants to save this article by adding clear sources, now is the time... I see a discussion about it on the American football talk page. SportingFlyer T·C 22:08, 21 June 2025 (UTC)[reply]
    • Comment Outside of the inaccuracy in the only other comment in the AFD, I can't disagree with the other people who are endorsing the closer's decision. AFDs are not votes, so comments in the discussion that are not accurate should not be taken into account by the closer. Royal Autumn Crest (talk) 13:17, 22 June 2025 (UTC)[reply]
  • Comment @Royal Autumn Crest, if you think my comments were "patently inaccurate," I think you should have at least pinged me to the deletion review Jahaza (talk) 01:26, 22 June 2025 (UTC)[reply]
  • I informed you that your comment was inaccurate during the AFD. This is not about the article, this is about the closure of the AFD. Royal Autumn Crest (talk) 13:17, 22 June 2025 (UTC)[reply]
    You also failed to add the appropriate notifications to Manchester Freedom and to the AFD discussion, which meant anyone with those pages on their watch list wouldn't have seen the deletion review that way. Jahaza (talk) 01:33, 22 June 2025 (UTC)[reply]
    That's not accurate. The instructions for deletion review only require notifying the closer of the afd. Royal Autumn Crest (talk) 13:17, 22 June 2025 (UTC)[reply]

Liz Lamere (closed)

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

Procedural nomination. Original AFD nominator has made a report at WP:ANI questioning a non-admin closure and suspecting canvassing, for which DRV is the appropriate venue. See Wikipedia:Administrators'_noticeboard/Incidents#Non-Admin_closure_of_an_AfDRobert McClenon (talk) 16:12, 21 June 2025 (UTC)[reply]

TheLongTone's ANI report was I recently put up an article Liz Lamere for deletion. The discussion seemed suspect to me, with a plethora of contributions from IP editors & very new accounts- leading me to suspect a degree of canvassing was going on . Now I see that the discussion has been the subject of a non-admin closure by Allblessed, a relatively new editor (30th March this year). Apart from the (imo) spam contributios, there were only two votes that looked kosher to me, one keep and one delete. TSventon (talk) 16:29, 21 June 2025 (UTC)[reply]
I notice that this was Allblessed's first AfD closure, they have also relisted a discussion. TSventon (talk) 17:07, 21 June 2025 (UTC)[reply]
  • Relist. Reading through the deletion discussion, it's clear that most of !votes run counter to our policies and guidelines; for example, by considering trivial mentions as legitimate sources, implying that notability is inherited, saying that record releases on non-notable/unimportant labels should count towards notability, etc. Woodroar (talk) 18:25, 21 June 2025 (UTC)[reply]
  • Comment Disclosure: as I was part of the deletion discussion, therefore I am WP:INVOLVED. While there were !votes from new/IP voters in the discussion, however I must fundamentally disagree with the comment from TheLongTone that appears to be characterising my !vote as "spam". In fact, there are 3 "keep" votes from editors with >5 year accounts, and I do request the "spam" insinuation is retracted. Regarding the close: in the discussion I identified a number of secondary sources with non-trivial coverage of the direct works of the subject, which are reliable, and that argument was never rebutted. ResonantDistortion 19:44, 21 June 2025 (UTC)[reply]
  • Relist It's not really a BADNAC except for all of the blatant canvassing, but it needs to be closed by a competent administrator. (I also wouldn't mind !voting now that I've looked at it.) SportingFlyer T·C 22:13, 21 June 2025 (UTC)[reply]
  • Endorse The question we have at DRV is whether the closer interpreted the consensus in the AFD correctly. From the discussion: the nominator and one other editor suggested that the coverage was largely about the subject's spouse or interviews about the subject (not meeting WP:GNG). Four of the five keep votes (discounting the IP comments for a moment), suggested that the sourcing would pass GNG.
While the closer is expected to discount !votes that are contrary to policy and guidelines, and in this case, whether we see the !vote as 7-2, 4-2, or something else, it is clear that a strong majority of participants concluded that the sourcing was sufficient to meet GNG. Thus, a keep close was within the discretion of the closer, and was far from a WP:BADNAC. --Enos733 (talk) 22:25, 21 June 2025 (UTC)[reply]
Given that the closer has entered a bolded relist below, I intend to relist this speedily. As the only endorse so far do you have any objections Enos733? Alpha3031 (tc) 09:25, 22 June 2025 (UTC)[reply]
  • Relist, as the closer did not take into account the level of canvassing, and taking it into account places the discussion outside of the case of beyond doubt a clear keep described at WP:NACAFD. Chaotic Enby (talk · contribs) 22:34, 21 June 2025 (UTC)[reply]
    I can accept that the IP votes may be treated with suspicion, but it is unclear to the degree that canvassing may have taken place (and the other concern, length of tenure of named editors was debunked). In this case, the allegation of canvassing was only raised by the nominator as a suspicion. IP editors in AFD are permitted. Even if there was late canvassing, the IP !votes occurred after all other editors commented (at least once) in the discussion and at the time, there were 5 comments supporting keeping the article and 2 editors supporting deletion. So, I cannot see this as "blatant" canvassing, and I lean to seeing any suspicious canvassing as not affecting the consensus to keep the article. (As an aside, I would be more worried that the IP comments are socks, rather than being canvassed) - Enos733 (talk) 00:17, 22 June 2025 (UTC)[reply]
  • Relist and see what further discussion gets. I would be against a delete closure at this stage despite the apparent canvassing or LOUTsocking, but it's not been relisted so a no consensus isn't appropriate yet, either. Jclemens (talk) 06:21, 22 June 2025 (UTC)[reply]
  • Relist Since there is a serious concern about the outcome of my closure, I’ll suggest a relist for a fair consensus, But I’ll say it again there where keep votes from eligible editors even if some IPs where around, those where the first vote I saw for a keep. Still a relist of the discussion is fine. For me I think the discussion is a non consensus. Allblessed (talk) 06:41, 22 June 2025 (UTC)[reply]
    Further I’ve dropped my remark on the closure, my closure was very fair. Allblessed (talk) 06:57, 22 June 2025 (UTC)[reply]
  • Relist per Woodroar. A competent close would have taken account of what was clearly in an influx of newish and IP editors. TarnishedPathtalk 07:35, 22 June 2025 (UTC)[reply]
  • Relist: The question isn't whether the closure was "fair." The question is whether it was competent. "Closers are also required to exercise their judgment to ensure that any decision complies with the spirit of Wikipedia policy and with the project's goals ... Consensus is not determined by counting heads or counting votes ... The closer is there to judge the consensus of the community, after discarding irrelevant arguments: those that flatly contradict established policy, those based on personal opinion only, those that are logically fallacious, and those that show no understanding of the matter of issue." (emphasis mine). Any closer has the responsibility not merely to count heads, but: "Wikipedia core policies, which requires that articles and information be verifiable, avoid being original research, and be written from a neutral point of view ... are not negotiable, and cannot be superseded by any other guidelines or by editors' consensus." Ravenswing 07:51, 22 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Draft:Chinmay Gaur (talk|edit|history|logs|links|watch) (restore)

Requesting temporary restoration of Draft:Chinmay Gaur (deleted on 14 March 2025 by Jimfbleak under G11). I am the creator (User:Rajat K26). I want to retrieve the content to rewrite it in a neutral, encyclopedic tone, remove promotional material, and resubmit via Articles for Creation. Rajat K26 (talk) 11:11, 21 June 2025 (UTC)[reply]

  • Remove the promotional material and there'd be practically nothing left. Strongly advise you stop attempting to create articles and try to work on existing ones instead if that's the way you write. —Cryptic 11:33, 21 June 2025 (UTC)[reply]
    • For interested nonadmin onlookers, there's some quotes from the draft at User talk:Rajat K26#Reply. I'll add "Chinmay Gaur began his professional journey as a faculty member at the Music College in Vadodara, ..." to the list, which - as usual - is an excellent predictor that the page as a whole is G11able: there's exactly one fully-neutral sentence in the entire draft, the one stating his birthdate and -place. —Cryptic 20:03, 21 June 2025 (UTC)[reply]
  • Cryptic, also the refs are largely junk, including YouTube, IMDB and Amazon, and I suspect that there may be a COI Jimfbleak - talk to me? 16:53, 21 June 2025 (UTC)[reply]
  • Comment - It is always a good idea to keep one's own copy of one's work, including but not limited to Wikipedia articles. It should not be the responsibility of Requests for Undeletion or Deletion Review to retrieve pages that were deleted either speedily or by AFD so that the originator can work on them. The originator should have kept a copy. If they don't, they can create the page again from the sources, which they already did once. Robert McClenon (talk) 04:58, 22 June 2025 (UTC)[reply]
  • Deny Temporary Restoration - The applicant is asking the restoring admins to write their article for them. Robert McClenon (talk) 04:58, 22 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Category:Rachael MacFarlane albums (talk|edit|history|logs|links|watch) (restore)

Hayley Sings is her only album she's made and she hasn't done another album 13 years since 2600:8801:8E:9900:3906:3A8C:E813:1274 (talk) 13:43, 19 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
  • The Pizza Meter – The Department of Redundancy Department is closed. This did not need to be here, but it also does not need to go to REFUND to effect a decision that there is no opposition to here and we/me are capable of implementing. The Draft is restored for improvement and if needed on mainspacing, a new AfD can happen. Star Mississippi 02:26, 18 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
The Pizza Meter (talk|edit|history|logs|links|watch) (XfD|restore)

During the original AfD, the article was deleted on the basis that, at the time, there was insufficient third-party coverage demonstrating notability. However, in light of recent events in the Middle East, a flood of news coverage has suddenly popped up over the topic: news.com.au, euronews, The Guardian, Economic Times, Futurism, Newsweek, The Telegraph, Haaretz. If the page is undeleted, I would suggest renaming it to Pizza Index, as that appears to be the WP:COMMONNAME. --benlisquareTCE 07:05, 17 June 2025 (UTC)[reply]

  • Allow recreation (i.e., undelete to draft or sandbox for update) per the new sourcing. This should probably not have been deleted previously; I suspect an appropriate search for sources at that time would have found more. No objection to renaming, anyone can nominate at any time, etc. Jclemens (talk) 07:10, 17 June 2025 (UTC)[reply]
  • As AfD closer, I do not object to a recreation using the new sources. Sandstein 07:43, 17 June 2025 (UTC)[reply]
  • As a delete !voter I'm still not sure this will pass our guidelines, but I have no problem with a new draft. SportingFlyer T·C 08:08, 17 June 2025 (UTC)[reply]
    I think the evidence that this wasn't even the COMMONNAME suggests an article could have been built with a bit more digging, but given the sourcing above, it's an academic question. Jclemens (talk) 18:53, 17 June 2025 (UTC)[reply]
    I think WP:NOTNEWS could be at play, though. I only see one article from before the last couple days. SportingFlyer T·C 22:39, 17 June 2025 (UTC)[reply]
  • Restore to mainspace. The AfD was closed correctly, but new sourcing is prima facie evidence of notability, sufficient at least to require renomination if contested. The deleted version wasn't great, but there's no reason to redo that work. Owen× 12:41, 17 June 2025 (UTC)[reply]
  • Endorse the 2024 close, but see at the top of this noticeboard: Deletion review should not be used:… 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, and if your new version does not qualify for deletion then it will not be deleted The requester has the right to create a draft, to submit a draft for review, or to create a new article subject to AFD. Robert McClenon (talk) 18:03, 17 June 2025 (UTC)[reply]
  • Sure, a new article could be written from scratch, but personally, I'd rather not reinvent the wheel if editors have already written a half-finished article that just needs fixing up. Time is finite, after all. --benlisquareTCE 18:34, 17 June 2025 (UTC)[reply]
These questions should not come to DRV. If you’re unsure and not wanting to waste time, request undeletion to draftspace at WP:REFUND. Improve the deleted article by removing poor sources and adding new better sources. Identify the best WP:THREE sources, by citing them first, or on the talk page, and seek review.
If you’re more confident, do the above but move it yourself back to mainspace. Th8s is ok, if you’re sure the sources are better, and as the AfD was so long ago.
DRV is not the right forum for requesting review of new sources. SmokeyJoe (talk) 22:23, 17 June 2025 (UTC)[reply]
  • For the record, I absolutely believe this is the proper forum - this is where the community gains consensus on what should be done with new information after a deleted recent AfD. SportingFlyer T·C 22:39, 17 June 2025 (UTC)[reply]
    And I strongly disagree. You are advocating scope creep.
    If every such case came to DRV, DRV would be overwhelmed. AfC and AfD are the forums that are appropriate. Even if DRV says “yes”, it confers no protection from being sent to AfD, and thus nothing has been achieved over the proponent simply recreating in mainspace with their new sources, except distracting DRV.
    There is no challenge to the AfD, and so this nomination should have been speedy closed.
    If the deleting admin had said “no”, or the REFUND to draftspace was refused, or an unsalting request was denied, then DRV is appropriate, when there is something to review. SmokeyJoe (talk) 23:13, 17 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Elito Circa (talk|edit|history|logs|links|watch) (XfD|restore)

Elito Circa, also known as Amangpintor, is a widely recognized Filipino visual artist noted for pioneering the use of human hair and indigenous materials in painting. He has been featured in national and international media, including Ripley's Beleive It Or Not, Reuters, CNN, SBS Australia, Philippine Daily Inquirer, GMA Network, and ABS-CBN. His story is documented in the National Commission for Culture and the Arts (NCCA), World Vision, Rotary International and Embassies and his works are displayed in public museums and Galleries. New reliable secondary sources are now available, proving long-term notability. 121.200.4.157 (talk) 11:04, 16 June 2025 (UTC)[reply]

FEATURED REFERENCES
The following discussion has been closed. Please do not modify it.


6 Extraordinary Mediums Filipino Artists Wield in their Works https://feuadvocate.net/6-extraordinary-mediums-filipino-artists-wield-in-their-works/

Bangladesh News https://www.anandabazar.com/lifestyle/filipino-painter-elito-circa-uses-own-blood-as-the-medium-for-his-painting-dgtl/cid/1392622

India News https://zeenews.india.com/hindi/off-beat/philippine-artist-elito-circa-painting-using-own-blood-wish-to-creat-world-record/1490492

Filipino painter Elito Circa uses own blood as the medium for his art https://nypost.com/2022/12/17/filipino-painter-elito-circa-uses-blood-for-his-art/

Environmental Advocacy Certificate https://ecertificate.seameo.org/certificates/321/SEAMEO201811SEAMEO-JapanESDAwardW000242.pdf

Contemporary Philippine Arts from the Regions - Local Materials https://www.slideshare.net/slideshow/contemporary-philippine-arts-from-the-regions-local-materials/254386670

Whose Who Look at the artworks of these Contemporary Artists https://studyx.ai/homework/111101716-activity-3-whose-who-look-at-the-artworks-of-these-contemporary-artists-and-guess-what

Chinese news https://www.jiuzyoung.com/tag/elito-circa/

Pintor, ginagamit ang sariling dugo sa pagpinta ng kaniyang mga obra https://www.gmanetwork.com/news/balitambayan/talakayan/713115/pintor-ginagamit-ang-sariling-dugo-sa-pagpinta-ng-kaniyang-mga-obra/story/

“Buhay na Obra" (Dokumentaryo ni Jay Taruc) https://www.gmanetwork.com/news/publicaffairs/iwitness/227129/buhay-na-obra-dokumentaryo-ni-jay-taruc/story/

Philippine artist has blood on his hands, literally - to create art with https://www.thestar.com.my/lifestyle/culture/2022/12/17/philippine-artist-has-blood-on-his-hands-literally---to-create-art-with

Filipino artist creates paintings using his own blood https://interaksyon.philstar.com/hobbies-interests/2022/12/19/237653/filipino-artist-creates-paintings-using-his-own-blood/

Elito Circa riskes his life to paint iconic montage of President Duterte https://kami.com.ph/57410-buwis-buhay-local-artist-paints-president-duterte-using-blood-sweat.html

Filipino artist paints with his own blood, sweat and tears… literally https://www.scmp.com/video/asia/3203615/filipino-artist-paints-his-own-blood-sweat-and-tears-literally

Write an essay about Some Philippine artworks challenge our perspectives and make us think differently https://www.classace.io/answers/write-an-essay-about-some-philippine-artworks-challenge-our-perspectives-and-make-us-think-differently-can-you-share-an-example-of-an-filipino-art-made-that-challenged-your-beliefs-or-made-you-see-thi#google_vignette

Filipino artist creates painting gs using his own blood https://news.am/eng/news/735522.html#google_vignette

Look: Filipino artist creates paintings using his own blood https://www.khaleejtimes.com/world/asia/philippine-artist-creates-paintings-using-his-own-blood

Filipino artist creates paintings using his own blood https://borneobulletin.com.bn/filipino-artist-creates-paintings-using-his-own-blood-2/

Vietnamese News: 'Dị nhân' vẽ tranh bằng chất liệu độc lạ: Người dùng nước mắt, người dùng cả máu https://baomoi.com/tag/Elito-Circa.epi

Philippine artist creates paintings using his own blood https://magtheweekly.com/detail/17261-philippine-artist-creates-paintings-using-his-own-blood#google_vignette

Bahrain News https://www.bna.bh/en/news?cms=q8FmFJgiscL2fwIzON1%2BDkh7TBmtbW0fqIdLEpax%2BmI%3D

The Expositor: Art in a whole new vein https://www.brantfordexpositor.ca/news/local-news/art-in-a-whole-new-vein

Slovenia News: Slika z lastno krvjo (FOTO) https://www.slovenskenovice.si/tag/elito-circa/#

Artist uses own blood, hair in his paintings https://punto.com.ph/artist-uses-own-blood-hair-in-his-paintings/

Elito Villaflor Circa -Famous Filipino Artist https://www.pechakucha.com/presentations/elito-villaflor-circa-famous-filipino-artist-754

Filipino Artist and Delegates Mark Active Presence at Rotary International Convention in Hamburg https://philippine-embassy.de/2019/06/03/filipino-artist-and-delegates-mark-active-presence-at-rotary-international-convention-in-hamburg/

Philippine Star: Artist uses own blood, hair in paintings https://www.philstar.com/breaking-news/705010/artist-uses-own-blood-hair-paintings/amp/

Daily Jang Daily Jang News: Pakistan's leading Urdu Newspaper: Philippine artist Elito Circa create painting using his own blood https://www.youtube.com/watch?v=TmCF00XHftQ

Artist with blood on his hands https://lifestyle.inquirer.net/256243/artist-blood-hands/

Philippine artist creates paintings using his own blood https://dzrh.com.ph/post/shinee's-minho-is-coming-to-manila!

ABS-CBN News: Artist uses own blood to paint Duterte masterpiece https://www.abs-cbn.com/life/11/01/16/artist-uses-own-blood-to-paint-duterte-masterpiece

Controversial Artist Uses His Own Blood as Paint https://www.odditycentral.com/art/controversial-artist-uses-his-own-blood-as-paint.html

Pulse Nigeria: What to know about the world-famous artist who paints with his blood https://www.pulse.ng/articles/lifestyle/the-filipino-artist-who-paints-with-his-blood-2024072704215785598

Philippine artist creates paintings using his own blood https://www.reuters.com/lifestyle/philippine-artist-creates-paintings-using-his-own-blood-2022-12-16/

PH artist Amangpintor meets his foster parent after 45 years https://www.sbs.com.au/language/filipino/en/podcast-episode/ph-artist-amangpintor-meets-his-foster-parent-after-45-years/chyae7fjj

About Elito Circa https://www.scribd.com/document/395849576/Elito-Circa

SCIENCE AND TECHNOLOGY SSRN (Social Science Research Network) International Publication Co-Author: Development and Validation of Electronic Imaging Sweetness Meter for Watermelon (Citrullus lanatus) https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4178717

FAO: Small Ponds Make a Big Difference: Integrating Fish with Crop and Livestock Farming Artist Illustrator https://openknowledge.fao.org/server/api/core/bitstreams/fecc9445-f288-44e5-8c0e-557115082e9d/content/x7156e.htm

— Preceding unsigned comment added by 121.200.4.157 (talk) 11:16, 16 June 2025 (UTC)[reply]

  • Endorse unanimous consensus to delete. Recreation is allowed as the title is not salted. As several of the sources post-date the AFD, any new article would not be substantially similar to the deleted version, therefore G4 speedy deletion would not apply. If the appellant were a user in good standing, and not an IP, my recommendation would be to request the deleted page be restored to draft space at WP:REFUND, incorporate the new references into the draft, and then submit it through the WP:AFC process. Frank Anchor 12:35, 16 June 2025 (UTC)[reply]
Per the below comment, a draft has recently been created, so modifying my response to reflect this. Frank Anchor 23:52, 16 June 2025 (UTC)[reply]
  • Endorse the original delete consensus. The same issues exist in relation to the quality of sourcing which includes user-submitted content, churnalism, human-interest or shock-value sources, blogs, promotional puff pieces, homework assignments and perplexing things like this: {{tq|Write an essay about Some Philippine artworks challenge our perspectives and make us think differently [1]. There does not seem to be any analytical art historical/art critical attention that is normally found for artists; no notable museum collections, etc. (Not sure if this has any bearing on a DRV, but the original article was created by a sock-puppeteer with the same name as the artists's pseudonym, see: [[2]]). Netherzone (talk) 14:11, 16 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Flower (skunk from Bambi) (talk|edit|history|logs|links|watch) (XfD|restore)

Incorrectly non-admin closed as a speedy keep, when it should have been a standard keep and a move. The move is specifically to an admin protected page so would need an admin to do so. CoconutOctopus talk 14:10, 15 June 2025 (UTC)[reply]

  • This needs some thinking. The AfD ended with three keep:one delete:one redirect. The speedy keep close is a concern. This isn't even a WP:SNOWing AfD. If the AfD was closed correctly, endorse. The delete/redirect !votes came in before substantial changes were made to the article within three days of the nomination. After that, people voted keep. Relist probably won't work since the keeps would probably pile-on and the discussion be closed short of the added 168 hours. ToadetteEdit (talk) 15:27, 15 June 2025 (UTC)[reply]
    Adding to my rationale above, I do not recall a page being moved as a result of an AfD, and assistance to move a page to a protected page can always be done at WP:RM/TR. I agree with the OP though that this should be closed by an admin, but I do not see any problem either way. ToadetteEdit (talk) 15:33, 15 June 2025 (UTC)[reply]
    Ah, I see that the closer has been indef'd for general disruption, so this may need to be reconsidered. ToadetteEdit (talk) 15:36, 15 June 2025 (UTC)[reply]
    Yeah, I posted this before reconsidering and taking it to ANI as a whole for bad closes. I do still think this one specifically should have been a Keep followed by a histmerge move, not a simple Speedy Keep. CoconutOctopus talk 15:43, 15 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.


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

Inproper use of G4. he content was significantly different to the previous content - it was unbiased and factual and had references as well as suggestions for further references in the talk page. Unlike the previous content, it focused just on Centre for Sight as a notable eye clinic in the UK and not on the centre's owner who has his own page. I am a new writer so had nothing to do with the previous page in 2017 (I would have been taking my A-levels then not even in work) and I read the guide for creating new pages carefully and applied it to the best on my ability. Erin Dearlove (talk) 12:54, 13 June 2025 (UTC)[reply]

  • Deleting admin's comment: The good-faith G4 by User:Onel5969 applies no matter which paid editor the doctor is using these days. I had offered to restore the page then nominate again for AfD but this paid editor seems to be in a hurry. I was not satisfied this page has better sources than in 2017, even though some sources may be different. Again, I'm happy to restore for now. BusterD (talk) 13:36, 13 June 2025 (UTC)[reply]
    Have restored and renominated. BusterD (talk) 13:53, 13 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Alisha Parveen (talk|edit|history|logs|links|watch) (XfD|restore)

Alisha has become notable now so can her deleted article be restored to draftspace so that I can work on it and submit it for review? Zainyloves (talk) 05:42, 12 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Template:AHM (talk|edit|history|logs|links|watch) (XfD|restore)

The reason for it to be deleted was not being widely used, that's changeable. I will put it to use, in addition it, I believe if more people knew it exists, it would also have been put to use more often. 2604:2D80:4D09:1A00:FDB5:CAB5:3ED6:E92B (talk) 02:50, 11 June 2025 (UTC) -->[reply]

  • This template was deleted over two years ago. Why are you only requesting this now? Stifle (talk) 08:43, 11 June 2025 (UTC)[reply]
    Because I wasn't here two years ago. I've already asked the person who deleted it, he didn't appreciate being bothered. 2604:2D80:4D09:1A00:D79:B3E7:D881:47A0 (talk) 00:28, 12 June 2025 (UTC)[reply]
    I probably wouldn't "appreciate" having something like this written to me, either. Daniel (talk) 05:40, 12 June 2025 (UTC)[reply]
    I don't understand the issue.
    I used his terminology, following his definition.
    I had already told him I am aware why it was deleted, he replied by telling me it was deleted because of the reasons I had already told him I have been made aware of, and had already disputed, something which he did not address, and when pressed on it he started making threats. "End of the road for you" are you building up on his intimidation tactics?
    I'm not even sure why the temporality of the request was even asked; It's only out of [evidently] undue politeness that I even added the section about requesting to have it restored; as to avoid my reply to the admin, who bothered replying to my requesting of a restoration of a nuanced template -which was deleted for no reason, save that one person didn't like it being used only once by one person prior -something which had already been remedied for in this petition- being that of simply pointing out the obvious; I wasn't here then; But I'll add some more now: Nor did I know it exists, Nor do most who would make use of it. 2604:2D80:4D09:1A00:F4F4:3E0A:508B:CDB6 (talk) 18:45, 12 June 2025 (UTC)[reply]
  • Restore based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). That's not enough to be considered consensus to delete, particularly without being relisted even a single time. We now have a user interested in correcting the reason for which the template was deleted. While I would normally vote to relist a sparsely-attended discussion, it does not make sense to relist a discussion from over two years ago. Any user would be free to start a new TFD. Frank Anchor 12:52, 11 June 2025 (UTC)[reply]
  • Comment - I think that this request reflects the idea that deletion of a template or category, unlike deletion of an article, is permanent, and that any recreation can be tagged as G4 unless it is brought here to DRV. Robert McClenon (talk) 15:34, 11 June 2025 (UTC)[reply]
  • Restore There was too little participation in the TfD, and this was from two years ago so relisting wouldn't be a good idea. Opm581 (talk | he/him) 20:42, 13 June 2025 (UTC)[reply]
  • Restore per above. TFD participation has long been low, and I think that the request to restore is I good faith. ToadetteEdit (talk) 16:40, 15 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Draft:Surya Devan (talk|edit|history|logs|links|watch) (restore)

Request for user space restoration only

I acknowledge that Draft:Surya Devan was deleted under CSD G11 for promotional content, and I also acknowledge a conflict of interest. I am not contesting that deletion from draftspace.

However, I respectfully request a user subpage copy at User:SuryaDevanE/SuryaDevan so that I can work on the material privately for learning and eventual neutral submission — possibly by a third party.

I’ve made a clear good-faith effort to understand Wikipedia’s policies and will not attempt to repost the article without editorial guidance. Admin Timtrent has declined restoration; I’m requesting community review.

Thank you. — SuryaDevanE (talk) 19:44, 9 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Template:Aubrey Plaza (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

  • Overturn Besides generally supporting procedural relist as DELREV nominator, looking at the production credits that made up most of the navbox (The Little Hours, Ingrid Goes West, Black Bear (film), Little Demon (TV series), and Emily the Criminal), in all cases Plaza is producer and main actor and, at least through our articles or a quick search, was the first producer signed on and a primary creative force in the projects being picked up and finished. Two of the film articles also indicate she was directly involved in casting. It's simply unreasonable to suggest Plaza would not be considered a primary creator, and this in addition to the character links, mean it's both a complete and tightly-focused (distinct creator connection throughout all items) navbox. Kingsif (talk) 04:26, 9 June 2025 (UTC)[reply]
    She is most definitely not the creator of Little Demon and she was one of 6-8 producers on a couple of the films you mention. She cannot be considered a primary creator for these. WP:FILMNAV clearly applies here. --woodensuperman 11:08, 9 June 2025 (UTC)[reply]
    Once again, FILMNAV (no matter what you wanted when you wrote it) is not a deletion policy - you can write a personal argument why you believe some of its content indicates that some items shouldn't be included, but that is 1. an opinion and 2. not something that leads directly to template deletion. At least you now seem to only question inclusion of a couple of the films, so regardless there is certainly enough for a navbox to exist. Kingsif (talk) 20:01, 9 June 2025 (UTC)[reply]
  • Relist based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). Thats not enough to be considered consensus to delete, particularly without being relisted even a single time, now that a user has presented an argument to retain the template. Frank Anchor 14:14, 9 June 2025 (UTC)[reply]
  • endorse or relist, there is precedent for director-centric navigation boxes and for deleting actor-centric and producer-centric navigation boxes (per MOS:FILM), but I see no harm with reopening this for more discussion. Frietjes (talk) 15:30, 9 June 2025 (UTC)[reply]
  • Relist - Inadequate discussion for consensus, should have been relisted once. Robert McClenon (talk) 16:17, 9 June 2025 (UTC)[reply]
  • Relist as per above. This should have been pointed out before the closing time. ToadetteEdit (talk) 06:51, 10 June 2025 (UTC)[reply]
  • As a usual closer at TFD, one comment + the OP is typical to establish consensus for a routine nomination. I would judge this as one such. I think relist comments based on this factor are probably a miss. (The OP here cites at least one other factor, on which I have no comment.) Izno (talk) 17:54, 14 June 2025 (UTC)[reply]
  • Question for User:Izno about TFD: Do the OP and one supporting comment establish a consensus to keep the title deleted, or can another editor recreate the title? Can the OP simply recreate a template with the same title? Robert McClenon (talk) 20:23, 16 June 2025 (UTC)[reply]
Template:Michael B. Jordan (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

Template:Halle Berry (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

  • Also, request undeletion so that previous versions (the original TfD nominator noted they significantly reduced it) can be properly assessed. Kingsif (talk) 04:11, 9 June 2025 (UTC)[reply]
  • Relist based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). Thats not enough to be considered consensus to delete, particularly without being relisted even a single time, now that a user has presented an argument to retain the template. Frank Anchor 14:13, 9 June 2025 (UTC)[reply]
  • endorse or relist, there is precedent for director-centric navigation boxes and for deleting actor-centric and producer-centric navigation boxes (per MOS:FILM), but I see no harm with reopening this for more discussion. Frietjes (talk) 15:30, 9 June 2025 (UTC)[reply]
  • Relist - Inadequate discussion for consensus, should have been relisted once. Robert McClenon (talk) 16:17, 9 June 2025 (UTC)[reply]
  • Relist all three of these, though I think the same result will occur due to our policies. SportingFlyer T·C 21:04, 9 June 2025 (UTC)[reply]
    With the Berry template, it seems likely, but that's okay: in a TfD we must allow the discussion to occur or we are sidestepping accountability. This is why I do take issue, in general, with acronyms (mis)used for authority and "per nom" being ways things get done: no user(s) take accountability and we can't blame a TfD system that has been used improperly, so it becomes increasingly hard to start new discussion or get to the root of decisions, which is how bad precedents are set. Kingsif (talk) 21:19, 12 June 2025 (UTC)[reply]
  • Relist as per above. ToadetteEdit (talk) 06:51, 10 June 2025 (UTC)[reply]
  • As a usual closer at TFD, one comment + the OP is typical to establish consensus for a routine nomination. I would judge this as one such. I think relist comments based on this factor are probably a miss. (The OP here cites at least one other factor, on which I have no comment.) Izno (talk) 17:55, 14 June 2025 (UTC)[reply]
    Even when the comment doesn’t say anything? Anyway, maybe two just generally shouldn’t be considered consensus - I don’t know where else it would. And I imagine if there were suddenly lots more non-consensus status quo closes, it would drive up engagement with TfD. Kingsif (talk) 10:48, 15 June 2025 (UTC)[reply]
    I can not see any future in any forum in which more no-con closes would increase engagement (or in which this would be healthy whatsoever for TFD). Which as you imply, is the problem. TFD has a second issue that it has no PROD or equivalent, which is how AFD would theoretically get around this case.
    On which point in fact, several admins at TFD will delete templates with solely a nom as a soft deletion despite there being no policy on the point. (I personally relist nom-only TFDs.) I raised that in 2021 (see Explicit talk page link); discussion at the time seemed not particularly concerned with the practice.
    As such, I don't think it's realistic to suggest 'two shouldn't be a consensus' without a wider guideline or policy saying what the minima are. Izno (talk) 20:37, 16 June 2025 (UTC)[reply]
    Question for User:Izno about TFD: Do the OP and one supporting comment establish a consensus to keep the title deleted, or can another editor recreate the title? Can the OP simply recreate a template with the same title? Robert McClenon (talk) 20:24, 16 June 2025 (UTC)[reply]
    I don't see how that question is interesting, TBH. If you mean, would someone recreating these navboxes have to contend with WP:G4? Assuredly. Izno (talk) 23:00, 16 June 2025 (UTC)[reply]
Ilyas El Maliki (talk|edit|history|logs|links|watch) (XfD|restore)

1. The new article was not substantially identical to the previously deleted version. It introduced at least 50% new sources, including coverage of the subject’s achievements from Dexerto, Kings League’s official website, and leading Moroccan media outlets like Hespress, L'Opinion, Telquel and Morocco World News.

2. The new sources were not properly evaluated. Editors repeatedly called for "speedy delete" without reviewing the sources or explaining why they failed WP:GNG.

3. Skepticism toward Moroccan media reflects potential systemic bias. Editors did not provide evidence that these outlets were unreliable, yet their reliability was dismissed. This reflects broader challenges in recognizing notability for figures from the MENA region.

  • I request a review to determine whether the sources and arguments presented were given adequate consideration before deletion.

Rap no Davinci (talk) 18:03, 9 June 2025 (UTC)[reply]

  • Can someone confirm whether WP:G4 applied? I think we've gotten this one wrong and it looks like we can have an article on him based on the wide amount of coverage he's received. SportingFlyer T·C 21:09, 9 June 2025 (UTC)[reply]
  • Overturn to no consensus with no prejudice against immediate re-nomination. The rationale for every delete vote was that an article on this subject was previously deleted in an AFD. However, the temp un delete shows the article deleted in the second AFD is vastly different than the one in the first AFD, including multiple references dated after the article was first deleted. G4 clearly does not apply. There is very little discussion of the merits of the actual article or of the references (particularly those that were not in the article during the first AFD) from the delete !voters. Frank Anchor 00:59, 10 June 2025 (UTC)[reply]
  • Overturn A "Delete because G4" when G4 does not apply is no delete !vote at all. It likely reflects fatigue with efforts to craft compliant articles on borderline notability people, and we need to instead properly evaluate notability based on the final sourcing provided. The late-breaking G4s after the earlier ones had been contested are particularly puzzling to me. Jclemens (talk) 02:38, 10 June 2025 (UTC)[reply]
  • Comments - I am puzzled. The old and the new temporarily undeleted versions that I am viewing are so different that no one should say that they are substantially the same. Was the new version of the article expanded while the second AFD was in progress, in which case some of the AFD participants saw a different less complete article?
    • This is a difficult case, because DRV is not AFD round 2, but the AFD does not appear to reflect reality. The Delete votes all said to Speedy Delete, and the nomination says that the article being reviewed is substantially the same as the deleted article, but the two articles are not substantially the same. I think that Ignore All Rules should be used very rarely, but this is a case where we need to ignore the rule that are not reviewing the AFD. The AFD was wrong. I was about to say to Relist, but this AFD has been tainted. Robert McClenon (talk) 02:49, 10 June 2025 (UTC)[reply]
  • Overturn to No Consensus as per User:Frank Anchor and permit a new AFD to be started, and the participants will know that G4 is not one of the valid answers. Robert McClenon (talk) 02:49, 10 June 2025 (UTC)[reply]
  • Overturn per above. G4 should not apply if there are substantial changes such that the concerns in the previous AFD are addressed. It is probably too excessive to delete the page because of the G4 comments in the AfD despite the author's convincing arguments against the delete !votes. ToadetteEdit (talk) 06:57, 10 June 2025 (UTC)[reply]
  • Overturn and allow a new AfD if you want, but I strongly suspect we're at the point where this will be kept. SportingFlyer T·C 07:19, 10 June 2025 (UTC)[reply]
  • Overturn and allow a new AFD, per above. Mooonswimmer 04:19, 12 June 2025 (UTC)[reply]
  • Overturn, clearly not G4 and also there are plenty of sources about him. Alaexis¿question? 14:19, 13 June 2025 (UTC)[reply]
  • I'm going to buck the trend here and say endorse This the result of an AfD discussion, not a speedy deletion, so the question of whether G4 actually applies or not as stated in the speedy deletion criteria doesn't technically matter. Instead, "delete per G4" is a perfectly reasonable shorthand way of saying "delete because I don't think the issues that caused the previous deletion have been addressed". And we don't have jurisdiction at DRV to determine that argument is invalid because doing so would merely be substituting our judgement for theirs rather than actually addressing a procedural error as we are supposed to do. * Pppery * it has begun... 23:08, 13 June 2025 (UTC)[reply]
Except there was a procedural error. The “delete per G4” voters did not have access to the previous version which was deleted and recreated. They just assumed, incorrectly, that since it was already deleted once it should simply be deleted again. The procedural error is in the closer (who would have access to both versions and see that G4, whether as an actual speedy or as an argument in an AFD vote, clearly didn’t apply) giving too much weight to these votes which were found out to not be based at all in P&G. That is certainly a valid concern for DRV. Frank Anchor 11:36, 14 June 2025 (UTC)[reply]
That's not what G4 says at all - it specifically says the draft must be sufficiently identical. The other wrinkle here is that this does look like it should have been kept looking at the available sources. SportingFlyer T·C 11:51, 14 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Violations (Star Trek: The Next Generation) (talk|edit|history|logs|links|watch) (restore)

The article is nothing but describing the plot of the episode. No source links provided, no production information, nothing. This article about the episode is rendered pointless.--Dr. Gregory House's Missing Cane (talk) 13:48, 8 June 2025 (UTC)[reply]

Close (wrong forum). SmokeyJoe (talk) 06:07, 9 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Douglas Cowgill (talk|edit|history|logs|links|watch) (restore)

The article can't be re-created but has sources such as [[3]] and [[4]] and [[5]] Wynwick55gl (talk) 09:08, 8 June 2025 (UTC)[reply]

Douglas Cowgill isn't protected, from what I can see. As a non-autoconfirmed user, you can't directly create it though, please use the article wizard to create & submit a draft. Victor Schmidt (talk) 10:40, 8 June 2025 (UTC)[reply]
Close (out of scope). DRV is not for giving permission to recreate old deletions. If you’re not sure, use WP:AFC. SmokeyJoe (talk) 06:10, 9 June 2025 (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
2025 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