Music Cataloging Procedures Home
|
Music Cataloging Procedures Home
|
|
Music Cataloging Procedures
CD Copy Cataloging -- Record Editing Instructions (RDA)
This document is meant to accompany the standard CD sound recording copy cataloging document found here. It will provide updates and new rules that the copy cataloger should be aware of when approaching an RDA record. This is not a complete list of all fields that the copy cataloger should check, but only those fields in which RDA practice differs significantly from previous cataloging codes.
Check this fixed field:
Desc: i
Check the 040 field for $e:
The 040 field should have "$e rda" code somewhere.
040 __ ERE $b eng $e rda $c ERE $d NOC
100 Creator (Personal name), 110 Creator (Group or ensemble)
The 100 field is only used for those figures involved in the creation of a work. This means that performers (including orchestras, choirs, and ensembles) and conductors are not featured in the 100 field. Mostly, you will only find composers here, but popular music ensembles (e.g., rock bands) that compose their own music might be here, as well as singer/songwriters that compose their own works and jazz artists that add substantial original material to their pieces. Performers and conductors will be put instead in 700 fields.
After the name in the authorized heading will come a relationship designator, which is preceded by a $e. The relationship designator will most likely be"composer." A heading would look like this:
100 1 _ Beethoven, Ludwig van, $d 1770-1827, $e composer.
Some names may have more than one relationship designator if they are responsible for multiple functions:
100 1 _ Dylan, Bob, $d 1941- $e composer, $e performer
110 2 _ Beatles (Musical group) $e composer, $e performer
Bob Dylan and the Beatles would get a 1XX field because they are responsible for composing, as well as performing, their works. Names such as the conductor George Szell or the ensemble Chicago Symphony Orchestra would not get a 1XX field, because they have no role in the composition of the works.
Add appropriate relationship designators if not present.
If there is no 1XX field, be sure that the 245 field reads 245 0 0 [title].
===
240 Uniform title. The word "arranged" is no longer abbreviated. If you see a "$o arr.", change this to read "$o arranged". Likewise, the instrument is now known as "cello" instead of "violoncello".
240 1 0 Concertos, $m cello, piano, $n B. 10, $r A major; $o arranged.
Many sound recordings contain selections. If these can't be distilled into a more specific category, the uniform title will be "Works. Selections" :
100 1 _ Beethoven, Ludwig van, $d 1770-1827, $e composer.
240 1 0 Works. $k Selections.
===
245 Title and statement of responsibility.
The subfield $c is used in this field to convey a statement of responsibility. Much like the 1XX fields, the 245 $c is only used to name creators of the work. Performers should not be named in this field (exception for popular/jazz recordings; see below).
Correct:
245 1 4 The nine symphonies / $c Ludwig van Beethoven.
Incorrect:
245 0 0 The best of the Cleveland Orchestra : $b symphonies and overtures / $c Cleveland Orchestra ; conducted by Leonard Bernstein.
In the last example, the Cleveland Orchestra and Leonard Bernstein are not responsible for the creation of the works, only their performance. So they should not be present in this field, and should be moved to a 511 field. The field would simply be:
245 0 0 The best of the Cleveland Orchestra : $b symphonies and overtures.
Move performers from a 245 $c field to a 511 field if necessary.
EXCEPTION: For popular and jazz music, a performer may still appear in the 245 $c field. This does not mean the performer will appear in the 100 field. For example:
245 0 0 Back to black / $c Amy Winehouse.
Performers still do not appear in the 245 $c for classical music.
The $h [sound recording] is not present in RDA records. Delete if found.
===
260 Imprint. 260 fields are almost never used in RDA; the information formerly contained here has been moved to the 264 field (see below).
===
264 Publication, etc. The 264 field is used to record multiple pieces of information related to the publication and distribution of the work.
Multiple 264 fields can be combined to describe an item's publication, distribution, and copyright information. Check these carefully to make sure each applies to the proper field. Remember that distributors are not publishers, and that a copyright date is not a publication date. The publication date will be in brackets if only a copyright date is visible.
264 _ 1 Hong Kong : $b Naxos Records, $c [2009]
264 _ 2 [Wisconsin] : $b Hal Leonard, distributor, $c [2009]
264 _ 4 $c ℗2009
Many sound recordings have no publication date. If only a phonogram date is present, make sure this date is present in a 264_4 field and include the date in brackets in a 264_1 field (see above example). If this is the case, be sure that your DtSt: t , and you have two Dates in the fixed field. So, for the above example, the fixed fields would be:
DtSt: t Dates: 2009, 2009
The abbreviations such as "s.l." and "s.n." have disappeared. There will be more user-friendly phrases, such as "place of publication not identified" or "date of distribution not identified". Additionally, the publisher will be transcribed as it appears on the resource; there will no longer be abbreviations such as "pub." or "co." unless it is written that way on the item in hand.
It is no longer necessary to add U.S. cities to the places of publication; the first or prominently named place will be the one used.
===
300 __ Physical Description.
The phrase "sound disc" is no longer used. Instead, use the phrase "audio disc".
In the $b subfield, the words "stereo" and "mono" are no longer considered abbreviations, and should not have a period after the word.
Example:
300 _ _ 1 audio disc (47 min.) : $b digital, stereo ; $c 4 3/4 in.
===
33X fields are used to describe the item in a way that can be read by machines. For CDs, these fields will most likely look like this:
336 _ _ performed music $b prm $2 rdacontent
337 _ _ audio $ s $2 rdamedia
338 _ _ audio disc $b sd $2 rdacarrier
===
34X fields are used to describe aspects of digital items in a way that can be read by machines. For CDs, these fields will most likely look like this:
344 _ _ digital $b optical $g stereo $2 rda
347 _ _ audio file $b CD audio $2 rda
Add these fields if not present. Remove the "$g stereo" if the item is not confirmed to be a stereophonic sound recording.
===
382 Medium of performance field
This field is used to indicate the medium of performance of a musical work. You may occasionally encounter these in score records; if found, keep as is unless it looks completely incorrect. Do not add if not present.
See more on the medium of performance field here.
===
500 Title note field
RDA requires a note on CD records to clarify where the title came from. In most cases, the title will come from the sticker affixed atop the disc itself. In this case, craft the note as follows:
500 _ _ Title from disc label.
Other options include "title from insert" or "title from container," depending on the source of the title in the 245 field.
===
650 Subject fields
Subject headings will no longer use the word "violoncello." Instead, the word "cello" will be used:
650 _ 0 Cello and piano music.
===
655 Genre fields
Genre headings are being used in RDA records, starting around 2015. For now, these currently mirror subject headings, but will eventually replace them altogether. Add a genre heading if not present and one can easily be ascertained from what's in the 650 field.
Search genres in Connexion by going to Authorities--Browse--LC Names and Subjects, and choosing "Genre". All terms come from the Library of Congress Genre/Form Thesaurus (LCGFT), and are placed in the 655_7 field, with a $2 lcgft.
So a jazz record might look like this:
650 _ 0 Jazz music $y 2011-2020.
655 _ 7 Jazz. $2 lcgft
A classical record might look like this. Remember that genres are different from medium of performance:
650 _ 0 Sonatas (Violin and piano)
655 _ 7 Sonatas. $2 lcgft
===
700 Added entry field
Like the 100 field, the 700 field will also container $e relationship designators. However, there will be more of these terms, including:
Do not add any relationship designators to names in 700 field if not present. Correct any obvious errors.
Example:
700 1 _ Bell, Joshua, $d 1967- $e performer.
===
The 700 12 name title field will follow the stipulations of the 240 field. The word "arranged" will be spelled out, and the instrument will be known as "cello" instead of "violoncello". For example:
700 1 2 Dvořák, Antonín, $d 1841-1904. $t Concertos, $m cello, piano, $n B. 10, $r A major; $o arranged.
There is no specific cut-off for the number of access points that can be added for name-titles. In general, control access points for classical music works. There may not be access points for pieces in anthologies or collections of popular or jazz music.
Created by cdh, 10/1/13
Edited cdh 10/1/13, 10/7/13, 5/30/14, 10/31/14, 6/18/15, 9/24/15, 1/26/16, 4/12/16
Top of page
Music Cataloging Procedures Home
 |
|||
|
|||
 |
Music Library East Carolina University Greenville, NC 27858-4353 USA 252.328.6250 |
 |
|