Egon Willighagen

Thank you for debugging the issue!

Thanks for the cross-link! Often changes or changes on the Wikidata side need updates here. The book example with versions and editions is an important one. Scholia indeed just visualizes...

> just changing the endpoint @fnielsen, I think the split will mean federated SPARQL queries over the two servers. Did you try that already? Where can I find the SPARQL...

> Can all of them be rewritten without adverse effects like timeout? @dpriskorn, no, I don't think so. This initial split is suffering from the problem we highlighted in a...

I just tried rewriting it, but it's nasty because essential info is split over the two resources (to be run at https://query-scholarly-experimental.wikidata.org/): ```sparql select ?year (count(distinct ?work) as ?number_of_publications) ?type_...

When I run the query from `main` I get closer, and it runs in reasonable time: ```sparql select ?year (count(distinct ?work) as ?number_of_publications) ?type_ ?venue_ ?role where { # get...

(crossposted from the Telegram Wikicite channel) I just finished a query that shows how content is scattered over the two splits: https://w.wiki/98km One of the powers of SPARQL is to...

> https://synia.toolforge.org/#author/Q18618629 - third table Yes, got that :) But unlike the other tables, this one does not have a link to the matching query service. I wanted to see...

> https://www.wikidata.org/wiki/Wikidata:Synia:author#Recent_publications_from_experimental_scholarly_endpoint Thanks. Now that I have seen the query, I think that one runs into exactly the problem I experienced and tried to describe.

> i.e. the query might be executed on different back-ends, but it should not be required to change the query. What I found is that this is not trivial at...