Commons:Bots/Requests/Gabrielchihonglee-Bot (3)

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

Gabrielchihonglee-Bot (talk · contribs) (3)

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

Bot's tasks for which permission is being sought: Fix double redirects as discussed in Commons:Bots/Work_requests#Double_category_redirects. Created with tremendous help from User:Zhuyifei1999.

Automatic or manually assisted: Automatic

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

Maximum edit rate (e.g. edits per minute): 6 edits / min

Bot flag requested: (Y/N): YES

Programming language(s): Python (pywikibot & mwparserfromhell)

Gabrielchihonglee (talk) 02:40, 13 January 2018 (UTC)[reply]

Discussion

  • Please see step III above. --Schlurcher (talk) 06:30, 13 January 2018 (UTC)[reply]
  • For to have a closer look at this problem I fixed a few hundred links using AWB (mainly page names starting with chars '0..9') and I noticed two things to be observed:
- There are links that contain invisible LTR marks and thus require special treatment.
- The {{Synonym taxon category redirect}} template transcludes {{Category redirect}}. Depending on your implementation (I don't know how you do detect the double catredirects) this might possibly need to be handled specially as there are catredirecting pages having more than one outgoing link pointing to other redirecting pages or to somewhere else: Illustrating this by an example: Category:Anagallis would be a false positive pointing to Category:Lysimachia but having also an outgoing page link to redirecting Category:Anagallis arvensis. But maybe that's irrelevant due to your algorithm.
--Achim (talk) 10:12, 13 January 2018 (UTC)[reply]
Looks good to me. --Schlurcher (talk) 13:55, 16 January 2018 (UTC)[reply]
No objections, looks good to me, too. --Achim (talk) 19:52, 16 January 2018 (UTC)[reply]

Approved. --Krd 13:00, 29 January 2018 (UTC)[reply]