Joyner Library Banner

Music Cataloging Procedures Home

 

Music Cataloging Procedures
Score Copy Cataloging -- Record Editing Instructions (RDA)

This document is meant to accompany the standard score 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 to make sure the record is RDA

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


Check Match Fields and Notes:

100 Composer. The 100 field will have an authorized heading of the composer responsible for the work. Only composers can be in the 100 field; arrangers and transcribers are instead recorded in 700 fields. After the authorized heading will come a relator term, which is preceded by a $e. For scores, the relator term will always be "composer." A heading would look like this:

100 1 _ Beethoven, Ludwig van, $d 1770-1827, $e composer.

Add a "$e composer" if not present.

===

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.

Other changes may be present in uniform titles. If in doubt, check to see if the title has a national authority file to consult.

===

254 Musical format statement. The 254 field is no longer used in RDA. All musical format statements (e.g., "study score" or "high voice") should be listed in the 250 field.

If a 254 field is present, move this information to a 250 field.

===

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 Kassel : $b Baerenreiter, $c [2009]

264 _ 2 [Wisconsin] : $b Hal Leonard, distributor, $c [2009]

264 _ 4 $c ©2009

Many pieces of music have no publication date. If only a copyright 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).

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 abbreviation "p." is no longer used in the $a subfield. Instead, spell out "pages" completely.

Additionally, the phrase "p. of music" or "pages of music" is no longer an option. All scores should be described as "1 score (x pages) :"

"Close score" and "miniature score" are no longer options for this field. A miniature score will now be referred to as a "study score" (this refers to the size of the notes and staves, not the size of the item. Large scores with small notes unsuitable for performance are still considered study scores). "Piano score" and "vocal score" can be used.

The full list of terms for musical materials in a 300 field is as follows:

score ; condensed score ; study score ; piano conductor part ; violin conductor part ; vocal score ; piano score ; chorus score ; part ; choir book ; table book .

In the $b subfield, the terms are no longer abbreviated. Words such as "illustrations" and "facsimiles" are fully spelled out. Spell out these abbreviations if you encounter them.

In the $c subfield, the letters "cm" are consider a "symbol" and it no longer has a period after it. (Exception: If there is a 490 field present, the 300 field does end with a period.)

Example:

300 _ _ 1 study score (34 pages) : $b illustrations ; $c 37 cm

===

33X fields are used to describe the item in a way that can be read by machines. For scores, these fields will most likely look like this:

336 _ _ notated music $b ntm $2 rdacontent
337 _ _ unmediated $b n $2 rdamedia
338 _ _ volume $b nc $2 rdacarrier

These should always be present in an RDA score record.

===

382 Medium of performance field

This field is used to indicate the medium of performance of a musical work. If found in a score record, keep as is unless it looks completely incorrect. Add if not present according to the instructions on the 382 page.

===

546 Language field Use $b here to record the sort of notation used. "Staff notation" will be the overwhelmingly most popular option, but other possibilities include "graphic notation, "tablature," or "mensural notation." The complete list is as follows:

graphic notation ; letter notation ; mensural notation ; neumatic notation ; number notation ; solmization ; staff notation ; tablature ; tonic sol-fa

The 546 field is repeatable, and a separate entry is used for recording language elements, like this:

546 _ _ English words, printed separately as text.
546 _ _ $b Staff notation.

Add this field if not present.

===

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 $v Scores.

===

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:

A "lyricist" writes the words for popular songs, a "librettist" writes the words for dramatic works. Any other authors of sung text should simple be referred to as "author" in the subfield $e.

Do not add any relationship designators to names in 700 field if not present. Correct any obvious errors.

===

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.

Occasionally you may see a $i relator code for the work, like this:

700 1 2 $i Contains (work): $a Dvořák, Antonín, $d 1841-1904. $t Concertos, $m cello, piano, $n B. 10, $r A major; $o arranged.

Other $i codes includes "Contains (expression)" or "Related to (manifestation)". These might be found in the 700 field or the 775 or 776 field. Generally they should be left alone. Do not add $i subfields to name-title access points.


Created by cdh, 7/31/13.

Edited cdh 8/5/13, 8/14/13, 9/6/13, 3/11/14

Top of page
Music Cataloging Procedures Home

 
ECU Logo  
Music Library
East Carolina University
Greenville, NC 27858-4353 USA
252.328.6250
Contact the Music Library
Page updated 7/31/2013 cdh
Return to ECU Home Page