Maybe the implication for new codes in general is that if Incubator follows them, they can take whatever measure they deem necessary.

T262922 links a sample in its task description. If you can do one or several similar ones, that would be sufficient.

Interesting find.

second thoughts: maybe the mismatched value column could be empty too.

Maybe handling of empty columns should be mentioned (e.g. ok for additional columns, nok for key and mismatched value column)

So DB1 and Wikidata have the same key and some different values for a property.

@Lydia_Pintscher on some of the open points:

• what's your view on the triage of tickets? Do you want to do it? Are the various boards/statuses fine with you? There was some debate about it at T168295#7165601
• how long should it take on Contact_the_development_team?
• are there are others we should enhance/complete?

Is there a way to do “Changed claim: demonym (P1549) in Russian: бразильянка”?

In T168295#7168437, @Nikki wrote:

Because you were wrong to add it. There's been no decision on how to implement it, therefore it's not ready for someone to submit a patch.

Developers are free to provide patches .. there is no requirement for you to decide on it

I'm looking for the ticket that defines "mismatch". Will it be this one?

So this is no longer needed?

@Nikki We are moving ahead .. it's WMF .. so we are going two steps forward, then one step back.

Thanks for looking into this.

sorry, missed that it was already done.

done

I don't see why these should be revision deleted. There are plenty of revisions with data that doesn't match the current format. What is so different about these?

renamed it to "disallow". Seems closer to the reporter's intent

In T273705#7165738, @Aklapper wrote:

maybe incubator shouldn't allow it.

What is "it"? What do you expect to happen?

( It has happened on Wikidata, but a separate merge property feature isn't really needed there).

@Lucas_Werkmeister_WMDE If you have no view on this, why did you remove the patch-welcome tag ?

@Aklapper following T284276 we try to have them available within a week. (A patch here being one or two added or changed lines in a configuration list)

An alternate way to implement this could be to create a new wiki and import the database there.

Is there are way to see how this was prioritized each quarter (or year) over the past decade?

@Aklapper The due date would have been for the (trivial) patch.

@Aklapper I guess that makes sense on some level.

@Zordsdavini I did list some of the progress above (see the description). I see @Hugo.arg is still active as well.

@Lucas_Werkmeister_WMDE are there some aspects you think are still missing? Or alternate solutions?

Can we add this to https://gerrit.wikimedia.org/g/mediawiki/extensions/Wikibase/+/ccacae57f44bb5f4a85168116ccb3b076bb56560/repo/config/Wikibase.default.php#199

Great. The sample on Wikidata went from red to blue.

Changed status given the lack of samples and set priority accordingly.

I updated the task accordingly.

@Jakob_WMDE I'm changing status to "stalled" given that it's unclear if anything is still needed.

changing status to "stalled" given that it's unclear if anything still needs to be done. Also, adjusting priority accordingly.

@hashar can you explain why you set priority for this to lowest ?

I think "mul-<script>" would be preferable.

In T245927#7164866, @Nikerabbit wrote:

I updated the task for LocalNamesRu.php and added the usual one week for patches as due dates

That's not how they are used. Please don't add Due dates for tasks you are not working on yourself.

Based on T285076#7164202 . Seems I asked them for review/input by error.

Based on T285076#7164202 . Seems I asked them by error.

seems to be ready to go. I add the usual one week for patches as "due date".

I updated the task for LocalNamesRu.php and added the usual one week for patches as due dates. It may still be fixed/communicated to CLDR as well.

Ideally we would have a list here of language names in Dutch you feel are missing, similar to "pt-br" mentioned above.

I updated the task accordingly and set the one week for the patch as "due date".

Seems to be ready to go. Request is consistent with Choctaw (Q32979).

here is one: https://www.wikidata.org/wiki/Q847664#P1476 and probably the name for every Spanish institution.

Set the due date given the usual one week timeframe for patches.

In T285076#7164095, @agray wrote:

Do we have a list of *all* language codes with a sco translation? I'm happy to go through the rest of the list to check, I'm just not quite sure where to find it.

In T285076#7164202, @Amire80 wrote:

While it's good to have more review on language configuration, I'm actually not sure why is the Language committee mentioned here at all. I don't think there's a rule about it ;)

Ok. One of its members was involved when these were first defined ( T162406), but I wont ask going forward. I will update T284915 as well.

This is probably somewhat of topic: Instead of trying to fine tune manually what goes into "depicts" (see Special:SuggestedTags), wouldn't it be more interesting to make this queryable by adding them into a new property on a large scale?

I removed the toke as somehow I thought the third party server was only for testing, not for the actual update of the feature.