I have a hunch that a separate message might be needed because it probably causes issues for translation otherwise due to the plural vs singular.

That makes sense to me.

In T411650#11429346, @Lucas_Werkmeister_WMDE wrote:

Wikibase has a few different configurations for tags: viewUiTags, termboxTags, specialPageTags, and updateRepoTags. Should we introduce a new configuration for this, or is it sufficient to apply the viewUiTags? (In Wikimedia production, viewUiTags and specialPageTags are the same, while termboxTags additionally configures the “termbox” tag.)

Update: temporary accounts are now live on Wikidata

I am leaning towards edit conflict.
Adding @Ifrahkhanyaree_WMDE also to check what the REST API does in this case. Or is that even a thing there? 🤔

Works great now. Thank you!

I think not at this point.

In T132690#11332687, @TiagoLubiana wrote:

Some of the examples are not showing up and we are not quite sure where the bug is. It is described in more detail here:

https://www.wikidata.org/wiki/Wikidata_talk:SPARQL_query_service/queries/examples#Internal Federation queries not appearing on the Query Service examples

Should I open a new ticket? It may be something very simple, but I am just not seeing it

Sounds good, yeah.

but this is perhaps good enough for now

👍

Good catch. Reopening so that last piece can be fixed.

Yes! Thank you.

It turns out there were sockpuppets involved in these discussions. That means we will not convert them until further support is shown. The exception is Cyclocross24 rider ID (P13724).

Current state of things on the new mobile version: https://www.wikidata.beta.wmcloud.org/wiki/Q424242?uselang=he

Poke about this. What's the status?

@ChristosV_WMDE @Christos_WMDE Can you reach out to them to fix their certificate?

No. Thank you!

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

Closing all tickets for the Reference Treasure Hunt since we will probably not revive it as-is.

@jhsoby @Amire80: Ok from your side?

In T405475#11218270, @dcausse wrote:

• Searching items: e.g. Q2 -> Earth is displayed, @Lydia_Pintscher have you seen cases where only the QID was displayed?

Yeah

Here is how I believe it should behave: It should follow what we do for Items and Property searches. This means specifically:

• The label and ID of the EntitySchema is shown as the header of the search result (This is already working fine it seems)
• The description of the EntitySchema is shown as the body of the search result. If no description is available then the body content is empty
• Both of these are shown in the language of the interface

Additional info: when testing this we also saw issues for Items, not just Lexemes.

@Lupascriptix This is likely the same underlying change but unrelated to this ticket. The OpenRefine team recently made a new release to address some of the issues: https://github.com/OpenRefine/OpenRefine/releases/tag/3.9.5#sq_i504e0cyt9 If that doesn't fix it or you I recommend opening a ticket there.

Yes what Adam says.
Given that right now the search only supports entities, let's leave out the main namespace if it doesn't contain Items. We have T396865 for adding non-entity namespaces to the dropdown. So let's handle that separately there.

Yes, let's!

No. Can be closed.

Yes can be archived

Done :)

Closing this. We have subtickets for the remaining pieces so I don't think we need to keep this open.

Actually not quite what the task is about but similar

@Addshore has done this here: https://addshore.com/2025/08/wikidata-instance-of-and-subclass-of-through-time-p31-p279/ Maybe we can turn this into something regular?