Wednesday, April 16, 2008

Did you know you can...

Did you know you can send blog posts to Blogger by using Jott? listen

Powered by Jott

Labels: ,

Wednesday, May 02, 2007

Reference services and Twitter

A few weeks ago, a friend put the idea into my head about whether there might be a use for Twitter for reference. If you're not familiar with Twitter, here's the basics:

  • sign up for a free account
  • send mini blog posts (140 characters max) to your account via a web form, your IM client (AIM, Gtalk, Jabber) , or your cell phone (as a text message)
  • receive mini blog posts sent by those who you've selected from the Twitter network as friends; read the posts on your Twitter page or as text messages on your cell phone
As a way of keeping in touch with friends, especially when you are out and about (such as at a conference, barhopping, clubgoing, etc.), the Twitter service is pretty nifty. But is there a way libraries might want to use this service to connect to users? I've seen a couple of institutions that are having a go at it:

Casa Grande Public Library (AZ)

As Jeff Scott noted on his blog on the Library 2.0 network, took the feeds of library events, new books, etc. and fed them into rss2twitter so that they would automatically get fed into his library's Twitter account. This seems like an easy way to get greater mileage out of the RSS feeds that your library is already generating. In messages I exchanged with Jeff, he said the thought he might scale back the feed to just the day's events so users aren't overwhelmed with Twitter messages from just his library or maybe create two Twitter accounts: one for just the daily events only and another that is a mega-feed combining the various feeds the library has.

Nebraska Library Commission

Michael Sauers describes on the NLC blog how the commission has started twittering (sorry, I can't bring myself to use the more au courant term "tweeting") the latest reference questions received by the reference department. Although Sauers' blog post, which is dated March 23, says that the answers will be made available, I don't see any there yet.
Before discussing how Twitter might be used for reference services, I'd like to first note that our users might hesitate before adding the library as a Twitter friend if they intend to receive most of their Twitter messages via text messaging. As noted on the Twitter help pages, the Twitter service itself is free, but receiving the messages on your phone may incur charges depending on the plan you have with your carrier.

If you're cheap, like me, you pay for each text message received, often in the range of ten or fifteen cents per message (my monthly texting charges come out a very manageable $0, as I don't really bother with texting myself). Some folks have plans that allow them to buy a monthly bucket of messages (say, one hundred per month). Others may be so into texting that they've paid a little extra for a plan that allows an unlimited number of messages.

While our users might be interested in receiving an updated stream of library content (news, events, question/answer pairs from our reference service, new books, etc.), I'm not convinced
many users would be willing to pay for it (which they in fact would be doing if they (a) elected to receive Twitter updates on their cell phones and (b) have a phone plan where you pay a flat fee per text message or have a limited monthly supply of messages). If a library patron is also a Twitter user but elects to receive messages on IM and their personalized Twitter page, that's OK; its the folks who get Twitter on the cell phones that we might annoy. As Twitter notes to its customers, "Twitter can be addicting, so check your plan to make sure you don't get a huge bill."

Let's leave the issue behind of whether or not users would really want to add their local library as a Twitter friend; assume for the moment that they do. Is there a way that we could use Twitter to provide "reference" in some way? Perhaps. Here's an idea that builds on the way that the Case Grande Library users Twitter (use a pre-existing RSS feed to populate your Twitter account with content) and is inspired by the way that the Nebraska Library Commission promises to provide question and answer pairs:
  1. User submits question to library (via Twitter direct message option or via chat, IM, email, reference desk, SMS reference, etc.)
  2. Library answers the question and asks permission to add it (stripped of all personally identifiable information) to a publicly searchable knowledgebase available from the library's web site. That knowledgebase spits out a RSS feed of all newly entered question/answer pairs.
  3. With permission from the user, the question and answer are added to the knowledgebase, which in turn sends out its RSS feed, which itself is sent to rss2twitter to be passed along to the library's Twitter account.
