---
id: "codex://object/an-archive-begins-with-an-editorial-decision"
archive_id: "an-archive-begins-with-an-editorial-decision"
slug: "an-archive-begins-with-an-editorial-decision"
url: "https://ndcodex.com/codex/an-archive-begins-with-an-editorial-decision/"
type: "codex"
title: "An Archive Begins with an Editorial Decision"
summary: "Teaching an archive means helping people decide what a record is, how its sources relate, and what a visitor can responsibly understand from it."
date_published: "2026-10-20T19:07:09.696Z"
date_modified: "2026-10-20T19:07:09.696Z"
status: "published"
visibility: "public"
language: "en-US"
axes:
  scale: "meso"
  depth: "structural"
  focus: "witness"
  function: "revelatory"
themes:
  - "archives"
  - "provenance"
  - "judgment"
constellations: []
tags:
  - "archives"
  - "editorial judgment"
  - "provenance"
  - "judgment"
keywords:
  - "Codex"
  - "archives"
  - "provenance"
  - "judgment"
  - "editorial judgment"
author:
  id: "nathan-davis"
  name: "Nathan Davis"
  designation: "Archive Operator"
  role: "Archive Operator"
  handle: "@nathandavis"
  avatar: "/media/people/nathan-davis.jpg"
  bio: "Designer, builder, and curator of the Codex Archive."
contributors:
  - id: "nathan-davis"
    name: "Nathan Davis"
    designation: "Archive Operator"
    role: "Archive Operator"
    handle: "@nathandavis"
    avatar: "/media/people/nathan-davis.jpg"
    bio: "Designer, builder, and curator of the Codex Archive."
relations: []
media: []
---
# An Archive Begins with an Editorial Decision

After an archive training session, I described what I had been doing as preaching editorial decisions.

There was software involved. There were fields and images and the practical matter of getting material onto a website. But I kept returning to the choices that make a record worth encountering.

What is this thing? Where does it begin and end? Which pieces of material belong together? What can we say about them?

Imagine a folder containing several photographs, a newspaper clipping, and someone's account of an event. That folder gives us a starting arrangement. We still have to decide whether we are describing the event, the individual objects, the person who collected them, or several connected records.

Each choice changes what a visitor can discover.

A photograph might support more than one story. A caption might contain information the image cannot establish by itself. A recollection might add something valuable while leaving the date uncertain. The record needs enough room for those differences to survive.

**The first thing we are teaching is how to decide what belongs together.**

The conversation after the session was encouraging. Someone had more material to share: a spreadsheet, organization notes, and a folder of content. That creates a useful next encounter between the proposed system and the way people have actually been keeping their knowledge.

Their organization deserves to be understood. A spreadsheet may contain distinctions that our fields have missed. A folder name may preserve a relationship that disappears during import. Something that looks inconsistent from the outside may have a practical explanation in the collection's daily use.

I want to follow a few real examples all the way through.

Where does the material arrive? What becomes a record? What remains supporting context? What does the visitor see? How does the team add a correction later?

That last question belongs near the beginning. A record will acquire new information. Someone may recognize a face, correct a date, or explain why two objects were kept together. The archive needs a way to receive that contribution while keeping its origin visible.

The training also left me with a useful distinction to preserve. Understanding the editorial idea is one achievement. Operating the system independently is another. Individual access and a real practice run will tell us more about the second.

This is where the design meets its people. Their material enters. Their habits become visible. They attempt the work without us narrating every step.

I want the archive to make their judgment easier to exercise and easier for someone else to understand later.

Every record is a small act of interpretation. A useful system helps us make that act carefully, and leaves it open to the next person who knows something we do not.