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

MARC Standards

HOME >> MARC Development >> Proposals List


MARC PROPOSAL NO. 2020-02

DATE: December 20, 2019
REVISED:

NAME: Adding Subfield $0 to Fields 310 and 321 in the MARC 21 Bibliographic Format

SOURCE: Network Development and MARC Standards Office (NDMSO), Library of Congress

SUMMARY: This paper proposes adding subfield $0 (Authority record control number or standard number) to fields in the MARC 21 Bibliographic Format that currently do not have subfield $0 defined: Field 310 (Current Publication Frequency) and Field 321 (Former Publication Frequency).

KEYWORDS: Authority record control number or standard number (BD); Subfield $0, in field 310 (BD); Current Publication Frequency (BD); Subfield $0, in field 321 (BD); Former Publication Frequency (BD)

RELATED: 2019-DP05; 2017-08; 2016-DP19; 2010-06

STATUS/COMMENTS:
12/20/19 – Made available to the MARC community for discussion.

01/26/20 – Results of MARC Advisory Committee discussion: Approved. BIBFRAME mapping will be corrected to support the distinction between current and former frequency, pending an amendment to current BIBFRAME to MARC conversion rules.

04/28/20 - Results of MARC Steering Group review - Agreed with the MAC decision.


Proposal No. 2020-2: Adding Subfield $0 to Fields 310 and 321

1. BACKGROUND

As a part of the BIBFRAME cataloging pilot at the Library of Congress, the development team has tried to introduce data entry efficiencies into the BIBFRAME editor software. Menu options that are tied to a controlled vocabulary have been widely used to capture such information as RDA Content/Media/Carrier Type, MARC relator codes, and headings from the LCNAF, LCSH, LCGFT and LCMPT files. The vocabulary lists have been constructed from term lists defined in the RDA Registry, term lists defined in controlled MARC fields, or a combination of the two. The URIs for these terms are added to the BIBFRAME data during the MARC to BIBFRAME conversion process.

NDMSO is now evaluating the conversion of BIBFRAME data to MARC. This analysis has shown that some MARC fields which contain data from a controlled vocabulary do not have a place for the standard identifier or URI of the term.  There are also some variable fields with controlled terms that do not have $0 defined yet.

2. DISCUSSION

The scope of subfield $0 was broadened to include the recording of standard numbers and identifiers in Proposal 2010-06, and Proposals 2016-DP19 and 2017-08 added subfield $0 to several MARC fields.

The preceding discussion paper (2019-DP05) proposed the expansion of subfield $0 to MARC fields 310, 321, and 521. Following the discussion during the meeting of the MARC Advisory Committee in June 2019, it was decided to drop field 521 from this proposal since intended audience characteristics with URIs can be recorded in MARC field 385.

To remain consistent with other fields, $1 (Real World Object URI) and $2 (Source) have also been added. The utility of $1 in this context was questioned during the LC review, along with the conflict of repeatability vs. non-repeatability between $0 and $1.

Adding subfields for identifiers also means that field 310 should be changed from non-repeatable to repeatable to accommodate identifiers from different sources.

Some note fields permit the storage of URIs in $u, as in field 520 (Summary, Etc.) However, this URI provides electronic access to descriptive data in the field. The data in $0 is a link to the related authority record or standard identifier.

3. PROPOSED CHANGES AND EXAMPLES

In fields 310 and 321 of the MARC 21 Bibliographic Format, add the following subfields (underlined):

3.1. Field 310


310 – Current Publication Frequency (NR) (R)

Subfield Codes
$a – Current publication frequency (NR)
$b – Date of current publication frequency (NR)
$0 – Authority record control number or standard number (NR)
$1 – Real World Object URI (R)
$2 – Source (NR)
$6 – Linkage (NR)
$8 – Field link and sequence number (R)

Examples:

310 ## $a
Monthly (except July and Aug.)

310 ## $a Updated irregularly, $b 2001-

310 ## $a Monthly $0 http://id.loc.gov/vocabulary/frequencies/mon

310 ## $a Continuously updated $0 http://id.loc.gov/vocabulary/frequencies/con

310 ## $a Bimonthly, $b 1958- $0 http://id.loc.gov/vocabulary/frequencies/bmn

[Note: In the first two examples, a URI in subfield $0 is not provided as the text of the note does not match the label of the URI.]

Also expressed in MARC 008/continuing resources, byte 18 Frequency

In BIBFRAME Instance, bf:frequency (property), bf:Frequency (Class)

Term list: http://id.loc.gov/vocabulary/frequencies.html
This list is based on RDA with augmentations from MARC

3.2. Field 321


321 – Former Publication Frequency (R)

Subfield Codes
$a – Former publication frequency (NR)
$b – Date of former publication frequency (NR)
$0 – Authority record control number or standard number (NR)
$1 – Real World Object URI (R)
$2 – Source (NR)
$6 – Linkage (NR)
$8 – Field link and sequence number (R)

Examples:

321 ## $a Frequency varies, $b 1966-1983

321 ## $a Ten no. a year, $b 2002-2004

321 ## $a Annual, $b 1993-2005 $0 http://id.loc.gov/vocabulary/frequencies/ann

321 ## $a Biennial, $b 1981/1982 $0 http://id.loc.gov/vocabulary/frequencies/bin

[Note: In the first two examples, a URI in subfield $0 is not provided as the text of the note does not match the label of the URI.]

In BIBFRAME Instance, bf:frequency (property), bf:Frequency (Class)

Term list: http://id.loc.gov/vocabulary/frequencies.html
This list is based on RDA with augmentations from MARC

4. BIBFRAME DISCUSSION

Including $0 in the above fields will enable a smooth conversion between BIBFRAME data and  MARC data, since URIs added within a BIBFRAME editor, or by a MARC to BIBFRAME data conversion, will be preserved.

5. SUMMARY OF PROPOSED CHANGES

In the MARC 21 Bibliographic Format:

5.1. Make field 310 (Current Publication Frequency) repeatable.

5.2. Define the following subfields in In fields 310 (Current Publication Frequency) and 321 (Former Publication Frequency):

$0 - Authority record control number or standard number (NR)
$1 - Real World Object URI (R)
$2 - Source (NR)


HOME >> MARC Development >> Proposals List

The Library of Congress >> Especially for Librarians and Archivists >> Standards
(04/28/2020)
Legal | External Link Disclaimer Contact Us