PROPOSAL NO: 2003-04

DATE: May 19, 2003
REVISED:

NAME: Definition of Field 024 (Other Standard Identifier) to the MARC 21 Authority Format

SOURCE: OCLC

SUMMARY: This paper proposes adding Field 024 (Other Standard Identifier) to the MARC 21 Authority Format to allow for recording standard identifiers relevant to the entity described in the authority record.

KEYWORDS: Field 024 (BD, AD); Other Standard Identifier (BD, AD); Identifier (BD, AD)

RELATED: 2003-DP03

STATUS/COMMENTS:
05/19/03 -- Made available to the MARC 21 community for discussion.

06/21/03 - Results of the MARC Advisory Committee discussion - Approved as amended. NLM proposed that the first two sentences of the field definition be combined with the word "which." The subfields were examined by NDMSO for applicability (especially subfield $c) and a decision was made to handle them as in the authority 020 field.

07/23/03 - Results of LC/NLC/BL review - Agreed with the MARBI decisions.

Proposal No. 2003-04: Definition of Field 024

1. INTRODUCTION

This paper proposes the addition of Field 024 (Other Standard Identifier) to the MARC 21 Authority Format. This would allow for the recording of standard identifiers relevant to what is identified in the 1XX field in the authority record. There are a number of efforts to develop standard identifiers for works/expressions as well as for people and organizations, and as they are implemented, there will be a need to record them in authority records. In addition, there are efforts to establish authority records for "trademarks," particularly in Europe. Examples are the International Standard Text Code (ISTC), International Standard Audiovisual Number (ISAN), International Standard Musical Work Code (ISWC), International Standard Recording Code (ISRC), and the International Standard Authority Data Number (ISADN).

The MARC Advisory Committee discussed 2003-DP03 (Adding Field 024 (Other Standard Identifier) to the MARC 21 Authority Format) at its midwinter ALA meeting in January 2003. Participants were in favor of a proposal to define field 024 in the MARC 21 Authority Format that would also discuss usage in the Bibliographic Format.

2. DISCUSSION

2.1. Authority records as identifiers

With the increasing proliferation of both nondigital and digital materials, there are efforts in standards organizations to uniquely identify both individual works/expressions as well as persons and organizations. In MARC, these entities are represented by authority records, which serve the function of providing a controlled form of name that can then be used in bibliographic records as a collocation device.

Authority records for uniform titles (Field 130 Heading - Uniform Title) and name/uniform title combinations (1XX fields/subfield $t) identify unique individual works/expressions using established headings constructed with generally accepted cataloging and thesaurus-building rules.

Currently authority records for uniform titles are not always established. Authority records for uniform titles may be created more frequently as the library community continues to integrate the FRBR model into cataloging practices. In addition, if there is a field in the Authority format to record an International Standard Text Code (ISTC) or other work/expression level codes, there may be an increase in their creation.

2.2 Standards developed by ISO TC46/SC9

Subcommittee TC 46/SC 9 of the ISO (International Organization for Standardization) has been developing standards for the identification and description of a variety of information resources using alphanumeric codes. These codes are intended for use by a variety of organizations, including libraries and archives and will allow for the unique identification of resources. A major function of these identifiers is assisting in tracking rights to the intellectual content of resources. Some of the standards have already been approved; others remain under development.

Some of the standards include:*

2.3 Application of ISO TC 46/SC 9 standards to authority records

In terms of the Functional Requirements of Bibliographic Records (FRBR) model, bibliographic records are generally created for bibliographic resources at the level of manifestation, while authority records for uniform titles are considered work or expression level. The codes listed above function as work or expression identifiers. For example an ISTC (International Standard Text Code) functions as an expression identifier (although there will be some instances when the work and expression are identical). ISTCs may be used to identify the entity described in an authority record. Although they represent manifestations, bibliographic records could also contain ISTCs, as it might be useful to record the expression level identifier there to show the relationship from a particular manifestation (as identified in the bibliographic record) to the work/expression (as identified in the authority record).

