At ALA Midwinter, ALCTS sponsored a panel discussion about sharing library-created data inside and outside the library community, with a particular focus on cataloging data. I was honored to be ask to speak on the topic from the perspective of a consortial office. This is the first in a series of posts that represents an approximation of what I said on the panel. (Also be sure to read the summary of the session by Norman Oder in Library Journal.)
Join fellow coders, hackers and tech-enthusiasts for a two-day WorldCat Hackathon at the New York Public Library. Sponsored by the OCLC Developer’s Network and NYPL Labs of The New York Public Library, the WorldCat Hackathon gives participants the opportunity for two full days of brainstorming and coding mash-ups and other Web services to take advantage of all that WorldCat, the world’s largest bibliographic database, has to offer.
Last month OCLC announced a new service offering for long-term storage of libraries’ digital collections. Called Digital Archive™, it provides “a secure storage environment for you to easily manage and monitor the health of your master files and digital originals.” Barbara Quint has an article in Information Today called “OCLC Introduces High-Priced Digital Archive Service” in which she makes a comparison to Amazon’s Simple Storage Service (or “S3″) from primarily a cost perspective: “The price for S3 storage at Amazon Web Services is 15 cents a gigabyte a month or $1.80 a year, in comparison to OCLC’s $7.50 a gig.” Barbara also goes into some of the technical differences, but I think it might be worthwhile to go a little more into depth on them.
OhioLINK is engaged in building a “trusted digital repository” on behalf of its membership. As we build it, we want to have an understanding of what “trusted” means, and so we are engaging in an audit process to assess whether we can claim to be trustworthy. This process is panning out to have four major phases:
- Research common and best practices for preservation.
- Evaluate the OhioLINK policies and processes against common and best practices.
- Perform a gap analysis between where we are now and where common and best practices suggest we should be.
- Propose and adopt policies and processes that get us closer to the ideal common and best practices.
This is a report at the end of phase 1. Earlier this year, two major reports were released that address how one measures a “trustworthy repository.” The two reports are summarized below, followed by a recommendation.
There are just a few days left to respond to the “International Digital Preservation Systems Survey” being run by Karim Boughida and Sally Hubbard from the Getty Research Institute. From the survey description:
This survey is intended to provide an overview of digital preservation system (DPS) implementation. DPS is defined here as an assembly of computer hardware, software and policies equivalent to a TDR (trusted digital repository) “whose mission is to provide reliable, long-term access to managed digital resources to its designated community, now, and in the future”1.
This post is the second in a series about the application of the Service Oriented Architecture (SOA) system design pattern to library services. The first post in this series focused on defining “Service Oriented Architecture” using the analogy of a transportation network. This post goes into some detail about what makes a “service” in this architecture and offers an example using a hypothetical use case: a union library catalog (Open WorldCat) making a statement about the availability of a book.