oxford-common-file-layout · shipping · also OCFL, OCFL object

Oxford Common File Layout

Oxford Common File Layout is a storage layout for versioned digital objects that maps logical file names to stored content through a digest-based inventory.

In OCFL 1.1, the object-root inventory.json records the object identifier, latest version, content manifest and version states. The manifest maps digests to stored content paths; each version's state maps those digests to logical file names. Stored paths and logical names can differ. [1]

A later version can reference content stored in an earlier version, so a version directory need not be a self-contained copy. Previous versions should remain immutable; removing old content can break newer states. [2]

The optional fixity block carries supplementary digests and may cover only some files. It does not replace the mandatory manifest or make payload checking optional. [1]

Validating an object establishes its internal consistency, not that it is the intended recovery target. For recovery, retain an independent version expectation and still verify the payload. [3]

Relations

related
Backup manifest, Content-addressed storage, Checksum, Restore test, BagIt

Limitations

  • The specification describes objects at rest; atomic updates and recovery procedures require implementation choices. [1, 2]
  • OCFL does not portably preserve filesystem permissions or timestamps and prohibits hard and symbolic links; preserving such features requires a suitable disk or filesystem image stored as a regular file. [1]

Citations

  1. OCFL 1.1 specification: inventories, versions, fixity and objects at rest (accessed 2026-11-21)
  2. OCFL 1.1 implementation notes: content paths, version immutability and updates (accessed 2026-11-21)
  3. Hesela: OCFL object validation and independent recovery-target checks (accessed 2026-11-21)
  4. Hankinson et al. (2019): The Oxford Common File Layout: A Common Approach to Digital Preservation (accessed 2026-11-21)
Sources & caveats
  • Source synthesis of OCFL 1.1; logical names, physical content and additional fixity digests are distinct concepts. [1]
  • The existing seven-fixture recovery study uses pinned ocfl-py 2.1.0. This definition does not extend those observations to other implementations. [3]
  • The 2019 design paper describes an alpha specification and compares metadata-access operations, not full payload validation or current restore performance. Use OCFL 1.1 for the format rules here. [4]

JSON: /data/terms/oxford-common-file-layout.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Oxford Common File Layout. Hesela. 2026-11-21. https://hesela.dev/terms/oxford-common-file-layout/