Firstly, AfD is not the right forum for MERGE or REDIRECT discussion. Let me also remind that it's WP:NOTAVOTE.
Secondly, the over a dozen references within the article itself assert notability while fulfilling and meeting the WP:GEOSCOPE, WP:DIVERSE and WP:NCRIME criteria of WP:NEVENT which reads:
"Coverage should be in multiple reliable sources with national or global scope."
Weak endorseRestore/allow recreation First, AfDs frequently result in outcomes that are short of deletion, such as merges or redirects. Second, I agree with you on the WP:GEOBIAS. However, I'm not voting to overturn for two reasons: first, consensus was generally against keeping by a 2:1 margin, and second, it's difficult to distinguish this from an event which doesn't qualify for its own page, because WP:LASTING was not clearly met. I don't think it's that far away from a keep, though, and it can be merged into the target article and spun off again if additional coverage is found. SportingFlyerT·C00:04, 9 November 2024 (UTC)[reply]
Endorse. AfD a poor forum for a merge discussion, but is not the wrong forum. AfD is the right forum on whether to turn a page into a redirect. Sources can assert notability but that notability, i.e. real-world notability, is not wiki-notability. There was a rough consensus to stop the article from being live, redirecting was a valid WP:ATD, and the closer noted that the content can be merged from history.—Alalch E.01:11, 9 November 2024 (UTC)[reply]
As far as the consensus is concerned, there were 4 Keep, 2 Merge and 2 Delete !votes (excluding the nominator) before @Liz: decided to re-list the AfD discussion for the second time on 28 October. So, there was a rough consensus to Keep the article at that point in time. — Mister Banker (talk) 06:36, 9 November 2024 (UTC)[reply]
Youre actually admitting there was not consensus to keep at that point. This is based on numbers and not looking into the reasoning (since AFD is not a vote). Four keep !votes and five delete/WP:ATD !votes (including the nom) is not consensus. A relist at that point was a reasonable choice. FrankAnchor13:52, 9 November 2024 (UTC)[reply]
Endorse. It was a poor nomination, people should not go to AfD with a vague merge proposal. And doing so is usually a train wreck. However, in this case the discussion recovered and I agree that it is a consensus to redirect. AfD is not not good for merges, but is perfectly good with redirection. Elements in the discussion were strong on the points that the article should not continue, and that there is no great ongoing need to merge anything, as the content is already at the target. SmokeyJoe (talk) 10:05, 9 November 2024 (UTC)[reply]
Endorse. AfD is the perfect place for redirect discussions. For poorly sourced articles that have a natural redirect target, a redirect is the best outcome. Once you discard the VAGUEWAVE !votes in this AfD, the redirect result reflects consensus well. Owen×☎11:36, 9 November 2024 (UTC)[reply]
I would gladly do so if this were AfD. But this is DRV, where we are asked to review consensus among AfD participants, not to rerun the AfD. Owen×☎07:31, 10 November 2024 (UTC)[reply]
Endorse. Many of the keep !votes were weak while the redirect/merge !votes were more based in policy. Consensus to not keep appeared to form after the final relist. FrankAnchor15:46, 9 November 2024 (UTC)[reply]
Endorse - Nominator's statement Where does it say that WP:LASTING is a mandatory criteria that must be met[1] makes it clear to me that they do not understand that routine events like this do not have or get enduring coverage, AFD is often the venue where the consensus for merging/redirection emerges so the closer was correct in redirecting this article. - Ratnahastin (talk) 06:09, 11 November 2024 (UTC)[reply]
Speedy Endorse - Appellant has been blocked as a sockpuppet, but ...
