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

MARC Standards

HOME >> MARC Development >> Proposals List


MARC PROPOSAL NO. 2010-03

DATE: December 14, 2009
REVISED:

NAME: Recording Place and Date of Capture in the MARC21 Bibliographic Format

SOURCE: RDA/MARC Working Group

SUMMARY: This proposal addresses issues of granularity in recording date and place of capture in the MARC21 Bibliographic Formats. It gives two options: changing field 033 to accommodate greater precision in coding date and place data or defining new subfields in field 518.

KEYWORDS: Field 033 (BD); Field 518 (BD); Date of capture (BD); Place of capture (BD)

RELATED: 2009-DP06/2; 2008-DP04; 2008-05/1

STATUS/COMMENTS:
12/14/2009 - Made available to the MARC 21 community for discussion.

1/17/10 - Results of MARC Advisory Committee discussion: Approved both options as amended. Add subfield $0 (Record control number) (R) to fields 033 and 518; add $o (Other capture information) (NR) and delete $i (Introductory phrase) in 518.

02/26/10 - Results of LC/LAC/BL review - Agreed with the MARBI decision.


Proposal No.2010-03: Recording Place and Date of Capture in the MARC 21 Bibliographic Format

1. BACKGROUND

As noted in Discussion Paper 2009-DP06/2, RDA provides greater granularity than the MARC21 formats in relation to Place of capture and Date of capture. These two RDA elements map to the same MARC21 Bibliographic fields. Field 033 provides greater granularity than Field 518, although the former field currently contains only coded data.

Although the MARC Advisory Committee supported moving 2009-DP06/2 forward to the proposal stage, the issue of granularity in these fields was debated and remained unresolved. Some committee members expressed concern about adding free-text data (suggested for a new subfield $d) in 033, a field which typically has included only coded data, while others thought it would be beneficial as a means of controlling place name. Additionally, some thought that parsing data in field 518 would be useful in making clear distinctions between place, date of capture, and materials specified (subfield $3), while others thought it would be more useful and less confusing to keep 518 as an unstructured eye-readable field. This proposal presents all of these options.

2. DISCUSSION

2.1. Current definition of Field 033

Field 033 already provides the necessary granularity to encode the basic information related to Place of Capture and Date of Capture. Note that the current definition restricts data in this field to coded form rather than prose in order to enable machine use of the data.

Field Definition and Scope:
Formatted date/time and/or coded place of creation, capture, or broadcast associated with an event or the finding of a naturally occurring object. This information in textual form is contained in field 518 (Date/Time and Place of an Event Note). Such information includes the date/time and/or place of recording, filming, execution, or broadcast of an event.

Subfield $a enables machine manipulation, as the data is recorded in an ISO-compliant form.  Data entered in subfield $b is limited to a four to six character numeric code derived from the Library of Congress Classification--Class G; for expansion, subfield $c may contain an alphanumeric Cutter number for a geographic subarea, again derived from the G Classification Schedule. This construction does not often allow for the specificity beyond the city or similar jurisdiction.  Although the field was originally defined only to include place data that is in coded form using LCC it could be expanded to include place data from other sources and in textual form.

2.2. Current definition of Field 518

Field 518 provides the equivalent date and place of capture information in eye-readable form. It contains the same if not more granularity as the 033, but its content is not parsed into subfields for each type of information. 

Field Definition and Scope:
Note on the date/time and/or place of creation, capture, recording, filming, execution, or broadcast associated with an event or the finding of a naturally occurring object. Field 033 (Date/Time and Place of an Event) contains the same information in coded form.

2.3. Expanding Field 033 for Place of capture

Field 033 could be expanded beyond the use of codes derived from the LCC Class G schedule to accommodate more specific locations, such as recording studios, particular churches, or most concert halls. Since the needed granularity for parsing date and place of capture is already available in this field, the simplest option is to revise the definition restricting the data to coded form and add a subfield for other place of capture data.

This proposal suggests a separate repeatable subfield $d (Place of capture). This addition would require changing the definition of Field 033 to allow for non-coded, and potentially uncontrolled, data. To accommodate a controlled form in subfield $d, subfield $0 (Authority record control number) and subfield $2 (Source of heading or term) need to be defined.

Because sound recordings may contain works captured in different places and/or on different dates, subfield $3 (already defined for materials specified) could be used for greater precision.

The definition of field 033 could be revised as follows (italics indicate additions):

“Formatted date/time and/or place of creation, capture, or broadcast associated with an event or the finding of a naturally occurring object in coded or uncoded form. This information in a non-parsed textual form is contained in field 518 (Date/Time and Place of an Event Note). Such information includes the date/time and/or place of recording, filming, execution, or broadcast of an event.”

