Operator: Anomie ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 22:49, Sunday, January 28, 2024 ( UTC)
Function overview: Remove direct use of parent monthly categories when a corresponding maintenance template already exists on the page.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Perl
Source code available: User:AnomieBOT/source/tasks/TagDater.pm
Links to relevant discussions (where appropriate): None
Edit period(s): Continuous
Estimated number of pages affected: Two currently. In the future it depends on how many more get added.
Namespace(s): Articles
Exclusion compliant (Yes/No): Yes
Function details: This is an extension to AnomieBOT's existing TagDater task. Previous BRFAs: 49, 55, 57, 72.
AnomieBOT logs pages that it finds in the parent monthly categories where it can't find a template to date, and I periodically go through these to clean them up. One common situation the bot can't handle is when someone puts a category like Category:Articles lacking sources directly on the article, usually either when creating via ContentTranslation or by misguided use of HotCat.
It seems safe for the bot to automatically remove these when a corresponding maintenance template (e.g. {{ Unreferenced}} for Category:Articles lacking sources) also exists on the page. If no maintenance template on the page would add the category, the bot will leave it for a human (to decide whether a template is really needed and which one specifically to use).
Examples:
The bot currently detects "a corresponding maintenance template" by checking for templates from WP:AWB/DT already on the page that, when called with no parameters, would generate the category in question.
The edit summary used for these edits would look something like " Category:Articles lacking sources should not be used directly. The template {{Unreferenced}} already on the page already handles the categorization correctly. ( added by User:1keyhole)". Anomie ⚔ 22:49, 28 January 2024 (UTC) reply
Operator: Anomie ( talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 22:49, Sunday, January 28, 2024 ( UTC)
Function overview: Remove direct use of parent monthly categories when a corresponding maintenance template already exists on the page.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Perl
Source code available: User:AnomieBOT/source/tasks/TagDater.pm
Links to relevant discussions (where appropriate): None
Edit period(s): Continuous
Estimated number of pages affected: Two currently. In the future it depends on how many more get added.
Namespace(s): Articles
Exclusion compliant (Yes/No): Yes
Function details: This is an extension to AnomieBOT's existing TagDater task. Previous BRFAs: 49, 55, 57, 72.
AnomieBOT logs pages that it finds in the parent monthly categories where it can't find a template to date, and I periodically go through these to clean them up. One common situation the bot can't handle is when someone puts a category like Category:Articles lacking sources directly on the article, usually either when creating via ContentTranslation or by misguided use of HotCat.
It seems safe for the bot to automatically remove these when a corresponding maintenance template (e.g. {{ Unreferenced}} for Category:Articles lacking sources) also exists on the page. If no maintenance template on the page would add the category, the bot will leave it for a human (to decide whether a template is really needed and which one specifically to use).
Examples:
The bot currently detects "a corresponding maintenance template" by checking for templates from WP:AWB/DT already on the page that, when called with no parameters, would generate the category in question.
The edit summary used for these edits would look something like " Category:Articles lacking sources should not be used directly. The template {{Unreferenced}} already on the page already handles the categorization correctly. ( added by User:1keyhole)". Anomie ⚔ 22:49, 28 January 2024 (UTC) reply