I've added tags for the main boards the SDC team monitors. We do monitor as many relevant boards as possible, but incoming SDC work across WMDE and WMF focuses mainly on these at the moment.

Any ideas on this one, Matthias?

This also happens on UploadWizard sometimes.

Upon further testing, although the image was able to proceed through the whole UI flow after I added several tags, those tags did not appear on the file itself as depicts statements (the file does have 1 existing depicts statement on it, but that shouldn't have caused an error, as there was no tag value collision)

Tested on production and works.

This is ready to be tested on production Commons.

This....kind of worked. On the Superbloom image I still got a "Something went wrong" message, but the tag submission still went through (for the first time, after months of failure). Further testing needed, but making progress.

The fix for this has been up on production for a while and appears to be working as intended

Tested on prod and works per the updated desired spec.

Based on discussions that Amir and Anne had, the expected result shifted over time but the main task description wasn't updated. I've updated that, and based on that it looks like this task does pass QA

@egardner does this look like something similar to what you've worked on recently?

For now, we just need the basics.

Hi Anne. Could you take a look at this again, re: the issue Ed found during testing?

This should be testable on Beta.

This should also be testable on Beta Commons now :)

This should be testable on Beta Commons now.

Tested on Beta and it works! Hopefully it works on prod :)

This is work that will be coming up soon. Best estimate for deployment is early Feb., but it could be earlier if things work out. We're a bit short-handed at the moment.

Yup. That one. I've updated the comment accordingly. Thanks. 👍🏼

This code was supposed to be merged, but it's still not working on Beta. The copy to all button appears but does not actually copy the data

Pinging @Addshore for potential insight on whether there are existing elements in the Wikibase code that will enable option #3 above. If not, things could get a little complicated.

Tested with URL statements with no "https://" prefix, error shows properly within the UI.

Hi! Sorry for the delay in response.

After looking into this, it appears that the problem is that English isn't being used as the fallback for British English, or it is being used but not before the user's other set languages. I looked through the Wikidata entities for many of the items in the screenshots that were in Dutch (platteland [aka "rural area", Q175185] and hoogvlatke [aka "highland", Q878223]), and they have English labels but no British English labels.

The scope right now is just for SDC.

Known issue (and unfortunately not an easy one to fix given that any solution must also work on mobile web), but we seem to have lost the original ticket we made for this so thanks for this one :)

This is actually a known (and old) issue with Wikibase Federation (see T221685). It's on our list of things to look at, but it's a tad tricky to find somewhere to store all the labels.

Assigning to Cormac for now since he's also looking into the edit conflict issue. The key point we're interested in investigating now is this stuff from @Pchelolo earlier:

Since we're not currently on this, let's move it back per Cormac's request

Also I don't think the map needs to be so big 🐳

Not to beat a dead horse, but #1 is how Wikidata does it (arbitrary number of maps and all)😄

Regardless of edit in place, even if I'm just deleting an old coordinate, it would remove a step from my workflow if I could see a map of that location right on the page so I know immediately it needs needs deleting 🌐

The map is used for input only.

Please also let me know by when do you want the updated numbers.

I'd prefer to see the existing analysis with the December numbers included so we can say more definitively "this is what 2019 looked like"

Hello! Thank you, Maya and Morten for doing this work. Looks good!

I think once the mobile tweaks are done, it'll be ready. I have some mild concerns about turning the map off by default, but let's give it a go.

@egardner how does it work on mobile? 😉

Works on production but let's keep an eye on it after the edit conflict bug is resolved.

Cormac to take a look for now.

I have not been able to replicate this, and I think the input process required to make it happen is an extreme edge case we don't need to worry about.

We're still exploring whether we need to search all Wikidata namespaces at once, but the original problem for this ticket has been solved long ago

This is now a feature of the Wikimedia Android App as part of the Suggested Edits feature set.

We moved away from using CleanChanges on SDC a while ago.

There are prominent CC0 notifications in multiple locations on Commons

This work was finished in 2019

The search prototype is not the direction we're going in and we've abandoned that approach.

Done and working on production.

This exists as part of WikibaseCirrusSearch: https://www.mediawiki.org/wiki/Help:Extension:WikibaseCirrusSearch#inlabel/incaption

We've done all the file page design adjustments we're going to do for SDC.

We've changed the way search works and this no longer applies

Enough time has passed and the SortedProperties page on Commons has a few statement orders put in place and they appear to work just fine on production, even on files edited a while ago.

Assigning this one to Edward for a more thorough look.

Input for this type is working on production. However, previously added URL qualifiers for statements with "somevalue" won't show up until phase 1 of T239172 is taken care of.

Both the original problem and the later one mentioned in the thread seem to have been fixed on production.

Tested on production (double checked on mobile) with length property. Works as expected. Still need to add unit support (which will be done via T239474 )

Confirmed working on production.

Tested on production and working as expected.

Thanks for that update to the page, James.

We did it!