I've been peer-reviewed

My first peer-reviewed article "Firefox Search Plugins: Searching Your Library in the Browser" has just been published in Volume 1, Number 1 of The Journal of Web Librarianship. I'm not specifically excited over the fact that it's a peer-reviewed journal. I'm not an academic so that's not exactly a requirement for me. I've written eight previous books and dozens of articles so I'm not exactly lacking in the publication category. Yes, I'm glad to have another article published (it has been a while and no, Christie, I haven't forgotten that podcasting article we talked about at CIL) as always, but the peer-reviewed thing at this point is just fitting into that "nice, added bonus" category.

However, I do have one, not so much complaint, as a concern over this whole experience: the fact that an article I submitted to the journal back in July 2006, wasn't published until July 2007. One year for a technology article to see print. These day's that's not even vaguely fast enough. In my specific case, at the last minute (December 2006), I had to get an extra few sentences added to the beginning of the article to say that the code I'm talking about was replaced with a different code/method with the release of Firefox 2.0 but that my code would still work. (Given the opportunity I would have re-written the whole article but the process was too far along for that to happen.)

The world of peer-reviewed journals is not mine. I don't have suggestions for fixing this, nor will I spend all that much time on it. I just needed to say all this, as I'm sure I'm not the only author with these concerns.

I'm in Walt's index

I just got our copy of Walt Crawford's Balanced Libraries: Thoughts on Continuity and Change and lo, what do I find in the index, but my name!

"Do you have a carefully developed acceptable use policy for internet access within the library? Why? What makes internet resources different from books or magazines, in terms of acceptable use within a library setting? Wouldn't it be more straightforward to have an overall acceptable-use policy that applies to all library resources? Eliminating redundant policies saves time and makes application more consistent and defensible. For that matter, you might be able to simplify library policies in general by taking a different approach. Read "Don't doesn't work" by Michael Sauers. I find his case for consistent, simplified, behavioral policies compelling—and almost certainly time-saving."

Thanks Walt! I can't wait to read the rest of the book.

Book signing @ CIL2007

For those of you that still don't own a copy of Blogging and RSS: A Librarian's Guide and will be attending Computers in Libraries in April, I will be doing a book signing at the Information Today booth. It will be during the afternoon coffee break on Tuesday from 2:30-3:15pm. See you there!