The Library of Congress >> Especially
for Librarians and Archivists >> StandardsThe Library of Congress >> Especially
for Librarians and Archivists >> Standards
HOME >> MARC Development >> Discussion Paper List
DATE: May 25, 2023
REVISED:
NAME: Adding Subfields $0, $1, and $5 to Linking Fields 76X-78X in the MARC 21 Bibliographic Format
SOURCE: OCLC
SUMMARY: This paper proposes adding subfields $0 (Authority record control number or standard number), $1 (Real World Object URI), and $5 (Institution to which field applies) in linking entry fields 760 (Main Series Entry), 762 (Subseries Entry), 765 (Original Language Entry), 767 (Translation Entry), 770 (Supplement/Special Issue Entry), 772 (Supplement Parent Entry), 773 (Host Item Entry), 774 (Constitute Unity Entry), 775 (Other edition), 776 (Additional Physical Form), 777 (Issued With Entry), 780 (Preceding Entry), 785 (Succeeding Entry), 786 (Data Source Entry), and 787 (Other Relationship Entry), and 788 (Parallel Description in Another Language of Cataloging) in the MARC 21 Bibliographic Format.
KEYWORDS: Linking Entry and Description fields (BD); Fields 76X-78X (BD); Real World Object URI (BD); Uniform Resource Identifier (BD); Authority record control number or standard number (BD); Institution to which field applies (BD); Subfield $0, in fields 76X-78X (BD); Subfield $1, in fields 76X-78X (BD); Subfield $5, in fields 76X-78X (BD)
RELATED: 2010-06; 2016-DP04; 2016-DP17; 2016-DP19; 2017-08; 2019-03; 2020-FT02; 2020-FT03; 2021-04
STATUS/COMMENTS:
05/25/23 – Made available to the MARC community for discussion.
06/29/23 – Results of MARC Advisory Committee discussion: MAC agreed that the addition of subfield $5 in the linking entry fields should be in its own paper and the number of fields should be reduced to those that have actual use cases. OCLC and RBMS will work together on a subfield $5 proposal that will include a smaller number linking entry fields which have real use cases in the archival and special collections community. For the subfield $0 and $1 in the linking entry fields there was no agreed upon approach on how to include URIs in these fields. The complexities behind the linking entry fields that contain several pieces of information make it difficult to decide on what type of URI should go in the linking entry field in the first place. OCLC will reach out to user communities like CONSER who are frequent users of the linking entry fields to get their feedback on what needs consideration for adding URIs in these fields. Subfield $5 will return as a separate paper, likely a proposal. OCLC will follow up the subfield $0/$1 content of this paper with likely another discussion paper.
Subfields $0 (Authority record control number or standard number), $1 (Real World Object URI), and $5 (Institution to which field applies) are currently defined in many MARC fields used for bibliographic description. Adding subfields $0 and $1 would be consistent with other fields and support linked data. OCLC is currently working on a conversion of BIBFRAME entities into MARC records which have linking fields with URIs that can be rendered to create the information found in the linking fields. We would need subfields $0 and $1 to be valid in the MARC linking fields to make use of these URIs.
The PCC URI Task Group on URIs in MARC explained why linking entry fields were not included in its MARC $0 and $1 proposals in its answer to question 21 of the URI FAQs document:
"76X-78X linking entry fields tend to be associated with instance or manifestation data. While there is no reason instances or manifestations should not have RDF representations that could be linked in $0 (or $1), it is not clear that stable sources exist yet for these data. The task group therefore gave enhancements to these fields a lower priority than its other proposals. ... it is open to use cases that may justify proposals affecting the 76X-78X fields."
This document was issued in September 2018, and the linked data landscape has changed greatly since then. There are now more stable RDF representations for works, expressions, and manifestations (called "instances" in BIBFRAME) in sources such as VIAF (Virtual International Authority File), Wikidata, and id.loc.gov. We believe it is time to include subfields $0 and $1 in the linking entry fields. Adding subfields $0 and $1 also provides more MARC support for the identifier and IRI recording methods in Official RDA.
We also recommend subfield $5 be considered for inclusion in selected linking fields. OCLC encountered a situation where a member library reported WorldCat records that had what seemed to be a local collection title in the 773 (Host item entry) field. After further investigation, we found several records that used this field for local collections. As there is no subfield $5 in the field to indicate the collection is specific to one institution, we were required to move the local collection name to a 710 field where subfield $5 can be used. Subfield $5 would allow agencies to use the linking fields like the 773 for the unique resources found in their archives and special collections. Subfield $5 is widely defined in MARC Bibliographic format fields, including fields 700-711, and 730, which record the resource's relationship to another entity. The linking entry fields serve a similar function by recording a resource's relationship to another resource.
2.1.1. Subfield $0
MARC Proposal 2017-08 added subfield $0 to several MARC fields including the 700-711, 730, and 751 in the Bibliographic format. Subfield $0 in the linking fields would contain the system control number of the related authority or a standard identifier. These identifiers may be in the form of text or a Uniform Resource Identifier (URI).
2.1.2. Subfield $1}
MARC Proposal 2017-08 also created the new subfield $1 and defined it for several MARC fields. Subfield $1 would contain the URI that identifies the Real World Object (RWO) that is cited in the linking field. Including subfield $1 would help in the machine linking to other sources. Work and manifestation descriptions have now been transformed into RDF by several sources such as BIBFRAME by the Library of Congress at id.loc.gov; Wikidata; VIAF, and OCLC entities.
2.1.3. Subfields $0 and $1 Referents in Linking Entry Fields
As noted in Discussion Paper 2016-DP17, "URIs for relationships and objects of those relationships may be open to misidentification by humans and machines if both types are recorded in the same subfield string." Because linking entry fields may contain all types of metadata information (e.g., work, expression, and manifestation), we have presented three possible options on how subfields $0 and $1 could be associated only with the linking entry field.
This part of the discussion will propose the addition of subfield $5 to all the linking and description fields. Based on the feedback from this discussion paper, OCLC may be submitting two separate proposals for subfields $0 and $1, and the other for subfield $5.
According to the MARC Bibliographic format "Appendix A - Control Subfields", $5 is defined as
"MARC code of the institution or organization that holds the copy to which the data in the field applies. Data in the field may not apply to the universal description of the item or may apply universally to the item but be of interest only to the location cited”.
We think that subfield $5 in the linking fields would be of use to institutions where the resource cited is associated to their local collection only. There are several linking fields where such a scenario would be possible.
We propose that subfield $5 be included in fields 760 (Main Series Entry), 762 (Subseries Entry), 765 (Original Language Entry), 767 (Translation Entry), 770 (Supplement/Special Issue Entry), 772 (Supplement Parent Entry), 773 (Host Item Entry), 774 (Constitute Unity Entry), 775 (Other edition), 776 (Additional Physical Form), 777 (Issued With Entry), 780 (Preceding Entry), 785 (Succeeding Entry), 786 (Data Source Entry), and 787 (Other Relationship Entry) as fields that may be used for resources in archival or special collections.
An example of field 762 can be found for an institution where they have a resource translated by a community or individual, and they would like to include a field 762 pointing to the resource they have cataloged that contains that translation. The translated entry is unique to their institution but may be of interest to others in knowing such a translation exists.
762 08 $i Translated as: $a Fielding, Beth. $s Animal colors. Cherokee. $t Inage anehi tsunalsuhwida. $d Waynesville, N.C. : Early Light, [2012] $z 9780985303709 $w (OCoLC)823937019 $5 NcCuW
A second example can be for local collections where resources have been added for an institution's special collections or archives. The resources added to the local collection may be of interest to others but not applicable to the universal description.
773 0# $t Joseph Brodsky Collection (Columbia University) $5 NNC
A third example can be found for an institution that has done a reproduction of a resource in another format with permission from the copyright owner. Again, the resource cited is applicable only to the cataloging institution, but it may be of interest to others in knowing that the resource has been copied in a different format.
500 ## $a Transferred from VHS to DVD-R by the University Libraries in 2014 with permission of Robert Heller.
775 08 $i Reproduction of (manifestation): $t Basic concepts in mechanics. $d New York : College McGraw-Hill Films, [1988] $w (OCoLC)18401294 $5 ViBlbV
In what probably would be rare circumstances subfield $5 may be associated with linking fields used for serials (fields 780 and 785) when a serial is issued in a manuscript format and there is a unique exemplar held only at one library. It would be possible for such serials to change titles, thus requiring separate bibliographic records connected by these linking fields. Rare serials, like any rare materials, can be prone to loss and destruction over time. It would be possible for only a single run of a serial (or a partial run) to have survived and thus be held at a single library.
Another rare scenario could be the use of subfield $5 for field 777 as this field is used for published resources issued together by definition, but there can be resources like artist's books that may have a single exemplar, held by a single library, containing two separate works (e.g., bound together in a dos-à-dos or tête-bêche binding), for which separate bibliographic records might be created and linked together. This would not be considered local binding; it is binding as issued by the artist.
Field 788 is not included in the paper as subfield $5 already exists in that MARC field.
In fields 76X-78X of the MARC 21 Bibliographic Format, add the following subfields (with the exception of subfield $5 to field 788):
$0 - Authority record control number or standard number (R)
See description of this subfield in Appendix A: Control Subfields.$1 - Real World Object URI (R)
See description of this subfield in Appendix A: Control Subfields.$5 - Institution to which field applies (NR)
See description of this subfield in Appendix A: Control Subfields.
Note: Linking entry fields may contain many types of metadata information and their relationships. We have provided three options in the examples on how different components of the linking entry fields may be associated with subfield $1. We are presenting these options due to how data models like the Library Reference Model (LRM) and content standards such as RDA have presented different entities: work, expression, manifestation, and item (WEMI) which can all be found in linking entry fields. OCLC does prefer option 3 as it would allow any URIs that are related to WEMI to be included in the linking field.
OPTION 1 – Subfields $0 and $1 in the linking entry fields are associated only with the portion of the field that deals with the description of a work (underlining the components of the linking field associated with the work for illustrative purposes), examples that include BIBFRAME URIs (http://id.loc.gov/resources/works …) are understood to relate to a specific BIBFRAME Work.
[Note: Example 2 includes a BIBFRAME hub URI due to it containing field 130 (Main Entry-Uniform Title) in the MARC bibliographic record.]
OPTION 2– Subfields $0 and $1 in the linking entry fields are associated only with the portion of the field that deals with the description of a manifestation (underlining the components of the linking field associated with the manifestation for illustrative purposes), examples that include BIBFRAME URIs (http://id.loc.gov/resources/instance …) are understood to relate to a specific BIBFRAME Instance.
OPTION 3– Subfields $0 and $1 in the linking entry fields are associated with the entire field, examples that include BIBFRAME URIs that have both (http://id.loc.gov/resources/works …) and (http://id.loc.gov/resources/instance ...) are understood to relate to a specific BIBFRAME Work and Instance.
Example 4.1.1
Option 1
780 00 $a United States. Office of Production Management. Bureau of Research and Statistics $t Historical record of the stockpile and public purchase programs $w (DLC) 2022204238 $w (OCoLC)1338246305 $1 https://id.loc.gov/resources/works/8188027
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
780 00 $a United States. Office of Production Management. Bureau of Research and Statistics $t Historical record of the stockpile and public purchase programs $w (DLC) 2022204238 $w (OCoLC)1338246305 $1 https://id.loc.gov/resources/instances/8188027
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
780 00 $a United States. Office of Production Management. Bureau of Research and Statistics $t Historical record of the stockpile and public purchase programs $w (DLC) 2022204238 $w (OCoLC)1338246305 $1 https://id.loc.gov/resources/works/8188027 $1 https://id.loc.gov/resources/instances/8188027
Example 4.1.2
Option 1
787 1# $t Associations unlimited (Online) $g <1998-> $w (DLC)sn 96034036 $w (OCoLC)34147706 $1 https://id.loc.gov/resources/hubs/787cef9e-ea2e-1993-39b4-61b89ae3ecc8
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
787 1# $t Associations unlimited (Online) $g <1998-> $w (DLC)sn 96034036 $w (OCoLC)34147706 $1 https://id.loc.gov/resources/instances/14793979
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
787 1# $t Associations unlimited (Online) $g <1998-> $w (DLC)sn 96034036 $w (OCoLC)34147706 $1 https://id.loc.gov/resources/hubs/787cef9e-ea2e-1993-39b4-61b89ae3ecc8 $1 https://id.loc.gov/resources/instances/14793979
Example 4.1.3.
Option 1
787 1# $t Encyclopedia of associations CD-ROM $x 1070-2318 $w (DLC) 93644451 $w (OCoLC)28299945 $1 https://id.loc.gov/resources/works/11419709
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
787 1# $t Encyclopedia of associations CD-ROM $x 1070-2318 $w (DLC) 93644451 $w (OCoLC)28299945 $1 https://id.loc.gov/resources/instances/11419709
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
787 1# $t Encyclopedia of associations CD-ROM $x 1070-2318 $w (DLC) 93644451 $w (OCoLC)28299945 $1 https://id.loc.gov/resources/works/11419709 $1 https://id.loc.gov/resources/instances/11419709
Example 4.1.4.
Option 1
760 08 $i In series: $t Neuromethods $x 0893-2336 $w (DLC) 92643478 $w (OCoLC)12700508 $0 https://id.loc.gov/authorities/names/n84736046 $1 https://id.loc.gov/resources/works/11403271 $1 http://viaf.org/viaf/185113725 $1 https://www.wikidata.org/wiki/Q53979634
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
760 08 $i In series: $t Neuromethods $x 0893-2336 $w (DLC) 92643478 $w (OCoLC)12700508 $1 https://id.loc.gov/resources/instances/11403271 $1 https://www.wikidata.org/wiki/Q53979634
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
760 08 $i In series: $t Neuromethods $x 0893-2336 $w (DLC) 92643478 $w (OCoLC)12700508 $0 https://id.loc.gov/authorities/names/n84736046 $1 https://id.loc.gov/resources/works/11403271 $1 https://id.loc.gov/resources/instances/11403271 $1 http://viaf.org/viaf/185113725 $1 https://www.wikidata.org/wiki/Q53979634
Example 4.1.5.
Option 1
770 0# $t New York times magazine $x 0028-7822 $w (DLC)sn 78005343 $w (OCoLC)1760221 $1 https://www.wikidata.org/wiki/Q3028269
[Note: Components associated with the work underlined for illustrative purposes]\
Option 2
770 0# $t New York times magazine $x 0028-7822 $w (DLC)sn 78005343 $w (OCoLC)1760221 $1 https://www.wikidata.org/wiki/Q3028269
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
770 0# $t New York times magazine $x 0028-7822 $w (DLC)sn 78005343 $w (OCoLC)1760221 $1 https://www.wikidata.org/wiki/Q3028269
Example 4.1.6.
Option 1
775 0# $t (Old) farmer's almanack (Boston, Mass. : 1848) $x 0078-4516 $w (DLC) 56051603 $w (OCoLC)4769691 $1 https://www.wikidata.org/wiki/Q437765
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
775 0# $t (Old) farmer's almanack (Boston, Mass. : 1848) $x 0078-4516 $w (DLC) 56051603 $w (OCoLC)4769691 $1 https://www.wikidata.org/wiki/Q437765
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
775 0# $t (Old) farmer's almanack (Boston, Mass. : 1848) $x 0078-4516 $w (DLC) 56051603 $w (OCoLC)4769691 $1 https://www.wikidata.org/wiki/Q437765
Example 4.1.7.
Option 1
775 08 $i Motion picture adaptation of (work): $a Oksanen, Sofi, 1977- $t Puhdistus. $d Helsinki : Werner Söderström Osakeyhtiö, [2008] $z 9789510339732 $w (DLC) 2010411502 $w (OCoLC)605064835 $0 https://id.loc.gov/authorities/names/no2015158559 $1 https://id.loc.gov/resources/works/16134342 $1 https://www.wikidata.org/wiki/Q1401127
[Note: Components associated with the work underlined for illustrative purposes]
Option 2
775 08 $i Motion picture adaptation of (work): $a Oksanen, Sofi, 1977- $t Puhdistus. $d Helsinki : Werner Söderström Osakeyhtiö, [2008] $z 9789510339732 $w (DLC) 2010411502 $w (OCoLC)605064835 $1 https://id.loc.gov/resources/instances/16134342 $1 https://www.wikidata.org/wiki/Q1401127
[Note: Components associated with the manifestation underlined for illustrative purposes]
Option 3
775 08 $i Motion picture adaptation of (work): $a Oksanen, Sofi, 1977- $t Puhdistus. $d Helsinki : Werner Söderström Osakeyhtiö, [2008] $z 9789510339732 $w (DLC) 2010411502 $w (OCoLC)605064835 $0 https://id.loc.gov/authorities/names/no2015158559 $1 https://id.loc.gov/resources/works/16134342 $1 https://id.loc.gov/resources/instances/16134342 $1 https://www.wikidata.org/wiki/Q1401127
Example 4.2.1.
773 0# $a Makino, Mamoru, 1930- $t Makino Mamoru Collection on the History of East Asian Film $5 NNC
Example 4.2.2.
774 08 $i Container of (manifestation): $a Rifas, Leonard. $s All-atomic comics. German. $t Atomkomix. $d Bremen : Ulli Jenkins, ©1976 $w (OCoLC)56100026 $5 CU-SC
Example 4.2.3.
776 08 $i Reproduction of (manifestation): $t Carlos Fuentes. $d Los Angeles, Calif. : Lannan Foundation, c1989 $z 1573940186 $w (OCoLC)34179504 $5 OKeU
Including linking information to data in MARC will facilitate the transition to fuller linking in BIBFRAME.
6.1. Do you agree that there is use for subfields $0 and $1 in the linking fields?
6.2. Do you agree that there is use for subfield $5 in the linking fields? If so, does adding subfield $5 in all the linking fields seem appropriate? If yes to either, would it be useful for subfield $5 to return as a separate proposal?
6.3. Which option is preferable for what the subfields $0 and $1 are pointing to (option 1-description of the work, option 2-description of the manifestation, option 3-description of work/expression/manifestation)?
6.4. Should BIBFRAME hub URIs be associated with the work component of the linking entry fields?
6.5. Does the proposed solution meet the needs discussed?
6.6. Are there potential consequences that this paper does not address?
HOME >> MARC Development >> Discussion Paper List
| The Library of Congress >> Especially
for Librarians and Archivists >> Standards (10/31/2023) |
Legal | External Link Disclaimer | Contact Us |