Commons:Bots/Requests/Hazard-Bot 7

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Hazard-Bot (talk · contribs)

Operator: Hazard-SJ (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Category replacements

Automatic or manually assisted: Automatically

Edit type (e.g. Continuous, daily, one time run): Periodically

Maximum edit rate (eg edits per minute):

Bot flag requested: (Y/N): No

Programming language(s): Python

There are cases when more help is wanted for category replacements. Now is an example. User:CommonsDelinker/commands has a backlog with, I believe, no bots working on it at the moment, so I'd like to be able to help out in such cases.  Hazard-SJ  ✈  01:36, 19 March 2013 (UTC)[reply]

Discussion

  • For the record, SieBot is, again, down, so I've gone ahead and coded the bot. I've ran a 16-edit trial with it here, doing four requests in all. Of course, as I already mentioned, the bot isn't able to edit the queue page, since the current one is fully protected. Also, for now, I'm just marking the old category as a category redirect to the new one.  Hazard-SJ  ✈  03:56, 21 April 2013 (UTC)[reply]
  • We need at least one other bot looking at the commands. SieBot is asleep way too often. However
    1. If the bot behaves differently from SieBot, it should replace it and not work alongside it
    2. If the bots are to work concurrently, you would have to account for more than one bot picking up the same request (as neither can edit User:CommonsDelinker/commands to remove a request before they start executing it).
If the bot doesn't behave like SieBot, can you specify in the request how it differs? Does the bot alter the old category for example (afaik SieBot does not)? –⁠moogsi (blah) 02:40, 28 April 2013 (UTC)[reply]
As for working concurrently, the only (if not, main) problem if they're working on the same category at the same time would be an edit conflict, which is already handled. Specifically, the bot currently creates the new category page if it doesn't exist (attributing the authors in the summary, or on the talk page if the list is too long), then moves the categories. After it determines that the category is empty, it replaces the content of the old category page with {{Category redirect|"new category name"}}. All that can be seen from the trial I made. As for behaving differently, I think the main difference is the implementation, and probably that my bot actually edits the old category afterwards (not sure if SieBot does that).  Hazard-SJ  ✈  02:56, 28 April 2013 (UTC)[reply]
{{Move}} requests have to be stripped during the transfer, no need to remove it from the delinker queue as it needs manual inspection (5 % of moves need manual intervention or category restructuring). --Foroa (talk) 16:08, 29 April 2013 (UTC)[reply]
I can implement that.  Hazard-SJ  ✈  02:25, 30 April 2013 (UTC)[reply]
  •  Support I want to make it clear that I support the proposal in its current form, before I start talking about additional features :) One thing which SieBot doesn't do (and which I think wouldn't be difficult to implement) is leave edit summaries for category moves. {{Move cat}} has a reason parameter which basically goes unused, as SieBot operates apparently without purpose –⁠moogsi (talk) 19:35, 12 May 2013 (UTC)[reply]

If nobody has further objections, I propose that we approve this request. I expect that there will be some teething issues, but am confident that the bot operator is capable and will be sufficiently responsive to resolve them. --99of9 (talk) 13:32, 14 May 2013 (UTC) Approved --99of9 (talk) 14:59, 30 May 2013 (UTC)[reply]

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Bots/Requests/Hazard-Bot_7&oldid=97301218"