Avoiding a Digital Dark Age

Richard Adler's picture

American Scientist could have researched this better (I would have liked to see something from the archival literature), but overviews of this issue for wider audiences are always good.

The general problem of data preservation is twofold. The first matter is preservation of the data itself: The physical media on which data are written must be preserved, and this media must continue to accurately hold the data that are entrusted to it. This problem is the same for analog and digital media, but unless we are careful, digital media can be more fragile.

The second part of the equation is the comprehensibility of the data. Even if the storage medium survives perfectly, it will be of no use unless we can read and understand the data on it. With most analog technologies such as photographic prints and paper text documents, one can look directly at the medium to access the information. With all digital media, a machine and software are required to read and translate the data into a human-observable and comprehensible form. If the machine or software is lost, the data are likely to be unavailable or, effectively, lost as well....

Unlike the many venerable institutions that have for centuries refined their techniques for preserving analog data on clay, stone, ceramic or paper, we have no corresponding reservoir of historical wisdom to teach us how to save our digital data. That does not mean there is nothing to learn from the past, only that we must work a little harder to find it. We can start by briefly looking at the historical trends and advances in data representation in human history. We can also turn to nature for a few important lessons....

Comments

Sam Rose's picture

Thanks, Rick. There have been

Thanks, Rick. There have been discussions in Rheingold's Brainstorms about this for years.

There are some interesting solutions in there. Seems there could also be some nanotech ways of dealing with this too, at least in some cases.

It also raises the question: will the exponentially-increasing volumes of data that we are creating mean we'll hit a point where we simply don't have any resources to store and archive them? (by "we" I mean all of humanity)

Richard Adler's picture

'Digital dark age' is a

'Digital dark age' is a phrase Margaret Hedstrom (of UM's School of Info) has used many times, and this is obviously a major concern of electronic records archivists, given that they are in the front lines when it comes to this problem.

Archivists in general tend to believe appraisal of records must still continue in electronic environments, both because resources will always be limited and because of current limits in our ability to search or filter records. If we try to keep everything, so the argument often goes, we will rapidly find ourselves unable to find anything.

Of course, that begs the question whether appraisal of electronic records is even possible in a time when email accounts swell to enormous proportions and database technology continues to evolve year-by-year. But archivists continue to insist on the importance of appraisal so it remains a debatable (and interesting) issue.

Paul and I have talked about this over the last couple of years, and I suspect we should delve into it together sometime in a F2F meeting.

Post new comment

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><blockquote>
  • Lines and paragraphs break automatically.
  • Link to content with [[some text]], where "some text" is the title of existing content or the title of a new piece of content to create. You can also link text to a different title by using [[link to this title|show this text]]. Link to outside URLs with [[http://www.example.com|some text]], or even [[http://www.example.com]].
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <c>, <c++>, <d5>, <d6>, <java>, <js>, <mxml>, <mysql>, <perl>, <php>, <python>, <rails>, <ruby>, <xml>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Copy the characters (respecting upper/lower case) from the image.