Wikipedia:Bots/Requests for approval/TheSandBot 11
- The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at Wikipedia:Bots/Noticeboard. The result of the discussion was Speedily Approved.
Operator: TheSandDoctor (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 03:39, Sunday, August 6, 2023 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available: analytics, editing code
Function overview: Categorize the existing backlog into subcategories based on the month/year timestamp that entries were reported. This will allow for easier tackling and metrics.
Links to relevant discussions (where appropriate): User talk:Anomie/Archives/2023#Anomie bot work at CAT:UAA; this task is a relative of Wikipedia:Bots/Requests for approval/TheSandBot 6
Edit period(s): One-time run, potential future need on smaller basis depending on if any slip through the cracks in future
Estimated number of pages affected: Approximately 1,955
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): Yes
Function details: Categorize the existing backlog into subcategories based on the month/year timestamp that entries were reported. This will allow for easier tackling and metrics. Bot works off of a slight variant of this query by @Anomie: to gather this information and replaces the existing category (Category:Wikipedia usernames with possible policy issues) with Category:Wikipedia usernames with possible policy issues from month year (where "month" and "year" are the filing month/year. For example, August 2023).
The code to update the templates was trialed in this sandbox by Anomie (I have since confirmed the template update from the sandbox works and implemented the change) and was spurred on by the automatic creation of Category:Wikipedia usernames with possible policy issues from August 2023. The numbers of pages and how this would shake out is as follows, but keep in mind that CAT:UAA is fairly active in terms of getting new numbers so the August count will undoubtedly change. To my knowledge, I am the primary admin who uses CAT:UAA and this template change and task would help me manage it easier.
Month/year breakdown
|
---|
September 2021: 1 occurrences |
Discussion
[edit]Sorry to be "that guy", but... what backlog? What's the issue? Primefac (talk) 15:44, 6 August 2023 (UTC)[reply]
- @Primefac: CAT:UAA is classed as an {{admin backlog}} (has been since its creation 11 years ago) and contains usernames that further review has been requested on by the very nature of tagging the accounts. Given its size, it makes sense to start splitting it up for easier handling to address the oldest first and so on. TheSandDoctor Talk 16:34, 6 August 2023 (UTC); clarified 17:21, 6 August 2023 (UTC)[reply]
- However, given that I have already generated a list of what would go where and have the code for that and can generate it at will, I guess I could review off of that and withdraw this request if desired. It just seemed more convenient to have a listing on-wiki as then it isn't just something I have & I am not the single point of failure, so to speak. TheSandDoctor Talk 16:50, 6 August 2023 (UTC)[reply]
- I don't think we need to put this on hold (yet), but I have some thoughts. You say that there has been a backlog pretty much since the category was created. Has the backlog decreased at any point? I ask because it's a question of outcome - if people are not hitting the backlog because "it's too big" or "it would be nice to work sequentially" or something along those lines, then yes, recategorisation by splitting it into dates would make sense.
- However, if the reason the backlog is not going down is because no one is looking at that category, it doesn't really matter if it's split into smaller pieces.
- In other words, it might be worth having a more general discussion about this category (or pointing to an existing one) that indicates that this category is a) useful, and b) could use some additional sorting to help out the cleanup effort. Otherwise, we might as well just get rid of UAA altogether and save everyone the hassle. Primefac (talk) 07:39, 8 August 2023 (UTC)[reply]
- @Primefac: I would argue that the category most definitely should exist because UPOL violations never expire and are still UPOL violations and per the policy a solid chunk should be blocked "immediately" (policy's wording, not mine) when discovered; deleting it would also mostly nullify the point of any username notice templates (just identifying the collateral). Folks should be able to tag them for review (though I would argue a good chunk of them should've ended up at WP:UAA instead).
- I did not mean that the category has permanently been in backlog, merely that it was identified with {{admin backlog}} as being a queue administrators should pay attention to since its inception. I can only speak since 2020 but it has substantially decreased in size due to my efforts and I have been regularly working on it (with TSB 6) since 2020. I've reviewed and cleared out thousands at this point (but wish another admin would come by and assist). Based on TSB 6, there were over 4000 listed in 2020 and the oldest reports in it right now are late 2021, meaning that those were all dealt with...mostly by me (and my bot TSB), alone. If there was an "adopt a category" sticker, I would probably have it for CAT:UAA. Perhaps we should raise the awareness of the category as a note on WP:UAA? The trouble, I think, is that a lot of admins don't actually know it exists (and also needs review) and it is a category that really can only be worked on by administrators. TheSandDoctor Talk 17:02, 8 August 2023 (UTC)[reply]
- Well, that answers that then. I guess my next thought is to see whether subcategorisation is something admins might find useful. Discussion at WP:AN maybe? I'm genuinely not doing this to be an arse about it, just seems from your description that "dating" the category calls won't really change much (but I am more than happy to be wrong). Hell, if you (as the primary cleaner-of-this-cat) think that this subcategorisation will be helpful, I suppose that's good enough for me. Primefac (talk) 18:59, 8 August 2023 (UTC)[reply]
- Just in case you missed the above - are you saying that this will help you in your efforts to clear out the categories? Primefac (talk) 11:45, 24 August 2023 (UTC)[reply]
- I'm sorry for the delay, been a busy month. Yes, I am saying that @Primefac:. TheSandDoctor Talk 00:55, 30 August 2023 (UTC)[reply]
- Speedily Approved. Proven operator, sandboxed and tested code. Primefac (talk) 08:38, 30 August 2023 (UTC)[reply]
- I'm sorry for the delay, been a busy month. Yes, I am saying that @Primefac:. TheSandDoctor Talk 00:55, 30 August 2023 (UTC)[reply]
- Just in case you missed the above - are you saying that this will help you in your efforts to clear out the categories? Primefac (talk) 11:45, 24 August 2023 (UTC)[reply]
- Well, that answers that then. I guess my next thought is to see whether subcategorisation is something admins might find useful. Discussion at WP:AN maybe? I'm genuinely not doing this to be an arse about it, just seems from your description that "dating" the category calls won't really change much (but I am more than happy to be wrong). Hell, if you (as the primary cleaner-of-this-cat) think that this subcategorisation will be helpful, I suppose that's good enough for me. Primefac (talk) 18:59, 8 August 2023 (UTC)[reply]
- However, given that I have already generated a list of what would go where and have the code for that and can generate it at will, I guess I could review off of that and withdraw this request if desired. It just seemed more convenient to have a listing on-wiki as then it isn't just something I have & I am not the single point of failure, so to speak. TheSandDoctor Talk 16:50, 6 August 2023 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at Wikipedia:Bots/Noticeboard.