How to Preserve Digital History: A New Frontier.

by

I want to talk about something incredibly important for all of us, especially writers: how we hold onto our digital creations. The digital world is amazing, right? We have access to so much information. But there’s this huge hidden problem: what we create digitally is incredibly fragile. Think about it: stone tablets, ancient scrolls, even printed books last for ages. Digital stuff? It can just disappear due to tiny errors, outdated formats, or the tech we use just vanishing.

As writers, this isn’t some abstract idea. This is about our craft, our research, our published work, and ultimately, the history we’re all helping to write. I want to go beyond just saying “back up your files.” This is about putting together a real-deal, actionable plan for keeping our digital history alive, especially with all the unique challenges and opportunities that come with these new digital frontiers.

The Myth that Digital Stuff Lasts Forever: Why We Need to Act Now

We often make the mistake of thinking that just because something is online, it’s there forever. It’s not. A website you see today could be gone tomorrow, replaced by an error message. The software that reads your 20-year-old writing files? It might not even exist anymore. Even big, seemingly stable platforms like social media can change direction fast, deleting or altering tons of content. This problem, what some call a “digital dark age,” isn’t some scary future movie plot. It’s happening right now. Our personal memories, crucial research, creative projects, even official records are at risk.

Understanding how fragile digital information is, that’s the first step to really saving it. We’re not just saving files; we’re saving context, the story behind them, and the very raw material that future historians will use to understand our time.

It’s More Than Just a Hard Drive: The Layers of Digital Preservation

Saving digital stuff isn’t a one-time thing. It’s a multi-layered, ongoing strategy. Imagine it like an archaeological dig, where different tools and techniques are used to preserve different artifacts at different depths. For our digital data, these layers include:

1. Making Sure the Data is Sound: The Very Start of Preservation

Before anything else, we have to make sure the data itself is healthy. This means stopping corruption and ensuring it’s really the original.

  • Checksums and Hash Values: Think of these as digital fingerprints. A checksum (like an MD5 or SHA-256 hash) is a unique string of characters generated from a block of data. If even one tiny bit of that data changes, the checksum changes too.
    • What to do: Use file integrity checkers (like FreeFileSync or SyncToy for Windows; rsync with checksum options for Mac/Linux; or special archival software) to generate and compare these checksums regularly. For really important files, embed the checksums right into the file’s info or keep a separate list. If a checksum doesn’t match, you know there’s corruption, and you can grab an uncorrupted version from your backups.
    • For example: When I finish a manuscript, I generate an SHA-256 hash for it and save it in a manifest.txt file right next to the manuscript. Next year, I’ll recalculate that hash. If it matches, great, the file is unchanged. If not, I know to investigate immediately.
  • Finding and Fixing “Bit Rot”: Hard drives, SSDs, even old CDs can silently degrade over time, changing individual bits of data. This “bit rot” can mess up your files.
    • What to do: Use file systems designed for data integrity (like ZFS, Btrfs if you’re really techy). These file systems automatically find and, if you have multiple copies (like RAID setups), often fix bit rot. For simpler setups, regularly copying data from one drive to another (using robocopy /mir on Windows or rsync -a on Mac/Linux) can expose errors you might not have noticed otherwise.
    • For example: Instead of just leaving a backup on an external drive plugged in, I periodically copy that full backup to a new external drive. This read-write cycle forces the system to re-read every single bit, which can reveal potential errors.

2. Dealing with Outdated Formats: The Problem with Technology

Digital file formats aren’t forever. Old WordPerfect documents, weird video formats, or niche software project files often become unreadable because the software that created them just isn’t around anymore.

  • Converting to Open, Standard Formats: Convert your data into formats that are widely supported, openly documented, and unlikely to disappear.
    • What to do: For text, always lean towards plain text (.txt), Markdown (.md), or Open Document Text (.odt). For images, use JPEG (for photos), PNG (for graphics with透明 backgrounds), TIFF (for super high-quality archives). For audio, FLAC or WAV. For video, FFV1 or ProRes. For structured data, CSV or JSON. Avoid proprietary formats like .doc (I prefer .docx or .odt), .psd (I’d rather use .tiff with layers if I absolutely have to), or those obscure app formats.
    • For example: I don’t just save my research notes as a .doc file. I convert them to .odt or, even better for long-term text preservation, export them as plain .txt files with clear separators for sections.
  • Emulation and Virtualization: For truly old formats where converting is impossible or you lose critical context (think interactive digital projects from the 90s, old software), consider saving the entire computer environment.
    • What to do: Use virtualization software (like VirtualBox, VMware) to create a virtual machine that acts like an older operating system (Windows 98, MS-DOS) and then install the original software on it. Save that entire virtual machine image.
    • For example: If I had created an interactive fiction piece using some specialized hypermedia program back in 1995, I could create a Windows 95 virtual machine, install the original program, and then run my interactive piece within that simulated environment. It’s like freezing a moment in computing history.

