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

MARC Standards

HOME >> MARC Development >> Discussion Paper List


MARC DISCUSSION PAPER NO. 2022-DP05

DATE: December 21, 2021
REVISED:

NAME: Accommodating Subject Relationships to Works and Expressions in the MARC 21 Authority Format

SOURCE: PCC Standing Committee on Standards

SUMMARY: This paper considers ways in which subject relationships to works and expressions can be accommodated in the MARC 21 Authority Format. It explores the possibility of adding a second indicator value 7 and subfield $2 for source of term in 5XX see also from reference fields, as well as options for using a new 3XX subject attribute field or the existing 381 field.

KEYWORDS: Fields 5XX (AD); Fields 3XX (AD); Field 381 (AD); Other Distinguishing Charactersitics of Work or Expression (AD); Subject relationships (AD); Work authority records (AD); Expression authority records (AD); RDA subject elements (AD)

RELATED:

STATUS/COMMENTS:
12/21/2021 – Made available to the MARC community for discussion.

01/27/22 – Results of MARC Advisory Committee discussion: Support for the paper was generally favorable although there were mixed views on which solution to pursue, with several commenting about genre not being applicable at the expression level. The Library of Congress submitted a note of dissent. Their position is that they have made preliminary explorations, through the lens of BIBFRAME development, of migrating title authorities to the Bibliographic format. They would neither support development along the lines proposed in the paper nor implement its changes if they were to pass. Meeting discussion took up the question of choosing between the 5XX and 3XX paths toward an ultimate proposal. Much of this hinged on the definition of "authorized" – whether it meant "supported by an authority record" or "compliant with a particular string encoding scheme". This may ultimately be a policy decision. But given the potential dynamics, they might argue for a "both/and" rather than an "either/or" approach with respect to the 5XX and 3XX question, although expanding the 381 field was disfavored in comparison to a new 3XX field if a 3XX solution is brought to the table. Owing to the Library of Congress's stated position and alternative solution, consensus was not reached. LC, PCC, and possibly the MARC/RDA Working Group will discuss next steps moving forward. The paper's status is to be determined.


Discussion Paper No. 2022-DP05: Accommodating Subject Relationships to Works and Expressions in the Authority Format

1. BACKGROUND

Original RDA included a chapter 23 for general guidelines and instructions on recording relationships between works and subjects. It described three techniques for recording the related subject of a work: identifier, authorized access point, and/or description of the related subject. Appendix M contained a list of relationship designators that could be used in conjunction with the three techniques. Examples include description of (work), commentary on (expression), description of (person), and description of (corporate body).  However, no relationship designators were provided for other kinds of subjects of works such as concepts, objects, or places.

New RDA includes a number of subject relationship elements, including subject, subject agent, subject collective agent, subject corporate body, subject expression, subject family, subject item, subject manifestation, subject nomen, subject person, subject RDA entity, subject timespan, and subject place. There are also narrower elements such as description of work, description of corporate body, analysis of expression, and commentary on work. Genre/form relationships are also included, in elements such as category of work and category of expression.

Because subjects are relationship elements to works, it is appropriate to include them in work descriptions.  In an ideal, linked data world, the subjects of a work and the form(s) of a work would only need to be recorded once, in a work description.  They would then automatically be associated with any expressions manifested of the work that a library held.  Subject and/or genre terms appropriate to only one or more expressions would be included in those expression descriptions and would be associated with all manifestations of those particular expressions.

In MARC name authority records subject and genre/form relationships to works and expressions can be recorded in 5XX fields. The relationship element can be recorded in subfield $i as a label and/or in subfield $4 as a code or URI. Examples:

130 #0 $a Botticelli (Motion picture)
500 0# $w r $i Subject person: $a Botticelli, Sandro, $d 1444 or 1445-1510 $4 http://rdaregistry.info/Elements/w/P10261
     [A documentary film]

100 1# $a Bassett, Arthur R. $t Jesus' sermon to the Nephites
500 0# $w r $i Description of person: $a Jesus Christ $4 http://rdaregistry.info/Elements/w/P10325
530 #0 $w r $i Analysis of work: $a Book of Mormon. $p Nephi, 3rd $4http://rdaregistry.info/Elements/w/P10140

