Wikipedia:Deletion review
Deletion discussions |
---|
|
Articles |
Templates and modules |
Files |
Categories |
Redirects |
Miscellany |
Speedy deletion |
Proposed deletion |
Formal review processes |
---|
|
For RfCs, community discussions, and to review closes of other reviews: |
Administrators' noticeboard |
In bot-related matters: |
|
Discussion about closes prior to closing: |
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:
- if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
- if a speedy deletion was done outside of the criteria or is otherwise disputed;
- if significant new information has come to light since a deletion that would justify recreating the deleted page;
- if a page has been wrongly deleted with no way to tell what exactly was deleted; or
- if there were substantial procedural errors in the deletion discussion or speedy deletion.
Deletion review should not be used:
- 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);
- (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.)
- 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);
- 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);
- to repeat arguments already made in the deletion discussion;
- to argue technicalities (such as a deletion discussion being closed ten minutes early);
- to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
- to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed);
- 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.)
- 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:
- 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.
- 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
If your request is completely non-controversial (e.g., restoring an article deleted with a PROD, restoring an image deleted for lack of adequate licensing information, asking that the history be emailed to you, etc), please use Wikipedia:Requests for undeletion instead. |
1. |
{{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:
|
3. |
For nominations to overturn and delete a page previously kept, attach |
4. |
Leave notice of the deletion review outside of and above the original deletion discussion:
|
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.
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.
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".
The page was deleted after the individual who requested the deletion mutilated the page by removing key links and information on the notability of the subject and in the process skewing the page to look bad.
The page was created around 2008 because of the notability of the individual in many respects including:- 1. Earliest Nigerian blogger since 1997 and created the website Dawodu.com. There are more than 50 Wikipedia articles that reference this website to show its significance in contributing to discussion on Nigeria’s socio-economic, political and historical issues. 2. He was one of the pioneer editors of the Knowledge Now (https://now.aapmr.org), a repository of articles in physical medicine and rehabilitation in the world hosted by the American Academy of Physical Medicine (AAPMR)and also pioneer author of articles on this platform. Inquiries can be made to AAPMR through their website AAPMR.org. 3. He was one of the pioneer authors of various articles on Emedicine that later became part of MEDSCAPE (MEDSCAPE.com) which is the number one website of medical articles in the world and that was as far back as 1998. His article on spinal cord injury and causa equina on MEDSCAPE was a reference for Emergency Room doctors in managing such conditions.
Some of these were fully discussed in the past at a previous attempt to delete the site.
The question that the editor that requested deletion needs to answer is why did he delete relevant references and mitigated the article before requesting the deletion of the article. One can see this as evidence of possible malice.
I do hope that this will be reviewed as soon as possible and allow the discussion to continue for another week to enable more people participate. Attempts were made by me behind the scene to ensure that the person that requested deletion will consider the above and withdraw the request. — Preceding unsigned comment added by Ckanopueme (talk • contribs) 13:03, 21 July 2024 (UTC)
- If "and candidate for Masters in Global Healthcare Leadership from University of Oxford Reuben College, Oxford" is such a critical part of the article so as to constitute "key links and information" and removing it is "mutilat[ion]" and "skews the page to look bad", then this never should have lasted this long. Endorse. —Cryptic 13:20, 21 July 2024 (UTC)
Joe Lonsdale (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
The page was deleted in 2021 with only two non-sockfarm !votes — one from an editor who wanted to avoid rewarding apparent UPE, and one from an editor who felt the coverage was trivial. I don't think the deletion was unreasonable given the !votes, nor do I think the trivial coverage concern was unwarranted given that some editors had stuffed the page full of ~60 references that were largely trivial. However, I think some of the old sources combined with substantial available new sourcing justify undeletion, and I'm happy to do the cleanup necessary after the page is restored. Lonsdale is notable as a founder of Palantir and later OpenGov and University of Austin. He is also among a group of politically active tech financiers who are pretty regularly covered in the news (most recently in a spate of coverage about a new super PAC for which he is evidently helping to fundraise — see NYT, etc.) GorillaWarfare (she/her • talk) 20:48, 17 July 2024 (UTC)
|
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. |
I've created an undeletion request at Wikipedia:Requests for undeletion#Wikipedia:Administrators' noticeboard/OldHeader.
Graeme Bartlett recommended (Special:Diff/1235028837) getting consensus here first. —andrybak (talk) 12:28, 17 July 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Global company with more than 10000 employees. Innumerable credible inline news sources and books . New articles with new sources , should not be deleted due to old article as innumerable credible sources have emerged 121.242.91.74 (talk) 06:54, 17 July 2024 (UTC)
- Comment Draft:EFS Facilities Services Group was deleted last week as G11; I believe that is what this is referring to. Jclemens (talk) 07:00, 17 July 2024 (UTC)
- ... and this has been before us twice before and endorsed on similar grounds: Wikipedia:Deletion review/Log/2023 November 9, Wikipedia:Deletion review/Log/2024 January 8. Jclemens (talk) 07:02, 17 July 2024 (UTC)
- Speedy Close and semi-salt all relevant draftspace titles so that only registered users can create drafts in the future. Enough is enough. Given the history, I'm not even wanting to ask to see the deleted material before assuming that G11 is once again valid. Jclemens (talk) 07:07, 17 July 2024 (UTC)
- Well, it doesn't mention the company's "economic journey", but it has most of the other hallmarks. In particular, most of the external links in the absurd refbombing are showing up as already-visited to me (though I don't remember taking more than a cursory look in previous visits to DRV); this is typical of the new ones.The sad thing is, the claims in the draft are such that I'd expect there to be usable sources on it somewhere, but you'd have to be daft to try looking for it among all the shallow promotion they've paid for.I'll try to work out a regex less gameable than the one I tested in November, but something's changed such that these queries, which used to complete in minutes, have been running for more than an hour now and show no signs of stopping. For just an autoconfirmed+ blacklisting, it seems like wasted effort. —Cryptic 13:27, 17 July 2024 (UTC)
- (And, as usual, it completed almost immediately after I complained that it wasn't going to complete. The public version at quarry:query/84908 should eventually get populated, maybe quickly if it cached well, maybe not. There were a couple new deletions since the November try, no new false positives, and nothing that would be caught by the wider regex that wouldn't have been by the old.) —Cryptic 13:39, 17 July 2024 (UTC)
- Well, it doesn't mention the company's "economic journey", but it has most of the other hallmarks. In particular, most of the external links in the absurd refbombing are showing up as already-visited to me (though I don't remember taking more than a cursory look in previous visits to DRV); this is typical of the new ones.The sad thing is, the claims in the draft are such that I'd expect there to be usable sources on it somewhere, but you'd have to be daft to try looking for it among all the shallow promotion they've paid for.I'll try to work out a regex less gameable than the one I tested in November, but something's changed such that these queries, which used to complete in minutes, have been running for more than an hour now and show no signs of stopping. For just an autoconfirmed+ blacklisting, it seems like wasted effort. —Cryptic 13:27, 17 July 2024 (UTC)
- Speedy close, endorse and salt all relevant titles per Jclemens above. I would do this myself but I closed the last DRV so, with no pressing need to intervene, would rather another administrator do it. Thanks, Daniel (talk) 08:22, 17 July 2024 (UTC)
- Endorse. Do not SALT. SALTing in draftspace encourages the game of cat and mouse with using variations on the title. Draftspace exists to attract and contain unworthy content, let it serve its purpose. It’s easier to keep deleting the same title than variations on the title. SmokeyJoe (talk) 09:23, 17 July 2024 (UTC)
- Endorse, speedy close, and title-blacklist for non-autoconfirmed users. Enough now. Stifle (talk) 09:38, 17 July 2024 (UTC)
- Oh yeah... title blacklist is probably the better solution. Never used it myself, so I keep forgetting it exists. Jclemens (talk) 15:35, 17 July 2024 (UTC)
- Endorse and list at WP:DEEPER (a recommendation from the previous DRV). I feel like blacklisting is going to be robust enough of a solution to figure as a net postive.—Alalch E. 15:49, 18 July 2024 (UTC)
- Off-topic: Tariq Chauhan slipped through. —Alalch E. 16:00, 18 July 2024 (UTC)
- User:Alalch E. - Not entirely off-topic. The one sentence that is left about Tariq Chauhan is not enough to pass general notability, and has been nominated for deletion. Robert McClenon (talk) 19:14, 18 July 2024 (UTC)
- Endorse all previous deletions. Robert McClenon (talk) 18:45, 18 July 2024 (UTC)
- Title Blacklist and list at WP:DEEPER (as recommended in previous DRV). Robert McClenon (talk) 18:45, 18 July 2024 (UTC)
- Do Not Salt in draft space. Useless drafts that cannot be accepted are harmless in draft space. Salting in draft space encourages the gaming of names. Robert McClenon (talk) 18:45, 18 July 2024 (UTC)
- ECP Salt in article space. Robert McClenon (talk) 18:45, 18 July 2024 (UTC)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
A non-admin closure was performed after just two days on grounds of WP:SNOW, which is disallowed under WP:NACAFD. While I don't disagree with the outcome, there were several "redirect" !voters in the discussion who (a) might have changed their !votes on their own premise (once opinion polls began to be available) or (b) perhaps had reasons to maintain their positions during the remaining discussion period, who knows. Given the procedural error, I propose re-opening the discussion and allowing an admin to interpret whether a SNOW closure is appropriate. Dclemens1971 (talk) 12:59, 16 July 2024 (UTC)
|
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. | |||||
A user SNOW-closed a discussion after just 5 hours, so short some people in certain time zones can’t respond, and on their talk page, refused to re-open the discussion. And while keepers cited how BIO1E does not apply, this does not take into consideration the WP:RECENTISM concerns, which went unaddressed.Downerr2937 (talk) 17:02, 14 July 2024 (UTC)
| |||||
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. |
G14 is not applicable, Joseph Beuys does disambiguate the term "Beuys". Paradoctor (talk) 15:39, 12 July 2024 (UTC)
|
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. |
I think the arguments put forward by the participants to deletion discussion do not conform to the Wikipedia guidelines. The main argument was that if the article was not notable it would not have so many sources -I think the issue is not the quantity of sources but the engagement with the subject. The article has many sources that simply reproduce each other, without going deeper.. Also, I pointed out that the sources that do exist do not refer to the party but to its leader, which is not the same thing. I have the impression that the user who closed the discussion was just counting votes not arguments. D.S. Lioness (talk) 04:06, 12 July 2024 (UTC)
|
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. |
|
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. |
The article was deleted and directed to redirect because it was unsourced. However, the subject has become notable now with his multiple lead roles in Kandy Twist, Pandya Store, Suhaagan (TV series) and his prominent role in Awasthy Vs Awasthy. I have created a draft Draft:Akshay_Kharodia which supports all these roles with reliable sources per WP:ICTFSOURCES but a reviewer has rejected the draft. Please move the draft to the mainspace and relist it in AFD. 202.41.10.107 (talk) 05:49, 8 July 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
- List of NCAA Division III independents football records (talk|edit|history|logs|links|watch) (XfD|restore)
I'm not sure what should be done here. If the closer really felt that the keep votes should have been discounted as mentioned and that there was "a clear consensus to delete", then it should be deleted. The given merge target was only suggested by one person and thus feels like a supervote. Moreover, the given target very clearly won't support the giant off-topic stats dump that this would bring to it. As desperate as relists can be sometimes, maybe that would be better here to get some more eyes on this. 35.139.154.158 (talk) 13:05, 5 July 2024 (UTC)
- Comment as the closer: if the appellant isn't sure what should be done, what is the remedy being sought here? When Delete is a valid outcome, and the content isn't in violation of policy, then both Redirect and Merge are valid alternatives. My use of "selective merge" in the result makes it clear there is no intention to include all, or even any of the content in the target, which may simply degenerate into a Redirect. The choice of what, if any, to merge is an editorial--not an administrative--one. There's no harm in relisting, and I had likely done so myself had the appellant contacted me directly prior to filing this DRV. But as said, it's not clear this is what they want, and I don't believe an outright deletion is correct with a valid ATD. Owen× ☎ 13:27, 5 July 2024 (UTC)
- I was being generous with the relist suggestion. ATD doesn't require that you avoid a "delete" outcome if it's called for. 35.139.154.158 (talk) 14:23, 5 July 2024 (UTC)
- True, ATD doesn't require avoiding deletion, it merely allows it, and I exercised my prerogative to pick an ATD that was minimally destructive. If you are arguing for deletion, as you now seem to be, please show us which part of the article's content violates policy to the point where it requires deletion. Owen× ☎ 14:30, 5 July 2024 (UTC)
- I was being generous with the relist suggestion. ATD doesn't require that you avoid a "delete" outcome if it's called for. 35.139.154.158 (talk) 14:23, 5 July 2024 (UTC)
- Endorse-ish, I personally would have closed it as N/C, but a merger is an editorial action and not an admin one so it's one anyone could have taken, including OwenX following the close. While there wasn't support for retention as a standalone, nor was there a case that the information needed removal-just relocation. I don't see this as a super vote so there's nothing wrong with the close which certainly falls within closer discretion. Star Mississippi 14:15, 5 July 2024 (UTC)
- Overturn - not a single participant !voted "merge". This wasn't a close, it was a super vote. Absolutely unacceptable close. Sergecross73 msg me 17:25, 5 July 2024 (UTC)
- I think you may have missed Jweiss' unbolded merge suggestion (I did too at first) Star Mississippi 17:50, 5 July 2024 (UTC)
- No, I saw that. But it wasn't even their preferred stance, let alone the consensus of the discussion on a whole. Sergecross73 msg me 17:53, 5 July 2024 (UTC)
- I think you may have missed Jweiss' unbolded merge suggestion (I did too at first) Star Mississippi 17:50, 5 July 2024 (UTC)
- Endorse. The closing statement correctly dismissed the keep votes, which were primarily based in WP:OTHERSTUFFEXISTS, showing a policy-based consensus to not keep the standalone article. Merging was suggested by one user and there was no stated opposition to a merge from the delete voters. Frank Anchor 02:28, 6 July 2024 (UTC)
- Overturn (to Redirect, with history available to optionally merge to NCAA Division III independent schools). Unless the closer immediately performs the merge. AfD consensus to merge requires a strong proponent of the merge who has a plan for how to do the merge. Leaving the article with that tag on top is a pretty poor presentation to readers. AfD should not be used as an alternative to Requested merges but with imaginary fairies who will complete the merge. —SmokeyJoe (talk) 09:54, 7 July 2024 (UTC)
- Endorse. It doesn't matter. AfD "redirect" (the usual "redirect" outcome whereby history remains accessible) and "merge" are the same. If the outcome is "redirect" the content from history can be copied, and if someone does that, that will constitute a merger. If the outcome is "merge" and the page is not initially replaced with a redirect, the would-be performer of the suggested merge can decide to replace the page with a redirect saying "there's noting to merge after all, as this content according to my independent editorial judgement does not belong on the suggested target page". The latter can be followed by someone copying all or some of the content from history and adding it to the suggested target article, and this can be contested by reverting that addition, and that makes for a regular content dispute which is resolved by identifying the minimum of transferable items, and through incremental editing. No need for a DRV.—Alalch E. 21:19, 7 July 2024 (UTC)
- It does matter. “Redirect” means the page is no longer live. “Merge” means that the page remains as before, except with a variation of a mergeto tag, indefinitely. The “Merge” result is functionally the same as a “No consensus” result. If it was a “no consensus”, it should be closed as “no consensus”. SmokeyJoe (talk) 22:39, 7 July 2024 (UTC)
- How is it functionally the same as "no consensus", when, in the end, an AfD "merge" equally turns the page into a redirect as the "redirect" outcome, with the only difference that there is not a set time for doing it after closure and tagging. But there is a general expectation that it will be done. It's not like someone can say "okay, well, this shouldn't be merged after all, in my opinion, so I will remove the merging tag, and the AfD should be interpreted as a 'no consensus' discussion from now on"; or: they can unilaterally remove the tag but only if something significant is done with the content while the page is tagged, which is claimed to address the cause for the AfD's outcome -- equivalent to how an article can be restored from a redirect, given a reasonable effort, which can be contested in a new AfD. —Alalch E. 22:58, 7 July 2024 (UTC)
- “Merge” doesn’t turn the page into a redirect. It leaves the page as it was but with a new tag on top. SmokeyJoe (talk) 23:02, 7 July 2024 (UTC)
- Which has to resolve into the page being turned into a redirect. It can't resolve into the status quo ante with the article staying the same as it was sans tag. (It can however, resolve into the article being relevantly changed and kept, which is the same as restoring the article from a redirect; that's a rarer scenario, not the primarily intended thing to happen.) —Alalch E. 23:05, 7 July 2024 (UTC)
- No, it does not have to resolve. And with not a single editor having expressed a wish to do the merge, it was a bad close. I read a consensus as per by bold !vote. SmokeyJoe (talk) 23:41, 7 July 2024 (UTC)
- If I do a zero-byte merger now by copying the content over to the target article and self-reverting and redirecting the source article (one way to do it; another way would be to say in the summary at the source article: "redirect - nothing to merge as none of this content makes the target article better, and no one else has identified any such content"), that redirection can't simply be undone, and has the same status as a redirection from a "redirect" AfD. —Alalch E. 23:47, 7 July 2024 (UTC)
- You could do that zero byte merge, but it would be an independent editorial action. It would not reflect the close and could be reverted at any time on that basis. A zero byte merge is called a redirect, and the close does not say redirect. The Keep or Merge !voter, or anyone agreeing with them, would be justified in reverting you. SmokeyJoe (talk) 02:01, 8 July 2024 (UTC)
- A merger is at least two actions, one on each side. Anything that happens at the target side is an independent editorial action but the redirection at the source article isn't: the page stops being a live article per the AfD consensus that the page should not be retained as a standalone page; that's one part of the "merge" outcome. That part of the merger is fixed. The variable part is what exactly happens to the target article. That's the area of normal editorial decision-making. The editor unhappy with what if anything was merged can make the desired changes themselves by copying the content over from history under the redirect and by simply editing it. There's never a need to undo the redirection. —Alalch E. 12:04, 8 July 2024 (UTC)
- You could do that zero byte merge, but it would be an independent editorial action. It would not reflect the close and could be reverted at any time on that basis. A zero byte merge is called a redirect, and the close does not say redirect. The Keep or Merge !voter, or anyone agreeing with them, would be justified in reverting you. SmokeyJoe (talk) 02:01, 8 July 2024 (UTC)
- If I do a zero-byte merger now by copying the content over to the target article and self-reverting and redirecting the source article (one way to do it; another way would be to say in the summary at the source article: "redirect - nothing to merge as none of this content makes the target article better, and no one else has identified any such content"), that redirection can't simply be undone, and has the same status as a redirection from a "redirect" AfD. —Alalch E. 23:47, 7 July 2024 (UTC)
- No, it does not have to resolve. And with not a single editor having expressed a wish to do the merge, it was a bad close. I read a consensus as per by bold !vote. SmokeyJoe (talk) 23:41, 7 July 2024 (UTC)
- Which has to resolve into the page being turned into a redirect. It can't resolve into the status quo ante with the article staying the same as it was sans tag. (It can however, resolve into the article being relevantly changed and kept, which is the same as restoring the article from a redirect; that's a rarer scenario, not the primarily intended thing to happen.) —Alalch E. 23:05, 7 July 2024 (UTC)
- “Merge” doesn’t turn the page into a redirect. It leaves the page as it was but with a new tag on top. SmokeyJoe (talk) 23:02, 7 July 2024 (UTC)
- How is it functionally the same as "no consensus", when, in the end, an AfD "merge" equally turns the page into a redirect as the "redirect" outcome, with the only difference that there is not a set time for doing it after closure and tagging. But there is a general expectation that it will be done. It's not like someone can say "okay, well, this shouldn't be merged after all, in my opinion, so I will remove the merging tag, and the AfD should be interpreted as a 'no consensus' discussion from now on"; or: they can unilaterally remove the tag but only if something significant is done with the content while the page is tagged, which is claimed to address the cause for the AfD's outcome -- equivalent to how an article can be restored from a redirect, given a reasonable effort, which can be contested in a new AfD. —Alalch E. 22:58, 7 July 2024 (UTC)
- It does matter. “Redirect” means the page is no longer live. “Merge” means that the page remains as before, except with a variation of a mergeto tag, indefinitely. The “Merge” result is functionally the same as a “No consensus” result. If it was a “no consensus”, it should be closed as “no consensus”. SmokeyJoe (talk) 22:39, 7 July 2024 (UTC)
- Relist – I intend to participate – or overturn to no consensus and allow renomination. Closing as merge was a WP:Supervote (essay) with aspects of both "Forced-compromise" and "Left-field".
- The AfD was relisted once, and two relists are permitted by WP:Deletion process#Relisting discussions (guideline, shortcut WP:RELIST).
- As 35.139.154.158 and Sergecross73 wrote above, Jweiss11 suggested merging without justification or bolding. The recommendations of WP:Merge what? (essay) were not followed.
- Since OwenX gave merge extra weight, I expect him to have checked that it was reasonable or, in his words, "valid". I skimmed the articles and identified obvious issues in two minutes, and I confirmed them in a few minutes more.
- List of NCAA Division III independents football records is a historical list of season records going back to 1973. Very few schools are included in recent years: 2024, 2023, and 2022 each list one or two teams.
- NCAA Division III independent schools is the current list of independent schools. The Football section contains only Maine Maritime Academy, which is highlighted in pink because it will join the Commonwealth Coast Conference in 2025. No records are included for any sport. There is a historical list of former full (all sports) independents under Former members.
- A comprehensive merge would create WP:WEIGHT (shortcut to WP:Neutral point of view#Due and undue weight, policy) problems. Merging only 2024 would have the same problems, only less pronounced.
- If no content is merged, I believe the redirect would be deleted at WP:Redirects for discussion as "not mentioned at target".
- If the merge outcome is not overturned, a merge discussion to reject merging the content and another deletion discussion will be required.
- Deleting List of NCAA Division III independents football records has a low cost, as recreating it from scratch would be easy. It's boilerplate and transcluded Category:NCAA Division III football independents standings templates formatted in a table. Side note: template transclusions are not creative content requiring attribution per WP:Copying within Wikipedia#Where attribution is not needed (guideline, shortcut WP:NOATT).
- Flatscan (talk) 04:51, 8 July 2024 (UTC)
- Two follow-up comments:
- This is Jweiss11's recommendation at the AfD:
Keep per Thetreesarespeakingtome. At the very least, this article could be merged to NCAA Division III independent schools.
It includes no details beyond the destination's title and makes no argument for merging, so it should be given very little weight toward a merge outcome. - Regarding WP:Deletion policy#Alternatives to deletion (policy, shortcut WP:ATD), I wrote a policy and consensus analysis that Alternatives to deletion are not preferred over deletion in July 2022. There have been subsequent discussions, but no material policy changes.
- This is Jweiss11's recommendation at the AfD:
- Flatscan (talk) 04:36, 10 July 2024 (UTC)
- Two follow-up comments:
- Endorse Admins making ATD decisions consistent with the points made, rather than bolded !votes, in a discussion are not supervoting. They're doing their policy-based job by determining the rough consensus. Jclemens (talk) 06:45, 9 July 2024 (UTC)
- Endorse - As Jclemens says, Merge is a valid alternative to deletion based on the comments in the AFD. It is true, as SmokeyJoe implies, that Merge can be a problematic ATD because it leaves the merging to be done by gnomes. (We don't know whether to believe in fairies, but we know that gnomes are very real and do a lot of useful work.) That is, closing admins are given an option that can be incomplete. That is a policy issue that doesn't need to prevent admins from following standard closing instructions and selecting Merge. Robert McClenon (talk) 22:42, 9 July 2024 (UTC)
- Relist (or overturn to redirect) - there is no explanation for how anything other than a "zero-byte merge" would be appropriate. A merge isn't just a "compromise" between keep and delete, it is actively making a different article worse, in a way not considered by discussion participants. Walsh90210 (talk) 23:18, 12 July 2024 (UTC)
- Relist or overturn to delete - although in general I think closers should be able to implement reasonable ATDs, merging here is not desirable because the content would be undue for the target, and a redirect would violate WP:RASTONISH. Hatman31 (he/him · talk · contribs) 17:33, 13 July 2024 (UTC)
- Overturn and delete. Supervote. WP:ATD is not a carte blanche to ignore a consensus, and merge closure is effectively equivalent to keep because nobody actually performs the merge. Stifle (talk) 11:15, 16 July 2024 (UTC)
- Relist or overturn to delete (involved). This is a supervote as others have already mentioned. WP:ATD does not override other notability guidelines since editing does not address the reasons for deletion, the merge wasn't even the first option of the one user who suggested it, and it is problematic as is per the points made by Flatscan. Let'srun (talk) 17:49, 20 July 2024 (UTC)
Down-ball (closed)
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Closer did not allow adequate time for new voices to engage in discussion after AfD was re-listed for that express purpose. Closer of a deletion discussion interpreted the consensus incorrectly Rockycape (talk) 02:45, 5 July 2024 (UTC)
Rockycape (talk) 04:25, 6 July 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |