Query the journal with SPARQL
The whole journal is a knowledge graph - DCAT 3 / DCAT-AP 3 and the same resources in CIDOC CRM. This page runs SPARQL over it in your browser. Every query is editable; change it, press Run, and see what the graph says.
There is no SPARQL endpoint and no server behind this page. On request your browser loads Python (Pyodide 314.0.7) and rdflib 7.6.0 from this site, about 13 MB, then the four Turtle files listed below with 19,125 triples. Nothing you type leaves your machine.
Graphs:
downloads/squirrelpapers.ttl · downloads/squirrelpapers.crm.ttl · vocab/types.ttl · ontology/index.ttl
- Every published entry, in journal order
- Entries by type
- Entries by year
- Entries per volume and issue
- People and how often they appear
- Who wrote with whom
- Entries by language
- Conferences and where they took place
- CIDOC CRM: who created what, and when
- CIDOC CRM: what was presented where
- PDF files per volume, with their size
1. Every published entry, in journal order
The table of contents of the whole journal: citation label, title, date and types of each entry. An entry with several types appears once, its types joined with a slash.
2. Entries by type
Counted over the SKOS concepts of the journal's own type vocabulary, with the COAR resource type each one maps to. The same numbers as the type facet on the search page.
3. Entries by year
The year of dct:issued - the date of the talk, poster or publication, not the year of the volume it was gathered into (Volume 1 collects everything up to 2019).
4. Entries per volume and issue
Walks the chain entry → issue → volume through dcat:inSeries, the way DCAT 3 links datasets to dataset series, and counts what hangs on each issue.
5. People and how often they appear
Authors, contributors and editors of entries, counted per person IRI. A person with an ORCID has an IRI built from it; the owl:sameAs link leads to the ORCID record. The same numbers as the person facet.
6. Who wrote with whom
Pairs of people who share at least two entries as authors. The FILTER on the IRIs keeps each pair once instead of twice.
7. Entries by language
dct:language points to the EU language authority. Where the source does not state a language, the build guesses it from the title and marks the entry with sqp:languageGuessed; entries without any language are not counted here.
8. Conferences and where they took place
Events with their place as a GeoSPARQL point: the ?wkt column can be pasted into QGIS as delimited text. Online events have no place and are left out.
9. CIDOC CRM: who created what, and when
The same authorship as in the people query, read from the CRM view instead: an E65 Creation (also LRMoo F28) carried out by persons (P14), with a time-span (P4) whose earliest begin (P82a) gives the date.
10. CIDOC CRM: what was presented where
An event is an E7 Activity that used the entry (P16) and took place at an E53 Place (P7), whose position is a WKT literal (P168). The PDF of an entry is a CRMdig D1 Digital Object that incorporates it (P165).
11. PDF files per volume, with their size
Every distribution with a byte size, summed per volume. The files stay on Zenodo; the graph records where they are, their media type and an MD5 checksum (SPDX).
The queries come from content/queries.yaml in the repository and are run against these graphs whenever the site is built; a query that returns nothing stops the build. The same queries are available as .rq files for any other SPARQL processor.