Page MenuHomePhabricator

[BLZMI] Create informational banner for the qlever qs-gui
Open, Needs TriagePublic

Description

As a user
I want to know how to use the qlever instance of the qs service gui (and understand why my labelservice queries do not work on qlever
so that I can write my queries correctly

a/c

  • The information banner is updated
  • The information is presented in the user's selected language (UniversalLanguageSelector) if the translation is available
  • tests updated as needed

Text for the banner:

Welcome to the QLever version of the Wikidata Query Service.

QLever uses the same SPARKL language as Blazegraph; however, it does not automatically include prefixes or the labelservice. You will need to update your queries accordingly.

Need the Blazegraph version? Visit query.wikidata.org

Details

Related Changes in Gerrit:
Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Remove unused code from the Banner classrepos/wmde/wikidata-query-gui!70thiemowmdebannerUnusedmain
Preparation for QLever deprecation and migration bannersrepos/wmde/wikidata-query-gui!69thiemowmdebannerTypesmain
Customize query in GitLab

Event Timeline

The "why" seems obvious - the WDQS label service is a non-standard construct that violates the assumptions built into the SPARQL SERVICE construct.

karapayneWMDE renamed this task from [BLZMI] Handle lack of labelservice to [BLZMI] Create informational banner for the qlever qs-gui.Jul 21 2026, 9:53 AM
karapayneWMDE updated the task description. (Show Details)
thiemowmde moved this task from Backlog to Doing on the Wikidata Query UI board.
thiemowmde moved this task from Incoming to The Board on the Wikidata-Omega board.
thiemowmde edited projects, added: Wikidata-Omega (The Board); removed: Wikidata-Omega.
ArthurTaylor updated Other Assignee, removed: thiemowmde.
ArthurTaylor subscribed.

Change #1314633 had a related patch set uploaded (by Arthur taylor; author: Arthur taylor):

[operations/deployment-charts@master] wikikube/wikidata-query-gui: Bump to latest version

https://gerrit.wikimedia.org/r/1314633

Change #1314633 merged by jenkins-bot:

[operations/deployment-charts@master] wikikube/wikidata-query-gui: Bump to latest version

https://gerrit.wikimedia.org/r/1314633

The "why" seems obvious - the WDQS label service is a non-standard construct that violates the assumptions built into the SPARQL SERVICE construct.

The label service has been an established, well-documented and widely used feature of the Wikidata Query Service for many years. I continue to find the idea of not supporting it absurd.

Regarding the message I am not so sure we need to update the people on the names of the backends.

I would say something similar but leave them out:

Welcome to the new version of the Wikidata Query Service!

Similar to the old version, you can query Wikidata using SPARQL. However, this new version does not automatically include prefixes or the labelservice in your queries. To learn how to update your queries for the new Wikidata Query Service, visit our helpful guide here: [link]

For a limited time, you can still access the old version here: query.wikidata.org

The "why" seems obvious - the WDQS label service is a non-standard construct that violates the assumptions built into the SPARQL SERVICE construct.

The label service has been an established, well-documented and widely used feature of the Wikidata Query Service for many years. I continue to find the idea of not supporting it absurd.

This is getting a bit far afield from the banner.

I think there are two separate issues. One is whether the UI will support something like the query service. The other is whether the underlying system will support the query service. The former is, I think, in the hands of WMDE. The later is defintely in the hands of the platform team.

I think it would be reasonable to have the UI support an invisible, or mostly invisible, label service. The QLever UI even used to have this. What would be nice is if the UI had an option to show how to add label components to queries so that (the small fraction of?) users who wanted to convert their UI queries to programmatic queries could see how this can be done.

Is there somewhere I can check this that is live?

Until the site becomes publicly accessible, you would need to access it using the user agent (outlined in the 'cors proxy' section of our doc). But I'll get a screenshot of what it looks

{F100212114}

{F100212119}