Top-level configurable

[egonw]

Is your feature request related to a problem? Please describe.
This is related to the ongoing developments around splits and integration with the UIs for queries, like WDQS.

See also:

• convert templated queries to named queries and separate concerns by introducing named query middleware #2412
• egonw@2015287
• https://github.com/egonw/scholia/commits/exploration/qlever/

Describe the solution you'd like
We need in both Python and JavaScript global URLs for the following things:

• run a SPARQL remotely and get the results table back (used for aspect tables)
• link to the QS to embed graphics in the iframe
• link to the QS to edit (and run) the SPARQL there

I think these three templates need to have a paramater (like $sparql) where the encoded SPARQL is embedded.

Describe alternatives you've considered
The current solution is to have these URL patterns hardcoded all over the place. This makes it hard to maintain and update Scholia for other endpoints (like Qlever).

[egonw]

@fnielsen, @Daniel-Mietchen, please let me know what you think a patch to do this should take into account.

[fnielsen]

Yes. Long time ago we an issue or PR.

[egonw]

Yes. Long time ago we an issue or PR.

@fnielsen, can you help me out? I can find the following related queries, but none capture this issue (fully):

• there are 49 places where the sparql endpoint URL is given #2250
• Test Scholia queries on other SPARQL endpoints #2063
• Look into QLever as a potential query engine for Scholia #1774

[fnielsen]

Yes. I think it would be fine with a configuration. I have previously used the config module: https://github.com/fnielsen/brede/blob/master/brede/config.py