 | All editors are encouraged to participate in the requests below – your comments are appreciated more than you may think! |
New to bots on Wikipedia? Read these primers!
- Approval process – How these discussions work
- Overview/Policy – What bots are/What they can (or can't) do
- Dictionary – Explains bot-related jargon
To run a bot on the English Wikipedia, you must first get it approved. Follow the instructions below to add a request. If you are not familiar with programming consider asking someone else to run a bot for you.
| Instructions for bot operators | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| Bot-related archives (v·t·e) |
|---|
| Bot Name | Status | Created | Last editor | Date/Time | Last BAG editor | Date/Time |
|---|---|---|---|---|---|---|
| KiranBOT 10 (T|C|B|F) | Open | 2024-09-07, 13:04:48 | Usernamekiran | 2024-09-08, 16:19:37 | Never edited by BAG | n/a |
| PonoRoboT 2 (T|C|B|F) | On hold | 2024-07-20, 23:38:17 | Primefac | 2024-08-04, 23:49:03 | Primefac | 2024-08-04, 23:49:03 |
| Platybot (T|C|B|F) | Open | 2024-07-08, 08:52:05 | Primefac | 2024-08-25, 20:09:43 | Primefac | 2024-08-25, 20:09:43 |
| Leaderbot (T|C|B|F) | Extended trial | 2024-08-10, 12:32:53 | Leaderboard | 2024-09-08, 11:47:11 | SD0001 | 2024-09-08, 10:35:46 |
| SodiumBot 2 (T|C|B|F) | In trial | 2024-07-16, 20:03:26 | Novem Linguae | 2024-08-08, 07:10:31 | Primefac | 2024-08-04, 23:51:27 |
| DannyS712 bot III 74 (T|C|B|F) | In trial | 2024-05-09, 00:02:12 | DannyS712 | 2024-07-21, 02:39:35 | TheSandDoctor | 2024-07-13, 22:20:18 |
| StradBot 2 (T|C|B|F) | In trial | 2024-02-17, 03:20:39 | SD0001 | 2024-02-17, 05:58:51 | SD0001 | 2024-02-17, 05:58:51 |
| CapsuleBot 2 (T|C|B|F) | Extended trial | 2023-06-14, 00:14:29 | Capsulecap | 2024-01-20, 02:36:30 | Primefac | 2024-01-15, 07:40:39 |
| AussieBot 1 (T|C|B|F) | Extended trial: User response needed! | 2023-03-22, 01:57:36 | Hawkeye7 | 2024-02-18, 23:33:13 | Primefac | 2024-02-18, 20:10:45 |
| DoggoBot 10 (T|C|B|F) | In trial | 2023-03-02, 02:55:00 | Osalbahr | 2024-09-09, 00:53:37 | Primefac | 2024-01-15, 07:40:49 |
| BaranBOT 4 (T|C|B|F) | Trial complete | 2024-09-07, 12:48:45 | DreamRimmer | 2024-09-07, 17:40:45 | ProcrastinatingReader | 2024-09-07, 15:23:28 |
| PrimeBOT 39 (T|C|B|F) | On hold | 2023-05-11, 12:48:50 | Primefac | 2024-08-16, 10:37:20 | Headbomb | 2023-07-02, 17:38:58 |
Current requests for approval
Operator: Usernamekiran (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 13:04, Saturday, September 7, 2024 (UTC)
Function overview: go through Category:Articles missing coordinates with coordinates on Wikidata, add the coordinates from wikidata to enwiki article, and remove the {{coord missing}} template
Automatic, Supervised, or Manual: automatic
Programming language(s): pywikibot
Source code available: not yet, soon on github, pywikibot script
Links to relevant discussions (where appropriate): requested at WP:BOTREQ, permalink
Edit period(s): once a month
Estimated number of pages affected: around 19,000 in the first run, then as they come in
Namespace(s): mainspace
Exclusion compliant (Yes/No): no
Function details: the bot goes through Category:Articles missing coordinates with coordinates on Wikidata, for each article: it reads the coordinates from the wikidata QID of that particular article. adds it to the infobox with | coordinates = parameter. If infobox is not present, then it adds to the bottom on the appropriate location, using {{coord}} template. If the coordinates are added successfully, then the bot removes {{coords_missing}} template. —usernamekiran (talk) 13:04, 7 September 2024 (UTC)
Discussion
- this seems to be borderline cosmetic bot, if that's the case would it be possible to run the bot with lower edit rates like one edit per minute, or 1edit/5minutes? —usernamekiran (talk) 16:19, 8 September 2024 (UTC)
Operator: Ponor (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 23:36, Saturday, July 20, 2024 (UTC)
Function overview: WP:MASSCREATE the remaining 3200 out of 6700 Croatian naseljes (settlements), which are the third level division of the country. The bot can create stubs like Dubrava, Split-Dalmatia County. Update the existing articles with ZIP codes (new official source), and historical population data graphs (where possible, under full supervision).
Automatic, Supervised, or Manual: Automatic creation. Supervised or manual updates.
Programming language(s): Python @ PAWS
Source code available: possible
Links to relevant discussions (where appropriate): Wikipedia talk:WikiProject Croatia/Archive 5#Croatian settlement articles mass creation
Edit period(s): one time run
Estimated number of pages affected: 3200 (+2500 or so)
Namespace(s): Articles
Exclusion compliant (Yes/No): irrelevant
Function details:
- Create some 3200 articles from the list Wikipedia:WikiProject Croatia/To Do List/Missing settlements, link them with Wikidata.
- Update existing Croatian settlement articles with ZIP codes and historical population data graphs, where possible (time permitting). The same job has been completed on hrwiki for all 6700 settlements.
Discussion
Needs wider discussion. The discussion you link was between you and only one other person. Please seek consensus at WP:Village pump (proposals) or a similar venue where we can be sure many people have seen it. Anomie⚔ 01:11, 21 July 2024 (UTC)
- Hm... Thanks, though I'm not sure I wanna go through anything like Wikipedia:Village pump (proposals)/Archive 207 again. I thought the 2000+ existing Croatian settlement stubs would prove the current consensus. A few hundred stubs created by the two users I mentioned in the linked WikiProject:Croatia discussion definitely contain less information than my bot can add, and were all kept. Let me ping @Joy to see if he can help push this through... somewhere. I don't have time for endless opinionated discussions myself, I'm afraid. Ponor (talk) 01:49, 21 July 2024 (UTC)
- You linked to a failed proposal to tighten the notability guideline, but it has little relevance to this proposal, because if all these new articles look like Dubrava, Split-Dalmatia County there's no way anyone's going to propose their deletion. These are not gas pumps masquerading as villages.
- Even if we wanted to upmerge that information into list articles, those historical population graphs would just seem to be unwieldy, it would be pointless shoehorning.
- @Primefac had previously allowed Wikipedia:Bots/Requests for approval/PonoRoboT and I don't remember seeing any problems, it seemed to be a nice, straightforward improvement to the encyclopedia.
- @Anomie, is there a real difference here? IOW why would this change to these 3k settlement articles need more discussion when the previous change to analogous 3k settlement articles didn't?
- The fact that one group of 3k Croatian places has articles while another group of them doesn't is a historical fluke. If we need a discussion on making this situation consistent, the previously existing group needs to be discussed as well. But we already know they all qualify under WP:5P1 etc, so I don't quite see why this would be frowned upon according to standard processes (WP:BOLD, WP:NOTBURO). --Joy (talk) 06:32, 21 July 2024 (UTC)
- I was only reminding everyone what our notability discussions end up looking like. Since there were recent MEAT creations of these stubs, I'm thinking creating them by hand would be a waste of anyone's precious time if I can do the same thing, or better, by my bot.
- I see that, for example, Serbia has all of their 3rd level two-sentence geo stubs created since 2010 or so. That says WP:EDITCON is there, no? Ponor (talk) 10:01, 21 July 2024 (UTC)
- The real difference between Wikipedia:Bots/Requests for approval/PonoRoboT and this is that this is about creations, and the community has for many years now wanted to vet bot creations of articles before they happen. And that's regardless of whether the proposed creations would pass WP:N (part of it is that the community wants independent evaluation of that before the creations happen) or whether other articles on the topic or related topics already exist.If you want to refer to policy, WP:MASSCREATION says (emphasis added)
It is also strongly encouraged (and may be required by BAG) that community input be solicited at WP:Village pump (proposals) and the talk pages of any relevant WikiProjects.
Unless you can get another BAGger to proceed without, this is me requiring. Anomie⚔ 11:17, 21 July 2024 (UTC)- I concur with Anomie on this one; we have an editor who, while other factors were involved, wanted to do a similar thing for 300 pages and is restricted to only making one per month. Creating ten times as many one-paragraph sub-stubs in a fraction of the time will need consensus. Yes, they aren't just gas stations, but other than "Town X has a population Y" there appears to be no more information readily available, so I would like to see a reasonable consensus to create these (and not just two editors agreeing it would be a good idea). As Anomie said, your first approved task was updating information, not creating new pages. Primefac (talk) 12:07, 21 July 2024 (UTC)
- It's a clerical difference, it's just because some editor mass-created tens of thousands of these two decades ago and happened to miss half of the Croatian settlements. But okay, let's go through the motions, I'll file a proposal when I have the time (and if no one beats me to it). --Joy (talk) 18:57, 21 July 2024 (UTC)
- @Ponor the best way to substantiate this proposal would be to make sure we show some external references on e.g. the Bureau of Statistics doing proper work (documenting existing human habitation as opposed to something weird), and illustrate the body of scholarly and other work out there on the topic of these settlements. If you have something to this effect already, please share. --Joy (talk) 19:05, 21 July 2024 (UTC)
- Sure, I'll help with everything I know, but can't take the burden of convincing everyone on the project alone atm. I'd start with the first four refs in Dubrava, Split-Dalmatia County: there are laws, one agency takes care of the division(s), the bureau uses their data. Every town and municipality have their web page listing these settlements. Most settlements have a church, school, etc. Let's continue at WikiProject Croatia, huh? Ponor (talk) 19:20, 21 July 2024 (UTC)
- @Ponor the best way to substantiate this proposal would be to make sure we show some external references on e.g. the Bureau of Statistics doing proper work (documenting existing human habitation as opposed to something weird), and illustrate the body of scholarly and other work out there on the topic of these settlements. If you have something to this effect already, please share. --Joy (talk) 19:05, 21 July 2024 (UTC)
- It's a clerical difference, it's just because some editor mass-created tens of thousands of these two decades ago and happened to miss half of the Croatian settlements. But okay, let's go through the motions, I'll file a proposal when I have the time (and if no one beats me to it). --Joy (talk) 18:57, 21 July 2024 (UTC)
- I concur with Anomie on this one; we have an editor who, while other factors were involved, wanted to do a similar thing for 300 pages and is restricted to only making one per month. Creating ten times as many one-paragraph sub-stubs in a fraction of the time will need consensus. Yes, they aren't just gas stations, but other than "Town X has a population Y" there appears to be no more information readily available, so I would like to see a reasonable consensus to create these (and not just two editors agreeing it would be a good idea). As Anomie said, your first approved task was updating information, not creating new pages. Primefac (talk) 12:07, 21 July 2024 (UTC)
- The real difference between Wikipedia:Bots/Requests for approval/PonoRoboT and this is that this is about creations, and the community has for many years now wanted to vet bot creations of articles before they happen. And that's regardless of whether the proposed creations would pass WP:N (part of it is that the community wants independent evaluation of that before the creations happen) or whether other articles on the topic or related topics already exist.If you want to refer to policy, WP:MASSCREATION says (emphasis added)
- I'd oppose the bot creating any more pages until Module:Croatian population data graph is translated into English and more pages become uneditable by editors unfamiliar with the language. Gonnym (talk) 11:00, 4 August 2024 (UTC)
On hold. Please feel free to disable the {{BotOnHold}} template when consensus about the appropriateness of this task has been demonstrated. Primefac (talk) 23:48, 4 August 2024 (UTC)
Operator: BilledMammal (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 08:51, Monday, July 8, 2024 (UTC)
Function overview: Adjusts templates based on provided JSON configuration files. This request is limited to Template:Cite news and Template:Cite web, and is primarily intended to correct issues where the work or publisher is linked to the wrong target.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python
Source code available: Not currently
Links to relevant discussions (where appropriate):
Edit period(s): Initially, irregular one-off runs, with each held after significant expansions to the configuration file. Once most citations have been fixed I will open a request for continuous operation in a maintenance mode.
Estimated number of pages affected: Varies considerably based on configuration. This configuration, which applies to ten sources, will edit approximately 23,000. This configuration, which goes beyond correcting wrong links and also always inserts the correct link when one is missing, will edit approximately 450,000.
Namespace(s): Mainspace
Exclusion compliant (Yes/No): Yes
Function details: Adjusts parameters of Cite news and Cite web based on a configuration file. This configuration can be applied to any parameter, but the intent of this request is to apply it to the following:
- work
- publisher
- publication-place
- department
- agency
- url-access
It determines which change to apply based on current parameter field values. Any field or combination of fields can be used, but the intent of this request is to use the "url" field.
Adjustments can be specified as "always", "onEdit", or "never". When "always" is specified, if a change is identified as being desired for a parameter the article will be edited to implement it. When "onEdit" is specified, desirable changes are only implemented if we are already editing the page. This reduces the impact on watchlists by skipping articles that don't have high priority issues.
Configuration schema
|
|---|
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "array",
"items": {
"type": "object",
"properties": {
"includes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string",
"example": "url"
},
"value": {
"type": "array",
"items": {
"type": "string",
"example": ["www.bbc.com", "www.bbc.co.uk"]
}
}
}
},
"description": "Lists conditions required to be met for this configuration to be applied to the template."
},
"excludes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string",
"example": "url"
},
"value": {
"type": "array",
"items": {
"type": "string",
"example": ["www.bbc.com/sport", "www.bbc.co.uk/sport"]
}
}
},
"description": "Lists conditions that must not be met for this configuration to be applied to the template."
}
},
"patternProperties": {
"^[a-zA-Z0-9-]+$": {
"oneOf": [
{
"type": "array",
"description": "Named for the parameter, and defines what will be done with it. Used when there are multiple possible configurations for the parameter.",
"items": {
"$ref": "#/definitions/parameter-config"
}
},
{
"type": "object",
"description": "Named for the parameter, and defines what will be done with it. Used when there is only one possible configuration for the parameter.",
"$ref": "#/definitions/parameter-config"
}
]
}
}
},
"definitions": {
"parameter-config": {
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "parameter-config",
"type": "object",
"properties": {
"includes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string",
"example": ["url"]
},
"value": {
"type": "array",
"items": {
"type": "string",
"example": ["www.bbc.com", "www.bbc.co.uk"]
}
}
}
},
"description": "Lists conditions required to be met for this configuration to be applied to the parameter."
},
"excludes": {
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string",
"example": ["url"]
},
"value": {
"type": "array",
"items": {
"type": "string",
"example": ["www.bbc.com/sport", "www.bbc.co.uk/sport"]
}
}
}
},
"description": "Lists conditions that must not be met for this configuration to be applied to the parameter."
},
"link": {
"type": "string",
"description": "Where the parameter should normally link to",
"example": ["ABC News (Australia)"]
},
"wikitext": {
"type": "string",
"description": "What the wikitext of the parameter should normally be",
"example": ["ABC News"]
},
"blacklist": {
"type": "array",
"items": {
"type": "string",
"example": ["ABC News (United States)", "ABC News"]
},
"description": "Links that will always be removed"
},
"greylist": {
"type": "array",
"items": {
"type": "string",
"example": ["Australian Broadcasting Corporation"]
},
"description": "Links that will only be removed when already editing the page. Used to prevent edits that would only fix issues we consider minor."
},
"whitelist": {
"type": "array",
"items": {
"type": "string",
"example": ["The Sunday Telegraph (Sydney)"]
},
"description": "Links that will never be removed. Used when we believe editors may have deliberately provided a non-standard value that we wish to respect."
},
"fixRedirects": {
"type": "string",
"enum": ["always", "onEdit", "never"],
"default": "onEdit",
"description": "Specifies when we will replace redirects to the provided link with the provided link."
},
"fixDisplay": {
"type": "string",
"enum": ["always", "onEdit", "never"],
"default": "onEdit",
"description": "Specifies when we will replace the currently displayed text with the displayed version of the provided Wikitext."
},
"fixOthers": {
"type": "string",
"enum": ["always", "onEdit", "never"],
"default": "always",
"description": "Specifies when we will replace links to pages that are neither redirects to the link nor on the provided lists."
},
"fixMissing": {
"type": "string",
"enum": ["always", "onEdit", "never"],
"default": "onEdit",
"description": "Specifies when we will add a missing value"
},
"priority": {
"type": "integer",
"default": 5,
"description": "Provides a tie-breaker when multiple array objects meet the inclusion or exclusion criteria. Higher value is preferred. It is unspecified which configuration object is used when both have the same priority level.",
"minimum": 1
}
}
}
}
}
}
|
What it does to these parameters depends on the configuration. For example:
"work":
{
"link": "ABC News (Australia)",
"wikitext": "ABC News",
"blacklist": ["ABC News (United States)", "ABC News"],
"greylist": ["Australian Broadcasting Corporation"],
"fixMissing": "onEdit",
"fixRedirects": "onEdit",
"fixOthers": "always"
}
Will ensure that the "work" parameter only links to ABC News (Australia). When it finds a link to a source other than ABC News (Australia), its redirects, or Australian Broadcasting Corporation, it will edit the article to correct that link.
When it encounters a redirect, or Australian Broadcasting Corporation, or a missing value, it will only correct those if it is already editing the article.
If we change "fixMissing" to "always", it would edit the article to insert the value.
"agency":
{
"includes":
[
{
"key": "agency",
"value": ["Reuters"]
}
],
"remove": "onEdit"
}
Will remove the agency field when it contains "Reuters". This is used to correct when the field has been incorrectly filled with the name of the publisher or work.
"department":
[
{
"includes":
[
{
"key": "url",
"value": ["reuters.com/world/"]
}
],
"wikitext": "World"
},
{
"includes":
[
{
"key": "url",
"value": ["reuters.com/world/reuters-next/"]
}
],
"wikitext": "Reuters Next",
"priority": 6
},
{
"includes":
[
{
"key": "url",
"value": ["reuters.com/business/"]
}
],
"wikitext": "Business"
}
]
This fills in the department field based on the source url. If none of these are met then the department field is not filled.
The current configuration file will do the following:
- ABC News (Australia)
- Set "work" to ABC News
- Set "publisher" to Australian Broadcasting Corporation
- Remove "publication-place"
- Remove "agency" when incorrect
- The Daily Telegraph
- Set "work" to The Daily Telegraph
- Set "publisher" to Telegraph Media Group
- Set "publication-place" to "London, United Kingdom"
- Set "department" when it can be determined
- Reuters
- Set "work" to Reuters
- Set "publisher" to Thomson Reuters
- Set "publication-place" to "London, United Kingdom"
- Set "department" when it can be determined
- Remove "agency" when incorrect
- The New York Times
- Set "work" to The New York Times
- Set "url-access" to "limited"
- Remove "publisher"
- Remove "publication-place"
- BBC News
- Set "work" to BBC News
- Remove "publisher"
- Remove "publication-place"
- Set "department" when it can be determined
- BBC Sport
- Set "work" to BBC Sport
- Remove "publisher"
- Remove "publication-place"
- The Guardian
- Set "work" to The Guardian
- Remove "publisher"
- Set "publication-place" to "London, United Kingdom"
- Set "department" when it can be determined
- The Guardian (Swan Hill)
- Set "work" to The Guardian
- The Daily Telegraph (Sydney)
- Set "work" to The Daily Telegraph
- Set "publisher" to News Corp Australia
- Remove "publication-place"
- ABC News (United States)
- Set "work" to ABC News
- Set "publisher" to American Broadcasting Company
- Remove "publication-place"
The intent is that the community will expand the configuration file, increasing the number of citations it can fix.
Example of template replacements
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
When editing a template, to improve readability it will also apply a consistent format and naming convention. This involves converting parameters away from aliases to their primary values, and placing the parameters into the following order:
Order
|
|---|
|
Discussion
- I'd prefer if this bot (and every bot) stopped short of reordering template parameters. Doing a full reorganisation on any template edited will make it much more difficult to tell what changes have been made when reviewing diffs. Folly Mox (talk) 09:23, 16 July 2024 (UTC)
- We can trust our bots that much, I'd say. And it shouldn't be much of a problem if you compare the diffs in visual diff mode, try here. In my experience, it's much easier for a bot (program) to reassemble a template in some predefined order. Having data in the order of final appearance does help with readability (BilledMammal: that'd be url?, author(s) data, date, title…).Ponor (talk) 06:48, 18 July 2024 (UTC)
- @Ponor: Currently, author(s) data, date, title, url - the full order can be seen in the final collapsed box. However, that is easy to change.
- It wouldn't be difficult to put it back in the original order (although it would result in new fields being dumped at the end), but personally I believe it is better to reorganize it, as while it makes it harder for editors using non-visual viewer to identify the changes, it easier for editors to parse the template going forward. BilledMammal (talk) 23:05, 18 July 2024 (UTC)
- I support putting the params in some canonical order, my only question is which one it should be. VisualEditor (TemplateData), IAbot, maybe even reFill, probaly use the same one ("Full parameter set in horizontal format" from {{Cite web}}?), which is what I'd use as well. Up to you, though. Ponor (talk) 14:05, 19 July 2024 (UTC)
- I started with the full parameter set from Template:Cite news, but quickly found that "full parameter set" doesn’t actually mean "full parameter set".
- I see the two templates differ in where to put the URL; I think Cite news' method is better, as the URL is difficult to read so better to put that at the end. BilledMammal (talk) 14:11, 19 July 2024 (UTC)
- The order is probably from the order used by TemplateData as that is where ProveIt takes its order from. Gonnym (talk) 11:07, 4 August 2024 (UTC)
- I support putting the params in some canonical order, my only question is which one it should be. VisualEditor (TemplateData), IAbot, maybe even reFill, probaly use the same one ("Full parameter set in horizontal format" from {{Cite web}}?), which is what I'd use as well. Up to you, though. Ponor (talk) 14:05, 19 July 2024 (UTC)
- We can trust our bots that much, I'd say. And it shouldn't be much of a problem if you compare the diffs in visual diff mode, try here. In my experience, it's much easier for a bot (program) to reassemble a template in some predefined order. Having data in the order of final appearance does help with readability (BilledMammal: that'd be url?, author(s) data, date, title…).Ponor (talk) 06:48, 18 July 2024 (UTC)
- I think consensus would need to be established for this at other venues. The part of the proposal regarding adding links where none exist has the potential to conflict with WP:WHENINROME. voorts (talk/contributions) 21:18, 16 August 2024 (UTC)
- That aspect doesn’t need to be enabled; exactly how this functions depends entirely on the configuration file.
- However, that aspect isn’t covered by WP:WHENINROME, which says
If all or most of the citations in an article consist of bare URLs, or otherwise fail to provide needed bibliographic data – such as the name of the source, the title of the article or web page consulted, the author (if known), the publication date (if known), and the page numbers (where relevant) – then that would not count as a "consistent citation style" and can be changed freely to insert such data.
- Emphasis mine. BilledMammal (talk) 18:24, 17 August 2024 (UTC)
- I was referring to the part of WHENINROME that states:
Editors should not attempt to change an article's established citation style, merely on the grounds of personal preference or to make it match other articles, without first seeking consensus for the change.
For example, if an article has proper citation formatting, but none of the publication titles are wikilinked, or only the first instance is, running this bot to add wikilinks to each publication parameter would run afoul of WHENINROME. In any event, given that we have a reasonable disagreement on this point, I think consensus would be needed to implement that part of the bot. voorts (talk/contributions) 18:28, 17 August 2024 (UTC)- Ah, I misunderstood. The configuration file can be updated to not replace unlinked, but otherwise correct, source names, if such behaviour is desirable.
- With that said, I’m not sure whether the decision to Wikilink or not falls under WP:WHENINROME, as such a decision appears to go beyond referencing style and instead fall under MOS:LINK, specifically MOS:UL, which says
Proper names that are likely to be unfamiliar to readers
- which would include virtually all source names, as few have worldwide recognition - should be linked. BilledMammal (talk) 18:48, 17 August 2024 (UTC)- I broadly construe WHENINROME to avoid referencing conflicts since the MOS is a contentious topic. voorts (talk/contributions) 19:04, 17 August 2024 (UTC)
- I don't necessarily have an issue with the rest of what the bot would do. Also, I would like to see a process for establishing consensus for what parameters should be included for each ref. For example, why doesn't The Guardian (Swan Hill) have a publication-place parameter? Why use publisher instead of publication-place for The Daily Telegraph(s)? These are things that might need to be worked out. voorts (talk/contributions) 18:31, 17 August 2024 (UTC)
- The omissions for Swan Hill Guardian are primarily because I wanted an example of a minimally completed source, to demonstrate the tools range.
- (The Daily Telegraph actually uses both)
- The process I was planning was standard WP:CONSENSUS, with the requirement that consensus be obtained prior to changing the primary configuration file. Or do you think something more involved is needed? BilledMammal (talk) 18:48, 17 August 2024 (UTC)
- I was referring to the part of WHENINROME that states:
I think even a rough consensus would be fine for the contents of the configuration file. I'd like to see it advertised at Wikipedia talk:Citing sources, Wikipedia talk:Manual of Style, and potentially other venues before this bot goes active. voorts (talk/contributions) 18:58, 17 August 2024 (UTC)
- Good idea; I think WP:VPR would also be a good location, although I’ll wait till BAG gives preliminary approval before taking it to the wider community. BilledMammal (talk) 19:01, 17 August 2024 (UTC)
- Apologies, have been meaning to tag this with
Needs wider discussion. but have had other things to deal with; I would like to see a rough consensus that this is a desired bot task. Primefac (talk) 12:02, 22 August 2024 (UTC)
- I've opened a discussion at the Village Pump. BilledMammal (talk) 09:03, 25 August 2024 (UTC) Link expanded to include section, no other change made. Primefac (talk) 20:09, 25 August 2024 (UTC)
- Apologies, have been meaning to tag this with
Bots in a trial period
Operator: Leaderboard (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 12:32, Saturday, August 10, 2024 (UTC)
Function overview: phab:T370842 - I want to see if this is something English Wikipedia wants for their local rights. I could not find evidence of this already being done or discussion about this on any other bot.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python
Source code available: https://github.com/Leader-board/userrights-reminder-bot, though this is under development
Links to relevant discussions (where appropriate): Wikipedia:Administrators'_noticeboard/Archive364#Bot_to_inform_temp_users_of_expiry I do not believe that this is required, but should it be considered necessary, I can file one explicitly.
Edit period(s): Daily.
Estimated number of pages affected: 2-3 per day approximately.
Namespace(s): User talk only.
Exclusion compliant (Yes/No): No, as it is not applicable. However, a mechanism to allow users to exclude the bot from running on their talk page is expected to be provided before the bot is formally run. This is otherwise opt-out.
Function details: As explained above. For users whose temporary rights are expected to expire in a week, the bot will simply remind the user on their talk page that their right will expire within that time. That's it - while I eventually expect this to run on multiple wikis, this request pertains only en.wikipedia. This request will not require the bot flag. Please ping me when needed.
Discussion
{{BotOnHold}} You do not have a working bot, you do not have consensus for this task, and you do not seem to understand that all bots need a bot flag. If you can come around to those three things, then re-open this task and we'll discuss whether it is feasible. Primefac (talk) 13:09, 10 August 2024 (UTC)
- @Primefac:, I was under the impression that the rules said that "Bot accounts will be marked by a bureaucrat as being in the "bot" user group upon BAG request", which implied that it was optional. Did I mis-read the rules? Regarding point 2: should I be doing it at Village Pump (Proposals) - I believed that my bot was not "controversial" enough but no issues taking the consensus route if needed? Regarding point 1: I'm requesting permission in advance, and did not know that was in error. Leaderboard (talk) 15:46, 10 August 2024 (UTC)
- I think it's fine to get some kind of indication a task will be approved before doing the development effort.
- I'd suggest asking in some community venue to see if people want this task, though. I'd probably opt for WP:VPP or WP:AN (posting at either and cross-notifying the other) ProcrastinatingReader (talk) 02:36, 15 August 2024 (UTC)
- Thanks, I'll do that. Leaderboard (talk) 14:21, 15 August 2024 (UTC)
- Many of our rights assignments are temporary on purpose and that is communicated during request/granting, so "reminding" someone of this seems like it could be more annoying then anything else. Specifically
confirmedandevent coordinatorare almost always granted for a fixed term. Especially confirmed, as it is often granted for 1-10 days for event attendees. As such, these groups probably shouldn't be "reminded". Remindingbotis fairly useless, and potentiallyIPBEas well (another group that is often granted for a fixed term). — xaosflux Talk 15:42, 15 August 2024 (UTC)- @Xaosflux: I thought IPBE was something where reminding was useful - what about the temp rights often granted at WP:PERM? Another option if the community prefers it that way is to make this opt-in instead of opt-out for this wiki. Leaderboard (talk) 16:23, 15 August 2024 (UTC)
- I'm not super sure on that one, could be useful. Perhaps an additional "don't notify someone that has been inactive for xxx" (like 3 months maybe)? Most of the other temp grants we do at PERM are "granted for a trial, come back and renew" - so those could be useful. — xaosflux Talk 16:25, 15 August 2024 (UTC)
- @Xaosflux: I thought IPBE was something where reminding was useful - what about the temp rights often granted at WP:PERM? Another option if the community prefers it that way is to make this opt-in instead of opt-out for this wiki. Leaderboard (talk) 16:23, 15 August 2024 (UTC)
@Primefac and Xaosflux: the bot is ready for en.wiki testing: meta:Global reminder bot. The consensus seems to be mostly positive (at WP:AN), with one concern about IPBE that I'm not sure how to interpret (this is assuming AN discussions do not need to be closed - I'm not sure). A test edit is testwiki:User_talk:Leaderbot_demo. Leaderboard (talk) 09:14, 22 August 2024 (UTC)
- What is your format for multiple entries in "always_excluded_local" ? (e.g. "x","y" ; "x,y" ; etc) ? Please create a local (or at least a global) userpage for this bot account, where such documentation could be linked. — xaosflux Talk 09:45, 22 August 2024 (UTC)
- Are local and global config entries merged, or overwritten? — xaosflux Talk 09:46, 22 August 2024 (UTC)
- Hi @Xaosflux:,
- the global userpage does link to the Meta-Wiki documentation page? You should be able to see it by forcibly creating a local account for Leaderbot.
- It's a JSON array, so currently it has
["confirmed"]in it. To add entries, just update the array, so for example,["confirmed", "bot"] - "Are local and global config entries merged, or overwritten" - I don't understand what you mean. For exclusion purposes, they are merged. For message purposes, it's local, with global used only if local does not exist.
- Leaderboard (talk) 10:09, 22 August 2024 (UTC)
- @Leaderboard ok it seems to be because that account is not present on this project (Special:CentralAuth/Leaderbot) - would you attach it please? — xaosflux Talk 12:30, 22 August 2024 (UTC)
- Thanks, so yes if global exclusion is "confirmed" and local is "bot" - then locally the exclusion is to confirmed, bot - correct? (Similarly, local can not un-exclude something in global). — xaosflux Talk 12:32, 22 August 2024 (UTC)
- @Xaosflux: Done, and yes to both. Leaderboard (talk) 12:48, 22 August 2024 (UTC)
- @Primefac: just want to check with you on whether I can "re-open" this task by formally disabling the BotOnHold template (you said to do that when all three things have been done, which I think is now the case but could be wrong). Leaderboard (talk) 13:49, 24 August 2024 (UTC)
- If you feel that you have what you need, then by all means go for it. I know it feels like a snarky answer, but it's more because I have not had (or taken) the time to do an evaluation of the situation, so I'll leave that to your discretion. Primefac (talk) 20:07, 25 August 2024 (UTC)
- Please link the AN discussion above under "Links to relevant discussions". – SD0001 (talk) 07:22, 1 September 2024 (UTC)
{{BAG assistance needed}} If this was premature, I apologise. Leaderboard (talk) 05:32, 31 August 2024 (UTC)
- Sounds useful. Editors are often confused why they can no longer patrol pages and such, not realizing their temporary access has expired. I don't think this really requires a community discussion, as long as opt-out options are clearly available. Would suggest not reminding if the original access was very short (< 2 weeks?) as then the user is likely to remember it as Xaosflux mentions.
Approved for trial (2 weeks or 10 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. – SD0001 (talk) 12:24, 31 August 2024 (UTC)
- As for the code, I'd suggest using a bot framework like mwclient or pywikibot for simplicity and so that error cases are handled. – SD0001 (talk) 12:25, 31 August 2024 (UTC)
Trial complete. Special:Contributions/Leaderbot @SD0001: Three things: (i) the bot had to be run a couple of times since it hit ratelimit a few times, and (ii) some accounts for which the bot sent messages didn't contribute at all (but indeed had IPBE) - I don't think there's an issue with that in my opinion, and (iii) all 10 messages it sent were for IPBE, as the 10 edits limit was hit before it could go to the users with other rights. (The reason it made these many edits in one day is because as the bot was never run before, it also captured users whose rights were expiring the next day, for instance) Leaderboard (talk) 13:18, 31 August 2024 (UTC)
- The language of the message could use some work.
- Hi, As part of Global reminder bot, this is an automated reminder –> Hi, this is an automated reminder
- to let you know that your WP:IPBE right will expire on 2024-09-06 11:56:03, which gave you the right to bypass IP-address blocks –> to let you know that your WP:IPBE right which gave you the ability to bypass IP address blocks will expire on 11:56, 6 September 2024 (UTC) It's good to match the signature timestamp format so that it'll be converted to user's time zone if they have the gadget enabled.
- At the end, consider adding To opt out of user right expiry notifications, add yourself to m:Global reminder bot/Exclusion.
- – SD0001 (talk) 20:03, 31 August 2024 (UTC)
- @SD0001: First and third one done (feel free to improve the message at metawiki:Global_reminder_bot/enwiki - the bot directly pulls the message from that page). The second one I will need to look further, since this format (i.e, $3 on the above page) is common for all wikis and would rather consider that for the future if possible. P.S: it's likely the "Global reminder bot" subpages on metawiki will be protected soon using an abuse filter - noting if you're concerned about unauthorised modification. Leaderboard (talk) 04:37, 1 September 2024 (UTC)
- $3 can be replaced with a wiki-specific date format. – SD0001 (talk) 07:20, 1 September 2024 (UTC)
- @SD0001 This is something I can look into for the future (and wonder if there's an easy way to do this?), but for now I would prefer retaining the current date/time style if that is something you're OK with. Leaderboard (talk) 07:35, 1 September 2024 (UTC)
- Easy way would be to include the date format accepted by python strftime in the per-wiki configuation, eg. for enwiki it would be
%H:%M, %-d %B %Y (UTC). Then while posting, substitute $3 with the formatted timestamp. – SD0001 (talk) 08:01, 1 September 2024 (UTC)- @SD0001: Got it; can the bot be approved before that? Another reason I'm inclined to delay this one for now is that I'm working on getting the bot approved on other wikis, and want to see if other wikis prefer a different date/time format. This will help when developing (for instance, in case I need to do something similar for another language). Leaderboard (talk) 11:17, 1 September 2024 (UTC)
- Easy way would be to include the date format accepted by python strftime in the per-wiki configuation, eg. for enwiki it would be
- @SD0001 This is something I can look into for the future (and wonder if there's an easy way to do this?), but for now I would prefer retaining the current date/time style if that is something you're OK with. Leaderboard (talk) 07:35, 1 September 2024 (UTC)
- $3 can be replaced with a wiki-specific date format. – SD0001 (talk) 07:20, 1 September 2024 (UTC)
- @SD0001: First and third one done (feel free to improve the message at metawiki:Global_reminder_bot/enwiki - the bot directly pulls the message from that page). The second one I will need to look further, since this format (i.e, $3 on the above page) is common for all wikis and would rather consider that for the future if possible. P.S: it's likely the "Global reminder bot" subpages on metawiki will be protected soon using an abuse filter - noting if you're concerned about unauthorised modification. Leaderboard (talk) 04:37, 1 September 2024 (UTC)
- The language of the message could use some work.
- As for the code, I'd suggest using a bot framework like mwclient or pywikibot for simplicity and so that error cases are handled. – SD0001 (talk) 12:25, 31 August 2024 (UTC)
Approved for extended trial (1 month). Please provide a link to the relevant contributions and/or diffs when the trial is complete. As the first trial only covered a single user group. Please use localised name of groups (eg. page mover) instead of the technical names (eg. extendedmover). The header ("Notice of expiration of ...") makes it sound like it already expired. "Upcoming expiry of ..." would sound more correct. And make the bot talk page not be a red link. – SD0001 (talk) 10:35, 8 September 2024 (UTC)
- @SD0001, regarding the usage of localised names, is User_talk:CharlieMehta#Upcoming_expiry_of_your_patroller_right OK, or would you prefer using only the localised name where applicable? Just want to check if I need to change something. Leaderboard (talk) 11:47, 8 September 2024 (UTC)
Operator: Sohom Datta (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 20:03, Tuesday, July 16, 2024 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available: https://github.com/sohomdatta1/npp-notifier-bot
Function overview: Notify previous reviewers of a article at AFD about the nomination
Links to relevant discussions (where appropriate): Initial discussions on NPP Discord + previous BRFAs surrounding AFD notifications
Edit period(s): Continuous
Estimated number of pages affected: 1-2 per day (guessimate?)
Exclusion compliant (Yes/No): Yes
Already has a bot flag (Yes/No): No, on enwiki, yes, for other wikis on other tasks
Function details:
- Use the eventstream API to listen for new AfDs
- Extract page name by parsing the AfD wikitext
- Identify previous reviewers of page at AFD
- Notify said reviewers on their talk pages with a customised version of the existing AfD notification message
Discussion
- I like this concept in general. I tried to make a user script that does this (User:Novem Linguae/Scripts/WatchlistAFD.js#L-89--L-105), but it doesn't work (I probably need to rewrite it to use MutationObserver). Would this bot be automatic for everyone, or opt in? Opt in may be better and easier to move forward in a BRFA. If not opt in, may want to start a poll somewhere to make sure there's some support for "on by default". –Novem Linguae (talk) 07:58, 17 July 2024 (UTC)
- I think it would be better to be on by default with the option for reviewers to disable. (t · c) buidhe 14:28, 17 July 2024 (UTC)
- Ah yes. "Opt out" might be a good way to describe this third option. –Novem Linguae (talk) 22:13, 17 July 2024 (UTC)
- I think it would be better to be on by default with the option for reviewers to disable. (t · c) buidhe 14:28, 17 July 2024 (UTC)
- Support - seems like a good idea. I've reviewed several articles that I've tagged for notability or other concerns, only to just happen to notice them by chance a few days later get AfD'ed by someone else. A bot seems like a good idea, and I can't see a downside. BastunĖġáḍβáś₮ŭŃ! 16:31, 17 July 2024 (UTC)
- This is the sort of thing that would be really good for some people (e.g., new/infrequent reviewers) and really frustrating for others (e.g., people who have reviewed tens of thousands of articles). If it does end up being opt-out, each message needs to have very clear instructions on how to opt out. It would also be worth thinking about a time limit: most people aren't going to get any value out of hearing about an article they reviewed a decade ago. Maybe a year or two would be a good threshold. Extraordinary Writ (talk) 18:48, 17 July 2024 (UTC)
- The PREVIOUS_NOTIF regex should also account for notifications left via page curation tool ("Deletion discussion about xxx"). The notification also needs to be skipped if the previous reviewer themself is nominating. In addition, I would suggest adding a delay of at least several minutes instead of acting immediately on AfD creation – as it can lead to race conditions where Twinkle/PageTriage and this bot simultaneously deliver notifications to the same user. – SD0001 (talk) 13:41, 19 July 2024 (UTC)
- {{Operator assistance needed}} Thoughts on the above comments/suggestions? Also, do you have the notice ready to go or is that still in the works? If it's ready, please link to it (or copy it here if it's hard-coded elsewhere). Primefac (talk) 12:48, 21 July 2024 (UTC)
- @Primefac I've implemented a few of the suggestions, I've reworked the code to exclude pages containing
{{User:SodiumBot/NoNPPDelivery}}, which should serve as a opt out mechanism :) I've also reworked the code to include SD0001's suggestion of adding a significant delay by making the bot wait at least a hour and also added modified the regex to account for the messages sent by PageTriage. - Wrt to Extraordinary Writ's suggestions, I have restricted the lookup to the last 3 years as well and created a draft User:SodiumBot/ReviewerAfdNotification which has instructions on how to opt out. Sohom (talk) 16:02, 21 July 2024 (UTC)
- Thanks, I'll leave this open for a few days for comment before going to trial. Primefac (talk) 16:07, 21 July 2024 (UTC)
- Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Please make sure this BRFA is linked in the edit summary. Primefac (talk) 23:50, 4 August 2024 (UTC)
- Thanks, I'll leave this open for a few days for comment before going to trial. Primefac (talk) 16:07, 21 July 2024 (UTC)
- @Primefac I've implemented a few of the suggestions, I've reworked the code to exclude pages containing
- I ran across Wikipedia:Bots/Requests for approval/SDZeroBot 6 today, which is a very similar task, and uses an "opt out" strategy. This suggests that the community may be OK with having AFD notifications be on by default for a bot task like this. –Novem Linguae (talk) 07:10, 8 August 2024 (UTC)
Operator: DannyS712 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 00:02, Thursday, May 9, 2024 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): JavaScript
Source code available: TBD
Function overview: Automatically mark redirects created by Wikipedia:Page movers as part of a page move as "patrolled" in the new page patrol / page curation system
Links to relevant discussions (where appropriate): Wikipedia talk:New pages patrol/Reviewers/Archive 51#Idea to reduce redirect backlog
Edit period(s): Continuous
Estimated number of pages affected: Lots
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): Yes
Function details: The code will be added to my current redirect patrolling bot rules (see User:DannyS712 bot III/rules for the current rules) once I write it. You can see the implementation I intend to use is to patrol all redirects based on the query below.
If possible, I'd like to request speedy approval and/or a time-based trial, so that I don't need to add a whole bunch of logic to the bot to count how many redirects have already been patrolled in the trial.
Query to run
|
|---|
SELECT page_id AS 'pageid', page_title AS 'title', ptrpt_value AS 'target', actor_name AS 'creator' FROM page JOIN pagetriage_page ON page_id = ptrp_page_id JOIN pagetriage_page_tags ON ptrp_page_id = ptrpt_page_id JOIN revision rv ON page_latest = rev_id JOIN actor ON rev_actor = actor_id JOIN user_groups ON actor_user = ug_user WHERE ptrp_reviewed = 0 AND ptrpt_tag_id = 9 # Snippet AND page_namespace = 0 AND page_is_redirect = 1 AND EXISTS ( # Only 1 revision based on rev_count page triage tag SELECT 1 FROM pagetriage_page_tags tags2 WHERE tags2.ptrpt_page_id = page_id AND tags2.ptrpt_tag_id = 7 AND tags2.ptrpt_value = 1 ) AND EXISTS ( # Move log from the same time by the same person SELECT 1 FROM logging_logindex lgl2 WHERE log_namespace = page_namespace AND log_title = page_title AND log_timestamp = rev_timestamp AND log_actor = rev_actor AND log_type = 'move' AND log_action = 'move' ) AND ug_group = 'extendedmover' LIMIT 100; |
Discussion
Approved for trial (100 edits or 14 days, whichever happens first). Please provide a link to the relevant contributions and/or diffs when the trial is complete. ProcrastinatingReader (talk) 10:58, 9 May 2024 (UTC) count updated. Primefac (talk) 17:03, 29 June 2024 (UTC)
- @ProcrastinatingReader the bot reports to User:DannyS712 bot III/Redirects.json every 15 minutes with the redirects that it patrols and why - a 14 day trial will be 1344 entries to scan through, and I would expect that almost all of the relevant entries would be on the first run (for any existing backlog) - would a shorter trial be okay? Like a day (or even less)? --DannyS712 (talk) 16:13, 9 May 2024 (UTC)
- (
Peanut gallery comment) I am BOLDly adding {{BAG assistance needed}}: {{BAG assistance needed}} HouseBlaster (talk · he/they) 03:32, 29 June 2024 (UTC)
- I've tweaked the trial numbers. Primefac (talk) 17:03, 29 June 2024 (UTC)
- Is there a reason that a single day trial (as requested by Danny) would be a Bad Thing? Of course, I am not a bot op, so there might be something I am unaware of :) HouseBlaster (talk · he/they) 22:39, 29 June 2024 (UTC)
- I'm also wondering that - also the "whichever happens first" means I would still need to add some logic to count how many redirects have been patrolled in the trial already --DannyS712 (talk) 12:18, 1 July 2024 (UTC)
- {{bag assistance needed}} (apologies for using this a lot as of late...) HouseBlaster (talk · he/they) 22:45, 6 July 2024 (UTC)
- Though I cannot speak on his behalf, I imagine a concern that @Primefac: may have had would be that the bot might be done within a day. What are your thoughts, Primefac? Provided that it won't actually complete within a day, I don't see an issue with a 1 day trial. cc @DannyS712: --TheSandDoctor Talk 04:24, 9 July 2024 (UTC)
- I had no concerns; I thought I was giving the botop what they wanted. They said 14 days was too long and there would be too many actions to look at. I threw out 100 as our standard number (which does happen to be "about a day's worth" when you do the maths) because on these "not sure how many per day" requests it might be only a few dozen over 14 days. Danny is a trusted botop and while it needs to go through a trial to make sure everything is working, we are not going to begrudge a handful of edits on either side of 100 if the task can be shown to be operating within expected parameters. So sure, run it for a day and see where you end up. Primefac (talk) 00:03, 10 July 2024 (UTC)
- And yes, HouseBlaster, using the assistance template twice in ten days is a bit excessive. Primefac (talk) 00:03, 10 July 2024 (UTC)
- @DannyS712: did you see the above? TheSandDoctor Talk 22:20, 13 July 2024 (UTC)
- Yes, sorry, I was out of town for a while but am back and will do bot stuff again soon --DannyS712 (talk) 02:39, 21 July 2024 (UTC)
- @DannyS712: did you see the above? TheSandDoctor Talk 22:20, 13 July 2024 (UTC)
- Though I cannot speak on his behalf, I imagine a concern that @Primefac: may have had would be that the bot might be done within a day. What are your thoughts, Primefac? Provided that it won't actually complete within a day, I don't see an issue with a 1 day trial. cc @DannyS712: --TheSandDoctor Talk 04:24, 9 July 2024 (UTC)
- Is there a reason that a single day trial (as requested by Danny) would be a Bad Thing? Of course, I am not a bot op, so there might be something I am unaware of :) HouseBlaster (talk · he/they) 22:39, 29 June 2024 (UTC)
- I've tweaked the trial numbers. Primefac (talk) 17:03, 29 June 2024 (UTC)
Operator: Mr. Stradivarius (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 03:19, Saturday, February 17, 2024 (UTC)
Function overview: Automatically populate sandboxes for modules listing disambiguation templates, set index templates or soft redirect templates; and if necessary issue edit requests to update the main modules.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python (Pywikibot framework)
Source code available: https://github.com/mrstradivarius/dabtemplates
Links to relevant discussions (where appropriate): Template talk:Pagetype#Detecting pages with Template:Wiktionary redirect and other soft redirects (permalink)
Edit period(s): Daily
Estimated number of pages affected: 5
Namespace(s): Module, module talk, template talk
Exclusion compliant (Yes/No): Yes
Function details: This is an expansion of Wikipedia:Bots/Requests for approval/StradBot (task 1). Task 1 was for updating a disambiguation template list for Module:Disambiguation; this task expands this to two more use cases: updating a list of set index pages for Module:Pagetype, and updating a list of soft redirects, also for Module:Pagetype.
The bot uses the following algorithm. This has not changed since task 1.
- The bot constructs a list of disambiguation templates, set index templates or soft redirect templates. The list includes template redirects. It does this by iterating through all templates in a specific category (the
-catoption). Non-templates are ignored, as are templates in the bot's exclusion list (the-excludeoption). It then retrieves redirects for all of these templates. - It formats the list of templates and template redirects as a Lua table, and saves the result in a module sandbox (the
-data-page-sandboxoption). Saving is skipped if the module's content would not change. You can see sample output from the bot here. - If the sandbox module was updated, and if its new content is different from that of the main module (the
-data-pageoption), then the bot adds an edit request to update the main module to the relevant talk page (the-data-talk-pageoption). There is a sample edit request here.
The bot will be used to update the following modules:
| # | Use case | Option | Value | Notes |
|---|---|---|---|---|
| 1 | Update disambiguation templates for Module:Disambiguation. | -data-page-sandbox
|
Module:Disambiguation/templates/sandbox | Already approved in Wikipedia:Bots/Requests for approval/StradBot. |
-data-page
|
Module:Disambiguation/templates | |||
-data-talk-page
|
Module talk:Disambiguation | |||
-cat
|
Category:Disambiguation message boxes | |||
-exclude
|
Template:Dmbox | |||
| 2 | Update set index templates for Module:Pagetype. | -data-page-sandbox
|
Module:Pagetype/setindex/sandbox | |
-data-page
|
Module:Pagetype/setindex | |||
-data-talk-page
|
Template talk:Pagetype | |||
-cat
|
Category:Set index article templates | |||
-exclude
|
Template:Dmbox | |||
| 3 | Update soft redirect templates for Module:Pagetype. | -data-page-sandbox
|
Module:Pagetype/softredirect/sandbox | |
-data-page
|
Module:Pagetype/softredirect | |||
-data-talk-page
|
Template talk:Pagetype | |||
-cat
|
Category:Templates for soft redirects | |||
-exclude
|
Template:Resolve category redirect |
Discussion
- Approved for trial (one-time run). Please provide a link to the relevant contributions and/or diffs when the trial is complete. – SD0001 (talk) 05:58, 17 February 2024 (UTC)
Operator: Capsulecap (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 00:14, Wednesday, June 14, 2023 (UTC)
Function overview: This task checks the Top 25 Report page frequently to see if the current report has updated. If it was updated, then it will go through all pages in the new report and add or update the Template:Top 25 Report template on their talk pages.
Automatic, Supervised, or Manual: Automatic
Programming language(s): Python
Source code available: No, but if necessary I can upload it
Links to relevant discussions (where appropriate): Wikipedia:Bot requests#Top 25 report
Edit period(s): Daily
Estimated number of pages affected: 25 pages/week
Namespace(s): Talk
Exclusion compliant (Yes/No): No
Function details: This task first checks the page Wikipedia:Top 25 Report to see if the transcluded link was modified. (This should mean that the report was updated.) If it has, then it uses the first revision of the transcluded page, which is always a basic list, to get a list of article talk pages to modify. It then goes through each talk page, updating the Template:Top 25 Report template if it exists and adding it if not. As for exclusion compliance, I have not added that feature in yet.
Discussion
The Top 25 report is updated weekly. Why does this task need to run twice a day? Primefac (talk) 09:08, 14 June 2023 (UTC)
- I wanted to ensure that the template is added quickly. I've changed it to daily, and if it should be longer then you can tell me. Capsulecap (talk • contribs) 14:24, 14 June 2023 (UTC)
- Additionally, some reports (including the one for last week) are finished late, and do not get added until later on. I wanted to ensure that the pages on the report get the template on their talk page. If the next report is done on time, then the maintainers of the report will replace the transclusion to the late report with the new one less than a week after the old report replaced the one before it. I agree that twice a day was a bit too excessive. Daily should be fine. Capsulecap (talk • contribs) 14:28, 14 June 2023 (UTC)
- Capsulecap is right about this. And task need to run twice a day.--BabbaQ (talk) 15:58, 14 June 2023 (UTC)
- @Capsulecap: Hi. What would happen if the same article comes in top 25 report again, say with a gap of four months? —usernamekiran (talk) 17:21, 21 June 2023 (UTC)
- If that happens, then there will be no difference from if it was featured twice with more than a four month gap. There is nothing that says to do anything different for pages on T25 which are featured multiple times in a small timespan, and pages like Talk:ChatGPT feature multiple such examples. Capsulecap (talk • contribs) 23:56, 21 June 2023 (UTC)
Approved for trial (1 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. I'm trying to wrap my head around what's this bot supposed to do exactly, so I'm going to approve it for a one-time run of 1 day. This should give me (and perhaps others) a better idea of what this is about. Headbomb {t · c · p · b} 17:34, 2 July 2023 (UTC)
- @Headbomb: Although I did a trial run, the bot made test edits with numerous errors. I have fixed the code causing these issues, and will (with permission) restart the trial when the next report comes in. Capsulecap (talk • contribs) 19:51, 3 July 2023 (UTC)
- @Capsulecap: can you link to the results nonetheless? Headbomb {t · c · p · b} 21:46, 3 July 2023 (UTC)
- See edits 4 through 29. Note that the newest three edits were a test run for a fix to something which happened in Talk:Elemental (2023 film), and that many incorrect edits were caused by other editors modifying talk pages to add the template before the test run was done. Although the bot will not add redundant templates assuming that nobody adds the top 25 placement before it, I am considering adding redundancy protection. One problem — the one on the page about the Titan submarine incident — was one I didn't think of, as the talk page was moved with the main page, causing the top 25 report template to be placed on a redirect instead of the actual talk page. This is a problem I am working on fixing, as I have noticed that "current events" pages that show up on the report often frequently get moved. The bot also ended up creating the page "Talk:Errible things in Russia, the North Atlantic and HBO have the most attention this week.", but I fixed the source issue and tagged the page for CSD. few of the edits are fine, and most would be fine if there was redundancy protection or if the top 25 templates didn't already have the week in there. One question, though — since the bot will run daily, and people wouldn't need to modify top 25 templates anymore — should I implement redundancy protection? Capsulecap (talk • contribs) 02:46, 4 July 2023 (UTC)
- "Should I implement redundancy protection" I would say that's a good idea, regardless of how often it comes into play. Headbomb {t · c · p · b} 02:52, 4 July 2023 (UTC)
- I just finished implementing the redundancy protection along with the redirect traversal stuff. The bot should work just fine now. Do I have to redo the trial? Capsulecap (talk • contribs) 04:35, 4 July 2023 (UTC)
- "Should I implement redundancy protection" I would say that's a good idea, regardless of how often it comes into play. Headbomb {t · c · p · b} 02:52, 4 July 2023 (UTC)
- See edits 4 through 29. Note that the newest three edits were a test run for a fix to something which happened in Talk:Elemental (2023 film), and that many incorrect edits were caused by other editors modifying talk pages to add the template before the test run was done. Although the bot will not add redundant templates assuming that nobody adds the top 25 placement before it, I am considering adding redundancy protection. One problem — the one on the page about the Titan submarine incident — was one I didn't think of, as the talk page was moved with the main page, causing the top 25 report template to be placed on a redirect instead of the actual talk page. This is a problem I am working on fixing, as I have noticed that "current events" pages that show up on the report often frequently get moved. The bot also ended up creating the page "Talk:Errible things in Russia, the North Atlantic and HBO have the most attention this week.", but I fixed the source issue and tagged the page for CSD. few of the edits are fine, and most would be fine if there was redundancy protection or if the top 25 templates didn't already have the week in there. One question, though — since the bot will run daily, and people wouldn't need to modify top 25 templates anymore — should I implement redundancy protection? Capsulecap (talk • contribs) 02:46, 4 July 2023 (UTC)
- @Capsulecap: can you link to the results nonetheless? Headbomb {t · c · p · b} 21:46, 3 July 2023 (UTC)
- Trial complete. See 21 most recent contributions. Out of the 25 pages in the June 25th to July 1st edition, 21 pages were correctly edited, two pages (Talk:Money in the Bank (2023) and Talk:Titan submersible implosion) were not edited because of unexpected and likely erroneous formatting in the report's first revision (a space was in place of the usual tab after those two pages' titles), and two pages were not edited as they already had this week in their templates. For context on those two pages which didn't get the template on accident, the first revision of the report is always an imported set of tab delimited data — in this case, spaces were in place of tabs for the names of those two articles. The bot created two new talk pages on accident, which I quickly tagged for CSD. Capsulecap (talk • contribs) 05:48, 7 July 2023 (UTC)
- Update: I've come up with a solution to this problem and will be implementing and testing it soon. This is the last issue which I will have to fix. Capsulecap (talk • contribs) 16:26, 7 July 2023 (UTC)
Approved for extended trial (25 edits or 7 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. One week's worth, or 25 edits, whichever you need. Headbomb {t · c · p · b} 17:16, 7 July 2023 (UTC)
- Trial complete. See See 25 most recent contributions. This time, I verified that all edits the bot would make would be correct on a script that had editing commented out. They were all good edits, so I ran the full script. All 25 pages on the report had the template added or changed on their talk pages. Capsulecap (talk • contribs) 01:57, 15 July 2023 (UTC)
- Most seemed fine, but there was this that stood out.
- Headbomb {t · c · p · b} 21:59, 20 July 2023 (UTC)
- I noticed that and didn't pay much attention to it as it was merely cosmetic. Since that was considered problematic, I'll get to fixing that and keeping the collapse as the last edit. Capsulecap (talk • contribs) 14:57, 21 July 2023 (UTC)
- For testing you can revert to a prior state and unleash the bot on it. Headbomb {t · c · p · b} 16:17, 21 July 2023 (UTC)
- Trial complete. See 22 most recent edits. Also see this test edit which the bot made in user talk space showing a similar condition to the page Talk:Deaths in 2023. If you would like, I can manually revert the edit on Talk:Deaths in 2023 which added the newest date and run the bot again to show you. Capsulecap (talk • contribs) 19:58, 21 July 2023 (UTC)
- Well... the collapsed stuff is handled correctly, but now it's inconsistent the other way around. It should list the ranks when they're there, or omit them when they're not.
- Or, probably a better idea, update old listings to list the ranks, e.g. [1]. You might need some discussion before though. Headbomb {t · c · p · b} 20:18, 21 July 2023 (UTC)
- I think it's a good idea to retroactively add the rankings to the templates, but I'm not sure of where to obtain consensus for that, and it would either require a bot task or lots of manual work. The other way you listed is probably easier, but causes inconsistency between pages. Something else I thought of is a Lua module that automatically grabs the placements, but I'm not sure if such a thing is supported. Capsulecap (talk • contribs) 20:30, 21 July 2023 (UTC)
- What if it deleted what was there first, then re-added the template with all dates and ranks? In the same edit that is. Headbomb {t · c · p · b} 20:46, 21 July 2023 (UTC)
- It could work, but I think I would have to submit a separate bot task for that. A separate (and much simpler) approach would be to add a "ranks" parameter that does nothing to the bot category. If set to yes, then the bot will add ranks when it updates the report. Otherwise or if unset, the bot will only add the date. This maintains consistency within talk pages, but not between talk pages; the latter would require consensus strongly towards either using ranks or not. Capsulecap (talk • contribs) 21:03, 21 July 2023 (UTC)
- Approved for extended trial (25 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Indeed, consistency within talk pages is usually a lesser threshold to clear. I'm giving you trial for that (make sure to include a mix of both types of edits), but if you want to have that (should we always rank things) discussion first, you can also wait for consensus to emerge before trialing. Headbomb {t · c · p · b} 21:11, 21 July 2023 (UTC)
- @Capsulecap, are you still doing this? — Qwerfjkltalk 14:43, 11 October 2023 (UTC)
- Yes, I am. Have taken a long break from editing but I never canceled this bot project. Capsulecap (talk • contribs) 15:44, 21 October 2023 (UTC)
- It could work, but I think I would have to submit a separate bot task for that. A separate (and much simpler) approach would be to add a "ranks" parameter that does nothing to the bot category. If set to yes, then the bot will add ranks when it updates the report. Otherwise or if unset, the bot will only add the date. This maintains consistency within talk pages, but not between talk pages; the latter would require consensus strongly towards either using ranks or not. Capsulecap (talk • contribs) 21:03, 21 July 2023 (UTC)
- What if it deleted what was there first, then re-added the template with all dates and ranks? In the same edit that is. Headbomb {t · c · p · b} 20:46, 21 July 2023 (UTC)
- I think it's a good idea to retroactively add the rankings to the templates, but I'm not sure of where to obtain consensus for that, and it would either require a bot task or lots of manual work. The other way you listed is probably easier, but causes inconsistency between pages. Something else I thought of is a Lua module that automatically grabs the placements, but I'm not sure if such a thing is supported. Capsulecap (talk • contribs) 20:30, 21 July 2023 (UTC)
- For testing you can revert to a prior state and unleash the bot on it. Headbomb {t · c · p · b} 16:17, 21 July 2023 (UTC)
- I noticed that and didn't pay much attention to it as it was merely cosmetic. Since that was considered problematic, I'll get to fixing that and keeping the collapse as the last edit. Capsulecap (talk • contribs) 14:57, 21 July 2023 (UTC)
{{Operator assistance needed}} It has been more than a month since the last post, is this trial still ongoing? Primefac (talk) 13:26, 31 December 2023 (UTC)
- Yes. As I said a long time ago, I wasn't really maintaining activity onwiki or paying attention to this page. I've decided to come back to wikipedia at some point in the near future (within 1-2 months) but I can add the features to the project. Thanks for reaching out. Capsulecap (talk • contribs) 22:27, 5 January 2024 (UTC)
- @Primefac: I've added support for that
ranksattribute, as is seen in the 5 most recent bot edits, all of which are to my test pages. I've also created support for converting preexisting top25 templates of the alternate form into regular form top 25s, and made it so top 25 report templates longer than 800 bytes are collapsed. I will test the bot once the report is switched to the current week, which should be on Saturday or Sunday. Capsulecap (talk • contribs) 01:34, 6 January 2024 (UTC) - @Primefac: Status: Current run had too many problems to use as a final trial. Fixed 2 bugs here. Should be ready to be released any week now. Capsulecap (talk • contribs) 03:27, 15 January 2024 (UTC)
- @Primefac: Status: Apparently what I said above was wrong. The bot works fine on the average page but I forgot to put the ranks parameter on new templates. That has since been fixed. However, there are several larger problems that I discovered on this run — the bot broke another bot's template that was split over two lines (how rude of it!), and the entries in the report were changed from the first entry, necessitating me to delete templates from two talk pages. For some reason it also ignored the page Franz Beckenbauer in the first revision, but that shouldn't be a problem once I manage to switch over to using the newest revision with tables. Also created a list at User:CapsuleBot/Todo. Capsulecap (talk • contribs) 02:36, 20 January 2024 (UTC)
Operator: Hawkeye7 (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 01:57, Wednesday, March 22, 2023 (UTC)
Function overview: Mark unassessed stub articles as stubs
Automatic, Supervised, or Manual: Automatic
Source code available: Not yet
Links to relevant discussions (where appropriate): Wikipedia:Bot requests/Archive 84#Stub assessments with ORES
Edit period(s): daily
Estimated number of pages affected: < 100 per day
Namespace(s): Talk
Exclusion compliant (Yes/No): Yes
Function details: Go through Category:Unassessed articles (only deals with articles already tagged as belonging to a project). If an unassessed article is rated as a stub by ORES, tag the article as a stub. Example
Discussion
Note: 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⚡ 00:10, 28 March 2023 (UTC)
- ^. Also, may potentially be a CONTEXTBOT; see Wikipedia:Stub:
There is no set size at which an article stops being a stub.
EpicPupper (talk) 23:04, 30 March 2023 (UTC)- The Bot run only affects unassessed articles rated as stubs by mw:ORES.
The ORES ratings for stubs are very reliable (some false negatives – which wouldn't be touched under this proposal – but no false positives)
. Hawkeye7 (discuss) 00:03, 31 March 2023 (UTC)
- The Bot run only affects unassessed articles rated as stubs by mw:ORES.
- ^. Also, may potentially be a CONTEXTBOT; see Wikipedia:Stub:
- Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Sounds reasonable as ORES is usually good for assessing stub articles as such. – SD0001 (talk) 11:41, 1 April 2023 (UTC)
Bot run with 50 edits. No problems reported. Diffs: [2]. Hawkeye7 (discuss) 00:42, 18 April 2023 (UTC)
- Comment: Some behavior I found interesting is that the bot is reverting start-class classifications already assigned by a human editor, and overriding those with stub-class. [3] and [4] EggRoll97 (talk) 03:28, 18 May 2023 (UTC)
- This should not be happening. Frostly (talk) 03:58, 18 May 2023 (UTC)
- The question is: what should be happening? The article were flagged because some of the projects were not assessed. Should the Bot (1) assess the unassessed ones as stubs and ignore the assessed ones or (2) align the unassessed ones with the ones that are assessed? Hawkeye7 (discuss) 04:21, 18 May 2023 (UTC)
- Per recent consensus assessments should be for an entire article, not per WikiProject. The bot should amend the template to use the article wide code. If several projects have different assessments for an article it should leave it alone. Frostly (talk) 05:03, 18 May 2023 (UTC)
- @Hawkeye7: Courtesy ping, I've manually fixed up the edits where the bot replaced an assessment by a human editor. 6 edits total to be fixed out of 52 total edits. EggRoll97 (talk) 07:16, 18 May 2023 (UTC)
- Bot has been amended. Hawkeye7 (discuss) 04:51, 19 May 2023 (UTC)
- @Hawkeye7: Courtesy ping, I've manually fixed up the edits where the bot replaced an assessment by a human editor. 6 edits total to be fixed out of 52 total edits. EggRoll97 (talk) 07:16, 18 May 2023 (UTC)
- Per recent consensus assessments should be for an entire article, not per WikiProject. The bot should amend the template to use the article wide code. If several projects have different assessments for an article it should leave it alone. Frostly (talk) 05:03, 18 May 2023 (UTC)
- The question is: what should be happening? The article were flagged because some of the projects were not assessed. Should the Bot (1) assess the unassessed ones as stubs and ignore the assessed ones or (2) align the unassessed ones with the ones that are assessed? Hawkeye7 (discuss) 04:21, 18 May 2023 (UTC)
- This should not be happening. Frostly (talk) 03:58, 18 May 2023 (UTC)
- {{BAG assistance needed}} This has been waiting for over 2 months since the end of the trial, and over 4 months since the creation of the request. Given the concerns expressed that the bot operator has since fixed, an extended trial may be a good idea here. EggRoll97 (talk) 05:19, 8 August 2023 (UTC)
- My apologies. I have been very busy. Should I run the new Bot again with a few more edits? Hawkeye7 (discuss) 18:57, 15 October 2023 (UTC)
- Approved for extended trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. – SD0001 (talk) 19:10, 15 October 2023 (UTC)
- Thank you. Hawkeye7 (discuss) 22:33, 15 October 2023 (UTC)
- My apologies. I have been very busy. Should I run the new Bot again with a few more edits? Hawkeye7 (discuss) 18:57, 15 October 2023 (UTC)
{{Operator assistance needed}} It has been more than a month since the last post, is this trial still ongoing? Primefac (talk) 13:26, 31 December 2023 (UTC)
- Yes. I wrote the bot using my C# API, and due to a necessary upgrade here, my dotnet environment got ahead of the one on the grid. I could neither build locally and run on the grid nor on build on the grid. (I could have run the trial locally but would not have been able to deploy to production.) There is currently a push to move bots onto Kubernetes containers, but there was no dotnet build pack available. The heroes on Toolforge have now provided one for dotnet, and I will be testing it when I return from vacation next week. If all goes well I will finally be able to deploy the bot and run the trial at last. See phab:T311466 for details. Hawkeye7 (discuss) 22:54, 31 December 2023 (UTC)
A user has requested the attention of the operator. Once the operator has seen this message and replied, please deactivate this tag. (user notified) Primefac (talk) 20:10, 18 February 2024 (UTC)
- Work was done in January and some changes made on Toolforge. Will resume the trial run when I get a chance. Hawkeye7 (discuss) 23:33, 18 February 2024 (UTC)
Operator: EpicPupper (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 02:55, Thursday, March 2, 2023 (UTC)
Automatic, Supervised, or Manual: automatic
Source code available:
Function overview: Replace AMP links in citations
Links to relevant discussions (where appropriate): BOTREQ, Village Pump
Edit period(s): Weekly
Estimated number of pages affected: Unknown, estimated to be in the range of hundreds of thousands
Exclusion compliant (Yes/No): Yes
Already has a bot flag (Yes/No): Yes
Function details: Using the AmputatorBot API, replaces AMP links with canonical equivalents. This task runs on all pages with citation templates which have URL parameters (e.g. {{cite news}}, {{cite web}}, etc).
Discussion
Approved for trial (50 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Primefac (talk) 10:27, 8 March 2023 (UTC)
- Just noting that I'm working on this but it may take some time. EpicPupper (talk) 23:01, 30 March 2023 (UTC)
- Been a bit busy IRL, but will get to this soon. Frostly (talk) 20:33, 25 June 2023 (UTC)
- soon — Frostly (talk) 20:33, 21 October 2023 (UTC)
- Been a bit busy IRL, but will get to this soon. Frostly (talk) 20:33, 25 June 2023 (UTC)
{{Operator assistance needed}} It has been more than a month since the last post, is this trial still ongoing? Primefac (talk) 13:26, 31 December 2023 (UTC)
- Primefac, my apologies, this flew off my radar. I'll work on setting up the bot on Toolforge this month and should have the results soon. — Frostly (talk) 06:13, 5 January 2024 (UTC)
- I've made progress on uploading to Toolforge; just fixing a few bugs. — Frostly (talk) 03:36, 4 February 2024 (UTC)
- There's been a few issues with the API that have been difficult to tackle; I think pivoting to self-hosting the API backend on Toolforge is a good solution (working on that this month). — Frostly (talk) 22:41, 21 February 2024 (UTC)
- Finishing up final revisions to the code! — Frostly (talk) 18:21, 17 July 2024 (UTC)
- about time! Hehe —usernamekiran (talk) 16:59, 18 July 2024 (UTC)
- @Frostly that is awesome! I actually was about to start this process (Wikipedia:Bot_requests#de-AMP_bot) and I am glad you already did. And it seems you are almost done. Is there a way I can find the source code or what any lingering issues there might be? Also, did you end up using the AmputatorBot API, another API, or your own implementation? Osalbahr (talk) 00:53, 9 September 2024 (UTC)
- Finishing up final revisions to the code! — Frostly (talk) 18:21, 17 July 2024 (UTC)
- There's been a few issues with the API that have been difficult to tackle; I think pivoting to self-hosting the API backend on Toolforge is a good solution (working on that this month). — Frostly (talk) 22:41, 21 February 2024 (UTC)
- I've made progress on uploading to Toolforge; just fixing a few bugs. — Frostly (talk) 03:36, 4 February 2024 (UTC)
Bots that have completed the trial period
Operator: DreamRimmer (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 12:48, Saturday, September 7, 2024 (UTC)
Automatic, Supervised, or Manual: automatic
Programming language(s): Python
Source code available:
Function overview: Removing spurious nobot notice
Links to relevant discussions (where appropriate): Special:Permalink/1244485662#Removing spurious nobot notice
Edit period(s): one-time
Estimated number of pages affected: 5187
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): Yes
Function details: Around a year ago, the {{bots|deny=PrimeBOT}} code was mistakenly added to {{Uw-coi}} and later removed. In the meantime, {{Uw-coi}} had been posted on 5187 user talk pages. BaranBOT will now remove this spurious notice from all these 5187 pages. – DreamRimmer (talk) 12:51, 7 September 2024 (UTC)
Discussion
Just for the record (and I'll note I'm recusing as BAG in this discussion) it was not mistakenly added to the template; if anything the mistake was more that the nobots wasn't put in a <noinclude> set, which caused it to be subst everywhere. Primefac (talk) 12:56, 7 September 2024 (UTC)
Approved for trial (25 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. ProcrastinatingReader (talk) 15:23, 7 September 2024 (UTC)
Trial complete. Edits. – DreamRimmer (talk) 17:40, 7 September 2024 (UTC)
Operator: Primefac (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 12:48, Thursday, May 11, 2023 (UTC)
Function overview: Convert template use following update
Automatic, Supervised, or Manual: Automatic
Source code available: WP:AWB
Links to relevant discussions (where appropriate): Wikipedia talk:WikiProject Templates § Request for a template
Edit period(s): OTR
Estimated number of pages affected:
Namespace(s): 783
Exclusion compliant (Yes/No): Yes
Function details: {{Wikisource author}} recently was updated to allow for a |lang= parameter to link directly to non-English versions of wikisource for an author. A similar template, {{Wikisourcelang}}, links to a generic search on said language wiki for said author. This task will change {{Wikisourcelang|<lang>|otherstuff}} into a {{Wikisource author|lang=<lang>|otherstuff}} call.
Discussion
- {{BAG assistance needed}} valid request not attended by any BAG members for almost two months. —usernamekiran (talk) 23:02, 29 June 2023 (UTC)
- Approved for trial (25 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
- This seems pretty straightforward. Let's go to trial.
- Headbomb {t · c · p · b} 17:38, 2 July 2023 (UTC)
- Trial complete. Edits. As a note, I did not run genfixes just to make the proposed change more obvious, but if this task does proceed I will be running genfixes alongside them.
- Piotrus, I think this request is a little more convoluted than initially requested. Languages such as
dedo not use an "author" prefix (see e.g. Adolph Friedrich Johann Riedel and his corresponding page on de Wikisource), but I can't figure out which languages it holds to. I am not necessarily seeing a specific pattern between what languages do and do not. My thoughts are of two possibilities - run this task only for languages where the proposed change has the intended effect, or just scrap this BRFA and do these changes manually. Primefac (talk) 12:52, 4 July 2023 (UTC)- @Primefac I think we can run it for some languages that we can determine now, it shouldn't be that hard as long as it is consistent for each language (ex. German never uses, Polish always uses it, etc.). We could create a list for all languages that wikisource exists on, or just run it for now for some editions that are the biggest (ex. the ones with interwikis here). I did some checks and it seems it's pretty consisten - just a wikisource naming convention. Note that depending on the language, the "author" prefix is different - Polish is "autor". Swedish is "Författare", etc. In the end, what we need to fix is not the outgoing links but the text on our side. Consider this case, similar to the German one you quote, where we improved the language or our template but messed the link: before, diff, after. Since the links work, can we just figure out the way to change the wording in the template but retain the same link as before? The older template was able to do it, somehow, seems we are introducing a new error somehow? Piotr Konieczny aka Prokonsul Piotrus| reply here 04:48, 5 July 2023 (UTC)
- If you wouldn't mind making a list of which languages use the Author (in whatever language) prefix, I can hard-code their use into the template so that there isn't any issue.
- This wasn't a problem before because {{wikisource author}} only linked to to the English version so no translation or odd coding was necessary. As mentioned in the original discussion, {{wikisource lang}} just links to a general search (which does sometimes turn up the author page directly) and thus does not require the "Author:" prefix. Primefac (talk) 08:06, 5 July 2023 (UTC)
- @Primefac I think we can run it for some languages that we can determine now, it shouldn't be that hard as long as it is consistent for each language (ex. German never uses, Polish always uses it, etc.). We could create a list for all languages that wikisource exists on, or just run it for now for some editions that are the biggest (ex. the ones with interwikis here). I did some checks and it seems it's pretty consisten - just a wikisource naming convention. Note that depending on the language, the "author" prefix is different - Polish is "autor". Swedish is "Författare", etc. In the end, what we need to fix is not the outgoing links but the text on our side. Consider this case, similar to the German one you quote, where we improved the language or our template but messed the link: before, diff, after. Since the links work, can we just figure out the way to change the wording in the template but retain the same link as before? The older template was able to do it, somehow, seems we are introducing a new error somehow? Piotr Konieczny aka Prokonsul Piotrus| reply here 04:48, 5 July 2023 (UTC)
- On hold. Just for now, while we deal with actual template issues. Primefac (talk) 08:31, 5 July 2023 (UTC)
- @Primefac See talk, is this helpful? Those are most larger Wiki source projects, should be enough to get most of our stuff sorted out. We can take a look at what, if anything, is left after dealing with those languages? Piotr Konieczny aka Prokonsul Piotrus| reply here 07:06, 7 July 2023 (UTC)
- Should do, thanks for that. Going to keep this on hold for a bit longer, there's a TFD for merging all of these together and I might be able to enact these proposed changes during the merge process. Primefac (talk) 08:13, 7 July 2023 (UTC)
- @Primefac Just checking the status of this? Piotr Konieczny aka Prokonsul Piotrus| reply here 09:54, 22 September 2023 (UTC)
- Somewhat stalled, been rather busy myself and it doesn't look like anyone has started work on the template merger. I think I might have cleared my on-wiki plate somewhat (touch wood) so I'll see about prioritising the merger. Primefac (talk) 10:51, 22 September 2023 (UTC)
- @Primefac Just checking the status of this? Piotr Konieczny aka Prokonsul Piotrus| reply here 09:54, 22 September 2023 (UTC)
- Should do, thanks for that. Going to keep this on hold for a bit longer, there's a TFD for merging all of these together and I might be able to enact these proposed changes during the merge process. Primefac (talk) 08:13, 7 July 2023 (UTC)
- @Primefac See talk, is this helpful? Those are most larger Wiki source projects, should be enough to get most of our stuff sorted out. We can take a look at what, if anything, is left after dealing with those languages? Piotr Konieczny aka Prokonsul Piotrus| reply here 07:06, 7 July 2023 (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.
- Protection Helper Bot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 13:59, 8 September 2024 (UTC) (bot has flag)
- KiranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 9) Approved 17:21, 1 September 2024 (UTC) (bot has flag)
- Platybot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 17:21, 1 September 2024 (UTC) (bot has flag)
- BaranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 12:02, 11 August 2024 (UTC) (bot has flag)
- HooptyBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 00:01, 5 August 2024 (UTC) (bot to run unflagged)
- ChristieBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Approved 23:42, 4 August 2024 (UTC) (bot has flag)
- C1MM-bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 23:26, 4 August 2024 (UTC) (bot has flag)
- HBC AIV helperbot14 (BRFA · contribs · actions log · block log · flag log · user rights) Approved 13:24, 27 July 2024 (UTC) (bot has flag)
- The Sky Bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Approved 10:58, 24 July 2024 (UTC) (bot has flag)
- IznoBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 12:58, 21 July 2024 (UTC) (bot has flag)
- AdminStatsBot 2 (BRFA · contribs · actions log · block log · flag log · user rights) Approved 12:41, 21 July 2024 (UTC) (bot has flag)
- BaranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Approved 12:36, 21 July 2024 (UTC) (bot has flag)
- Mdann52 bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 14) Approved 12:36, 21 July 2024 (UTC) (bot has flag)
- The Sky Bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Approved 16:34, 17 July 2024 (UTC) (bot has flag)
- RustyBot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 18:05, 5 July 2024 (UTC) (bot has flag)
- Mdann52 bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 15) Approved 18:05, 5 July 2024 (UTC) (bot has flag)
- Qwerfjkl (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 30) Approved 18:05, 5 July 2024 (UTC) (bot has flag)
- PrimeBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 45) Approved 13:47, 29 May 2024 (UTC) (bot has flag)
- Numberguy6Bot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 13:18, 26 May 2024 (UTC) (bot has flag)
- BsoykaBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Approved 13:18, 26 May 2024 (UTC) (bot has flag)
- SDZeroBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 13) Approved 13:08, 26 May 2024 (UTC) (bot has flag)
- CopyPatrolBot (BRFA · contribs · actions log · block log · flag log · user rights) Approved 12:59, 18 May 2024 (UTC) (bot has flag)
- Qwerfjkl (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 29) Approved 11:35, 3 May 2024 (UTC) (bot has flag)
- ButlerBlogBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 4) Approved 11:35, 3 May 2024 (UTC) (bot has flag)
- PrimeBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 42) Approved 11:39, 1 April 2024 (UTC) (bot has flag)
- PrimeBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 43b) Approved 20:42, 31 March 2024 (UTC) (bot has flag)
- PrimeBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 44) Approved 20:26, 31 March 2024 (UTC) (bot has flag)
- BattyBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 82) Approved 12:48, 30 March 2024 (UTC) (bot has flag)
- Qwerfjkl (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 28) Approved 07:32, 29 March 2024 (UTC) (bot has flag)
- Qwerfjkl (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 25) Approved 12:45, 13 March 2024 (UTC) (bot has flag)
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.
- MdWikiBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:04, 3 August 2024 (UTC)
- Arjunaraocbot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 07:35, 23 March 2024 (UTC)
- UrbanBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Bot denied 14:23, 12 October 2023 (UTC)
- Aesthetic Bot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 19:53, 9 September 2023 (UTC)
- Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: V) Bot denied 11:24, 25 July 2023 (UTC)
- UrbanBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:43, 18 July 2023 (UTC)
- pumi (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 11:46, 10 July 2023 (UTC)
- DYKToolsAdminBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 11:39, 1 April 2023 (UTC)
- KiranBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 5) Bot denied 07:53, 4 February 2023 (UTC)
- PuggleBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 12:03, 11 January 2023 (UTC)
- Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: IV) Bot denied 13:04, 29 September 2022 (UTC)
- CapsuleBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 08:21, 27 May 2022 (UTC)
- BsoykaBot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 17:50, 3 April 2022 (UTC)
- Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: III) Bot denied 17:24, 3 April 2022 (UTC)
- Dneo bot (BRFA · contribs · actions log · block log · flag log · user rights) Bot denied 17:32, 6 March 2022 (UTC)
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.
- BattyBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 81) Withdrawn by operator 15:48, 26 August 2024 (UTC)
- Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: VII) Expired 15:41, 27 June 2024 (UTC)
- Dušan Kreheľ (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: VIII) Expired 15:41, 27 June 2024 (UTC)
- PearBOT (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 14) Expired 00:23, 15 June 2024 (UTC)
- PearBOT II (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 13) Expired 07:35, 23 March 2024 (UTC)
- VulpesBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 3) Expired 21:04, 10 March 2024 (UTC)
- DYKNomCheck (BRFA · contribs · actions log · block log · flag log · user rights) Withdrawn by operator 19:20, 10 March 2024 (UTC)
- BattyBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 78) Expired 13:13, 20 February 2024 (UTC)
- VulpesBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Expired 12:06, 20 February 2024 (UTC)
- LemonadeBot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Expired 09:37, 16 February 2024 (UTC)
- Yet another TfD implementor bot (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 2) Withdrawn by operator 19:03, 23 January 2024 (UTC)
- Credibility bot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 07:38, 15 January 2024 (UTC)
- RoccBot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 07:38, 15 January 2024 (UTC)
- SodiumBot (BRFA · contribs · actions log · block log · flag log · user rights) Expired 07:38, 15 January 2024 (UTC)
- Qwerfjkl (bot) (BRFA · contribs · actions log · block log · flag log · user rights) (Task: 24) Expired 18:31, 17 December 2023 (UTC)