Papers › Datatractor: Metadata, automation, and registries for extractor interoperability in...
Datatractor: Metadata, automation, and registries for extractor interoperability in the chemical and materials sciences
Matthew L. Evans, Gian-Marco Rignanese, David Elbert, Peter Kraus
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Two key issues hindering the transition towards FAIR data science are the poor discoverability and inconsistent instructions for the use of data extractor tools, i.e., how we go from raw data files created by instruments, to accessible metadata and scientific insight. If the existing format conversion tools are hard to find, install, and use, their reimplementation will lead to a duplication of effort, and an increase in the associated maintenance burden is inevitable. The Datatractor framework presented in this work addresses these issues. First, by providing a curated registry of such extractor tools their discoverability will increase. Second, by describing them using a standardised but lightweight schema, their installation and use is machine-actionable. Finally, we provide a reference implementation for such data extraction. The Datatractor framework can be used to provide a public-facing data extraction service, or be incorporated into other research data management tools providing added value.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections