Open main menu

BAG member instructions

If you want to run a bot on the English Wikipedia, you must first get it approved. To do so, follow the instructions below to add a request. If you are not familiar with programming it may be a good idea to ask someone else to run a bot for you, rather than running your own.

New to BRFA? Read these primers!
 Instructions for bot operators

Contents

Current requests for approval

DannyS712 bot III 56

Operator: DannyS712 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 03:09, Tuesday, August 13, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Javascript

Source code available: User:DannyS712_test/redirects.js

Function overview: Automatically patrol redirects that only differ in the use of dashes/hyphens/etc

Links to relevant discussions (where appropriate):

Edit period(s): As needed

Estimated number of pages affected: A dozen per week (guessing)

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Patrol redirects where the title and target match the form Foo[-‒–—―]Bar -> Foo[-‒–—―]Bar, meaning that the only difference is the use of a dash/hyphen/minus sign, etc

Discussion

  • What does it mean to "patrol" these redirects? What will the bot do when it encounters a redirect that matches the criteria described above? ‑Scottywong| yak _ 03:37, 13 August 2019 (UTC)
    @Scottywong: the bot is a new page patroller - when it finds an unpatrolled redirect that matched the criteria, it marks the page as patrolled DannyS712 (talk) 03:40, 13 August 2019 (UTC)
    Ok, thanks. While I don't see this particular task saving more than perhaps a minute or two of time per week for new page patrollers, it doesn't seem like it could do much harm either. ‑Scottywong| gossip _ 00:41, 14 August 2019 (UTC)
    @Scottywong: its part of a series of bot tasks to patrol uncontroversial redirects - see User:DannyS712 bot III/rules --DannyS712 (talk) 00:50, 14 August 2019 (UTC)

PearBOT

