This is the third weekend I am working on Scholia, the first two part of the April 2025 hackathon. It follows the hackathons\nlast year October and\nNovember hackathons.\nThere is some urgency for this unpaid work, because Wikidata is splitting the RDF into two\nSPARQL endpoints (see this The Signpost\nand this post by Finn).\nThis split has happened, but there is a legacy server for tools that have not been upgraded.
\n\nScholia has not been upgraded. It has more then 350 SPARQL queries, and each one has to be tested\nseparately and updating every query is not trivial. Together with Daniel, Finn, and others, I have\nhacked up patches last year to:
\n\n\n\nThis month I continued working on the second, and I:
\n\n\n\nThat second also indicated that the legacy server has more limited resources and users will more\nquickly run into error messages that too many queries are run in parallel. Now, users can rerun\nthe query, but then the results table contains the previous error message. Second, you want to run\nthe queries for one aspect to not run all at the same time, but have Scholia send of the\nquery when the panel becomes visible (and scrolling a page takes a bit of time).
\n\nFor these issues, I wrote these two patches (yet to be approven and merged):
\n\n\n\nNow, the iframes already had some aspects of lazy loading, but it turned out that it was mostly\nlazy display, and the queries were still run as soon as possible. This last patch challenged my\nJavaScript skills and I learned Intersection Observer API, a browser technology that allows\nthe browser to see what part of the webpage you are looking at right now. Yeah, I can easily\nsee how that does user profiling, but in this case it is just used to fire of the SPARQL\nquery when it become relevant. It uses an additional callback function, so I had to\nmake sure Jekyll/Liquid creates custom callback functions for each panel.\nActually, I intended to show the code here, but I am not entirely sure how to escape\nthe code so that Jekyll does not try to run the instructions. For now, you have to\ncheck the PR.
The other things I have been doing, is finally finish up the Scholia Chemistry paper.\nThat actually depended on the maturing of various tools, me figuring out how to characterize\nthe actual amount of content contributed to Wikidata and how to make that transparent,\nand more recently, the above to be able to convince readers Scholia will not die with\nthe graph split. With the above pages, we have, I think, sufficient guarantee it will\nbe around for another few years, at least.
\n\nThis paper, which I hope to finish the final draft today, applying\nsome good feedback from co-author last weekend, is the final bit of work done on\nthe Alfred P. Sloan Foundation grant.
\n\nWe intend to put the paper up as preprint soon and then submit it do a Diamond Open Access\njournal, one that supports CiTO citation intent annotation.
", "summary": "This is the third weekend I am working on Scholia, the first two part of the April 2025 hackathon. It follows the hackathons last year October and November hackathons. There is some urgency for this unpaid work, because Wikidata is splitting the RDF into two SPARQL endpoints (see this The Signpost and this post by Finn). This split has happened, but there is a legacy server for tools that have not been upgraded.", "date_published": "2025-04-20T00:00:00+00:00", "date_modified": "2025-04-20T14:58:00+00:00", "tags": ["scholia","javascript","sparql"], "_funding": [{"award": { "title" : "To support development on Scholia, a software tool to facilitate the exploration and curation of the research literature", "acronym" : "Scholia", "uri" : "https://sloan.org/grant-detail/G-2019-11458" }, "funder": { "name": "Alfred P. Sloan Foundation", "ror": "052csg198" } }], "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ] } ] }