Skip to content
Archēglyph
Menu
Archēglyph

Versioning

Also: Dataset versions · Versions

Named, immutable snapshots of a dataset's bundle at a point in time. Let you return to exactly that state later.

Last updated

A version in Archēglyph is a named, immutable snapshot of a dataset’s bundle at a point in time. Save a version after a successful analysis run and you can always come back to exactly that state, even after re-running the pipeline with different models. Versions are tracked via an object-storage manifest; the bundle bytes themselves are immutable once published.

Why it matters for your research. Reproducibility. An article that cites Archēglyph results without a version pin is citing a moving target. Versioning also supports non-destructive exploration: try a different embedding model, keep the old version for comparison, archive either, revert if needed.

In Archēglyph. Every dataset exposes a versions panel; each version has its own viewable URL and its own bundle snapshot. See Why we snapshot per dataset.

An example collection, three editions in

  1. Edition 1

    12 March 2026

    Forty issues, 1896–97, read and searchable.

    fixed · its own link

  2. Edition 2

    3 June 2026

    Twenty-two more issues; three faint pages re-read.

    fixed · its own link

  3. Edition 3

    18 September 2026

    Translations into English added beside the originals.

    fixed · its own link

Download any edition, whole

The text, the index that makes it searchable, the themes, and a list of every page with its fingerprint — ready to deposit in your institution's repository.

next A permanent identifier (DOI) for each edition.

Findable
Every edition has its own permanent link.
Accessible
Published editions are public, and any edition downloads whole.
Interoperable
Open, documented formats — nothing locked inside Archēglyph.
Reusable
Each edition records how it was made: what read, translated and grouped it.
A collection grows; what you cited does not change. Each edition is fixed when it is made, has its own permanent link, and downloads whole — so the work can outlive a grant, a platform, and us. Read against FAIR, it is already findable, accessible, interoperable and reusable; a DOI for each edition is next.

Not to be confused with.

  • Git commits — those operate on source code, not on derived indices.
  • Database backups — those are operational and not semantic save- points; they don’t name why you saved.
  • Exports — an export is a copy that leaves the system. A version is the live object the system keeps.

Related terms

← Back to the glossary