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.
Be careful what you wish for, etc.
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:
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:
$a cardiCast :
$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