Differences of opinion

Catalogers do not always agree. Frankly, much of the time we don't agree. But that's what cataloger's judgment is all about. Three people can see at least 5 different ways to catalog the same thing. We all work in different environments and while we all ultimately have the same goal to make things findable for our users, our users are often very diverse and different, so we catalog things in different ways to accommodate that. Variety in local practices can be astounding, but exist to serve a specific set of users' needs. What the users of an art library need will be very different than a set of elementary school students, which will be different still from undergraduates, who are different than researchers, etc. You get the idea.

This is where the "play nice with each other's records" clause comes into the guidelines for cataloging in a shared utility environment. Unless it's flat out wrong, you don't change it. Edit your records locally (by all means!), but do not edit the record in the big shared database. Local practice is just that, LOCAL. And just because you don't like the way someone phrases their notes is not a reason to change it, even if you're editing something else in that record. You only change it in the shared database when it's wrong/outdated or you are adding new/additional information. Additionally, you don't delete things that aren't wrong, even if they are from previous cataloging rules and no longer part of our most recent set of rules (which, by the way, are going to be changing again in the next few years). They aren't "wrong," just no longer used. So leave it alone, I don't care if you don't like it or it looks "ugly." Play nice, people, and edit locally to your heart's content.

These differences of opinion can become a problem when one cataloger is the reviewer of another cataloger's work. It can become a serious issue when the cataloger and their reviewer don't agree on things like note phrasing. Some of the differences of opinion are downright pedantic. My institution uses *this* phrasing but their institution uses *that* phrasing. Both options are correct because it's a free-text NOTE field, people! Yes, there are guidelines for notes, and books of example phrasing, but even within such guides and books there is stunning variation.

So why oh why do I have to phrase my note the way you want me to? Oh yeah, you're reviewing my records. And until I phrase things the way you want them phrased, I'm doomed to continue to having my records reviewed. Never mind that as soon as you turn me loose I'm probably going to phrase my notes the way I see fit. And that's OK, because both of us are correct.

Don't you just love cataloger's judgment?

Proof that I'm busy

Alternately titled: Proof that I'm a dork

I realize there's been a lack of regular posts lately. Well, I've been a bit busy. Still am. But I offer up the following story as proof that I really am that busy.

I am a cataloger. A continuing resources and electronic resources cataloger to be specific. I am extremely detail oriented by nature. I always have been. Fortunately, this trait is beneficial in cataloging. So my career choice is a very natural fit. What you need to take away from this paragraph: Shana = detail oriented. Little things don't usually slip through the cracks.

As you all know, we're undergoing a forced software migration. Two big services are merging, and one of them is being folded into the other. Unfortunately, my library was part of the service being absorbed, so we're migrating to the "other" service whether we like it or not. I have lots of experience with this other service, so I've been doing a lot of training to help facilitate this change. This is not news.

In June at the big ALA Annual Conference, we learned of the deadlines. The service being absorbed will be going away ("retired") the end of August. But, as of the end of July, while it will be there, nothing new will be added to it, rendering it pretty much useless for anything but searching legacy data. That means that as of August 1st, everyone in my library has to be using the "new other" software full time. This migration to the "other" software can't be completed until everyone upgrades to the new version, 2.0, of said software. Version 2.0 included some major changes, so it was decided that "orientation" sessions highlighting those changes needed to happen before everyone downloaded the update and started using it. It took me a few weeks to put together handouts, and I split the sessions over two weeks in the hope of accommodating various vacation schedules (it is, after all, the middle of summer).

So last week when I began the sessions I put a request into the IT department for them to put together the webpage for the software update. This is a standard "loader" webpage with instructions, and a link to the file they need (unzipped and ready to use), that is used for any software update/download at my library. No big deal. I asked that they put together the loader, but hey, told them they've got time because I don't want it sent out until AFTER I finished the version 2.0 orientation sessions (which I did on Wednesday). I even included a date in my message that they should send out the email to the staff with a link to the webpage with the download instructions.

I SENT THE WRONG DATE.

I looked at my message again today and panicked. Instead of Friday JULY 27th as the date in my message, I put Friday AUGUST 27th. I put the MONTH in wrong. This is a rather large problem, given that the staff need the software update by next Wednesday, not a month from now. So I sent a message apologizing profusely and asking that they put together the loader ASAP (please, pretty please, with sugar on top??). I got a reply, a very gracious reply, telling me they should be able to have something ready by tomorrow morning.

*whimper*

And at the same time, I had to send another message to IT asking them to install the software on the 17 machines in the electronic classroom so I can do some hands on training sessions next week (Wed. and Thurs.).

*sigh*

I either need more sleep or a nice stiff drink...I'm not sure which one is more appealing at the moment.

*headdesk*