The Shipwright's Knot: What Data Preservation Can Learn from Traditional Crafts
I recently found myself watching a documentary about traditional wooden boat building, a world of salt-stained hands and the scent of cedar. The shipwright spoke not in megabytes or checksums, but in terms of grain, joinery, and the subtle give-and-take of materials. As he demonstrated a series of complex knots used to lash timbers, he made an offhand comment that struck me: "A good knot isn't one that just holds fast. It's one that can be untied, even after years under strain, when it's time for repair." In that moment, the analogy to digital preservation became beautifully, starkly clear.
We in the digital world are obsessed with permanence. We talk about WORM storage (Write Once, Read Many) and deep-freeze archives, imagining a perfect, static state for our data. But the shipwright understands that nothing truly endures by being frozen in time. A wooden boat at sea is in a constant state of flux, battered by waves and weather. Its longevity depends entirely on a philosophy of planned maintenance and, crucially, the ability to access and replace its parts. A rivet that can't be removed dooms the entire hull. Similarly, our data formats are not timeless artifacts; they are like planks of wood that will eventually rot. Preservation, then, is less about building an indestructible vault and more about ensuring the data remains accessible, reparable, and reinterpretable.
This is where the principle of the reversible knot comes in. The shipwright’s knot is strong enough to withstand immense pressure, yet its structure is intelligible to any craftsperson who encounters it. It doesn't require a proprietary tool from a company that went out of business decades ago; it requires knowledge, passed down through practice. In our realm, this translates to the imperative for open formats and transparent standards. Are we tying our data up in proprietary knots—complex, encrypted, or patent-protected formats—that future archivists will struggle to untie? Or are we using the digital equivalents of a clove hitch or a bowline: simple, well-documented, and universally understood formats like plain text, CSV, or TIFF?
The Wisdom of the Repair
The most profound lesson, however, lies in the concept of repair itself. A shipwright expects repairs. They are not a sign of failure but a natural part of the lifecycle. In digital preservation, we often treat data corruption or format obsolescence as catastrophic failures. But what if we built our systems with an expectation of repair? This means creating not just the data, but extensive provenance information—the 'why' and 'how' of the data's creation—and detailed preservation metadata—the 'what' and 'when' of its treatments. This metadata is the shared knowledge that allows a future archivist, like a new shipwright, to understand the original intent and make a faithful repair.
Our digital archives are not unsinkable ships. They are vessels we are launching into the uncertain seas of the future. Perhaps instead of solely focusing on building stronger locks for our data vaults, we should also be learning the ancient crafts of knot-tying and repair. We need to ensure that the data we are so diligently saving is not just stored, but is lashed together with intelligent, reversible bonds, ready for the next generation of custodians to take the helm, understand the craft, and perform the necessary maintenance to keep the whole vessel afloat.
Notes & further reading
A few pages I came back to while writing this: