Wikisource:Bot requests

From Wikisource
Jump to navigation Jump to search
Bot requests
This page allows users to request that an existing bot accomplish a given task. Note that some tasks may require that an entirely new bot or script be written. This is not the place to ask for help running or writing a bot.

A bot operating performing a task should make note of it so that other bots don't attempt to do the same. Tasks that are permanently assigned or scheduled for long-term execution are listed on Persistent tasks.

See also

Unassigned requests[edit]

Template:Header to Template:Translation header[edit]

We have a situation that I am parking here for broader consideration, especially as it is not one that I have the best familisarisation. We have moved numbers of main ns works to the Translation namespace due to their being Wikisource-sourced translations. Numbers have been moved and not converted to use {{translation header}}. They take a little bit of manipulation based on knowledge of the works, though that should be evident from the language of the work. We need to review https://en.wikisource.org/w/index.php?title=Special:WhatLinksHere/Template:Header&namespace=114&limit=500 and automate those that can be automated, and either manual update the remainder, or look to populate with information that allows for automation. — billinghurst sDrewth 01:35, 15 January 2016 (UTC)

Can someone who likes working in Translation: ns please advise on the requirements for converting these works. There will be something like "header" to "translation header"; addition of language parameter (and use the categorisation to determine that parameter). What else needs to happen? — billinghurst sDrewth 21:56, 7 August 2019 (UTC)

Replace {{blank line}} with {{nop}}[edit]

The template {{blank line}} is deprecated and is slated for deletion per WS:PD, but it is used on nearly 2000 pages, and needs to be replaced before deletion can occur. —Beleg Tâl (talk) 13:41, 31 October 2016 (UTC)

One comment: replacement should be done according to recommended usage of nop (used at the end of a paragraph in the PAGE: namespace where the paragraph terminates the page). So if blank line is at the beginning of a page, it should be inserted at the end of the previous page.— Mpaa (talk) 17:04, 31 October 2016 (UTC)
I have tested it, and it appears to work correctly with nop at the top of the page. If the bot can be made to put it at the bottom of the previous page, that would be great, but I do not think that is necessary. —Beleg Tâl (talk) 17:13, 31 October 2016 (UTC)
It is deprecated usage, not wrong usage. Why are we bothering? Can't we live with it? — billinghurst sDrewth 22:27, 31 October 2016 (UTC)
I'd think so, but several people indicated a preference to delete at WS:PD and nobody opposed until today. —Beleg Tâl (talk) 11:18, 1 November 2016 (UTC)
Just to note that "blank line" is a (wacky) span template, and "nop" is a div template. — billinghurst sDrewth 14:12, 20 February 2018 (UTC)

Question Question can we close this as X mark.svg Not done. It is two separate bot tasks taken without clear vision of the consequences, and for little evident value. That there was a deletion discussion will just mean that the template will need to exist until it is done by other means. I would suggest that someone runs a check on new usage and see if we need to restrict future addition. — billinghurst sDrewth 21:50, 7 August 2019 (UTC)

Conversion of {{FI}} to {{large image}}[edit]

Now that User:Inductiveload has created the template {{large image}} which is less storage- and bandwidth-heavy than {{FI}}, I am converting all the templates in the 5+ volumes of Once a Week that I did so far. There are quite a lot that are all the exact same pattern, except that I wasn’t consistent about top and bottom margins, so I hope a bot can take care of them. It would be like so (note that this only applies to images that have no caption):

1. Convert to {{large image|[[File:filename|500px|center]]|max-width=100%|style=margin-top: Npx; margin-bottom: Mpx;}}

  • EITHER {{FI|file=filename|width=500px|cstyle=margin-top:Npx;margin-bottom:Mpx}}
  • OR {{FI|file=filename|width=100%|cstyle=margin-top:Npx;margin-bottom:Mpx;max-width:500px}}

2. Convert to {{large image|[[File:filename|450px|center]]|max-width=90%|style=margin-top: Npx; margin-bottom: Mpx;}}

  • EITHER {{FI|file=filename|width=450px|cstyle=margin-top:Npx;margin-bottom:Mpx}}
  • OR {{FI|file=filename|width=90%|cstyle=margin-top:Npx;margin-bottom:Mpx;max-width:450px}}

3 etc. The same for 400px/80%, 375px/75%, 350px/70%, and 300px/60%.

Levana Taylor (talk) 19:42, 15 February 2020 (UTC)

Done. Mpaa (talk) 16:19, 16 February 2020 (UTC)
Thank you very much! But I don't see why Volume 9, page 220 didn’t get fixed, for just one example. The bot only found things in volumes 5, 7, and 8, and I know I used the same pattern elsewhere. One problem I see is that the {{FI}} in Volume 2 contain the (useless) parameter "align = center," see Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/633 for an instance, but that doesn’t apply to volume 9. Levana Taylor (talk) 16:29, 16 February 2020 (UTC)
Done. 1) I wrongly assumed all pages were starting with "Page:Once a Week Volume", 2) parameters were in different positions, I assumed only above cases were to be found.
The following are left out, in addition to the ones with caption, please take a look at them. I checked a couple and they have 'alt' param or 'min-width:500px;max-width:675px;' or similar.
  1. Page:Once a Week Volume 8.djvu/7
  2. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/12
  3. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/61
  4. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/70
  5. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/75
  6. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/80
  7. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/89
  8. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/128
  9. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/134
  10. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/265
  11. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/161
  12. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/167
  13. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/187
  14. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/200
  15. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/203
  16. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/597
  17. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/451
  18. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/552
  19. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/551
  20. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/574
  21. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/562
  22. Page:Once a Week Jul - Dec 1859.pdf/132
