Sunday, January 11th, 2009

Why libraries must reject the OCLC Policy (part 1)

I have been thinking about the new, proposed OCLC Policy, scheduled to take effect in mid-February. I was driven to act after a recent AUTOCAT posting, in which a librarian suggested libraries not expose their collections to the web, except for “original cataloging,” for fear of the new OCLC Policy. How terrible would that be?

I’m not sure the specific fear is justified, but fear certainly is. As the Policy states, violations of the OCLC Policy “automatically” terminate a libraries right to use any OCLC records. And OCLC gets to say what constitutes a violation.

It got me thinking about compiling all the arguments against the Policy. I want to start with the process and legal ones, which have gotten very short shrift. OCLC spokespeople are persuasive personalities, and OCLC’s “Frequently Asked Questions” allay fears, but the Policy itself is a scary piece of legal writing and, as it explictly asserts, the only writing that matters.


1. The Policy fundamentally changes the character of OCLC, a “member” institution, with no formal member approval and with little member input.

WorldCat is why OCLC was created, is OCLC’s largest revenue source, the basis of most of their other services and the most common way OCLC interacts with its members. The Policy transforms WorldCat in many respects, but most of all in how OCLC relates legally to its members from a cooperative to a sort of licensure.

OCLC is supposed to be a member organization. But what member organization would fundamentally alter its core business and transform their relationship with members without putting the issue squarely before them? Yet OCLC has done just that.

2. The Policy is a legal document. No other statements matter.

The policy is a legal document, not a statement of intent or aspirations. It explicitly states (§E7) that it is “the final, complete and exclusive statement of the agreement of the partiwith respect to the subject matter hereof.” That means that the “intent” of the Policy as voiced by OCLC spokespeople or the seemingly gentler “Frequently Asked Questions” have no legal standing. If it’s not in the Policy, it’s not part of the agreement.

Licenses are legal documents. You don’t sign legal documents based on casual pleasantries. If a landlord says you can move out at any time, but the lease says you have to give notice and pay rent until a new tennant is found, trust the lease or make the landlord change it.

3. The Policy is illegitimately retroactive.

The Policy limits the use and transfer of all records, not just new ones. The diligent catalogers of forty years ago who thought that OCLC was a humble cooperative helping libraries copy catalog had no idea that they were laying the foundations of a data monopoly.

Retroactive licenses are legally dubious and morally obnoxious. If OCLC wants to impose a new license, it should not do so on legacy data.

4. The Policy is perpetual and will create a perpetual monopoly.

Most licenses lay out what does and does not “survive” termination. Not here. There is no out from the Policy whatsoever. You can leave OCLC and sit on your records for twenty years and they still effectively own them, and they can still strip your library of them at any time. The policy lasts forever, on every record it touches and no matter who touches it.

The perpetual nature of the agreement means that, once this policy goes into effect, it’s all over. The vast majority of the world’s library data is owned and restricted. What US library could even think of exempting themelves of every “OCLC-derived” record? The “network effect” is just too great.

Unless OCLC changes its mind or dies, there will be no second chance.

5. OCLC can change the Policy at any time, in any way.

As the Policy states, “OCLC may issue a modified version of this Policy or a substitute for this Policy at any time.” There is no check whatsoever on what this new policy can require or prohibit. Given the lack of member input that characterized its introduction, OCLC members may confidently expect to have no role in any future changes or “substitions” either.

A perpetual license that can be changed at any time is a lot of power to any institution. Does OCLC deserve that sort of power?

6. If you violate the policy your library automatically loses the right to any “OCLC-derived” records you have.

(§E1) “The rights to Use and Transfer WorldCat Records afforded by this Policy shall automatically terminate upon any breach of the terms of this Policy.”

Imagine losing all the OCLC-derived records in your library catalog. Imagine turning all your automated systems off until every bibliographic and authority record that passed through OCLC at any point was identified and removed from your library, and new “untained” ones found or created from scratch. What library in the United States could keep its doors open if it lost the right to use “OCLC-derived” records?

It sounds dire, but according to the Policy, if you violate the Policy in “any” way, OCLC can shut down your library.

7. OCLC has sole discretion to declare a library in violation and strip it of its records.

Not only can OCLC shut down your library, but you have no recourse to stop them. As the Policy states “[§E6] OCLC has the sole discretion to determine whether any Use and/or Transfer of WorldCatRecords complies with this Policy.”

If someone handed a government agency the power to kill libraries, and do so with no appeal or legal recourse, librarians would be in the streets in protest. Why does OCLC get a pass?

Call to action

Librarians and interested parties have only a month before the OCLC Policy goes into effect. It is time to put up or shut up.

