
LOCKSS
@lockss
The @LOCKSS Program is a provider of community-centric #digitalpreservation solutions based in @StanfordLibs @DigitalLib. Lots of Copies Keep Stuff Safe.
ID: 778004714055016448
https://www.lockss.org/ 19-09-2016 22:55:53
94 Tweet
340 Followers
49 Following

@ewg118 Andy Jackson @j_colomb Dan Brickley W3C.social/@hvdsomp (Herbert) Alastair Dunning Crossref (inactive Jan 2025) There's LOCKSS and CLOCKSS. A stable-well understood identifier landscape helps with digital preservation. en.wikipedia.org/wiki/LOCKSS clockss.org/clockss/Home

@benosteen Helen Hockx-Yu Maybe I’ve missed it but there seems to be surprising little in the literature about tactics to help protect content from our own mistakes. Replication strategies, use of file system permission to avoid accidentally changes etc.



echoing Stanford University Libraries + @StanfordVPTL Michael A. Keller here: mellon.org/media/filer_pu… + our own Chief Scientist Emeritus #DSHR here: blog.dshr.org/2019/08/a-trib…, we congratulate @djw0952 on his retirement + celebrate his impactful legacy Mellon Foundation!


More from Lyubomir Penev's #ARPHA presentation: ✅Automated indexing & archiving Elsevier | Scopus Zenodo PubMed Online DOAJ CLOCKSS RePEc etc. upon publication ✅Semantically enhanced articles ✅Automated maps All services:arphahub.com/about/services #ScholarlyPublishing


some exciting personal-professional news: i'll be leaving Stanford University Libraries Stanford Digital Lib LOCKSS later this year to join Los Alamos National Laboratory research library as deputy group leader for technology strategy + services


slides from Nicholas Taylor's presentation Internet Archive Archive-It web + data services partner meeting at #ipres2019 on co-hosted #DigitalPreservation services are up: web.stanford.edu/group/lockss/r… (PDF)

slides from Nicholas Taylor's #ipres2019 presentation on #DigitalPreservation in the #cloud are up: web.stanford.edu/group/lockss/r… (PDF) cc: @jefferson_bail Roslynn Ross, CEC



hilights: IU Bloomington IU Libraries has multiple redundancy copies and uses #LOCKSS and #CLOCKSS -- what is the effect of all of these copies, the server space, the energy, etc? (might be of interest @SarahEHare @hoops_jenny & IUSW)




Euan Clements I know I can be naive and idealistic, but this is why I advocate for community-built resources, included shared infrastructure. This is what libraries have always done, after all! I think we're just trying to figure out what digipres looks like in that kind of consortial space.
