Government data is at risk, but that is nothing new. The existence of Data.gov, the Federal Open Data Policy, and open government data belies the…
Government Data At Risk
Posted in Data Mirror, Digital Preservation, and UC3
UC3 :: California Digital Library Posts
Software is as important as data when it comes to building upon existing scholarship. However, while there has been a small amount of research into…
csv,conf,v3 is happening! This time the community-run conference will be in Portland, Oregon, USA on 2nd and 3rd of May 2017. It will feature stories about data…
Software Carpentry / Data Carpentry Instructor Training for Librarians
Posted in Data, events, Library Carpentry, and UC3
We are pleased to announce that we are partnering with Software Carpentry (http://software-carpentry.org) and Data Carpentry (http://datacarpentry.org) to offer an open instructor training course on May 4-5,…
Dispatches from PIDapalooza
Posted in events, Persistent Identifiers, PIDapalooza, and UC3
Last month, California Digital Library, ORCID, Crossref, and Datacite brought together the brightest minds in scholarly infrastructure to do the impossible: make a conference on…
There’s a New Dash!
Posted in UC3
Dash: an open source, community approach to data publication We have great news! Last week we refreshed our Dash data publication service. For those of…
The integration of the Merritt repository with Amazon’s S3 and Glacier cloud storage services, previously described in an August 16 post on the Data Pub blog, is…
Thanks to everyone who gave feedback on our previous blog post describing our data management tool for researchers. We received a great deal of input related…
Collaborative Web Archiving with Cobweb
Posted in UC3
A partnership between the CDL, Harvard Library, and UCLA Library has been awarded funding from IMLS to create Cobweb, a collaborative collection development platform for web archiving.…
CC BY and data: Not always a good fit
Posted in UC3
Simba dans le carton, jacme31, CC BY-SA 2.0
This post was originally published on the University of California Office of Scholarly Communication blog.
Last post I wrote about data ownership, and how focusing on “ownership” might drive you nuts without actually answering important questions about what can be done with data. In that context, I mentioned a couple of times that you (or your funder) might want data to be shared under CC0, but I didn’t clarify what CC0 actually means. This week, I’m back to dig into the topic of Creative Commons (CC) licenses and public domain tools — and how they work with data.