The Library of Congress >> Especially
for Librarians and Archivists >> StandardsThe Library of Congress >> Especially
for Librarians and Archivists >> Standards
HOME >> MARC Development >> Proposals List
DATE: June 4, 2015
REVISED:
NAME: Extending the Use of Subfield $0 (Authority record control number or standard number) to Encompass Content, Media and Carrier Type
SOURCE: British Library
SUMMARY: This paper proposes the definition of subfield $0 (Authority record control number or standard number) in fields 336, 337 and 338 in the Bibliographic Format and 336 in the Authority Format.
KEYWORDS: Subfield $0 (AD, BD); Authority record control number or standard number (AD, BD) ; Controlled vocabularies (AD, BD); Field 336 (AD, BD) ; Content Type (AD, BD); Field 337 (BD) ; Media Type (BD); Field 338 (BD); Carrier Type (BD)
RELATED: 2009-01/2 ; 2011-08 ; 2010-06
STATUS/COMMENTS:
06/04/15 – Made available to the MARC community for discussion.
06/28/15 – Results of MARC Advisory Committee discussion: Approved with the amendment to also define subfield $0 (Authority record control number or standard number) in Appendix A and fields 337 (Media Type) and 338 (Carrier Type) in the Holdings format.
08/06/15 - Results of MARC Steering Group review - Agreed with the MAC decision.
The MARC formats make provision for recording a number of RDA controlled vocabularies. Controlled vocabularies relating to content, media and carrier type are covered by the 33X tag block. Controlled vocabularies relating to carrier characteristics are covered by the 34X tag block. However, whereas it is possible to code subfield $0 (Authority record control number or standard number) in the case of carrier characteristics, the same is not the case for content, media and carrier type. The British Library suggests that this inconsistency could be resolved by defining $0 in the 33X fields relating to the Bibliographic and Authority formats. Implementing this change would be beneficial in terms of supporting linked data applications. The URIs (Uniform Resource Identifiers) for controlled vocabulary terms could be recorded in the case of content, media and carrier type as they can be for carrier characteristics.
RDA implementation has been facilitated by the definition of new fields and subfields to accommodate controlled vocabularies in the MARC formats. Fields 336 (Content Type), 337 (Media Type) and 338 (Carrier Type) were defined following the approval of Proposal 2009-01/2. Fields 344 (Sound Characteristics), 345 (Projection Characteristics of Moving Image), 346 (Video Characteristics) and 347 (Digital File Characteristics) were defined following the approval of Proposal 2011-08. Results of the MARC Advisory Committee discussion on the latter paper included the definition of subfield $0 in MARC fields 344, 345, 346, 347 and also 340 (Physical Medium).
The scope of subfield $0 was broadened to encompass the recording of standard numbers as well as authority control numbers following the approval of Proposal 2010-06. The current definition of $0 in Appendix A of the Bibliographic and Authority formats is given below:
Subfield $0 contains the system control number of the related authority record, or a standard identifier such as an International Standard Name Identifier (ISNI). The control number or identifier is preceded by the appropriate MARC Organization code (for a related authority record) or the Standard Identifier source code (for a standard identifier scheme), enclosed in parentheses. See MARC Code List for Organizations for a listing of organization codes and Standard Identifier Source Codes for code systems for standard identifiers. Subfield $0 is repeatable for different control numbers or identifiers.
The following example demonstrates the coding of an ISNI standard identifier in relation to a name authority heading:
100 1# $a Trollope, Anthony, $d 1815-1882.$0 (isni) 0000000121358464
Besides the ISNI, the MARC list of standard identifier source codes also makes provision for recording URIs in subfield $0. The following example demonstrates the coding of a URI in relation to an LCSH heading:
650 #0 $a Courtship $v Fiction $0 (uri) http://id.loc.gov/authorities/subjects/sh2008100298
Definition of $0 in fields 340, 344, 345, 346 and 347 already allows URIs to be recorded as identifiers for controlled terms relating to carrier characteristics. The following example demonstrates its use in this context:
344 ## $a analog $0 (uri) http://rdaregistry.info/termList/typeRec/1001
Adding subfield $0 to fields 336, 337 and 338 would provide the same functionality in the 33X tag block as that which exists in the 34X tag block.
Although fields 337 and 338 are defined in the Holdings as well as the Authority and Bibliographic formats, it is not necessary to define $0 in these cases because the subfield is not present at the holdings level. Further definition of $0 may be desirable in the Authority and Bibliographic formats beyond the 33X tag block. However, such a development is beyond the scope of this paper.
The following example sets illustrate the use of subfield $0 as a means of recording URIs for controlled terms which relate to content, media and carrier type in MARC records. Four different scenarios are modelled.
Example Set 1
33X field terms qualified by URIs recorded on id.loc.gov and MARC codes identifying the source of term.
336 ## $a performed music $0 (uri) http://id.loc.gov/vocabulary/contentTypes/prm $2 rdacontent
337 ## $a audio $0 (uri) http://id.loc.gov/vocabulary/mediaTypes/s $2 rdamedia
338 ## $a audio disc $0 (uri) http://id.loc.gov/vocabulary/carriers/sd $2 rdacarrier
Example Set 2
33X field codes qualified by URIs recorded on id.loc.gov and MARC codes identifying the source of code.
336 ## $b prm $0 (uri) http://id.loc.gov/vocabulary/contentTypes/prm $2 rdacontent
337 ## $b s $0 (uri) http://id.loc.gov/vocabulary/mediaTypes/s $2 rdamedia
338 ## $b sd $0 (uri) http://id.loc.gov/vocabulary/carriers/sd $2 rdacarrier
Example Set 3
33X field terms and codes qualified by URIs recorded on id.loc.gov and MARC codes identifying the source of term and code.
336 ## $a performed music $b prm $0 (uri) http://id.loc.gov/vocabulary/contentTypes/prm $2 rdacontent
337 ## $a audio $b s $0 (uri) http://id.loc.gov/vocabulary/mediaTypes/s $2 rdamedia
338 ## $a audio disc $b sd $0 (uri) http://id.loc.gov/vocabulary/carriers/sd $2 rdacarrier
Example Set 4
33X field terms qualified by URIs recorded on the RDA Registry; repeated 33X field terms qualified by MARC codes identifying the source of term.
336 ## $a performed music $0 (uri) http://rdaregistry.info/termList/RDAContentType/1011
336 ## $a performed music $2 rdacontent337 ## $a audio $0 (uri) http://rdaregistry.info/termList/RDAMediaType/1001
337 ## $a audio $2 rdamedia338 ## $a audio disc $0 (uri) http://rdaregistry.info/termList/RDACarrierType/1004
338 ## $a audio disc $2 rdacarrier
In example sets 1-3 each content, media and carrier type term is qualified by both a URI and a source code. This is because the vocabularies for content, media and carrier listed at id.loc.gov correspond to equivalent MARC21 term and code lists. 33X fields in example set 4 do not follow this pattern. Instead, each content, media and carrier type term is repeated as a means of separating the URI from source code qualifier. This is because the RDA Registry and MARC21 term and code lists, though presently comparable in most respects, are subject to independent development. Under these circumstances, using a field which contains both an RDA Registry URI and a MARC21 code as a source linked data may lead to semantic inconsistency over time. The same condition may apply to a field which contains both an RDA Registry and an id.loc.gov URI. However, example set 4 still presents a means of serving both the linked data and MARC21 communities in a single record context.
The inclusion of an identifier in $0 is highly desirable for BIBFRAME when converting MARC data.
In fields 336, 337 and 338 of the MARC 21 Bibliographic Format and field 336 of the Authority Format define:
$0 - Authority record control number or standard number (R)
See description of this subfield in Appendix A: Control Subfields.
HOME >> MARC Development >> Proposals List
| The Library of Congress >> Especially for Librarians and Archivists >> Standards ( 08/06/2015 ) |
Legal | External Link Disclaimer | Contact Us |