100 1# $a Alvord, Samuel E. $t Alvord's history of Noble County, Indiana
380 ## $a History $2 marcgt
551 ## $w r $i Subject place: $a Noble County (Ind.) $4 http://rdaregistry.info/Elements/w/P10321

However, current PCC NACO policy is that entities recorded in 5XX authority fields must be established in the same authority file as the entity described by the record.  For the LC/NACO authority file, that means that only agents (persons, families, corporate bodies), some kinds of places, and works and expressions may be recorded as subjects in a 5XX field.

Some subject relationships can already be recorded in existing 3XX attribute fields.  For example, for a place that is the subject of work, field 370 could be utilized instead of field 551:

100 1# $a Alvord, Samuel E. $t Alvord's history of Noble County, Indiana
370 ## $i Subject place: $f Noble County (Ind.) $4 http://rdaregistry.info/Elements/w/P10321 $0 http://id.loc.gov/authorities/names/n82070505

Entities recorded in 3XX fields do not have to come from within the NAF. The following subject relationship can also be recorded in field 370:

100 1# $a Carroll, Raymond. $t Complete illustrated map and guidebook to Central Park
370 ## $i Subject place: $f Central Park (New York, N.Y.) $2 lcsh $4 http://rdaregistry.info/Elements/w/P10321 $0 http://id.loc.gov/authorities/subjects/sh85021920

However, many subjects do not fit comfortably into any existing 3XX field (e.g., a person who is the subject of a work; a topical term that is not any kind of RDA entity). Other existing 3XX fields currently lack subfields $i and $4 that would be needed to employ them to record subject relationships (e.g., fields 373 and 381). RDA defines subjects as relationship elements rather than as attributes. Relationships in MARC authorities are typically recorded in the 5XX block.

2. DISCUSSION

The RDA element subject is defined as "A topic that a work is about."  The element has the domain of Work, but no range, allowing it to be used for any kind of subject.  For subjects that are RDA entities, RDA instructs catalogers to use the appropriate element subtype for a subject relationship for the entity, such as subject person, subject family, subject place, and subject work.

In the MARC 21 Authority Format, there is currently no method for specifying that a term in name authority 5XX fields was taken from a source external to the LC/NACO authority file.  This may preclude catalogers from recording in 5XX fields the topical subjects of works and the categories of works and expressions using terms from LCSH, LCGFT, or any other controlled subject or genre/form vocabulary.

In order to allow recording subject headings and genre/form terms in 5XX fields of work and expression authority records, it would be desirable to be able to indicate the source of the term. This could be accommodated by the addition of a second indicator value 7 and subfield $2, a technique used elsewhere in MARC, such as in the 6XX fields of the Bibliographic format and in the 7XX linking entry fields of the Authority format.  The second indicator value in 5XX fields of the Authority format is currently undefined.

In addition to the solution above that would allow controlled terms from outside the LC/NACO authority file to be used in 5XX fields, two other methods could be employed:

  1. Establishing a new 3XX field specifically for subjects.
  2. Utilizing the existing 381 field (Other Distinguishing Characteristics of Work or Expression) by establishing subfields $i (Relationship information) and $4 (Relationship)

Note that recording subject relationships in 5XX and 3XX fields are not necessarily mutually exclusive, depending on the limitations imposed in MARC or by community practices for using the 5XX fields.

3. PROPOSED CHANGES

One or more of the following options would enable the recording of RDA subject relationships in work and expression authority records.

3.1. OPTION 1: Changes to 2nd indicator and addition of new subfield $2 in 5XX fields

In the MARC 21 Authority Format in all 5XX fields listed below, redefine the label of the second indicator from "Undefined" to "Thesaurus."  Redefine the meaning of second indicator value of # (blank) from "Undefined" to "Unspecified." Define a second indicator value 7, with meaning "Source specified in subfield $2" and define subfield $2 for the source of heading or term.

In the following fields:

