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, 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:
- 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.
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".
- List of films released by Anchor Bay Entertainment (talk|edit|history|logs|links|watch) (XfD|restore)
Cannot see why this should be closed as no consensus. Only one editor opposed the delete with three in support of deletion. Okay, it was relisted with a request for further information, which was never given. However WP:NOTCATALOG is policy, and as this is article is clearly a catalog of releases for DVD reissues (established by precedent at a whole host of other deletion discussions detailed at the linked discussion), something is wrong if we allow the one oppose citing the guideline WP:NLIST to trump policy. --woodensuperman 08:57, 26 November 2024 (UTC)
- Endorse. I see a valid nomination, one P&G-based Keep !vote, and two Delete votes that have nothing to do with policy or guidelines, and were correctly WP:DISCARDed by the closer. A no-consensus close was the correct outcome. Owen× ☎ 11:20, 26 November 2024 (UTC)
This was an unfortunate AfD featuring wall-of-text comments, COI meatpuppets, and a generally poor signal-to-noise ratio. My metaphorical hat is off to the closer, OwenX, for tackling this. However, that said, I do think he missed some crucial signal amid the noise.
During the discussion, three of us !voted to keep on the basis that papers in the journal are cited frequently in reliable sources including Science and Nature. See [1] [2] [3] for specifics. These arguments were founded on Criterion #2 of the WP:NJOURNALS essay, according to which frequently cited journals would count as notable. In determining consensus, the closer discounted these !votes on the grounds that C2 requires frequent citations of the journal itself, not of papers in the journal. See their closing statement and this clarification for details. However, this subsequent discussion on the NJOURNALS talk page resulted in a unanimous consensus that that C2 is indeed satisfied by frequent citations of papers in a journal.
So putting aside the COI !keeps, there seems to be an even split among the P&G-based !votes, which doesn't look like a consensus to me. Botterweg (talk) 19:02, 25 November 2024 (UTC)
- Endorse: OwenX gave a detailed closing statement that says it all. (Disclosure: I was the nom of this AfD). --Randykitty (talk) 19:32, 25 November 2024 (UTC)
- Endorse, you have completely skipped over the very salient point that NJOURNALS is not a guideline and GNG is the requirement for this journal to have a standalone. Therefore it is completely irrelevant what anyone's interpretation of NJOURNALS criteria is when the subject demonstrably does not meet GNG. JoelleJay (talk) 00:32, 26 November 2024 (UTC)
- For better or worse (and I have mixed feelings) the NJOURNALS essay is indeed used as the basis for closing as keep when there's local consensus. In this AfD, nobody cited the issues with NJOURNALS as a reason to delete, so I don't think that's a factor in determining what the consensus was. Botterweg (talk) 01:13, 26 November 2024 (UTC)
- Endorse to my knowledge showing citation counts would be, as Headbomb said, through things like impact factors, not just individual instances of citations. We're on thin ice with NJOURNALS as is, I see no need to push it further. PARAKANYAA (talk) 01:19, 26 November 2024 (UTC)
- Overturn to Keep there are two possibilities in a 5 keeps vs. 3 delete situation read as a deletion. In this case, it's pretty clear that the P&Gs with respect to journals are unsettled. In such a case, outcomes must be held to be descriptive: a delete is a supervote assuming that the folks arguing based on the currently recognized inclusion guidelines somehow trumps the numerical preponderance. Journals are a particularly thorny example, because notability doesn't work well for journals. The best journals are read and cited, but essentially never talked about. That's why notability is not, has never been, and will never be a core policy. It's a guideline, and to the extent that reasonably well-cited journals don't meet the GNG or an SNG, we obviously need another metric besides notability to measure inclusion. The Procrustean, if conventional. answer that journals don't fit well into our notability guidelines and thus should be excluded has everything backwards. Oh, and a no consensus might have been a better way to handle this, but I still believe that keep is the correct outcome based on the discussion. Jclemens (talk) 08:05, 26 November 2024 (UTC)
- As I stated in that discussion, the fact that a paper has been cited in Science or Nature is not an indication that the journal in which that paper appears is notable on en.wiki. Simply relitigating that discussion here as if it hasn't already been demolished is not bringing any additional light to the AfD. The point has been made, taken account and refuted. JMWt (talk) 09:53, 26 November 2024 (UTC)
Administrator asilvering relisted this "don't delete" discussion requesting more evaluation of sources for the subject to determine between keeping the article or merging into a related topic. The non-administrator closer seems to have ignored that comment and only counted the bolded comments when closing as "merge" without any more comments in the discussion. The closer did not respond when asked about it and has not edited in nearly two weeks. This discussion should be relisted. Ivanvector (Talk/Edits) 18:20, 25 November 2024 (UTC)
- Endorse close. The nominator makes a fair point that there were no further comments after the last relist, and a further relist might have teased some out, but there were no actual keep !votes on that discussion. The closest was my own, where I said I was leaning keep because I had found mentions (but not SIGCOV). I would have been persuadable to keep, but I could not find more sources myself, and my actual !vote was merge. Now the reason I think the merge close should be endorsed is this: the school sits within the Brest Naval Training Centre which also is home to the École de Maistrance and the École des Mousses. By merging these into a single article, we now have an article that is still poorly sourced, but is approaching a decent start class rather than a set of minimal unsourced stubs that had poorly machine translated names. On the back of this close I merged them all together into this article. Redirects exist so an interested reader will find their information need met, rather than finding a stub that tells them nothing. Overturning this close would mean demerger, and that would be a net negative to the encyclopaedia. I also presume that if the Lycée naval de Brest part of this article becomes more cleary notable in its own right, and the article section balloons as a result, then spinout is perfectly possible, and I marked the redirect as with possibilities and printworthy for that exact reason. Please also note that I renamed the Lycée naval to Lycée naval de Brest before merging under WP:MADRENAME. That is how it is known. You therefore need to view the history of the redirect at Lycée naval de Brest to see how the article looked prior to merge. Sirfurboy🏄 (talk) 19:10, 25 November 2024 (UTC)
- I personally would probably have read the lack of further input as "no opposition to merge" and gone with merge -- asilvering (talk) 20:35, 25 November 2024 (UTC)
- Endorse - As noted, Asilvering had relisted to see if there were any other votes. When there weren't, a non-admin close of Merge was reasonable. Robert McClenon (talk) 05:16, 26 November 2024 (UTC)
- Comment to User:Mattdaviesfsic - When four of your AFD closes are taken to DRV at the same time, a lesson should be learned. When you resume editing, I suggest that your first task be to decide what the lesson should be. Robert McClenon (talk) 05:16, 26 November 2024 (UTC)
- Endorse as a correct reading of a non-controversial discussion and suitable for a NAC. However, at the same time an AfD closed as merge should never be implicitly construed as a barrier to a spinout should more sourcing arise suitable to justify one. Jclemens (talk) 08:14, 26 November 2024 (UTC)
Zainal Arifin Mochtar (closed)
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
In a relisting comment, administrator Liz noted that the discussion should be closed as no consensus if there were no further comments. The closer, who is not an administrator, appears to have counted the bolded "keep" comments without reading the discussion nor the relisting comment, did not reply to inquiries on their talk page, and has not edited in nearly two weeks. Discussion has already been relisted twice and should be overturned to no consensus. Ivanvector (Talk/Edits) 18:20, 25 November 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
Stephen Barlow (conductor) (closed)
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Closer failed to observe WP:RELIST and closed this discussion on the basis of a single comment. Closer did not adequately explain their close, did not respond to comment afterwards, and has not edited at all in about two weeks. This should be relisted to give time for additional comment. Ivanvector (Talk/Edits) 17:58, 25 November 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
- International reactions to the 2024 United States presidential election (talk|edit|history|logs|links|watch) (XfD|restore)
Not only was this a WP:BADNAC per criteria #2 (this is covered under Wikipedia:Contentious topics/American politics), the close didn't explain why merge !votes were weighted more heavily that delete ones, especially given the technical considerations such as WP:TOOBIG. On a purely numerical basis, there were 18 !votes mentioning delete (14 of which were to just delete without merging), 15 !votes that mentioned merging (including an equal number of "merge or delete" and "merge or keep"), 9 !votes mentioning keeping, and 1 !vote specifically opposing merging. Since merging didn't have a strong numerical advantage over deleting, I have a hard time seeing a clear enough consensus to not have relisted instead of closing. An attempt was made to discuss this with the closer at User talk:Mattdaviesfsic#Recent non-admin closes at AFD, but the closer immediately stopped editing when that was posted and has not been active in the 11 days since. --Ahecht (TALK
PAGE) 17:11, 25 November 2024 (UTC)
- With this one honestly I think the thing to do is vacate the close entirely, and start a non-deletion discussion somewhere about splitting more lists out of that monster of an article. Enacting the close results in a 100+kB list being added back into an article that's already over half a megabyte; I said somewhere else that the resulting page would be in the top ten longest articles on Wikipedia by byte count, and I was already having problems loading the page on a gaming system that's less than a year old. More of the target article needs to be split off into companion articles and lists, not have more added back into it. Ivanvector (Talk/Edits) 17:30, 25 November 2024 (UTC)
- Overturn this is a BADNAC, fair and true, and should be quickly vacated. I have no comment on what should happen here. SportingFlyer T·C 18:29, 25 November 2024 (UTC)
- Overturn to no consensus. This is clear WP:BADNAC as there was nothing close to a consensus to merge, delete, or keep (or even to not keep with a delete/ATD split). These decisions are best handled by an administrator with significant experience closing AFD discussions. Relisting is an acceptable option as well, though I think it is unlikely any consensus will form based on the already high attendance. Frank Anchor 19:03, 25 November 2024 (UTC)
- Eh. Agree that this is obviously a contentious close, but given that the merge appears to already be in progress, I'd be inclined to leave this one. Normal editing can sort out whether all of the content is worth merging or just some of it. -- asilvering (talk) 20:33, 25 November 2024 (UTC)
- • Overturn This looks to me like a clear cut case of WP:BADNAC. There has been one try at merging already, but that one was reverted due to technical issues with size. Like @Ivanvector I am also having issues with the article loading without a merge of another large article, I am also on a Desktop Gaming PC. User Page Talk Contributions Sheriff U3 21:16, 25 November 2024 (UTC)
- Overturn, but definitely not to "no consensus" as there was a clear consensus against keeping the article as a standalone. JoelleJay (talk) 00:39, 26 November 2024 (UTC)
- Do not overturn to no consensus which would serve the participants poorly where there was clear consensus that it should not be kept. The merge could be pragmatically upheld (the information would necessarily be pared back in a merge through editor decisions) or it could be overturned to delete. Sirfurboy🏄 (talk) 08:00, 26 November 2024 (UTC)
- Vacate BADNAC but I am torn between merge, relist, and no consensus. Delete !voters ignore ATDs and the NOTNEWS arguments are simply tired and wrong, so there's clearly no consensus to delete, nor any policy-based way for such to develop with a relist. Jclemens (talk) 08:11, 26 November 2024 (UTC)
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
I think this should not have been deleted as large non-free, but was actually a mislabeled PD-text file. I brought this up on the copyright discussion noticeboard and received little notice besides one concurrence from Aafi. I would like the original file (dated 04:12, 13 October 2024) restored at full resolution so it can be moved to Commons as
|
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 would like to say that the deletion of this was unjustifible that it happned WITH OUT AN PROPER DEBATE and even the talk page was deleted I only have 1 question? why? I request for the talk page to be renstated and the flow debate to continue (it is to note no proper consisnes was reached) before the deletion of the article and again request the talk page to be renstated with also the article for the time being ( out of context - I swear if there is a loophole allowing this I don't even know what I will do to myself anyone likes cats here?) Sarim Wani (talk) 16:22, 19 November 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 am requesting a review of the deletion of the article "Jairam Kumar Mahato" based on new evidence and arguments not discussed in the original deletion discussion. Jairam Kumar Mahato was responsible for launching a notable movement in Jharkhand, India. Specifically, his protests led to changes in the recognition of regional languages, where languages such as Bhojpuri, Magahi, and Angika were included in the list of regional languages for state-level examinations in 11 districts. He strongly advocated for promoting local languages and demanded that jobs in the state be reserved for Jharkhand natives, preventing individuals from other states from gaining these opportunities. This qualifies him under Wikipedia's notability guideline for people as: 1. **Biography**: "The person has made a widely recognized contribution that is part of the enduring historical record in a specific field." 2. **Politicians and Judges**: "Major local political figures who have received significant press coverage." Additionally, he does not fall under "People notable for only one event," as his actions and media coverage span multiple related events (2 to be exact), thus meeting the threshold for separate documentation. If required, I can provide citations for these claims. Thank you for considering this request. Sarim Wani (talk) 10:54, 17 November 2024 (UTC)
Robert McClenon (talk) 18:21, 18 November 2024 (UTC)
Requesting for an independent actor to end debate with :
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |
- Alexander Tetelbaum (talk|edit|history|logs|links|watch) (restore)
- I ask you to consider restoring the page "Alexander Tetelbaum" as being deleted without fair justification by Diannaa.
- Initially, the reason for deletion was that the page had infringed Amazon copyrights. Namely, had an image and text about the book "Executive Director". The page never had this staff--only a reference to the book.
- Later, Diannaa changed the reason and stated the similarities between the page and Amazon's Author BIO. Yes, the two BIO's are similar and it must be expected--if they had been different it would mean that one of them or both are incorrect. Also, this BIO is not the property of Amazon and got into Amazon about 15 years later than was published in Wikipedia.
- Also, Dianna questioned notability. Alexander Tetelbaum was the founding President of the first Jewish University in Ukraine, the author of 20 books, and dozens more achievements.
- It took 5 seconds to delete the page and now Dianna suggested resubmitting the page--and this is 40-50 hours of work. There is also a difference in that the original page was created in 2007 vs. a possible new one.
- This does not look right when one person can make such decisions and constantly change the reason for deletion. In case of resubmission, it can be also rejected taking into account that we are not happy with how Dianna handled this issue and we are afraid of retaliation.
- I honestly do not see any serious arguments to remove the page with 17 history, fully true, and all facts are supported by multiple references. I do not want to speculate, but the page was deleted soon after Dr. Tetelbaum published his book "Executive Director" which had some criticism of Wikipedia. Also, he recently published a joke on X and Truth websites where Wikipedia was mentioned among other organizations.
- To conclude, I ask you to restore the page and if you see any issues, we will fix them. Thanks for your consideration.
- Respectfully, Natalie Heroux (nheroux) Nheroux (talk) 18:57, 13 November 2024 (UTC)
The editor couldn't figure out how to post here, so I have copied the above from my talk page at her request. Diannaa (talk) 19:42, 13 November 2024 (UTC)
- I can't check the old version, but copyright violation is one of if not the most serious reason to delete a page on Wikipedia, and Diannaa is one of the most experienced users here with dealing with copyvios. If the person is notable, there is nothing preventing you from starting a new version which does not copy text from anywhere else - and yes, it could be rejected for various reasons, but not liking the content is not one of those reasons. SportingFlyer T·C 20:25, 13 November 2024 (UTC)
- Nheroux appears to have misunderstood some of the things that I did. The deletion was triggered by a report at CopyPatrol for the book "Executive Director" Book, where all the content was a match for content present at Amazon. After redirecting this to the author article Alexander Tetelbaum I noticed that everything in the author's article was a match for content present at Amazon as well. Since Amazon's webpages are not archived in the Wayback Machine there's no way to confirm whether or the content at Amazon was copied from Wikipedia or the other way around. So absent that proof, I decided that the author's article should be deleted as well. I never changed the reason for deletion; I noted from the start that the article was a match for the content at Amazon, noting "foundational copyvio, copied from Amazon" in my deletion rationale. I suggested that a new article could be started in draftspace. Diannaa (talk) 20:45, 13 November 2024 (UTC)
- Endorse but you are welcome to start a draft in your own words, using independent reliable sourcing about Tetelbaum. Star Mississippi 01:54, 14 November 2024 (UTC)
- Endorse as a matter of taking copyright seriously, even when no one else on the Internet takes copyright seriously, and of trusting the judgment of an experienced copyright administrator. I have multiple comments:
- I doubt that the material was copied from Wikipedia to Amazon. If it was originally on Wikipedia, it should not have been. It is written in an Amazon style. It looks more likely that it was copied from Amazon to Wikipedia, and Wikipedia does not allow that.
- I find the claim that it will take 40-50 hours to write a biography of a living person to be lacking in plausibility, even if there was a large amount of information beyond the Amazon blurb that was deleted.
- If the appellant was the original author of the article, why didn't she keep a copy on her computer? I find pleas that an author needs the deleted Wikipedia article in order to start a new article unpersuasive. In 2024, large amounts of solid-state storage are cheap. I don't know why authors don't have copies.
- The deleting administrator refers to the Wayback Machine, and says that Amazon is not archived. But Wikipedia is archived. Even if the author forgot to keep a copy, doesn't the Wayback Machine have a copy? It is a copyright-infringing copy, but that is a legal detail, and it can be rewritten from.
- Notability is not mentioned in the deletion log. It is not necessary to argue that Tetelbaum is biographically notable.
- The appellant has already been asked about an association with Tetelbaum, which is a conflict of interest, and does not appear to have answered the question.
Robert McClenon (talk) 02:31, 14 November 2024 (UTC)
- Endorse The only relevant appeal for copyvio deletion is "It wasn't a copyvio, and here's why." This doesn't accomplish that. Jclemens (talk) 09:33, 14 November 2024 (UTC)
- Endorse and enjoin the appellant from editing this topic, broadly construed. The appellant created the page three times. The first two were essentially identical, while the third was a stub she expanded over the years to the version that was deleted last month as a copyvio. Statements such as,
this is 40-50 hours of work
andthe two BIO's are similar and it must be expected--if they had been different it would mean that one of them or both are incorrect
make it clear she is not here to copyedit, but to copy-paste. Her declared inability to write a bio that isn't a verbatim duplicate of the one published on Amazon tells us all we need to know. Her failure to respond to the question about COI, the aspersions cast against the deleting admin, the disruptive edits on her Talk page, her use of the first-person plural pronoun when talking about her edits, and the Tetelbaum-centric contribution history paint a clear picture. The only article we can expect from this SPA is a duplicate of the one that was deleted. I'd welcome a draft from an unrelated, experienced editor, but for the WP:TENDENTIOUS appellant, a topic ban would be appropriate. Owen× ☎ 14:12, 14 November 2024 (UTC) - Comment/Question - Deletion Review is a content forum. I agree with the criticism by User:OwenX of the conduct of the appellant, but what should we (DRV) do other than endorse the G12? Robert McClenon (talk) 06:57, 15 November 2024 (UTC)
- The closer, if an admin, can choose to action both pieces based on feedback from participants. Star Mississippi 15:36, 15 November 2024 (UTC)
- Nheroux has now stated on her talk page that she is the daughter of the subject of the article. She mentions that the content at Amazon also originated with her (no surprise there) and that's why they match. She thought if she removed it from Amazon there would not longer be a copyright issue (which is not true; that ship has sailed) but has agreed to my suggestion to instead start a new Wikipedia article on her father, rewriting with new content in draftspace. I have no comment on the still to-be-determined issue of notability. Diannaa (talk) 01:59, 16 November 2024 (UTC)
- Educating this editor on the proper way to do this seems like a win all the way around. Jclemens (talk) 21:12, 16 November 2024 (UTC)
- User:Nheroux wrote:
this BIO … got into Amazon about 15 years later than was published in Wikipedia
. - That’s good enough for us to accept that it is not a simple copyright infringement. It is, however, a WP:COI issue. COI authors are required to not write into mainspace directly.
- User:Nheroux wrote:
- Educating this editor on the proper way to do this seems like a win all the way around. Jclemens (talk) 21:12, 16 November 2024 (UTC)
- Undelete to draftspace. SmokeyJoe (talk) 09:56, 17 November 2024 (UTC)
- Draftification is not intended for articles that are more than 90 days old. WP:DRAFTNO. So I am opposed to this idea. Diannaa (talk) 13:54, 17 November 2024 (UTC)
- I think you're missing a piece of that RFC, @Diannaa. Consensus can be behind the draftification. Personally I think starting fresh would be easier if the editor really does intend to make a compliant article but that's also draft space so distinction without a difference unless you're opposed to giving her the material. Star Mississippi 14:32, 17 November 2024 (UTC)
- She already has the material, so refusing to give her a copy seems a little bureaucratic. So I am not opposed to giving her the material, but I don't see the point of doing so. Diannaa (talk) 14:37, 17 November 2024 (UTC)
- If it's not a copyvio, it makes more sense to restore the article to mainspace rather than move it to draftspace. Diannaa (talk) 15:48, 17 November 2024 (UTC)
- I agree with Diannaa here, I don't see the point of draftifying this if it's a copyvio where the author already has the original material. SportingFlyer T·C 16:16, 17 November 2024 (UTC)
- COI editors are required to use AfC to write articles. Draftification is retrospectively correcting their mistake. If the page is ok, an AfC reviewer will approve it. SmokeyJoe (talk) 20:20, 17 November 2024 (UTC)
- That makes sense to me. I have no preference where she creates the article. I just thought draft space would be easier for a relatively inexperienced editor without the threat of an AfD hanging over her article development. Star Mississippi 16:19, 17 November 2024 (UTC)
- I agree with Diannaa here, I don't see the point of draftifying this if it's a copyvio where the author already has the original material. SportingFlyer T·C 16:16, 17 November 2024 (UTC)
- User:Diannaa, you are referring to unilateral draftification. SmokeyJoe (talk) 20:18, 17 November 2024 (UTC)
- I think you're missing a piece of that RFC, @Diannaa. Consensus can be behind the draftification. Personally I think starting fresh would be easier if the editor really does intend to make a compliant article but that's also draft space so distinction without a difference unless you're opposed to giving her the material. Star Mississippi 14:32, 17 November 2024 (UTC)
- Draftification is not intended for articles that are more than 90 days old. WP:DRAFTNO. So I am opposed to this idea. Diannaa (talk) 13:54, 17 November 2024 (UTC)
- Overturn the G12 deletion. WP:G12 is not met, there is no unambiguous copyright violation. Send to XfD to resolve any doubt. —SmokeyJoe (talk) 21:43, 17 November 2024 (UTC)
- I am looking at some of the deleted revisions, and I do see it to be a copyright. Are you suggesting @Nheroux release the text for use, or otherwise that it's not a copyright violation? Star Mississippi 02:42, 18 November 2024 (UTC)
- Do you see an *unambiguous* copyright violation? There’s a claim that Nheroux published it all on Wikipedia first (thus released the text under the GFDL), making the Amazon copyright claim invalid, or at least generating enough ambiguity for it to go to XfD as an apparent copyright violation.
- If you are sure, then email the deleted page to her, that is allowed.
- In either case, Heroux is a coauthor on a for profit book with Alexander Tetelbaum, and that is a clear connection establishing a WP:COI, and Heroux is not allowed to write on Tetlbaum in mainspace, she must either use draftspace and AfC, or talk page suggestions.
- I think the copyright violation is ambiguous enough to justify an XfD. SmokeyJoe (talk) 06:21, 18 November 2024 (UTC)
- I am looking at some of the deleted revisions, and I do see it to be a copyright. Are you suggesting @Nheroux release the text for use, or otherwise that it's not a copyright violation? Star Mississippi 02:42, 18 November 2024 (UTC)
- Overturn. Justifiable suspicion but the suggested scenario of this content proliferating from Wikipedia onto Amazon is very plausible, and the deleted article (accessed via the Wayback Machine) does resemble a legitimate Wikipedia article, and copied content often doesn't. Editors should look at this and figure it out in an AfD.—Alalch E. 20:22, 20 November 2024 (UTC)
- ...or rather, at WP:CP —Alalch E. 11:45, 26 November 2024 (UTC)
- Overturn. The article was created on 25 February 2007, and he didn't start publishing books through Amazon until 2017 or so, so I have no reason to think Nheroux's claim that the profile
got into Amazon about 15 years later than was published in Wikipedia
isn't correct. At a minimum there's enough ambiguity to send it to a discussion (which would be at WP:CP, not AfD). Extraordinary Writ (talk) 07:17, 25 November 2024 (UTC)
2024 Duki coal mine attack (closed)
|
---|
The following is an archived debate of the deletion review of the page above. Please do not modify it. |
Firstly, AfD is not the right forum for MERGE or REDIRECT discussion. Let me also remind that it's WP:NOTAVOTE. Secondly, the over a dozen references within the article itself assert notability while fulfilling and meeting the WP:GEOSCOPE, WP:DIVERSE and WP:NCRIME criteria of WP:NEVENT which reads:
Thirdly, at the expense of being called out for WP:OTHERSTUFFEXISTS, I'll still say that having articles on street brawl and stabbing incidents in the West but not one on a terrorist incident that occurred outside of an active warzone in the Global South is a pure example of WP:GEOBIAS. — Mister Banker (talk) 19:24, 8 November 2024 (UTC)
|
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it. |