GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [epic] Scholia transition to a QLever backend · Issue #2756 · WDscholia/scholia

[epic] Scholia transition to a QLever backend #2756

New issue
Copy link
New issue
Copy link
Open
Open
[epic] Scholia transition to a QLever backend#2756
Copy link
Labels
documentationhopefully helpful explanations of how things workhopefully helpful explanations of how things worklegacy-replacementTag for SPARQL query validation and determination on which WDQS the query should run.Tag for SPARQL query validation and determination on which WDQS the query should run.qleverIssues related to how Scholia interacts with QLeverIssues related to how Scholia interacts with QLever

Description

@Daniel-Mietchen
Daniel-Mietchen
opened on Dec 14, 2025
Issue body actions

In light of the Wikidata Query Service split that came into effect earlier this year, we're actively working on transitioning Scholia to a QLever-based setup. Relevant documentation is spread across multiple places - some public, some not - and this ticket is meant to facilitate getting or keeping an overview of this transition.

Some key points:

  • An experimental fork of Scholia has been deployed at https://qlever.scholia.wiki/ based on code in https://github.com/ad-freiburg/scholia/tree/qlever . This is very actively being developed and very likely to change in significant ways until mid-January 2026.
  • We have the legacy-replacement and qlever labels here as well as the issues at https://github.com/ad-freiburg/scholia/issues and the QLever home repo at https://github.com/ad-freiburg/qlever with its issues at https://github.com/ad-freiburg/qlever/issues .
  • It is as yet unclear whether and especially how Wikidata as a whole or any other Wikibase instances are going to replace Blazegraph any time soon. Scholia's experience can inform the relevant discussions.
Reacted by Egon Willighagen and Nizo Priskorn

Activity

  1. Daniel-Mietchen
    added
    documentationhopefully helpful explanations of how things workhopefully helpful explanations of how things work
    legacy-replacementTag for SPARQL query validation and determination on which WDQS the query should run.Tag for SPARQL query validation and determination on which WDQS the query should run.
    qleverIssues related to how Scholia interacts with QLeverIssues related to how Scholia interacts with QLever
    on Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationhopefully helpful explanations of how things workhopefully helpful explanations of how things worklegacy-replacementTag for SPARQL query validation and determination on which WDQS the query should run.Tag for SPARQL query validation and determination on which WDQS the query should run.qleverIssues related to how Scholia interacts with QLeverIssues related to how Scholia interacts with QLever

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.