some things really do change overnight

I’ve been getting over a nasty flu just on the backside of the MIT Mystery Hunt so I’ve been a little scarce. I also pretty much slept through most of the Inauguration festivities yesterday. However, I didn’t need to listen to speeches or see record crowds to know that some things are changing. I think Obama is as fallible as the next human being, but I’ve been encouraged at a few of the things that have happened this week, some intentional, some coincidental.

The first is Obama’s immediate revocation of Executive Order 13233, an order by the Bush administration that, according to the National Coalition for History, “severely limited access by the public to presidential records” You can read the offical text of the order on the revamped Whitehouse.gov which I recommend a look at.

The second good news this week was the Supreme Court declining to review “a Third Circuit Court decision last July striking down the Child Online Protection Act of 1998.” In other words, COPA was struck down by a US District judge, a decision which was upheld by the Third Circuit Court of Appeals and then contested by the Bush Administration to the US Supreme Court who, this week, refused to hear it. You can read the timeline yourself on Wikipedia. The Supreme Court’s failure to act is pretty much the death knell for COPA, a law that never took effect. While not as applicable to libraries as CIPA, the law itself does touch on whether or not restricting or prohibiting materials as “harmful to minors” is itself a problematic restriction on speech. U.S. District Judge Lowell Reed commented “perhaps we do the minors of this country harm if First Amendment protections, which they will with age inherit fully, are chipped away in the name of their protection.”

What happens in a copyright dispute on YouTube?

One the the benefits of my free agent status is that I can occasionally push the envelope on certain rules in a spirit of “see what happens” realizing that some small town in Vermont won’t be bankrupted if I get sued. I’ve often said that I’d like to see more civil disobedience from libraries concerning copyright legislation (especially concerning public performance rights to movies and ability to make copies of our own content) but it’s not happening quickly. That said, as you may know, I make some videos and have put them on YouTube. One of them was popular for a little while. Sadly, that one had a soundtrack from a Beausoleil album that I liked and did not have permission to use. The other much less popular video was just some shots out the window driving in a rainstorm while listening to the radio. The song in question comes on the radio for about the last minute of my video.

Last week I got an email from YouTube saying… I don’t still have the email but in short their Video Identification tool had matched a song in two of my videos and my videos had immediately been removed from public viewing. My options were to 1. delete the audio and/or use their AudioSwap feature to replace it 2. dispute the copyright claim on a few grounds 3. delete the video. I opted to try AudioSwap for my popular video, sort of sad because it removes my voiceover and other sound effects, but decent because it’s a better option than removing the video entirely. I replaced the soundtrack with a free track from AudioSwap. If I felt like I had time and energy I’d write to Michael Doucet and see if he’d give me permission, but it’s probably not even him but his record company, etc. The AudioSwap interface is clunky and may or may not put an advertisement in your video (and hasn’t worked yet for me but I keep trying) but it’s a good option to have.

In the second case, I really feel like I have a decent Fair Use case, so I filled out this form. The form says that I think the clip is fair use under copyright law. It’s my responsibility to “understand the law” according to YouTube, and that is my understanding of it. I had to “sign” it and also type [well copy/paste] the line that says I’m not intentionally abusing the dispute process. After I did that, I was sent to this help article to see what will happen next. The article warns

If the content owner disagrees with your dispute for any reason, they will have the option to submit a copyright takedown notice which will result in the disabling of your video and/or penalties against your account. To avoid penalization, only submit legitimate dispute claims.

So, we’ll see. I think I’m right. I hope the copyright holder thinks so too. At the very least they will be bored with four minutes of windshield rainstorm before they even hear their song and even then they’ll probably be straining saying “Is that it?” At the worst, I’ll get some sort of “penalty against my account” of unspecified awfulness. So, for those of you too timid to try this at home, or possibly being cavalier about the audio you swipe, that’s my report of the consequences … so far.

Who Has What – Vermont libraries’ automation systems

Vermont has a new State Librarian and I’ve been diving into more of the reports from the state Department of Libraries lately. Their most recent newsletter mentioned the Who Has What page which is a list of which vendors all the automated lirbaries in Vermont are using for their catalogs. What isn’t mentioned is that Vermont has about 192 public and community libraries. The DoL list has 86 libraries listed in the public section. You’re getting that little unstated statistic, right?

ruminating about privacy

I was emailing with a friend this week and he was saying how it seems strange that librarans are so aggressive in their defense of privacy while at the same time the population seems to be more and more shifting towards openness and “hey here’s my list of books” behavior outside of their library. I always draw the line between what people reveal about themselves versus what their institutions reveal, or must legally disclose, about them.

I also often feel that one of the reasons we’re in this strange place is because many privacy issues are ones that technology could be solving for us. Yet, at the same time the technology we’re working with doesn’t allow us the granularity of making, for example, patron reading information available in the aggregate while still keeping the patron’s identity completely private. We have many patrons

Patron 1 wants to make sure no one ever knows what they are reading. Tells the OPAC to not keep his reading list. Knows his PIN. Wants to make sure the public access PCs don’t retain records of the sites he’s visited. Is a bit horrified that the library data we do keep isn’t in some way encrypted or otherwise protected.
Patron 2 wants to know every book she has ever checked out. Wants the library to leave the name of the book she has on hold on her answering machine. Wants her friend to be able to pick the book up for her at the library. Doesn’t remember her PIN and finds it vaguely annoying that she needs more than her library card number to use the OPAC.

A privacy solution that works for Patron 1 becomes a usability impediment to Patron 2. While libraries have the responsibility to keep both patrons’ data safe, they also have the responsibility to be usable and accomodating to both patrons. Technology, in my opinion, can address these issues but librarians have to a) embrace it b) request it from their vendors c) be willing to tolerate the learning curve that comes with any new technology.

I’m off to the tiny library today to help them with their slow automation project. In the meantime, these are the articles I have been reading about privacy lately. They’re about the information the mailman has, not the librarian, but it could apply to any of us at our job as well. The blog post is about an NPR story following a mail carrier on her route. She talks about what she knows about the world and the economy based on what people are getting delivered. She is supposed to keep people’s mail private, and she never mentions any names. Yet, there’s a lot of metadata in mail delivery, things the mailman knows. The blog’s author wonders how simple it would be to identify the people getting mail delivered from the information the mail carrier imparts. Feel free to read the rest.