What is up with OCLC?

This all started with a little wink-wink posting about OCLC from Tim over at LibraryThing which was the first I’d heard about OCLC’s policy changes. As someone who doesn’t interact with OCLC or their data too much, I didn’t really understand this and had to wait for some clarification posts to understand both what was going on and how it affected people and projects like LibraryThing and Open Library. The upshot as I understand it is that OCLC is basically saying “Sure you can share your records, but not with people or organizations who materially compete with us” That’s my summary anyhow. Here’s the non-legalese policy on the OCLC site. Here’s the more legalese version. Here’s a wiki version of the changes between the “old” new policy and the new policy. Isn’t technology grand? Karen Calhoun a VP over at OCLC has written a defense of the new policy on her own blog; there is some lively discussion happening in the comments. There is also this podcast of Roy Tennant and Karen Calhoun talking with Richard Wallis from Talis (whose business model is also potentially affected by this policy change) about the ramifications of this change.

So, the policy OCLC has put up has been revised somewhat, doesn’t go into effect until February, and gives people a lot of time to think about what if anything they want to do about this. Tim Spalding has a business model that is compromised by OCLCs refusal to let their members share these records. The Open Library project is also possible compromised and Aaron Swartz has written two posts about the policy change: Stealing Your Library: The OCLC Powergrab and OCLC On The Run. He also directs people to the Stop OCLC Petition if you’d like to sign on to ask OCLC to repeal these changes. More community discussion taking place at MetaFilter, Inside Higher Ed, and Slashdot and code4lib is maintaining a wiki with links to more commentary. I’m still catching up on the back and forth and may write more later, but it’s interesting to watch this unfold.

Open Library, really open. Aaron Swartz discusses.

David Weinberger blogs about Aaron Swartz talking at the Berkman Center about the Open Library project. Pay close attention to the Q and A and think about this in terms of the Google Books post/article from yesterday. Who is really in faveor of openness? Who talks the most about openness? Want to help? They still need programmers. And book lovers.

Q: Why won’t OCLC give you the data?
A: We’d take it in any form. We’d be willing to pay. Getting through the library bureaucracy is difficult…
A: (terry) You need to find the right person at OCLC
A: We’ve talked with them at a high level and they won’t give us any information. Too bad since they’re a non-profit. Library records are not copyrightable. OCLC contractually binds libraries.

job opening: data munger needed for Open Library project

I rarely post links to job here because it seems to me that most postings for library jobs are more or less the same. This one is different. The Open Library project, which I linked to here before, is looking for some new folks. You’d be working with a fun team of geniuses, most notably Karen Coyle who is the chief librarian of the project. Telecommuting an option. Interested? Read the job description, then email Aaron and tell him you heard about it here.

Tasks include: working with our chief librarian, Karen Coyle, to implement algorithms to do data merging and other processing tasks; writing scrapers and crawlers to grab various data sources; writing importers to parse this data into something that can be imported into our database; and managing all the people who want to help us with these tasks.