UPDATE: Note that it’s Friday, January 16. See the page.

*I am dying to be there, but I simply can’t make it. One way or another, however, we’ll try to get our word out.

Labels: oclc

Sunday, January 11th, 2009

This is like a Heinlein Novel!

I recently enjoyed a recorded talk by Christine Peterson, co-founder of the Foresight Nanotech Institute, on open-source security and politics.

The basic point is to get alpha geeks to think about what they can contribute to basically polticial questions–to better, less invasive physical national security but also to stand up and fight against absurdities like polling machines running proprietary software, when everyone in software knows open source would provide a much better check on potential hacks.

She has a section that mirrors how I feel about the new OCLC Policy and librarians’ and library technologists’ responsibility to get engaged and do heroic things, to keep libraries “free to all” and not the cornerstone of a perpetual monopoly:

So you may be sitting there going, “God, the Constitution! Franklin, Jefferson… this is like a Heinlein novel! She’s trying to convince me I’m in a Heinlein novel, where there’s heroic action to take.”

Well, guess what, you are! You really are. This is a critical time. And there’s going to be huge decisions and a lot of work to be done. And you’re the best ones to do it. I hate to tell you that. I know you have other things to do.

Labels: inspiration, oclc

Tuesday, January 6th, 2009

New Products…

1. The iPhone Wheel:

Apple Introduces Revolutionary New Laptop With No Keyboard
Of course, every LibraryThing employee is a Mac person…

2. The Pomegranate

Would like some garlic fingers? BTW: Can you guess what this is advertising?

3. Who can forget If Amazon sucked like our old OPAC?

4. Someone should do a joke pomegranate-like OPAC video. It would start out with standard features, then add Web 2.0 features, like tagging, then searching everything every printed, then searching all TV shows, including never-aired episodes, then searching all conversations in Starbucks, Panera Bread and Roy Rogers, then searching all thoughts that took place within a meter of an iPhone, etc.

Labels: Uncategorized

Thursday, January 1st, 2009

Lawrence of Arabia’s library, and other Legacy updates

The latest addition to the ever-expanding Legacy Library universe is T.E. Lawrence, whose 1,181-title library was entered (in just two months) by Kordo, BGP, and Direlander. The collection, drawn from an inventory of Lawrence’s books made at the time of his death, is very rich and certainly worth a browse.

Lawrence’s books include a wide selection of title by authors such as W.B. Yeats (also a Legacy Library in progress), George Bernard Shaw, William Morris, D.H. Lawrence, Sir Basil Henry Liddell-Hart (ditto), Thomas Hardy, Stephen Crane and William Blake, plus many classical titles and fine press books (including a Kelmscott Chaucer).

Another recent completion (in keeping with the military theme) is Gen. George S. Patton, Jr., whose library was added to LT by sergerca and BOB81 from Roger Nye’s The Patton Mind. Not surprisingly, Patton’s books primarily concern military theory and practice.

The Libraries of Early America announcement brought a huge influx of suggestions for that project (at least forty new suggestions for collections, plus some additions to existing libraries). I’ve been thrilled by the response, and can report that some of the suggestions are already completed, with more underway. As a direct result of the project announcement, LT now includes the libraries of New York’s Lewis Morris, a signer of the Declaration of Independence (his books are now in the library of Yale Law School) and John Askin, a fur trader and local official in early Michigan. The colonial-era collection of the Pennsylvania General Assembly (partially purchased by Benjamin Franklin) has also been added, by LTer Melancthon.

2008 was an extremely productive year for the Legacy Libraries project, and we anticipate continued progress and advancement in the new year.

Labels: legacies, libraries of the dead

Wednesday, December 31st, 2008

666

Another OCLC logo parody. The person who did wishes to remain anonymous—and for good reason!


Labels: oclc

Tuesday, December 30th, 2008

LTFL Reviews now works with iBistro and Voyager catalogs

When we decided to add Reviews as an enhancement to LibraryThing for Libraries, we wanted to work on just a few OPACs at a time.

Otherwise, it would be 2010 before we finished Reviews (and no one wanted that). We started with Horizon Information Portal and WebPac, for a number of reasons*. Next, we decided to get iBistro and Voyager† on board.

We’ve had a couple of iBistro libraries add the Reviews Enhancement, but no Voyager libraries are live yet. You can check out the full list here.

* We knew the systems well, many libraries use them, and who doesn’t like saying HIP?
† I can’t talk about that particular OPAC without pronouncing it ‘vee-ger’ in my head. I’m pretty sure it’s just me.

Labels: book reviews, enhancement, ExLibris, iBistro, librarything for libraries, ltfl, sirsidynix, Voyager

Sunday, December 28th, 2008

Book blogs?

