The Library of Congress >> Especially for Librarians and Archivists >> Standards

MARC Standards

HOME >> MARC Development >> Proposals List


MARC PROPOSAL NO. 2017-FT01

MARC FAST-TRACK PROPOSAL

DATE: November 07, 2017
REVISED:

NAME: Repeatability of Field 384, and Adding Subfield $3 to that Field in the MARC 21 Bibliographic Format

SOURCE: Music Library Association

SUMMARY: MLA's main request is that MARC Field 384 (Key) be made repeatable in the Bibliographic format. In addition, to help associate the field 384 with the part of the resource or work to which it pertains, MLA requests validating Subfield $3 (Materials specified) in field 384 of the Bibliographic Format.

KEYWORDS: Field 384 (BD); Key (BD); Subfield $3, in field 384 (BD); Materials specified (BD)

RELATED: 2016-07

STATUS/COMMENTS:

11/07/17 – Submitted to the MARC Steering Group for consideration as a MARC Fast-Track proposal.

11/28/17 – Results of MARC Steering Group review - Approved.

12/18/17 – Changes made to the MARC documentation as part of MARC Update No. 25 (December 2017).


MARC Fast-Track Proposal No. 2017-FT01: Repeatability of Field 384, and Adding Subfield $3 to that Field

1. JUSTIFICATION

Music catalogers deal with compilations on a regular basis. The currently non-repeatable nature of field 384 in the Bibliographic format limits its use to single works, not composites, on the assumption that the field will be associated with the overall work being cataloged. Making the field repeatable would allow its use for compilations.

Field 384 already has $8, permitting some catalogers to associate Key with the works in a compilation to which they apply, provided access points for those works were provided by the cataloger. However, at least in North America, it is a much more prevalent practice to use subfield $3 to associate a field with other parts of the description. Related to this discussion, MARC Proposal 2016-07, Defining Subfield $3 in Field 382 of the MARC 21 Bibliographic Format, provided a further justification for the potential use of $3 in situations where a cataloger does not provide a formal access point for the works in compilation. This logic for adding $3 to field 382 could easily be applied to adding the subfield to field 384. For these reasons we also ask to validate the subfield $3 in the Bibliographic format.

Repeating Field 384 in the Authority Ffrmat could have some uses, though the use cases are different and less compelling to pursue at this time. We will not be requesting changes to the Authority format at this time.

Also, the 384 field could conceivably be used and repeated in the MARC Holdings frormat. However, it’s not currently defined there, and, again, we won’t address that topic as part of this proposal.

2. EXAMPLES

Two examples employing the proposed $3 in bibliographic records

An example employing $3 to associate keys listed in Field 384 with works described in a contents note, but perhaps for which individual access points have not been provided by the cataloger. The text of $3 could be prescribed by best practices, and perhaps could explicitly name works—as shown here—or refer to the numerical placement of works in a compilation—as the second example shows.

384 0# $3 Scriabin sonata no. 3 $a F♯ minor
384 0# $3 Prokofiev sonata no. 8 $a B♭ major
384 0# $3 Shostakovich sonata no. 2 $a B minor
245 00 $a Emil Gilels plays three Slavonic piano masterpieces of the 20th century.
505 0# $a Piano sonata no. 3 in F sharp minor, op. 23 / Alexander Scriabin (20:16) -- Piano sonata no. 8 in B flat major, op. 84 / Sergei Prokofiev (31:28) -- Piano sonata no. 2, op. 64 / Dmitri Shostakovich (28:12).
[No added access points provided in this record.]

An example employing $3 to associate keys listed in Field 384 with works described in both a contents note and in added access points. The Subfield $8 could be used instead of or in addition to $3; however, as mentioned earlier, its use is currently limited, and therefore is omitted from this example.

384 0# $3 Symphony H. 1, 49 $a F minor
384 0# $3 Concerto H. XVIII, 11 $a D major
384 0# $3 Symphony H. 1, 104 $a D major
100 1# $a Haydn, Joseph,  $d 1732-1809,  $e composer.
240 10 $a Orchestra music.  $k Selections
245 10 $a Symphonies 49 & 104 ; $b Piano concerto in D major / $c Haydn.
505 0# $a Symphony no. 49 in F minor : la passione (23:10) -- Piano concerto in D major Hob. XVIII:11 (19:55) -- Symphony no. 104 in D major : London (29:06).
700 12 $i Container of (work):  $a Haydn, Joseph,  $d 1732-1809.  $t Symphonies, $n H. I, 49, $r F minor.
700 12 $i Container of (work):  $a Haydn, Joseph,  $d 1732-1809.  $t Concertos, $m harpsichord, orchestra, $n H. XVIII, 11, $r D major.
700 12 $i Container of (work):  $a Haydn, Joseph,  $d 1732-1809.  $t Symphonies, $n H. I, 104, $r D major.

3. PROPOSED CHANGES

Make the following changes to field 384 (Key) of the MARC 21 Bibliographic Format:

3.1. Make the field repeatable.

3.2. Define subfield $3 (Materials specified).


HOME >> MARC Development >> Proposals List

The Library of Congress >> Especially for Librarians and Archivists >> Standards
(11/27/2017)
Legal | External Link Disclaimer Contact Us