Mostly interested in Wikidata
Tue, Jun 22
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.
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:
Is there a way to do “Changed claim: demonym (P1549) in Russian: бразильянка”?
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.
Mon, Jun 21
sorry, missed that it was already 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
( It has happened on Wikidata, but a separate merge property feature isn't really needed there).
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.
@Lucas_Werkmeister_WMDE are there some aspects you think are still missing? Or alternate solutions?
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.
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.
Sun, Jun 20
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.