Skip to content
Guides · 3 long reads

Guides to file formats, identification and metadata records

Longer explanations that tie the reference pages together, each with worked examples.

Updated

The three guides cover the questions that come up whenever digital files have to be kept usable for longer than the software that made them. The first explains file format identification: how magic bytes, offsets and container contents reveal what a file really is, and how tools such as DROID and Siegfried turn that evidence into a registry identifier. It includes a working identification tool and a table of common signatures.

The second turns from identification to choice. It weighs the criteria archives use to rate a format's chances of lasting (published specification, wide adoption, no encryption or external dependencies) and applies them to images, documents, audio, video, data and web content, with honest notes on where the usual recommendations trade quality against convenience.

The third shows how to write the result down. A Dublin Core record is short, but small habits decide whether it stays useful: one value per statement, controlled vocabularies for dates, languages and places, and media types for formats. Worked examples for a digitized report and a born-digital dataset show the difference.

Which guide to read first

The order depends on where a collection stands. Someone facing a drive of unlabeled files from a donor or an old project server should start with identification, because nothing else can be decided until each file has a known format and version. A team planning a digitization project, or choosing what to accept from depositors, gets more from the preservation guide: it sets out which formats to ask for and which to convert on arrival. Catalogers who already know what they hold and need consistent records can go straight to the Dublin Core guide.

In practice the three steps repeat. A file is identified, its format is checked against the preservation criteria, a decision is made to keep or normalize it, and the outcome is written into a record that names the format, the tool and the date. The guides follow that cycle, and each ends with the points where the next one picks up, so a reader who works through all three ends with a complete workflow for a single file: from an unknown sequence of bytes to a described, checkable object in a collection.

None of the guides assumes special software. The identification guide works with the in-browser tool on this site and explains what dedicated tools add; the preservation guide relies on criteria that any institution can apply with a spreadsheet; the metadata guide uses plain XML and RDF examples that can be copied into most repository systems. Where a step depends on a particular product, the guide says so and names the free alternatives that do the same job.

Each guide links to the reference pages for the individual terms it uses, so a reader can stop at any property, class or code and read its full definition before moving on.

Questions about the guides

Which guide should be read first?

For anyone receiving files of unknown type, the file format identification guide comes first. Catalogers starting a metadata project usually begin with the Dublin Core records guide.

Do the guides assume programming knowledge?

No. Hex values and RDF snippets appear as examples, and each is explained in plain language. Readers who never open a terminal can follow every guide; developers will find enough detail to automate the steps.

How do the guides relate to the term pages?

The guides explain tasks from start to finish and link to the term pages for detail. A term page explains one property, class or code in depth; a guide shows how several of them work together in a real record or workflow.

Are the format recommendations official policy?

They summarize criteria used across the archival field, such as openness of the specification, adoption and external dependencies. Each institution still sets its own format policy, and the guides point out where common recommendations differ.