Change Details

As a query service user, I want the label service to produce useful labels, even when Wikidata editors start to remove labels in other languages that are redundant with the new `mul` language code (see parent task). Since the label service doesn’t do language fallbacks on its own – it just goes through the list in its parameters (`bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en"`) – it’s probably sufficient to add `,mul` to that list in the autocompletion suggestions and in the query examples? Feature request -> QS sync meeting via lydia

**Problem:** We will soon release the new `mul` language code on Wikidata (see T285156). We hope that the Wikidata Community will then start removing labels in languages with redundant strings and instead use the new `mul` language code. This might however prevent the WDQS from producing useful labels. (Wikidata itself will have a fallback chain that ends in the `mul` language code, so all functionality will stay the same within the project.) **Acceptance criteria:** [] We have a way to ensure that replacing labels in favor of the new `mul` language code will not harm the user experience on WDQS. **Open questions:** * Since the label service doesn’t do language fallbacks on its own – it just goes through the list in its parameters (`bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en"`) – it’s probably sufficient to add `,mul` to that list in the autocompletion suggestions and in the query examples?

As a query service user,**Problem:** We will soon release the new `mul` language code on Wikidata (see T285156). We hope that the Wikidata Community will then start removing labels in languages with redundant strings and instead use the new `mul` language code. This might however prevent the WDQS from producing useful labels. I want the label service to produce useful labels(Wikidata itself will have a fallback chain that ends in the `mul` language code, even when Wikidata editors start to remove labels in other languages that are redundant with the new `mul` language code (see parent task).so all functionality will stay the same within the project.) Since the label service doesn’t do language fallbacks on its own – it just goes through the list in its parameters (`bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en"`) – it’s probably sufficient to add `,mul` to that list in the autocompletion suggestions and in the query examples? Feature request**Acceptance criteria:** [] We have a way to ensure that replacing labels in favor of the new `mul` language code will not harm the user experience on WDQS. **Open questions:** -> QS sync meeting via lydia* Since the label service doesn’t do language fallbacks on its own – it just goes through the list in its parameters (`bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en"`) – it’s probably sufficient to add `,mul` to that list in the autocompletion suggestions and in the query examples?