Building a career on laziness

It worked for me - building a career on other people's laziness.

Most people don't want to spend time checking data, or working on data repairs - it's not exciting or glamorous, even if it teaches you an awful lot about the way the database works.

Most people don't want to go to boring routine meetings - but even the dullest meeting has other people at it who might turn out to be really interesting.

Most people don't want to engage with detail, with a mass of routine tasks, with the daily repetitious grind, and they'll be delighted if you offer to help them out with it. And cataloguers are naturally good at this sort of thing, after all - we've got the eye for detail, we can manage a whole heap of tasks, we can sort stuff out, we can spot patterns in things and fit things together - we've got that sort of mindset.

So it always surprises me that more people don't want to get involved in what seems to be the boring stuff, but is actually the stuff which teaches you an awful lot about the way your system, your organisation, fits together and works (or doesn't work). I've heard all sorts of excuses - I'm too busy, I haven't got time, I'm stressed enough already, why should I, it's not in my job description, why can't someone else do it. Some cataloguers even shun this sort of thing because they think that it feeds the stereotype and that cataloguers too should be dealing with ideas and strategies and policy.

Of course we should. Even if what I am advocating seems like the very opposite of high-visibility cataloguing, I don't want cataloguers to get stuck in the mud. But one of the ways to get influence and respect is to be able to sort out other people's problems, contribute ideas which help them achieve what they want to do, come up with ideas for developments which fit well with what's already being done and take it a bit further forward. These are the things which come out of knowing how things work and having a mastery of the detail, of the underside of stuff.

I think we should engage with our inner geek and take advantage of any opportunity to get involved with what's going on around us, even at the lowest level, and make that the first step on the ladder, because knowledge really does become power.

So, next time one of your colleagues is complaining about having to do something really really boring, offer to help out by doing it for him; he'll thank you for it, and you'll be doing yourself and your future a power of good.

Sorting the fact from the fiction

I've had a bit of a break and was bemused and amused in equal measure on my return by the correspondence that has been going on amongst the RDA-L list members about main entries for fictitious characters who purport to have written books. To put it briefly, if a book presents itself as having been written by a character who we all know doesn't really exist, we still have to make that fictitious character the main entry. So, "The Hums of Pooh" will appear under Pooh's name even though we all know that Pooh didn't really write them and AA Milne did.

I've bleated about this before and it still strikes me as moderately daft. We don't classify by title (we don't do we? Please tell me you don't put "Leaves of grass" in botany) but do our best to find out what the book is really about - and therefore why shouldn't we make an equivalent attempt to discover and reveal the true author? Yes, we should also make it plain that the book seems to have been written by a fictional character, either in the statement of responsibility or in a note, because that helps and informs the reader - just as we make a note if a book is not at all about what the title makes it seem.

What bothers me, though, is that we are adopting this new rule - copying what it says on the title-page without any questioning or any application of common-sense - at exactly the same time as we are all jumping up and down trying to explain the importance of what we do, how we mediate and manage and moderate information to add value for our users. I think I'm going to find that quite difficult when I appear to believe that "Me Cheeta" was written by an ape.

Crispy bacon

We often lament that cataloguing is a specialism, a niche activity, that not many people want and for which there is little or no market.

On my way to work, I often see a white van delivering to the various sandwich shops and delis along my route. On the side of the van is emblazoned, "Crispy bacon and cooked sausage specialists". Now I wouldn't have thought there was that big a market for crispy bacon, it wouldn't have occurred to me that a firm could have built a reputation and a business on it. But that white van has been making its deliveries for years now (in fact, they have extended the business, they used to be just, "crispy bacon specialists").

It cheers me up. A world that supports the crispy bacon trade surely has room in it for specialist cataloguers too!

Administrative? Who, me?

One of the reasons for the lack of posts lately is that like many, if not most, library authorities at the moment, mine is engaged in restructurings, rumours and threats of redundancies, ever-changing plans and plots, to the point that now we begin to long for any conclusion at all, even the worst, as long as it puts an end to the uncertainty. It is all very time-consuming and tiring and noone is going to come out of it well.

One of the latest plans for restructurings - it was only yesterday, but there has probably been another one since - showed Bib Services being merged under the overall title of "Administrative Services".

Now, "Support Services" I could have borne with a reasonable degree of equanimity - we provide support and a service. That's what we do.

But there's something about "Administrative Services" that really puts my back up. There is, I suppose, nothing wrong with being an administrator - but to be part of an administrative service? Doesn't that sound petty and mean and unimportant and, well, downright unprofessional? A way of demeaning and belittling bib services into something which involves form-filling and pen-pushing and counting paperclips? The sort of bad name you'd give a dog before neglecting and finally shooting him?

A rose by any other name would smell as sweet, just as long as it wasn't called an administrative service.

Tell me, am I being arrogant? Am I just tired and overwrought and a big glass of wine and half an hour with Monty Don will make me feel better?

You say, "Resource discovery technology"; I say, "Catalogue"

This is a response to the post on the High Visibility Cataloguing blog here:
http://highvisibilitycataloguing.wordpress.com/why-cataloguers/challenging-metadata-surrogacy-processes/ . I would have added a comment, but I just knew that I would have gone on too long!

