This all sounds very reasonable. I'm happy that there are already standard procedures to set up a proxy. I had expected this would be manual work via a toolforge instance - please forget everything I said about this.

OK, pm20database is it - fine. I have added you as a member with create/delete privileges.

Hi @bking: Is there something I could/should do? (I'm not familiar with the processes - sorry for this).

A debian VM, where the qlever .deb package can be installed, sounds very good! In my test installation, qlever-0.5.48 package installed docker seamlessly, and worked without hassles. scp file transfer and data loading shouldn't be too difficult. Probably, debian version should be 13 (trixie) - I don't know if and for how long debian 12 (bookworm) is supported by qlever.

Tricky wg. anzeigbarer und nicht anzeigbarer Dokumente/Images, sowohl für Mappen wie für Filmabschnitte.

Tested with company, person, ware, subject example searches - worked.

TODO: reinstate PM20 Labels (T409633)

R3351:f2063223c7e886343aade907d8a52633531de759
R3351:233999868f116f826f4181d5a635ad794696231a

Two identical results with different labels (Bergedorfer Eisenwerk|Bergedorfer Eisenwerk AG) for search "bergedorfer eisenwerk".

R3351:5dcfd022ae14e88c7954d107fb94ff8f5cd7ba30 and R3351:8f50d461f715d6e85444cb53bfd0d6147d92d7c4

Ok, figured it out: Had to switch from "bastion" to "pm20database" project ...

Thanks, @Andrew ! I was able to log into Horizon, but I see no "Launch Instance" button:

That sounds great! Project name "pm20database" would be fine.

Hi @dcaro , sorry for the late respose - I was some days off and missed the notification.

Re. the "pastebin somewhere" idea: For our "SPARQL Lab", we use a mechanism to load queries from Github (or alternatively from an internal git repository). That has the additional advantage that the queries can be updated under a constant URL, discussed, forked etc. For details and links see https://zbw.eu/labs/en/blog/publishing-sparql-queries-live

Probably depends on T225701.

For checking exactly one item in a simple way, see also CheckShEx UserScript (based on PyShExy API).

Thanks - I've moved the requests to https://www.wikidata.org/wiki/Wikidata:SPARQL_federation_input#Incoming_nominations and added two endpoints with derived datasets from GND

OK, I did not think about licenses - sorry!

Examples for the federated query use case see at https://github.com/zbw/sparql-queries/tree/master/wikidata#power-queries (queries with econ_pers or ebds in name). The intermediate set fed into Wikidata was about 450,000 GND IDs. Currently, that requieres setting up a custom Wikidata endpoint.

This is not only a question of the tools in use, but also it also imposes length restrictions to queries, which are transmitted in the GET URL.

Another argument for enabling POST requests is, that GET requests / URLs are limited in length. The exact limit depends (see http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers), but often seems to be about 2000 characters. I hit this in the past in several real queries.