Archive for the 'access' Category

while I was away – sxsw

So, I may have mentioned earlier that this is the month I’m away giving talks and talking to librarians instead of typing on my blogonet. I’m partway done. I’ve been to Florida and Alaska and Austin Texas and I’ll be stopping by Portland Oregon next week and then I’m pretty much done. I’ve done a few talks you’ve maybe heard before but the biggest news is the panel that NYPL’s Jenny Engstrom and I did at SXSW on Tuesday. It was called How The Other Half Lives: Touring The Digital Divide [link goes to our slides] and it was a look at how libraries are dealing with people on the other side of the digital divide.

Some of this is stuff you’ve heard before but some is newish. We were lucky enough to give our presentation after the FCC released the results of their broadband study but before they actually released their Broadband Plan, so there was a lot to talk about but not too much to fight about. The talk was well-attended, well-tweeted and folks asked a lot of questions and stuck around to talk more. I’ve just gotten back from Texas so I’ll save more links and discussions for a little later. Thanks to everyone who showed up and who supported us in our desire to get this talk on the roaster at SXSW. I think we gave people a lot of food for thought.

fair use in online classes?

UCLA is in the middle of discussions with the Association for Information and Media Equipment over UCLA’s use of streaming videos and video clips in their online course materials. While teachers have shown videos in classes since there have been videos, the embedding of copyrighted videos in online course, even password-protected course areas, is causing new copyright discussions. While UCLA feels that the TEACH Act of 2003 applies in this case, they are nonetheless ceasing to embed videos in online courses while they try to work out a settlement. Inside Higher Ed has a longer discussion of the issues involved in this article. One of the more interesting wrinkles is that copying a DVD in order to stream it online violates the DMCA which is not covered by the TEACH Act.

Unlike most news content online, the comments really add to the discussion happening here and I suggest checking them out. [via molly]

on defaults, and design

Aaron Schmidt has a column in Library Journal about user experience. Here is his first column. The ideas of design and user experience seem sometimes orthogonal to what we do in libraries. We are concerned with content not containers, you know “judging a book by its cover” and all that. Aaron explains why design matters and how it pervades many aspects of what we do. Sarah got the best pullquote out of it already

Every time librarians create a bookmark, decide to house a collection in a new spot, or figure out how a new service might work, they’re making design decisions. This is what I like to call design by neglect or unintentional design. Whether library employees wear name tags is a design decision. The length of loan periods and whether or not you charge fines is a design decision. Anytime you choose how people will interact with your library, you’re making a design decision. All of these decisions add up to create an experience, good or bad, for your patrons.

This comes up in my technology-instruction world quite often. Many things about how a user interacts with a computer are pre-determined or at least have a default setting. So the talking paperclip? Someone made a choice that you would see that, instead of having it be a turn-onable option. The “your computer may be at risk!” messages? You can turn them off but the default is ON. These are all choices, actively or passively made. My feeling is that the more we explain to people that they can re-make some of these choices [get the talking dog away from the search box!] it empowers them to envision their computing experience the way they might want it to be, to know they have choices.

when good librarians go bad, genuine options in librarianship

I upgraded WordPress this week. Please let me know if anything is wonky.

This is an exchange from facebook with names changed to protect the innocent. It highlights something I find happening to me in the library world all the time — having to balance solving the problem with following the rules. The person posting the update needed an article. The rules said they had to pay $31.50 for an article. This didn’t pass the sanity check ["$30 for one article from a journal, that's crazy!"] and the librarian was grousing. They’re also grousing to a huge network of librarians, many of whom had free [or, paid for by their institution] access to the same content. I saw Nicole speak in Florida this past week and one of the quotes she repeats again and again is “With enough eyeballs, all bugs are shallow” meaning that a particular coding problem that might vex one or two programmers is unlikely to vex, say, a thousand programmers.

My Jessamyn corollary to this is “With enough libraries, all content is free.” That is to say… if the world was one big library and we all had interlibrary loan at that library, we could lend anything to anyone. The funding structures of libraries currently mean that in many cases we’re duplicating [and paying for] content that we could be sharing. This is at the heart of a lot of the copyright battles of today and, to my mind, what’s really behind the EBSCO/Gale/vendors. Time Magazine is losing money and not having a good plan for keeping their income level up, decides to offer exclusive contracts to vendors and allows them to bid. EBSCO wins, Gale loses. Any library not using EBSCO loses. Patrons lose and don’t even know they’ve lost.

