Revision as of 02:36, 29 August 2006 editH (talk | contribs)23,582 edits →stupid bloody icons← Previous edit | Latest revision as of 04:46, 22 January 2025 edit undoJclemens (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers45,526 editsm →merge proposals: typo | ||
Line 1: | Line 1: | ||
{{Skiptotoctalk}} | |||
{{shortcut|]<br>or ]}} | |||
{{Talk header|noarchive=yes|WT:AFD}} | |||
{| class="infobox" width="270px" | |||
{{FAQ|collapsed=no}} | |||
|- | |||
{{WikiProject banner shell| | |||
!align="center"|]<br>] | |||
{{WikiProject Deletion}} | |||
---- | |||
}} | |||
|- | |||
{{Press | |||
| | |||
| subject = project page | |||
*], ], ], ], ], ], ] | |||
| collapsed=yes | |||
*], ], ], ], ], ] | |||
|author= Noam Cohen |date= 8 October 2006 |url= http://query.nytimes.com/gst/fullpage.html?res=9D0CE3DF1330F93BA35753C1A9609C8B63 |title= Misplaced Pages Wars: Giving the Heave-Ho in an Online Who's Who |org= New York Times | |||
* ], ], ], ], ], ], ] | |||
|author2=David Segal |date2= 3 December 2006 |url2= http://www.washingtonpost.com/wp-dyn/content/article/2006/12/02/AR2006120201111.html |title2=Look Me Up Under 'Missing Link': On Misplaced Pages, Oblivion Looms for the Non-Notable |org2= Washington Post | |||
*], ], ], ], ], ], ], ], ], ], ] | |||
|author3= Daniel Terdiman |date3= 11 January 2007 |url3= https://www.cnet.com/news/to-delete-wikipedia-entry-or-not-to-delete/ |title3= To delete Misplaced Pages entry or not to delete? |org3= CNET News | |||
*], ] | |||
|author4= Matthew Moore |date4= 1 October 2009 |url4= http://www.telegraph.co.uk/technology/wikipedia/6250515/Wikipedia-20-articles-earmarked-for-deletion.html |title4= Misplaced Pages: 20 articles earmarked for deletion |org4= Daily Telegraph | |||
<small>Renamed ''Articles for deletion'' about this time.</small> | |||
}} | |||
*], ], ], ], ], ] | |||
{{archives|collapsed=yes|search=yes|auto=short|bot=MiszaBot|age=25|index=/Archive index| | |||
|}<!--Template:Archivebox--> | |||
{{Misplaced Pages:Archived delete debates/Page history}} | |||
__FORCETOC__ | |||
* ] (]) | |||
==Voting symbols== | |||
}} | |||
Symbols that may be used whilst voting: --] 02:18, 29 August 2006 (UTC) | |||
{{Search deletion discussions|small=yes}} | |||
==A newbie has a problem with the deletion process== | |||
{{User:MiszaBot/config | |||
|archiveheader = {{aan}} | |||
|maxarchivesize = 250K | |||
|counter = 78 | |||
|minthreadsleft = 4 | |||
|algo = old(25d) | |||
|archive = Misplaced Pages talk:Articles for deletion/Archive %(counter)d | |||
}}{{User:HBC Archive Indexerbot/OptIn | |||
|target=/Archive index | |||
|mask=/Archive <#> | |||
|leading_zeros=0 | |||
|indexhere=yes | |||
}} | |||
== Tool XFDcloser == | |||
Is there a way or tool to check how many closures an editor has performed, particularly when the XfD closure has resulted in a '' 'keep' ''? ] (]) 05:18, 8 January 2025 (UTC) | |||
I was looking for an administrator to help me with a article deletion process, and "Requests for administrator attention" sent me here. I edited a section of an article, restoring chronological order and NPOV mostly, but also various little but necessary tweaks like a broken ref and redundacy. Part of the changes is under discussion on the talk page. | |||
:https://sowhy.toolforge.org/afdcloses.php? ] (]) 05:27, 8 January 2025 (UTC) | |||
::Yes, thank you. ] (]) 05:32, 8 January 2025 (UTC) | |||
== Requiring Google Scholar for BEFORE == | |||
Someone created a new article copying the pre-edited content whole with POV and errors hours later, then went and linked it from many article. I was unfamiliar with the deletion process so I went and read the deletion policies. I couldn't find anything relating to this particular problem: is it OK to bypass the discussion process and simply create a content fork using old material? I'm not asking about weither this particular section deserve it's own article (I think it don't, it's just one controverstial ad campaign among many others and merely a content fork to evade debate), but rather what is appropriate for me to do in this situation (afd, proposed deletion or speedy?) and what arguments I'm supposed to make since they don't mention content forks. I can't go and edit the new article either, since it's the basicly the same content as in the main article and still under discussion on the talk page. I'll just be accused of silencing criticism anyway (again). Any help is appreciated. ] 23:54, 13 August 2006 (UTC) | |||
:Content can be split out from articles. I notice that ] is a very long article, so if the content was originally in that article and moved to ], that would make sense. However, most of the detail about the campaign seems to have been left in ], so if a split is being done then some of the material in the PETA article should be cut down. Alternatively, you could turn ] into a redirect to ], discussing it on ] if necessary. I don't think an AfD is necessary - a redirect would make more sense. --]<sup>]</sup> 00:01, 14 August 2006 (UTC) | |||
BEFORE (D)(1) currently states {{tq|The minimum search expected is a normal Google search, a Google Books search, a Google News search, and a Google News archive search; Google Scholar is suggested for academic subjects.}} (links omitted) Given our relatively robust access to academic sourcing through the Misplaced Pages Library, and the number of recent AfDs I've seen that have completely missed obvious Google Scholar sources on fictional literature (e.g., ], ]), I'd like to make Google Scholar expected, rather than "suggested for academic subjects". We have a lot of pop culture media and literature that are being addressed as "academic subjects" and I believe the current wording doesn't well serve the encyclopedia. | |||
:If you think it has been forked off just to provide a POV you should discuss it on the talk page (and make sure that editors from both articles are involved). This may be useful in the discussion: ]. It is only a guideline but at its root it goes back to ], so if you are unable to resolve the problem on the talk page you could list at AFD as a POV article. ],] and ] are (possibly less aggressive) alternatives to listing it for deletion if you can't resolve it amongst the editors. ]] 00:13, 14 August 2006 (UTC) | |||
:1) Is there a good reason to ''not'' add Google Scholar to the expected list for general topics? | |||
:1a) Could we wordsmith it so that obviously non-academic topics such as BLPs are excluded? | |||
:2) Is going from 4 to 5 expected searches ''too much'' effort? If so, would it be appropriate to swap out one of the other four? | |||
I believe the encyclopedia suffers when things that are clearly notable are nominated for deletion, and I'd like to make sure our efforts here are the best balance of making the nominator do ''appropriate'' work to find and evaluate the most obvious sources before creating work for the community and administrators. ] (]) 00:11, 13 January 2025 (UTC) | |||
:I'd support that. I think common-sense exceptions already apply (you don't need to check Google Books for a breaking-news story), but if that's a concern we could just stick an "in general" on the front. To compensate (or either way, honestly), we should get rid of the Google News Archive search, which ]. ] (]) 00:20, 13 January 2025 (UTC) | |||
:::I would oppose this, but only because access to the Misplaced Pages Library is contingent on time (one has to be active for six months if I am remembering correctly), and one has to apply for access (which may not have been done by all participants at AFD). There are enough access barriers in place that I don’t think this can be required.] (]) 00:25, 13 January 2025 (UTC) | |||
::::One need not have access to the Misplaced Pages Library to use Google Scholar; it's just a great tool to get access if you want to see "does this scholarly article really cover this topic in depth?" for those who don't have access to a University library's online collections. So to clarify, the Google Scholar search would be expected, Misplaced Pages Library use would be ''recommended'' as it already is per (D)(2). ] (]) 00:39, 13 January 2025 (UTC) | |||
::::Oh, and to clarify: BEFORE is only about the nominator's pre-deletion expected work. Nothing about BEFORE creates any obligation on anyone other than an AfD nominator. ] (]) 00:46, 13 January 2025 (UTC) | |||
:::::I think you are splitting hairs here. Simple facts: 1. Google scholar's materials are in most cases behind paywalls and are not viewable to most people. The assumption that people can still use it without the Misplaced Pages Library is false. 2. Those without a university library access are unlikely to be able to access the majority of materials. 3. The Misplaced Pages Library has spotty access to the works in google scholar with roughly a 1/3 of all materials remaining unavailable even with an account (more or less depending on the content area; many law and science journals for example tend to be not viewable even with a Misplaced Pages Library account ) 4. Users cannot qualify for the Misplaced Pages Library until 6 months after their user account creation and if they have meet the minimum editing participation requirements as required by that application. 5. AFD participation is open to all and those with a user account can make a nomination not long after account creation. 6. Imposing this rule would stop new people from having access to making AFD noms due to Misplaced Pages Library access rules and it make enrollment compulsory. | |||
:::::Fundamentally, we can't put a rule in place that creates a barrier to free and open access to AFD nominations. Making Misplaced Pages Library enrollment compulsory (which is the effect of what you are proposing) to participate in the AFD process is morally wrong. It doesn't fly. '''We are an encyclopedia anyone can edit.''' That includes AFD. The spirit of that policy is an ethical core must for the project, and per that reason this is a hard no we can't do this from my point of view.] (]) 08:36, 13 January 2025 (UTC) | |||
::::::First, no one has suggested that actual access to materials must be gained. That's not what the current document says, and no proposal to change it has been advanced. Second, your objection would also be an objection to BEFORE as currently written--I'd really rather you provided a critique in the context of the change from current practice; you're treating this as if it's a new proposal rather than a tweaking of existing expectations. Third, your ethical argument fails as deletion is asymmetric--it's far easier to destroy content through a misapplication of deletion policy than it is to create new content--which is why 'deletion' and 'editing' are different concepts. Misplaced Pages never promises to be the encyclopedia from which anyone can delete articles. In fact, the majority of our editing tools, including content removal within an article, are arbitrarily reversible, which is why anyone can do them. Deletion, of course, is outside the scope, only being doable or reversible by administrators. ] (]) 09:04, 13 January 2025 (UTC) | |||
::I have no issue deprecating or outright deleting the Google News Archive search. It's not linked on {{tl|find sources}} and I haven't used it in so long I wasn't even aware it didn't work. ] (]) 00:42, 13 January 2025 (UTC) | |||
:::I've just gone ahead and removed Google News Archive; it didn't seem to have any defenders the last time I mentioned it either. Happy to discuss if anyone disagrees. ] (]) 09:11, 13 January 2025 (UTC) | |||
::::I would have preferred this been dealt with as one change, as folks seem to be disagreeing about things that area already part of the expectations. That is, I don't think people perceive that upgrading scholar and removing Google News Archive together make a net zero change in effort required of nominators. ] (]) 17:24, 13 January 2025 (UTC) | |||
:The two examples you put forth call into question the necessity of doing so. For the Spacing Guild example, the first example appears to be a single paragraph, not the sort of in-depth coverage we expect; the Guild is not mentioned in either the abstract of the article or the first page of the article shown on the store page. The second doesn't look deeper. Meanwhile, in both deletion discussions you cite, there look to be enough non-Google Scholar-ly sources to render a Keep. ] is already a burden; before we increase its weight, I'd want to see not just that Scholar can point to sources on such topics, but that it can point to sources on such topics that would not have had enough sources through other means already required by BEFORE. -- ] (]) 01:10, 13 January 2025 (UTC) | |||
::There are more examples; I picked two. Whether you agree that those are sufficient to demonstrate GNG being met by themselves misses the point--it is the nominator's job to find such obvious issues and either make a compelling case for non-retention (merging, etc.) despite the presence of that coverage or to abandon the idea of a nomination. As far as scholar vs. other choices, I'd actually argue that Scholar is probably more useful than a "vanilla" Google search, in that if we can identify multiple truly relevant hits in Google Scholar, the value of those hits is sufficiently higher than a random plain Google search hit that it is more ''efficient'' to evaluate Scholar sources first, rather than basic Google hits. ] (]) 02:31, 13 January 2025 (UTC) | |||
:::No, I don't think it misses the point if this added effort is just going to identify as keepable things that would be identified as keepable anyway. ] is a problem here, and is my concern with this proposal. -- ] (]) 02:37, 13 January 2025 (UTC) | |||
::::The entire point of BEFORE is to identify as keepable things that would ideally be identified as keepable in an AfD discussion, but to put the workload on the nominator so AfD discussions aren't either 1) a waste of time, or 2) risking deleting something notable because no one is paying attention. This changes nothing about that, merely seeks to optimize the work that's already expected of nominators. ] (]) 05:23, 13 January 2025 (UTC) | |||
:::::Yes, but if the only things doing this step is going to identify as keepable are things that should've been detected by the other existing steps of BEFORE, then it's just putting an unneeded additional step on the process. So that's the question I see before us. And if you say "I found it in these articles, so it was something that the nominator should've checked", that's an argument that can be made for checking ''everything'' that gets discovered during AfD. -- ] (]) 06:08, 13 January 2025 (UTC) | |||
::::::Ah, I see--you're saying that if the nom had done the rest of BEFORE correctly, this wouldn't be an issue. I can't disagree with that, but I am very much trying to make sure processes are optimized before considering approaching this as a user conduct issue. I will take issue with the ''additional'' characterization: It's already listed as a suggested step, I'm just proposing we change it to be clear when we can reasonably expect it to be beneficial. I completely agree that we shouldn't be doing box checking, but rather intelligently searching out the most relevant couple of web search methodologies likely to generate ''usable'' sources. And, as noted above, I'm also suggesting we consider if this should be prioritized, should another expected search step (or more?) be deprecated to avoid making the pre-nomination burden unwieldy? How can we get the best outcome with the least required work on the nominator's part. | |||
::::::Just as a side note, this whole section feels like teaching EMT class. We give students about 20 things to check in order in patient assessment, and once they've demonstrated they can do them in a regimented fashion, we turn them loose to parallelize those tasks (e.g. checking skin warmth and a radial pulse simultaneously). BEFORE should ideally be that sort of thing that transforms from a formal checklist into a natural methodology that skilled nominators can breeze through. ] (]) 08:00, 13 January 2025 (UTC) | |||
*'''Oppose''' I am the sort of elderly nerd that read ''Dune'' well over a half a century ago back when SciFi seemed "very important" to me, and I will not bother to mention all the other portentious novels I read back then because there were just too many. But the notion that we need to force AfD nominators to use Google Scholar in their BEFORE search for sources about pop culture topics comes off like a Saturday Night Live skit to me. If another nerd wants to use Google Scholar to find sources to save an article, then bravo! But let's not force other editors to be nerds against their will. ] (]) 08:57, 13 January 2025 (UTC) | |||
*:To clarify: You're fine with Google, Google News, Google Books, and Google News Archive being required as it stands now? ] (]) 09:05, 13 January 2025 (UTC) | |||
*::No, I am not fine with that, {{u|Jclemons}}. Sadly, Google News Archive has been worthless for years, so getting around to removing it makes sense. If someone wants to use ] instead of Google, why should we object? I am fine with suggesting tools to editors but not fine with forcing them to use tools. ] (]) 19:00, 13 January 2025 (UTC) | |||
*:::So, the status quo requires specific tool use. How would you prefer we improve it? I think you make a great point about general purpose search engines--we should not be requiring a specific for-profit company's tools be used for a free as in freedom project. Is there a Bing equivalent to Google Books, Google News, and/or Google Scholar? ] (]) 20:19, 13 January 2025 (UTC) | |||
*::::Well, then there is something wrong with the status quo. I am not a regular Bing user so cannot comment on their range of offerings. I use many Google products including several for running my small business unrelated to Misplaced Pages. I use them because I freely choose to, not because someone forces me to. ] (]) 03:26, 14 January 2025 (UTC) | |||
*:::::Again, how do you propose we improve on the status quo? Would it be appropriate to change {{tq|normal Google search}} to {{tq|a robust general-purpose search engine search, such as Google or Bing}}? ] (]) 06:10, 14 January 2025 (UTC) | |||
:Not against adding Scholar but a caution that it's listing's often include thesises and other non peer reviewed grad school output, more commonly seen for non traditional academic topics, which themselves aren't reliable. Editors should be checking for sources in non predatory journals with Scholar searches.<span id="Masem:1736789522587:Wikipedia_talkFTTCLNArticles_for_deletion" class="FTTCmt"> — ] (]) 17:32, 13 January 2025 (UTC)</span> | |||
::This is absolutely a balancing act. Scholar, just like the other search engines, is a great way of identifying things to be further investigated. The main use in a BEFORE search is the negative result: If a topic isn't covered at all, no further work is needed and the AfD proceeds. If there are results, then things get a bit more nuanced about what should happen next, as you can see from the rest of the discussion above. ] (]) 20:21, 13 January 2025 (UTC) | |||
== Process == | |||
::For now I'm redirecting the fork back to the main article. I've given an explanation on the fork and it's editor talkpages. As well as initiated a discussion on the main article in addition to the content dispute. I do think it was meant as a sort of pov fork, but we'll discuss it, maybe fork it later. It should be fine. ] 00:50, 14 August 2006 (UTC) | |||
I have marked ] for deletion and kindly request that someone complete the process for me. Thank you very much. ] (]) 19:41, 13 January 2025 (UTC) | |||
==seperate closed discussions== | |||
== ] == | |||
Would it be reasonable to move closed AFDs to a seperate page, and replace them with a one line summary & link? The sheer size of the daily log and the time it takes to load is hard to work with; seperating the ones that are no longer open for discussion seems like the simplest way to shrink this. -] 16:48, 14 August 2006 (UTC) | |||
:Sounds like a good idea to me. At times, there are over 200 AfD's, some of which have a response rate of 15 or more bullet point statments. Lets see if we can get a consensus though. ] 16:51, 14 August 2006 (UTC) | |||
::I'm for it. Speedy deletes and closed relisted discussions can sometimes take up half the log page even on the day they are listed. ]] 17:11, 14 August 2006 (UTC) | |||
:::I'm not. It would create more unnecessary work for admins closing discussions for the sake of - what - people having to press Page Down less often? We have enough of a backlog at ] as it is. Scrolling down a list of 100-200 AfDs (Ctrl-F doesn't work on the edit window) looking for one in particular is annoying enough on the few occasions I'm relisting an article (taking it out of the old log and inserting it into a new one). If I had to do it on every single AfD, I would in all probability stop doing one of my favourite admin activities. Without wanting to sound elitist and "har har you don't know what you're talking about", none of the above three supporters are admins and I'm not sure they appreciate how annoying this extra step on an already sufficiently burdensome process would be. --]<sup>]</sup> 17:21, 14 August 2006 (UTC) | |||
I would appreciate some regular AFD reviewers commenting on this page. There's been lots of activity from potential ] accounts, and it would be good to have some clearly non-partisan people participating. All opinions are welcome.] (]) 01:30, 14 January 2025 (UTC) | |||
To endorse Sam's position, we used to have that step as part of the archiving procedure. It was never properly followed. We lost a lot of deletion discussions that were never properly archived. We got into countless arguments over renominations - arguments which we have been able to quickly solve since we changed to this archiving procedure. | |||
== Semi-protected edit request on 14 January 2025 == | |||
What you can do instead is to create a .css subpage which will automatically hide all the closed discussions from ''your'' view while leaving it visible for people like Sam who still need it. Instructions follow. ] <small>]</small> 19:31, 14 August 2006 (UTC) | |||
Please either correct completely or else delete the article on Govinda (actor) Sir immediately as it is libellous and false. Based on communication from Misplaced Pages Foundation Legal Counsel office we had posted an edit request on article talk page. It is more than 36 hours, actually 72 hours and the libels have not been removed and our communication completely ignored. Hence you are once again requested to completely remove all defamation and libels from article page of Govinda Sir. NB: As per laws of India, Misplaced Pages is a PUBLISHER irrespective of what other persons may have published elsewhere. | |||
# Check your preferences and see which Skin you are using. The default is "monobook". | |||
# Create a new page titled ] (where "Foo" is your username and "skin" is the name of your skin - mine is at ]) | |||
# Paste ".vfd { display:none; }" into the new page. | |||
# Save. | |||
# To disable the hiding, go back to your style page and temporarily blank it, then reload the AFD page. Note: You may have to manually purge your computer's cache. | |||
I am unable to post to this page as I am a new user. ] (]) 04:51, 14 January 2025 (UTC) | |||
I'm sure we all know how burdensome the the process is. I just wanted to know if it was reasonable to make the page a bit smaller, so we wouldn't have to wait so long for it to render each time, since this makes it more tedious to participate in the discussion. | |||
:{{u|अधिवक्ता संतोष}}, there is no chance that an article about a very well known actor and politician such as ] will be deleted. That is simply not going to happen. As for your request at ], it is far too vague. You need to explain ''specifically'' why the content that you want removed violates Misplaced Pages's ]. ] (]) 05:04, 14 January 2025 (UTC) | |||
::Kindly note that we are not concerned with Misplaced Pages Policies and Guidelines as they have no legal force India and are not compliant with requirements of India's internet regulations. As per the advice of your legal Counsel We have approached the editor community to voluntarily correct all self evident libels in Govinda Sir's article which have been inserted by his political opponents using anonymous user IDs and IP addresses. Also note that defamation in India is a criminal offence unlike USA and definition of defamation in India is also quite different from USA's. Since this website is allowing , you may either correct / delete the article within 36 hours or else surrender intermediary status in India. ] (]) 05:33, 14 January 2025 (UTC) | |||
:::I strongly recommend that you look at ]. ] (]) 07:08, 14 January 2025 (UTC) | |||
:::@] - to be clear, ] is to '''delete libel as soon as it is identified'''. However we need you to tell us what specific statements in the article you believe are libelous and should be removed. The statement about "failed acting career" has already been removed, but what else would you like to see delete? The people you have already engaged with are trying to help, but they cannot to ''read your heart and mind'' so we need you to tell us what you think should be removed. If you are not satisfied with the assistance of these volunteers, you're welcome to email info-en-q{{@}}wikipedia.org who can directly assist you further. ] ] 07:11, 14 January 2025 (UTC) | |||
::::Thanks for your assistance. What you are proposing is a chicken-egg pretzel logic situation. We have availed the info-en-qwikipedia.org and our email was forwarded to Wikimedia Legal Counsel who suggested we make an edit request on the talk page. Only when this was not acted upon speedily did we post to this forum. The policies of this website, being grounded in USA laws, do not apply in India where defamation is primarily a criminal offence not a civil action. A person from India who is being defamed cannot be compelled to acquiesce in surrendering their legal protections afforded under India's laws to sue/prosecute by polices such as WP:NOLEGALTHREATS. In which case, it would be far better that this website does not publish articles on Indian data subjects, as such policies and also those like WP:VERIFIABILITY and WP:RELIABLESOURCES do not apply under India's new data protection regime which incidentally . In the alternative, Wikimedia can appoint a so that aggrieved persons or their lawyers do not have to publicly deal with unpaid volunteers who are mostly ill-equipped to handle what they perceive to be legal "threats" conveyed in the form of due legal notice. ] (]) 07:59, 14 January 2025 (UTC) | |||
:::::@], do note that we ''are'' unpaid volunteers, and that when we see calls to legal action, we usually block people as we are unable to deal with these complaints and any party who would wish to file suit would '''know''' to file with the right body, the Wikimedia Foundation. Given the legitimacy of your complaint, nobody has blocked you and the defamatory content has been resolved. If there ever end up being grounds for legal recourse, again I will stipulate that is the business of the Wikimedia Foundation, not for a bunch of unpaid internet users—the internet users can only modify pages, not deal with legal paperwork. However, in most instances, as the people you emailed told you to do, simply asking for removal of the damning, untrue content on a page works perfectly fine. Which it did here. Because unpaid internet users can remove content on pages. It's really the question of invoking the right tool for the job. Thankfully, as you have performed the steps that you have performed, the defamatory content is resolved, which resolves the dispute before any legal action needed to be taken. Have a nice day. <span style="background: cornsilk; padding: 3px;border:.5px solid salmon;">]]</span> 13:05, 14 January 2025 (UTC) | |||
::::::I would posit that any further push by this user for additional, unspecified actions, while continuing to spout legalese, should be considered in violation of ]. - ] ] 13:36, 14 January 2025 (UTC) | |||
:::::::The user is now blocked for legal threats. They absolutely had a legitimate grievance, and may have others, but they are going about it the wrong way. ] (]) 12:03, 15 January 2025 (UTC) | |||
== Repeating AFDs and prior consensus == | |||
If admins don't want to do it (and of course, why would they) couldn't a bot just summarize the closed AFDs, and leave a link to the full discussion? | |||
When reviewing new articles, I focus on company topics which were previously deleted at AFD as non-notable. Does the new article and/or available references indicate that the topic is now notable? If not, a new AFD is needed. | |||
It looks like Rossami's css doesn't quite do what I wanted, but seems to speed rendering up enough that I'd do something like that anyway. But a few small changes to a few templates would probably make it feasible to keep a summary and block the discussion. -] 20:26, 14 August 2006 (UTC) | |||
Because of the low participation at AFD these days, these then rattle round the relist cycle. The soft-delete option is unavailable to reviewing Admins, precisely because of the previous AFD deletion. This seems a somewhat perverse position - that an article can't be deleted because of the previous consensus to delete! | |||
:FWIW, while I was closing deletion discussions during my lunch break at work, I had to use Internet Explorer rather than Firefox to view the daily log, as viewing it in Firefox would crash the crappy company laptop. So I don't object in principle to making the daily logs shorter. However, it certainly shouldn't be a human activity, and I'm unsure about bots. For example, when deciding how to 'summarise' the debate, I assume that would involve saying what the outcome was, and for a bot the natural choice would be to pick out whatever the closing admin highlighted in bold. However, not all discussions get closed with a single term in bold - while the majority are ''''keep'''', ''''delete'''', ''''transwiki'''', etc, in some cases it can be more complicated. For example, in nominations involving multiple articles, "'''Delete''' ] and ], '''keep''' ]." Or I may use bolding once for the outcome, then once again for emphasis in my reasoning. Or I may just forget to bold the outcome at all. | |||
:Really, that's the sort of reasoning that should be left up to those that can actually create bots and know more about the difficulties. All I can say is, I freely admit that I was in the extreme minority when I got annoyed because I had to use a slow browser during part of the process, and wouldn't consider suggesting any more than the most minor change to remedy that. --]<sup>]</sup> 21:43, 14 August 2006 (UTC) | |||
::Wasn't there an experiment with closing *FDs by deleting all the content/discussion except the closing admin's result, and then compressing that between the {{tl|*fd top}} {{tl|*fd bottom}} templates? A link to the last full-screen edit might be useful for those who wish to view it. | |||
::Another option would be to use the new hide/show tags, if they ever get the crossbrowser/crossskin bugs worked out. -- '']']'' 21:54, 14 August 2006 (UTC) | |||
:::Using noinclude tags in the closing templates might be a solution - it wouldn't create any more work for the admins, but properly implemented would make the discussion disappear from the log page while still appearing on the article page.See what I mean: ] and ] just has noinclude added to the closing templates. There's probably some escaping to take into account as it's one stage removed from the template and it needs a link to the discussion page, but it did take me all of 3 minutes, so you'd expect some polishing to be needed. ]] 22:33, 14 August 2006 (UTC) | |||
::::Well, that would have been a good solution if <nowiki><noinclude></nowiki> tags could be nested or escaped, but a little research has revealed that isn't yet possible. ]] 12:08, 15 August 2006 (UTC) | |||
:::::Check out this lovely bit of voodoo by ], found ]: <code><nowiki><incl<includeonly>u</includeonly>deonly></incl<includeonly>u</includeonly>deonly></nowiki></code>; might be a place to start. -- '']']'' 15:04, 15 August 2006 (UTC) | |||
::::::Ah, I was playing around with splitting the tags, but not embeding the other tags inside them. I'll have another go. Nice, thanks. ]] 15:07, 15 August 2006 (UTC) | |||
::I was thinking to summarize the debate by keeping at least the name of the article and the admin's result, and possibly the reason for the nomination, but moving the discussion somewhere else, and leaving a link to it. I agree with Sam Blanning that it wouldn't be useful to try and sumarize the admin result. I've forgured out a way to reduce these using css, as Rossami recomended (thanks!): | |||
So to my suggestion... If a previous AFD decided on deletion (except on TNT grounds), then any subsequent AFD which has not attracted a "keep" opinion can be closed as deletion after 7 days, in line with prior consensus. | |||
div.vfd dl{display:none} | |||
div.vfd ul{display:none} | |||
Views? ] (]) 08:46, 17 January 2025 (UTC) | |||
Which seems to kill most of the discussion, while still listing the the result, and leaving a lik to at least the wikitext discussion. Using a bot to move/delete the discussion would be a nice way to make things simpler for people to participate without css hacking, though. -] 14:21, 15 August 2006 (UTC) | |||
:Why should a discussion be closed as delete if everyone !votes "merge"? ] (]) 10:03, 17 January 2025 (UTC) | |||
==voodoo== | |||
Thanks to the Voodoo from Nae'blis, I have a working version of the afd templates that compact the closed discussions down to title and result, without the need for a new page and let you see the full discussion by clicking on a link. | |||
:"an article can't be deleted because of the previous consensus to delete" - Well, soft deletion works by pretending like the AfD is an expired, uncontested PROD; recreating the article is, in effect, contesting the PROD, so it is by design that soft deletion is not allowed a second time. However, I am partially sympathetic to your point, and would like to distinguish between two different situations: | |||
See: ] for an example. | |||
:#The article was soft deleted at AfD the first time. In that case, the article never gained consensus for deletion, so a recreation should not be eligible for soft deletion. | |||
:#The article was hard deleted at AfD the first time. In that case, it might be eligible for speedy deletion under G4, but that could be controversial, and edge cases should be brought to AfD. For this situation, I think soft deletion could make sense, but as a theoretical framework we should not be treating it as an expired PROD, but rather requiring an affirmative consensus to overturn a previous consensus to delete. Currently, there is no consensual process to overturn an AfD that resulted in deletion on substance, as opposed to on procedure (which would be DRV), with the only option being to try recreating an article and see if somebody nominates it for G4 or AfD, making it a very capricious process. | |||
:]]]] 17:50, 17 January 2025 (UTC) | |||
::What if the original soft-delete was of an article that was about a different topic with the same name? | |||
::No, personally I cannot see why recreations should not be treated as new articles. PROD/soft delete should not be avoidable on mere technicalities - someone should have to act to avoid them. ] (]) 12:11, 20 January 2025 (UTC) | |||
:This proposal makes sense as long as you adjust {{tq|which has not attracted a "keep" opinion}} to {{tq|which has not attracted a "keep" or "merge" opinion}}. '']''<sup>]</sup> 23:46, 18 January 2025 (UTC) | |||
::Or a "redirect" for that matter! Really, this is about the "empty room" discussions: ''"<AFD rationale>,(Project listings),(silence),<relist>..."'' where a previous AFD decided on deletion (meaning after actual discussion, not soft-deletion). Perhaps I should have said "...which has not attracted <strike>a "keep" opinion</strike> ''substantial response'' can be closed as deletion after 7 days...". ] (]) 15:20, 19 January 2025 (UTC) | |||
== merge proposals == | |||
It doesn't require any more work from admins as far as I can see: although the reason for deletion is a parameter to the template, it defaults to delete (as most AFDs are deleted I believe) and automatically signs it for you, so in theory it should be less work. It's not the most attractive template code in the world, but does anybody care about that? ]] 16:45, 15 August 2006 (UTC) | |||
I feel like lately there have been AFDs that are actually merge proposals showing up pretty regularly. Policy would seem to indicate that the administrative reaction to this would be to ] if we catch them before anyone has voted to delete and/or all comments agree with a merge. I just found myself closing one as "merge" as it was the result, but at the same time not what AFD is for. I guess I'm asking if others agree that speedy keep is the correct close, and can be done at any time if there are no conflicting comments to delete or whatever? ] ] 22:47, 21 January 2025 (UTC) | |||
:I like it. I'm not sure if everyone would agree with hiding the heading & removing it from the TOC, since that could confuse people. I agree substing the sig is the way to go; I do that when I add the afd2, also. Could you post a link to the template? -] 19:10, 15 August 2006 (UTC) | |||
:Unless the notability of the article that's suggested to be merged is so obvious that it shouldn't be at AfD, I don't think we should necessarily be discouraging this. ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 23:02, 21 January 2025 (UTC) | |||
:Slick work. I notice that {{tl|afd top}} uses a noinclude tag to just avoid closing the div, so that {{tl|afd bottom}} can envelop the whole thing. Rather than making the reason for deletion a parameter, can you emulate this behavior instead? That would alleviate a lot of confusion on the part of closers who want to try adopting this. -- '']']'' 19:24, 15 August 2006 (UTC) | |||
::Should be totally discouraged. Deletion inclined editors will delete needlessly. ] (]) 04:31, 22 January 2025 (UTC) | |||
:Until and unless ] is implemented, yes, pure merge proposals do not articulate a reason for ''deletion'' and should be speedily kept and kicked back to the talk page. ] (]) 04:45, 22 January 2025 (UTC) | |||
The templates are here: ] and ]. I tried to think of a way round the parameter thing, but the reason for deletion is ''above'' the closing of the top template now (to allow the discussion to be enclosed in noinclude tags) rather than ''after'' it as it is in the current template. I can't see anyway of solving it without adding a third template {{tl|afd middle}} which would be more work. See if you can see any solution in the templates. ]] 19:54, 15 August 2006 (UTC) | |||
:it seems unlikely that there would be a good way around that. When it occurs at the very end, as it does now, it makes sense to keep it outside. In your version, probably not. One minor thing, it looks like you may have overdone the <includeonly>. Assuming I'm reading this right, they're only to break up special syntax, so you could just have an empty pair in key places, like <nowiki><<includeonly></includeonly>onlyinclude> or ~~<inlcudeonly></includeonly>~~</nowiki>, and the rest may be overkill. Nice effect, though. -] 21:36, 15 August 2006 (UTC) | |||
::Unless you use them to cover the whole of the tag in one way or another you get (partial) display of the tag when viewing the original template. It doesn't actually cause any problems but it looks ugly. I figured it was better to look ugly in the template itself. I fixed the heading so it appears in the summary btw (although the link is broken while it is in the user space it gives you an idea of how it would look) ]] 22:36, 15 August 2006 (UTC) | |||
:::I don't mind if the original template is jacked up (use a <noinclude> section to prettify it, if that's your concern), as it's only a Part 1 of 2 template; maintaining consistency with current template behavior would go a long way toward increasing the likelihood of this being adopted, IMO. Thanks for running with this, though... -- '']']'' 14:03, 16 August 2006 (UTC) | |||
::::I think we are talking at cross purposes (or I've lost the plot). I had to move the closing admin's comment to be a parameter to the template because it has to be inserted before the end of the {{tl|afd top}} template in order to allow the <nowiki><noinclude></nowiki> tag to start after it and above the discussion (otherwise the discussion will be visible or the result hidden). I agree it would be preferable to keep the process the same for the admins, but I can't see any way to do that and hide the discussion, which is the object of the exercise. I was hoping the fact that for a "Delete" result the admin would have less work (just pasting in the top and bottom templates) would offset the disagreeable business of changing the system. On a point of trying to get concensus maybe we should reopen this discussion somewhere where ''Category:Admins who do a lot of AFD closing hang out''? ]] 15:14, 16 August 2006 (UTC) | |||
:::::Aha. Yeah, I think I got sidetracked there. I don't see a clean way to get around that problem; being as we're already at ], I'd try ] to get more feedback (I've even included a handy new section header, at ]). -- '']']'' 15:29, 16 August 2006 (UTC) | |||
Is the entire aim of this to hide closed discussions so that the ones that are still open are easier to locate on per-day pages? We already have a mechanism for that. Being able to read prior discussion pages ''in their entirety without any extra hoops to jump through'' is useful, especially when articles are discussed again, as they sometimes are. (There have been several in the past few days alone.) Please don't prevent that. The discussion is just as important as the decision by the closing administrator. If your problem is with scanning through old per-day pages, please use the existing solutions for that. ] 17:38, 16 August 2006 (UTC) | |||
:The aim is to hide closed discussions on the log page - it does nothing to the discussion page itself. If you look at the examples above ] is how it would appear on the log page, ] is the discussion page (unchanged and in its entirety). It uses noinclude and includeonly tags to show different information on the log page and the actual page. ]] 17:53, 16 August 2006 (UTC) | |||
:The reason I started the thread is that one of the barriers to participating in AFD is that it takes so long to render the log page, and it gets rerendered each time you post a comment. So there is a fair amount of latency if you want to go along and participate in the discussions. Since there are so many that get speedied out quickly, the most obvious way to speed up the rendering is to only inline the discussions that you can actually participate in, and have the archived entries be visible, and only a click away if you want to get the details on this. It seems like if these templates are used to close the discussions, it would approximately double the rendering speed of the current log page, and probably have more of an affect on older pages. -] 18:04, 16 August 2006 (UTC) | |||
* You can also wrap the ''log page'' in a div, and do some fancy CSS to hide everything between the tags without using <nowiki><noinclude></nowiki>. For example, put a <nowiki><div class="afdlog"></nowiki> at the top of the page, and then do something like this in a global CSS page: | |||
.afdlog * div.vfd, .afdlog * div.vfd ul{display:none}; | |||
:]]<sup>(])</sup> 19:53, 16 August 2006 (UTC) | |||
:But since that only hides the items once they have been downloaded, so it wouldn't speed the load times would it? I doubt it would save much rendering time either as I suspect the hidden divs are rendered then hidden (but I must admit I know nothing about the internals of css rendering engines). The advantage of noinclude tags is the content is removed before it is served. ]] 20:03, 16 August 2006 (UTC) | |||
There's a better solution down at ]. ]] 20:32, 16 August 2006 (UTC) | |||
== Header - time stamps == | |||
Anyone think it would be a good idea for header on each AfD to say something like: | |||
<blockquote>Created: 10:20, 10 August 2006 (UTC); Current date: 18:20, 14 August 2006 (UTC)</blockquote> | |||
Similar to how an RfC header is, so that people can immediately see how much longer to go (barring early closure, of course). ] (]) 19:25, 14 August 2006 (UTC) | |||
: Don't you already know the start-time just by looking at the timestamp of the nomination? And does the theoretical end-time really matter since the AFD/Old page is usually backlogged by days or more? The instructions are complicated enough already. What does this extra step add? ] <small>]</small> 19:35, 14 August 2006 (UTC) | |||
::Just an idea, to make it even clearer, really, with the extra line of text at the top. It's not a big deal I guess. ] (]) 19:41, 14 August 2006 (UTC) | |||
:::RfCs close in 48 hours, so it's a big deal if I create an RfC at 23:58 on Monday, and an admin deletes it at 00:01 on Wednesday, after only running for one day and 3 minutes, just over half the time it's supposed to. That's why we judge '48 hours' to be from the very minute it starts. But AfDs run for a minimum of 5 days, and often don't get closed that early due to backlog. I've never seen anyone complain that an AfD only lasted four days and a bit instead of five - ok, I suppose they ''could'' complain about ~20% of potential discussion time being lost, but I can't imagine it being a solid reason for overturning. --]<sup>]</sup> 21:48, 14 August 2006 (UTC) | |||
::::The general rule was that you can't close a discussion until the log-page has been moved over to the /Old page - a bot-enabled action which happens pretty much right at day 5 plus or minus a few minutes. Other than speedy-closes (which have their own rules), I've never really seen anyone jumping the gun. I know the bot was down for a while but thought it was back up by now. ] <small>]</small> 23:06, 14 August 2006 (UTC) | |||
== stupid bloody icons == | |||
So, I notice that those "vote" icons might be making a comeback. If so, let's all try to do the sensible thing and hack them down mercilessly before the rot spreads in and Winamp gets stuck on Britney Spears for an hour, okay? ] (]) 12:23, 15 August 2006 (UTC) | |||
:Why? What does Winamp or Britney Spears have to do with this? Can you explain your objection using some sort of arguement? ] 12:54, 15 August 2006 (UTC) | |||
::The icons take up unnecessary bandwidth, make out that some editor's comments are more important than others (which in turn leads other editors to start using them in a race to the bottom), and furthers the misconception that AfD is <s>not</s> a vote. I would certainly encourage all editors to remove icons from comments they see posted in AfDs. --]<sup>]</sup> 13:00, 15 August 2006 (UTC) | |||
::''...and furthers the misconception that AfD is not a vote''. Uhh, Sam? One too many words there? -- '']']'' 14:50, 15 August 2006 (UTC) | |||
:::Thanks. --]<sup>]</sup> 19:14, 15 August 2006 (UTC) | |||
::Bah, that's what I get for trying to be funny. That's it, I'm off to the Monastery ... ] (]) 13:37, 15 August 2006 (UTC) | |||
:::One other reason for their removal: on debates with a ''lot'' of those icons, my computer freezes. I don't know if that's happening to anyone else, but it appears to be a further reason for their removal. ] ] 13:43, 15 August 2006 (UTC) | |||
::: Back to ye olde scary devil monastery, I take? ] 14:54, 15 August 2006 (UTC) | |||
:::: Oh, I'm not worthy to have those fine fellows delete all my files, send a threatening email to the boss in my name and trick me into corrupting the entire Accounts database ... ] (]) 08:24, 16 August 2006 (UTC) | |||
It's funny that there are almost adjacent threads on how people can make the discusison render faster, and this one on how people can make it render slower. I'd absolutely agree with removing icons from the discussions. -] 19:13, 15 August 2006 (UTC) | |||
: I'm all for a series of very nice notes explaining to the users why they are pure evil. I've had abouta 97% success rate in the past. It should also be noted that before I've tracked it to use of *horrer* automated voting scripts, which should also be killed with fire. - ]<span class="plainlinks"> </span> 08:37, 16 August 2006 (UTC) | |||
] - <SMALL>(image text-link by ] see history for reason)</SMALL> | |||
::I think really think that it would add a touch of class to AfD to add a few decorative pastel boxes that would improve debate by calling attention to the best and most valid points of the discussions. We used to have them. AfD really looks pallid and dull without them. Do I also need to add ] here? ] ] 13:27, 16 August 2006 (UTC) | |||
:: I agree, get rid of them, quickly. We are already having technical issues in AFD because we're transcluding too many pages (see ]) - why do we need to burn the 1MB of transclusion memory we have by wasting it on pretty icons? ]]<sup>(])</sup> 19:43, 16 August 2006 (UTC) | |||
Is there anything like a policy statement or guideline on this? I notice WikiCats has just added a section, top of this page, pointing to vote icons for use in these discussions. ] ] 02:24, 29 August 2006 (UTC) | |||
:If the icons are causing technical problems then their limited merits do not justify them being used. ] 02:34, 29 August 2006 (UTC) | |||
== A bot to seperate closed discussions== | |||
I've been following the discussion on the voodoo and seperate closed discussions thread. I'm wondering if a bot should handle this work instead. Thus alleviating anyone having to do it. I have someone willing to make the bot, and I'm willing to run it. If I can get a consensus here, I'll post it to ]. Any thoughts? ] 18:09, 16 August 2006 (UTC) | |||
:Do you mean tracking through the page after the afd templates are put on and adding noinclude tags around the discussion? It would have the problem of trying to detect the end of the admin's comments, but if they alway date stamped them it would be fairly straightforward and isn't a bad idea. Personally, I think my template is an easy solution (as it saves the admins work most of the time) but getting people to change to it will be a struggle because it requires a slight change in how things are done. ]] 19:40, 16 August 2006 (UTC) | |||
::Well, the idea I had in mind was for the bot to remove the closed AfD altogether (to a subpage), and leaving only a link, similar the one found here: ]. I'm not entirely sure how it would work, as I wouldnt be the one designing it. Although I can say that I dont think there would be much of an issue in tracking, the bot would look for the template top being used, possibly even if its subst'd. So anything under <nowiki>{{Afd top}}</nowiki> and above <nowiki>{{Afd bottom}}</nowiki> would be moved to the subpage. Any suggestions for improving the bot or concerns can be raised, and addressed here if needed. The builder is ], who has created ] for AfD's, and I believe has also helped work on ] and ]. Its my feeling that the bot would in fact be at its best. ] 19:57, 16 August 2006 (UTC) | |||
:::If the link on the log page says it is closed it only has to link to the discussion page, there is no need for another subpage (and in fact another subpage would be pointless). I think the information in ] is probably the bare minimum that should be left. That isn't supposed to be a subpage, it is supposed to show what the link would look like in the main log page (I probably should have surrounded it with some dummy open discussions to illustrate). ]] 20:13, 16 August 2006 (UTC) | |||
::::Yeah you're right. I forgot that the discussion is its own page. Then all the bot would need to do is provide the closed template. Which in my opinion, would require no new changes to closing by admin's and non admins. ] 20:23, 16 August 2006 (UTC) | |||
:::::I agree - I'll stamp on the other discussion ]] 20:30, 16 August 2006 (UTC) | |||
::::::Thanks for supporting the idea. I'm also looking for any objections from others before we begin working on the details of the bot, coding and what not. I'm still concerned about how often the bot should be run. I'm leaning toward every few hours, or possibly something like the Mediation Cabals bot is run. Its spots a change, and automatically adjusts. I'm just not sure if it would be better for the bot to run 24/7, and check all five current logs, so it can catch the close as soon as possible or not. The downfall of not letting it run 24/7 would be making it a semi-bot, and running it only at special peak times. And in a large stretch of time, many AfD's could be closed, as speedy delete, speedy keep, etc. This however wouldnt help out much, since approx. 15 AfD's will close in the first 6 hours, but there is really no way of knowing how many will be closed, or relisted elsewhere (to MfD, TfD, CfD, etc. ). ] 21:35, 16 August 2006 (UTC) | |||
:::::::But then again, I know nothing ''about'' bots, which is why someone else is going to be making it, and updating the code. ] 22:01, 16 August 2006 (UTC) | |||
::::::::I don't think it is necessary for it to constantly cycle checking for changes. The size of a new log page doesn't become a problem for several hours and an occasional pass to compact the closed AFDs should take most of the sting out of it. Running it something like every 4 hours would probably be fine. ]] 22:39, 16 August 2006 (UTC) | |||
::"if they alway date stamped them it would be fairly straightforward and isn't a bad idea" - this is getting above my head but I thought I'd better pull this out - sometimes admins post 'P.S.'s, so that there are two signed comments in the closing summary. I'm certain I've done so at least once. --]<sup>]</sup> 23:26, 16 August 2006 (UTC) | |||
::* I often come back and either expand my closing comments, or add additional information beneath. I also often note if something has gone to DRV or other similar events. - ]<span class="plainlinks"> </span> 06:21, 17 August 2006 (UTC) | |||
:::*I doubt this will be a problem - when I made my earlier comment I was thinking on simpler terms. The bot should only replace the included link in the log, not the actual afd file, so you will be able to treat the discussions exactly as you do now. It will have to go through the bot approval process anyway, so any problems should get caught there. ]] 15:46, 18 August 2006 (UTC) | |||
I confirm that SynergeticMaggot has been in contact with me. I will set forth the proposed paremeters for the bot in a few hours from this post. —— ] (]) 22:21, 16 August 2006 (UTC) | |||
:As of right now, our data shows that the bot should be run approx. every 12 hours. The bot will be located at ]. ] 01:39, 17 August 2006 (UTC) | |||
Whoa there, steady on fellows... perhaps we should engage a slightly wider audience first? - ]<span class="plainlinks"> </span> 06:21, 17 August 2006 (UTC) | |||
:Did you just get off a ranch partner? :) What did you have in mind? I figured AfD talk was the place to discuss this. ] 07:25, 17 August 2006 (UTC) | |||
:: This ''is'' the place to discuss it, but most people's watch lists are very busy, and the section header "a bot" does not exactly scream "Hey we're about to make a functional change to the way this works and then run a bot over the top to enforce it." I'd suggest a note at the adminstrator's noticeboard with a brief summary and a link to this thread. Greenhorn. - ]<span class="plainlinks"> </span> 07:37, 17 August 2006 (UTC) | |||
:::Suggestion noted. Before I run to AN, I would like to know what others think first, here. It wouldnt hurt to have a bot name and trial runs to show off (sandbox mind you). ] 07:41, 17 August 2006 (UTC) | |||
:::: For me it seems like much complication for very little gain. I do wp:afd/old all the time, and I don't have ''that'' much of a problem with the way it already works. But I am a luddite. - ]<span class="plainlinks"> </span> 07:57, 17 August 2006 (UTC) | |||
:::::Well thats the great thing about it being a bot, to the previous two talk headers to which this thread sparked from. You wouldnt have to change the way you close. The bot picks up the closed AfD and replaces it with a link to the discussion, thus alleviating long discussions and uneeded reading. ] 08:24, 17 August 2006 (UTC) | |||
::::::I did put a request on AN with reference to the previous discussion above, and made a note to look down here. But judging by the massive response, another one wouldn't hurt. ]] 09:22, 17 August 2006 (UTC) | |||
There was discussion on the other thread about the possibility of doing it with a bot before the template voodoo came about. Considering how frequenty AFDs get speedied on the day they're submitted, I'd think the bot would need to run fairly frequently, at least on the current day; maybe every hour or so. For previous days, maybe not so much. Although I do like the instant gratification affect of the templates, I'm not too worried about how it's done; if a bot did the updated frequently enough, that would be cool. -] 13:56, 17 August 2006 (UTC) | |||
:I haven't closed in a while, shame on me, but I found the js automation that hid closed discussions to be very useful. (I forget where it is from but it's the two functions hideafd() and showafd() in my ] along with loading code for when you are on an afd page) ...you still pay load time cost of course but the still open ones stand out nicely. So is this other solution necessary? js of course only works for those that use it. ++]: ]/] 16:20, 18 August 2006 (UTC) | |||
::As you say, it doesn't change loading speed and relies on you having the js installed which isn't possible for (or desired by) everybody. ]] 01:28, 20 August 2006 (UTC) | |||
:I've posted to AN per the request. I will admit that I know nothing about js. ] 01:35, 20 August 2006 (UTC) | |||
== ] == | |||
<s>All of the discussions on the afd log page aren't transcluded properly for some reason. As far as I can tell, it's just because the page is too large, since removing random entries would cause the rest of them to format correctly. The problem seems to have started somewhere between (when the amount of discussions on the page took a dive, even though the page itself didn't change). It probably doesn't belong here, so if you know of a better place to post this, pass it along, thanks. - ] 12:08, 17 August 2006 (UTC)</s> | |||
:It's back to normal now, for those who care. - ] 22:01, 17 August 2006 (UTC) | |||
==]== | |||
Does anyone recall if this article ever went through an AfD, perhaps under a different name? It was deleted April 14 as speedy non-notable and recreated May 26 this year. It was tagged today as a speedy but this time as reposted AfD article. I can't find the AfD and it appears to me there is some claim of notabilty that I believe stops it being a speedy. Thanks. ] ] 23:35, 17 August 2006 (UTC) | |||
:My best guess would be that it never went to afd and the person who says it did doesn't know that afd specifically means this process instead of speedy deletion (he has no edits in afds himself). People tag speedied entries with db-repost all the time which is likely here. - ] 07:53, 18 August 2006 (UTC) | |||
::Thanks. ] ] 09:53, 18 August 2006 (UTC) | |||
==]== | |||
This article was first posted for AfD on the 4th of August, it was then relisted on the 11th. Shouldn't it be closed by now? --] 09:46, 20 August 2006 (UTC) | |||
:AfD is subject to backlog every now and then. It should be closed soon. Also note that others in that days log arent closed yet, or else that days log would have been removed from the main page, and into the archives. Regards. ] 09:57, 20 August 2006 (UTC) | |||
== Link back to the log page in the template? == | |||
Sorry if this has been suggested/discussed before, but I'd like to suggest that a link to the appropriate log/day page appear on each individual AfD. The log pages transclude the AfDs themselves, so when you've edited an AfD to record your comment, the link at the top is ], from which you have to scoot down to the day links at the bottom. Am I missing some obvious navigation back to the log pages here? If not, it would be nice to have those AfD articles have a link back to the log page, so that for example on ] there would be a link that leads to ]. If it could lead back to the #section title, that would be even better; that would drop you right back in to the list where you were before you edited. Hope this makes sense. I don't yet understand templates well enough to go and experiment in my sandbox on this, but it seems to me that a change to afd2 is what would be needed. ] ] 00:25, 21 August 2006 (UTC) | |||
:I tend to agree. It does get rather annoying to have to do this, even when closing. ] 01:19, 21 August 2006 (UTC) | |||
::I don't think it is straightforward as the template on the individual AFD page would need to link back to the log page it was linked from, and, since nothing is transcluded from the log page into the individual AFD page, I don't know how you would know on which log page the AFD was listed (think about relistings for example). However it is late here, and my brain may be broken. ]] 01:26, 21 August 2006 (UTC) | |||
:::Could this be combined with the ] for header timestamps? If so, on creation the template could perhaps parse the date for the appropriate log page to link back to? I'm arguing by analogy from other coding languages here, so the argument may not go through for templates, but essentially I'm suggesting that if we pass in a date we can use it to create the link at article creation time. Again, I hope this makes sense. ] ] 01:33, 21 August 2006 (UTC) | |||
::::That's possible, but again brings up problems for relistings and AFDs where the main page is created at, say, 11.58pm and the article listed in the log at 12.02am the next day (both of which would go "back" to the wrong page). Personally, I use the back button or history in my browser to get round this, or launch the link to the article from the log in new window and work from that. ]] 09:36, 21 August 2006 (UTC) | |||
== Talk page notice template== | |||
Perhaps am overlooking it, but I am suggesting that we create and make available a notice template for inclusion in the talk page(s) of related article(s) to one being suggested for deletion and to make this part of the steps suggested. This is useful in AfD for sub-articles, when a large number of editors might want to be informed of an AfD, and easier than informing each one. However I do not mean it to be a substitute to notifying the page creator in his/her talk page. | |||
Something like this: | |||
<div style="padding:5px; background-color:#F1D1EE">A related or sub-article of this article, ], has been listed at ]. Please look there to see why this is, if you are interested in it not being deleted. Thank you. <!-- Template:Adw --></div> | |||
Comments?--] 09:17, 21 August 2006 (UTC) | |||
:Why? We have the AfD tag on the article page. ]|] 02:57, 22 August 2006 (UTC) | |||
:Yes, why would this be necessary? You're supposed to put the afd tag on every article included in a particular afd discussion, this would be redundant. - ] 08:28, 22 August 2006 (UTC) | |||
::I'm guessing that Cerejota meant to place a tag on ], for example, if ] was nominated for deletion. I've done this before in an informal way, to get a better consensus, but I don't think a template is necessary. -- '']']'' 22:41, 23 August 2006 (UTC) | |||
==]== | |||
What's everybody's opinion on having an automated process for voting on AfD? Seems to me to violate the "discussion" purpose of AfDs. ]|] 02:57, 22 August 2006 (UTC) | |||
:Personally, each time I see a discussion contribution via wikivoter I discount it. It may not be rubberstamping—there may have been long rumination before deciding which ''button to push''—but the appearance is that of rubberstamping. There is much brouhaha over not calling what we do at afd voting. I think we do no violence to the word ''voting'' by employing it, but I understand the reason for that semantic prohibition. If it is discussion we want, and not ''simple'' voting, this automated process is our worst enemy.--] 03:35, 22 August 2006 (UTC) | |||
::The only automation this program does is filling in some of the manual-labor type stuff. Editors still see the actual AfD page, the article page, ''plus'' some additional tools to help make an ''informed'' decision about the AfD. Like any Misplaced Pages tool, it's the responsibility of the user to use the program appropriately, according to Misplaced Pages policies and guidelines. --] ] 03:47, 22 August 2006 (UTC) | |||
:::I agree, it's really not automated, you actually have to manually type in a reason as to why you are making such a vote. I find that the tool saves a lot of time by making it easy to find AfD's based on the date the AfD was created. ] 03:54, 22 August 2006 (UTC) | |||
:I believe this is a total non-issue. If people leave a relevant comment, why should it matter whether they used this to make it or not? If they just leave a vote with no discussion, would it be any better if they hadn't used this thing? If someone thinks it's useful, let them use it. - ] 08:26, 22 August 2006 (UTC) | |||
==Deleting redirects to deleted articles== | |||
I was randomly meandering around today and ran across a redirect that pointed to an article that was deleted via AFD (]). Is it SOP to leave redirects after a successful AFD requiring the redirects to go through RFD or should these have been deleted? --] 21:25, 22 August 2006 (UTC) | |||
:*Busy admins may may miss them when closing AFD's. It really helps if, during an AFD, someone does a "what links here" and posts a note in the AFD that there are redirects. ] 21:27, 22 August 2006 (UTC) | |||
:*If you see a redirect like that around, just tag it with {{tl|db-r1}}. ] usually has a lot of them, it just happens sometimes. - ] 21:32, 22 August 2006 (UTC) | |||
::Thanks. Added tags to redirects.--] 21:45, 22 August 2006 (UTC) | |||
== Suggested changes to guidelines == | |||
Can I suggest that step one of the process is tweaked in the following way to help make the edit summaries more helpful? | |||
*Current text: "Please include the phrase "nominated for deletion, see ]" in the edit summary" | |||
*Suggested text: "Please include the phrase "nominated for deletion, see ]" in the edit summary, replacing PageName with the name of the page you are proposing for deletion" | |||
*Reason: Takes people directly to the discussion from the edit summary | |||
Also, step two could be improved with the following changes: | |||
(1): | |||
*Current text: "replacing ''PageName'' with the name of the page to be deleted" | |||
*Suggested text: "replacing ''PageName'' with the name of the page you are proposing for deletion" | |||
*Reason: current text assumes deletion will happen, the change removes this prejudicing statement. | |||
(2): | |||
*Current text: "Consider the Edit summary "First deletion reason" | |||
*Suggested text: "Please use an edit summary such as "Creating deletion discussion page for <nowiki>]</nowiki> and providing reason for deletion nomination", replacing ''PageName'' with the name of the page you are proposing for deletion" | |||
*Reason: current suggested edit summary too short and uninformative. | |||
Overall, standards of edit summaries should be high here, to allow people to trace the history of such discussions and see more easily what is happening when viewing edit summaries either in a page history, or in a User contributions list. ] 12:16, 23 August 2006 (UTC) | |||
: I agree. I think the proposed wording is better and more towards a NPOV. ] 22:36, 23 August 2006 (UTC) | |||
:: I don't know how many people even pay attention to edit summary guidelines, and my guess is not many. I don't know if adding mroe steps and making the process more complex will have any significant results. ]]<sup>(])</sup> 06:38, 24 August 2006 (UTC) | |||
:If you want to use those summaries go ahead. But these are only suggestions anyway, and people are free to use whatever summary they like, or to use none at all. There are no ''requirements'' and making them longer and more complicated will just make more people ignore them completely. -] - ] 13:43, 24 August 2006 (UTC) | |||
:May the Lord save us from helpful people! What Misplaced Pages needs is ''more'' process? ] (]) 14:04, 27 August 2006 (UTC) | |||
: Frankly, I'd ''prefer'' that they went to the main AFD page first and not directly to the deletion discussion. There are some very important instructions and very useful tips either directly on the page or on one of the linked pages. Newcomers (the only ones who would be really helped by such a link) are the ones who most need the chance to read those instructions. ] <small>]</small> 00:42, 28 August 2006 (UTC) | |||
== WP:AFD/OLD == | |||
Is there really a point of having ] and ]? The first is the one that is rarely up to date and gets included in the main afd page, the second is the bot-updated one at WP:AFD/OLD. Wouldn't it be better just to get rid of /old altogether and include /Old on the main page with the irrelevant parts tagged with noinclude? - ] 13:37, 26 August 2006 (UTC) | |||
== Cuddle puddles? == | |||
hey guys, the article ] was marked for deletion, but i don't see anything wrong with it- anyone think it should be deleted? ] 19:04, 26 August 2006 (UTC) | |||
== section == | |||
how do you propose that a specific section of an article be deleted?{{unsigned2|(20:16, August 28, 2006|Shawn88}} | |||
:]; if someone disagrees, they will replace the section. It is best to explain in your ] why you want to remove the section, and if it's established and well-known material, consider discussing it on the talk page first. What section of what page are you thinking about deleting? -- '']']'' 01:32, 29 August 2006 (UTC) |
Latest revision as of 04:46, 22 January 2025
Skip to table of contents |
This is the talk page for discussing improvements to the Articles for deletion page. |
|
view · edit Frequently asked questions Q1: I don't like this page's name. I want to rename it to Articles for discussion or something else. A1: Please see Misplaced Pages:Perennial proposals#Rename AFD. Note that all of the "for discussion" pages handle not only deletion, but also proposed mergers, proposed moves, and other similar processes. AFD is "for deletion" because the volume of discussion has made it necessary to sub-divide the work by the type of change. Q2: You mean I'm not supposed to use AFD to propose a merger or a page move? A2: Correct. Please use Misplaced Pages:Proposed mergers or Misplaced Pages:Requested moves for those kinds of proposals. Q3: How many articles get nominated at AfD? A3: Per the Oracle of Deletion, there were about 470,000 AfDs between 2005 (when the process was first created) and 2022. This comes out to about 26,000 per year (2,176 per month / 72 per day). In 2022, there were 20,008 AfDs (1,667 per month / 55 per day). Q4: How many articles get deleted? A4: Between 2005 and 2020, around 60% of AfDs were closed as "delete" or "speedy delete". This is about 270,000. More detailed statistics (including year-by-year graphs) can be found at Misplaced Pages:Oracle/All and Misplaced Pages:Misplaced Pages records#Deletion. Q5: Is the timeline strict, with exactly 168 hours and zero minutes allowed? Should I remove late comments? A5: No. We're trying to get the right outcome, not follow some ceremonial process. If the discussion hasn't been closed, it's okay for people to continue discussing it. Q6: How many people participate in AFD? A6: As of October 2023, of the 13.9 million registered editors who have ever made 1+ edit anywhere, about 162,000 of them (1 in 85 editors) have also made 1+ edit to an AFD page. Most of the participants are experienced editors, but newcomers and unregistered editors also participate. Most individual AFD pages get comments from just a few editors, but the numbers add up over time. |
This project page does not require a rating on Misplaced Pages's content assessment scale. It is of interest to the following WikiProjects: | ||||||||
|
This project page has been mentioned by multiple media organizations:
|
Archives |
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 31, 32, 33, 34, 35, 36, 37, 38, 39, 40 41, 42, 43, 44, 45, 46, 47, 48, 49, 50 51, 52, 53, 54, 55, 56, 57, 58, 59, 60 61, 62, 63, 64, 65, 66, 67, 68, 69, 70 71, 72, 73, 74, 75, 76, 77, 78 |
|
This page has archives. Sections older than 25 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
About deleted articles
There are three processes under which mainspace articles are deleted: 1) speedy deletion; 2) proposed deletion (prod) and 3) Articles for deletion (AfD). For more information, see WP:Why was my page deleted? To find out why the particular article you posted was deleted, go to the deletion log and type into the search field marked "title," the exact name of the article, mindful of the original capitalization, spelling and spacing. The deletion log entry will show when the article was deleted, by which administrator, and typically contain a deletion summary listing the reason for deletion. If you wish to contest this deletion, please contact the administrator first on their talk page and, depending on the circumstances, politely explain why you think the article should be restored, or why a copy should be provided to you so you can address the reason for deletion before reposting the article. If this is not fruitful, you have the option of listing the article at WP:Deletion review, but it will probably only be restored if the deletion was clearly improper.
List discussionsWP:Articles for deletion WP:Categories for discussion WP:Copyright problems WP:Deletion review WP:Miscellany for deletion WP:Redirects for discussion WP:Stub types for deletion WP:Templates for discussion WP:WikiProject Deletion sorting WT:Articles for deletion WT:Categories for discussion WT:Copyright problems WT:Deletion review WT:Miscellany for deletion WT:Redirects for discussion WT:Stub types for deletion WT:Templates for discussion WT:WikiProject Deletion sorting |
Tool XFDcloser
Is there a way or tool to check how many closures an editor has performed, particularly when the XfD closure has resulted in a 'keep' ? Jeraxmoira🐉 (talk) 05:18, 8 January 2025 (UTC)
- https://sowhy.toolforge.org/afdcloses.php? Extraordinary Writ (talk) 05:27, 8 January 2025 (UTC)
- Yes, thank you. Jeraxmoira🐉 (talk) 05:32, 8 January 2025 (UTC)
Requiring Google Scholar for BEFORE
BEFORE (D)(1) currently states The minimum search expected is a normal Google search, a Google Books search, a Google News search, and a Google News archive search; Google Scholar is suggested for academic subjects.
(links omitted) Given our relatively robust access to academic sourcing through the Misplaced Pages Library, and the number of recent AfDs I've seen that have completely missed obvious Google Scholar sources on fictional literature (e.g., Misplaced Pages:Articles for deletion/Spacing Guild (2nd nomination), Misplaced Pages:Articles for deletion/List of James Bond villains), I'd like to make Google Scholar expected, rather than "suggested for academic subjects". We have a lot of pop culture media and literature that are being addressed as "academic subjects" and I believe the current wording doesn't well serve the encyclopedia.
- 1) Is there a good reason to not add Google Scholar to the expected list for general topics?
- 1a) Could we wordsmith it so that obviously non-academic topics such as BLPs are excluded?
- 2) Is going from 4 to 5 expected searches too much effort? If so, would it be appropriate to swap out one of the other four?
I believe the encyclopedia suffers when things that are clearly notable are nominated for deletion, and I'd like to make sure our efforts here are the best balance of making the nominator do appropriate work to find and evaluate the most obvious sources before creating work for the community and administrators. Jclemens (talk) 00:11, 13 January 2025 (UTC)
- I'd support that. I think common-sense exceptions already apply (you don't need to check Google Books for a breaking-news story), but if that's a concern we could just stick an "in general" on the front. To compensate (or either way, honestly), we should get rid of the Google News Archive search, which has never worked properly and isn't really supported anymore. Extraordinary Writ (talk) 00:20, 13 January 2025 (UTC)
- I would oppose this, but only because access to the Misplaced Pages Library is contingent on time (one has to be active for six months if I am remembering correctly), and one has to apply for access (which may not have been done by all participants at AFD). There are enough access barriers in place that I don’t think this can be required.4meter4 (talk) 00:25, 13 January 2025 (UTC)
- One need not have access to the Misplaced Pages Library to use Google Scholar; it's just a great tool to get access if you want to see "does this scholarly article really cover this topic in depth?" for those who don't have access to a University library's online collections. So to clarify, the Google Scholar search would be expected, Misplaced Pages Library use would be recommended as it already is per (D)(2). Jclemens (talk) 00:39, 13 January 2025 (UTC)
- Oh, and to clarify: BEFORE is only about the nominator's pre-deletion expected work. Nothing about BEFORE creates any obligation on anyone other than an AfD nominator. Jclemens (talk) 00:46, 13 January 2025 (UTC)
- I think you are splitting hairs here. Simple facts: 1. Google scholar's materials are in most cases behind paywalls and are not viewable to most people. The assumption that people can still use it without the Misplaced Pages Library is false. 2. Those without a university library access are unlikely to be able to access the majority of materials. 3. The Misplaced Pages Library has spotty access to the works in google scholar with roughly a 1/3 of all materials remaining unavailable even with an account (more or less depending on the content area; many law and science journals for example tend to be not viewable even with a Misplaced Pages Library account ) 4. Users cannot qualify for the Misplaced Pages Library until 6 months after their user account creation and if they have meet the minimum editing participation requirements as required by that application. 5. AFD participation is open to all and those with a user account can make a nomination not long after account creation. 6. Imposing this rule would stop new people from having access to making AFD noms due to Misplaced Pages Library access rules and it make enrollment compulsory.
- Fundamentally, we can't put a rule in place that creates a barrier to free and open access to AFD nominations. Making Misplaced Pages Library enrollment compulsory (which is the effect of what you are proposing) to participate in the AFD process is morally wrong. It doesn't fly. We are an encyclopedia anyone can edit. That includes AFD. The spirit of that policy is an ethical core must for the project, and per that reason this is a hard no we can't do this from my point of view.4meter4 (talk) 08:36, 13 January 2025 (UTC)
- First, no one has suggested that actual access to materials must be gained. That's not what the current document says, and no proposal to change it has been advanced. Second, your objection would also be an objection to BEFORE as currently written--I'd really rather you provided a critique in the context of the change from current practice; you're treating this as if it's a new proposal rather than a tweaking of existing expectations. Third, your ethical argument fails as deletion is asymmetric--it's far easier to destroy content through a misapplication of deletion policy than it is to create new content--which is why 'deletion' and 'editing' are different concepts. Misplaced Pages never promises to be the encyclopedia from which anyone can delete articles. In fact, the majority of our editing tools, including content removal within an article, are arbitrarily reversible, which is why anyone can do them. Deletion, of course, is outside the scope, only being doable or reversible by administrators. Jclemens (talk) 09:04, 13 January 2025 (UTC)
- I would oppose this, but only because access to the Misplaced Pages Library is contingent on time (one has to be active for six months if I am remembering correctly), and one has to apply for access (which may not have been done by all participants at AFD). There are enough access barriers in place that I don’t think this can be required.4meter4 (talk) 00:25, 13 January 2025 (UTC)
- I have no issue deprecating or outright deleting the Google News Archive search. It's not linked on {{find sources}} and I haven't used it in so long I wasn't even aware it didn't work. Jclemens (talk) 00:42, 13 January 2025 (UTC)
- I've just gone ahead and removed Google News Archive; it didn't seem to have any defenders the last time I mentioned it either. Happy to discuss if anyone disagrees. Extraordinary Writ (talk) 09:11, 13 January 2025 (UTC)
- I would have preferred this been dealt with as one change, as folks seem to be disagreeing about things that area already part of the expectations. That is, I don't think people perceive that upgrading scholar and removing Google News Archive together make a net zero change in effort required of nominators. Jclemens (talk) 17:24, 13 January 2025 (UTC)
- I've just gone ahead and removed Google News Archive; it didn't seem to have any defenders the last time I mentioned it either. Happy to discuss if anyone disagrees. Extraordinary Writ (talk) 09:11, 13 January 2025 (UTC)
- The two examples you put forth call into question the necessity of doing so. For the Spacing Guild example, the first example appears to be a single paragraph, not the sort of in-depth coverage we expect; the Guild is not mentioned in either the abstract of the article or the first page of the article shown on the store page. The second doesn't look deeper. Meanwhile, in both deletion discussions you cite, there look to be enough non-Google Scholar-ly sources to render a Keep. WP:BEFORE is already a burden; before we increase its weight, I'd want to see not just that Scholar can point to sources on such topics, but that it can point to sources on such topics that would not have had enough sources through other means already required by BEFORE. -- Nat Gertler (talk) 01:10, 13 January 2025 (UTC)
- There are more examples; I picked two. Whether you agree that those are sufficient to demonstrate GNG being met by themselves misses the point--it is the nominator's job to find such obvious issues and either make a compelling case for non-retention (merging, etc.) despite the presence of that coverage or to abandon the idea of a nomination. As far as scholar vs. other choices, I'd actually argue that Scholar is probably more useful than a "vanilla" Google search, in that if we can identify multiple truly relevant hits in Google Scholar, the value of those hits is sufficiently higher than a random plain Google search hit that it is more efficient to evaluate Scholar sources first, rather than basic Google hits. Jclemens (talk) 02:31, 13 January 2025 (UTC)
- No, I don't think it misses the point if this added effort is just going to identify as keepable things that would be identified as keepable anyway. WP:CREEP is a problem here, and is my concern with this proposal. -- Nat Gertler (talk) 02:37, 13 January 2025 (UTC)
- The entire point of BEFORE is to identify as keepable things that would ideally be identified as keepable in an AfD discussion, but to put the workload on the nominator so AfD discussions aren't either 1) a waste of time, or 2) risking deleting something notable because no one is paying attention. This changes nothing about that, merely seeks to optimize the work that's already expected of nominators. Jclemens (talk) 05:23, 13 January 2025 (UTC)
- Yes, but if the only things doing this step is going to identify as keepable are things that should've been detected by the other existing steps of BEFORE, then it's just putting an unneeded additional step on the process. So that's the question I see before us. And if you say "I found it in these articles, so it was something that the nominator should've checked", that's an argument that can be made for checking everything that gets discovered during AfD. -- Nat Gertler (talk) 06:08, 13 January 2025 (UTC)
- Ah, I see--you're saying that if the nom had done the rest of BEFORE correctly, this wouldn't be an issue. I can't disagree with that, but I am very much trying to make sure processes are optimized before considering approaching this as a user conduct issue. I will take issue with the additional characterization: It's already listed as a suggested step, I'm just proposing we change it to be clear when we can reasonably expect it to be beneficial. I completely agree that we shouldn't be doing box checking, but rather intelligently searching out the most relevant couple of web search methodologies likely to generate usable sources. And, as noted above, I'm also suggesting we consider if this should be prioritized, should another expected search step (or more?) be deprecated to avoid making the pre-nomination burden unwieldy? How can we get the best outcome with the least required work on the nominator's part.
- Just as a side note, this whole section feels like teaching EMT class. We give students about 20 things to check in order in patient assessment, and once they've demonstrated they can do them in a regimented fashion, we turn them loose to parallelize those tasks (e.g. checking skin warmth and a radial pulse simultaneously). BEFORE should ideally be that sort of thing that transforms from a formal checklist into a natural methodology that skilled nominators can breeze through. Jclemens (talk) 08:00, 13 January 2025 (UTC)
- Yes, but if the only things doing this step is going to identify as keepable are things that should've been detected by the other existing steps of BEFORE, then it's just putting an unneeded additional step on the process. So that's the question I see before us. And if you say "I found it in these articles, so it was something that the nominator should've checked", that's an argument that can be made for checking everything that gets discovered during AfD. -- Nat Gertler (talk) 06:08, 13 January 2025 (UTC)
- The entire point of BEFORE is to identify as keepable things that would ideally be identified as keepable in an AfD discussion, but to put the workload on the nominator so AfD discussions aren't either 1) a waste of time, or 2) risking deleting something notable because no one is paying attention. This changes nothing about that, merely seeks to optimize the work that's already expected of nominators. Jclemens (talk) 05:23, 13 January 2025 (UTC)
- No, I don't think it misses the point if this added effort is just going to identify as keepable things that would be identified as keepable anyway. WP:CREEP is a problem here, and is my concern with this proposal. -- Nat Gertler (talk) 02:37, 13 January 2025 (UTC)
- There are more examples; I picked two. Whether you agree that those are sufficient to demonstrate GNG being met by themselves misses the point--it is the nominator's job to find such obvious issues and either make a compelling case for non-retention (merging, etc.) despite the presence of that coverage or to abandon the idea of a nomination. As far as scholar vs. other choices, I'd actually argue that Scholar is probably more useful than a "vanilla" Google search, in that if we can identify multiple truly relevant hits in Google Scholar, the value of those hits is sufficiently higher than a random plain Google search hit that it is more efficient to evaluate Scholar sources first, rather than basic Google hits. Jclemens (talk) 02:31, 13 January 2025 (UTC)
- Oppose I am the sort of elderly nerd that read Dune well over a half a century ago back when SciFi seemed "very important" to me, and I will not bother to mention all the other portentious novels I read back then because there were just too many. But the notion that we need to force AfD nominators to use Google Scholar in their BEFORE search for sources about pop culture topics comes off like a Saturday Night Live skit to me. If another nerd wants to use Google Scholar to find sources to save an article, then bravo! But let's not force other editors to be nerds against their will. Cullen328 (talk) 08:57, 13 January 2025 (UTC)
- To clarify: You're fine with Google, Google News, Google Books, and Google News Archive being required as it stands now? Jclemens (talk) 09:05, 13 January 2025 (UTC)
- No, I am not fine with that, Jclemons. Sadly, Google News Archive has been worthless for years, so getting around to removing it makes sense. If someone wants to use Microsoft Bing instead of Google, why should we object? I am fine with suggesting tools to editors but not fine with forcing them to use tools. Cullen328 (talk) 19:00, 13 January 2025 (UTC)
- So, the status quo requires specific tool use. How would you prefer we improve it? I think you make a great point about general purpose search engines--we should not be requiring a specific for-profit company's tools be used for a free as in freedom project. Is there a Bing equivalent to Google Books, Google News, and/or Google Scholar? Jclemens (talk) 20:19, 13 January 2025 (UTC)
- Well, then there is something wrong with the status quo. I am not a regular Bing user so cannot comment on their range of offerings. I use many Google products including several for running my small business unrelated to Misplaced Pages. I use them because I freely choose to, not because someone forces me to. Cullen328 (talk) 03:26, 14 January 2025 (UTC)
- Again, how do you propose we improve on the status quo? Would it be appropriate to change
normal Google search
toa robust general-purpose search engine search, such as Google or Bing
? Jclemens (talk) 06:10, 14 January 2025 (UTC)
- Again, how do you propose we improve on the status quo? Would it be appropriate to change
- Well, then there is something wrong with the status quo. I am not a regular Bing user so cannot comment on their range of offerings. I use many Google products including several for running my small business unrelated to Misplaced Pages. I use them because I freely choose to, not because someone forces me to. Cullen328 (talk) 03:26, 14 January 2025 (UTC)
- So, the status quo requires specific tool use. How would you prefer we improve it? I think you make a great point about general purpose search engines--we should not be requiring a specific for-profit company's tools be used for a free as in freedom project. Is there a Bing equivalent to Google Books, Google News, and/or Google Scholar? Jclemens (talk) 20:19, 13 January 2025 (UTC)
- No, I am not fine with that, Jclemons. Sadly, Google News Archive has been worthless for years, so getting around to removing it makes sense. If someone wants to use Microsoft Bing instead of Google, why should we object? I am fine with suggesting tools to editors but not fine with forcing them to use tools. Cullen328 (talk) 19:00, 13 January 2025 (UTC)
- To clarify: You're fine with Google, Google News, Google Books, and Google News Archive being required as it stands now? Jclemens (talk) 09:05, 13 January 2025 (UTC)
- Not against adding Scholar but a caution that it's listing's often include thesises and other non peer reviewed grad school output, more commonly seen for non traditional academic topics, which themselves aren't reliable. Editors should be checking for sources in non predatory journals with Scholar searches. — Masem (t) 17:32, 13 January 2025 (UTC)
- This is absolutely a balancing act. Scholar, just like the other search engines, is a great way of identifying things to be further investigated. The main use in a BEFORE search is the negative result: If a topic isn't covered at all, no further work is needed and the AfD proceeds. If there are results, then things get a bit more nuanced about what should happen next, as you can see from the rest of the discussion above. Jclemens (talk) 20:21, 13 January 2025 (UTC)
Process
I have marked Mr. Beat for deletion and kindly request that someone complete the process for me. Thank you very much. 2A02:C7C:2DCE:1F00:4D29:6661:1D4E:6058 (talk) 19:41, 13 January 2025 (UTC)
Misplaced Pages:Articles for deletion/Meyer Schleifer
I would appreciate some regular AFD reviewers commenting on this page. There's been lots of activity from potential WP:SPA accounts, and it would be good to have some clearly non-partisan people participating. All opinions are welcome.4meter4 (talk) 01:30, 14 January 2025 (UTC)
Semi-protected edit request on 14 January 2025
Please either correct completely or else delete the article on Govinda (actor) Sir immediately as it is libellous and false. Based on communication from Misplaced Pages Foundation Legal Counsel office we had posted an edit request on article talk page. It is more than 36 hours, actually 72 hours and the libels have not been removed and our communication completely ignored. Hence you are once again requested to completely remove all defamation and libels from article page of Govinda Sir. NB: As per laws of India, Misplaced Pages is a PUBLISHER irrespective of what other persons may have published elsewhere.
I am unable to post to this page as I am a new user. अधिवक्ता संतोष (talk) 04:51, 14 January 2025 (UTC)
- अधिवक्ता संतोष, there is no chance that an article about a very well known actor and politician such as Govinda (actor) will be deleted. That is simply not going to happen. As for your request at Talk: Govinda (actor), it is far too vague. You need to explain specifically why the content that you want removed violates Misplaced Pages's Policies and guidelines. Cullen328 (talk) 05:04, 14 January 2025 (UTC)
- Kindly note that we are not concerned with Misplaced Pages Policies and Guidelines as they have no legal force India and are not compliant with requirements of India's internet regulations. As per the advice of your legal Counsel We have approached the editor community to voluntarily correct all self evident libels in Govinda Sir's article which have been inserted by his political opponents using anonymous user IDs and IP addresses. Also note that defamation in India is a criminal offence unlike USA and definition of defamation in India is also quite different from USA's. Since this website is allowing anonymous and unverified persons to defame Govinda Sir by publishing he is a failed actor, you may either correct / delete the article within 36 hours or else surrender intermediary status in India. अधिवक्ता संतोष (talk) 05:33, 14 January 2025 (UTC)
- I strongly recommend that you look at WP:NOLEGALTHREATS. DonIago (talk) 07:08, 14 January 2025 (UTC)
- @अधिवक्ता संतोष - to be clear, the policy on defamation is to delete libel as soon as it is identified. However we need you to tell us what specific statements in the article you believe are libelous and should be removed. The statement about "failed acting career" has already been removed, but what else would you like to see delete? The people you have already engaged with are trying to help, but they cannot to read your heart and mind so we need you to tell us what you think should be removed. If you are not satisfied with the assistance of these volunteers, you're welcome to email info-en-qwikipedia.org who can directly assist you further. TiggerJay (talk) 07:11, 14 January 2025 (UTC)
- Thanks for your assistance. What you are proposing is a chicken-egg pretzel logic situation. We have availed the info-en-qwikipedia.org and our email was forwarded to Wikimedia Legal Counsel who suggested we make an edit request on the talk page. Only when this was not acted upon speedily did we post to this forum. The policies of this website, being grounded in USA laws, do not apply in India where defamation is primarily a criminal offence not a civil action. A person from India who is being defamed cannot be compelled to acquiesce in surrendering their legal protections afforded under India's laws to sue/prosecute by polices such as WP:NOLEGALTHREATS. In which case, it would be far better that this website does not publish articles on Indian data subjects, as such policies and also those like WP:VERIFIABILITY and WP:RELIABLESOURCES do not apply under India's new data protection regime which incidentally WIKIPEDIA is unhappy with. In the alternative, Wikimedia can appoint a legally qualified grievance officer so that aggrieved persons or their lawyers do not have to publicly deal with unpaid volunteers who are mostly ill-equipped to handle what they perceive to be legal "threats" conveyed in the form of due legal notice. अधिवक्ता संतोष (talk) 07:59, 14 January 2025 (UTC)
- @अधिवक्ता संतोष, do note that we are unpaid volunteers, and that when we see calls to legal action, we usually block people as we are unable to deal with these complaints and any party who would wish to file suit would know to file with the right body, the Wikimedia Foundation. Given the legitimacy of your complaint, nobody has blocked you and the defamatory content has been resolved. If there ever end up being grounds for legal recourse, again I will stipulate that is the business of the Wikimedia Foundation, not for a bunch of unpaid internet users—the internet users can only modify pages, not deal with legal paperwork. However, in most instances, as the people you emailed told you to do, simply asking for removal of the damning, untrue content on a page works perfectly fine. Which it did here. Because unpaid internet users can remove content on pages. It's really the question of invoking the right tool for the job. Thankfully, as you have performed the steps that you have performed, the defamatory content is resolved, which resolves the dispute before any legal action needed to be taken. Have a nice day. BarntToust 13:05, 14 January 2025 (UTC)
- I would posit that any further push by this user for additional, unspecified actions, while continuing to spout legalese, should be considered in violation of WP:NOLEGALTHREATS. - UtherSRG (talk) 13:36, 14 January 2025 (UTC)
- The user is now blocked for legal threats. They absolutely had a legitimate grievance, and may have others, but they are going about it the wrong way. 331dot (talk) 12:03, 15 January 2025 (UTC)
- I would posit that any further push by this user for additional, unspecified actions, while continuing to spout legalese, should be considered in violation of WP:NOLEGALTHREATS. - UtherSRG (talk) 13:36, 14 January 2025 (UTC)
- @अधिवक्ता संतोष, do note that we are unpaid volunteers, and that when we see calls to legal action, we usually block people as we are unable to deal with these complaints and any party who would wish to file suit would know to file with the right body, the Wikimedia Foundation. Given the legitimacy of your complaint, nobody has blocked you and the defamatory content has been resolved. If there ever end up being grounds for legal recourse, again I will stipulate that is the business of the Wikimedia Foundation, not for a bunch of unpaid internet users—the internet users can only modify pages, not deal with legal paperwork. However, in most instances, as the people you emailed told you to do, simply asking for removal of the damning, untrue content on a page works perfectly fine. Which it did here. Because unpaid internet users can remove content on pages. It's really the question of invoking the right tool for the job. Thankfully, as you have performed the steps that you have performed, the defamatory content is resolved, which resolves the dispute before any legal action needed to be taken. Have a nice day. BarntToust 13:05, 14 January 2025 (UTC)
- Thanks for your assistance. What you are proposing is a chicken-egg pretzel logic situation. We have availed the info-en-qwikipedia.org and our email was forwarded to Wikimedia Legal Counsel who suggested we make an edit request on the talk page. Only when this was not acted upon speedily did we post to this forum. The policies of this website, being grounded in USA laws, do not apply in India where defamation is primarily a criminal offence not a civil action. A person from India who is being defamed cannot be compelled to acquiesce in surrendering their legal protections afforded under India's laws to sue/prosecute by polices such as WP:NOLEGALTHREATS. In which case, it would be far better that this website does not publish articles on Indian data subjects, as such policies and also those like WP:VERIFIABILITY and WP:RELIABLESOURCES do not apply under India's new data protection regime which incidentally WIKIPEDIA is unhappy with. In the alternative, Wikimedia can appoint a legally qualified grievance officer so that aggrieved persons or their lawyers do not have to publicly deal with unpaid volunteers who are mostly ill-equipped to handle what they perceive to be legal "threats" conveyed in the form of due legal notice. अधिवक्ता संतोष (talk) 07:59, 14 January 2025 (UTC)
- Kindly note that we are not concerned with Misplaced Pages Policies and Guidelines as they have no legal force India and are not compliant with requirements of India's internet regulations. As per the advice of your legal Counsel We have approached the editor community to voluntarily correct all self evident libels in Govinda Sir's article which have been inserted by his political opponents using anonymous user IDs and IP addresses. Also note that defamation in India is a criminal offence unlike USA and definition of defamation in India is also quite different from USA's. Since this website is allowing anonymous and unverified persons to defame Govinda Sir by publishing he is a failed actor, you may either correct / delete the article within 36 hours or else surrender intermediary status in India. अधिवक्ता संतोष (talk) 05:33, 14 January 2025 (UTC)
Repeating AFDs and prior consensus
When reviewing new articles, I focus on company topics which were previously deleted at AFD as non-notable. Does the new article and/or available references indicate that the topic is now notable? If not, a new AFD is needed.
Because of the low participation at AFD these days, these then rattle round the relist cycle. The soft-delete option is unavailable to reviewing Admins, precisely because of the previous AFD deletion. This seems a somewhat perverse position - that an article can't be deleted because of the previous consensus to delete!
So to my suggestion... If a previous AFD decided on deletion (except on TNT grounds), then any subsequent AFD which has not attracted a "keep" opinion can be closed as deletion after 7 days, in line with prior consensus.
Views? AllyD (talk) 08:46, 17 January 2025 (UTC)
- Why should a discussion be closed as delete if everyone !votes "merge"? Thincat (talk) 10:03, 17 January 2025 (UTC)
- "an article can't be deleted because of the previous consensus to delete" - Well, soft deletion works by pretending like the AfD is an expired, uncontested PROD; recreating the article is, in effect, contesting the PROD, so it is by design that soft deletion is not allowed a second time. However, I am partially sympathetic to your point, and would like to distinguish between two different situations:
- The article was soft deleted at AfD the first time. In that case, the article never gained consensus for deletion, so a recreation should not be eligible for soft deletion.
- The article was hard deleted at AfD the first time. In that case, it might be eligible for speedy deletion under G4, but that could be controversial, and edge cases should be brought to AfD. For this situation, I think soft deletion could make sense, but as a theoretical framework we should not be treating it as an expired PROD, but rather requiring an affirmative consensus to overturn a previous consensus to delete. Currently, there is no consensual process to overturn an AfD that resulted in deletion on substance, as opposed to on procedure (which would be DRV), with the only option being to try recreating an article and see if somebody nominates it for G4 or AfD, making it a very capricious process.
- King of ♥ ♦ ♣ ♠ 17:50, 17 January 2025 (UTC)
- What if the original soft-delete was of an article that was about a different topic with the same name?
- No, personally I cannot see why recreations should not be treated as new articles. PROD/soft delete should not be avoidable on mere technicalities - someone should have to act to avoid them. FOARP (talk) 12:11, 20 January 2025 (UTC)
- This proposal makes sense as long as you adjust
which has not attracted a "keep" opinion
towhich has not attracted a "keep" or "merge" opinion
. TarnishedPath 23:46, 18 January 2025 (UTC)- Or a "redirect" for that matter! Really, this is about the "empty room" discussions: "<AFD rationale>,(Project listings),(silence),<relist>..." where a previous AFD decided on deletion (meaning after actual discussion, not soft-deletion). Perhaps I should have said "...which has not attracted
a "keep" opinionsubstantial response can be closed as deletion after 7 days...". AllyD (talk) 15:20, 19 January 2025 (UTC)
- Or a "redirect" for that matter! Really, this is about the "empty room" discussions: "<AFD rationale>,(Project listings),(silence),<relist>..." where a previous AFD decided on deletion (meaning after actual discussion, not soft-deletion). Perhaps I should have said "...which has not attracted
merge proposals
I feel like lately there have been AFDs that are actually merge proposals showing up pretty regularly. Policy would seem to indicate that the administrative reaction to this would be to speedy keep if we catch them before anyone has voted to delete and/or all comments agree with a merge. I just found myself closing one as "merge" as it was the result, but at the same time not what AFD is for. I guess I'm asking if others agree that speedy keep is the correct close, and can be done at any time if there are no conflicting comments to delete or whatever? Beeblebrox 22:47, 21 January 2025 (UTC)
- Unless the notability of the article that's suggested to be merged is so obvious that it shouldn't be at AfD, I don't think we should necessarily be discouraging this. SportingFlyer T·C 23:02, 21 January 2025 (UTC)
- Should be totally discouraged. Deletion inclined editors will delete needlessly. Randy Kryn (talk) 04:31, 22 January 2025 (UTC)
- Until and unless WP:PEREN#Rename AFD is implemented, yes, pure merge proposals do not articulate a reason for deletion and should be speedily kept and kicked back to the talk page. Jclemens (talk) 04:45, 22 January 2025 (UTC)