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

MARC Standards

HOME >> MARC Development >> Proposals List


MARC PROPOSAL NO. 2022-FT01

MARC FAST-TRACK PROPOSAL

DATE: January 26, 2022
REVISED:

NAME: Adding Subfields $i and $4 to Field 373 of the MARC 21 Authority Format

SOURCE: PCC Standing Committee on Standards

SUMMARY: This paper proposes adding subfields $i (Relationship information) and $4 (Relationship) to field 373 (Associated Group) of the MARC 21 Authority Format.

KEYWORDS: Field 373 (AD); Associated Group (AD); Subfield $i, in field 373 (AD); Relationship information (AD); Subfield $4, in field 373 (AD); Relationship (AD); Affiliation (AD); Associated institution (AD); RDA

RELATED: 2022-DP04; 2017-02; 2017-03

STATUS/COMMENTS:
01/26/22 – Discussion Paper 2022-DP04 was converted to a MARC Fast-Track proposal at MAC Midwinter meeting.

05/06/22 – Submitted to the MARC Steering Group for consideration as a MARC Fast-Track proposal.

05/19/22 – Results of MARC Steering Group review - Approved.


Proposal No. 2022-FT01: Adding Subfields $i and $4 to Field 373

1. BACKGROUND

Authority field 373 (Associated Group) was created to accommodate recording of the original RDA attributes Affiliation (RDA 9.13) and Associated Institution (RDA 11.5).  In new RDA, these attributes are now represented by several relationship elements, including person member of corporate body of, related corporate body of person, corporate body member of corporate body of, and related corporate body of corporate body.  Relationships to corporate bodies may be recorded in MARC authority records in either field 373 or fields 510 (See Also From Tracing - Corporate Name) and 511 (See Also From Tracing - Meeting Name).  Field 373 can be used when the related body is not established in the LC/NACO Authority File, whereas entities recorded in 5XX fields must always be established.

2. DISCUSSION

When a 5XX field is used to record a relationship, subfields $i and $4 are available to record a label for the type of relationship and a URI for that relationship.  However, these subfields are not currently defined for field 373.  It would be desirable to add them to the field so that the specific nature of the relationship can be recorded.  This is especially useful when the entity recorded is not established in the LC/NAF, and therefore the relationship cannot be recorded in a 5XX field (as in many of the examples below that lack subfield $2 in the 373 field).  In situations where an associated institution is not established in the LC/NAF, if there are real-world object URIs for the entity, such as from Wikidata, they can be included in subfield $1, facilitating linked data applications, as also shown in some of the examples.  In addition, the 373 field can accommodate recording of applicable start and ending dates in subfields $s and $t, metadata that cannot be included in 5XX fields.

As in fields 370 and 386 (see Proposal 2017-02 and Proposal 2017-03), multiple relationships to the same entity could be recorded in a single field with repeatable subfields $i/$4, or using repeated fields with a single subfield $i/$4. When URIs are recorded in subfield $4, it would be best to repeat the field. An example showing both methods is included in section 4 below.

Examples of specific types of relationships that could be recorded include membership in an organization, graduation from an educational institution, employment, academic affiliation, and many others. Relationship labels and URIs are available as constrained and unconstrained properties in the RDA Registry, and from other sources such as Wikidata, MARC Relators, and the LC Linked Data Service relationships vocabulary. The examples show a variety of these relationships.

3. PROPOSED CHANGES

In field 373 of the Authority format, define the following subfields:

$i - Relationship information (R)
Designation of a relationship between the associated group recorded in the 373 field and the 1XX entity in the record. This may be an uncontrolled textual phrase or a controlled textual value from a list of relationships.

$4 - Relationship (R)
Code or URI that specifies the relationship from the entity described in the record to the entity referenced in the field.

4. EXAMPLES


4.1.

100 1# $a Ahmed, Fodio
373 ## $i Person member of corporate body of: $a Society of Young Nigerian Writers $4 http://rdaregistry.info/Elements/a/P50095

