# From Code Archival to Knowledge Graph: Bridging Software Heritage, COAR Notify and Wikidata

arXiv: https://arxiv.org/abs/2609.21667 · HTML: https://mlsanity.com/paper/2609.21667/

## Key facts

- No citing papers in the map yet (data through 14 Oct 2026).
- Builds on 9 of its 42 references that are in the map.
- First posted on arXiv 18 Sep 2026.

## Builds on (most cited first, 9 of 9)

- [SoMeSci- A 5 Star Open Data Gold Standard Knowledge Graph of Software Mentions in Scientific Articles](https://mlsanity.com/paper/2108.09070/) (2021)
- [Archiving and referencing source code with Software Heritage](https://mlsanity.com/paper/2004.00514/) (2020)
- [Synthetic vs. Real Reference Strings for Citation Parsing, and the Importance of Re-training and Out-Of-Sample Data for Meaningful Evaluations: Experiments with GROBID, GIANT and Cora](https://mlsanity.com/paper/2004.10410/) (2020)
- [Source Code Archiving to the Rescue of Reproducible Deployment](https://mlsanity.com/paper/2405.15516/) (2024)
- [Journal of Open Source Software (JOSS): design and first-year review](https://mlsanity.com/paper/1707.02264/) (2017)
- [Referencing Source Code Artifacts: a Separate Concern in Software Citation](https://mlsanity.com/paper/2001.08647/) (2020)
- [The Software Heritage Open Science Ecosystem](https://mlsanity.com/paper/2310.10295/) (2023)
- [Interoperable verification and dissemination of software assets in repositories using COAR Notify](https://mlsanity.com/paper/2508.02335/) (2025)
- [MediaWiki Code2Code Search: Neural Retrieval for the Semantic Discovery of Open-Source Software Entities](https://mlsanity.com/paper/2607.26766/) (2026)

## Abstract (arXiv)

Software is a first-class scientific object, yet validated links between source code and the scholarly record remain largely absent from the Linked Open Data (LOD) cloud, isolating archived artefacts from semantic discovery. This paper presents an end-to-end reconciliation pipeline that harvests, validates, and models publication-to-repository pairs from sources where the link between a paper and its source code is explicit and editorially verified: the software-centric journals JOSS, SoftwareX, and IPOL, together with the reproducibility reports of the SIGMOD Availability and Reproducibility Initiative (ARI). This yields a curated corpus of 4,397 langleDOI, repository-URLrangle pairs. We design two distinct application profiles grounded in Wikidata classes (one for scholarly articles, one for software instances) aligned with the schema.org and CodeMeta vocabularies. This architectural separation enables rule-based reconciliation at two granularities: lightweight, inline publication references or standalone, first-class Wikidata software nodes equipped with SWHIDs, Software Heritage's content-addressed identifiers. A read-only lookup against Wikidata shows that only 82 of the harvested repositories were already modelled there; human-reviewed batches have since created 4,182 new software items cross-linked to their articles. We further show that payloads of the emerging COAR Notify protocol, an external effort we do not develop, map natively onto our input format, so the same backend could later serve a live enrichment stream. Our core contribution is a pair of application profiles that turn Wikidata into a connector between the scholarly record and archived source code; we openly release all code, application profiles, and harvested datasets.