User talk:Ladsgroup

Previous discussion was archived at User talk:Ladsgroup/Archive 8 on 2015-09-02.

Hi! I remember you run a very efficient bot and in the past I asked you some fixes which were very efficient. Now I mostly do fixes through QuickStatements, which is a very good tool, but isn't still able to fix references leaving the statements unchanged. I sometimes notice big groups of items (thousands and tens of thousands) having references which are imprecise or wrong and I don't know who to ask for correction. Could I slowly report you some notable cases of references to be fixed, so that we can slowly deal with them through your bot? I think it is crucial for our data quality having references which are exactly correct, whilst at the moment this fact often doesn't happen. Thank you very much in advance!

Hey sure. I try to write something but I want to know the exact framework so I don't need write similar code every time, so I would write something general and use that every time.

Can you give me a couple of examples?

OK, great! So, here is a detailed panoramic of the situation. I see three main types of errors to be corrected:

• first type: correct previous imprecise bot-edits
  • one known case: all references containing stated in (P248) property (Q1400881) + Internetowy Polski Słownik Biograficzny ID (P8130) ID (you can easily infer a complete list from here) should have the stated in (P248) corrected in Internetowy Polski Słownik Biograficzny (Q96022943) (example); these wrong references have been recently added by @Reinheitsgebot:, to which I reported the problem without obtaining a correction
• second type: properties which changed their format, so that references are now broken
  • case 1: thousands of references containing HDS ID (P902) still have IDs with 4 or 5 digits (complete list): now the IDs require always 6 digits, so 1 zero should be added before the 5 digits (example), 2 zeros before the 4 digits (example); if absent, stated in (P248) Historical Dictionary of Switzerland (Q642074) should be added before HDS ID (P902) (example)
  • case 2: hundreds of references containing InPhO ID (P863) still have IDs containing only a number (complete list): now the IDs require the prefix "thinker/", which should always be added before the number (example)
  • case 3: hundreds of references containing Spanish Biographical Dictionary ID (P4459) still have IDs containing only a number (complete list): now the IDs require also the following part, with "/" and the name, which should always be added after the number; if, as nearly always happen, the ID in the reference numerically coincides with the main value of P4459, the main value of P4459 should be used to complete the value of P4459 used in the reference (example)
• third type: properties which have been added twice as references to the same statement, with small differences or exactly equal; the two references should be merged keeping all the properties except reference URL (P854) (possibly obsolete and anyway not stable): stated in (P248), ID, named as (P1810) if present, most recent retrieved (P813) if present (here the range of properties involved is huge, I will give only some examples - more to follow in the next weeks) - introductive example 1, introductive example 2

  note: the following queries regard only date of birth (P569), but should be repeated at least for date of death (P570) and possibly for all properties

  • Bibliothèque nationale de France ID (P268): first list (example of merged references, another one) and second list^{may timeout, if necessary use LIMIT} (example of coincident references, the oldest is removed, same here)
  • Artsy artist ID (P2042): list^{contains false positives} (example of coincident references, the one having P813 first is removed)
  • Artnet artist ID (P3782): list^{contains false positives} (example of merge of three references)
  • GND ID (P227): list (example: a reference with P248 but without ID is markedly imprecise, so in presence of another reference having both P248 and ID should simply be removed)

For whichever question, ask me! When you have the bot ready, please start with some test-edits, so that I can have a look. Thank you very much in advance!

Thanks. I try to tackle it next weekend. This weekend I'm drowning in something personal.

Hi! Any updates? Obviously no urgence, as I said - just a little message in order not to forget myself the issue :)

Hey, sorry. I have been doing a million things and have been drowning in work but will get to it ASAP. I took some vacation for volunteer work :)

But it's on my radar, always has been. Don't worry.

Again. I have not forgotten about this. One day I will get it done. It's just there are so many things to do :(

All the edits from JhealdBatch (talk • contribs • logs) go through QuickStatements. I thought QS took care of throttling, to make sure it adjusted to what was sustainable, including how many batches it would try to run concurrently from each user, depending on overall load.

When I queue batches to "run in background" on QS, I have no control when QS will execute them. What am I supposed to do? When I execute these through QS, I am relying on QS's monitoring of the weather, and execution of the edits at a consequently appropriate rate.

I understood QS was well-behaved and did exactly this, throttling back when busy, but allowing more edits when load was less, and/or allowing individual users a larger fraction of its pool of edits when load was light and fewer users were using QS.

I have no manual control over this, having lined up the batches and given them to QS, so I'm at a loss to know what I can do better.

Unfortunately, I don't know the internals of QS to tell you what exactly you need to do but maybe put less batches in it? Wait two batches to finish and then add more?

I can unblock your bot if you're sure the bot won't edit like this again.

I've posted on Magnus's talk page, asking him to look into it (Topic:Vsjff5i2i7wmb0d9), but I really need him to look into it.

