The Potter's Kiln: On Firing Data for Future Use
In a ceramics studio, the kiln is the point of no return. It’s where the artist’s careful work—the wedged clay, the centered vessel, the delicate glaze—is subjected to intense, transformative heat. This process, called firing, does not merely dry the piece; it chemically alters its very structure, turning soft, fragile earth into a hardened, functional object. The parallel to digital preservation is striking, and it offers a lesson far removed from the cold logic of servers and file formats.
We often think of archiving as an act of freezing, of placing a digital object in a state of suspended animation where it is safe from the decay of time. But this is a misconception. Like clay that has been shaped but left unfired, data in a merely stored state is incredibly vulnerable. A change in software, a shift in hardware architecture, or the simple erosion of bit rot can cause it to collapse. The true work of preservation isn’t about stasis; it’s about catalyzing a change that makes the data durable enough to survive an unpredictable future.
The Art of the Controlled Transformation
A potter doesn’t just throw a raw pot into a blazing fire. The firing process is meticulously controlled, with a careful ramp-up of temperature, a sustained period at peak heat, and a gradual, managed cooldown. This controlled transformation is what we lack in many digital preservation strategies. We might make a copy, but we don’t always fire it.
Firing data means subjecting it to the kiln of migration and normalization. It’s the process of converting a proprietary file format into a standard, open one. It’s the act of extracting raw text from a PDF and pairing it with its metadata. It’s the sometimes-risky but necessary step of emulating old hardware to ensure a file can still be read. These are active, transformative processes. They change the object, but they do so with the explicit intent of baking in longevity, of creating a version that is less dependent on a specific, fleeting technological environment.
An unfired pot might look finished, but it dissolves in water. An unfired dataset might look safe on a backup drive, but it is one software update away from becoming a mystery. The goal is not to preserve the original bits at all costs—sometimes those bits are the problem. The goal is to produce a usable artifact, even if the path to get there requires the heat of change.
This borrowed wisdom from the potter’s studio reframes the archivist’s role. They are not just collectors or custodians; they are artisans who must understand the composition of their materials and the conditions required to make them last. They must know when and how to apply the heat of transformation to ensure that the data they steward doesn’t just exist, but remains functional and meaningful for whoever might need to use it, long after the original tools have turned to dust.
Notes & further reading
A few pages I came back to while writing this:
- Topeka, KS
- The Librarian's Dilemma: Choosing What to Ignore
- Lexington, KY
- The Gardener of the Web: On the Quiet Cultivation of Archive Team
- Louisville, KY
- The Index's Folly: Why Full-Text Search Can Miss the Forest for the Trees
- Baton Rouge, LA
- Lafayette, LA
- New Orleans, LA
- Shreveport, LA
- Boston, MA
- Springfield, MA
- Worcester, MA