Permalink
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
57 lines (44 sloc) 3.95 KB
title layout category tags updated drafted unique_id description image_index image
Designing this site: an archive
singel
writing
archiving
future
git
indieweb
photography
web
2016-10-09 00:57
2014-11-08 12:34
2014-11-08:design-notes-an-archive
On my approach to self-archiving.
index/1988-oliver-young.jpg
src alt caption quality
1988-oliver-young.jpg
Oliver as a toddler
A photo taken of me in … 1988? I have no idea! This is an example of why I miss having a complete archive.
50

Looking back at my files and memories from my life so far, I find there are few things that are constant or well-maintained. I do not own a physical album of photos from when I was young – I wish I did. I do not even have many scans of old photos. I am missing most of my creative output from when I was younger, as well. I think my life would be richer for having a better understanding of where I came from.

{% assign image = page.image[0] %} {% include block/image.html class="right" %}

If you never have, you should dig into the Internet Archive’s Wayback Machine. You can find the history of sites no longer online, or no longer in their previous form. All of those attempts, versions and missteps are encoded in HTML and publicly hosted until they are discarded in a matter of months or years. The Archive team saves this history. It is cared for by preservationists who realized that if they did not make the effort, this creative output and cultural memory would certainly be lost history in the space of far less than a lifetime (since, by default, not much lasts long on the web).

It takes a lot of effort to keep a comprehensive and long-lasting archive of one’s own history and output. While I strive to get better at backing things up and creating systems for maintaining old files, it is possible to build a website with the intention to serve the future instead of just the present moment.

How to back up a personal archive

Right now my home backup system works like this:

  • Back up my MacBook to a Time Capsule running Time Machine.
  • Store a complete archive of all of my photography on a local external drive. I use a LaCie D2 Thunderbolt.
  • Keep Backblaze running, backing up both the MacBook and the external drive.

This means I have a local repository, a working remote copy on GitHub, and then a local backup of everything (Time Machine), and a remote backup of everything (Backblaze). It is robust enough for now, and it is literally fire-proof.

I am building an archive. {:.focus}

Git will help me keep track of versions and ensure that I lose as little data as possible while working on projects. Because the data for the site will be kept off-site (in a [GitHub repo]({{ site.link.source }})) that can also be backed up in multiple other ways, this should prove more robust and long-lasting than any software I have ever used.

I hope that the best way to maintain an archive that I will be happy to browse years later is to take extra effort now to design it as one. Once I have more written and archived, I look forward to the design challenge of organizing that information. Too much of the web right now is structured as “news”, or otherwise oriented toward ephemerality. I want to see more sites that treat themselves as long-lasting things, with information design and content that is built to last – not to be buried and forgotten about.

I plan to share more about archiving-friendly design practices as they take form. Read more writing on archiving from this site.


{% include block/project--satellite.html id="2016-10-08:preserving-jekyll-sites" %}