thing 5 & 6: flickr

So, we’ve been doing this thing at work following the Learning 2.0 model that Helene Blowers developed for the Public Library of Charlotte and Mecklenburg County a few years ago. We’re on week three and thing five & six, which involve posting something on Flickr (been doing that since March 2005), adding it to the pool, and then blogging about the experience. Alternatively, participants can find an interesting photo on Flickr and include it in a blog entry (with proper attribution, of course).

For me, doing the basics was nothing new, so that part was… well… boring. However, it leads into thing six, which is to explore Flickr mashups. I made this using the Spell with Flickr tool:
E C coloured card disc letter l DSC_1576 c T C
DSC_1410 Copper Uppercase Letter I Brass Letter B _R (2 days left) A R i a in the pavement, kalmar, sweden McElman_080417_6572_N

I have played with Tag Galaxy before, and I have an old Librarian Trading Card. I decided to make a new card, and I’ve bookmarked the color pickr for later use.

For my fellow TechLearners and anyone else out there who cares, I suggest you don’t use Flickr’s Uploadr if you need to upload a bunch of images (as in, more than 10). Something broke with version 3.0 and more often than not I get upload errors when I try to use it. I have not tried it on the Mac, so it’s possible that my problems are Windows-specific.

thinking like a user, not a librarian

I should have know that this would be the slippery slope that lead to… a wishlist.

I did something today that was revolutionary. Well, for me, anyway. I tagged an album on RateYourMusic that I do not own, nor have I ever owned. I tagged an album for my wishlist.

I have been treating RateYourMusic as a LibraryThing for music, which it pretty much is, without all the flair and design and integration that LT currently provides. My personal rule (a.k.a. thinking like a librarian) was that I would “catalog” what I owned, not what I wanted or had previously owned. That’s how I roll over at LT, and for my book collection, it makes a lot of sense.

My music collection, however, is much more fluid. I’m less likely to hang on to a CD once I’ve grown tired of it, so I regularly trade out “old” albums for “new” ones. A while back I started tagging albums as “used to own” rather than completely de-accessioning them. Because I’m regularly acquiring new music, I need to know what I’ve already evaluated and passed on, and this is one way to do that.

I should have know that this would be the slippery slope that lead to… a wishlist. Sure, I have wishlists all over the place, from Amazon to the various swap sites I participate in. However, RateYourMusic is supposed to be a catalog, right? And a library catalog doesn’t have wishlist items, right? (Well, unless you count those books that never show up from the publisher/jobber/vendor.)

This is the point at which I stopped thinking like a librarian and started thinking like a user. Having a wishlist mixed in with my have and use-to-have lists means it’s all in one, indexed collection. It feels freeing to let go of the “rules” that keep me from using all of the tools available to me!

more degrees for the same pay

In a recent Chronicle article, Todd Gilman complains about the lack of job postings for librarian subject specialists who have secondary master’s or doctoral degrees. While I think he makes valid points for why subject specialists should have post-graduate education in their fields of study, particularly if they are in tenure-track positions, I think he misses the mark as to why libraries are hiring folks without those degrees.

In that job posting and many others, the most attention paid to subject expertise (in the form of a master’s or Ph.D.) is a brief mention in the list of “preferred” qualifications. That is a strong indication that the hiring institution will settle for less — much less. In fact, I’m told that in a number of recent hires, Ph.D.’s and M.A.’s — some with years of professional experience working in top academic libraries in addition to having an MLIS — have been passed over in favor of candidates straight out of library school whose only previous degree was a bachelor’s.

Were they passed over because they asked for more compensation than what the institution was willing to pay? I suspect that may play a much larger role than what Mr. Gilman is giving it.

Libraries are usually the first target for budget cuts, and one of the biggest expenses in a library is staff salaries. Someone who has post-graduate degrees beyond the MLS will likely expect to be compensated for the additional skills and knowledge they bring to the job. University administrators either don’t understand or don’t care about the value that these folks add to collections and instruction, and as a result, they are unwilling to meet the compensation demands of these “better qualified” candidates. Recent graduates in any field will cost the university less in the salary department, and that short-term benefit is the only one that (mostly short-timer) administrators care about.

Given all that, would you go through the trouble of getting a second master’s degree or a doctoral degree, knowing that unless you are already in a tenure-track position with fair compensation, it is unlikely that you’ll be payed any more than you are already? Probably not, unless you were particularly passionate about research in your field of study.

Even so, that research might not help you with tenure, as some colleagues of mine discovered when their institution’s tenure requirements changed so that scholarship in their primary field (read: library science) alone counted towards tenure and post-tenure review. Nevermind that they focused most of their scholarly research in their secondary subject specialties.

All of the above is why I took myself out of the tenure-track world. I have no interest (at this time) in becoming a subject specialist in anything but what I do every day: librarianship. I’m happy to let others make decisions about content, so long as they let me focus on my areas of expertise, such as delivery platforms, access, and licensing issues.

css.php