Operator: Trialpears (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 12:12, Saturday, August 10, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: Standard pywikibot: Source code at User:PearBOT/Aircraft specs/source

Function overview: Converting instances of the deprecated template {{aircraft specifications}} to {{aircraft specs}}

Links to relevant discussions (where appropriate): Wikipedia talk:WikiProject Aircraft#Template:Aircraft specs merger bot, Wikipedia:Templates for discussion/Log/2019 March 20#Template:Aerospecs

Edit period(s): One time run, probably with secondary run(s) when problems encountered by the bot has been fixed manually and the bot handles more edge cases.

Estimated number of pages affected: The template has 1868 transclusions. The bot will only be able to convert about half without human assistance, in a secondary run where problems have been manually fixed and/or the bot can handle more edge cases up to a few hundred more could be converted.

Exclusion compliant (Yes/No): Yes

Already has a bot flag (Yes/No): No

Function details: The bot will go through all transclusions of {{Aircraft specifications}} replacing the template with {{Aircraft specs}} after reformatting the information to be compatible with the new template. If the bot encounters anything unexpected it will skip the page and report the problem at User:PearBOT/Aircraft specs problems. After the original run editors can fix problems listed there (usually unit problems or extra text in parameters that usually only contain a number and a unit) or I can make the bot handle more edge cases and perform a secondary run converting more templates.

Discussion

A lot of people in that discussion believe that this is too complex for a bot. Are they wrong? Jo-Jo Eumerus (talk, contributions) 15:17, 10 August 2019 (UTC)
Jo-Jo Eumerus There were many editors expressing concerns about difficulties with the conversion, but I believe my solution can satisfy all of these concerns by skipping a lot of pages and changes to the template (currently in an edit request). I've tagged everyone who participated in the TfD discussion at Wikipedia talk:WikiProject Aircraft#Template:Aircraft specs merger bot giving them a chance to review test edits and noone has objected to it in it's current state. The biggest issue in the TfD seemed to be double rounding leading to less precise figures, which was a major concern with the old version of the template, but now after I've modified {{aircraft specs}} it's a much smaller issue. It now use the parameter values if they're avalible which makes all figures the same before and after the conversion. For values not in the pre conversion templates there could still be double conversions, but since adding values in units (usually Knots and Nautical miles) not previously displayed is an unambigous improvement I believe this would be acceptable. If it's not acceptable the bot will only be able handle a few without some manual assistance, but even in this case the bot can still do most of the work. --Trialpears (talk) 20:14, 10 August 2019 (UTC)

OAbot 3

Operator: Nemo_bis (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search) for this task; Pintoch (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search) as main owner and author of the bot

Time filed: 13:52, Thursday, July 25, 2019 (UTC)

Function overview: Add and maintain supported identifiers to citation templates (mostly {{cite journal}}), including related metadata such as access level but excluding the |url= parameter.

Automatic: A queue of edits is created automatically (manually triggered), then a cursory review of its contents is performed manually to exclude anomalies, then select items are moved to a queue for the bot to perform them automatically. Edits are then sampled for manual checks and some manual fixes are performed by the operators in the few hours or days following a bot run on the pages which ended up on Category:CS1 maintenance (typically less than one in a thousand).

Programming language(s): Python

Source code available: https://github.com/dissemin/oabot / phabricator:tag/oabot/ (relying on https://github.com/dissemin/dissemin/ and https://github.com/Impactstory/oadoi )

Links to relevant discussions (where appropriate): Wikipedia talk:OABOT, Help_talk:Citation_Style_1#RfC_on_linking_title_to_PMC and similar for the desirability of identifiers and precise information on them.

Edit period(s): Once every few weeks or months.

Estimated number of pages affected: Less than 20k for the first steps; more than 300k overall considering all articles with DOIs.

Namespace(s): 0

Exclusion compliant (Yes/No): Yes

Adminbot (Yes/No): No

Function details: Following the success of task OAbot 2, we're proposing to extend the functionality of the bot to all identifiers. The addition of arxiv and PMC identifiers (about 25k edits) has been a success: it has encountered few mistakes and the bot has been made more robust in response (for instance we are now stricter in matching publications).

The first step will be to add |hdl= identifiers and |hdl-access= status on about 2k articles. Those handles typically point to an institutional repository like https://ntrs.nasa.gov/ or https://deepblue.lib.umich.edu/ (the most common in the queue is https://quod.lib.umich.edu/ for now). Citation bot is also able to add such identifiers, but does so more slowly and does not (yet) set access status, while we now do (T228632): example edit [1].

After this is done, other identifiers will be handled depending on demand and volumes. The most consequential work will be to eventually add |doi-access=free to all relevant citations (an estimated 200k DOIs): this functionality was part of the original request (and not challenged by anybody) but later dropped when the bot became a user-triggered tool, as the number of required edits is incompatible with human editing.

Expected improvements in the new future, if this task is approved, include:

  • maintenance of existing identifiers, e.g. to remove or report on broken identifiers (e.g. CiteSeerX records which may have been taken down);
  • avoiding more publisher URLs even in manual mode, instead add DOIs or DOI access data where relevant (to avoid creating more work for Citation bot, which removes redundant URLs);
  • give the community full prior control on what identifiers are added by the bot, by adding a subpage to Wikipedia:OABOT where users would be able to blacklist individual URLs (and therefore identifiers) they consider undesirable for whatever reasons, including suspected errors in open access repositories (mismatch between record and DOI, files mistakenly open for download etc.), even if such cases are a minuscule minority.

Discussion

This might not be relevant yet, but I take that the bot won't add identifiers without some kind of procedure to reject unsuitable identifiers? This bot has had some copyright issues in the past. It also won't replace already existing URLs? Because that might be problematic under WP:SAYWHEREYOUGOTIT. Jo-Jo Eumerus (talk, contributions) 16:07, 25 July 2019 (UTC)
The current procedure to reject unwanted identifiers is to either blacklist the bot on the specific page with {{bots}} or comment out the identifier in the specific citation template. The proposed additional procedure is to let any user blacklist an identifier by means of linking it on a central subpage, so that it's no longer added to any other page: this will allow users to reject one, ten or a thousand identifiers with a single edit and have the community decide it by consensus.
This task proposes that no edits are made to the |url= parameter at all using the bot account. I'll note however that WP:SAYWHERE specifically states that «You do not have to specify how you obtained and read it. So long as you are confident that you read a true and accurate copy, it does not matter [...]». Nemo 16:24, 25 July 2019 (UTC)
I have no objection to adding hdl identifiers. But I am currently seeing huge numbers of OABot edits on my watchlist, making it difficult to find any other changes and impossible to manually check them for accuracy, and would be interested in knowing whether there are any plans for throttling the bot to a more reasonable rate of updates. Also, if the "other identifiers" to be added are to be included in this BRFA, they need to be specified explicitly. For instance, I would be opposed to automatically adding citeseerx identifiers automatically, for all the previously-discussed reasons, and wouldn't want this BRFA to be taken as sidestepping that discussion. —David Eppstein (talk) 17:57, 25 July 2019 (UTC)
On the first point, I agree we need a frank conversation on the scope of the task; I just suggest to avoid having the same conversation over and over for each new identifier. On the second, as far as I can see the bot has respected the typical rate limit of 12 edits per minute, but it would not be a problem to reduce the speed. Nemo 20:06, 25 July 2019 (UTC)
I support this task, but I'll let someone else from the BAG to do a review here. I'll note here that WP:BOTREQUIRE suggests 6 EPM for non-urgent tasks however. Headbomb {t · c · p · b} 14:10, 30 July 2019 (UTC)
One thing I would like to see is that zenodo support is added to CS1 templates. Headbomb {t · c · p · b} 14:13, 30 July 2019 (UTC)
Actually, Zenodo links were the reason why I did ask whether the bot won't add identifiers without some kind of procedure to reject unsuitable identifiers as we've had copyright problems and disputes about them. I am not sure if the problem was resolved, though. Jo-Jo Eumerus (talk, contributions) 14:20, 30 July 2019 (UTC)
This request, sic stantibus rebus, would not produce any addition of links to Zenodo, as there is no identifier for it. As for the existing identifier parameters, which evidently were added because the target websites are considered good resources rather than systematic copyright infringement rackets, the proposal is the blacklist of specific URLs above. The discussions you linked were often focused on hypothetical or apodictic statements, impossible to discuss constructively; if users instead can focus on explaining which URLs are bad for which reasons, a consensus will be easier to find. Nemo 19:56, 30 July 2019 (UTC)
I pushed a change to reduce the editing speed. Nemo 19:56, 30 July 2019 (UTC)

Sounds great, thanks for the update. – SJ + 18:38, 16 August 2019 (UTC)

TheSandBot 4

Operator: TheSandDoctor (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 06:51, Sunday, June 9, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: https://github.com/TheSandDoctor/American_British_page_mover/blob/master/cats_british_american_converter_server.py

Function overview: An extension of WP:Bots/Requests for approval/TheSandBot 3, this task moves categories and their associated subpages. This task is different enough to necessitate its own BRFA.

Links to relevant discussions (where appropriate): WP:Bots/Requests for approval/TheSandBot 3

Edit period(s): Until done

Estimated number of pages affected: 88 categories worth, so probably few hundred to couple thousand

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Reads category page names from User:Alex 21/sandbox2 into memory. Then the script repeats the following process on all listed categories:

  1. Moves category
  2. Reads the category page itself to determine if any of its categories need switching (if so, they are done now)
  3. Iterates through category contents (currently under previous name) and moves them to the current category
  4. Looks for any links from the old category name. If they are found, corrects them to new name

Discussion

Bots in a trial period

DannyS712 bot 47

Operator: DannyS712 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 03:00, Sunday, June 9, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): AWB

Source code available: AWB

Function overview: Help implement TfD closes

Links to relevant discussions (where appropriate):

Edit period(s): Continuous / as needed

Estimated number of pages affected: Thousands

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Per discussion at Wikipedia:Bots/Requests for approval/DannyS712 bot 46, I'd like to file a BRFA for implementing general TFD closes. Similar past tasks include Wikipedia:Bots/Requests for approval/DannyS712 bot 22, Wikipedia:Bots/Requests for approval/DannyS712 bot 23, and Wikipedia:Bots/Requests for approval/DannyS712 bot 31.

Discussion

  • Pinging participants in previous discussions: @Primefac --DannyS712 (talk) 03:03, 9 June 2019 (UTC)
  • I'm not entirely convinced as to the need for this bot when there are already two other bots approved for the same task. * Pppery * it has begun... 03:43, 9 June 2019 (UTC)
    @Pppery: Even if there is not a need for this, is there any disadvantage? As seen in #46, sometimes things do slip through the cracks. --DannyS712 (talk) 04:07, 9 June 2019 (UTC)
  • I'm recusing as a BAG member, but for the record here are the BRFAs for SporkBot and PrimeBOT (orphaning and merging), which as mentioned have a remit to implement TFD outcomes. I'm mostly ambivalent about having a third bot with the same remit. Primefac (talk) 12:58, 9 June 2019 (UTC) (please do not ping on reply)
  • If it can be demonstrated that this new bot will not be conflicting/getting in the way of the existing bots, then this is probably harmless/some net-benefit. -FASTILY 08:05, 16 June 2019 (UTC)
  • {{BAGAssistanceNeeded}} its been 10 days --DannyS712 (talk) 11:37, 19 June 2019 (UTC)
  • @DannyS712:   Approved for trial (50 edits). As per usual, please post a permalink here when done and take all the time you need for the trial. --TheSandDoctor Talk 04:04, 22 June 2019 (UTC)
    @TheSandDoctor:   Trial complete. 50 edits made: [2]. The only issue is that AWB edit summaries are too short, so I couldn't link to both the BRFA and the TFD, but once approved that shouldn't be an issue. --DannyS712 (talk) 09:58, 22 June 2019 (UTC)
    For the record, I find it in poor taste that Danny is using this trial/task to sidestep the decline of a previous BRFA. I have added the template in question to the auto-subst list and recommend sending this back to trial after said transclusions are removed. Primefac (talk) 12:28, 22 June 2019 (UTC)
    @Primefac: After you closed the previous BRFA, I realized the AnomieBOT generally isn't used for TfD substitutions - see here. The point of this BRFA was to implement TfD closes that are missed by the other bots, and Double image is exactly the type of template I was thinking about. I have no issue with an extended trial, and I apologize if I unintentionally misled you or TSD --DannyS712 (talk) 18:12, 22 June 2019 (UTC)
  • From a "things to think about" perspective, not only for this task but in general:
    • If you're linking to a TFD, link to the day (not the specific #subheading)
    • If the links/descriptions are getting too long, create a user subpage (e.g. I link to User:PrimeBOT/24 for Task 24 to keep things short).
Keeping these in mind you shouldn't have an issue linking to everything relevant. Primefac (talk) 12:52, 22 June 2019 (UTC)
{{BAGAssistanceNeeded}} Its been a week since the trial ended. --DannyS712 (talk) 05:22, 28 June 2019 (UTC)
@Primefac:, do you still have an objection to this task following the above response(s)? --TheSandDoctor Talk 04:56, 16 July 2019 (UTC)
I'm not sure what's changed. I'm still objecting to your sidestepping the previous TFD, and my opinions regarding this request (in general) have not changed; I'm still mostly ambivalent. I'm also still recusing from BAG duties on this task. Primefac (talk) 16:35, 16 July 2019 (UTC)
@TheSandDoctor: Can you take a look at this? DannyS712 (talk) 14:28, 24 July 2019 (UTC)
@TheSandDoctor: {{BAGAssistanceNeeded}} --DannyS712 (talk) 18:28, 1 August 2019 (UTC)
  Approved for extended trial (50 edits). We got off on a bit of the wrong foot, let's see if we can correct it. Primefac (talk) 23:01, 7 August 2019 (UTC)
Thanks - will report back with results --DannyS712 (talk) 23:02, 7 August 2019 (UTC)
Made the first 4 edits - [3]. I haven't seen many TfDs closed as orphan or substitute recently, so its taking a while. DannyS712 (talk) 00:31, 18 August 2019 (UTC)
There are a ton of templates to convert, merge, replace, etc, but obviously take what you're comfortable with. Primefac (talk) 19:18, 18 August 2019 (UTC)

Ahechtbot 6

Operator: Ahecht (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 03:36, Friday, June 7, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): python

Source code available: User:Ahechtbot/transclusioncount.py

Function overview: Create lua-formatted lists of highly transcluded templates.

Links to relevant discussions (where appropriate): Template talk:High-use#Number of transclusions

Edit period(s): Weekly

Estimated number of pages affected: 27

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Will run a script similar to that used to generate Wikipedia:Database reports/Templates transcluded on the most pages (which is no longer regularly updated). All edits will be to subpages of a single module. No more than 27 edits will be made per week outside of the bot's userspace.

Discussion

  • If I understand correctly, Module:Transclusion count, when it is created, will be redundant to Module:Data. * Pppery * it has begun... 11:43, 7 June 2019 (UTC)
    • Not exactly. The module will take a template name as input, extract the first character, load the appropriate data table based on that character (either "A"–"Z" or "other"), and return the transclusion count. I could have the bot load the data into a submodule of Module:Data and leave the name parsing to Wikitext (e.g. {{#invoke:Data|Module:Data/Template transclusions/{{#invoke:String|match|s={{PAGENAME}}|pattern=^[A-Z]|nomatch=other}}|{{PAGENAME}}}}), but since that requires spinning up Lua twice it seemed cleaner to do it all in one step in a new module and just call {{#invoke:Transclusion count}}. --Ahecht (TALK
      PAGE
      ) 14:12, 7 June 2019 (UTC)
      • Well, I don't see the benefit of splitting the data pages by letter either and the code you posted falls far below my standard of "merits a Lua module" -- but its probably better to let TfD decide this rather than arguing about it on a bot request. * Pppery * it has begun... 19:00, 7 June 2019 (UTC)
        • Splitting pages by letter code was mainly due to the size. Most of the Database reports tend to split lists with over a thousand entries, and splitting by letter makes lookup of any particular template straightforward. There are thousands of templates that will end up on this list, and having the documentation page for each of the thousands of pages using {{high use}} loading and parsing a giant table weekly seemed inefficient from a server load standpoint. --Ahecht (TALK
          PAGE
          ) 13:47, 9 June 2019 (UTC)
  •   Approved for trial (28 days). Ahecht, I know it might take a bit to create the module and related content, so run the 4 weeks from whenever the bot starts editing. As far as implementation goes I'll leave that to you, but from a "proof of concept" I think replacing a few calls to {{high risk}} with a sandbox version that invokes the module will work. Primefac (talk) 12:49, 15 June 2019 (UTC)
    • @Primefac:   On hold. The trial is currently on hold. There is currently an issue with the toolforge database replicas, and the transclusions query that had been taking about 15 minutes is now timing out after 30 minutes or so (the same query, which had run successfully at https://quarry.wmflabs.org/ is also now failing there, so this appears to be a global issue, not a bot-specific one). I will run the trial once this gets resolved. --Ahecht (TALK
      PAGE
      ) 16:54, 20 June 2019 (UTC)
      • Just a quick update: The database replica issue seems to be resolved (and, according to the phab:T226050, future slow-downs should last hours, not days), but I will be away from the internet next week so I don't want to start a 4-week trial before that. I will re-activate this BRFA when I return. --Ahecht (TALK
        PAGE
        ) 03:13, 22 July 2019 (UTC)
        • I started the first run on Friday, and had to make a few tweaks to get it working properly when saving in the Module: namespace. It's now set to run each Sunday morning for the next few weeks. --Ahecht (TALK
          PAGE
          ) 00:28, 12 August 2019 (UTC)

Xinbenlv bot

Operator: Xinbenlv (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 06:29, Wednesday, February 20, 2019 (UTC)

Function overview: User:Xinbenlv_bot#Task 1: Notify (on Talk page) cross language inconsistency for birthdays.

Automatic, Supervised, or Manual: Automatic

Programming language(s): Javascript

Source code available: [4]

Links to relevant discussions (where appropriate): Wikipedia:Village_pump_(technical)/Archive_166#Cross_Lang_Conflicts

Edit period(s): daily or twice a week

Estimated number of pages affected: 30 per day to begin with, can increase to 100 per day if community sees it helpful. Speed is completely controllable. Overall, there are a few thousands between major wikis like EN - JA(~3000), EN - DE(~5000).

Namespace(s): Talk

Exclusion compliant (Yes/No): Yes

Adminbot (Yes/No): No

Function details:

The bot will notify editors by writing a new section on Talk page of a subject, if that subject has inconsistent birthdays in this and another wikipedia languages.

The data of inconsistency comes from a public available dataset Github, called Project WikiLoop. An example edit looks like this

- Notifying French Editors fr:Utilisateur:Xinbenlv/sandbox/Project_Wikiloop/unique_value/Discussion:Samuel_Gathimba
- Notifying English Editors en:User:Xinbenlv/sandbox/Project_Wikiloop/unique_value/Talk:Samuel_Gathimba

Discussion

  • {{TakeNote}} This request specifies the bot account as the operator. A bot may not operate itself; please update the "Operator" field to indicate the account of the human running this bot. AnomieBOT 06:49, 20 February 2019 (UTC)
Fixed, changed to User:Xinbenlv. Xinbenlv (talk) 06:54, 20 February 2019 (UTC)
  • {{TakeNote}} This bot appears to have edited since this BRFA was filed. Bots may not edit outside their own or their operator's userspace unless approved or approved for trial. AnomieBOT 06:49, 20 February 2019 (UTC)
@Anomie, @AnomieBOT, Sorry, I mistakenly used my bot account to create its BRFA, it was me manually. The only bot auto edits are those in its User page. Xinbenlv (talk) 06:52, 20 February 2019 (UTC)
Don't worry about it Xinbenlv. I've struck it now as the notice isn't relevant. --TheSandDoctor Talk 04:17, 21 February 2019 (UTC)
Thank you, that makes sense. I also updated the Not for operator. Let me know if I've not done it right. @TheSandDoctor. Xinbenlv (talk) 07:18, 21 February 2019 (UTC)
This bot is helping on cross-language inconsistency therefore it shall be editing other languages, how should I apply for global bot permission? Xinbenlv (talk) 06:53, 20 February 2019 (UTC)
@Xinbenlv:, m::BP should be what you're looking for. RhinosF1(chat)(status)(contribs) 16:16, 20 February 2019 (UTC)
Thank you RhinosF1 thank you!. it seems the m::BP requires the bot to obtain local community permission and keep it running locally for a while. Therefore, I think I shall apply for approvals from multiple local communities each individually for now. Do I understand it correctly? Xinbenlv (talk) 18:48, 20 February 2019 (UTC)
Xinbenlv, That's how it read to me aswell. It's probably best to make them aware anyway before launching anything that will affect them in a big way (e.g. mass notifications being issued). You don't want to cause confusion. RhinosF1(chat)(status)(contribs) 19:01, 20 February 2019 (UTC)
RhinosF1 Thanks, agreed! That's why I am asking advice and approval in English Wikipedia so this most active community can help take a look of my (wild?) idea. Xinbenlv (talk) 19:07, 20 February 2019 (UTC)
Xinbenlv, I think it's a great idea. RhinosF1(chat)(status)(contribs) 19:25, 20 February 2019 (UTC)
Thanks everyone who are interested. Just so that you know, the bot has two trial edits on German wiki, as encouraged by the BRFA discussion. Feel free to take a look and advice is welcomed! Xinbenlv (talk) 21:59, 21 February 2019 (UTC)
Added Xinbenlv (talk) 17:15, 25 February 2019 (UTC)
    1. How often is the dbase updated? Could this potentially result in one page receiving multiple notices simply because no one has either seen or cared enough to fix the missing information?
Datebase will be updated on a daily / weekly basis, currently still in development. I plan to also rely on "Xinbenlv_bot" to surppress articles that already been touched by the same bot. Xinbenlv (talk) 17:15, 25 February 2019 (UTC)
This seems like a reasonable task to deal with cross-wiki data problems, just want to get a better feel for the size and scope of the task. Primefac (talk) 20:26, 24 February 2019 (UTC)
Thanks @Primefac: If I apply to change the bot scope to be "=<200 edits in total" for first phase, what do you think? Xinbenlv (talk) 21:37, 24 February 2019 (UTC)
The number of edits per day/week/month can be discussed, I'm just looking for more information at the moment. Primefac (talk) 21:47, 24 February 2019 (UTC)
What can I do to provide the information you need? Xinbenlv (talk) 02:04, 25 February 2019 (UTC)
Just looking for some numbers. I assume you know where to find them better than I would. Primefac (talk) 02:07, 25 February 2019 (UTC)
@Primefac: The EN-JA file contains around ~3000 inconsistencies of birthdays, the EN-DE contains around ~5000 inconsistencies. To begin with, I think we can limit to 100 - 200 edits on English Wikipedia. Xinbenlv (talk) 16:47, 25 February 2019 (UTC)

@Xover's suggestion regarding using maintenance template

Would adding a maintenance template (that adds a tracking category) be a viable alternative to talk page notices? It might be more effort due to the inherently cross-project nature of the task, but talk page notices are rarely acted on, is extra noise on busy talk pages, and may cause serious annoyance since the enwp date may be correct (it's, for example, the dewp article that's incorrect) and the local editors have no reasonable way to fix it. A tracking category can be attacked like any gnome task, and the use of a maint template provides the option of, for example, flagging a particular language wikipedia as having a verified date or specifying that the inconsistency comes from Wikidata. In any case, cross-project inconsistencies are an increasingly visible problem due to Wikidara, so kudos for taking on this issue! --Xover (talk) 18:41, 25 February 2019 (UTC)

@Xover: thank you. So far, I am applying to 5 different wikis for botflag in the same time. I received 3 suggestions:
1. use template and transclusion
2. add category
3. put it as a over article "cleanup" message box or Talk page message.
For the #1 and #2, there is consensus amongst all responding communities (EN, DE, ZH, FR). So now the trial edits on these communities are using template and category, see ZH examples:
* https://zh.wikipedia.org/wiki/Category:WikiProject_WikiLoop/Inconsistent_Birthday
For #3, put it as an over article "cleanup" message box, the DE community some editors prefer a Talk page message, while some prefer over-article message box. My personal opinion is that we can start slow, do some Talk page message (like 200) for trial edits, and then when they looks good, we can start to approve for allowing the bot to write over article messages? The reason being, I hope it demonstrate more stability before writing on (article) namespace. Especially for such high impact wikis of English wikipedia.
By the way, the format I prepare for English wikipedia is actually a maintenance template at User:Xinbenlv_bot/msg/inconsistent_birthday, could you take a look, @Xover:?
Xinbenlv bot (talk) 22:09, 25 February 2019 (UTC)
Well, assuming the technical operation of the bot is good (no bugs) maint. templates in article space are generally less "noisy" than talk page messages (well, except the big noisy banners that you say dewp want, but that's up to them). I suspect the enwp community will prefer the less noisy way, but I of course speak only for myself. In any case, I did a small bit of copyediting on the talk page message template. It changed the tone slightly, so you may not like it, and in any case you should feel free to revert it for whatever reason. Finally, you should probably use {{BAGAssistanceNeeded}} in the "Trial edits" section below. --Xover (talk) 05:22, 26 February 2019 (UTC)
There was a consensus to stop InternetArchiveBot from adding talk page notices. I suspect that if this bot were to start running that there would be a similar consensus to stop adding the same. My suggestion is not to do #3. --Izno (talk) 23:29, 29 March 2019 (UTC)

Trial Edits now available (in sandbox)

Dear all admins and editors,

I have generated 30 trial edits in sandbox, you can find them in en:Category:Wikipedia:WikiProject_WikiLoop/Inconsistent_Birthday. I also generated 3 trial edits in real Talk page namespace


Please take a look. Thank you!

Xinbenlv (talk) 00:13, 26 February 2019 (UTC)

Update: [5] shows editor @LouisAlain: who happens to be the creator of en:Gaston_Blanquart, which is one of our 3 trial edits, update the birthday and death date on English Wikipeda. Xinbenlv (talk) 08:22, 1 March 2019 (UTC)
Update : generated 10 more trial edits in Talk namespace, I will actively monitor them. Xinbenlv (talk) 08:33, 1 March 2019 (UTC)
Dear Admins and friends interested in this topic @RhinosF1:, @Primefac:, @Xover:, @TheSandDoctor:, how do I proceed to apply for the bot status? Xinbenlv (talk) 00:38, 7 March 2019 (UTC)


Confess - realized trial edits before trial approval

{{BAG assistance needed}}

Dear Admin, I just realize English Wikipedia requires trial edits approval before running trial edits, which I already did for 9 edits in (Article) namespace. Shall I revert the trial edits? I am sorry Xinbenlv (talk) 21:13, 15 March 2019 (UTC)
@Xinbenlv: don't revert if they were good edits. — xaosflux Talk 13:49, 20 March 2019 (UTC)
@Xaosflux:, OK, thank you! By the way, is there anything else I need to do other than just wait for people to comment? It seems the discussion has halted.
How should I get trial approval?
Xinbenlv (talk) 18:08, 20 March 2019 (UTC)
Xinbenlv You just have to wait for a a member of the bot approvals group to come and approve a trial. Galobtter (pingó mió) 15:07, 22 March 2019 (UTC)

Discussion Redux

Could I just verify something? I notice that all of the sandbox trials are placing what appear to be talk page sections, while it sounds like the majority of participants (on multiple languages) feel either a maintenance template or category are more appropriate to fix this issue.

In other words, the template you've made looks like it's a wall of text that (as mentioned previously) users aren't generally thrilled about dealing with. Is there another way to make this template look more like a "maintenance" template? Maybe just the intro line ("An automated process has determined...") and the table, with instructions to remove when checked? Something that can be placed at the top of a talk page? Primefac (talk) 20:16, 4 April 2019 (UTC)

@Primefac: thank you for your question.
Message box My understanding of consensus is the other way around, for example in EN Wiki, My suggestion is not to do #3. --Izno.. In German on de:HD:Personendaten after a long discussion they reached a consensus that a talk page section (not look like a message box) is preferred in their opinions.
Category: The category is in place, see en:Category:Wikipedia:WikiProject_WikiLoop/Inconsistent_Birthday, this is added by including the template.
Actually I have an iteration that does message-box like notification but then was suggested to change to talk page section.
Something that makes this process very challenging is this is a cross language project so we are trying to accommodate suggestions from different language of Wikis while try to keep them as aligned as possible so we can effectively maintain them across languages. See FAQ m:User:Xinbenlv_bot

─────────────────────────   On hold. I feel there's a sweet spot to be had. A short message done through a template would be ideal.

== Possible Wikidata issue==
{{Inconsistent Interwiki/Wikidata Issue<!-- Come up with a better name than this please
 |lang1=fr |subject1=Ernst Joll |date1=1902-06-19
 |land2=en |subject2=Ernst Joll |date2=1902-09-10
 |fixed=yes/no
}}
Automated notice by ~~~~

@RexxS and Pigsonthewing:, you're the resident Wikidata experts here. Could you come up with a template that scales generalize to other Interwiki/Wikidata conflits? @Xinbenlv: feel free to participate in those efforts too. Until that template is designed, I'm going to put this on hold. Headbomb {t · c · p · b} 05:21, 9 April 2019 (UTC)

Thank you, agreed Xinbenlv (talk) 19:01, 15 April 2019 (UTC)
@Headbomb and Xinbenlv: It's quite difficult to shorten the documentation by much, but I've made a demo at User:Rexxbot/msg/Inconsistency. It takes 11 named parameters, because if you want to generalise it to other inconsistency issues, you need to supply the name of the issue as well as the other parameters. Here's an extract from the rudimentary documentation that I knocked up:
{{User:Rexxbot/msg/Inconsistency
| issue    = birth date
| lang1    = en
| article1 = Ernst Joll
| value1   = 1902-09-10
| lang2    = fr
| article2 = Ernst Joll
| value2   = 1902-06-19
| bot      = Xinbenlv bot
| date     = 28 April 2019
| status   =
| by       =
}}
You can see what it produces by looking at the documentation page at User:Rexxbot/msg/Inconsistency/doc.
If it's any use to you, please feel free to hack at these pages until you have something to your liking and/or take it for your own bot space (no attribution needed). Let me know if you want me to fix any of it. Cheers --RexxS (talk) 21:40, 28 April 2019 (UTC)
@RexxS: I've made a small tweak. The headers should be made by the bot, since we want those to give editable sections. Or at least sections that are editor-friendly. For the rest, I'm generally indifferent to the output and exact functionality, although the eyes of @Pigsonthewing and Xinbenlv would be appreciated to see if the design of the template is solid and scaleable. If everyone agrees it's a good design (and agree on a template name, e.g. {{Interwiki issue}}), we can proceed to trial. There's an option to have that as a wrapper template to create issue-specific sub-templates, but that might be a case of over engineering. Headbomb {t · c · p · b} 21:48, 28 April 2019 (UTC)
@RexxS: also tweaked the 'by' parameter to take a signature instead. Headbomb {t · c · p · b} 21:56, 28 April 2019 (UTC)
@Headbomb: That's fine, but I was under the impression that the template would only be deployed by the bot, so it really isn't likely to care what the template is called  . --RexxS (talk) 21:57, 28 April 2019 (UTC)
Well the bot wouldn't really care, but it's less WTF-y to have a template in template space for this. It could be in the bot's userspace, but that makes it a bit harder to find if similar bots are deployed in other languages, which may harm some internationalization efforts. Not a huge issue, but might as well do things right when we can. Headbomb {t · c · p · b} 22:01, 28 April 2019 (UTC)
That makes sense, even though the only technical difference between template space and any other namespace is you don't have to include the namespace prefix when transcluding it. You're right though, if you're anticipating using this sort of template with other bots, then template space is the best place for ease of location. Good thinking. --RexxS (talk) 22:19, 28 April 2019 (UTC)

{{OperatorAssistanceNeeded}} Headbomb {t · c · p · b} 01:16, 13 May 2019 (UTC)

thank you!. @Headbomb:,
  1. we expect to provide more than 2 inconsistency languages, such as 3 - 5, what will the template look like in that case?
  2. we hope to ensure cross-language consistency, if this template is going to be internationalized and copied to other languages Wikis, what is a best way to do so?
Xinbenlv (talk) 04:59, 13 May 2019 (UTC)

For 1, I believe you can just scale |lang1/article1/value1= to |lang3/article3/value3= etc. RexxS can confirm. For 2, no idea. It's good to think about, but that's not a blocker for the English Wikipedia or this bot. Headbomb {t · c · p · b} 05:06, 13 May 2019 (UTC)

@Headbomb and Xinbenlv: I'm pretty certain that it will scale gracefully to more languages, but I'd really recommend getting the bot working and approved before trying to modify it. It's far easier to get approval for improvements once there's evidence of it already working on a simpler task or smaller scale. As for internationalisation, you can call the Lua module Module:Complex date] to render dates in the wiki's language if that's the part you feel may need translating, as long as the module is available on the wiki you're working on. I assume that you've already taken care of the article titles in other languages. Beyond that, you just need to translate the text and documentation. Cheers --RexxS (talk) 16:48, 13 May 2019 (UTC)
Then once the template is moved to the Template namespace to its 'official name' (i suggest {{Interwiki issue}}, but it could be something else),   Approved for trial (10 edits).. Headbomb {t · c · p · b} 17:10, 13 May 2019 (UTC)
@RexxS:, very helpful, in particular the date internationalisation that I haven't think o.
@Headbomb: thanks for granting the trial edits. Xinbenlv (talk) 03:46, 15 May 2019 (UTC)
Sorry for my late arrival to this discussion. Xinbenlv, will there be some way for a user to mark the template, so that it is removed from the tracking category, but not retagged? For instance, when the date on enwp is confirmed as correct. Also, how does the dataset accommodate different calendars, such as when one wiki may list a date in the Gregorian calendar and another in the Julian? StudiesWorld (talk) 21:11, 30 May 2019 (UTC)
Yes!, @StudiesWorld: there are in the template if you mark fixedBy=someone Xinbenlv (talk) 22:11, 30 May 2019 (UTC)
Xinbenlv, great! Have you run the trial yet? StudiesWorld (talk) 22:26, 30 May 2019 (UTC)

{{OperatorAssistanceNeeded}} Headbomb {t · c · p · b} 04:17, 6 August 2019 (UTC)

@StudiesWorld:, hi yes we conducted some trial runs on other languages and is still in debate of what's the best format to notification. Xinbenlv(t) please notify me with {{ping}} 00:19, 8 August 2019 (UTC)

SportsStatsBot 2

Operator: DatGuy (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 18:49, Thursday, April 4, 2019 (UTC)

Automatic, Supervised, or Manual: automatic

Programming language(s): Python

Source code available: https://github.com/DatGuy1/footy/blob/master/playerstats.py

Function overview: Automatically update football (soccer) players' career statistics

Links to relevant discussions (where appropriate):

Edit period(s): Every 15 minutes

Estimated number of pages affected: Unsure

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: I've been holding a few tests over at the testwiki. Runs a check every 15 minutes. Uses data from soccerway.com (provided from Opta Sports)

Discussion

  • Looking over the contributions at testwiki, that page doesn't appear to have any sources. How exactly would you add sources for these edits here on enwiki? --DannyS712 (talk) 04:52, 7 April 2019 (UTC)
  • Unless the plan is for a subset of footballers, there are more than 100,000 football biographies, so I think you'd want to think about how often the statistics need to be updated (even once a month would be in the range of tens of thousands of edits a month, depending on whether it is offseason of course) and discuss at WT:FOOTBALL. Galobtter (pingó mió) 07:44, 7 April 2019 (UTC)
  • The plan is for a case-by-case basis starting out. Afterwards if all goes well, I'll seek to gain consensus on categories for a specific league/country before mass-implementing any changes. Dat GuyTalkContribs 13:30, 7 April 2019 (UTC)
    @DatGuy: You say "case-by-case basis starting out" - what pages do you intend to start out with? --DannyS712 (talk) 00:52, 10 April 2019 (UTC)
Probably some Championship players. Dat GuyTalkContribs 11:03, 11 April 2019 (UTC)

{{BAGAssistanceNeeded}}

What length/type of trial would you prefer, DatGuy? I am open to suggestions in this case. --TheSandDoctor Talk 19:50, 27 April 2019 (UTC)

@TheSandDoctor: Most of the major leagues are ending soon. There's three Serie A matchdays remaining, so maybe a trial for a player on a team in that league? Dat GuyTalkContribs 12:49, 30 April 2019 (UTC)


  Approved for trial (10 edits). @DatGuy: As per usual, take all the time that you need to complete this trial and post the results here when done (preferably diffs or perma link to contribs section). --TheSandDoctor Talk 18:20, 2 May 2019 (UTC)

I'm going to be away for a few days soon. I'll start the trial ~ the 9th. Dat GuyTalkContribs 11:07, 4 May 2019 (UTC)
TheSandDoctor The bot will run on Gabriel Barbosa and Luan Garcia. Dat GuyTalkContribs 15:51, 11 May 2019 (UTC)
@DatGuy: would you mind using big-endian / or an ISO 8601 like date format in your edit summaries, just to head of any future complaints? — xaosflux Talk 02:05, 28 May 2019 (UTC)
  Done, Dat GuyTalkContribs 11:25, 28 May 2019 (UTC)
  • So about the citations... In edits such as this it looks like you are updating a table that is already cited, to a source that is older than your 'as of' new date stamp. So, it looks like the citation no longer matches the article text but is being left there. How can this be improved? — xaosflux Talk 15:33, 28 May 2019 (UTC)
{{OperatorAssistanceNeeded}} can you comment on the question above? — xaosflux Talk 18:13, 16 June 2019 (UTC)
@Xaosflux: Very sorry about the delayed response/hiatus in editing. Before adding a page I'd check if there's a Soccerway.com reference, and if not add it. I've also fixed a bug. Can the trial be restarted and for ~6 edits? Thanks. Dat GuyTalkContribs 05:14, 18 July 2019 (UTC)
@DatGuy: so in the edit I mentioned above, you changed content, but that content was already cited. Your changed content is newer than the existing citation - so it should no longer be supported by the citation that you are leaving there. — xaosflux Talk 11:58, 18 July 2019 (UTC)
Xaosflux, I don't think I understand. {{Soccerway}} would be used as a reference on pages the bot runs on, as is in Gabriel Barbosa. The website automatically updates after every match. Does that make sense? Dat GuyTalkContribs 05:44, 19 July 2019 (UTC)
@DatGuy: OK, in this edit there is a table, it is already cited, wtih a citation from 2019-03-25. You changed the data in the table to be about an event on 2019-04-04 - how is your new content still supported by that citation? — xaosflux Talk 11:23, 19 July 2019 (UTC)
Xaosflux, do you mean the BBC Sport reference? The other {{NFT player}} template is dynamic. Dat GuyTalkContribs 08:32, 25 July 2019 (UTC)
Yes the www.bbc.co.uk reference that is current referencing that chart. — xaosflux Talk 11:36, 25 July 2019 (UTC)

───────────────────────── To be honest, the BBC Sport reference isn't necessary. It's nice to have since the player had only played one international game and the article is more detailed, but it could work only with the National-Football-Teams.com reference, since that one automatically updates on the same page. Dat GuyTalkContribs 20:19, 1 August 2019 (UTC)

Bots that have completed the trial period

WikiCleanerBot 10

Operator: NicoV (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 09:35, Wednesday, July 10, 2019 (UTC)

Function overview: Fix some errors reported by Special:LintErrors/misnested-tag

Automatic, Supervised, or Manual: Automatic

Programming language(s): Java (WPCleaner)

Source code available: On GitHub (especially algorithm 539)

Links to relevant discussions (where appropriate):

Edit period(s): Several edit sessions to go through the existing list once, then once or twice a month at most.

Estimated number of pages affected: On the ~7000 pages currently in Special:LintErrors/misnested-tag, a dry run results in about 250 pages modified.

Namespace(s): Main

Exclusion compliant (Yes/No): Yes

Function details: Fix some cases of misnested tags as reported by Special:LintErrors/misnested-tag. The idea is to fix cases where there's no doubt about the solution. For example, on 101 Ways to Leave a Gameshow, it will replace ''心跳阿根廷<br><small>Xin Tiao A Gen Ting''</small> by ''心跳阿根廷<br><small>Xin Tiao A Gen Ting</small>'' (correct nesting of italic and small).

Discussion

{{BAG assistance needed}} Any objection on running a few test edits? --NicoV (Talk on frwiki) 11:44, 30 July 2019 (UTC)

  •   Approved for trial (50). NicoV, please post a permanent link of the bot's contributions page which shows the edits. If you have any questions, please do ask away. --TheSandDoctor Talk 03:26, 6 August 2019 (UTC)

DannyS712 bot 53

Operator: DannyS712 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 15:03, Friday, July 19, 2019 (UTC)

Automatic, Supervised, or Manual: manual

Programming language(s): Javascript

Source code available: Modified version of User:Qwertyytrewqqwerty/DisamAssist

Function overview: Disambiguate links following page moves without flooding recent changes

Links to relevant discussions (where appropriate):

Edit period(s): As needed

Estimated number of pages affected: Variable, probably only used for more than 30 links per dab page

Exclusion compliant (Yes/No): No

Already has a bot flag (Yes/No): Yes

Function details: Sometimes an RM is closed with consensus to disambiguate, and a new dab pages is created. All incoming links to that page were, minutes ago, working links to the page that was moved, and after the dab page is created they must be retargeted to keep working. Having closed a recent requested move and then making over 250 edits to retarget links, this would avoid flooding recent changes (though the script does limit the rate of edits)

Discussion

This is a WP:CONTEXTBOT issue, many of the links this bot will be "fixing" will be incorrect (as the initial link will be wrong in the first place), making the issue worse, not better. Leave this to the human dab solvers to deal with. IffyChat -- 08:39, 29 July 2019 (UTC)

@Iffy: my intention was to make these edits manually, and to only use the bot account to avoid flooding recent changes (since enwiki doesn’t have a “flooder” user group). I’ve changed it to be manual instead of supervised - sorry for the confusion. I agree that this has context issues, but all edits are being made manually by me, so I think it should be okay. Thanks, —DannyS712 (talk) 16:48, 29 July 2019 (UTC)
{{BAGAssistanceNeeded}} - this has been open for a week and a half. I hope my clarification that this is a manual task (meaning that I will personally use the script to make each individual change) helps. If desired I could do this with a different bot account to separate "automatic" (bot) tasks from "manual" (flood) tasks --DannyS712 (talk) 21:32, 30 July 2019 (UTC)
  •   Approved for trial (20 edits or 14 days). (which ever comes first) with the clarification that this is 100% manual, bot as a bot-ran-task it should not change the meaning of any article content. — xaosflux Talk 00:49, 6 August 2019 (UTC)
    @Xaosflux: what do you mean "as a bot-ran-task"? DannyS712 (talk) 00:52, 6 August 2019 (UTC)
    @DannyS712: Since this is running as a bot, it should not be changing the "meaning" of statements in articles, such as changing a wikilink to go from pony to pony; that is you will need to manually make sure the context of the link persists through the edit. — xaosflux Talk 00:57, 6 August 2019 (UTC)
    @Xaosflux: oh, okay. That makes sense. I was just confused by the juxtaposition of "100% manual" and "bot-ran-task".   Trial complete. - I happened to come across the exact situation at Talk:Mission: Impossible (1966 TV series)#Requested move 26 July 2019. Half of the edits at [6] are the trial (the other half was task 52 running at the same time - search for "Disambiguating" to find the relevant changes). Thanks, --DannyS712 (talk) 01:54, 6 August 2019 (UTC)

qbugbot 3

Operator: Edibobb (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 05:01, Friday, March 29, 2019 (UTC)

This will edit pages created by qbugbot 2, updating references, photos, common names, and a few minor edits. Not all changes will be made to all pages, and some pages will not be changed.

Automatic, Supervised, or Manual: Automatic

Programming language(s): vb.net

Source code available: Yes. I will update User:Qbugbot/source before the first test.

Links to relevant discussions (where appropriate): There have been some comments, requests, and edits over the past year that have motivated to do this, but I have not requested a consensus on ToL. I think it will be non-controversial.

Edit period(s): 8-24 hours per day.

Estimated number of pages affected: 17,000

Namespace(s): Mainspace

Exclusion compliant (Yes/No): Yes

Function details:

Qbugbot2 created around 18,000 pages about a year ago. I'd like to make corrections and updates to these pages. These changes are a result of comments and page edits. Edits made to these pages since they were created will be preserved. The first 100+ edits by this bot will be reviewed manually.

1. "Further reading" and "External link" references will be updated, and in most cases cut back or eliminated. Any references in Further reading and External links that were created with the page will be removed and replaced with the new references from the current qbugbot database. This will provide fewer and more specific references in these areas. Any reference added by other editors will be retained as is. References are matched by title, or by authors and year. This item will affect most pages, and has been the source of most negative comments about qbugbot articles.

2. If the prose, infobox, and inline refererences have not been edited since an article was created, it will be updated with the following changes:

  • Wording in the prose may be updated, usually for the distribution range or common names, sometimes to correct errors.
  • Inline references will be updated. Sometimes more specific references will be added, and sometimes non-specific references may be removed (such as EOL, some redundant database references, and some database references without specific data on the article.)
  • The database sources for lists of taxonomic children (species list, etc.) will be removed. While this information might be handy, it makes it difficult for people to update the list. When list is edited, the source database information tends to be omitted.
  • Occassionally, the taxonomic information and children will updated.

3. Photos will be added if they are available and not already on the page. This will affect a minority of pages. The Photos have been manually reviewed.

4. Unnecessary orphan and underlinked tags will be removed.

5. External link to Wikimedia commons will be updated to handle disambig links properly, without displaying the "(beetle)" in something like "Adelina (beetle)"

6. The formatting of many references has been improved, correcting errors, adding doi's, etc. These will be updated in most cases. If the references has been edited since creation, it will not be changed.

Here is an example of a page editing manually using bugbot 3 content: Muellerianella

Discussion

  • You say that this will edit around "17,000" pages, despite creating ~18,000 - why not edit the other 1,000? --DannyS712 (talk) 20:29, 29 March 2019 (UTC)
Some pages have been changed so much that the bot can't successfully revise them without altering other people's edits, something I'd rather not do automatically and something that's probably not necessary in pages with significant additions. Some other pages won't need any of these changes, either because the changes have already been made through manual edits, or because the original pages happened not to need them. I am just estimating the 1,000 pages. It could be more or less than that. Bob Webster (talk) 00:38, 30 March 2019 (UTC)
I looked at this and decided to postpone it for another update. The main problem is that I could see no easy way to determine what was described in 1956 (or any year) -- insects? moths? spiders? animals? beetles? North American millipedes? I was also considering narrowing down some of the categories (bees to sweat-bees, etc.) as some editors have been doing, but I haven't found a reliable list of categories to use. The same thing applies the -stub templates. I would prefer to do these three tasks in another bot session. Bob Webster (talk) 03:00, 31 March 2019 (UTC)
Having done some of this categorisation [caveat: not so much recently], I have to agree that this problem exists, and there are various schemes of parent categories that are in use if the category you are assigning needs to be created. One could put everything into a higher level category, to await sorting, but I see no great advantage. I would accept it as WP:WORKINPROGRESS. William Avery (talk) 08:56, 1 April 2019 (UTC)
That's correct. Bob Webster (talk) 22:02, 7 April 2019 (UTC)

  Approved for trial (50 edits). Since I fixed a crapton of those citations myself, I'm rather enthusiastic about qbugbot cleaning up after its own mess. Headbomb {t · c · p · b} 05:25, 9 April 2019 (UTC)

  •   Trial complete. 50 pages were updated, and are listed on the bot talk page. I found and fixed a couple of bugs. One prevented the introduction from being updated sometimes, and the other was a minor line spacing error. Bob Webster (talk) 23:04, 10 April 2019 (UTC)
{{BAG assistance needed}} Bob Webster (talk) 04:04, 17 April 2019 (UTC)
@Edibobb: what exactly is the criteria for removal/addition here? Headbomb {t · c · p · b} 05:54, 17 April 2019 (UTC)

Also, see...

Headbomb {t · c · p · b} 05:42, 17 April 2019 (UTC)

I've significantly reduced the number of references in further reading in new pages created by qbugbot. This was a manual, subjective process. The pages edited in qbugbot3 will have the original further reading references replaced with this new set. If a further reading reference has been added by an editor since page creation, it will be included in the edited page. The inline citations of qbugbot have also been updated. If the text of a page has not been edited, the original set of inline citations will be replaced.
I've corrected the references you listed, and fixed the problem of ending up with the same references in both inline citations and further reading.
Bob Webster (talk) 14:53, 17 April 2019 (UTC)
Also, EOL inline citations are removed even if the text has been edited. Bob Webster (talk) 14:56, 17 April 2019 (UTC)
@Edibobb: I think that given the number of articles/citations affected, it would be a good idea to have a sandbox version of all references that will be used. Then you (or I, if you don't know how) could run citation bot on them, and see what the improvements are, and those could get implemented, reducing the future cleanup load. Headbomb {t · c · p · b} 15:12, 17 April 2019 (UTC)
I think that would be good. I don't know how to run the citation bot, but I've copied all the citations to these sandbox pages. Can you run the bot on them? (A few of the citations are leftover and will never be used. It's easier to fix them all than sort them out, so don't worry if you see a few weird titles and dates.) Thanks!
Bob Webster (talk) 15:56, 17 April 2019 (UTC)
User:Citation bot/use explains the various methods. Right now the bot is blocked, so only the WP:Citation expander gadget works. I'll run the bot on these pages though. There's an annoying bug concerning italics and titles though, so just ignore that part of the diffs that will result. Headbomb {t · c · p · b} 16:01, 17 April 2019 (UTC)
@Edibobb: could you upload in batches of 250 citations? The bot chokes on pages so massive. Headbomb {t · c · p · b} 16:15, 17 April 2019 (UTC)
No problem, they're up now on User:Edibobb/sandbox/ref1 through User:Edibobb/sandbox/ref15 Bob Webster (talk) 17:36, 17 April 2019 (UTC)
@Edibobb: The bot still crashes. Could you do 100 per page? Headbomb {t · c · p · b} 19:58, 17 April 2019 (UTC)
@Headbomb: They're up now, 100 per page, User:Edibobb/sandbox/ref1 to User:Edibobb/sandbox/ref36 Bob Webster (talk) 23:09, 17 April 2019 (UTC)


Approved requests

Bots that have been approved for operations after a successful BRFA will be listed here for informational purposes. No other approval action is required for these bots. Recently approved requests can be found here (edit), while old requests can be found in the archives.


Denied requests

Bots that have been denied for operations will be listed here for informational purposes for at least 7 days before being archived. No other action is required for these bots. Older requests can be found in the Archive.

Expired/withdrawn requests

These requests have either expired, as information required by the operator was not provided, or been withdrawn. These tasks are not authorized to run, but such lack of authorization does not necessarily follow from a finding as to merit. A bot that, having been approved for testing, was not tested by an editor, or one for which the results of testing were not posted, for example, would appear here. Bot requests should not be placed here if there is an active discussion ongoing above. Operators whose requests have expired may reactivate their requests at any time. The following list shows recent requests (if any) that have expired, listed here for informational purposes for at least 7 days before being archived. Older requests can be found in the respective archives: Expired, Withdrawn.