Random question #2: Why do we need to pay an organization an annual fee to give us temporary access on a remote server to the content we already bought?
I’m speaking of Portico, one of two major competing preservation methods for e-journals; the other is LOCKSS, for Lots of Copies Keep Stuff Safe. I know — because I do, just trust me — that I’m now going to get email and phone calls from Portico people explaining to me why Portico works that way. That’s fine. Portico is a model, and it has its arguments; you can read pros and cons in this Library Journal article, written, in the ultimate form of nepotism, by me.
Portico isn’t heinous the way that Google Book Project is heinous. In fact, Portico isn’t heinous at all. There are even good arguments for hedging your bets and doing both Portico and LOCKSS. But it still bugs me that I’ve watched librarians wave Portico agreements as if they were sprinkling powder on a baby’s bottom. We need to put more thought into our decisions and not assume that the decision that involves writing a check and moving on to whatever we think is really important equals practicing strong professionalism.
But back to LOCKSS. This preservation method is a librarian-grown innovation designed to protect the interests of librarianship. Like OCA, LOCKSS is community-built and operated. Its sliding scale is very affordable, and it’s extremely easy to set up a LOCKSS box.
CLOCKSS — or Controlled LOCKSS — is a version of LOCKSS for copyright-controlled content.
The technical design of LOCKSS assumes strength in numbers and the need to repair content from time to time. A LOCKSS network has at least six nodes. The LOCKSS network audits its content and fixes it when it breaks.
The philosophical design of LOCKSS as an organization places content in the stewardship of the common librarian trust — or firmly back in the jurisdiction of collection management.