Document the workflow for customizing a local QLever instance based on Wikidata dump

[Daniel-Mietchen]

At a hackathon this weekend, @WolfgangFahl has set up a local QLever instance based on the current Wikidata dump. It works well for our main purpose (testing Wikidata-related queries) but we have not yet figured out how to customize our instance.

Landing page Freiburg:

Landing page Aachen:

No major differences except for the Format/ Reset button, and we would like to customize the footer.

Index Information Freiburg:

Index Information Aachen:

Here, we are clearly lacking information but haven't figured out how to get the relevant information to display there.

Backend Information Freiburg:

Backend Information Aachen:

Again, not much of a difference there, except for the ask command.

Thanks for any pointers.

[hannahbast]

@Daniel-Mietchen and @WolfgangFahl: Thanks for the feedback. Some comments/questions:

1. Did you use the the qlever CLI aka qlever script with the pre-configured QLeverfile for Wikidata? if yes, everything should have just worked out of the box. Please let us know if you encountered any problems. If you did, I would like to find out whether you did more work than necessary (people sometimes do that) or if there are some bugs on our end.

2. The functionality for the "Format" button is in Query formatter qlever-ui#103, which is not merged yet because of some nitpicks. If it is important for you, you can just merge it yourself for your instance. We will also merge it soon.

3. Exactly what is it that you want to customize? Are you aware that there is a configuration for each backend, which you can customize by clicking on "Backend information" and then "Edit this backend"? The layout of the page is currently not customizable, but it is very easy to modify the template files, which are in https://github.com/ad-freiburg/qlever-ui/tree/master/backend/templates

4. You can set the description for the index and the text index in the Qleverfile. The respective variable names are DESCRIPTION and TEXT_DESCRIPTION.

5. ASK queries are not yet implemented, but will be very soon. There is already a PR that works: Implement ASK queries #1562