The @LOCKSS Program is a provider of community-centric #digitalpreservation solutions based in @StanfordLibs @DigitalLib. Lots of Copies Keep Stuff Safe.
Stanford, CA
Joined September 2016
- Tweets93
- Following49
- Followers331
- Likes17
LOCKSS retweeted
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.
LOCKSS retweeted
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
Deep within an Arctic mountain in Svalbard, Norway your open source code can be stored for generations to come in the GitHub Arctic Code Vault.
Get your code in by 02/02/2020.
#GitHubUniverse
LOCKSS retweeted
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.
LOCKSS retweeted
There's LOCKSS and CLOCKSS. A stable-well understood identifier landscape helps with digital preservation.
en.wikipedia.org/wiki/LOCKSS
clockss.org/clockss/Home
LOCKSS retweeted
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!
LOCKSS retweeted
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)
LOCKSS retweeted
Looking at technology that's best for this initiative, lead by Western Michigan Univ. Library. Will pilot with #LOCKSS solution. #AMM2019 #MIMUSEUMS2019
LOCKSS retweeted
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. xitter.cf/hvdsomp/status/9804473…
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
LOCKSS retweeted
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
LOCKSS retweeted
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
LOCKSS retweeted
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
LOCKSS retweeted
(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-race…
LOCKSS retweeted
This is a great example of the kind of risk/threat orgs need to plan for in digital preservation. Underscores need to plan for copies across independent systems. If you have 4 copies in one system and can loose access to all 4 at once you have a major single point of failure. – at Hyattsville, MD
This Post is from an account that no longer exists. Learn more
LOCKSS retweeted
So look bitrot and format obsolescence do cause problems, especially for older media and formats.
But, seriously, their impact is tiny compared to the economic and technical difficulties of simply managing large amounts of digital media.
LOCKSS retweeted
Why I think #digipres is important:
//Previously, victors rewrote history. Now, in the digital age, our adversaries could rewrite our present. //
aspi.org.au/report/identity-…
LOCKSS retweeted
@cwvandyck of @CLOCKSSArchive Alexandra Ohlson of @LOCKSS will join the Interactive Scholarly Works and Enhanced eBooks: Challenges and Emerging Solutions panel at 10:30am PST at #SSP2019, Pacific Ballroom 17 #libraries #publishing #preservation
LOCKSS retweeted
💡#LPForum19 Session Spotlight💡
How should we define a published scholarly product in our rapidly changing digital information environment?
Come help @bc_butler, @cgerman21, and Craig Van Dyck tackle this Q + suggest a framework for future practice ➡️ bit.ly/lpf_definitions
ALT May 8-10, 2019. Library Publishing Forum. Simon Fraser University Harbour Centre. Vancouver, BC.