In the Bibliographic format, field 024 (Other Standard Identifier) already exists and would be an appropriate field in which to record this information if desired, with the source of the identifier recorded in subfield $2. The Library of Congress would define additional source codes to accommodate the new identifiers (e.g. istc, iswc, isadn, etc.). The field would need to be defined in authority records, where it is not currently defined.

During the discussion of 2003-DP03 some participants suggested using another MARC field since the ISTC and other codes are different type of identifiers than those currently used in field 024. However, too few 0XX fields remain available in either the Bibliographic or Authority formats. Since these codes function in a similar manner as the standard identifiers for which the 024 field is used in the Bibliographic format, this paper proposes using this existing field. It might be considered whether the application of field 024 in authority records should be limited to specific types of entities. For instance, it seems unlikely to be applicable for subject records.

2.3.1 ISTC assignment and maintenance

Usage of the ISTC code, could begin in the near future. The OCLC ISTC Global Registration Service will maintain the ISTCs and their associated metadata. Top-level metadata elements include information about the title, contributor, language and registration as well as work origination information (from a controlled list) and source work information. This metadata will be accessible to organizations assigning ISTCs. OCLC will also relate the ISTCs to the appropriate authority and bibliographic records.

2.3.2 Use of ISTCs on items

The latest draft of the ISTC standard does not mention whether or not ISTCs would be displayed on items; however, the working group developing it thinks that publishers would eventually display them on items they publish. This means that expression level identifiers might appear on the manifestation of an expression. Display on an item should not be a requirement for recording an ISTC in an authority record, since there may be other sources for the data (e.g., the OCLC ISTC database).

2.4 Definition of field 024

2.4.1 Definition in the bibliographic format

Field 024 is defined as follows in the bibliographic format:

024 Other Standard Identifier (R)

2.4.2 Definition in the authority format

If defined in the authority format not all content designators are needed. The indicator values are for manifestation level identifiers except for the International Standard Recording Code (ISRC), which is an expression level identifier. Thus values 1-4 are not appropriate in an authority record, which includes entities at work or expression levels. The second indicator is also irrelevant to an authority record.

Discussion at the 2003 ALA midwinter meeting indicated the desirability of keeping usage of the 024 field in the Authority format generally consistent with that in the 024 field in the Bibliographic format. However there was some concern that including indicators that would be irrelevant in the Authority format might result in coding errors. Consequently this proposal suggests indicating the source of the identifier in subfield $2 and defining only indicator values 7 and 8.

The same subfield codes that are in the bibliographic format would be needed in the authority format. Although $c (Terms of availability) includes information about the manifestation, it also may include parenthetical qualifying information so it should be included for authority records.

The field would need to be repeatable, as it is in the bibliographic format, to allow for recording different types of identifiers, whose source is identified in $2.

The field definition and scope would need to be modified to apply to authority records. The following is suggested:

This field contains a standard number or code associated with the entity named in the 1xx field. It cannot be accommodated in other standard number fields (i.e., field 020 (International Standard Book Number), 022 (International Standard Serial Number)). The source of the standard number or code is identified in subfield $2. The subfields in this field are defined for consistency with field 020 in the MARC 21 Format for Bibliographic Data.

Examples of the use of field 024 in authority records are as follows:

010 ## no 98012500
024 7# $a [ISTC number/code] $2 istc
100 10 $a Eliot, George, $d 1819-1880. $t Daniel Deronda

010 ## no 00050348
024 7# $a [ISTC number/code] $2 istc
100 10 $a Rowling, J. K. $t Harry Potter and the Chamber of Secrets. $l Hebrew

3. PROPOSED CHANGES

Define Field 024 (Other Standard Identifier) in the MARC 21 Authority Format:

024 Other Standard Identifier (R)

This field contains a standard number or code associated with the entity named in the 1xx field. It cannot be accommodated in other standard number fields (i.e., field 020 (International Standard Book Number), 022 (International Standard Serial Number)). The source of the standard number or code is identified in subfield $2. The subfields in this field are defined for consistency with field 020 in the MARC 21 Format for Bibliographic Data.

• List of Proposals
• MARC Home Page
• Library of Congress Home Page