Examples of changes for field 033:

   033 00 $a200008--$b5754$cL7$dAbbey Road Studio 1
   Capture: August 2000, Abbey Road Studio 1, London

   033 10 $a197907--$a197802--$a197909--$a198001--$b5834$cP3$dSalle Wagram
   Capture: July 1979, February 1978, September 1979, January 1980, Salle Wagram, Paris

or

   033 00 $31st -2nd works$a197907--$b5834$cP3$dSalle Wagram
   033 00 $33rd work$a197802--$b5834$cP3$dSalle Wagram
   033 00 $34th work$a197909--$b5834$cP3$dSalle Wagram
   033 00 $35th work$a198001--$b5834$cP3$dSalle Wagram
   Capture: July 1979 (1st-2nd works), February 1978 (3rd work), September 1979 (4th work), January 1980 (5th work), Salle Wagram, Paris

   033 20 $a19930801$a19930806$b3454$cL25$dEglise de la Nativité de la Sainte-Vierge
   Capture: August 1-6, 1993, Eglise de la Nativité de la Sainte-Vierge, La Prairie, Québec

   033 20 $31st-3rd works$a20070911$a20070912$b6299$cB3$dTeldex Studios
   033 00 $34th work$a20061112$b6299$cN38$dReitstadl
   Capture: September 11-12, 2007, Teldex Studios, Berlin (1st-3rd works); November 12, 2006, Reitstadl, Neumarkt in der Oberpfalz (4th work)

   033 11 $3Cziffra$a196205--$a196207--
   033 11 $3Moiseiwitsch$a19541103$a19630207
   033 01 $3Bolet$a19621116
   Broadcast: May, July 1962 (Cziffra); November 3, 1954, February 7, 1963 (Moiseiwitsch); November 16, 1962 (Bolet)

2.4. Expanding Field 518 for Date of capture and Place of capture

Field 518 contains the information specified by RDA in a note form.  It is not clear whether RDA is mandating that the information be included in the record or that it be included and parsed (via subfielding in the case of MARC).  Usually parsing is done to support retrieval and is accompanied by formatting of the information for machine manipulation, especially date and geographic information.  However another option involves expanding field 518, which would require more format changes and redundancy with data already recorded in field 033.  Possible new subfields that would need to be defined are: $d for Date of capture, $i for an Introductory phrase and $p for Place of capture. In addition, subfields $0 and $2 would be needed to pertain to the data in $p.  Possible new subfields that could be defined are: $d for Date of capture, $i for an Introductory phrase and $p for Place of capture. Subfields $d and $p could be recorded in a controlled form or in free text. Subfields $0 and $2 also could be defined to pertain to the data in $p. If these new proposed subfields are approved, the existing subfield $a should be retained with its current definition to accommodate data in a non-parsed form.

Examples of new subfields:

   518 ## $iBroadcast$d1954 October 17 at 7:30 p.m. (PST).

   518 ## $iFilmed on location:$pRome and Venice$d1976 January through June.

   518 ## $iRecorded$d1979 March 19-21 and November 16-18$pKirche der Karlshöhe, Ludwigsburg.

   518 ## $iRecorded live$pLugano Festival Stelio Molo, Lugano, Italy$d2007 June.

   518 ## $i1st-2nd works recorded$d1969 December 14-17$pLukaskirche, Dresden.

   518 ## $i3rd work recorded$d1981 November 25$pNeues Gewandhaus, Leipzig.

or

   518 ## $31st-2nd works$irecorded$d1969 December 14-17$pLukaskirche, Dresden.

   518 ## $33rd work$irecorded$d1981 November 25$pNeues Gewandhaus, Leipzig.

3. PROPOSED CHANGES

3.1. Option 1. Define the following subfields in Field 033 in the MARC 21 Bibliographic Format:

$d – Place of capture.  (R)
Place of creation, capture, recording, filming, execution, or broadcast associated with an event or the finding of a naturally occurring object. May be in a controlled or uncontrolled form.

$2 - Source of heading or term (R) [for $d only]

Leave field 518 as defined for the information in textual note form.

3.2.  Option 2. Define the following subfields in Field 518 in the MARC 21 Bibliographic Format:

$d – Date of Capture (R)
Date/time of creation, capture, recording, filming, execution, or broadcast associated with an event or the finding of a naturally occurring object. May be in a controlled or uncontrolled form

$i – Introductory Phrase (NR)
Introductory phrase that introduces the date or place of capture.

$p – Place of Capture (R)
Place of creation, capture, recording, filming, execution, or broadcast associated with an event or the finding of a naturally occurring object. May be in a controlled or uncontrolled form.

$2 – Source of heading or term (R). [for $p only]


HOME >> MARC Development >> Proposals List

The Library of Congress >> Especially for Librarians and Archivists >> Standards
( 12/21/2010 )
Legal | External Link Disclaimer Contact Us