Thanks for point out.
The algorithem in LOCKSS is to use peers in the network to preserve/restore/repair files (by voting with the majority). My question is: if I have a MD5/SHA signiture, I know if the file is authenticated. Why do I need a vote?
As your library is a member of MetaArchive, could you explain more about how you handle the digitial signiture? do you do any modification of the LOCKSS source code?  what about the cost? (in this case, I assume that you are using PC as a storage unit. the cost should be lower).

From: Beth Nicol []
Sent: Monday, January 29, 2007 7:31 AM
To: OSS4LIB (E-mail); Han, Yan; Ferran Jorba
Subject: Re: [oss4lib-discuss] Storing and keeping safe thosehugedigitalisation files

I'm not sure what you mean by "it does not work for straight TIFF/PDF's" -- you must organize your files into Archival Units, and create a manifest page just as you would for a journal. I've harvested several GB's of tiff's using LOCKSS.

Beth Nicol <>
Information Technology Specialist
Auburn University Libraries

>>>"Han, Yan" <> 01/26/07 3:09 PM >>>
This is not an easy answer for your questions.

my understanding of LOCKSS is that it does not work for straight TIFF /PDFs. There are organizations who can take care of your problems. OCLC is testing the idea of preservation. There is also a research project going on with NDIIPP project, which has a consortium to do digital preserv! ation. (Emory U. is one of the partners).

Or you can just buy some hard drives/tapes and save multiple copies in off-site storage. but in this case, you are responsible for the migration of formats etc.

I like the idea of consortium preservation, but there are other issues to be sorted out.

Yan Han
The University of Arizona Libraries

-----Original Message-----
From: on behalf of Ferran Jorba
Sent: Thu 1/25/2007 8:33 AM
To: OSS4LIB (E-mail)
Subject: [oss4lib-discuss] Storing and keeping safe those hugedigitalisation files


I'm going to ask help for something I'd say it is a common situation
nowadays mostly everywhere.

My university is engaged in digitalisation of old material, like most
do.  So do some of my neighbour univesrities.  Our libraries belong to
a local consortium, like ! most libraries do.  This digitalized material
means, among other things, lots of fat TIFF files, totaling a huge
amount of Gigabytes.  I think most of you know that.

There are plenty disk array vendors willing to sell you their
solutions.  I like specially Capricorn Tech
(, due to their pedigree,
and Copan Systems ( for their MAID concept.

But one of our most urgent problems is keeping those original TIFF
(and their corresponding PDFs) safe beyond just storing them
somewhere: I mean having more than one copy, doing backups, veryfiying
checksums, automatically fixing the damaged files, maybe changing
formats, etc.  This second part is already invented, and it is called
LOCKSS (  It is a software with anything I could
ask for, and more.

What I have been unable to find in the L! OCKSS site is a configuration
model where some libraries, in a local consortium, join together to
keep jointly this material.  Ok, I understand that LOCKSS is designed
to keep the material of [external] publishers.  But when I first
learned about CLOCKSS (Controlled LOCKSS) I immediately thought that
it would address the scenario we are facing in our consortium.  However,
I cannot find it in their web pages.

May I ask how are you addressing this scenario?  If there is a better
forum for this question, I'd gladly ask it there again.



Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
see also

Take Surveys. Earn Cash. Influence the Future of IT
Join's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash

see also