Cheers. Mpaa (talk) 21:57, 17 February 2020 (UTC)
This list is done. Levana Taylor (talk) 01:43, 18 February 2020 (UTC)

This is great! Do you plan to add support for captioning? Or is there a major obstacle to that? -Pete (talk) 22:15, 17 February 2020 (UTC)

Thank you Mpaa! If the only additional parameter in addition to the patterns you already used is "caption," the output pattern would be as follows, for the style in OAW (Inductiveload deliberately didn’t build captions into Largeimage so as to keep it stripped down & allow separate formatting of the captions):
<div style="margins">
{{large image|[[File:filename|width(px)|center]]|max-width=width(percent)}}
{{c|{{fs90|caption}}}}
</div>
Levana Taylor (talk) 00:35, 18 February 2020 (UTC)
Done. Left:
  1. Page:Once a Week Volume 8.djvu/9
  2. Page:Once a Week Volume 8.djvu/65
  3. Page:Once a Week Volume V.djvu/6
  4. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/119
  5. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/124
  6. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/320
  7. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/623
  8. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/514
  9. Page:Once a Week Jul - Dec 1859.pdf/10
  10. Page:Once a Week Dec 1860 to June 61.pdf/10
  11. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/379
  12. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/376
  13. Page:Once a Week, Series 1, Volume II Dec 1859 to June 1860.pdf/482
Mpaa (talk) 21:11, 18 February 2020 (UTC)
Umm… when in the above output pattern I wrote <div style="margins"> I meant, for example, <div style="margin-top:25px; margin-bottom:20px;"> but you literally put <div style="margins"> everywhere! Levana Taylor (talk) 23:33, 18 February 2020 (UTC)
<sigh> You changed notation so I thought you really meant it like that. Not easy to fix automatically, will be faster by hand than to implement the logic. What I can easily do is to replace "margins" using a default of 20px&20px for top&bottom as it is the most popular choice. Otherwise, it needs to be done by hand, looking at MpaaBot contributions on Feb,18, looking at the delta in history comparison and copy it to the latest revision. Sorry about that.Mpaa (talk) 08:17, 19 February 2020 (UTC)
Sorry about being confusing! I would prefer top:25px, bottom:20px which works best for the new way of doing captions. Using that should be plenty good enough for 99 out of 100 pages. Levana Taylor (talk) 09:41, 19 February 2020 (UTC)
Done (maybe :-) ). Mpaa (talk) 17:43, 19 February 2020 (UTC)
Great! Thank you very much for spending so much time working on this. Would it take you long to pull up a list of any OAW pages that still contain {{FI}} or its sister template {{FIS}}? (I am still working on converting a few of the more complex uses of FIS to Img float or something else). Levana Taylor (talk) 18:00, 19 February 2020 (UTC)
See this query. Mpaa (talk) 20:20, 19 February 2020 (UTC)

OK. For now I will continue using {{FI}}, and assume that at some point somebody will figure out the most straightforward way to add captions. I'm not worried about formatting for most of the stuff I do, I just want it to look more or less OK -- much more interested in making high quality text and graphics available to the masses. -Pete (talk) 08:26, 19 February 2020 (UTC)

Stray unprintable characters or non-standard spaces in section headers[edit]

Would you it be possible to try to standardize spaces to ASCII 32 for all section headers in:

Sample change: [1][2]. This would have the advantage that the article title matches the section header. Also, while editing the pages, it might be worth putting them the category for the work (Category:A Naval Biographical Dictionary). Thanks! Jura1 (talk) 23:24, 5 April 2020 (UTC)

@Jura1: The issue with the proposal is that changing the tag in the Page: namespace will require exactly the same change to the article in section tag in the transclusion, the one in the section parameter. Then we will be needing to move the pages so the pagename matches the section and transclusion, which then will mean editing each preceding and next articles for the respective next and previous links. That is a lot of work, and fraught with risks of breaking transclusions and not knowing what is borken, and where. (FWIW I checked a few pagenames and the same spaces appear in the name, and the section, which is not surprising as they will have been built from the same master list. I am not seeing the "difference" problem that you are identifying.)
With regard to categorisation, it has not been our practice to categorise each subpage of a work with a parent category, especially as tools are able to drill down levels in categories. The subpage itself does that categorisation, and I am not certain of the benefit that you envisage from the proposed categorisation for the community. Such an output replicates an existing index (in the work, or curated), or a table of contents, or the special:prefixindex that you generated earlier.
I do agree that the non-standard spaces is not ideal, I don't think that the proposed solution has the value to undertake. I do not see that things are broken, eg. broken searches, or the lookahead typing. In fact, I say that your changes are problematic when you undertake then if we undo your edits, we then have to undo, undo, undo, undo, undo as a chain reaction. Maybe you should stop doing something without demonstrated value. — billinghurst sDrewth 11:30, 6 April 2020 (UTC)
Maybe it's just query server that is broken and not the browser correcting it on the fly.
If it's preferred to revert things over sorting things out .. do whatever you prefer. Jura1 (talk) 11:42, 6 April 2020 (UTC)
I don't want to be in a situation with half-fixes, as there is an ugly complexity, to moves and fixes and aligning headers, and related pages, and each linked set of 3 curated pages. The intra-related nature of our works in main namespace means that half-fixes can kill pages. We really need concerted and considered efforts with changes, and a clear value which outweighs doing nothing. — billinghurst sDrewth 12:59, 6 April 2020 (UTC)

Assigned requests[edit]