How fils/qleverflow works
This repository is primarily an exploratory QLever deployment toolkit: an operator configures local or Portainer stacks and serves graph datasets through QLever, with the UI and Petrimaps as companion services. Its other product branches are example catalogue Qleverfiles, SPARQL query collections, a free-text search UI, an MCP query server, and SHACL validation utilities. The validation flow is visible in sampled source; several deployment and catalogue details are documented only at a high level, so their wiring is not expanded beyond that evidence.
Main entry points: validateToOxigraph.py Validation Runner · validateToLance.py Lance Validation · docker-compose.yml Compose Stack · client.py Text Search UI
Components 23
Deployment
- Compose Stack
deployment/docker-compose.yml - QLever Services
deployment/qlever_services.yaml - QLever Server
- QLever UI
- Petrimaps
Graph Catalogues
- Dataset Qleverfiles
catalogues - Graph Data Products
catalogues/README.md
Search and Query
- SPARQL Queries
queries - Text Search UI
ui/client.py - Usage Information
ui/defs/usage_info.py - Query Preparation
ui/query_prep.py - MCP Query Server
mcp/server/main.py - QLever MCP Client
mcp/agent/qleverClient.py
SHACL Validation
- Validation Runner
validation/shapeValidator/validateToOxigraph.py - Dataset Discovery
validation/shapeValidator/defs/getGraphs.py - Graph Construction
validation/shapeValidator/defs/getConstruct.py - Shape Reader
validation/shapeValidator/defs/getShape.py - SHACL Validation
validation/shapeValidator/defs/shaclValidator.py - Validation Result Store
validation/shapeValidator/validateToOxigraph.py - Lance Validation
validation/shapeValidator/validateToLance.py - LanceDB
validation/shapeValidator/validateToLance.py - SHACL Shape Files
validation/shapes
Other components
- Operator
Connections 22
- Operator → Compose Stack: deploys
README.md - Compose Stack → QLever Services: configures
- Compose Stack → QLever Server: provides
README.md - Compose Stack → QLever UI: provides
README.md - Compose Stack → Petrimaps: provides
README.md - Dataset Qleverfiles → Graph Data Products: describes
README.md - Text Search UI → QLever Server: queries
ui/client.py - Text Search UI → Usage Information: renders
ui/client.py - Query Preparation → Text Search UI: supports
- MCP Query Server → QLever Server: queries
mcp/server/main.py - QLever MCP Client → MCP Query Server: connects
- Validation Runner → Dataset Discovery: discovers
validation/shapeValidator/validateToOxigraph.py - Validation Runner → Shape Reader: loads
validation/shapeValidator/validateToOxigraph.py - Validation Runner → Graph Construction: constructs
validation/shapeValidator/validateToOxigraph.py - Validation Runner → SHACL Validation: validates
validation/shapeValidator/validateToOxigraph.py - Validation Runner → Validation Result Store: loads results
validation/shapeValidator/validateToOxigraph.py - Shape Reader → SHACL Shape Files: reads
- Lance Validation → Dataset Discovery: discovers
validation/shapeValidator/validateToLance.py - Lance Validation → Shape Reader: loads
validation/shapeValidator/validateToLance.py - Lance Validation → Graph Construction: constructs
validation/shapeValidator/validateToLance.py - Lance Validation → SHACL Validation: validates
validation/shapeValidator/validateToLance.py - Lance Validation → LanceDB: opens table
validation/shapeValidator/validateToLance.py