← DF Sentinel/Digital Preservation
DF Sentinel · Digital Preservation Workflow

Preservation doesn't stop at capture-time hashing.

Ingest, format identification (DF Sentinel Catalogue, powered by PRONOM), ongoing fixity monitoring, descriptive metadata and standards-compliant BagIt export — one workflow from accession to repository handoff, not a one-off checksum step you run once and forget.

Built around the ingest checklist archivists already think in: write-block, capture, verify, document — as something visible on screen, not living in someone's head or a shared spreadsheet.

PRONOM/Siegfried format ID Ongoing fixity, not one-off hashing RFC 8493 BagIt export
DF Sentinel case workspace showing the ingest checklist and case-confidence gauge for a case in progress
The ingest checklist and case-confidence gauge for an open case.
The Ingest Checklist Made Visible

Write-block, capture, verify, document.

Archivists already think in this checklist. Most tools don't mirror it, so the workflow lives in someone's head or a shared document instead of on screen. DF Sentinel makes each stage a literal, visible step against every case — something an operator can point to and explain to a colleague or manager, not a process only one person fully understands.

01

Register & ingest

Media is logged as a case item and imaged, establishing the audit trail before processing begins.

02

Verify

Cryptographic hashing proves the capture matches its source, byte for byte.

03

Identify

Every file is format-identified against PRONOM and rated for obsolescence risk.

04

Describe

Dublin Core metadata is captured once — title, creator, dates, scope, provenance.

05

Package

A standards-compliant BagIt export carries the metadata automatically into the package.

06

Monitor

Fixity checks continue after handoff — preservation doesn't end at ingest.

PRONOM / Siegfried

Format identification the preservation world already speaks.

Every file is identified against the UK National Archives' PRONOM registry via an integrated Siegfried engine — by inspecting content and structure directly, not by trusting a file extension that could be wrong, missing, or deliberately misleading.

Identified formats are then rated for obsolescence risk, with a suggested action attached — the preservation-planning step most tools skip entirely.

Low risk — actively maintained, widely supported formats
Moderate / High risk — obsolete word processors and proprietary formats flagged, with a suggested action
Unrated, honestly — a format outside the registry is reported as unrated, never quietly assumed safe
The Differentiator

Capturing a file correctly is only half of preservation.

The other half is noticing when it stops being correct. DF Sentinel's fixity monitor re-checks every preserved file's checksum against what was recorded at capture — on demand, or on a schedule you set — so bit rot or silent corruption years later doesn't go unnoticed. If nothing has changed, it says so plainly.

If a check finds nothing it can verify — because a file was added outside the normal capture flow, say — it's reported honestly as a coverage gap, never quietly counted as a pass. A check that's stopped early never overwrites an earlier failing result or resets the "last checked" clock. That's the difference between a tool that reassures you and a tool that's actually watching.

Dublin Core

Described once, carried everywhere.

Title, creator, date range, scope and content, subjects, rights, provenance and arrangement notes — captured once during processing, then carried automatically into every BagIt export as standard Dublin Core tags. The archival package describes itself to whoever opens it years from now, without anyone having to re-enter the same details by hand.

Standards-Compliant Handoff

BagIt export your repository already understands.

A standards-compliant RFC 8493 BagIt package for transfer into digital repositories and preservation systems — with exact payload validation and the case's descriptive metadata carried automatically into bag-info.txt. No proprietary container to negotiate with whatever system your institution already runs downstream.

Legible At A Glance

The state of a collection, without digging through a log.

A calm, ambient case-confidence indicator sits beside every open case — green when verified, amber when work is outstanding, red only when something has actually failed. Alongside it, a Digital Asset Register export gives a CSV register of everything preserved in a case, in the format archivists already use to report holdings upward to managers and funders.

Frequently Asked Questions

Questions about the preservation workflow.

Is this just a one-time checksum tool?
No — that's the whole point. Capture-time hashing proves a file was copied correctly on day one. Fixity monitoring re-checks every preserved file's checksum against what was recorded at capture, on demand or on a schedule, so bit rot or silent corruption years later doesn't go unnoticed. A one-off checksum script only ever answers the first question.
What happens if a fixity check finds nothing to verify?
It's reported honestly as a coverage gap, not disguised as a clean pass. If a case holds files with no recorded checksum — added outside the normal capture flow, say — a fixity check says so plainly rather than overstating the result as "everything verified."
Does the BagIt export meet a real standard, or is it a custom format?
It's a standards-compliant RFC 8493 BagIt package — the format most digital repositories already expect — with exact payload validation and the case's descriptive metadata carried automatically into bag-info.txt.
Where does the descriptive metadata in the BagIt package come from?
Dublin Core fields — title, creator, date range, scope and content, subjects, rights, provenance and arrangement notes — captured once during processing and carried automatically into the BagIt export as standard tags, so the package describes itself to whoever opens it years from now.
How does format identification actually work?
Every file is identified against the UK National Archives' PRONOM registry via an integrated Siegfried engine — by content and structure, not by trusting a file extension that could be wrong or missing.
What does the format-risk rating actually tell us?
Identified formats are rated Low, Moderate or High risk of future unreadability, with a suggested action — obsolete word processors and proprietary formats get flagged, and anything not in the registry is reported honestly as unrated, never quietly assumed safe.
Part Of DF Sentinel

More from DF Sentinel.

From accession to repository handoff

Talk to us about your preservation workflow.

Whether you're clearing a backlog or setting up an ongoing preservation programme, tell us what you're working with and we'll help you find the right fit.

No newsletters, no mailing lists, no marketing follow-up — whichever way you get in touch.