You see, I agree 100% with Venessa's desire to raise the profile of cataloguers and I agree that it is something that desperately needs doing. I agree that we are seen as "antiquated gatekeepers" and I'd go further and say that it isn't only authoritarians who see us that way. When she says that we need to rethink who does what, or that we should challenge the legacy of our predecessors, I'm right there and cheering.

I differ with her in two respects, firstly, that in my opinion she doesn't go nearly far enough in redefining roles; and secondly, that I think that we shouldn't rely on changing words to make us sound good.

"The systems librarians is now an integral part of the cataloguing team". No. No. Cataloguers and systems librarians are becoming the same thing. I make no pretence of being a technician (start talking to me about servers and I'm thinking of Wimbledon), but a cataloguer deals with data, creates data, edits data, manages data, exploits data. Cataloguers are getting in touch with their inner systems librarian, and that's the way it has to be. Cataloguers aren't being asked to take on bulk editing, or digitization - that's what they should be, and are, wanting and needing to do, and deciding to get involved with on their own initiative. If cataloguers wait to be asked, then we'll soon be extinct. Cataloguers need to be "re-skilled"? Nonsense. We've got the skills, all we need is the courage to use them.

"Should we even still be using the term ‘cataloguing’ for what our role will be in the future?" Yes, there's nothing wrong with the word. Metadata is data about data - and it's what you'll find on a catalogue card. The added value that we bring is largely brought from rules and rulers, whether or not the cataloguer is sitting in a dark corner.

I don't have the word "cataloguer" in my job title, but I quite often introduce myself as, "the nearest thing you'll find round here to a chief cataloguer". I said exactly that in a meeting last week. And bless him, a senior manager spoke up and said, "Oh no, you're much more than that - you're one of the innovative people". That doesn't stop me being a cataloguer - I hope it makes me a good one, but a cataloguer is what I am and a cataloguer is what I'll remain. Not a metadata manager.

We'll redeem cataloguing when we explain what we do and why it matters, not when we change the name.

RDA and OPACs

Following on from my previous post, about the gap between the standards we apply when creating data and the ways in which we want to use it, I would like to give some thought to what lies in the middle - our OPACs.

We are all data creators - we all create data and edit data and hold it in databases - and we all follow some sort of rules (AACR, RDA, ONIX, DC or whatever) to structure that data.

Equally, we all have views on how we want to make the data usable, the ways in which we want to make it available, the things we want people to be able to do with it.

We don't necessarily agree about either the kind of data we want, or what we want to do with it. But the fact is that in the middle, for most of us, sits our OPAC - which dictates both the structure we use and what we can do with it.

I often curse our LMS supplier into heaps - why can't our OPAC do this, or that? Why does it take so long to persuade them that this (or that) really is important and something our users are waiting for?

Sometimes I feel sorry for our LMS suppliers - if we can't, as a cataloguing community, agree about our data and its purpose, how can they possibly develop the means to satisfy us?

But for most of the time we are all making our decisions - about what our data should be like and what it can do - on the basis of the product in front of us at that time. Should we ensure that our data is to the tippest of top standards because one day an OPAC will come which can actually use all that data to its fullest potential? Should we tailor our data to what our OPAC can actually do at the moment and tweak and twiddle and bodge the standards to get the result we want now, never mind what happens five years down the line? Or do we make our data according to what we think we and our users will want in the future, even if we don't, and can't, actually know what we or they will want then?

You see, I think that is what RDA is trying to do. I think RDA is looking into the future and predicting what we will all want and trying to make provisions for it. We (some of us, including me) criticise RDA because it neither sticks with the standards we've already got, nor offers anything our present OPACs can make use of in any kind of a helpful way. And prediction is a sticky business - look at the predictions made 20 years ago about how we'd all be living now and they are mostly wrong.

What do we want, really really want - something that used to work, something that works now or something that might work in the future?

RDA and standards

I have thought for a long time that there are two sorts of behaviour displayed in people who do cataloguing, with most people doing some mixture of both.

The first is the organising temperament - liking to sort things out, make things clear, set things out neatly, resolve muddle. This is the mindset that likes rules and clarity and consistency, that enjoys data creation and input.

The second is the mindset that puzzles out what to do with data, how to get it out, how searches and indexes work or ought to work, who want to use the data to produce answers.

As I said, most cataloguers are a mixture of both, and both are important. If the data isn't good, then you can't use it effectively. Rubbish in, rubbish out. On the other hand, there's no point in having data if you don't, or can't, use it. But although most cataloguers are a mixture of both types of mindset, and use both in their work, most cataloguers incline to one more than the other and are either data creators by instinct, or data users.

The whole RDA argument seems to be between those two ways of thinking. Opponents of RDA often worry about what will happen when the rules change, what the effect will be on catalogues which contain both RDA and non-RDA data, whether it will be possible, let alone desirable, to maintain consistency and order. That is the voice of the data creator.

Supporters of RDA believe that it will enable us to make more of our catalogue data, spread it more widely, combine it more easily with other types of data. That is the data user speaking.

Most of us are both data creators and data users and therefore end up divided on RDA. Is some of the heat in the debate generated by the fact that we are all arguing with ourselves?