Jabref Daily: Data Fidelity Fixes and Traceable Architecture
Today's activity centers on preventing silent data corruption—keyword separators, URL links, and arXiv queries all got fixes that stop JabRef from quietly mangling user data. A parallel thread hardened the project's own architecture tooling, replacing an unchecked annotation system with enforced tracing.
Duration: PT2M28S
Episode overview
This episode is a short developer briefing from Jabref Daily.
It explains recent repository work in plain language.
- Show: Jabref Daily
- Published: 2026-09-05T04:01:11Z
- Audio duration: PT2M28S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's September 5th, and this is JabRef Daily.
The throughline today is silent data corruption—and closing the gaps that let it happen.
Start with keywords. PR sixteen eight three five fixes a bug where opening a library with a different keyword separator than your global preference would silently rewrite every keyword field. Oliver Kopp's fix makes the separator a per-library setting, and turns the rewrite itself into an explicit, opt-in cleanup…
Same pattern, different surface: PR sixteen seven seven four. Online file and DOI links routed through the filesystem-open code path, which truncated URLs with query strings using Path-of. Links now go through a proper URL-aware browser call, with fallbacks when that fails. And PR sixteen eight two five fixes…
Second theme: making the build itself trustworthy. PR sixteen eight four one replaces the old e-adr annotation—which no build step ever checked—with OpenFastTrace links to architecture decisions, so broken references now fail the trace-requirements build. A same-day follow-up, PR sixteen eight five four, fixes…
Smaller but notable: PR sixteen two eight six finally fixes drag-and-drop moves between libraries, correctly…
Nearby episodes from Jabref Daily
- Hardening the Project's Foundations
- Sync Reliability and a Regression Cleanup Sprint
- Shared Databases Get Smarter, Resilience Gets Tougher
- Cleaning House on Docs, Dialogs, and CI
- Data Safety and Git Get Serious
- Protecting Data, Polishing the UI
- Git Workflow Takes Center Stage
- Data Integrity and Native Build Fixes