@Jdforrester-WMF we're good to go anytime. Thanks!

Anne to look into this and see how much effort is involved in the fix.

Assigning to Cormac for another code review look.

Thanks! I'll defer to @matthiasmullie on that.

This patch has been approved and merged (you can test it on Test Commons now), but it won't reach real Commons until next Wednesday, due to a split rollout because of the holiday (US Thanksgiving).

Works on prod.

Tested, works.

works as designed on prod

We moved away from the old design a while ago, current redesign is reflected in current code.

Works on prod

assigning this to Pam for confirmation that we're good here :)

Just to be clear here - we currently have no plans to bring this in-house. Developer time is scarce and there are many things taking higher priority.

Matthias will look into discrepancies between number of files with mediainfo slots vs. what's indexed in Cirrus.

Per the MachineVision Concept Review (T227591), can we confirm that WMF-Legal's review of the extension/service was completed? Is there any corroborating documentation or a new privacy policy/ToU we could reference and review?

Okay. So what I'm guessing is that the functionality implemented for T224604 isn't compatible with Chrome on at least some Android devices (seems to work fine on iOS.). Gonna throw this over to @egardner for further insight.

@Astinson Hello. Just to clarify: this is an issue when attempting to select an entity listed in the autosuggest text box when you start typing?

This would be a neat feature, but perhaps too clever for where we are now. We just have to get the thing working, and we haven't even put it on test Commons yet 😸 I suggest we keep things simple and focus on making base functionality as clean as possible.

Either @egardner or @AnneT (or both) will tackle this after CAT tasks are finished. Open question of whether our map tools are ready for this.

Can be reproduced

pinging @Cparle and @Mholloway for code review when this is ready (later this week probably).

Tested on prod and works.

@matthiasmullie On production, this half works. The Copy to All files button does appear, but when clicking it to apply statements, those statements do not appear on the other files

Tested. Works.

This has been working for a while, just slipped through the VoP cracks.

Tested on production and works as normal once again.

However! Any depicts-specific or wiki-specific things (descriptions, links) is also quite tricky, because we have this thing on multiple wikis, in multiple different configurations and hard-coding things for a 'depicts/production commons' configuration is not ideal (not impossible, just "let's make sure we *really* need this")

Per discussion today:

Per discussion today:

Assigning to Cormac for now so he can assess.

Assigning to Cormac for now so he can assess.

Additional info:

There are two goals for the call to action in UploadWizard, one main one and one "stretch"

Tested on production! Works!

Heads-up - we're going to start addressing some of these issues soon, but there's a refactoring patch that has to go out first (https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/WikibaseMediaInfo/+/528825/).

We'll add a check to the captions field that ensures it's at least 5 characters long (the same rule as Descriptions has)

In T234250#5535274, @Mholloway wrote:

@Ramsey-WMF Where did we come down on excluding images with existing depicts statements? IIRC, we were leaning toward including them anyway.

@MarkTraceur @matthiasmullie - per discussion in backlog grooming today will research increasing the edit rate limits on Commons to reduce the odds of this error happening

@Mholloway thoughts? Beta is pretty borked right now 😿

Hi @EBernhardson Did you intend that patch for this task, or T231038 ?

Tested on production with multiple protected files using multiple transclusions. All good.