4.2.

100 1# $a Alender, Katie
373 ## $i Member of: $a International Thriller Writers $4 http://rdaregistry.info/Elements/u/P60648 $1 http://www.wikidata.org/entity/Q12767555

4.3.

100 1# $a Brommel, Angela M., $d 1975-
373 ## $i Graduate of: $a Antioch University Los Angeles $4 http://rdaregistry.info/Elements/a/P50253

4.4.

100 1# $a Abzug, Mark J.
373 ## $i Academic appointment: $a University of Colorado Anschutz Medical Campus. Department of Pediatrics $4 http://www.wikidata.org/entity/P8413

4.5.

100 1# $a Paton, Siobhan, $d 1983-
373 ## $i Participant in: $a Paralympic Games (11th : 2000 : Sydney, N.S.W.) $4 http://www.wikidata.org/entity/P1344 $1 http://www.wikidata.org/entity/Q855688

4.6.

100 1# $a Baker, Leslie Scott, $c Jr.
373 ## $i Employer: $a Andrews University. Press $s 2015 $4 http://rdaregistry.info/Elements/u/P60679 $1 http://www.wikidata.org/entity/Q4759111

4.7.

110 2# $a Byron Society of America
373 ## $i Corporate body member of corporate body of: $a International Association of Byron Societies $4 http://rdaregistry.info/Elements/a/P50230

4.8.

110 2# $a International Association for Cryptologic Research
373 ## $i Sponsored corporate body of corporate body: $a CRYPTO (Conference) $2 naf $4 http://rdaregistry.info/Elements/a/P50009

4.9.

111 2# $a Equal Is Not Enough (Conference) $n (3rd : $d 2015 : $c Antwerp, Belgium)
373 ## $i Organizer: $a Steunpunt Gelijkekansenbeleid $4 http://www.wikidata.org/entity/P664 
373 ## $i Host institution: $a Universiteit Antwerpen $2 naf $4 http://id.loc.gov/entities/relationships/hostinstitution

4.10.

111 2# $a CRYPTO (Conference) $n (41st : $d 2021 : $c Online)
373 ## $i Sponsoring corporate body: $a International Association for Cryptologic Research $2 naf $4 http://rdaregistry.info/Elements/a/P50015

4.11.

111 2# $a Management Procedures for Commercial Whaling Workshop $d (1993 : $c University of British Columbia. Fisheries Centre)
373 ## $i Sponsoring corporate body, $i Host institution: $a University of British Columbia. $2 naf $4 spn $4 his
           [Repeated subfield $i and $4]

4.12.

111 2# $a Management Procedures for Commercial Whaling Workshop $d (1993 : $c University of British Columbia. Fisheries Centre)
373 ## $i Sponsoring corporate body: $a University of British Columbia.$2 naf $4 http://rdaregistry.info/Elements/u/P60451
373 ## $i Host institution: $a University of British Columbia. $2 naf $4 http://rdaregistry.info/Elements/u/P60061
     [Repeated field with relationship URIs]

4.13.

130 #0 $a Night at the museum (Motion picture)
373 ## $i Setting: $a American Museum of Natural History $2 naf $4 https://id.loc.gov/vocabulary/relators/stg

4.14.

151 ## $a Chapleau Cree First Nation
373 ## $i Member of: $a Mushkegowuk Council $4 http://rdaregistry.info/Elements/u/P60648 $1 http://www.wikidata.org/entity/Q6941270

5. BIBFRAME DISCUSSION

Since this discussion paper addresses changes to the MARC21 Authority Format, the MADS ontology and conversion may need to be updated.

6. SUMMARY OF PROPOSED CHANGES

In field 373 (Associated Group) of the MARC 21 Authority Format, define the following subfields:

$i - Relationship information (R)

$4 - Relationship (R)


HOME >> MARC Development >> Proposals List

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