Also found in: Wikipedia.
LOCKSSLots of Copies Keep Stuff Safe (Stanford University)
References in periodicals archive ?
She has worked on institutional repository teams, including at Stanford, where LOCKSS was created.
Just as with regards to preservation via LOCKSS, SEER/ OJS may or may not be configured to require metadata at the time of submission, and unfortunately, the default is for it not to.
Both Portico and LOCKSS work directly with the publishers of the content, who also act as their own digital distributors.
Presumably, when Florida was a partner in the PeDALS LOCKSS plan, these were issues that were discussed, but no plan to implement these procedures was discoverable, and no law mandates such a plan or its implementation.
org/clocliss/Home, accessed July 26, 2011) has aspects of both LOCKSS and Portico.
With respect to the preservation of the digital files within the OSCDL, it should be noted that the project works upon the LOCKSS model: Lots of Copies Keep Stuff Safe.
projects as LOCKSS and Cornell's no-longer-active Virtual Remote Control but excludes such large-scale projects as Online Computer Library Center's Web Archives Workbench, now in beta testing, and its underlying methodology developed at the Arizona State Library and Archives.
While the acronym may not roll off the tongue, the powerful premise behind LOCKSS (Lots of Copies Keep Stuff Safe) comes through loud and clear.
Currently, the most famous example of this comes from the LOCKSS project at Stanford University (http://lockss.
LOCKSS provides software that converts a generic PC into a preservation appliance.
LOCKSS (Lots of Copies Keep Stuff Safe) is an online archiving program designed to provide reliable access to academic materials published online.
The system has a wonderful acronym, LOCKSS, for Lots of Copies Keep Stuff Safe--just like having (paper) copies of Shakespeare in many libraries.