This month’s GLAM Blog Club theme is the delightfully adaptable ‘question’. Next month’s #auslibchat theme is the equally interesting ‘Library Roles’. These have both wound up being quite timely, for reasons I probably shouldn’t discuss on the open internet, but I do have some questions about my role as a librarian with a technical bent.
I’m trying to get out of my perfectionist shell, so these are more free-flowing thoughts than I would normally commit to pixels. I should also mention I had a coconut margarita for dinner this evening, and I’m in a bit of a mood.
Back in the olden days, back-of-house library functions like cataloguing, acquisitions, et cetera were broadly known as ‘technical services’. When I started in libraries just over four years ago this term baffled me. I supposedly worked in this kind of area, but it felt like a hangover phrase from The Time Before Computers. Nothing ‘technical’ about serials check-in, I thought. Technical people worked in the systems department. Or in web publishing. Or in IT, which sat outside the library itself.
Four roles and three workplaces later, I still don’t work in any of those areas, but I also still don’t know how I feel about the phrase ‘technical services’. For context, I currently work as a web archivist, which is easily one of the best and coolest jobs I will ever have. I have the rare pleasure of a role that combines curatorial, technical and metadata aspects, in a team full of good people who know their stuff. I love (almost) every second. I haven’t been this happy at work since I spent 5 1/2 years running an ice-cream shop on weekends. I’ve been meaning to blog for ages about how awesome my current job is. I should get on that.
Notably, I am the only woman in a team of five people, and it’s taken some getting used to. Anecdotally, cataloguing and other ‘technical services’ are female-dominated, with a greater proportion of people from non-Anglo backgrounds (mostly due to the need for vernacular language skills). Yet library IT, like IT everywhere, is male-dominated. It’s not good enough for organisations like ALIA to blithely state that the LIS sector needs to hire more men. We need to look at the distribution of genders within the sector. IT pays good money. Cataloguing doesn’t. Librarianship has historically been a feminised profession, an ‘acceptable’ career path for women. It’s hard not to wonder whether tech services would be taken more seriously if more men were doing it.
But I also wonder whether I got into librarianship because it seemed like a safe and acceptable way for me, a white woman, to be technical. Being a systems thinker, I’ve always looked at how things work together, taking a broad view of the forest and its ecosystem while also occasionally delighting in a particular tree. Libraries are just one big system, right? But that system has to be meaningful to people, too, and it’s what I find most interesting about being a cataloguer.
As a technically-minded librarian I often feel like I inhabit a kind of liminal space. I don’t feel technical enough for IT—largely because I’m not much of a coder—yet I feel almost too technical for a lot of library work. Most library jobs these days are not conceived as being ‘technical’ roles. Library schools push a front-of-house mindset almost from day one. My study visit cohort were firmly told what attributes we needed in order to succeed in libraries, and I didn’t feel like I had any of them. I was a natural introvert, not very good at people, quite fond of books and reading thanks, drawn to computers and systems. I vividly remember walking the streets of suburban Perth on the brink of tears because I felt like I didn’t fit the mould the lecturer had set for us. I spent the rest of the visit wondering whether I had made the biggest mistake of my life by enrolling in library school. I seriously considered giving it all away.
I know now, of course, that the lecturer was rude, crude and totally wrong. I do have what it takes to be a librarian. Just not the kind of librarian she was thinking of. But the idea persists that librarians are not technical people, or that the heart of librarianship is not—or should not—be a technical one. We’ve been technical for decades. We were one of the first professions to embrace the possibilities of automation. (We’re still dealing with some of those possibilities now. Ask any cataloguer about whether MARC has died yet.) What happened to that? Where did that power go? Where has that technical skill and ability ended up? And why has the section known as ‘technical services’ not been at the centre of this change?
Too library for the tech staff, too techy for the library. It’s hard not to feel as if I will one day be made to choose between them.
And I will refuse to choose.
Our profession needs all the techy librarians it can get. People who speak library AND speak IT. People with the ethical grounding of librarianship, who may or may not work back-of-house, but who can also critically assess and use technology, ensuring it functions in accordance with the values of this profession. No siloing. No separating. No boundaries. And I say all this not just because I’m on the committee of VALA, a library technology organisation that was literally founded to bring librarians and technologists together, nor because I’m trying to shore up my own career prospects in an uncertain world. I say this because I want library automation to happen BY us, not TO us. I want librarians to be able to take control of their own technological destinies. I want equitable cataloguing to be supported by equitable systems. I want us to be able to speak tech, so we can either tell tech what to do, or feel suitably empowered to do it ourselves.
It’s not technical services as we’ve traditionally known it. But a lot of library traditions are changing.
A librarian’s innate desire to help is often redirected into a desire to provide great customer service. That is, until what constitutes ‘customer service’ changes, and suddenly what some kinds of librarians do isn’t considered ‘helpful’ enough. I’m sure I had something else in mind when I suggested the theme ‘help’ for GLAM Blog Club. But one of Danielle’s tweets today set a different set of cogs in motion:
Every public library collection job I've seen, they never talk about discovery, only ever about buying. Surely the two are linked or if not should be.
Yes. You can’t manage a lending collection properly if you don’t look at how it is used. You can’t analyse how it’s used without understanding how it’s discovered. You can’t analyse how it’s discovered without understanding how it’s catalogued.
And you can't do any of these things without in-house technical and collections expertise, which so many public libraries seem to think they can outsource or eliminate (because it's not considered 'customer service') https://t.co/38J2eSPNWW
A public library director once told me to my face that he wasn’t interested in hiring cataloguers. I don’t recall exactly how he phrased his justification (though I do recall my response being ‘I’m sorry to hear that’) but he clearly conceptualised his library as a ‘customer service’ organisation, where that phrase meant ‘an exclusive focus on front-of-house activities and services’. Collection development, systems administration and cataloguing, collectively ‘technical services’ in library parlance, are not commonly viewed as opportunities for great customer service. Instead they’re seen as something that can (and should) be outsourced in the interests of ‘efficiency’.
Brisbane City Council Library Service abolished their in-house tech services department twenty years ago and, oddly, chose to present about it at the 13th National Cataloguing Conference. The library moved entirely to shelf-ready stock and turfed all their cataloguers.1 The writeup in Cataloguing Australia notes (emphasis mine):
This driver of customer service is paramount at Brisbane City Council and Library Services. All our restructuring and re-engineering has been predicated on the assumption that it will provide better customer service and responsiveness. The wider implication of no longer having a Technical Services Section is that Library Services is now solely a customer service branch. There is no longer a back room mentality, and the expectation is that staff spend 80% of their working day in direct customer service.2
To be fair, a typical late-nineties tech services department probably wasn’t all that user-focused. But I reckon it could have been, if management had chosen to imbue that customer service ethos into all areas of library administration, not just the face-to-face parts. I can see I’ll be shouting ‘CATALOGUING IS POWER’ until the day I die. I’ll never understand why so many libraries, especially public libraries, willingly throw this power away. What do we lose from ‘efficiency’? What do we lose, when we lose the people who are paid to care?
I have worked for, patronised, and otherwise dealt with far too many libraries that are not resourced to care about the integrity and usefulness of their metadata, collections or systems. These things are clearly not prioritised by decision-makers, and so they are outsourced, often with little oversight. This is not good customer service. This does not help. Having a crappy website or an unusuable catalogue sends a strong message that the only patrons the library cares about are those accessing the library in person. Has the internet taught us nothing? Have twenty-plus years of ‘everything is online now’ not compelled us to create the best online presences possible for our libraries? To curate the best online and electronic collections? To boost our SEO (search engine optimisation) using well-structured, highly detailed metadata? To develop and deploy systems that don’t make people jump through endless hoops, divulge their personal data, or give up entirely in frustration and turn to a paid competitor? Why do I know so many librarians who use Audible instead of Overdrive? Who are we really competing against?
I abhor the practice of referring to library users as ‘customers’. Customers, by definition, purchase. The library has nothing to sell. The library invites the community it serves to make use of its facilities, collections and knowledge. These services are not without cost, but they are, proudly, free to the user. In lieu of ‘customer’, I prefer the term ‘library user’ or sometimes ‘patron’. The library I work for uses ‘reader’, supposing the majority of our visitors are, in fact, here to read.
Save for the two hours a week I choose to spend on a reference desk, my job is not directly user-facing. But it is user-focused. Everything I do as a librarian, I do for my library’s users (and, through the power of co-operative cataloguing, the users of hundreds of other libraries). I don’t catalogue for the catalogue’s sake. I catalogue so people can find things. Most people will never know how my cataloguing has helped them. I’m okay with that. I don’t need to be sitting in front of a library user for my work, and my help, to be valuable.
The above-mentioned issue of Cataloguing Australia, the journal’s last, also featured a paper from the then-Customer Services Manager at CAVAL. To my surprise and absolute delight, she took a similar view to me of customer service and cataloguing:
Let me begin, as we should all begin, by looking at our customers. Even if we never see them, we should never forget who they are. […] When you are making a map of the heavens, you need to be aware of whether you are doing this for a child, an astrologer, a serious astronomer or a Star Trek fan. Each one of those maps is useless to any of the other groups. So, too, with our catalogue records. For our customers are infinitely more varied than those for star maps.3
The entire article is a joy.4 It’s full of sensible, user-focused thinking (seemingly a rarity in 1999) and it’s easily my new favourite piece of professional literature. But I’m intrigued by the fact it came from a vendor. By outsourcing so much of our technical services work, has our sector also outsourced the capacity to think of this work as inherently ‘customer’-focused? A vendor’s ‘customers’ are libraries themselves—does this change a catalogue record’s intended audience?
A tech services worker might ask ‘How can I help?’, as I so often greet people on the desk, but libraries need to be structurally capable of accepting that help, and cultivating it in-house. By reframing our conception of cataloguing as an inherently user-focused (or customer-focused) activity, libraries can ensure we’re providing the right metadata to create the right map, in order to help the right people find the right materials. After all, we’re here to help.
The author mentions ‘we now have no cataloguers on our staff’ so I guess they were either made redundant or reassigned to other, non-cataloguing duties, though two staff were put in charge of quality checking vendor records. ↩
Mackenzie, Christine. (1999). ‘The end of the world as we know it? Outsourcing at Brisbane City Council Library Service’. Cataloguing Australia 25(1/4), pp. 184-187. ↩
Dearman, Rosemary. (1999). ‘Whose information universe? Customer services and cataloguing’. Cataloguing Australia 25(1/4), pp. 222-231. ↩
This is the working transcript of ‘We need to talk about cataloguing’, a talk I gave at the 9th New Librarians’ Symposium in Adelaide, South Australia on Saturday 6th July 2019. I made some last-minute edits to the text and said a few things in the wrong order, but overall I pretty much stuck to script (which was very long, hence my conscious decision to talk too fast!).
Thank you. I begin by acknowledging the traditional and continuing owners of the land on which we meet, the Kaurna people, and pay my respects to Elders past, present and emerging. This land always has been, and always will be, Aboriginal land.
Library workers, students and allies, we need to talk. You’ve probably heard of this strange thing called ‘cataloguing’. You may even have met some of these strange people called ‘cataloguers’. But for many people in the library sector, that’s about all we can say. Many of us don’t have the vocabulary to be able to talk about areas of library practice that aren’t our own.
It’s not quite the talk I promised to give, but it’s a talk I think we need to have. About what this work entails, why it matters, and why you should care. Consider how, and to whom, we should start talking. Our colleagues, our supervisors, our vendors, ourselves.
My name is Alissa McCulloch. We need to talk about cataloguing.
Firstly, a bit about me. I work at a small, minor national library that shall remain nameless, because I’m not speaking on behalf of my employer today (I just need to make that very clear, these are all my opinions, not theirs). I’ve been in libraries for around four years and have had a library degree for around six months. My work life consists mostly of cataloguing whatever turns up in the post.
You may have seen or heard me talk about cataloguing ad nauseam on podcasts, on my blog, or on twitter, because I LOVE CATALOGUING and it sparks SO MUCH joy and I think it’s amazing. Suffice to say my reputation precedes me. So perhaps some of what I’m about to say will not be a surprise to you. But I am surprised, quite often, by the reactions I get when I tell people what I do all day.
They go ‘Oh… is that still a thing?’ And I’m like ‘Yes, actually, it is still a thing’. People act like metadata grows on trees, that carefully classified shelves of books are ‘serendipitously’ arranged, that cataloguing is obsolete, that structured metadata is unnecessary in an age of keyword searches, that we’ve all been automated out of existence, that AI is coming for the few jobs we have left.
It’s more than just ‘data about data’. It gives meaning and structure to a collection of items, whether that’s a simple website, Netflix, a corpus of research data or a library catalogue. Metadata forms a map, a guide, a way of making sense of the (in many cases) enormous collection of resources at a user’s disposal. A chaotic library is an unusable library.
‘Cataloguing’ doesn’t just mean painstaking creation of item-level metadata (although it can involve that, and it’s what I spend a lot of my time doing). It involves a lot of problem-solving, detective work, ethical decisions, standards interpretation, and data maintenance. If you like puzzles, you’ll love cataloguing. Modern metadata is all about connections. It’s relational, it’s often processed at great scale, it’s about making collections accessible wherever the user is.
You might hear these jobs described as ‘metadata librarians’ or similar. If given the choice, I would describe myself as a ‘cataloguer’. In fact, at my current job no one ever actually told me what my job title was, and I needed an email signature, so I picked ‘cataloguer’ and nobody seemed to mind.
But I specifically didn’t call this talk ‘We need to talk about metadata’. Don’t get me wrong, I could talk about metadata all day, but I deliberately said ‘We need to talk about cataloguing’. The word’s kinda gone out of style. It’s old-fashioned, it’s a bit arcane, it’s not hip and modern and contemporary like ‘metadata’ is. But I’m the sort of person who likes to reclaim words, and I can reclaim this one, so I do.
Words mean things. But sometimes, if we want to, we can change those things.
Once I’ve explained what I do for a living, people then go ‘That’s great. Why should I care?’. And it’s a good question. Why should you care? You’re all busy. You all have other jobs. You don’t have time to care about metadata.
For some reason, a library vendor in California took this tweet and made a shareable graphic meme thing out of it. I stand by what I said, but what really got me was that they left out the best part of the quote. The line immediately after this was:
‘Cataloguing is power, and I will die on this hill!’
We as cataloguers have, as Hope Olson famously put it, ‘the power to name’. We decide what goes where, what’s shelved together, what’s shelved separately. We describe these things in the catalogue so that people can find them. The language used in and about cataloguing is tremendously important. If something is poorly-described, it might as well be invisible, both on a shelf and in a search engine.
Cataloguing is power. That power must be wielded responsibly.
As humans, we are all shaped by language. Our everyday language changes through time, as social and cultural practices change, but library language changes far more slowly, when it changes at all. (We’ve been putting punctuation in weird places for a long time, too. Look, I’m sorry, but I will never care about where to put a full stop in a MARC record.)
Metadata is not fixed. Metadata is never ‘finished’. Metadata is contextual. Contested. Iterative. Always changing. ‘Corrections’ are not, and can never be, universal. An accepted term today might be a rejected term in thirty years’ time, and the process will begin again. The Library of Congress Subject Heading (LCSH) for ‘People with disabilities’ is now on its fourth iteration, as the preferred language has changed over time. Previous versions of this heading used terms that would now be considered quite offensive.
We all need to look out for these things. Have new concepts arisen for which your library has no standardised heading? Has a word shifted meaning, such that it has ceased to be meaningful? Are users looking for resources by name, but finding nothing in our collections? Think of the power we have. Think of how we ought to wield that power.
What do I mean by that? Consider the widespread use in the English-speaking library world of Library of Congress Subject Headings, a standardised vocabulary originally designed by American librarians to meet the information needs of the United States Congress. Because the Library of Congress is the source of a lot of American copy cataloguing, their subject headings were widely adopted in the US, and later by other Anglophone countries. Most (though not all) Australian libraries use LCSH in some capacity. Has anyone stopped to think about how weird that is? We’re not the US Congress. We use different words and different spellings, we serve vastly different communities, we have our own information needs and information contexts that LCSH necessarily cannot meet.
Yanni Alexander Loukissas recently wrote a book titled ‘All Data Are Local’, which is sitting on my bedside table at home. I would extend that to ‘All Metadata Are Local’. And they should be. Each library serves a distinct community of users. Our metadata needs to speak their language.
Attitudes toward cataloguing itself are shaped by the language we as cataloguers use to describe our work. For example: a big part of cataloguing is about standardising names and subjects, and to a lesser degree titles, so that resources with or about those things can all be found in the one place! We call this authority control, which has gotta be one of the worst phrases in librarianship for two reasons:
A) whose ~authority~ is this done under? Who died and put us in charge? What gives us the right to decide what someone’s name is, or the best phrase to describe a certain topic? Why do we even have to choose just one? Why can’t we have several, equally valid terms?
B) Why do we have to ‘control’ everything? What need is there for this giant bibliographic power trip? Why can’t we let people decide these things for themselves, instead of us being authority control freaks?
This phrase says a lot about how we’ve historically thought about cataloguing: that we have authority, and that we are in control. Cataloguers haven’t been either of these things for a while. Which is great, because our survival depends on it.
The outlook I’ve just described, and the outlook I bring to my work, is known as radical cataloguing. It’s a way of looking at cataloguing and metadata from a structural, systemic standpoint. Getting to the root of what—and who—our data is for, and making sure it meets our users’ needs.
It’s broadly similar to the contemporary movement called critical librarianship, of which critical cataloguing is a part, which aims, according to the critlib.org site ‘to [bring] social justice principles into our work in libraries’.
Critical and radical cataloguing can involve establishing local policies for catalogue records, working to improve common standards and practices, sometimes ignoring those standards and practices, and encouraging critical viewpoints of—and within—the catalogue.
It sounds quite cool, calling myself a radical cataloguer. But this work and this ethos have never felt all that radical to me. It feels normal, to me. It feels like common sense. It feels like bringing my values to work. Sometimes these align with traditional library values. Sometimes they don’t. But it’s all in the service of making the library better. Think of it as ‘evidence-based whinging’. It’s done in good faith, and it’s done for a purpose.
Sadly, common sense isn’t as common as I’d like it to be. A recent article on tech news website The Verge described the terrible quality of metadata in the music industry, which meant people weren’t getting paid royalties for music they had written, performed, or contributed to. Bad metadata literally costs money. The author described metadata as ‘Important, complex and broken’. And I was like ‘yeah… I feel that’. A lot of what they said about commercial music metadata could just as easily be applied to the library world—infighting, governance issues, funding challenges, cultural differences and copyright laws.
This work is difficult, painstaking, often invisible and mostly thankless. But the results of not doing the work can be slow to manifest—you might be able to get by on deteriorating metadata quality for a while, but soon enough it’s gonna be a huge problem that will cost lots of money to fix, which you could have avoided with enough care, attention and maintenance.
It’s not about simply following rules and standards because that’s just how we do things, or have always done things. It’s about imbuing our information practice with an ethic of care. Thinking not just about what we do, but how and why we do it. Who benefits, who loses out, and what happens when and if the work stops being done. The ‘we’ in this instance is an information maintainer: a cataloguer, an eresources manager, a systems librarian. People. Not robots.
People often try to replace me with a robot. They ask, sometimes innocuously and sometimes not, ‘But what about AI and machine learning?’
And I go, ‘It’s a great tool. But like any tool, it has to be used responsibly.’ Algorithms are as biased as the people who write them. We all have biases, we all look at the world a particular way. The key is ensuring that library automation of any kind is properly supervised and evaluated by real people. Metadata professionals with an ethical grounding. Cataloguers, of the past, present and future.
Dewey is a product of its time. But it’s also a product of our time. Dewey is now in its 23rd edition, maintained by paid staff and volunteers from around the world. AI can’t do this. It can’t write its own rules. And it can’t be left unsupervised, because it won’t produce quality metadata.
What do I mean when I say ‘quality metadata’?
I don’t think about ‘quality’ the way most other people think about ‘quality’. People think ‘quality’ means total adherence to local, national and international policies and standards. A record can do all of those things and still be functionally useless. I don’t consider that ‘quality’.
To me, a ‘quality’ record is informative, accessible, respectful, accurate and empowering. You won’t find these ideals in RDA, or in the MARC standards, or in BIBFRAME. You’ll find them in your community. Those of you who work in libraries should have an idea of the kinds of materials your patrons are looking for, and how your library might provide them. Is your metadata a help or a hindrance? Are you describing materials the way your patrons might describe them? Are people asking you for help because your catalogue has failed them?
I know most of you are not cataloguers. Many of you undoubtedly work for libraries that outsource most or all of their cataloguing. Records appear in your system by what looks like magic but is probably a Z39.50 connection. You may well have no way of knowing what constitutes ‘good’ and ‘bad’ metadata. Here are some brief tips for you!
Compare a record with the resource it describes. Are the title, author and year correct? Does your system disambiguate different authors with the same name? I know I said I hate the phrase ‘authority control’, but you still gotta do it, the work still needs to be done. How would a user describe this item? Are those words or phrases in the record? What kinds of people use your library? Will these words meet their needs? Are they current? Offensive? Relevant?
Next, compare that record with how your OPAC displays it. Backend versus frontend. Have a look at a MARC record, even if it looks like a bunch of numbers and dollar signs. Is anything obviously missing? Are there MARC fields that your OPAC displays oddly, or not at all? Have a play around with the OPAC. Are some fields searchable but not others? Does your system support faceted browsing, like Trove does? If so, what facets are available?
I once worked for a library whose ILS didn’t display the 545 field, used for biographical and historical data in manuscript records. I’d been using this field for months. Why didn’t I know that my ILS did this stupid thing? How might I have worked around it?
If any problems appear with your library’s data, think about how you might advocate for getting them fixed…
We are constantly having to advocate for our jobs. I’m doing it right now. Right here, with this talk. And not just because my contract is up in two months and I need all the help I can get. But because without people like me shouting from the rooftops, our work is practically invisible. We are the people behind the curtain. We have to keep telling managers why quality metadata matters. But I am only one person, and I can only shout so loud. Cataloguers need your help, gathered library workers, students and allies, to talk about cataloguing.
So what should we say?
The key is to mind your language.
Firstly, what can you think about?
How does bad metadata make your job harder? What kinds of questions do you get asked that better metadata would be able to answer? Such as: ‘A friend recommended a book to me, I can’t remember what it was called, but it was blue, and it had birds on the cover. I think it was set in Queensland?’ We don’t routinely add metadata for a book’s colour in a catalogue record, it’s not searchable, but people ask questions like this all the time. Perhaps AI could help us with this metadata…!
Secondly, what can you talk about?
Appeal to your managers’ financial sensibilities. ‘Hey, we spent a lot of money on these materials. If people can’t find them, that’s money down the drain. Good metadata makes those materials findable: it’s a return on investment.’ Talk about how much time and effort is wasted dealing with bad vendor metadata, and how that staff time could be better spent on other metadata tasks. I’m sure you’ve got plenty.
Alternatively, appeal to their morals and sense of social justice. If they have one. You could say, ‘We have a lot of refugees and asylum seekers in our community, and books about people in this situation often use the phrase “Illegal aliens”. This sounds kinda dehumanising to me, do we have to use this term?’ And if they say ‘But it’s in LCSH, and that’s what we follow’ you can say ‘well… so? Just because LC does it, doesn’t mean we have to’. You can change that subject heading locally to whatever you want, or get your vendor to do it. It’s already happening in American libraries. It could just as easily happen here.
Being a radical cataloguer doesn’t mean rewriting a whole record from scratch—if good copy exists, it makes sense to use it. But do so with a critical eye. How will this metadata help my users? How will it help my colleagues do their jobs in reference, circulation, instruction or document supply? Is it fit for purpose?
And lastly, what can you do?
Make suggestions internally and externally about what problems could be solved with better metadata. What kinds of patrons ask what kinds of questions or search for what kinds of materials. What your catalogue doesn’t include. What it could start including.
If everything I’ve talked about sounds fascinating and you want more, consider joining ACORD, the new ALIA Community on Resource Description. It’s so new it doesn’t quite exist yet, but it’s slated to launch later this month, and there’s an article about it in the July issue of InCite. I’m hoping ACORD will be a great forum for cataloguers and metadata people to meet, exchange ideas, and work towards better cataloguing for all.
It can be hard to make these kinds of suggestions in your workplace, much less change international rules and standards. But you can do it. You can be part of this change. And the first step is talking about it. If you have an opinion on anything I’ve spoken about today, get talking, get writing, get tweeting, get involved with ACORD, which liaises with the committees overseeing all these rules and policies.
These rules were made by people. They can be changed by people.
And if the rules aren’t working for you, break them.
Change has to start somewhere. So it can start with you.
Last week at work I had one of the most incredibly serendipitous experiences of my library career. It was a beautiful illustration of why I became a librarian. To not only collect and preserve people’s stories, but to sometimes be part of them, and weave a broader tale.
It began in early January, when 110 books turned up from the same publisher. Being in the legal deposit business, my job is to catalogue whatever turns up in the post. Any genre, subject, author, publisher, size, format, you name it, I deal with it. (Unless it’s a serial.) We often get large boxes of books from publishers, but this particular enormous haul intrigued me. I volunteered to catalogue the lot. What can I say, I’m a sucker for punishment. And I wanted something fun to do before I went on holidays.
I slowly realised I held an entire library in my processing trolley. A living, breathing library.
It all started a few years ago in Iceland, where apparently one in ten people publish a book in their lifetime. Margaret Woodward and Justy Phillips, co-founders of Tasmanian arts collective A Published Event, found themselves in Iceland in 2012 doing arty things. They wondered whether there was a similar latent writing community in Tasmania, which is around the same size. Most of us would probably have pondered this for a short while and left it at that. But not these two. They decided to create a kind of performance library, soliciting unpublished manuscripts from would-be Tasmanian authors and publishing a whole lot of them in one go. Giving a voice to people who might otherwise never have published a book. Creating a kind of ‘time capsule’ showcasing Tasmanian life and writing during the late twenty-teens. It’s huge. It’s faintly ridiculous. And it’s completely awesome.
The People’s Library comprises 113 books. Their authors range in age from 15 to 94. All live in Tasmania, from all kinds of backgrounds, writing all sorts of things. Novels by first-time authors. Anthologies by U3A writers’ groups. Memoirs. Poetry. Non-fiction. Experimental literature. An opera about Sir Douglas Mawson, no less. Each assigned a cover colour from Werner’s nomenclature of colours, creating a beautiful rainbow effect when the books are lined up in order on a shelf.
The People’s Library was installed at Salamanca Arts Centre, Hobart, in September 2018. Authors read, performed and gave life to their stories. There were panels, responsive art pieces, readers-in-residence (and also readers-in-bed). The books took centre stage. None were for sale—this was a library, after all.
Then it came to us. To me. Cataloguing these wonders took me a full, magnificent week. They were a joy to process. I learned so much about Tasmania, about total strangers, about the limits of the written word, and even about myself. I realised we were missing three of the books, so an email was sent politely requesting copies. I returned after a month’s holiday (in Tasmania, as it happened) to an email from the publishers, promising to send the missing books and wanting to know more about how the Library was catalogued. Omg. A genuine interest in cataloging. Nobody ever asks me how I’ve catalogued their books unless they’re complaining about it, so I was very excited. I promptly wrote back with probably too much detail, which amusingly made its way back to some of the authors. Many of them were thrilled that we had collected and preserved their books.
And then I thought no more of it until last Wednesday, when I sat at the reference desk for my weekly shift. Not all cataloguers do shifts in the reading rooms, but some of us do. It was one of the first things I asked to do when I started this job, because I want to keep in touch with how people actually use and experience the library, and how the metadata I create might be a help or a hindrance.
I noticed a few volumes of The People’s Library on the collection shelves, ready for a reader to peruse. Occasionally people actually read the books I catalogue, which is always nice. I hastily arranged the volumes in colour order. The reader arrived and I retrieved the books. As I carried over the last handful I remarked, ‘I catalogued these books, they’re awesome.’ The reader looked at me oddly. ‘Are you… oh, you’re the one who sent us that lovely email!’
One half of A Published Event. In town for other reasons, but who had popped in to admire her handiwork. I had no idea she was coming, let alone during the two hours a week I spend on the desk. To have come all that way, to read some of the books she had given life to, and to have been greeted by the very same person who had lovingly catalogued them, and who only briefly sits at the reference desk… Absolute serendipity. You couldn’t have written it.
The fact it had taken me a week to catalogue the Library was cause for amusement. As part of the Library’s performance at Salamanca Arts Centre, four readers-in-residence had each read some of the books, also for a week, and produced a digest summarising what they had read and learned. In a way, she supposed I became the fifth reader-in-residence, and the catalogue records for these books constituted a fifth digest. An incredible way that librarians not only collect and preserve stories, but can sometimes be part of them. By cataloguing The People’s Library I became a part of its performance, weaving a broader tale, ensuring the voices of over a hundred Tasmanians can be read and heard by all who visit us. I felt honoured to be a part of this work.
I already can’t wait to peruse A Published Event’s next library, Lost Rocks, a collection of 40 ‘fictionellas’ borne from an almost-empty rock board picked up at the tip shop in Glenorchy. ‘A slow-publishing event of mineralogical, metaphysical and metallurgical telling.’ It doesn’t get better than this.
See, this is what I should have sung at karaoke the other day. Or something by Erasure, since it turns out Andy Bell and I have the same vocal range (who doesn’t want a little respect?). But that’s for another blog club, while this month we take some time out from changing the world to write about it.
For the longest time, the words ‘change’ and ‘cataloguing’ haven’t sat well together. Cataloguers are stereotyped as change-averse pedants who prioritise rule-following over user-helping. You’ve all heard the joke about how many cataloguers it takes to change a lightbulb, I’m sure (WHAT?! CHANGE??!?!?!). Lord knows I’ve met enough people who embody this stereotype, much as I’d like to disclaim it. And yet, to me, change is the only constant. I’ve never known a professional existence where change has been optional, and so I accept it, and go with the flow.
I glance over to my copy of Radical cataloging: essays at the front, a 2007 compendium of critical and radical analysis of cataloguing in North America. A lot has changed in the eleven years since the book was published, the biggest change being the replacement of AACR2 with RDA. With that change came a complete overhaul in how catalogue data was meant to be theorised and perceived by cataloguers—no longer card-based, but element-based, with the promise of linking those elements together in new and exciting ways. For better or worse I learned to catalogue after the introduction of RDA, but I hear there was much wailing and teeth-gnashing as the changes were introduced. People seem over it now, though.
Many of the chapters in Radical cataloging don’t seem all that radical to me, now. Yes, LCSH is unfit for the myriad of purposes we’re now putting it to. Yes, controlled subject access is practically dead (but that’s because our systems don’t harness our data well enough, not because the data itself is suddenly worthless). Yes, we should bend and/or break cataloguing rules where there are clear benefits for users. Yes, cataloguing remains a necessary and sought-after skill. Change and deviation from established standards doesn’t seem as radical to me as perhaps it did to others a decade ago. I find myself disagreeing with, though nonetheless respecting, some of the deeply-held views about the value of a rigorously-constructed catalogue. But I was raised on Google, so what would I know?
People have written entire books about how cataloguers cope with change (and I’m kicking myself for not having read that one before writing this post). Tina Gross’ chapter ‘Who moved my pinakes?’ in Radical cataloging blasts the old stereotype out of the water—that cataloguers do not oppose change for change’s sake, but rather because proposed changes are not considered to be in users’ best interests. Joan E. Schuitema’s chapter ‘The current cataloging landscape: a therapist’s perspective’ from The psychology of librarianship examines cataloguers’ experiences of trauma as a direct result of having the professional rug pulled out from under them.
And yet I suspect it’s no accident that the LCSH ‘Change’ lists ‘Catastrophical, The’ as a related term. Not all change is catastrophical, but all catastrophes are change.
If it were up to me, I know what I’d change. I would work with systems librarians and developers to better integrate our existing name and subject taxonomies into keyword-search interfaces. I would ensure our data formats recorded each element of bibliographic information once per item, and once only. I would break the Anglophone world’s inexplicable dependence on LCSH and help each sector build new and better vocabularies. I would decentralise cataloguing, by which I mean I would work to ensure a library’s users had a direct say in how its collections were described. But most importantly, I would finish off the cataloguer stereotype once and for all.
That used to be us. I think you’ll find we’ve changed.
ALIA Sydney recently hosted their first Saturday School of Critical Librarianship, a gathering for critically- and radically-minded librarians to talk shop and take stock. It was a seriously full-on day. I spent most of today sleeping it off, and there’s a worryingly large memory gap where a lot of yesterday should have been. But I did remember to jot down a few not-terribly-insightful thoughts.
We are worthy. I awoke in a spaceship at sunrise, to a blistering Twitter discussion on the merits of metadata. (Sounds blissful, really.) I was staying in a capsule hotel, because it turns out Sydney has one and I wanted to try it out, but it was very poorly ventilated and I didn’t get a great sleep. The hot topic of discussion at 6am turned out to be the Digital Public Library of America (DPLA), broadly the American equivalent of Trove or Europeana, laying off several staff, apparently including their metadata librarian. Cue spirited conversation about the value institutions place, or don’t place, on their metadata workers. Perversely it was a bit of a personal mood boost:
Honestly existential cataloguing angst at 6am on a Saturday having slept in a spaceship is the mood boost I needed to explain to a bunch of people today why this shit matters. Genuinely. Metadata is just as important as other facets of LIS, and today I’m gonna demonstrate why.
We are facilitators. The word ‘facilitator’ kept cropping up, and it wasn’t just because a few of us had been asked to ‘facilitate’, or lend our expertise to, various breakout sessions. Instead the word arose organically as a way to describe how we might envision a future, more critical (or radical) librarianship. Historically our profession has been structured around either having the answers or knowing where to find them (that is, in our collections), but might we instead take our lead from our patrons and communities? Whether it’s building collections, planning programs or cataloguing our library’s contents, there’s a lot to be said for not just listening to, or consulting with, our patrons—but actively listening to how their collections and programs and knowledge and memory ought to be managed, which we could then use our LIS skills to make happen.
We are, um, not all cataloguers. I stayed for all three iterations of the rotating breakout discussions on cataloguing, as I had been asked to help guide this discussion (I tried to move to another topic but found myself blurting out ‘my people need me’). I’m sorry to say that I don’t think I did a very good job. I wish I’d been better prepared and had more structured discussion topics. As it was, the conversation drifted from cataloguing into collection development, preservation of time-based media art, and systems librarianship. This suggested to me that people didn’t really know what to say, or felt they had nothing to say, or waited for me to do all the talking (and I still feel like I talked too much). But perhaps that in turn suggests that critical tech services in general is under-theorised and under-discussed, especially in Australia, and especially by non-tech services staff.
I was reluctant to steer the conversation back to cataloguing, figuring that people were talking about what was interesting and meaningful to them. If you were hoping I would do more active facilitating then I am sorry. But I hope people enjoyed the discussions nonetheless.
We are critical radical librarians! So this happened:
I think my group(s) have decided that instead of ‘critical librarianship’, a very American term, they’d prefer ‘radical librarianship’. Less negative-sounding, more empowering, inspires action #SydCritLib
I know there was more to this conversation that my poor memory chose not to retain, but I found it interesting that we chose to critique the very name of our fledgling local movement. I think a few attendees took ‘critical’ to mean ‘criticising everything, unproductively’, rather than the more nuanced meaning assigned it by critical theory. The hashtag-critlib movement began in the United States, I understand principally from infolit and instruction librarians in university libraries, and it is running the risk of becoming a bit cliquey. I also had Nora Almeida’s chapter ‘Interrogating the collective: #critlib and the problem of community’ from the LJP critlib book in the back of my head during this discussion. Personally, I think ‘radical librarianship’ sounds friendlier and has a more activist tone. But I also really liked Andrew’s take on it from afar:
It’s a good point – though I like the association of “critical” with being inward-looking and identifying the things that need to change internally. I feel that, too often “radical” is associated with changing the external world to meet a fixed agenda.
We can’t do it all. I really liked a point Kirsty Thorpe made about gaining power through focus—as library workers, choosing an area to focus on and directing energies towards making that area better, focusing on a couple of select things we can do, rather than spreading ourselves too thinly on things we can’t.
This was part of a broader discussion near the end of the day about power, and it prompted me to reflect on how much power I have within LIS. At my workplace, an institution fond of bureaucracy, I often feel powerless because all the decisions are made above me and I can’t change established practices or standards. Yet people from elsewhere look at me and go ‘You work where!? You have so much power! You can get things done!’ Plus I have managed to accomplish a couple of things in cataloguing entirely independently of wherever I have worked. And I wondered if this meant I had power because… people think I do? As in, they recognise power in me and they act accordingly? (Is this Schrödinger’s power?!) So what can I do with this power that I may or may not have, to push for change within LIS, and within my institution?
Also, we give a crap. We all showed up on a Saturday, some of us (including me) having come from out of town, because we care about our profession and we want to do better and do differently. There was a lot of talk about further critlib schools in Sydney, as well as opportunities to coalesce around shared or common goals. I really hope these come to fruition, because there’s really nothing like an in-person gathering to network with like-minded people and galvanise us into action. But next time I’m in Sydney, I think I’ll stay somewhere with functioning windows. And maybe a door.
On Monday 13th August I attended the ‘Resource description in the 21st century’ seminar at the NLA, organised by the Australian Committee on Cataloguing (ACOC). It came at an interesting time for me, looking to regain some of my lost passion for this work, but I was very pleasantly surprised by how energised I felt at the end of the day. As always, the below observations and symptoms of foot-in-mouth syndrome are entirely my own. (MPOW were very keen that I emphasise this. :P)
Tweeting is good. This was the first seminar / conference / extended PD activity I went to where I primarily tweeted my notes, rather than scribbling them down. (The scribbles I did make were exactly that—largely unintelligible!) I found tweeting-as-notetaking to be an excellent way to record and synthesise my experiences of the day—not only was I recording and distilling what the speakers were saying, but I was also interpreting and annotating them for the benefit of those not attending. I was also doing so in 280 characters a pop, so my observations were necessarily brief. I’m sure someone once told me the best way to learn something is to teach it, and it definitely felt like I was doing that, to a degree—not so much teaching as relaying information in bite-size chunks. The #ACOC18 hashtag is mostly me, with contributions from Edith, Monika, Melissa and Cherie.
I did get, by the end of the day, some fairly severe shoulder and thumb cramps. Maybe it’s a hitherto unknown condition, ‘tweeter’s shoulder’.
Free Snoopy! So this happened:
I asked Gordon about Snoopy. He is concerned that including fictitious entities as people will muck up the data + misrepresent the true authorship of a book. I disagree with the answer but I respect his time and expertise in responding to me. #ACOC18
(My hands are shaking so badly atm. I think Gordon is tired of having this conversation. But I remain firm that we mislead users and do them a disservice by not including fictitious entities as authors. Some of our users are children. They just want books by Snoopy.) #ACOC18
I had a bit of an argument with Gordon Dunsire, the chair of the RDA Steering Committee, about IFLA-LRM’s prohibition on recording fictitious entities as Agents (that is, as authors of books), which has been replicated in RDA.1 Gordon had used books by Snoopy the cartoon dog as an example, so I went with that. I asked about the RSC’s thought process behind accepting the LRM decision, while offering the view that such a policy was not in the best interests of library users. It was a… robust conversation. Attendees described it to me as ‘controversial’ and ‘the highlight of their day’! I have somehow become someone who courts cataloguing controversy wherever they go. I don’t know how this happened. I’m supposed to be a professional introvert.
Gordon pointed out that we could still use Snoopy as an access point in a record, but it wouldn’t be as a formal Agent. Or ‘Snoopy’ would end up being a Nomen (that is, a pseudonym, or a non-preferred name) for whichever real person actually wrote the book—‘Charles Schultz’ or an anonymous ghostwriter or team thereof. Gordon’s concern is with maintaining a clean dataset, and also something about all this being a variety of fake news (the idea being that we would be wilfully misrepresenting a book’s true authorship to our users).
In my view, it would be even worse to have to create all these unknown Agent entities for fictitious characters who are presented by works as supposedly being their author. The only purpose I can see this serving is to create a totally logically consistent data set anchored in the real world, purely for the benefit of a small subset of cataloguers and perhaps a smaller subset of researchers. The bibliographic universe doesn’t work like that. Our users don’t work like that. If we are to catalogue the item in hand—a maxim my workplace strictly enforces—then that entails taking what a book says about itself at face value. It might be real. It might not be. It doesn’t always matter. Rare books might need this kind of provenance attention. Mass-market children’s paperbacks don’t.
Accept entropy. Embrace chaos. Free Snoopy.
The future is bright, and also a long way off. Several speakers were at pains to emphasise that the future is not in metadata at the record level. Our future is in bulk uploads, editing, mass cataloguing and metadata management. A lot of cataloguers will be uneasy with this change, and it will probably not suit all sectors (especially rare books and more unique items). This is the kind of metadata future I want to be involved in. I just want to be involved in it now, and not in however many years when our systems are finally capable of more than just MARC. I have previously expressed my impatience with how long linked data is taking to actually happen. I am sick of waiting.
Ebe exhorted us to read Hugh Rundle’s 2015 post ‘Burn it all down’, so I did. Little has changed. The fire smoulders. Unlike Hugh, I don’t believe the age of cataloguers is over. But the age of handcrafted, bespoke, record-level metadata is almost over, which is the work cataloguers are used to doing (which is what I think Hugh was trying to say). I lean more towards reinventing or reclaiming the name ‘cataloguer’, rather than admitting defeat and styling myself a ‘metadata librarian’ (or, for that matter, ‘bibliographic data wizard’). Cataloguers will continue to do this work, using some of the skills we already have. As Melissa said, paying people with brains the size of planets to sit there and transcribe text is insanity. Make better use of us, and we will do amazing things.
RDA, meet Bibframe. I learned that the LRM / RDA community and the Bibframe community aren’t really talking to each other. It points to a growing issue of different standards developers working in isolation from each other and only really collaborating at the end, in sort of a ‘So, you’re gonna accept all this work I did, right?’ kind of way. I’m not saying this is necessarily a bad thing, because I suppose the alternative would be a highly centralised development approach (which is what produced MARC, and look where that got us). I was surprised by it, though. It would be like the authors of MARC and AACR2 not talking to each other, which would be inconceivable considering how tightly intertwined the two are.
They don’t need our standards. I get that Gordon has his heart set on a unified LAM metadata element set but I just can’t get behind it. For one thing, where’s the use case? Who else would use a library-developed schema for their non-library collections? Archives don’t need our leftovers—they’ve already got several competing standards, including ISAD(G), ISO 15489 DACS, RAD and others, and they’re all working fine. Rare books will keep using the awesome DCRM and museums already have CIDOC-CRM (apparently interoperable with IFLA-LRM) so they don’t need our thing either.
I don’t understand this blind pursuit of a cross-GLAM metadata model, when the whole reason we are still constituent GLAM sectors and not one big information management / cultural heritage conglomerate is because we have different use cases, different collections, different user needs regarding the description of those collections. (I was reminded of the numerous conversations at FutureGLAM on this topic.) What purpose does one model serve? Besides, isn’t one of the features of linked data that we can pick and choose elements and schemas that suit our collections?2 Why must we all be the same? Why are we bending over backwards to develop a schema that meets others’ needs, but not our own?
Still on the 'it's not just for libraries' bandwagon. I am firmly opposed to any standard for library resource description that does not prioritise libraries–and library users. LRM and RDA ain't it. Sorry, Gordon. #ACOC18
Are you there, cataloguing? It’s me, Alissa. Attending the ACOC seminar helped reawaken a little of the passion for cataloguing that I thought I’d lost. But it’s definitely changed, and I have changed with it. I’m still here, still standing, but a bit more weathered, and a bit less shiny. A lot less blindly optimistic. Cataloguing is still something I’m quite good at, knowledgeable about, adept in… but it feels less like my whole self, like there is still a hole in my soul. Maybe this is a new phase, a levelling-up, where I become a little more hardened and a little less magical. I don’t like it much.
Keeping this up will be the hard part. I’m straight back into a cataloguing environment with systems and standards that aren’t what they could be. I can’t do anything about that, but I can do something about how I react to and process these things. To an extent I’m just gonna have to lump it, and that is hard, but I also need to make sure I’m keeping up with new developments, poking my head above the parapet, looking out for what might be on the horizon.
ACOC helped me see the future of cataloguing. I hope that in some small way I can help make that future happen. 🙂
This comes up so often at seminars like this it’s made IFLA’s list of frequently raised gripes. (Also, LRM instructions can have citation numbering but RDA can’t, apparently. I decided to save my thoughts on that for another time.) ↩
Content warning: This post discusses self-harm, mental illness and institutional indifference to trauma.
That the Library of Congress Subject Headings (LCSH) are a biased, offensive and wholly outdated set of controlled terms is not a new concept in cataloguing. Plenty has been written on the innumerable ways LCSH describes people, places and concepts in ways that do not belong in a modern library catalogue. I hope plenty has also been written on the trauma this can cause library users (though I confess at the moment I can’t find much). But today I need to talk about a couple of terms in particular, terms that hit a little too close to home, and which I never want to see in a catalogue ever again. I need to talk about the trauma this causes me, a cataloguer. I need to talk. LCSH needs to listen.
Today on my cataloguing pile, there appeared a book on dealing with depression and mental illness. I won’t identify the book or its author, but it was a wonderfully helpful book that encouraged its reader to write in it and make it their own. This being a library copy, our readers naturally can’t do that, but I guess they could photocopy parts of the book if they needed. The author clearly had lived experience of these issues and sought to write a book that might help someone who is struggling, as they had once done.
One section of the book discusses what to do if the reader feels a need to self-harm. It includes things like ‘glue your fingers together and pick at that instead’, ‘count from 100 backwards and start again if you lose track’ and ‘make a list of people you can talk to, and don’t feel bad about talking to them’. To another cataloguer, it might have seemed like a minor portion of a book that is substantially about other things. To me, this topic is so important, and the advice so genuinely helpful, that I decided it needed surfacing in the catalogue record. In particular, I decided it merited its own subject heading.
Parasuicide (May Subd Geog)
Here are entered works on deliberate acts of selfharm in which there is no intent to die. Works on attempted suicide are entered under Suicidal behavior. UF Deliberate self-harm
Harm, Deliberate self
Self-harm, Non-fatal BT Self-destructive behavior RT Suicidal behavior
Self-mutilation (May Subd Geog)
Here are entered works on behaviors by which individuals intentionally cause damage to their bodies. Works on stereotyped behaviors by which individuals unintentionally cause damage to their bodies are entered under Self-injurious behavior. Works on nonstereotyped behaviors and cognitions by which individuals directly or indirectly cause harm to themselves are entered under Self-destructive behavior. UF Automutilation
Self-injurious behavior (Self-mutilation)
Self-injury (Self-mutilation) BT Malingering
Self-destructive behavior NT Cutting (Self-mutilation)
I hit the roof.
I read these and said, out loud, to an empty office: ‘You’ve got to be fucking kidding me.’ I skipped right past the dubious non-preferred terms (UFs), the distant and unfeeling scope notes, the questionable broader terms (‘Malingering’? Really?!). I zeroed in on the terms that someone, somewhere, in another place and another time, had decided were the right words to use to describe someone harming themselves.
Describing these acts as ‘Parasuicide’ is not helpful. I say this both as a cataloguer and as someone with lived experience of the acts in question. This is not good enough. This term needs to go.
People searching for works on this topic almost certainly be using the keyword ‘Self-harm’ or a close variation. If they’re using keyword search instead of subject search (and they will be, because nobody uses subject search anymore except librarians), these works will not appear in search results. They would have to know the particular term used by LCSH, thereby negating the point of having non-preferred terms in the first place, and be willing to overlook the inappropriateness of this term. I doubt anyone with an information need on this topic would be willing to overlook this. Certainly I’m not.
The scope notes for ‘Parasuicide’ are almost exclusively drawn from medical reference sources, suggesting the term is used in a medical context. Yet the term does not appear in the Medical Subject Headings (MeSH), used by most medical and health libraries. MeSH instead groups the concepts expressed by the LCSH terms ‘Parasuicide’ and ‘Self-mutilation’ together under ‘Self-injurious behavior‘, with a much more cogent hierarchy and set of non-preferred terms. MeSH restricts the term ‘Self-mutilation‘ to ‘the act of injuring one’s own body to the extent of cutting off or permanently destroying a limb or other essential part of a body’, with the implication that this is deliberate.
Because my library catalogues for a general audience, using LCSH and not MeSH, I would argue it is inappropriate to base a term on medical sources. We should instead be using general ones, using terms ordinary people would use. In an LCSH library, who is most likely to need information on this topic? How do they need it described? I would think the likeliest people are those experiencing ideations of self-harm, or people who know someone in this situation. Why does LCSH draw a distinction between ‘self-harm caused by mental illness’ and ‘self-harm caused for other reasons, including supposedly for attention’, and, from an information retrieval perspective, does this distinction matter? Would works intended for a general audience be more likely to use one term over another? What harm might this cause?
This book is primarily about helping sufferers help themselves. I would like to index it $a Self-harm $x Prevention $v Popular works (leaving aside for now the issues of having a specific form heading for ‘books for ordinary people’). Instead I will almost certainly have to use the heading $a Parasuicide $x Prevention $v Popular works, or perhaps I’ll go one step higher and use the broader term to both these headings, $a Self-destructive behavior. Even though that doesn’t really cover it, and doesn’t bring out the specific issue that I wanted the heading to address.
When I tweeted the other day that ‘Cataloguing is power’, this is what I meant! We have the power to guide users to the materials they’re looking for, via the words and phrases we use. Cataloguers have a responsibility to use terms that are meaningful to their users, especially when their userbase is the general public, and to take a stand against terms in their controlled vocabulary that are no longer appropriate.
I have a greater ability than most people to advocate for change in subject headings. I would like to see the heading ‘Parasuicide’ changed to one of its non-preferred terms that includes the phrase ‘Self-harm’. Ideally this term and ‘Self-mutilation’ would be combined, akin to the MeSH term ‘Self-injurious behavior’, with the accompanying taxonomy. But this won’t happen overnight. It certainly won’t happen in time for me to finish cataloguing this book. My workplace is very strict on adherence to standards and my options for deviation are limited. I might include some key phrases in a summary field, so that a keyword search would pick them up and bring this book to the people who need it most.
This post is a direct result of my emotional response to these headings. It is informed by my own lived experience of mental illness. It is the trauma of cataloguing, just as it is cataloguing that trauma. It is a traumatic response. I had this response at 5.30pm when the office was virtually empty, so everyone I might have talked to had already left for the day. Perhaps that was for the best. Instead I’ve been able to direct my energy into researching these headings and formulating options for change. I also bought myself some chocolate, which definitely helped.
I needed to talk. You, the reader, have generously listened. Now LCSH needs to listen, and reflect, and change.
The other day I decided to catalogue a podcast, mostly because Hugh gave me the idea. I cast about for a suitable work and I figured—why not catalogue cardiCast? I’m not a huge podcast listener, but I’ve really grown to enjoy the mix of live cardiParty recordings and interviews with selected guests.
Resources for cataloguing podcasts are thin on the ground, so I thought I’d share my take. This is not an officially-sanctioned, PCC-compliant guide or anything, just the views of a simple cataloguer who does this for fun.
any of you audio heads seen a PL catalogue podcasts (as continuing audio resources I guess)? ping @lissertations Because this is me but for podcasts and the apps don’t often have great discovery. I imagine there’d be some podcast/eaudio crossover interest.
This is gonna get technical. Let’s look at the Leader fields, first:
LDR/07 = (i), non-musical sound recording
LDR/08 = (s), serial
There’s not a lot of records on the ANBD with that particular combination. The closest I found to a podcast record was ‘Surgical news extra’, an audio accompaniment to an existing textual serial. (The cataloguer at SLV who created this is clearly a talented individual, they did a really good job!)
As far as the cataloguer is concerned, there are three aspects to a podcast: its audio content (spoken word, non-musical sound recording); its computer content (digital file, stored and accessed online); and its seriality (continuing resource, issued in discrete episodes as part of a broader whole).
Capturing these three aspects requires a lot of fixed field data, most of which (sadly) an ILS will never use. We will need the following:
1 x 008 field, music (matching the LDR/07 material type, non-musical sound recording. Just go with it)
Generally speaking, “the 008 and 006 are regarded as containing “bibliographic” information about a work, while the 007 is regarded as carrying information about the “physical” characteristics of the item”. I could go into exhaustive detail about each byte, but if you really want to know you’ll have clicked on the above hyperlinks already, so why reinvent the wheel?
Two aspects of fixed field entry stood out as being particularly tricky:
008/24-29, ‘Accompanying matter’ [to sound recordings]: this is really intended for physical accompaniments, not digital ones. ‘Show notes on iTunes’ doesn’t really fit any of the given options, so despite having six bytes to play with I settled for only one, ‘f’ (Biography of performer or history of ensemble), as the show notes (either in iTunes as embedded metadata or on the newCardigan website) usually have a brief explainer about who’s talking and what the topic is.
008/30-31, ‘Literary text for sound recordings’: I have two bytes to fill. Here I have to think quite deeply about the nature of cardiCast. I have a reasonably good list of options, but ‘cardiParties’ isn’t one of them. Nor can I record anything specific about the live nature of many podcast recordings. I eventually settled on ‘l’ (lectures, speeches) and ‘t’ (interviews).
Title and access points
Pleasingly, the title (as spoken by Justine at the beginning of each episode) actually fits really neatly into the ISBD syntax, as transcribed in the 245 field:
[Title] $a cardiCast :
[Subtitle] $b a GLAM podcast /
[Statement of responsibility] $c brought to you by newCardigan.
I really wanted to know whether I could keep newCardigan’s distinctive camelCase in the title and access points, or whether I had to refer to the work as ‘Cardicast’ and the producer as ‘Newcardigan’. Fortunately the RDA toolkit saw my dilemma coming, and handily permits the retention of unusual capitalisation if it is the most commonly-known form.
Names of Agents and Places
For names with unusual capitalization, follow the capitalization of the commonly known form. eg. eBay (Firm)
Titles of Manifestations
[…] Unusual capitalization. For titles with unusual capitalization, follow the capitalization of the title as found on the source of information. eg. eBay bargain shopping for dummies; SympoTIC ’06
I ran the catalogue record past the cardiCore before writing this post, to make sure I’d gotten the metadata itself correct. They agreed that Justine (as host) and Clare (as the sound editor) deserved added entries of their own. MARC accommodates this quite readily, simply by giving them each a 700 and a $e relator term from the exhaustive list. Naturally, newCardigan is accommodated in a 710 field.
Because nobody is actually going to read those fixed fields I just spent two hours painstakingly creating, I’m now going to fill in my 3XX and 5XX fields with all sorts of descriptive data about the podcast: how often it comes out (field 310), whether it’s streamable or downloadable (or both, in this instance), when it began (field 362), and what kind of content I can expect from the podcast (field 520).
Field 508 (Creation/Production Credits Note) enables me to credit the podcast as a newCardigan production and expand on Justine and Clare’s roles, while field 511 (Participant or Performer Note) notes that each episode has a different guest. I’ve also noted in field 588 where my descriptions have come from. This isn’t mandatory, but for a resource with no defined title page or home page it can be useful to know where the metadata came from.
The RDA content/media/carrier types are surprisingly simple: ‘spoken word’ content, ‘audio’ and ‘computer’ medium (so 2 fields) and ‘online resource’ carrier.
This podcast was difficult to index, chiefly because at first I wound up with too many overly-specific headings. I would have preferred an overarching $a GLAM industry $v Periodicals and $a GLAM workers $v Interviews but LCSH doesn’t have anything like that, so I had to split up the GLAM into its constituent sectors. I’m also not sure how I feel about $v Periodicals for continuing resources of this type. I think it’s the lack of print, textual content that bothers me a little. But it works, it has precedent elsewhere and I don’t have any better ideas. Perhaps in future $v Podcasts will become a form subdivision, just as it is already a genre/form term. Or we’ll abolish form subdivisions altogether. That’d be good.
In LCSH, ‘Galleries’ is a UF for ‘Art museums’, in case you were wondering.
NB: I originally wrote this in MarcEdit and painstakingly inserted all the spaces between subfields (don’t tell me, there’s a regex for that). The slash characters represent a blank space.
LDR 01880cis a2200433 i 4500
040 \\ $a ABCD $b eng $e RDA $d ABCD
042 \\ $a anuc
043 \\ $a u-at---
245 00 $a cardiCast : $b a GLAM podcast / $c brought to you by newCardigan.
246 3\ $a Cardi Cast
264 \1 $a Melbourne, Vic.: $b newCardigan, $c 2016-
300 \\ $a 1 online resource (audio files).
310 \\ $a Fortnightly
336 \\ $a spoken word $b spw $2 rdacontent
337 \\ $a audio $b s $2 rdamedia
337 \\ $a computer $b c $2 rdamedia
338 \\ $a online resource $b cr $2 rdacarrier
347 \\ $a audio file $b MP3 $2 rda
362 1\ $a Began in 2016.
500 \\ $a Available as streaming audio or as downloadable MP3 files.
500 \\ $a Resource website includes episode listing and links to individual downloads.
508 \\ $a Hosted by Justine Hanna ; sound editing by Clare Presser. A corporate
production of the newCardigan GLAM collective.
511 \\ $a Each episode features a different speaker or interviewee.
520 \\ $a "cardiCast is a GLAM podcast published every fortnight. Hear a recording of
a previous cardiParty, or interviews with interesting GLAM people from
around Australia and the world."--newCardigan website.
588 \\ $a Description based on episode 32 and information from the newCardigan
website. Title from spoken introduction of episode 32 (accessed
June 14, 2018).
610 20 $a newCardigan $v Periodicals
650 \0 $a Art museums $v Periodicals
650 \0 $a Libraries $v Periodicals
650 \0 $a Archives $v Periodicals
650 \0 $a Museums $v Periodicals
655 \7 $a Podcasts $2 lcgft
700 1\ $a Hanna, Justine $e host
700 1\ $a Presser, Clare $e recording engineer
710 2\ $a newCardigan $e producer
856 40 $z Website with links to episodes and accompanying text
UPDATE (20 June 2018): This has now been addressed! I noticed a couple of days ago that the NLA have updated this authority record, such that it now follows the AIATSIS example, “Jandamarra, approximately 1870-1897.” (The Libraries Australia heading and Trove duplicate issue both remain, but I understand they are managed by different areas within NLA.) While I was not directly informed of the NLA’s decision to update Jandamarra’s authority record, I am thrilled that they have done so. Thank you, NLA cataloguers, for making this necessary change.
It’s all well and good for librarians to talk about decolonisation, but we need to put our money where our mouths are. Cataloguers are no exception—we decide how resources are described and accessed. We dictate the effectiveness of a search strategy. We alone have the power to name.1
Being the sort of person who browses library catalogues for fun, I wound up on a NLA record for a play about Jandamarra, the Bunuba resistance fighter. Except the subject headings in this record didn’t name him at all. Instead they named some bloke called ‘Pigeon’.
The whole thing couldn’t be more colonial if it tried.3 A colonial institution (the library) referring to an Indigenous man by a colonial name (‘Pigeon’) and qualifying it with his year of death in a colonial calendar (1897). Jandamarra’s authority record represents his name and life as it was known to white people. How would the Bunuba describe him? Would they use the name ‘Jandamarra’ at all? What could a more culturally appropriate authority record look like? How might we disambiguate people without reference to colonial names, occupations or calendars?4
As a white cataloguer I firmly believe a change needs to be made. Such a change would have greater impact if it were also made in Libraries Australia, the national union catalogue (on which more later). The name ‘Pigeon’ is also used there, identically to its use in the NLA’s catalogue.
Let’s fix that
The issue then becomes: how might I make this change? More importantly, how might the community suggest a change? There is a way to suggest changes to name headings on the ANBD, but it’s very difficult to find—the Libraries Australia reftracker includes two options for ‘Propose a LCSH change’ and ‘Propose a new LCSH’ (where ‘LCSH’, apparently, includes all headings, name and subject alike). The form states that the info you provide goes straight to LC (that is, it’s not evaluated locally). It also immediately starts demanding my name, my NUC code, tells me to choose my 1XX heading, include 670 source citations, LC pattern or SCM memo, use for, broader term, related term??
I am a fluent MARC speaker and I know a 680 when I see one, but I have never dared fill out that form. I can’t see how an ordinary person would ever be able to suggest a formal change for Australian usage. Crowdsourcing initiatives like Violet Fox’s Cataloging Lab (which, for the record, I love), are necessarily US-centric and wouldn’t immediately address a local problem. Besides, the guidelines for establishing name authorities in the ANBD expressly state that Australian entities are exempt from the ‘let LC decide’ policy.
Besides, even if we were able to navigate the form and suggest a change, what would the change be? For guidance, I looked to AIATSIS’ catalogue. Sensibly, and in delightful accordance with RDA, they have opted to use 100 0# $a Jandamarra, $d approximately 1870-1897 as the preferred form. I figure if it’s good enough for AIATSIS, it’s good enough for me.
This record was created in 1989 and revised in 2013. A search of both LC’s catalogue and WorldCat (via the Libraries Australia Z39.50 interface, in case that makes a difference) brought up no results with this spelling, so I couldn’t determine if a particular work was used as its basis. Usually these works would be recorded in a 670 field, but these had nothing.
It would not be beyond LC to update its heading to the more commonly-used spelling. Pleasingly, they have form in this area: in 2003, LC changed several dozen subject headings relating to $a Aboriginal Australians (or $a Australian aborigines, as they were then described) in consultation with the NLA.
What’s in Trove?
I then found myself browsing the Trove People and organisations zone, where authority records are given a new life as sources of biographical data. Like other parts of Trove, the P&O zone aggregates and incorporates data from a variety of sources. I was therefore surprised to find Jandamarra listed under this name, using data from AIATSIS and the Australian Dictionary of Biography; as established above, both sources used the most commonly-known spelling. Notably, this did not include data from Libraries Australia:
The great thing about Trove identity records is that they display the ‘Also known as’ data (or UFs, or non-preferred terms, or 4XX fields, or whatever). It’s really hard to get an ILS to display this info, especially in an easy-to-read format like Trove has done. I’m really pleased to see this data out in the open and not hidden down the back of the authority file sofa.
We see that Jandamarra (-1897) is the first result, but the fifth is for Jundumurra, Pigeon (?!), which features data from AIATSIS and Libraries Australia. (This particular LA record pulls its data from AIATSIS anyway, so strictly speaking this isn’t the NLA’s fault, but it’s still a dupe that LA and/or Trove would have to merge.)
Interestingly, the original authority record from the NLA (‘Pigeon’, remember him?) doesn’t appear to be represented in the P&I zone at all. I wonder if that was a conscious or unconscious decision?
100 0# $a Jandamarra, $d approximately 1870-1897
400 #0 $a Jundamurra, $d approximately 1870-1897
400 #0 $a Sandamara, $d approximately 1870-1897
400 #0 $a Sandawara, $d approximately 1870-1897
400 #0 $a Tjandamara, $d approximately 1870-1897
400 #0 $a Tjangamarra, $d approximately 1870-1897
400 #0 $a Jandamura, $d approximately 1870-1897
400 #0 $a Pigeon, $d approximately 1870-1897
400 #0 $a Wonimarra, $d approximately 1870-1897
It turns out that Jandamarra has three (!) name authority records in Libraries Australia, one from the NLA and two from AIATSIS. Ordinarily I would consider this a major data integrity issue, and 100 10 $a Jundumurra, Pigeon is a bit of a problem, but for the moment I’m actually okay with the other two full-level records, because they help illustrate the differing approaches and mindsets from the two institutions. In time, I’d like to narrow that down, though.
In short, here’s what I would like to see happen so that Jandamarra is referred to by his rightful name in the ANBD, and in catalogues that use ANBD records:
1) Libraries Australia to modify their name authority record and establish the preferred form as $a Jandamarra, $d approximately 1870-1897, in accordance with that used by AIATSIS, and add non-preferred forms as appropriate. This change could then ripple across to the NLA’s catalogue, and other libraries that use Libraries Australia authorities would eventually follow suit. Maybe a little publicity around the change—after all, it’s being done for the right reasons.
2) Trove to merge the two identity records such that Jandamarra appears only once, that ‘Pigeon’ appears under the ‘Also known as’ list (so those who know him by that name are redirected accordingly), and that the sources of data encompass AIATSIS, Libraries Australia and the National Dictionary of Biography.
Such moves may seem small, but they would represent a sincere and concerted effort to decolonise the authority file. Cataloguers can, and should, restore the power to name to Indigenous communities, especially where colonial names have been used to describe Indigenous people and concepts. A name is not the cataloguer’s to take—it is the community’s to give.
Olson, Hope A. (2001). The Power to Name: Representation in Library Catalogs. Signs: Journal of Women in Culture and Society, 26(3), 639-668. doi: 10.1086/495624↩
For more on the cultural sensitivities around Indigenous subject headings, see Kam, D. V. (2007). Subject Headings for Aboriginals: The Power of Naming. Art Documentation: Bulletin of the Art Libraries Society Of North America, 26(2), 18-22. doi: http://dx.doi.org/10.1086/adx.26.2.27949465↩