I need to broaden my horizons, and pick up a few good book-industry and bookseller blogs. I don’t care about book deals, but I wouldn’t mind some insight into how publishing is changing, particularly when it comes to technology.

I subscribe to some 114 blogs right now—mostly library-related, with a smattering of technology, startup, web 2.0 and competitor ones thrown in. But I don’t follow much in the way of publishing industry blogs—pretty much only the BookFinder Journal, Michael Cairns’ Persona non Data, Eoin Purcell, BookBrunch and Joe Wikert. And I only read one bookseller blog, the recently-discovered Hang Fire Books, which I read for the pulp covers.

Does anyone know of any good blogs?


Labels: book blogs, books

Thursday, December 25th, 2008

© Santa

Christmas 2007 Christmas 2008

Labels: christmas, copyright

Monday, December 22nd, 2008

LCSH.info, RIP

LCSH.info, Ed Summers’ presentation of Library of Congress Subject Headings data as Linked Data, has ended. As Ed explained:

“On December 18th I was asked to shut off lcsh.info by the Library of Congress. As an LC employee I really did not have much choice other than to comply.”

I am not as up on or enthusiastic about Ed’s Semantic-Web intentions, but the open-data implications are clear: the Library of Congress just took down public data. I didn’t think things could get much worse after the recent OCLC moves, but this is worse. The Library of Congress is the good guy.

Jenn Riley put it well:

“I know our library universe is complex. The real world gets in the way of our ideals. … But at some point talk is just talk and action is something else entirely. So where are we with library data? All talk? Or will we take action too? If our leadership seems to be headed in the wrong direction, who is it that will emerge in their place? Does the momentum need to shift, and if so, how will we make this happen? Is this the opportunity for a grass-roots effort? I’m not sure the ones I see out there are really poised to have the effect they really need to have. So what next?”

The time has come to get serious. The library world is headed in the wrong direction. It’s wrong for patrons—and taxpayers. And it’s wrong for libraries.

By the way, Ed, we’re recruiting library programmers. The job description includes wanting to change the world.

See also: Panlibus.

Labels: library of congress, open data

Sunday, December 21st, 2008

uClassify library mashup? (with prize!)

I keep up with the Museum of Modern Betas* and today it found something wonderful: uClassify.

uClassify is a place where you can build, train and use automatic classification systems. It’s free, and can be handled either on the website or via an API. Of course, this sort of thing was possible before uClassify, but you needed specialized tools. Now anyone can do it—on a whim.

Their examples are geared toward the simple:

  • Text language. What language is some text in?
  • Gender. Did or a man or a woman write the blog? It was made for genderanalyzer.com (It’s right only 63% of the time.)
  • Mood.
  • What classical author your text is most alike? Used on oFaust.com (this blog is Edgar Allen Poe).

Where did I lose the librarians—mood? But wait, come back! The language classifier works very well. It managed to suss-out Norwegian, Swedish and Dutch reviews of the Hobbit.** So what if the others are trivial? The idea is solid. Create a classification. Feed it data and the right answer. Watch it get better and better.

Now, I’m a skeptic of automatic classification in the library world. There’s a big difference between spam/not-spam and, say, giving a book Library of Congress Subject Headings. But it’s worth testing. And, even if “real” classification is not amenable to automatic processes, there must be other interesting book- and library-related projects.

The Prize! So, LibraryThing calls on the book and library worlds to create something cool with uClassify by February 1, 2009 and post it here. The winner gets Toby Segaran’s Programming Collective Intelligence and a $100 gift certificate to Amazon or IndieBound. You can do it by hand or programmatically. If you use a lot of LibraryThing data, and it’s not one of the sets we release openly, shoot me an email about what you’re doing and I’ll give you green light.

Some ideas. My idea list…

  • Fiction vs. Non-Fiction. Feed it Amazon data, Common Knowledge or LT tags.***
  • DDC. Train it with Amazon’s DDC numbers and book descriptions. Do ten thousand books and see how well it’s guessing the rest.
  • Do a crosswalk, eg., DDC to LCC, BISAC to DDC, DDC to Cutter, etc.

Merry data-driven Christmas!


*A website that tracks new “betas.” Basically, it tracks new web 2.0 apps. It also keeps tab of their popularity, according to Delicious bookmarks. LibraryThing is now number 12, beating out Gmail. Life isn’t fair.
**Yes, we’re going to get it going for reviews on the site itself. Give us some time. Cool as it is, we’re pretty busy right now. Note: You can’t give it the URL alone. You have to give it the text of the review.
***We may do this with tags. We already do it very crudely, using it only for book recommendations.

Labels: Dewey Decimal Classification, Open Shelves Classification, uclassify