When I was blogging for BoingBoing I often came across content that I didn’t have access to. I was also confronted with, in many cases, unreasonable fees requested [$9.95 for 100 words, really?]. Me being me, I could always find a librarian with access to, say the Times Online archive, or old articles in JSTOR. But I also felt it was cheating. But I was also annoyed that being resourceful is also somehow cheating. And I knew that many of my patrons with fewer resources would just pony up. Where do we draw the line between enforcing other people’s rules and solving problems with our patrons? Now that we’re getting more and more networked, this whole idea of local content works for some things [historical photos, town history] and not for others [journal articles that are held in thousands of libraries worldwide]. Do we have a plan for moving forward?

what happens when you don’t get what you pay for

Nicole wonders aloud why people who paid for an Open Source OPAC from LibLime aren’t raising hell when they are instead pressured to accept the closer-source version instead?

So why are these librarians taking it? Why are they being quiet? I don’t have an answer for you – and so I’m hoping someone out there can answer this for me. If you signed a contract for one product and then are told you have to use another – do you just say okay? or do you move on or demand the product you originally wanted. I think that the result of the Queens Library law suit will be very interesting – but I’m shocked that this is the first!! Librarians have been just taking these hits and coming back for more.

Jessamine county has very little in common with me

You probably saw this on the tubes today. Library workers in Jessamine County Kentucky [a library system I've featured in talks before, though I can't remember why] got fired when it was discovered they’d colluded to sort of permanently check out graphic novels to keep kids form being able to check them out Please feel free to read more

Amusingly, the graphic novel in question was Alan Moore’s The League of Extraordinary Gentlemen: The Black Dossier. Yesterday was his birthday.

an open letter to the Evergreen Community

I’ve been trying to blog less right before a weekend — convenient time for me, less convenient for readers, but I read The Equinox Promise: An Open Letter to the Evergreen Community and felt that I should pass it along. The whole LibLime thing has been sort of upsetting both because they seemed to both totally adhere to the letter of the law [and the license] and so totally run roughshod over the spirit of the open source community. I think it’s safe to say that Koha wouldn’t be where it is now without the efforts of LibLime, but I’m a little more concerned thatn usual for where it’s going. Ever since the Evergreen Conference that I went to, where I got to hang around with a lot of really excited and capable people, I’ve been pretty jazzed about Evergreen as well. Here’s hoping…

what’s the real story behind Brooklyn Public’s removal of TinTin from the shelves?

Not trying to start a flamewar here, just thinking that this NY Times blog piece about an old racist Tintin book may be a little off. According to the article…

[I]f you go to the Brooklyn Public Library seeking a copy of “Tintin au Congo,” Hergé’s second book in a series, prepare to make an appointment and wait days to see the book.

“It’s not for the public,” a librarian in the children’s room said this month when a patron asked to see it.

The book, published 79 years ago, was moved in 2007 from the public area of the library to a back room where it is held under lock and key

The article also has, even more interestingly, some of the actual challenges filed by BPL patrons in which the patrons’ addresses are removed but their names and City/State information are published. If your name is unusual redacting your address doesn’t really protect your anonymity. I’m curious what the balance is between patron privacy and making municipal records available.

update: I got an email from the patron whose name I used asking me to remove it. I have done so.

Koha and LibLime and the letter and the spirit of open source

Another link or two about the thing I mentioned in my day in the life post from a week or so ago. I had mentioned there was some Koha/LibLime drama but I didn’t know much about it. I spent some time emailing with people asking about it — my library is a Koha library, or a nascent one, so this is professionally as well as personally interesting to me — and reading a lot of email and chat transcripts. My impression now is that there’s a little bit of a “there” there and now there’s something I can link to.

This thread on the Koha users discussion group list outlines some of the issues. In short, what I understand, and please correct me if I’m wrong, is that LibLime is building features into their hosted version of LibLime that may not be rolled into the main version of Koha that is openly distributed. This became apparent during a user group meeting tha thappened at ALA, a loose transcript of which is included in this discussion. This release option is technically okay according to the terms of the license which is GPL V2 which says that only released code needs to be made available to the larger community. Some clients feel that this is against the spirit of what they thought they were purchasing which was code they’d have access to and that they could edit and/or alter themselves. Other large clients like WALDO want their investment in improvements protected, it seems.

LibLime has lost some staff recently and it is felt that there is a schism growing in the Koha community over this and related issues. I’d be interested to know if other people are running into this.

Apple sort of censors the dictionary

Noted without (much) comment: “Apple requires you to be 17 years or older to purchase a censored dictionary that omits half the words Steve Jobs uses every day.” Please feel free to cleanse your palate of the bad taste in your mouth by reading this old article form The Atlantic Monthly which includes my favorite dictionary joke (ah yes we librarians have dictionary jokes…) punchline: ‘So you have been looking for them, Madam?’