Wikidata:Requests for permissions/Bot/BorkedBot 9

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Approved--Ymblanter (talk) 20:05, 6 March 2023 (UTC)[reply]

BorkedBot 9

BorkedBot (talk • contribs • new items • new lexemes • SUL • Block log • User rights log • User rights • xtools)
Operator: BrokenSegue (talk • contribs • logs)

Task/s: Import values of YouTube handle (P11245) based on YouTube channel ID (P2397) and vice versa.

Code: Will be a modifiation of the current youtube job (bot's github linked on the user page).

Function details:

For every page with YouTube channel ID (P2397) lookup the youtube handle and set it with a reference indicating it was inferred from the channel ID.
For every page with a YouTube handle lookup the YouTube channel ID (P2397) and set it with a reference indicating it was inferred from the YouTube handle.
I'm also going to change the existing job that sets social media followers (P8687) for youtube channels to also qualify the count with the current handle.

Hopefully making this request before the property is created isn't premature.

--BrokenSegue (talk) 06:56, 26 November 2022 (UTC)[reply]

For every page with a YouTube handle lookup the YouTube channel ID (P2397) and set it with a reference indicating it was inferred from the YouTube handle.

Do you check that the YouTube channel ID doesn't already exist on another item before adding it?

If so, I

Support Lectrician1 (talk) 05:30, 9 December 2022 (UTC)[reply]

@Lectrician1: I do not. Why should that be needed? There are some legitimate cases where a youtube channel would be associated with multiple items. Or at the very least we need a human to deconflict them. BrokenSegue (talk) 06:43, 9 December 2022 (UTC)[reply]

If someone just adds YouTube handle (P11245)tseries to an item as spam, well then:

It's likely wrong
A human has to delete it and the associated and duplicate-valued channel ID that BorkedBot would put on the item.

Lectrician1 (talk) 14:03, 9 December 2022 (UTC)[reply]

Let me see how feasible doing that is. It complicates the bot a lot and I do not do this kind of filtering elsewhere (for example I don't check for duplicates when adding follower counts). BrokenSegue (talk) 16:33, 9 December 2022 (UTC)[reply]

@Lectrician1: this request greatly complicates the bot and I'm not sure it's necessary. Can you support without this functionality? I don't think there are many cases this will apply to. BrokenSegue (talk) 18:00, 11 January 2023 (UTC)[reply]

@BrokenSegue Why is this so hard? It's just a simple ASK query that needs to be run whenever a channel ID needs to be added that is inferred from a handle... Lectrician1 (talk) 20:02, 11 January 2023 (UTC)[reply]

@Lectrician1: what is an ASK query? I currently use SPARQL for queries like this and that would be slow to have to do for every item i want to edit. BrokenSegue (talk) 20:07, 11 January 2023 (UTC)[reply]

An ASK query asks if a statement exists in the database and returns a boolean. Here's an example. I wouldn't be concerned that you have to do this for every item you edit since the constraint checker technically has to do that for every edit as well...

For any items the bot comes across where the channel item already exists, you can output those QIDs to a file and then later review them to fix them.

I'm just a supporter of data quality. Why automatically add bad statements when we have to ability not to? Lectrician1 (talk) 20:30, 11 January 2023 (UTC)[reply]

Ok. I'll check if youtube channel id is in use already using the ASK query and is so I won't populate it. BrokenSegue (talk) 20:40, 11 January 2023 (UTC)[reply]

Support, fixes a common mistake by new editors.--One-car funeral (talk) 20:06, 11 January 2023 (UTC)[reply]

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.