Category: access

What is up with OCLC?

Posted on by jessamyn

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.

world usability day is tomorrow

Posted on by jessamyn

If you’re into the whole usability idea — and more and more our interfaces to technology are all we have when interacting wiht the goods, services and government in our lives — then you might like to know that World Usability Day is tomorrow. I’ll noodle around a bit looking at my own websites and I suggest that you and your libraries do the same.

Technology should enhance our lives, not add to our stress or cause danger through poor design or poor quality. It is our duty to ensure that this technology is effective, efficient, satisfying and reliable, and that it is usable by all people. This is particularly important for people with disabilities, because technology can enhance their lives, letting them fully participate in work, social and civic experiences. Human error is a misnomer. Technology should be developed knowing that human beings have certain limitations. Human error will occur if technology is not both easy-to-use and easy-to-understand. We need to reduce human error that results from bad design.

School Library Journal throws down the gauntlet in ALA’s direction

Posted on by jessamyn

I did some email back and forth with Brian Kenny from School Library Journal last month when I was trying ot find back issues of their content online. I incorrectly assumed that because I couldn’t find it, it wasn’t there. He took the time to set me straight. Now he’s written an editorial for SLJ asking ALA why more of their content isn’t freely available online, drawing the same conclusion I have “[L]ibrarians are the most vocal advocates for open access to journal content—except, apparently, when it’s their own publications.”

thinky paper about facebook and privacy and the law

Posted on by jessamyn

My friend James Grimmelman, New York Law School professor, has published a paper about Facebook and Privacy which is my Labor Day reading. In it he asserts that while Facebook is partially culpable for having bad privacy policies and practices, a more nefarious side-effect of the Facebook universe is that the model encourages people to violate each other’s privacy. When you share information about yourself, you wind up sharing information about others who may have different approaches to personal privacy than you do. If you’re interested in understanding more about the Facebook mechanisms from someone who both uses and studies it, I suggest giving this article a read.

You think you’re my friend; I disagree. We may be able to work together in real life without needing to confront the basic fact that you like me but not vice versa. But if you Facebook-add me and say “We dated,” what am I supposed to do? Uncheck that box and check “I don’t even know this person?” Divergences are made manifest, sometimes to mutual chagrin.

Facebook’s reputation on privacy matters is terrible. When people use “Facebook” and “privacy” in the same sentence, the word in between is never “protects.” Facebook’s privacy missteps haven’t just drawn the attention of bloggers, journalists, scholars, watchdog groups, and regulators, they’ve also sparked mass outrage among Facebook users. An anti-Beacon group attracted over 70,000 members. and an anti-News Feed group over 700,000. Facebook’s pattern—launch a problematic feature, offer a ham-handed response to initial complaints, and ultimately make a partial retreat—hasn’t given it much privacy credibility. In short, consumers don’t, can’t, couldn’t, and shouldn’t rely on Facebook’s privacy policy to protect their personal information as they use it.

If you read all the way down to page 40 or so, you’ll get some analysis of legal attempts at social networking site use restrictions including DOPA which many librarians should be familiar with.

YakPac

Posted on by jessamyn

I subscribe to the LibLime news blog which is often announcements of libraries that have decided to go with Koha. It’s an interesting blog, I’m always curious who decides to go to the Open Source route. This latest announcement about the Derby Public Library cheered me because not only are they going with Koha, they’re implementing YakPac which is a kid-specific OPAC that still has a huge degree of functionality. I show it off a lot in my 2.0 talks because it’s engaging and entertaining and represents the answer to the question “how far can you go with the OPAC?” without a lot of bells and whistles, just fun easy-to-use design.