Here's a question – where do the units come from? Are we using a hard-coded list, or somehow fetching a list of appropriate units based on the property? Units will also be property-specific (a "length" property will have different units from a "weight" property).

To echo what @Ramsey-WMF said, the read-only/delete-able label for somevalue is a short-term solution. We understand that this feature is important and plan to support it eventually, just as we are working to enable support for the various other types of statements (https://phabricator.wikimedia.org/T233036). We plan to roll out support for new types as they are ready but this is something that will begin happening soon.

I opened a new subtask for the specific issue of updating the FormatValue element and related logic. I have a WIP patch for it as well (still trying to figure out how to implement the changes on the PHP side): https://phabricator.wikimedia.org/T239552

From a technical perspective, it's probably easiest to add support for both special values at once (though this will depend somewhat on the proposed UI).

This assumes that constraints for Wikidata are the same as constraints as for Commons. I don't think this assumption will hold. For example on Commons we currently don't add P31 (instance of) yet. So every item with a creator will get a constraint violation. See for example https://commons.wikimedia.org/w/index.php?title=File%3ATerWorm.jpg&type=revision&diff=374654987&oldid=365995523

In T239163#5691308, @Multichill wrote:

Where do you plan to store the constraints? Currently the constraints are on Wikidata on the properties.

@PDrouin-WMF here's what I was thinking for an updated input UI here (this would actually apply to all "string" types: URL, external-identifier, plain string, maybe monolingual-text).

Here's a question about this datatype RE: acceptance criteria.

We have the ability to display these properties in a very basic way right now, but we have not enabled yet because we are working on updating the UI. Most of the team's energy has been focused on getting the machine vision tool out, but that work is mostly complete now so I'm hoping we can improve the situation here shortly.

The widgets in the WikibaseMediaInfo extension use templates and render() methods to ensure that the visible UI remains in sync with the structured data as it changes. Existing DOM elements are often thrown out and re-rendered from scratch to ensure consistency. Our introduction of this workflow into the Captions widget is probably what initially broke this gadget.

@Krinkle WikibaseMediaInfo is not being actively monitored as far as I am aware; I'll bring this ticket (as well as the question about the best way to handle issues like these) to the attention of the rest of the team.

I've updated the "bundled view" to not be expandable per @Ramsey-WMF's suggestion – the concern is that batch uploaders may be confronted with way too much information if we show a line for each individual file.

Ok, made some progress on this. Here are some screenshots of the current appearance/behavior of notifications:

Hi @ArielGlenn – we were talking about this recently within the team, and we agree that the docs should be expanded and improved. Thanks for putting a draft together.

I'm going to see how far I can get following these guidelines: https://m.mediawiki.org/wiki/Extension:Echo/Creating_a_new_notification_type

External Identifier property datatypes correspond to string value types, so (basic) support for these types is enabled via: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. Some UI work will be necessary to improve the experience.

Support for String, Quantity, and URL datatypes is introduced here: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. Follow-up patches will introduce support for more exotic datatypes.

Quantity datatype support is introduced in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253, but some updated UI designs are needed to improve the user experience.

Support for URL property types is added in this patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/542253. But we're going to need to do a little UI work to improve the user experience before this is really ready for production.

Here's a screenshot of the datatypes that we'll be able to start supporting once this patch gets merged.

I'm not attending TechConf this year, but the lack of a common, well-supported local development environment has been a huge pain point during my time here.