User talk:FlickypediaBackfillrBot

Bot request

See Commons:Bots/Requests/FlickypediaBackfillrBot – I posted an initial draft of the proposal here for review by a few colleagues at the Flickr Foundation and Wikimedia Foundation, before posting it for community review.

Photos from Flickr which don’t have any SDC

As part of my work analysing the Wikimedia Commons snapshots, I've found ~950k files on Wikimedia Commons which:

• Have a Flickr URL somewhere in their Wikitext
• Don't have any Flickr information in their SDC

It would be beneficial to add SDC to these photos, but that's out-of-scope for FlickypediaBackfillrBot (at least for now).

It's comparatively difficult to tell the difference between, say:

• This photo is from Flickr.com: {flickr.com/…} where we would want Flickr info in the SDC, and
• For other photos of this same building, see {flickr.com/…}, where we wouldn’t want Flickr info in the SDC

I’d like to get to this at some point, but it’s out-of-scope for the initial version – it’ll need more manual intervention and care, for a comparatively small selection of photos. Alexwlchan (talk) 10:39, 2 November 2023 (UTC)

Blocked

Blocked Indefinitely

You have been blocked indefinitely from editing Commons. If you believe this block is unjustified, you may add {{Unblock}} below this message explaining clearly why you should be unblocked. For more information, see Appealing a block. See the block log for the reason that you have been blocked and the name of the administrator who blocked you.

Please request the bot flag. Thanks, --Yann (talk) 16:21, 18 December 2023 (UTC)

