First off, I am surprised and delighted at how many people are participating in this program. I have had to create a new folder in Google Reader to handle all the 23 Things traffic. Awesome.

Secondly, next week we get into RSS and the like, which is where my beloved Google Reader fits in. It’s an inbox for my blogs, for those of you unfamiliar (for now) with feed readers. New posts show up as unread, and I read as I get the time and never forget to visit one. For those of you who are already beginning to feel like there are too many blogs to visit and you’re losing your grip on how to manage the time and energy, this will make you sigh and relax. I read on a few folks blogs that they were nervous about RSS. It’s a beautiful thing that will simplify your life in untold ways. Promise.

Third, I just cataloged a bunch of beginner Linux and Web Design books for my library. I insisted that we buy them even though we do not have anything even loosely approximating technology courses of study here. My argument for them was largely based on the fact that web design is fun once you get a handle on it. Also, as a low-res school, we really need to promote these tools because most of the business these students do with the school is conducted online. Email is not really a proper place for a 75 page packet with photos. This kind of thing crashes servers and whatnot. Since this 23 things program started up and soooo many people hoped on board, I feel even better about these purchases. It proves that, as Costner would say, if you build it they will come. Most of these books are already checked out…even the Ubuntu book, and checked out by an unlikely suspect!

Lastly, I have rolled into another fatalistic mood about our ILS. Seriously, I hate it. I have put in 5 trouble tickets to their IT department already this week (we upgraded last week, which always, ALWAYS causes problems). I would never say that they aren’t trying their hardest or that their system isn’t right for some other institution, but when I start pitching to totally replace the system (as the Systems Librarian, evidently I can do that!), I keep 2 things in mind:

  1. Use the right tool for the job – this system is designed for a closed-stack library with on-campus patrons. We are an open-stack library with off-campus patrons. What with there being so many hybrids of the two systems, and so many low-res/distance only colleges now, surely there is a more appropriate tool for us.
  2. I wouldn’t torch my paycheck – we pay them too much money to have this many issues. If this were a new car, we would have called Lemon Law by now! I am a budget minded person, and my paycheck has to cover a lot of ground. Whenever I think I can save money and receive at least the same level of service I am used to, I do it. So why don’t we do this in our libraries? We constantly let these people torch our budgets.

And there it is. The big problem with number 2, of course, is finding the time to research all the options. I get accused of being tech savvy all the time, but it’s relative. To someone who has never had a cell phone or email account, I probably am. To computer programers and network administrators, whose language this stuff is written in, I am cute because I try so hard but I only half know what I’m talking about. But, I learn the language more every day. And I have people all around me who can explain terms and ideas to me if I simply ask.

I guess the point of that long ramble is choose the tools that work best for you, get your money’s worth, and use all the people who know better for your collective education. Gee, that sounds easy, I don’t know what I’m so worried about.

ps-that last bit was sarcasm, I was making a face, but you can’t see it ;)