Although I've gotten some good comments to my postings about patron privacy and RSS feeds, I've gotten lots of reactions that make me feel like I "have lobsters crawling out of my ears." (description borrowed from Paul Holliday, Cranston Public Library.)
That is, just seeing "RSS Feed Security" makes some folks feel a little gooey, even when they otherwise have great clarity on the importance of patron privacy. Yet what good does it do to take a stand against the PATRIOT Act if library records are not terribly private in the first place?
Here's a summary of a series of posts on what I've learned as I've tried out Library Elf - a third party service that offers email and RSS delivery of your own patron record, as well as the records of other cards you input. This can be done without your library's involvement, since the Elf finds library patron databases on its own.
Problem One: By signing up for RSS feeds, some library users can unwittingly show others what they have checked out.
I accidentally stumbled on live patron records, including email addresses, first names, and titles of books checked out, on hold etc. I found them by typing "library elf" into a bloglines search box. What I saw were records of patrons from various libraries who signed up for Library Elf's RSS delivery to Bloglines.com, a popular web-based RSS reader.
Library Elf took quick action (A+ on responsiveness) after my discovery and immediately stopped sending out those particular RSS feeds. It also issued a warning to users about this issue. Today it says "error error error" if you do the search. In fact, if you've never seen an RSS feed, congratulations for reading so far into this post. To see one, do the Bloglines search right now and click on one of the matches. You'll see a frozen snapshot of pretty much what I saw. You may have to scroll down to see the actual patron records.
The Seattle and Ann Arbor public libraries offer direct RSS feeds from their libraries (don't need Elf) to deliver patron records. Maybe your library does too. These libraries have apparently been grappling with the privacy issue for some time, and do not show the patron's email address in the RSS feed. Seattle shows the patron's first name (not bad for "Joe" but not so great for "Esmerelda"). Ann Arbor shows no names, no identifying information.
Both Seattle and Ann Arbor issue warnings to users that their feeds may be public, though Seattle's warning makes it sound like you can set your feeds to "private." (In reality, even setting a feed to "private" when using Bloglines does not make it private).
How to fix it: Probably look to Ann Arbor District Library as a model - no names, no identifying information, warnings to patrons.
Problem Two: Even when patrons don't sign up for RSS feeds or even know what they are, snoops can sometimes get RSS feeds to see what other people have checked out -- if the library has weak patron database security.
Libraries that let you see your record just by typing in the card number (and sometimes a PIN like the last four digits of your phone number) have pretty-poor-privacy-security. At one level, I guess I always knew that, but using Library Elf made me realize that it's a bigger problem than I realized.
That is, signing up with Elf (or a related service if there is one), allows you to enter multiple library cards all at once, and get the records sent to you regularly, by RSS or by email. Either way, you don't have to go back time after time to hunt for records. Takes 99% of the work out it - just take five minutes to set it up one time, and get other-people's-library-records delivered to your computer til the end of time. Quick, easy, convenient snooping.
How to fix it: (1) Libraries could stop letting patrons into library patron databases or (2) Libraries could greatly strengthen the passwords needed to get in. Don't use card numbers and phone numbers. Let patrons set up their own user names and strong passwords.
----------
As always, feel free to comment with clarifications or corrections. I'm not a techie, but a library law consultant, concerned with privacy of patron records.
-----
Jan 6 note - I'm still tinkering with some wording in this post to try to make it clearer - if I think I'm changing any substance I'll try to indicate that. - MM
Recent Comments