500 - See Also From Tracing - Personal Name (R) 
510 - See Also From Tracing - Corporate Name (R)  
511 - See Also From Tracing - Meeting Name (R)
530 - See Also From Tracing - Uniform Title (R)   
547 - See Also From Tracing - Named Event (R)   
548 - See Also From Tracing - Chronological Term (R)   
550 - See Also From Tracing - Topical Term (R)  
551 - See Also From Tracing - Geographic Name (R)   
555 - See Also From Tracing - Genre/Form Term (R)   
562 - See Also From Tracing - Medium of Performance Term (R)   
580 - See Also From Tracing - General Subdivision (R)   
581 - See Also From Tracing - Geographic Subdivision (R)   
582 - See Also From Tracing - Chronological Subdivision (R)  
585 - See Also From Tracing - Form Subdivision (R)

make the following changes (new additions in underlined bold text):

Second Indicator
Undefined Thesaurus
# – Undefined Unspecified
7 – Source specified in subfield $2

Subfield Codes
$2 - Source of heading or term (NR)

3.2. OPTION 2: Define a new 3XX field

Define a new 3XX field for subjects, similar to the 380 field in which the RDA elements Category of work (formerly, Form of work) and Category of expression can be recorded. The 35X block is available, as are most fields in the 36X block except 360 and 368. Within the 37X and 38X blocks, only 379 and 389 are available (387 has been proposed as a possible field for Representative expression in Proposal No. 2022-04).  Since the 38X block is used for attributes of works and expressions, it might be best to define a new field 389, or perhaps expand into the 39X block. A new 379 field, immediately preceding the 380, might also be ideal. However, the MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media states "In general, any tag containing the character 9 is reserved for local implementation within the block structure." Unless the "in general" condition can be disregarded, it seems that a new field in the 36X block would be the most appropriate to employ.

Define a new 3XX field as follows:

3XX - Subject of Work or Expression (R)

First Indicator
Undefined
# - Undefined

Second Indicator
Undefined
# - Undefined