3. Having Lots of Copies Everywhere: The “Lots of Copies Keep Stuff Safe” Rule

Having just one copy is asking for trouble. You need multiple copies across different types of media and in different places.

  • Cloud Storage with Reputable Providers: Cloud storage is convenient and offers off-site backup, but always understand the provider’s terms and how long they’ll be around.
    • What to do: Use well-known cloud providers (like Google Drive, OneDrive, Dropbox, Backblaze B2, Amazon S3 Glacier). Crucially, do not rely only on cloud sync services as your only backup. Actively copy files to the cloud as a separate backup step, not just a synced folder. Set up versioning if it’s available.
    • For example: In addition to syncing my current work folder, I have a monthly automated backup script that copies my entire “Archives” folder to a separate, dedicated cloud storage bucket (like Backblaze B2, which is more for long-term storage than active syncing).
  • Diverse Physical Media: Don’t put all your eggs in the hard drive basket.
    • What to do: Keep backups on at least two different types of physical media: external hard drives (preferably those archival-grade, helium-filled ones), and maybe M-DISC optical media (DVDs/Blu-rays advertised to last 1000 years, though we’re still testing that). USB flash drives are generally not good for long-term storage because they wear out and can lose data.
    • For example: My main working files are on my computer’s SSD. Daily backups go to an external HDD. Monthly, a snapshot of critical, completed works goes to a second, identical HDD stored somewhere else (like at my family member’s house). Annually, my most important work might get burned to M-DISC archives.
  • Different Locations: A house fire, a flood, or a local disaster can wipe out all your local backups.
    • What to do: Make sure at least one backup copy is stored in a physically separate location – cloud services count, as does a safe deposit box, a trusted friend’s house, or a dedicated off-site storage facility.
    • For example: My primary backup goes to an external drive. A second external drive, with an identical backup, is kept at my parents’ house 50 miles away.

4. Metadata and Context: The Story Behind the Data

A file without metadata is like a book without a title page, author, or publication date. Context is everything for future understanding.

  • Embedding Essential Information: Information about the file, when it was created, who made it, and what’s in it should be embedded directly within the file or kept with its folder.
    • What to do: Use tools that let you embed metadata (like image editors for EXIF/IPTC data, PDF creation tools for document properties). For all digital assets, at a minimum include the creation date, last modified date, author, and a short description. For text files, a simple header at the top can do this.
    • For example: At the top of every plain text research note file, I include: # Title: Post-War Japanese Haiku Revival. Author: [My Name]. Date Created: 2023-10-26. Keywords: Japan, poetry, mid-century. License: CC BY-NC-SA 4.0.
  • Meaningful Naming Conventions: Clear, consistent file and folder names are like built-in metadata.
    • What to do: Avoid generic names like document1.docx or image.jpg. Use YYYY-MM-DD_ProjectName_DocumentTitle_Version.ext or YYYY-MM-DD_Event_Subject.ext. Create logical folder structures.
    • For example: Instead of novel.doc, I use 2023-08-15_OdysseyProject_Chapter3_Draft2.docx. For images from an event, 2023-10-20_BookLaunch_SpeakerPanel_001.jpg.
  • README Files and Folder Outlines: For complex projects or collections of files, a README.txt file explains the contents, structure, and purpose.
    • What to do: In every main project folder (like my “Research” folder, or a specific book project folder), I include a README.txt that describes the overall project, its goal, key files, and any specific software or fonts needed to view/edit the content.
    • For example: A README.txt in my “Historical Fiction Research – 18th Century France” folder might list the subfolders for primary sources, secondary sources, character sketches, and specify that some PDFs need a specific version of Acrobat Reader for the annotations to show up correctly.

5. Active Management and Migration: Digital Preservation is a Process, Not a Quick Fix

