-
Notifications
You must be signed in to change notification settings - Fork 89
Open
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.performancethe way Scholia treats the machines using itthe way Scholia treats the machines using itqleverIssues related to how Scholia interacts with QLeverIssues related to how Scholia interacts with QLevertools+workflowsabout ways in which Scholia integrates with WikiCite curation workflowsabout ways in which Scholia integrates with WikiCite curation workflows
Description
The current Scholia setup is
- https://scholia.toolforge.org/ with a full-graph real-time Blazegraph backend currently scheduled to be switched off on January 20
- https://qlever.scholia.wiki/ with a full-graph real-time QLever backend, both hosted on servers of the University of Freiburg
We want to migrate this such that the Toolforge-hosted version is using a full-graph real-time QLever backend hosted on Wikimedia servers, for which we have a test system (wikiqlever) running on Wikimedia Cloud Services.
In order to get there, I suggest the following steps:
- Set up a copy of the current https://scholia.toolforge.org/ at https://scholia-blazegraph.toolforge.org/ #2767
- Set up a Toolforge copy of the QLever-based Scholia at https://scholia-qlever.toolforge.org/ #2768
- Set up a Toolforge copy of the QLever-adjusted Wikidata Query Service UI #2774
- Switch https://scholia-qlever.toolforge.org/ to using wikiqlever as the QLever backend #2769
- Test https://scholia-qlever.toolforge.org/ for traffic-related issues #2770
- Set up copies of wikiqlever as needed, along with some load balancer #2771
- OPTIONAL:
- If https://scholia-qlever.toolforge.org/ is stable, move its code to https://scholia.toolforge.org/ #2772
- keep https://scholia-qlever.toolforge.org/ for testing purposes and perhaps as a staging server
- keep https://scholia-blazegraph.toolforge.org/ for documentation purposes as long as Wikidata is still maintaining its Blazegraph endpoints
- keep https://qlever.scholia.wiki/ for testing purposes and as a backup in case of Toolforge issues
- Set up some mechanism that can redirect traffic from https://scholia.toolforge.org/ to https://qlever.scholia.wiki/ if needed #2773
- closely monitor the setup for some weeks and tweak as needed.
This is part of
Metadata
Metadata
Assignees
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.performancethe way Scholia treats the machines using itthe way Scholia treats the machines using itqleverIssues related to how Scholia interacts with QLeverIssues related to how Scholia interacts with QLevertools+workflowsabout ways in which Scholia integrates with WikiCite curation workflowsabout ways in which Scholia integrates with WikiCite curation workflows