LOCKSS

#DSHR on @LOCKSS + more recent research on auditing the integrity of multiple replicas blog.dshr.org/2019/11/auditi… #cloud #blockchain

@benosteen @hhockx 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.

Now this is awesome! Ensure your public #GitHub repos are active on 02/02/2020 to be archived in the GitHub Arctic Code Vault for thousands of years to come! #WebArchiving @internetarchive @LOCKSS

@euanc 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.

@ewg118 @anjacks0n @j_colomb @danbri @hvdsomp @alastairdunning @CrossrefOrg There's LOCKSS and CLOCKSS. A stable-well understood identifier landscape helps with digital preservation. en.wikipedia.org/wiki/LOCKSS clockss.org/clockss/Home

Complex digital film assets of sets of files and relationships between files, with checksums to maintain record of access and repair. #amia19 #libraryscience also, with the cloud #LOCKSS and geodistribution!

hilights: @IUBloomington @iulibraries 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)

Looking at technology that's best for this initiative, lead by Western Michigan Univ. Library. Will pilot with #LOCKSS solution. #AMM2019 #MIMUSEUMS2019

Pods are so cyberpunk anarchy that if we pursue, it might give birth to the Dark Scholarly Web. Then? Anyone can say anything about anything? We'd investigate Scholarly Escape Pods; launch stuff to the outer space. Lots of Copies in Space Keep Stuff Super Safe. twitter.com/hvdsomp/status…

This view never gets old 🌅

slides from @nullhandle's #ipres2019 presentation on #DigitalPreservation in the #cloud are up: web.stanford.edu/group/lockss/r… (PDF) cc: @jefferson_bail @rozross

slides from @nullhandle's presentation @internetarchive @archiveitorg web + data services partner meeting at #ipres2019 on co-hosted #DigitalPreservation services are up: web.stanford.edu/group/lockss/r… (PDF)

current @LOCKSS technical manager + 14-year program contributor @stanfordthib has assumed the role of acting @LOCKSS program manager. i look forward to supporting him through the leadership transition, over the next couple of months

some exciting personal-professional news: i'll be leaving @StanfordLibs @DigitalLib @LOCKSS later this year to join @LosAlamosNatLab research library as deputy group leader for technology strategy + services

More from @LyuboPenev's #ARPHA presentation: ✅Automated indexing & archiving @Scopus @ZENODO_ORG @PubMedOnline @DOAJplus @CLOCKSSArchive @repec_org etc. upon publication ✅Semantically enhanced articles ✅Automated maps All services:arphahub.com/about/services #ScholarlyPublishing

reliably finding article full-text is hard for machines, too! we (and others) must maintain site-specific heuristics for our archival harvesters to be able to collect content. indicates need for something like #signposting signposting.org

echoing @StanfordLibs + @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 @MellonFdn!

(7/7) With all of the above in the forefront of our minds, in our latest blog post, we ask: "Why Are So Many Scholarly Communication Infrastructure Providers Running a Red Queen's Race?" Read our take: educopia.org/red-queens-rac…

possibility of attacks on information by privileged insiders should be part of a robust #digitalpreservation threat model lockss.org/about/preserva…