Subfield Codes
$a - Subject of work or expression (R)
$i - Relationship information (R)
$0 - Authority record control number or standard number (R)
$1 - Real World Object URI (R)
$2 - Source of term (NR)
$3 - Materials specified (NR)
$4 - Relationship (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

FIELD DEFINITION AND SCOPE
A subject heading or other term describing what a work or expression is about.

Multiple headings or terms from the same source vocabulary may be recorded in the same field in separate occurrences of subfield $a (Subject of work or expression). Headings or terms from different source vocabularies are recorded in separate occurrences of the field.

Note: The subfield codes shown above are modeled on other 3XX fields. PCC practice for recording LCSH subject headings strings in these fields is to replace the subfield coding for any subdivisions with two hyphens and close up the spaces between the main heading and subdivisions. For example, for a person whose field of activity is the history of Japan, a NACO cataloger would record: 372 ## $a Japan--History $2 lcsh

An alternative to having just subfield $a available to record a string could be to replicate the structure in other 5XX fields by adding subfields $v, $x, $y, and $z to the new 3XX field proposed above (additions in underlined bold text):

3XX - Subject of Work or Expression (R)

First Indicator
Undefined
# - Undefined

Second Indicator
Undefined
# - Undefined

Subfield Codes
$a - Subject of work or expression (R)
$i - Relationship information (R)
$v - Form subdivision (R)
$x - General subdivision (R)
$y - Chronological subdivision (R)
$z - Geographic subdivision (R)
$0 - Authority record control number or standard number (R)
$1 - Real World Object URI (R)
$2 - Source of term (NR)
$3 - Materials specified (NR)
$4 - Relationship (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

3.3. OPTION 3: Add new subfields to field 381

Define subfields $i (Relationship information) and $4 (Relationship) in existing MARC Authority field 381 (Other Distinguishing Characteristics of Work or Expression). This field could then be used to record subject relationships. Adding subfield $3 for materials specified would probably also be useful.

Add new subfields $i, $4, and $3 (in underlined bold text) to field 381 as follows:

381 - Other Distinguishing Characteristics of Work or Expression (R)

First Indicator
Undefined
# - Undefined

Second Indicator
Undefined
# - Undefined

Subfield Codes
$a - Other distinguishing characteristic (R)
$i - Relationship information (R)
$u - Uniform Resource Identifier (R)
$v - Source of information (R)
$0 - Authority record control number or standard number (R)
$1 - Real World Object URI (R)
$2 - Source of term (NR)
$3 - Materials specified (NR)
$4 - Relationship (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

4. EXAMPLES

4.1. OPTION 1: Changes to 2nd indicator and addition of new subfield $2 in 5XX fields

Note: All examples include URIs for the RDA relationship element in subfield $4 and URIs for the authority record for a subject in $0. The $4 URI shown in the examples is from the constrained work properties listed in the RDA Registry. An alternative that some communities might prefer would be to use the unconstrained property rdau:P60805.  Inclusion of URIs in authority records is optional and would be decided by community practices. The final example shows that the subfield $2 code "naf" could be used to specify entities in the LC/NACO Authority File, should this be considered desirable. Alternatively, a community (e.g., NACO) could decide that specification of the source is not necessary when referring to another entity within the same source as the record itself.

Example 4.1.1.

100 1# $a Clinton, Chelsea. $t Don't let them disappear
550 #7 $w r $i Subject: $a Endangered species $2 lcshac $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/childrensSubjects/sj2021050059
550 #7 $w r $i Subject: $a Rare animals $2 lcshac $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/childrensSubjects/sj96006043
555 #7 $w r $i Category of work: $a Picture books $2 lcgft $4 http://rdaregistry.info/Elements/w/P10004 $0 http://id.loc.gov/authorities/genreForms/gf2016026096

Example 4.1.2.

100 1# $a Tauranac, John, $d 1939- $t Empire State Building
510 27 $w r $i Subject: $a Empire State Building (New York, N.Y.) $2 lcsh $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh85042848
550 #7 $w r $i Subject: $a Architecture $z New York (State) $z New York $2 lcsh $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh2007101284
551 #7 $w r $i Subject: $a New York (N.Y.) $x Buildings, structures, etc. $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh2008116320

Example 4.1.3.

100 1# $a Casanova, Julián. $t República y guerra civil
551 #7 $w r $i Subject: $a Spain $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1204303
547 #7 $w r $i Subject: $a Spanish Civil War $c (Spain : $d 1936-1939) $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1352321
548 #7 $w r $i Subject: $a 1931-1939 $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1355883
555 #7 $w r $i Category of work: $a History $2 fast $4 http://rdaregistry.info/Elements/w/P10004 $0 http://id.worldcat.org/fast/1411628

Example 4.1.4.

100 1# $a Casanova, Julián. $t República y guerra civil. $l English
400 1# $a Casanova, Julián. $t Spanish Republic and Civil War
555 #7 $w r $i Category of expression: $a Translations $2 fast $4 http://rdaregistry.info/Elements/e/P20331 $0 http://id.worldcat.org/fast/1423791
            [Subjects and category of work only recorded in the work authority record]

Example 4.1.5.

100 1# $a Frank, Anne, $d 1929-1945. $t Achterhuis. $l English $s (Massotty). $h Spoken word $s (Bonham Carter)
555 #7 $w r $i Category of expression: $a Translations $2 fast $4 http://rdaregistry.info/Elements/e/P20331 $0 http://id.worldcat.org/fast/1423791
555 #7 $w r $i Category of expression: $a Audiobooks $2 lcgft $4 http://rdaregistry.info/Elements/e/P20331 $0 http://id.loc.gov/authorities/genreForms/gf2011026063
            [Subjects and category of work only recorded in the work authority record]

Example 4.1.6.

100 1# $a Bassett, Arthur R. $t Jesus' sermon to the Nephites
500 0# $w r $i Description of person: $a Jesus Christ $2 naf $4 http://rdaregistry.info/Elements/w/P10325 $0 http://id.loc.gov/authorities/names/n79084784
530 #0 $w r $i Analysis of work: $a Book of Mormon. $p Nephi, 3rd $2 naf $4 http://rdaregistry.info/Elements/w/P10140 $0 http://id.loc.gov/authorities/names/nr94020118

4.2. OPTION 2: Define a new 3XX field

Note: When the subject relationship corresponds to the general definition of the field (such as in the RDA relationship element "Subject"), subfields $i and $4 are not necessary. They have been left out in the examples where a general subject relationship is being recorded. When a more specific type of subject relationship is needed, such as shown in example 4.2.4., subfields $i and $4 could be employed.

Example 4.2.1.

100 1# $a Clinton, Chelsea. $t Don't let them disappear
3XX ## $a Endangered species $2 lcshac $0 http://id.loc.gov/authorities/childrensSubjects/sj2021050059
3XX ## $a Rare animals $2 lcshac $0 http://id.loc.gov/authorities/childrensSubjects/sj96006043
380 ## $a Picture books $2 lcgft $0 http://id.loc.gov/authorities/genreForms/gf2016026096

Example 4.2.2.

100 1# $a Tauranac, John, $d 1939- $t Empire State Building
3XX ## $a Empire State Building (New York, N.Y.) $2 lcsh $0 http://id.loc.gov/authorities/subjects/sh85042848
3XX ## $a Architecture--New York (State)--New York $2 lcsh $0 http://id.loc.gov/authorities/subjects/sh2007101284
3XX ## $a New York (N.Y.)--Buildings, structures, etc. $0 http://id.loc.gov/authorities/subjects/sh2008116320

Example 4.2.3.

100 1# $a Casanova, Julián. $t República y guerra civil
3XX ## $a Spain $2 fast $0 http://id.worldcat.org/fast/1204303
3XX ## $a Spanish Civil War (Spain : 1936-1939) $2 fast $0 http://id.worldcat.org/fast/1352321
3XX ## $a 1931-1939 $2 fast $0 http://id.worldcat.org/fast/1355883
380 ## $a History $2 fast $0 http://id.worldcat.org/fast/1411628

Example 4.2.4.

100 1# $a Bassett, Arthur R. $t Jesus' sermon to the Nephites
3XX ## $i Description of person: $a Jesus Christ $2 naf $4 http://rdaregistry.info/Elements/w/P10325 $0 http://id.loc.gov/authorities/names/n79084784
3XX ## $i Analysis of work: $a Book of Mormon. $p Nephi, 3rd $2 naf $4 http://rdaregistry.info/Elements/w/P10140 $0 http://id.loc.gov/authorities/names/nr94020118

Example 4.2.5.

Alternative example to 4.2.2. with additional subfields for heading strings:

100 1# $a Tauranac, John, $d 1939- $t Empire State Building
3XX ## $a Empire State Building (New York, N.Y.) $2 lcsh $0 http://id.loc.gov/authorities/subjects/sh85042848
3XX ## $a Architecture $z New York (State) $z New York $2 lcsh $0 http://id.loc.gov/authorities/subjects/sh2007101284
3XX ## $a New York (N.Y.) $x Buildings, structures, etc. $0 http://id.loc.gov/authorities/subjects/sh2008116320

4.3. OPTION 3: Add new subfields ($i and $4) to field 381

In these examples, $i is employed to indicate that the other distinguishing characteristic recorded is a subject relationship.

Example 4.3.1.

100 1# $a Clinton, Chelsea. $t Don't let them disappear
380 ## $a Picture books $2 lcgft $0 http://id.loc.gov/authorities/genreForms/gf2016026096
381 ## $i Subject: $a Endangered species $2 lcshac $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/childrensSubjects/sj2021050059
381 ## $i Subject: $a Rare animals $2 lcshac $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/childrensSubjects/sj96006043

Example 4.3.2.

100 1# $a Tauranac, John, $d 1939- $t Empire State Building
381 ## $i Subject: $a Empire State Building (New York, N.Y.) $2 lcsh $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh85042848
381 ## $i Subject: $a Architecture--New York (State)--New York $2 lcsh $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh2007101284
381 ## $i Subject: $a New York (N.Y.)--Buildings, structures, etc. $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.loc.gov/authorities/subjects/sh2008116320

Example 4.3.3.

100 1# $a Casanova, Julián. $t República y guerra civil
380 ## $a History $2 fast $0 http://id.worldcat.org/fast/1411628
381 ## $i Subject: $a Spain $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1204303
381 ## $i Subject: $a Spanish Civil War (Spain : 1936-1939) $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1352321
381 ## $i Subject: $a 1931-1939 $2 fast $4 http://rdaregistry.info/Elements/w/P10256 $0 http://id.worldcat.org/fast/1355883

Example 4.3.4.

100 1# $a Bassett, Arthur R. $t Jesus' sermon to the Nephites
381 ## $i Description of person: $a Jesus Christ $2 naf $4 http://rdaregistry.info/Elements/w/P10325 $0 http://id.loc.gov/authorities/names/n79084784
381 ## $i Analysis of work: $a Book of Mormon. $p Nephi, 3rd $2 naf $4 http://rdaregistry.info/Elements/w/P10140 $0 http://id.loc.gov/authorities/names/nr94020118

5. BIBFRAME DISCUSSION

BIBFRAME accommodates subject relationships for all of BIBFRAME resources: Hubs, Works, Instances.

6. QUESTIONS FOR DISCUSSION

6.1.  Should the MARC Authority Format be revised so that any kind of subject or genre/form relationship to work or expression can be recorded in work and expression authority records?

6.2.  Is there a preference for only one of the options? Or could both option 1 and either option 2 or option 3 be usefully implemented?  Of options 2 and 3, is there a preference for one over the other?

6.3.  If option 1 is one of the preferred options, instead of just adding second indicator value 7, would it be preferable to include all of the defined values that are used in the 7XX linking entry fields?

0 - Library of Congress Subject Headings
1 - LC subject headings for children's literature
2 - Medical Subject Headings
3 - National Agricultural Library subject authority file
4 - Source not specified
5 - Canadian Subject Headings
6 - Répertoire de vedettes-matière
7 - Source specified in subfield $2

6.4.  If option 1 is one of the preferred options, does MARC require that a subject string be established in a subject authority record in order to use it in a 5XX field?  This is not a requirement in 6XX fields in bibliographic records. For example, 6XX second indicator value 0 means "Heading conforms to and is appropriate for use in the Library of Congress Subject Headings (LCSH) and the Name authority files that are maintained by the Library of Congress." There is no requirement that every subject string constructed and recorded in a bibliographic record be authorized by an authority record.  Is there such a requirement for authority 5XX fields?

Consider the following example of an LCSH heading constructed using a free-floating subdivision. In the absence of a subject authority record for Sea birds--Hawaii, is the following see also from reference permitted?:

100 1# $a Shallenberger, Robert J. $t Hawaiian birds of the sea
550 #7 $w r $i Subject: $a Sea birds $z Hawaii $2 lcsh $4 http://rdaregistry.info/Elements/w/P10256
    The subject string Sea birds--Hawaii is a valid LCSH string but there is no authority record
   for it

Note that if MAC determines that an unestablished but properly constructed string such as the example above is not permissible in a 5XX field, it could go into a 3XX field used for subjects.  Is this a good use case for allowing multiple options (5XX when established, 3XX when uncontrolled)?

6.5.1.  If option 2 is employed, is there a need to distinguish between subjects related to work and subjects related to expression?  If there is a need, what would be the better way to accomplish this, separate subfields ($a for work, $b for expression) or indicator values?

6.5.2. Under option 2 would there be any benefit to including subfields $v, $x, $y, and $z in the new 3XX field?

6.6.  Should field 380 (Form of Work) be revised to "Form of Work or Expression" to allow recording of genre/form terms applicable to expressions (RDA's category of expression)? Would there be any benefit to changing the field name to be in sync with RDA, i.e., rename it "Category of Work or Expression"?

6.7. Is there anything else that should be taken into account?


HOME >> MARC Development >> Discussion Paper List

The Library of Congress >> Especially for Librarians and Archivists >> Standards
(05/17/2022)
Legal | External Link Disclaimer Contact Us