Hi Yann – I did [ request the bot flag (Commons:Bots/Requests/FlickypediaBackfillrBot), and I had a conversation from Schlurcher about it after my test edits. I thought everything was a-okay to go, but it sounds like I was meant to wait for something else to happen first?

Sorry if I was a bit quick off the mark! Alexwlchan (talk) 16:23, 18 December 2023 (UTC)

Unblock request granted This blocked user asked to be unblocked, and one or more administrators has reviewed and granted this request. Request reason: "Flickypedia Backfillr Bot approved. See Commons:Bots/Requests/FlickypediaBackfillrBot – this was approved last week. Sorry, I got confused about how the approval process works, and thought it was approved before it was! Alexwlchan (talk) 12:12, 11 March 2024 (UTC)" Unblock reason: "Unblocked by Krd on 6 March 2024. Yann (talk) 13:00, 11 March 2024 (UTC)" This template should be archived normally.

(Block log) (unblock) (Change local status for a global block) (contribs)

Notes from running the bot in practice

Now the bot is approved, I'm starting to run it in larger and larger numbers.

I thought it would be useful to note a couple of areas where it gets “confused” – i.e. where it can’t work out how to update the SDC, so it does nothing and just flags a warning for inspection.

• creator (P170) when there’s a non-Flickr user in there. e.g. there are files where the Flickr user is also a WMC user, they uploaded their own photo to WMC, and they put their Wikimedia username in the creator field. The bot only expects to see a Flickr user statement on Flickr photos, so it gets confused.
  It might be useful to add the Flickr username as an additional statement.
• creator (P170) when the Flickr user ID (P3267) field contains the Flickr "path alias" instead of the NSID.
  e.g. if the https://www.flickr.com/people/nasacommons account has the P3267 nasacommons instead of 44494372@N05.
  The P3267 field is already used quite inconsistently across Wikidata/WMC, and there’s an opportunity for more cleanup there.
• inception (P571) when the precision on the "date taken" hasn’t been mapped correctly from Flickr.
  e.g. the date taken on Flickr is 2024 but it’s been mapped as 1 January 2024.
  It would be useful to fix these, but right now I don't know if this is widespread enough to be worth automating, or whether they can be fixed with manual edits.

Plus a certain amount of link rot on the Flickr side – photos and photographers whose pages no longer exist (or are private), so the bot can't get a full set of metadata. In this case it adds a ‎Flickr photo ID (P12120) statement and nothing else. Alexwlchan (talk) 21:12, 12 March 2024 (UTC)

BOT flag

Appears that the BOT flag has not been set as the edits are not been marked as BOT edits in the watchlist, thus the "ignore BOT" option is not excluding the edits from the watchlist. Keith D (talk) 17:49, 16 March 2024 (UTC)

I just ran into this; my watchlist is impossible. mr.choppers (talk)^-en- 00:49, 17 March 2024 (UTC)

Hey both, thanks for the feedback, sorry for the disruption!

I'm a bit busy this week, so I've paused the bot until I can look at this properly. Alexwlchan (talk) 14:14, 18 March 2024 (UTC)

Hi both, thanks for the feedback!

I thought I was sending the API parameter to mark these edits as coming from a bot, but it doesn’t seem to be working correctly – I’ve popped a question on the village pump to find out what I need to change. Alexwlchan (talk) 11:56, 10 April 2024 (UTC)

Okay, I believe I’ve got this sorted and the bot is running again, setting the flag correctly. Thanks for letting me know! Alexwlchan (talk) 06:35, 9 May 2024 (UTC)

Please don't add Null coordinates

Please don't add Null coordinates, like on this edit.

Thanks HenkvD (talk) 10:01, 21 June 2024 (UTC)

Ooh, good spot! This seems to be a bug in the underlying Flickr data which I haven't seen before – this is the "location" data we get from the Flickr API:

<location latitude="0.000000" longitude="0.000000" accuracy="16" context="0">

I’ve paused the bot until I can fix this, and I’ll change it to ignore location data on photos with null coordinates.

Tracked here: https://github.com/Flickr-Foundation/flickypedia/issues/461 Alexwlchan (talk) 06:58, 22 June 2024 (UTC)

Thanks for pausing your bot until it is fixed. I have removed the incorrect Null coordinates. HenkvD (talk) 17:21, 22 June 2024 (UTC)

I've fixed the bug, and run the bot in a one-off test against that file – it no longer tries to write any location data.

This should avoid adding null coordinates in any future edits, and I've made a note to look for any other null coordinates already-written as a separate task. Alexwlchan (talk) 08:45, 24 June 2024 (UTC)

I found a few (only 3) cases where the bot added Null coordinates (on July 1st). See this one and this one and this one. There is no need to stop your bot, but maybe you can have an other look. HenkvD (talk) 14:52, 9 July 2024 (UTC)

Thanks for spotting! I see the issue – I was being overly restrictive in my filter for null coordinates on Flickr, and not catching these. Easy fix: https://github.com/Flickr-Foundation/flickypedia/pull/490 Alexwlchan (talk) 11:09, 10 July 2024 (UTC)

Thanks for fixing. I have not spotted any since. HenkvD (talk) 18:14, 21 July 2024 (UTC)

Bot editing logged out

Hi, looks like FlickypediaBackfillrBot has sometimes been edited logged out as 92.14.15.136 and 81.131.37.170. You might want to use the assert parameter on your request to check if the bot is currently logged in. Thanks! --Nintendofan885^{T&Cs apply} 11:32, 7 July 2024 (UTC)

Ah thank you!

Yes I spotted that – the login credentials I was using expired. I was wondering if that assert-like behaviour was possible, but I couldn't see anything in the <code>wbeditentity</code> API docs. Thanks for the pointer, I'll definitely add that! Alexwlchan (talk) 09:36, 8 July 2024 (UTC)

Delete my historical edits on vikidia and wikipedia because it is inadmissible and unacceptable

ΣΥΡΙΖΑ un sitio de vikidia, búscalo tú mismo, lo verás, está en vikidia y me gustaría que elimines ciertas modificaciones históricas y un resumen de modificaciones y contribuciones. GRACIAS 81.248.177.61 11:41, 18 August 2024 (UTC)