Digital preservation isn’t a “set it and forget it” task. It needs ongoing attention and proactive migration.

  • Regular Checks and Health Audits: Periodically verify your backups and the health of your data.
    • What to do: I schedule quarterly or bi-annual “preservation check-ups.” This involves: (1) restoring a few random files from my backups to make sure they’re readable, (2) recalculating checksums on critical archives, (3) reviewing cloud storage usage and settings, and (4) checking for updated versions of my chosen preservation software.
    • For example: Every January 1st and July 1st, I dedicate an hour to checking my primary and off-site backups. I pick a seemingly random file, delete my local copy, and restore it from the backup. If it restores perfectly, my backup system is working. If not, I troubleshoot.
  • Planning and Executing Migrations: As technology changes, you’ll inevitably need to move data to newer formats or storage media.
    • What to do: Stay informed about warnings for outdated formats and new archiving standards. Don’t wait until a format is unreadable. Proactively convert files to newer, more stable formats when industry shifts happen. Similarly, as hard drives get old, plan to move their contents to newer, healthier drives.
    • For example: When my current external hard drives are 5-7 years old, even if they’re still working, I proactively buy new drives and move all the data over, verifying checksums during the process. This prevents potential drive failure.
  • Succession Planning (Digital Will): What happens to your digital legacy when you’re no longer here to manage it?
    • What to do: Create a “digital will” or a clear document outlining your digital assets, account credentials (for trusted executors, maybe using a password manager’s emergency access feature), and instructions for their preservation. Specify how your archives should be handled, whether they should go to an institution, be published, or remain private.
    • For example: As a writer focusing on niche historical topics, I might designate a specific university archive as the recipient of my research notes and completed manuscripts, outlining specific access conditions. All this should be clearly documented in a secure, accessible location for my trusted executor.

Working Together for Preservation: Beyond Just Me

While individual responsibility is super important, the sheer scale of digital history means we need to work together. As writers, creators, and consumers of information, we have a vital role in advocating for and collaborating on bigger preservation efforts.

  • Supporting Archival Institutions: Libraries, archives, and historical societies are increasingly grappling with digital preservation.
    • What to do: Support institutions that are actively preserving digital content. Consider donating specific digital collections (like personal papers, website archives, correspondence) to an institutional repository if they fit the institution’s collection policies. These institutions have dedicated staff and infrastructure for long-term preservation far beyond what most individuals can manage.
    • For example: A prominent author I know worked with their alma mater’s special collections library to set up a digital archive of their draft manuscripts, digital literary correspondence, and research files, making sure their literary legacy is preserved for future scholars.
  • Participating in Open-Source Projects and Standards Bodies: The best long-term formats are often those created by open standards and community efforts.
    • What to do: Get involved with or support organizations that promote open formats and digital preservation standards (like the Open Preservation Foundation, Digital Preservation Coalition). Contribute to discussions on best practices, and use open-source preservation tools.
    • For example: A technical writer might contribute documentation or bug reports to an open-source project developing a new tool for converting old word processing formats, directly helping industry-wide preservation efforts.
  • Archiving Websites: Saving the Live Web: Websites are temporary, but they are crucial historical records.
    • What to do: Regularly archive your own websites, blogs, and social media content. Tools like Httrack (for local copies) or services like the Internet Archive’s “Save Page Now” (for public archiving) can capture snapshots. Be mindful of terms of service when archiving others’ content.
    • For example: An investigative journalist who relies on online sources for their work makes it a practice to save local, verifiable copies of critical web pages they cite, in addition to relying on services like the Internet Archive. They might also proactively submit their own professional blog to the Internet Archive’s Wayback Machine.

The Importance of Legacy: Your Part in the New Digital History

For us writers, preserving digital history isn’t just an option; it’s a moral and professional must. Our words, our research, our very intellectual output, are increasingly conceived and live in the digital world. To lose this data isn’t just to lose personal work, but potentially invaluable insights, historical records, and the very narrative of our time.

By embracing this multi-layered approach to digital preservation – focusing on sound data, formats that last, robust multiple copies, careful metadata, and proactive management – we move beyond just “backing up.” We become active participants in shaping the historical record of the 21st century. This new frontier of preservation demands constant learning, vigilance, and collaboration. It’s a long game, but its true value will only be appreciated by generations to come, who will depend on our foresight to reconstruct the digital echoes of our present.