multiple datasets, default dataset, UI datasets dropdown select

[rat10]

I have two local datasets each running it's own docker instances of Qlever and Qlever-UI. I tried to configure them with the same ports in the respective Qleverfie but the second one wouldn't start. So I gave the second one different ports and open the UI in a different browser window. Is that how it's supposed to be - each dataset its own containers for database and UI - or am I missing something?

In the Qleverfile I tried to name the UI like my dataset, e.g.

[ui]
UI_CONFIG          = myDataset

but that was rejected (so I used default). Of course, this is mainly a cosmetic issue, just asking.

In the web UI I can't have all my datasets in the dropdown menu. Again, mostly a cosmetic issue but probably related to the questions above, and maybe there is an easy fix?

[hannahbast]

@rat10 Yes, each database should be in its own folder with its own Qleverfile and own port.

The qlever ui command is currently only suited to quickly fire up a UI for a single QLever instance. If you want a persistent UI for multiple instances, like on https://qlever.cs.uni-freiburg.de, you should clone https://github.com/ad-freiburg/qlever-ui in an own directory and then configure your backends in the UI (on the top right: Resources -> QLever UI Admin). These changes are persisted in this file https://github.com/ad-freiburg/qlever-ui/blob/master/db/qleverui.sqlite3 .

It's not really hard. Please feel free to give it a shot and play around and let us know if you have questions. It is on our TODO list to write documentation for this use case (the README.md in the repo is a bit out of date).

[rat10]

@hannahbast Thank you for the clarification! It is not a pressing need for me, so I'll probably not play with the source anytime soon, but thanks for the pointer.