I'll close out the existing batches cautiously, one by one, and then leave it until I hear more. Thanks for the unblock.

The whole point of QS (at least for large jobs) is to be able to load it up a pile of batches and then to be able to leave it to get on with all them, as slowly or quickly as appropriate. So the edits can go through overnight while one is asleep, or during the day while one is doing something else, without having to be individually activated each couple of hours.

QS used to handle all that throttling very ably. If it now no longer capably doing so, I'll just have to wait until it can again. Thanks for spotting and catching this.

Thanks. I unblocked the bot. I think QS needs to have a cap on batches and process batches one by one, or two by two per user. That would solve lots of our issues here.

I thought that's exactly what it did do -- limit a user to two batches executing concurrently.

But it's just done 290 edits for me in a minute, just from a single batch active, so something is definitely wrong.

Some vandals are known to hijack existing items for other things, for example Q97272697. Please make sure your bot does not delete such kind of items.

Fixed.

Another thing is some pages are deleted then later restored - such items should not be deleted, but the sitelink should be restored, or if a new item is created, the item should be merged.

Also some pages are deleted then another page (probably a draft or /temp page, or a page with unrelated topic) moved to this name. They should be skipped to allow human review. Remember this bot is optional.

Hi! When your bot deleted Q97342854, it mentioned that its label was “Neugebäude”, but it didn’t mention that the previously deleted sitelink pointed to hu:Neugebäude (egyértelműsítő lap) (and not simply hu:Neugebäude). As the article was also deleted on Wikipedia, not even a search helps to find out what page and why was deleted; the only way I got to know the exact title is that I got a watchlist notification email when the sitelink was removed, and that mentions it. Could you please mention the sitelink itself in the deletion summary, with something like this?

Bot: Automatic deletion of an item that used to have a sitelink that is deleted and doesn't have any good statement, no backlink in main namespace and no sitelinks. Label: "Neugebäude", deleted sitelink: w:hu:Neugebäude (egyértelműsítő lap)

(By the way, there’s a typo in the current summary: it should be “deletion” instead of “deleton”.) Thanks in advance!

Thanks. I will fix it.

Should be fixed now. Thanks!

Your bot is deleting requests after 168 *minutes* after a request has been done. How am I supposed to take action on this? Now the items is gone, all evidence deleted without any human eyes checking on it. Don't you think that we should be able to get at least 8 hours of sleep, without the risk that during that time your items get nominated AND deleted? I believe 48 hours wait time would even be short. We are not all 24/7 available, and deleting an item is not of any life urging matter.

The delete is not based on deletion requests, the bot doesn't look at that at all and doesn't know when/if an item got nominated for deletion. It looks at empty items that have their sitelinks deleted in Wikipedia/sister projects.

Right.. for this case I still don't understand as it was said to be an iteam recently created with a sitelink to Hungarian wiki. My bot script usually makes items for nl-wiki, but maybe this was from a run over Hungarian templates/categories... but if it was really an empty item with previously a hungarian link, I can't care too much.

Another question... many lemmata that get deleted on xx-wiki, will still be relevant to Wikidata. How does your bot then decide what to keep and what to delete? In your explanation it reads like "no wiki, never relevant, delete everything you can". I do not agree with that approach.

The bot checks if there's no back link in main namespace too. It also checks if there's any statement on the item, if there's anything (beside P31 which doesn't bring any value on its own). Then it deletes them.

This is bot is active to reduce the workload of admins so they don't get overwhelmed by the tedius and large number of deletions.

I see. These additional restrictions to the delete criteria will do the trick indeed. Thanks for the clarification!

Hello again Ladsgroup, Some days ago, I saw Dexbot that archived talk page sections on fawiki. Now, Can Dexbot do this work for ckbwiki talk pages (especially, village pump sections)? We really need a bot to do that. Thanks!

Sure. Just copy paste the templates you see on the page (like this one on WP:VP):

{{کاربر:Dexbot/Archivebot
|archive = ویکی‌پدیا:قهوه‌خانه/گوناگون/بایگانی %(counter)s
|algo = old(10d)
|counter = 103
|maxarchivesize = 200K
|archiveheader = {{بایگانی شده}}{{جعبه بایگانی|ریشه=ویکی‌پدیا:قهوه‌خانه/گوناگون}}
|minthreadsleft = ۰
|minthreadstoarchive = ۱
}}

into your pages and it will automatically archives them.

I REALLY THANK YOU! but the above texts are in Persian. Can i translate persian texts to Kurdish (Sorani)? What about the parameters, can i translate them also?

The arguments can't be translated (as they are English even in Persian Wikipedia) the "User:" part should be translated "old(10d)" should not be translated (but it can be changed to like to 30 days instead of 10), "ویکی‌پدیا:قهوه‌خانه/گوناگون/بایگانی" and "{{بایگانی شده}}{{جعبه بایگانی|ریشه=ویکی‌پدیا:قهوه‌خانه/گوناگون}}" must be translated but not the "%(counter)s". Hope that helps.