The Twitter account for the library would then be advertised on the library's home page. Library users who also happen to be on Twitter could add the library as a friend in Twitter so they can receive the stream of question/answer pairs. You could streamline this model by making it just a Twitter service. There would be no knowledgebase with an RSS feed that gets fed back into Twitter. Instead, the model would look like this:
  1. Library sets up a Twitter account for reference and advertises it on library web site (among other places, obviously)
  2. Users add the library as a friend in Twitter so they can send reference questions to Twitter, having been forewarned that there is no privacy in submitting their questions this way (the library could tell users that it's like putting a question on an online bulletin board or forum). Users might also use the direct message option in Twitter to submit their questions.
  3. The library answers the question in Twitter using the direct message option.

There are more privacy issues in this second model that make me uncomfortable with it. Both models seem a bit awkward, too. My intent in publishing this post is toss an idea out there and see what kind of reaction it gets. Comments (please)?

Labels: , , , ,

Wednesday, March 28, 2007

RSS feeds for College and Research Libraries

Does anyone know of a way to get a feed of the contents of College and Research Libraries? I realize that there are tools for converting HTML pages to RSS feeds, but I have a feeling that won't work too well for the "current issue" page of College and Research Libraries, which has a unique URL for each issue.

I'm going to try fooling around with the email alerts I can get from Wilson's Education Full Text database and see if I can convert the emails I get into an RSS feed (don't know how doable this is).

Of course, it would be great if ALA itself would offer RSS feeds of its journals. My aim is to add the feedbar as a sidebar to our library's blog for reference staff.

Any ideas out there?

Labels: , , ,

Friday, February 16, 2007

Grazr + OPMLmanager = Friday fun

At the tail end of a Friday, I decided to see if I could make an OPML file using the free service from OPMLmanager so that I could build a Grazr. Or to put it in terms that make more sense to me, I used a free service (OMPLmanager) to bundle together some blog feeds, then with the file that the service created I was able to design my own customized feed reader (with a set collection of feeds) that anyone can use.

Still not making sense? Then check out the results of my OPMLmanager/Grazr project. The set of feeds selected is designed to appeal to my colleagues at work; I hope to embed this in the sidebar of our reference blog, where I earlier added a Grazr with just one blog feed.

Labels: , , ,

Friday, January 26, 2007

QuestionPoint's blog is now public

For nearly a year, QuestionPoint offered their subscribers a password-protected blog that, for those of us who use web-based aggregators like Bloglines, left us frustrated by our inability to safely add the feed to our reader. This week, QuestionPoint has dropped the password and opened up the blog to all who care to read it. Let's have a "hurrah" for this move toward greater transparency!

Read the blog here and get the feed here.

Labels: , ,

Friday, December 15, 2006

Techie blogs I "read"

Although I couldn't write code or install a server if my life depended on it, I do like to read blogs by librarians who can. Although a lot of what gets posted on these blogs goes right over my head, there is a residue of learning that takes place too. I aspire some day to better appreciate the content of these blogs below. (Please forgive my overly brief annotations for each blog, as I can't really do justice to what these folks cover in just a sentence of two.)

Blake's Journal
Blake Carver is an all-around great guy who happens to run LISNews and LISHost, the hosting service for this blog and many other library-themed blogs and sites. In his journal, he frequently discusses the challenges of running a hosting service.

Caveat Lector
Dorothea Salo's got a lot to say about open access, institutional repositories, and much more, and she's not afraid to put it in print.

Dilettante's Ball
Ross Singer from Georgia Tech helped create that library's umlaut project that (as much as I can understand it) improves on the functionality and user interface of SFX.

Disruptive Library Techology Jester
Peter Murray's blog talks, among other things extensively about SOA (service oriented architecture), which is still pretty fuzzy to me.

ebyblog
Ryan Eby writes often on issues related to the OPAC and to APIs.

Library Web Chic
Karen Coombs at the University of Houston focuses on web design issues primarily.

One Big Library
Dan Chudnov's blog also features a great series of podcasts that even a non-library-geek geek like me can enjoy and learn form.

OUseful Info
Tony Hirst from Open University authors this blog that mostly "aspirational" for a non-techie like me.

TechEssence.Info
This blog does a better job of explaining itself than I can:
You're busy. You don't have time for a lot of jargon, techie posturing, or attitudes. You've come to the right place. We don't put you down, we don't talk down to you, we just give it to you straight. Come here for accurate, understandable explanations of important information technologies for libraries. Go elsewhere for the hype.

Labels: