Digital literature faces unique preservation challenges as platforms and formats become obsolete. Questions arise about what constitutes the 'text'—source code, executed output, interactive experience, or all three. Preservation requires technological intervention and curatorial decision-making that shapes how future readers encounter digital works, making preservation itself an interpretive practice.
Print literature faces its own preservation challenges—paper degrades, books are lost, libraries burn. But digital literature faces a fundamentally different problem: technological obsolescence. A book from 1950 can be read today with no more than good light. Digital literature from 1995 requires software that may no longer be available, hardware that is no longer manufactured, and formats that operating systems no longer support. Digital preservation is thus not primarily about storage but about sustained technological maintenance.
Consider a hypertext fiction created in Storyspace, a tool that dominated 1980s-90s hypertext authoring but is now obsolete. To preserve this work and keep it readable, what must be preserved? The source code alone is not sufficient—readers need a functioning Storyspace application to open it. One preservation approach is emulation: recreate the original Storyspace environment on contemporary systems so the work runs exactly as designed. But emulation is labor-intensive and brittle; it must be continuously updated as operating systems change. Another approach is migration: convert the work to a contemporary format, such as HTML with JavaScript interactivity. This ensures access but changes the reading experience—the aesthetic of original link behavior may be lost.
The problem becomes even more complex when we ask: what is the work? Is it the source code? The visual output? The interactive experience? A decision about which aspects to preserve is implicitly a decision about what the work is. If you preserve only the narrative text, stripping away the interactive navigation, you preserve content but lose formal meaning. If you preserve only screenshots, you preserve visual appearance but lose interactivity. These are curatorial decisions, not purely technical ones.
Digital preservation thus becomes interpretive practice. The preservationists must make judgment calls: Will we maintain original platforms at great technical cost? Will we migrate to ensure access? Will we prioritize the interactive experience or the source code? Each decision shapes what future readers encounter. If a hypertext fiction's meaning depends on reader uncertainty (as with 'Afternoon, a Story'), migrating to a platform with clearer navigation structures alters that meaning. Preservation decisions are not neutral; they constitute interpretation.
This reveals that digital literature requires ongoing institutional commitment. Unlike print, which can be preserved passively (keep it in a stable environment), digital literature requires active maintenance: emulation systems must be updated, migrations must be performed, formats must be converted. This ongoing labor means that digital literature preservation is always partial and provisional, shaped by decisions about which works merit sustained effort and what aspects of works matter most to preserve.
Topics in reflective domains aren't scored by quiz answers. Read, reflect, and mark when you've thought it through.
No topics depend on this one yet.