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: December 13, 2016
REVISED:
NAME: Defining Subfields $u, $r and $z in Field 777 of the MARC 21 Bibliographic Format
SOURCE: Canadian Committee on Metadata Exchange (CCM)
SUMMARY: This paper proposes the need for subfields $r (Report number), $u (Standard Technical Report Number) and $z (ISBN) in Field 777 (Issued With Entry) of the MARC 21 Bibliographic Format.
KEYWORDS: Field 777 (BD); Subfield $r, in field 777 (BD); Subfield $u, in field 777 (BD); Subfield $z, in field 777 (BD); Report number (BD); Standard Technical Report Number (BD); International Standard Book Number (BD)
RELATED: 88-1
STATUS/COMMENTS:
12/13/16 – Made available to the MARC community for discussion.
01/22/17 – Results of MARC Advisory Committee discussion: There was general support for the addition of subfields $r $u and $z to field 777 in the Bibliographic format. The existing subfield $i was thought to have sufficient flexibility so no new display constants or indicator values were recommended. This will return as a proposal.
This discussion paper puts forward the idea of defining three subfields that are appropriate for monographs in a field that has traditionally been used for serial to serial relationships, 777 (Issued With Entry). Subfields $r (Report number), $u (Standard Technical Report Number) and $z (ISBN) contain identifiers that are assigned to monographs. The ‘Issued With’ relationship could be appropriate between two monograph descriptions in cases of accompanying material.
Field 777 is one of three fields historically designated for use only on serials. The array of subfields reflects this limitation. The subfield array did not change throughout the format integration work of the 1980s and 1990s. The intention of format integration was expressed in Proposal 88-1, page 2:
For USMARC, the process of format integration would involve the elimination, insofar as possible, of restrictions on data elements that currently make them valid only for specific forms of material.
Subfields $r, $u and $z are defined in linking entry fields, 765, 767, 770, 772, 773, 774, 775, 776, 780, 785, 786 and 787. Subfields $r, $u and $z have not been defined for three linking entry fields, 760, 762 and 777. Perhaps there was no identifiable use-case to justify their addition.
The scenario in which accompanying material is described separately is the inspiration for this Discussion Paper. The changes suggested below would bring Field 777 in alignment with most of the other linking entry fields and allow for the recording of three types of identifiers traditionally associated with monograph resources. The discussion below will look at the concept of ‘issued with’ as defined in the current cataloging content standard Resource Description and Access (RDA). Whether the MARC concept of ‘issued with’ matches the RDA concept may need to be discussed. Consideration may also need to be given to the RDA concept of ‘accompanied by’ instead of ‘issued with.’
Field Definition and Scope:
Information concerning the publication that is separately cataloged but that is issued with or included in the target item (horizontal relationship). When a note is generated from this field, the introductory phrase Issued with: may be generated based on the field tag for display.This field is not used for bound with notes (field 501 (With Note)) that refer to local binding practices nor for component parts (analytical relationships).
The pre-format-integration definition of field 777 specifically mentioned serials. The field was only defined for use in the serials (SE) format to record the entry for publications which are issued with the serial cataloged (horizontal relationship). This field should not be confused with the ‘bound with’ note which refers to local binding practices and is not included in this field. A serial issued with another serial is sometimes referred to as a ‘serial within a serial.’ Over the years, the wording was revised to make it clear that field 777 is for a horizontal, non-hierarchical relationship between two items.
MARBI paper 88-1 (August 28, 1987) continued the discussion of format integration in USMARC and included the background:
At the January 9, 1984 MARBI meeting, the question was again discussed and the following agreement resulted:
In its discussions of format integration, MARBI has agreed upon the following definition of an integrated format: THE USMARC bibliographic formats are considered a single integrated format. Content designation defined therein is valid in any record in which it is appropriate.
While the stated Scope of the field has matured to reflect format integration principles, the array of subfields did not similarly evolve.
It is difficult to justify the prohibition on the use of this field for linking a monograph to another monograph in a post-format integration scenario. The second paragraph of the field definition and scope prohibits the use of this field for analytical relationships. The decision to use field 777, or not, should be a local policy decision. The blanket prohibition on the use of this field for bound-with situations, analytics, or indeed between all monograph records is unnecessary and not in line with current descriptive standards and practices.
A library may choose to create separate bibliographic records for a resource with multiple parts, e.g., a resource issued with another resource, kits containing multiple physical parts, etc. The fact that one part is issued with another part is sufficient to justify using a linking entry. The intellectual relationship between resources that are issued together can be expressed with relationship designators from RDA J.2.5 Accompanying Work Relationships, and J.3.5 Accompanying Expression Relationships. These could be recorded in 777 $i (Relationship information).
RDA relationship designators are available for linking descriptions of resources that are issued together.
J.4.5 Accompanying Manifestation Relationships
accompanied by (manifestation) A manifestation issued with another manifestation, without any relationship to its content. Reciprocal relationship: accompanied by (manifestation)
issued with A manifestation that is issued on the same carrier as the manifestation being described. Reciprocal relationship: issued with
filmed with (manifestation) A manifestation that is issued on the same microform with the manifestation being described. Reciprocal relationship: filmed with (manifestation)
on disc with (manifestation) A manifestation that is issued on the same disc with the manifestation being described. Reciprocal relationship: on disc with (manifestation)
(Resource Description & Access, Appendix J.4.5, accessed on July 11, 2016)
‘Issued with’ can be specified by using either the second indicator # (display constant ‘Issued with’), or the ‘issued with’ designator in subfield $i. Additionally, it may be appropriate and desirable to record multiple subfield $i’s. In RDA Appendix J.4.5, it is noted that the ‘issued with’ designator is to be used for manifestations issued on the same carrier. Manifestations on separate carriers that accompany other manifestations use the ‘accompanied by (manifestation)’ designator.
J.5.5 Accompanying Item Relationships
accompanied by (item) An item brought together with another item after being issued. Reciprocal relationship: accompanied by (item)
bound with An item that has been bound within the same binding as the item being described. Reciprocal relationship: bound with
filmed with (item) An item that is contained on the same microform with the item being described. Reciprocal relationship: filmed with (item)
on disc with (item) An item that is contained on the same disc with the item being described. Reciprocal relationship: on disc with (item)
(Resource Description & Access, Appendix J.5.5, accessed on July 11, 2016)
Two situations are suitable for using field 777 but are currently not possible. In both situations, the resources may be considered to be traditional accompanying material, but for which libraries have chosen to create separate descriptions:
These changes would allow field 777 to be used between monograph records.
Field Definition and Scope:
Information concerning the publication that is separately cataloged but that is issued with or included in the target item (horizontal relationship). When a note is generated from this field, the introductory phrase Issued with: may be generated based on the field tag for display.This field is not used for bound with notes (field 501 (With Note)) that refer to local binding practices nor for component parts (analytical relationships).
3.1. Example of a postcard inserted in a monograph
Current practice:
LDR 01213nkm a2200289 i 4500
001 0005245785
003 CaQMBN
005 20161026093050.0
007 kp#|||
008 160315s2015####qucnnn############knfre##
040 ##$aQMBN$bfre$erda$cQMBN
100 1#$aPigeon,$d1980-$ephotographe.
245 10$aBaz et Didier dans le lit.
264 #1$a[Montréal] :$b[Le Pigeon et Catherine D'Amours],$c[2015]
300 ##$a1 carte postale :$bcouleur ;$c11 x 16 cm
336 ##$aimage fixe$bsti$2rdacontent
337 ##$asans médiation$bn$2rdamedia
338 ##$afiche$bno$2rdacarrier
500 ##$aPhotographie reproduite au recto par le Pigeon.
500 ##$a"Pourquoi tu me shootes pas? un livre de Pigeon et Catherine D'Amours, jerrylepigeon.bigcartel.com"—Verso.
588 ##$aTitre du verso.
600 16$aPigeon,$d1980-$tPourquoi tu me shootes pas?
650 #6$aJeunes hommes.
650 #6$aLits à deux places.
650 #6$aPhotographie artistique$y21e siècle.
655 #6$aCartes postales.
787 08$iEncarté dans :$aPigeon, 1980-$tPourquoi tu me shootes pas?$dMontréal : Le Pigeon et Catherine D'Amours, [2015]$h1 volume (non paginé) : tout en illustrations ; 26 cm$z9782981531605$w(CaQMBN)0005136907
Proposed change:
787777 08$iEncarté dans :$aPigeon, 1980-$tPourquoi tu me shootes pas?$dMontréal : Le Pigeon et Catherine D'Amours, [2015]$h1 volume (non paginé) : tout en illustrations ; 26 cm$z9782981531605$w(CaQMBN)0005136907
[Note: encarté dans is the French translation of ‘inserted in’ from J.4.4 Whole-Part Manifestation Relationships]
3.2 Example of a resource comprising four compact discs and a booklet
Current practice:
LDR 03906cjm a2200433Ma 4500
001 ocn931735120
003 OCoLC
005 20161028095526.0
007 sd#fungnn|m|ed
008 111114s2011####gaumunn###########n#mul#d
040 ##$aEEM$beng$erda$cEEM$dOCLCO$dOCLCF
024 1#$a880226002220
028 00$aDTD-22$bDust-to-Digital
035 ##$a(OCoLC)931735120
245 00$aOpika pende :$bAfrica at 78 RPM /$c[compiled and edited by Jonathan Ward].
260 ##$aAtlanta, Ga. :$bDust-to-Digital,$cp2011.
300 ##$a4 sound discs :$bdigital ;$c4 3/4 in.
336 ##$aperformed music$bprm$2rdacontent
337 ##$aaudio$bs$2rdamedia
338 ##$aaudio disc$bsd$2rdacarrier
500 ##$a100 original 78 rpm recordings of traditional and popular African music from the 1920s to the 1960s.
500 ##$a4 Compact discs in folded cardboard case, accompanied by booklet ( 111 pages : illustrations (some color), maps) in a box set.
505 0#$aDisc 1. Surah Al-Haaqqa, pt. 1 -- E Zzine Emlih Yamana -- Enna Nehoub, pt. 2 -- Sigha Med'heb, pt. 2 -- Ghina' Loziq -- Chanson De Dyahadi, pt. 2 -- Guelabiessi -- Ere Ye Agerie Lidj -- Abdulkadiri Kwori -- Cèlu Mankan -- Algrouane, pt. 2 -- Ahlen Bikoum -- Zendani Staiffi -- 'Aishek Baba -- Steukhbar Rasd Eddil, pt. 1 -- Taqsim Bayati -- Mestakhbar Mezmoum -- Doumoua Ellaini -- Git Lil-Haq, pt. 1 -- Aita Moulay Brahim -- Haragli Guelbi, pt. 1 -- Rabi Alaamlih Iydaabar, pt. 2 -- Adhouh, Adhouh, pt. 1 -- Gheniet Ben Soussan, pt. 7 -- Air De Kel Ajjer (Rhythme Ellehelleh)
505 0#$aDisc 2. Tu Nja Tengene Elie -- Osu Oblanyo -- I Tondo Muya -- Air De Haoua -- Bārā Sānābo Bārā -- Dagagne -- Ngwop -- Egberun Buso -- The Jambo song -- Okafu Nyi -- Kenssa -- Morigbé -- Domagbe -- Oyida Mayi Magbo -- Oblemo -- Djelouwei Wenike Ahlanon -- Cholie -- High life-Dagomba -- Eho Ma Ne Wubu Efu -- Ante Maria -- De Ehuo -- Kurungu -- Musique De Danse -- Saka Amodu -- Suro Onipa
505 0#$aDisc 3. Batata Dia Bwanga -- Molildo Kiruk-Yuk -- Tolingana -- March guitar -- Arabian Conga -- Stephen Opio -- Ndumba Wakumi Diekde Dikasa -- Iyan We Kimoino -- Ja Bane -- Tom Tom -- Furaha Ya Kanu -- Titi -- N. Odera -- Ngosingosi -- Naswa -- Kiboba Kiyma Nkuaku -- Ba'd El Zouz Marghub -- Mawali -- Tela, pt. 1 -- Comic sketch -- Nambanda -- Musungayi Nembwa Matumba -- Kayanda -- Masanga -- Napenda
505 0#$aDisc 4. Flute solo -- Siyahamba -- Wachona Thayelo -- Sati Wa Vakwela -- Yenz' Inqab' Intombi -- Ditee -- Laloe E! -- Cuisine Roulante -- Onano -- Yini Wena Funa -- Wati Si Sasekahipahpa -- Vura Matambo -- Bambo Siyaya -- Kxomo Muwa -- Fuzhi Inopenduka Kwenda Lamukiya -- Nkau Haka Khoele -- Dia Veloma I Said Omar -- Imini Ifikile -- Swaziland -- Ndapera Cha Cha -- Kama Kalinyana -- Nongqangqa Lishonile -- Boshiwe -- Waltz of the young hearts -- Nkosi Sikelel' Iafrika
520 ##$aOpika pende is a saying in Lingala language meaning to be strong, stand firm, and resist. This is a collection of 100 original 78 rpm recordings of traditional and popular African music from the 1920s to the 1960s. This collection is an attempt to showcase a diverse amount of long-forgotten music from Africa. Within the 100 tracks, traditional music stands side by side with popular music as traditional culture coexists with the modernity of the time.
650 #0$aFolk music$zAfrica.
650 #0$aPopular music$zAfrica.
650 #7$aFolk music.$2fast$0(OCoLC)fst00929383
650 #7$aPopular music.$2fast$0(OCoLC)fst01071422
651 #7$aAfrica.$2fast$0(OCoLC)fst01239509
655 #0$aWorld music$zAfrica.
655 #7$aWorld music.$2fast$0(OCoLC)fst01726780
700 1#$aWard, Jonathan.
Given there is a separate record for the booklet, here is the proposed change (adding to the record):
777 08#$iIssued with:$aWard, Jonathan, 1972-$tOpika pende.$dAtlanta, Ga : Dust-to-Digital, 2013$z1938922255$w(OCoLC)845516611
Referring to the BIBFRAME 2.0 Vocabulary (http://id.loc.gov/ontologies/bibframe.html) and Relationships (https://www.loc.gov/bibframe/docs/bibframe-relationships.html) pages:
Property |
Domain |
Range |
Definition |
relatedTo |
Work or Instance |
Work or Instance |
Any relationship between a Work or Instance and another Work or Instance. |
accompaniedBy |
Unspecified |
Unspecified |
Resource that accompanies the described resource |
accompanies |
Unspecified |
Unspecified |
Resource that adds to or is issued with the described resource. |
issuedWith |
Instance |
Instance |
Resource that is issued on the same carrier as the resource being described. |
issuance |
? |
? |
Categorization reflecting whether a resource is issued in one or more parts, the way it is updated, and its intended termination. |
Note that it is unclear why ‘accompaniedBy’ and ‘accompanies’, which are inverse expressions of one another, do not share the same sub-properties, nor why their definitions are slightly different in scope.
The ‘accompaniedBy’/‘accompanies’ relationship in BIBFRAME does not specify a domain or a range, i.e., it may be used when appropriate.
Similarly, lacking any specifications to the contrary, it seems possible to use the ‘issuedWith’ property on the description of a monograph Instance.
While MARC21 has retained restrictions on the use of linked entries according to the bibliographic level and mode of issuance of a resource, BIBFRAME has not continued that practice.
The current usage of ‘Issuance’ is unclear in BIBFRAME, given that it is defined simultaneously as a class (subclass of Resource) and as a property, without defining a domain or range for the latter. However, since it is stated that the property Issuance can be used with a Work or Instance, the traditional limitation of ‘mode of issuance’ for use with continuing resources seems to be absent.
5.1. Do you agree that it is appropriate to use field 777 for relationships between descriptions of manifestations that are issued together, i.e., when it is only appropriate to use a relationship designator from J.4.5 Accompanying Manifestation, and from J.5.5 Accompanying Item?
5.2. Do you agree that it is appropriate to use field 777 for intellectual relationships between resources that are also issued together, i.e., when relationship designators from J.2.5 Accompanying Work?
5.3. Are there other types of relationships between monographs in which the “Issued With” relationship may be appropriate? Are more display constants required?
5.4. Is the use of 777 $i sufficient to accommodate RDA relationship designators, or are new values in Indicator 2 preferred?
5.5. Given that field 787 Other Relationship Entry can be used with any appropriate relationship designator, and that 787 already has subfields to identify monographs, and given that field 777 has up until now, only been used between serials for a specific purpose, is broadening the scope of field 777 worthwhile?
5.6. Fields 760 (Main Series Entry) and 762 (Subseries Entry) are similarly intended for linking between serials, as indicated by the absence of monograph subfields $r, $u and $z, and are similarly restricted to linking between serials. Without having specific use cases, would the MARC Advisory Committee be open to adding subfields $r, $u and $z to fields 760 and 762?
HOME >> MARC Development >> Discussion Paper List
| The Library of Congress >> Especially
for Librarians and Archivists >> Standards ( 03/13/2017 ) |
Legal | External Link Disclaimer | Contact Us |