Hope this would be useful for you: https://ckb.wikipedia.org/wiki/%D8%A8%DB%95%DA%A9%D8%A7%D8%B1%DA%BE%DB%8E%D9%86%DB%95%D8%B1:Dexbot/Archivebot

Thank you for creating ckb:بەکارھێنەر:Dexbot/Archivebot! I have created and updated the related pages. For now and a test edit, i added the following to ckb:ویکیپیدیا:دیوەخان (پێشنیارەکان).

{{بەکارھێنەر:Dexbot/Archivebot
|archive = ویکیپیدیا:دیوەخان (پێشنیارەکان)/ئەرشیڤی %(counter)s
|algo = old(1d)
|counter = 67
|maxarchivesize = 200K
|archiveheader = {{ئەرشیڤ}}{{بۆکسی ئەرشیڤ|root=ویکیپیدیا:دیوەخان (پێشنیارەکان)}}
|minthreadsleft = 0
|minthreadstoarchive = 1
}}

Is this correct? And is Dexbot work with ArchiveCloser gadget? Thanks!

I fixed the counter (67 -> 1) secondly, Are you sure any discussion older than a day would get archived? that seems pretty quick. In fawiki, it's 10 days.

It's Worked! See the three last edits here. I chose one day so I just wanted to see how the bot works and i reverted the bot's edits. I will set the better setting. Actually, because our community is so small, I set 20 days for now. I may have another question after translating the doc page if I had any questions. Finally, We (ckbwiki) really appreciate it. Warm regards!

Hey, Sorry for something slightly unrelated but can you take a look at https://phabricator.wikimedia.org/T259951 ? You added a CSS that broke things :D

Hello Ladsgroup, I left a message on phabricator. Thanks for the warning message.

Spammer

Why did you just delete the entire album Q97959243??!! Undo the deletion or I will report you to the admins for vandalism!!!!

Why did you delete the album?! What the fuck is wrong with you?! You're a terrible admin! You should be banned!

Hello Ladsgroup, I want to know how Dexbot added the good article badge for ڕەی فارکەھارسن and بەردە ڕەشەکە articles on ckbwiki? That is, how the process happened. Please ping me when you replied. Thanks!

They both are in this category :ckb:پۆل:وتارە باشەکانی ویکیپیدیا that is connected to :en:Category:Wikipedia good articles

Thank you for explaining it, but that category should contain good article's talk pages, not the article pages. The right category which contains good article pages is ckb:پۆل:وتارە باشەکان (en:Category:Good articles). Can you tell the bot to fix it?

It should be fixed now. Thanks!

Hi! Can I ask you a little favour? Could you merge fa:بروسوس and fa:بروص (کاهن)? Thank you very much!

Done!

I'm Fussi from Wikivoyage/de. We just noticed that your bot put badges to our articles on Wikidata. I have to admit, probably exceptionally one user we haven't been aware of that. One user has just found <nowiki> this bot edt. After a short period of nebulosity and a process of asking around we found out what happens and why. Your bot seems to badge our articles in this category as recommended article. FriedhelmW once contacted yous as well.

We think the current attribution ist wrong. Whe have six classifications. The right one sould be:

• complete articles badges good article
• recommended articles badges recommended article

We currently do not have ee special "excellent article" classification. The recommended category classifies our most comprehensive travel guides. Can you adapt the work of your bot to remvo wrong badges and set the new badges vor Wikivoyage/de in future? It may differ to the way, that other language versions handle their articles. And our [voy:de:Wikivoyage:Lounge#Valletta_-_Empfohlener_Artikel? current community feedback voy:de:Wikivoyage:Lounge#Valletta_-_Empfohlener_Artikel? current community feedback] is very limited, but almost empty articles like Aalen are definately not recommended. Thanks. Stay healthy. best wishes from Germany. -- DerFussi 09:04, 18 April 2020 (UTC)

Hey,

I'm sorry this is happening but this is just "Garbage in, Garbage out." The bot works based on interwiki links of that item and if you fix it, the bot should fix those automatically and if this doesn't fix it after a couple of weeks, let me know. Thanks.

Sorry. I do not understand. What kind of interwiki links? What interwiki link is responsible, that the German article about voy:de:Valletta was badged as recommended article? Waht should be done to remove any badges from the German article about Valetta?

I meant interwiki links of :voy:de:Kategorie:Brauchbare_Artikel but it seems that it's fixed now. Is there any new mistakes by the bot? The one that you showed is for six years ago.

Then the Bot should have removed the wrong badge on Valetta, right? Our Article voy:de:Worpswede was recently (two month ago classified as recommended article but its not badged. What is your bot looking for to decide what article is badged as good and recommended? (PS: I've fixed one link in my first message above). -- DerFussi 05:48, 20 April 2020 (UTC)

I'm not sure if my bot is active anymore (doing the badges) and as I said I don't remember its details. It was six years ago.