If you’re trying to understand how LOCKSS works and why anyone would want their own copies of government data when GPO/Google/[Your Third Party Here] will keep it safe and free forever, check out these two recent news items from LOCKSS:
- LOCKSS Team featured by Library of Congress (04/24/07) Pioneers of Digital Preservation on the Library of Congress’ web site features an overview of the LOCKSS program.
- Presentation at CNI (04/17/07) Vicky Reich and David Rosenthal talked at the CNI meeting in Phoenix, AZ. Vicky gave an overview of the status of the CLOCKSS program, and David talked on Can We Afford To Preserve Large Databases?.
The LC page not only demonstrates that LOCKSS can be a trusted and TESTED partner in digital preservation, but also explains an excellent plain English explanation of how the system works.
David Rosenthal’s CNI powerpoint touches on the non-technology reasons why information solely in the hands of the government is at risk, especially his slide 18:
Example: Insider Attack
â— Political interference (Hansen 2007):
â€“ 2006 Earth Science budget retroactively reduced 20%
â€“ ”One way to avoid bad news: stop the measurements!”
â€“ Suppose the data itself turned out to be ”inconvenient” …
â— Remove it (e.g. EPA pollution database)
â— Alter it?
â— Independent replicas essential
â€“ Independently administered in different jurisdictions
â€“ Mutually audited so they’re tamper evident
The rest of the presentation is a good though slightly technical primer on performance requirements for digital preservation and the need for further research. Also has some scary things to say about RAID.
More evidence that no ONE system, not even a Future Digital one, is enough to safeguard America’s government information. No system is safe from its parent – particularly when that parent is so reluctant to fully fund information access and preservation.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.