NAME: Defining a Constituent Unit Entry Field in the USMARC Bibliographic Format
SOURCE: Research Libraries Group; Avery Arts and Architecture Library; Athenaeum of Philadelphia
SUMMARY: This paper proposes broadening the use of field 770 (Supplement/Special Issue Entry) to include constituent units of the whole. This field would contain descriptive information about items that are constituents or elements of the item being cataloged or contained in the collection, group, or set being cataloged. The relationships between linking entry fields 770, 772 and 773 is explored. The paper proposes the addition of a second indicator in fields 770 and 772 to control display constants. An alternative is given to define a new field 774 for Constituent Unit Entry and remove the restriction in field 773 (Host Item Entry) that it be used only for titles that are subunits or component parts, i.e., physically contained in the host.
KEYWORDS: Field 770; Field 772; Field 773; Field 774; Supplement/Special Issue Entry; Parent Record Entry; Host Item Entry; Constituent Item Entry; Component parts
RELATED: DP89 (June 1995); DP80 (Feb. 1995)
12/1/95 - Forwarded to the USMARC Advisory Group for discussion at the January 1996 MARBI meetings.
1/20/96 - Results of USMARC Advisory Group discussion - Approved with the following amendments:
PROPOSAL NO. 96-4: Defining a Constituent Unit Entry Field 1. BACKGROUND In 1987, the Research Libraries Group added to RLIN a local field, 789, to contain information about items that are constituents or elements of the item being cataloged, or that are contained in the collection, group, or set being cataloged. Although this field has been used primarily in the cataloging of graphic materials in the RLIN Visual Materials file (VIM), it appears to be applicable to any circumstance where highlighting of individual contents of the described materials is desired, and, secondarily, in circumstances where a link to ancillary file materials is desirable. Further discussion of the use of field 789 in the Avery Architectural and Fine Arts Library at Columbia University's AVIADOR project and The Athenaeum of Philadelphia Architectural Archives's PACSCL Graphics Cataloging Project is given in Discussion Paper No. 89 (<URL:gopher://marvel.loc.gov:70/00/.listarch/usmarc/dp89.doc>). In the situations for which field 789 has been used (the link down to constituent units), separate records are not created for the constituent units being described for several reasons. It is easier to display the information if the descriptive information about the parts is in the same record; there are cases where separate records would not be practical, such as incipits for music, which may be linked to but do not represent separate bibliographic entities; and, it may not be desirable to fully catalog separately special issues of serials. Discussion Paper No. 80 (Defining a Component Item Entry Field in the USMARC Bibliographic Format), discussed in February 1995, first brought up this issue. It reviewed the cataloging options currently available for description of component items, but some participants favored the definition of a component item field because of particular situations where separate analytic records are not desirable, or when a 505 field does not give the information needed. The USMARC Advisory Group recommended that a second discussion paper be written. Discussion Paper No. 89 (Defining Field 774 as a Component Iten Entry Field in the USMARC Bibliographic Format) was considered by the USMARC Advisory Group in June 1995. It was requested that the paper come back as a proposal to define a new field 774 as follows: - reconsider the definition of component part in Leader/07 and in the Linking Entry Fields to take out the restriction of being "physically" part of another item - use subfields defined across linking entry fields with the addition of a second indicator for Display constant controller and a new subfield for Other identifier - allow for two techniques for linking to the electronic item: use of subfield $8 (Link and sequence number) to link between 774 and 856, or use of subfield $3 with the item identifier that is also contained in 774 $i - do not provide a specific sequencing technique, since if $8 is used to link to 856 it can also sequence them. If the other method is used, $8 is still available, since it has been defined across fields in the bibliographic format. 2. RELATIONSHIPS BETWEEN LINKING ENTRY FIELDS 770, 772 and 773 The USMARC Bibliographic Format has two linking entry fields available for a vertical relationship up from an item to its parent or host item. Field 772 (Parent Record Entry) is defined to contain information concerning the related parent record when the item is a single issue, supplement, or special issue of the parent item. Field 773 (Host Item Entry) is defined to contain information concerning the host item for the component part or subunit described in the record. Its purpose is to enable the user to locate the physical piece that contains the part being described. It is restricted to situations where the item is coded as a component part (monographic or serial) or subunit in the Leader/07 (Bibliographic level). Thus, the distinction between fields 772 and 773 is whether the item described is physically independent. The definition of a component part in the Leader/07 and in the Linking entry fields is as follows (definitions for monographic and serial component parts have been combined here: [Monographic or Serial] Component Part. Code [a or b] indicates a [monographic or serial] bibliographic unit that is physically attached to or contained in another [monographic or serial] unit such that the retrieval of the component part is dependent on the physical identification and location of the host item or container. Examples of monographic component parts with corresponding host items include an article in a single issue of a periodical, a chapter in a book, a band on a phonodisc, and a map on a single sheet that contains several maps. The bibliographic record for a component part contains fields that describe the component part and data that identify the Host Item Entry (field 773). An example of a serial component part with corresponding host item is a regularly appearing column or feature in a periodical. A subunit is defined in the Leader/07 as "a part of collection, especially an archival unit described collectively elsewhere is the system ... may be items, folders, boxes, archival series, subgroups or subcollections". When a bibliographic item has a vertical relationship to a parent item and it is physically independent, field 772 is appropriate for the link up. However, the display constant associated with this field is "Supplement to:", and it has been used for supplements to serials or technical reports. Currently, the map community has a need for this field when there is a parent/child relationship between items and the child is not physically a part of the parent. In particular, the University of California at Santa Barbara is creating records for digital maps as part of a Digital Library Project grant funded by the National Science Foundation. In these cases, field 772 is needed to contain information that is different than the parent record and to provide a link to that record. Digital files are physically separate and do not require the retrieval of the parent record for its physical identification, so it is not appropriate to code them as component parts in Leader/07. In the case of RLIN's field 789, the request is for a new field that would link down (the opposite situation of field 772). As with the maps project, the items are physically separate and not dependent upon the parent record for their physical identification. The field that has been used as a compliment to field 772 in serials cataloging is field 770 (Supplement/Special Issue Entry). Because this field has such a specific name and the display constant associated with it is "Has supplement", its possible use as a general link down in situations such has RLIN has identified has been overlooked. If the distinction between field 772 and field 773 (being independent of or physically a part of the whole) is necessary, then field 770 seems appropriate for the link down in these situations if its definition were broadened and an indicator for display constant controller added. The indicator would be needed in both field 770 (value blank (#) could be retained to generate "Has supplement"; a value could be added to generate "Includes:") and field 772 (value blank (#) retained to generate "Supplement to"; a value added to generate "Parent:"). The question arises whether a downward linking field complimentary to field 773 is needed as well, to bring out the distinction between the constituent units being physically a part of the whole or being physically independent. However, no need has been expressed for the link down when the constituent item is physically dependent upon the host. Other techniques can be used to make the distinction, such as use of field 505. It is important to consider whether the relationship expressed in the 770/772 pair is the same relationship as in the RLIN 789 field. The following questions need to be examined: - Can a supplement/special issue be considered a constituent unit of the serial, i.e. the same type of relationship as the constituent unit described in the RLIN 789 field? Or is the 770/772 relationship something different and one that we want to identify by using a different field? - If the relationship is different, then a new field is needed as the link to the constituent unit. Such a new field would be paired with field 773, which is the link up. If the 773 restriction of being physically dependent upon the host is removed, then what would be the distinction between fields 773 and 772? How might this be clarified? Format integration allowed for linking entry fields with specific serial uses to be defined across types of material. Some of the relationships expressed in these fields may be applicable to other types of material. Since the 770/772 relationship appears to be the same (a vertical link) as that needed for the RLIN 789 field, this proposal suggests broadening the use of those fields. 3. NEW DATA ELEMENTS NEEDED IN CONSTITUENT UNIT ENTRY FIELD Discussion Paper No. 89 mapped the subfields being used in RLIN's two projects in field 789 to currently available linking entry subfields. The only data elements not accommodated are: second indicator for display constant controller and a subfield for item, creator, or accession number. Second indicator. In the RLIN projects, a second indicator is used to control the display constant generated. It is defined as follows in RLIN's field 789: Display constant controller # No information provided 8 No display constant generated The display constant used in RLIN is "Component item" and is associated with the tag. It was defined so that users would have the option of suppressing it. In field 770, the second indicator could be defined so that blank is used to generate "Has supplement:", which has been used in the field for supplements or special issues for serials, and value 0 defined for "Includes:" for constituent units. The second indicator could not be defined as a display constant controller across all linking entry fields, since it is used for Type of relationship (which results in the generation of a display constant based on the value) in fields 780 and 785. It is also needed in field 772 to provide a display constant such as "Parent:". Additional display constants could be added as values when needed or subfield $i could be defined for display text for other text associated with the field. RLIN uses "Component item:" for a display constant, but, because of the specific definition in USMARC of component item as something physically a part of another, an alternative display constant is suggested. Subfield for other identifiers. Field 770 would use the subfields defined for the Linking Entry fields, 76X-78X. In addition, a subfield is needed for "Other identifier", which would include an item or accession number (subfield $o is proposed). The component item number used in the RLIN applications is any number chosen by the cataloging agency, and it is indexed in the RLIN Component item number (CIN) index. This subfield contains numbers associated with the constituent unit other than standard identifiers that already have specific subfields defined, for example accession numbers or creator's numbers. The subfield might be applicable to other linking entry fields when it is desirable to include other standard or non-standard identifiers that do not have specific subfields. In the future, it might be considered for a Uniform Resource Number, a standard being developed by the Internet Engineering Task Force, with the wrapper "URN:" to indicate what it is. However, the URN has not stabilized to the point that it is desirable to find a place for it yet in the MARC format. 4. LINKING THE CONSTITUENT UNIT DESCRIPTION TO THE ELECTRONIC ITEM The AVIADOR project uses the 789 field to provide a link to images on an analog videodisc. The link is implemented by the RLIN LaserLink software, which uses the accession number (contained in its subfield $i) to locate on an internal index the machine-readable address of the corresponding videodisc image. Thus, the online record contains no information about the actual address of the image on the videodisc. In some cases it may be desirable to include a field 856 in the record if the location is an Internet resource, often using a URL in subfield $u. In this case it would be necessary to provide a link between the descriptive information and field 856 to associate the specific item with its location. A record like one of the AVIADOR records might have several electronic locations: -- the electronic address in the AVIADOR videodisc -- the digital file name in the DIAP project (where there is overlap between the two projects) -- the address on a PhotoCD -- the URL on the Columbia University network where the image is accessible online Thus, a combination of approaches might be needed. Technique 1: Subfield $3 in 856 field. Subfield $3 (Materials specified) could be used in field 856 to specify the portion of the record to which the field applies. Data that provides a unique identification of the item could be used in the subfield, such as an accession number that matches that recorded in 770 $i, and electronic location information could be recorded in other appropriate 856 subfields. Technique 2: Subfield $8 link to 856 field. The 856 field could be linked to a constituent unit entry field using the subfield $8 linking technique that was approved in June 1994 as part of MARBI Proposal No. 94-15. In this case, a link code would need to be defined. The 856 field would contain the electronic location and access information (either a URL or other data). It would be linked to the appropriate 770 field using a subfield $8, which would match the $8 in the 770 field. A new code "e" could indicate that the data is provided to link the field to another field in the record (i.e., field 856) for electronic access. See Attachment C for an example of how each technique could be used. See Attachment D for the World Wide Web page showing access to the images used in the example. (For electronic access use: <URL:http://www.cc.columbia.edu/imaging/html/browsers/camilo/NYDA 93-F100.html>) Sequencing 770 fields. When $8 is used for linking, it also serves to sequence the 770 fields. If $8 is not needed for linking with an 856 field, it could also be used to indicate the sequence of occurrences of field 770 for display. This kind of sequence number aids the user in discriminating between occurrences of field 770 with brief information and gives clues about where the user is if the display of the record takes more than one screen. It has been used in the 789 implementation (in subfield $l). The number could take the form <link number>.<sequence number>\s, where "s" would be defined as a code for "sequence". Alternatively, it could simply use the link number portion of the subfield, i.e., <link number>\s. Participants in the discussion of Discussion Paper No. 89 wanted both of the linking techniques to be available to satisfy different needs. 5. FIELD 505 VERSUS 770 Field 770 is being used in a manner similar to a contents note with more content designation, and it is also being used to link to a digital item, although the link is through field 856. Both fields 505 and 770 describe constituents of the item. Field 770 would be available if it is necessary to provide more detailed information than that provided in 505 and parsed into separate subfields for each element. It is likely that there will also be cases where a link is desired to another bibliographic record (for the constituent unit) when one exists through the subfield $w. In addition, it may also be desirable to use the linking entry field for indexing of additional elements, e.g., ISSN, ISBN, uniform title. 6. IMPLICATIONS FOR RECORD LENGTH The use of a linking entry field for constituent unit has implications for exceeding limits for record length. If separate 770 fields are created for each constituent unit with descriptive information recorded in its separate subfields, and each field is linked to a corresponding 856 field with electronic location information, the record could potentially become very large. RLIN has had to use two or three records by which arbitrarily breaking up the information about the constituent units, and they have so far not had a problem. Institutions will need to consider these constraints when determining whether or how to use this approach. &. PROPOSED CHANGES The following is presented for consideration: - Change the name of field 770 (Supplement/Special Issue Entry) to Supplement/Special Issue/Constituent Unit Entry in the USMARC Bibliographic Format. Alternatively, define field 774 as Constituent Unit Entry, remove the restriction in field 773 that the record must be coded as a component part or subunit, and clarify the relationship between fields 772 and 773 with that restriction removed. If this option were followed, the other proposed changes below are also needed (except the second indicator defined for 770 would instead be defined in field 774). - Define a second indicator for field 770 as Display Constant Controller. # No information provided 0 Includes: 8 No display constant generated Value # is used to generate the text previously associated with the tag ("Has supplement") - Define a second indicator for field 772 as Display Constant Controller. # No information provided 0 Parent 8 No display constant generated Value # is used to generate the text previously associated with the tag ("Supplement to:") - Define subfield $o (Other item identifier) in the 76X-78X Linking Entry Fields. - Define subfield $i (Display text) in the 76X-78X Linking entry Fields - Define the following link codes for subfield $8 code e - electronic access code s - sequence See Attachment A for a description of the 76X-78X Linking entry fields if this proposal is approved. See Attachment B for a description of field 770 if this proposal is approved. ------------------------------------------------------------------ ATTACHMENT A 76X-78X Linking EntriesūGeneral Information Note: [ ] indicates deletion; < > indicates addition 760 Main Series Entry 762 Subseries Entry 765 Original Language Entry 767 Translation Entry 770 Supplement/Special Issue/<Constituent Unit> Entry 772 Parent Record Entry 773 Host Item Entry 775 Other Edition Entry 776 Additional Physical Form Entry 777 Issued With Entry 780 Preceding Entry 785 Succeeding Entry 786 Data Source Entry 787 Nonspecific Relationship Entry Indicators First Note controller 0 Display note 1 Do not display note Second 760-777, 786-787 Undefined # Undefined <770 Display constant controller # No information provided 0 Includes 8 No display constant generated 772 Display constant controller # No information provided 0 Parent: 8 No display constant generated> 780 Type of relationship 0 Continues 1 Continues in part 2 Supersedes 3 Supersedes in part 4 Formed by the union of ... and ... 5 Absorbed 6 Absorbed in part 7 Separated from 785 Type of relationship 0 Continued by 1 Continued in part by 2 Superseded by 3 Superseded in part by 4 Absorbed by 5 Absorbed in part by 6 Split into ... and ... 7 Merged with ... to form ... 8 Changed back to Subfield Codes Control subfields $3 Materials specified (NR) [773 only] $6 Linkage (NR) $7 Control subfield (NR) /0 - Type of main entry heading /1 - Form of name /2 - Type of record /3 - Bibliographic level Descriptive information $a Main entry heading (NR) $b Edition (NR) $c Qualifying information (NR) [all except 773] $d Place, publisher, and date of publication (NR) $g Relationship information (R) $h Physical description (NR) <$i Display text (NR) [770/772 only]> $j Period of content (NR) [786 only] $k Series data for related item (R) [all except 760 and 762] $m Material-specific details (NR) $n Note (R) $p Abbreviated title (NR) [773 only] $s Uniform title (NR) $t Title (NR) Numbers/codes $e Language code (NR) [775 only] $f Country code (NR) [775 only] <$o Other identifier (R)> $r Report number (R) [all except 760, 762, and 777] $u Standard Technical Report Number (NR) [all except 760, 762, and 777] $v Source contribution (NR) [786 only] $w Record control number (R) $x International Standard Serial Number (NR) $y CODEN Designation (NR) $z International Standard Book Number (R) [all except 760, 762, and 777] DEFINITION AND SCOPE The linking entry fields contain data concerning related items. These fields specify the relationship between the related bibliographic items. These relationships fall into two classes: 1) those related items that may assist the user in continuing to search but are not necessarily required in order to obtain the target item, e.g., former entries for serials, translations of the target item; 2) those related items that are required to obtain the target item (e.g., the host item for a component part). The linking entry fields are designed to display a note in the record in which the linking entry field appears and to provide machine linkage between the record for the target item and the record for the related item, if one exists. Definitions of terms used in descriptions of the linking entry fields are: Target Item. A bibliographic item that is the principal or primary unit for the description of which the record was constructed. The target item is the item to which the data in character positions 06 (Type of record) and 07 (Bibliographic level) of the Leader apply. Related Item. A bibliographic item that has either a chronological, horizontal, or vertical relationship with a target item, and for which the linking entry field is formulated. Component Part. A bibliographic item that is physically part of another bibliographic item such that the retrieval of the part is dependent on the physical identification and location of the host item (e.g., a chapter in a book, an article in a journal). <Constituent Unit. A bibliographic item that is a part of another item. The constituent unit may be physically separate from the parent item.> Host Item. A bibliographic item that physically contains the component part described by the target item record (e.g., the book containing the described chapter, the journal in which the article appears). Chronological Relationship. The relationship in time between bibliographic items (e.g., the relation of a serial to its predecessors and successors). Horizontal Relationship. The relationship between versions of a bibliographic item in different languages, format, media, etc. Vertical Relationship. The hierarchical relationship of the whole to its parts and the parts to the whole (e.g., a journal article to the journal, subseries to main entry series). Record Links and Notes The record-linking technique in USMARC is described below. Linking Entry Fields (fields 760-787)ūThese fields carry descriptive data concerning the related item, the control number for the record of the related item, or both. Minimal content designation is provided for the data concerning the related item that is used in the linking entry fields. For data operations requiring fuller content designation such as indexing and sorting, subfield w (control number for the related item) allows the system to follow that link to the related record to obtain fully content-designated data. Moreover, the coded data in control subfield 7 allows some types of indexing without reference to the actual related record. Linking Entry Complexity Note (field 580)ūThe Linking Entry Fields are designed to support generation of a note concerning the related item in a display of the record for the target item. When the relationship is too complex to be expressed using a display constant and the data from the linking entry field or the linked record, the note is recorded in the Linking Entry Complexity Note field. When used, this field appears in addition to any relevant linking entry field. The value used in the first indicator position of the linking entry fields determines whether a note is to be generated from the linking entry field or from field 580. Linked-Record Requirement (Leader/19)ūThis data element indicates whether sufficient information is present in the linking entry field to support generation of an eye-legible note that identifies the related item or whether only a related record number is recorded. If only a record number appears, the system will need to obtain the appropriate information from the related record to construct a standard display. The following subfields or subfield combinations are considered sufficient for display purposes: Subfield a + t Main entry heading + Title Subfield a + s Main entry heading + Uniform title Subfield t Title Subfield u Standard Technical Report Number Subfield r Report Number ------------------------------------------------------------------ ATTACHMENT B 770 Supplement/Special Issue/<Constituent Unit> Entry (R) Indicators First Note controller 0 Display note 1 Do not display note Second [Undefined] <Display constant controller> # Undefined <0 Includes 8 No display constant generated> Subfield Codes $a Main entry heading (NR) $b Edition (NR) $c Qualifying information (NR) $d Place, publisher, and date of publication (NR) $g Relationship information (R) $h Physical description of source (NR) <$i Display text (NR)> $k Series data for related item (R) $m Material-specific details (NR) $n Note (R) <$o Other identifier (R)> $r Report number (R) $s Uniform title (NR) $t Title (NR) $u Standard Technical Report Number (NR) $w Record control number (R) $x International Standard Serial Number (NR) $y CODEN designation (NR) $z International Standard Book Number (R) $6 Linkage (NR) $7 Control subfield (NR) /0 - Type of main entry heading /1 - Form of name /2 - Type of record /3 - Bibliographic level FIELD DEFINITION AND SCOPE This field contains information concerning supplements, [or] special issues, <or constituent units> associated with the target item but cataloged and/or input as separate records <or described separately in this field> (vertical relationship). When a note is generated from this field, it is displayed and/or printed with an introductory phrase that is generated as a display constant based on the [field tag] <value in the second indicator>. GUIDELINES FOR APPLYING CONTENT DESIGNATORS A description of the first and second indicator positions and all subfield codes, as well as input conventions except for display constants, for field 770 are given in the 76X-78X Linking EntriesūGeneral Information section. EXAMPLES 245 00$aNews of the Cooperative Health Statistics System. 770 0#$tDirectory: United States, territories, and Canada$w(DLC)$$$78646712$w(OCoLC)4579783 [Record is for the parent title; link gives entry of a supplement.] 245 00$aJournal of cellular biochemistry. 767 0#$tJournal of cellular biochemistry. Supplement$x0733- 1959 [Record is for the parent title; link gives entry of a supplement.] INPUT CONVENTIONS Display Constant <Introductory terms or phrases such as Has supplement: that are displayed in notes with the data recorded in field 770 are not carried in the USMARC record. They may be system generated as display constants associated with the second indicator value.> [Has supplement:] [The introductory phrase Has supplement: that is displayed in notes with the data recorded in field 770 is not carried in the USMARC record. It may be system generated as a display constant associated with the field tag.] RELATED USMARC FIELD OR DOCUMENT 76X-78X Linking EntriesūGeneral Information ------------------------------------------------------------------ ATTACHMENT C Example 1. DIAP record. Option 1 (Use of $3): Note that subfield $8 in 770 is used to sequence the fields (code "s), since it is not used in this option to link to field 856. Two URL's are provided in each 856 field for two different file formats of the same item (DIAP image and PhotoCD image). ID:NYDA93-F100 RTYP:c ST:s FRN: MS: EL: AD:09-16-93 CC:9114 BLT:gc DCF:a CSC:d MOD:? SNR: ATC: UD:10-18-93 CPR:xx L: INT:? TEQ:? TYPE:s PC:i PD:1989/1993 RUN:??? GPC:? ACMP:????? 043 n-us-ny 100 1 Vergara, Camilo J. 245 10 [136th Street, southeastern section of the Bronx]$h[graphic]. 260 [between 1989 and 1993]. 300 11 slides :$bKodachrome 64 daytime ;$c35 mm. 500 Slides taken by Camilo Vergara in the company of Lenny Hicks. 500 Forms part of the New American Ghetto Collection. 500 Bracketed information supplied by cataloger. 650 7 Expressway.$2aat 650 7 Garden suburbs.$2aat 650 7 Apartment houses.$2aat 650 7 Buildings.$2aat 650 7 Streets.$2aat 650 7 Street maps.$2aat 651 0 Mott Haven (New York, N.Y.)$xPictorial works. 700 1 Hicks, Lenny. 770 00 $81\s$oNYDA.1993.010.00130.$n[DIAPimage].$tMap of area with highlighted street 770 00 $82\s$oNYDA.1993.010.00131.$n[DIAPimage].$tView of Mill Brook Houses from one of the houses,$d89/05 770 00 $83\s$oNYDA.1993.010.00132.$n[DIAPimage].$tView SE from Mill Brook Houses on rooftop on Cypress Ave. between 136st. St. and 137th St.,$d93/05 770 00 $84\s$oNYDA.1993.010.00133.$n[DIAPimage].$tView N from 136th St. roof top of area between Bruckner Expressway and Cypress Ave.,$d93/06 770 00 $85\s$oNYDA.1993.010.00134.$n[DIAPimage].$tView E from rooftop of garden bounded by Bruckner Expressway,136st St. and 135th St.,$d93/06 856 7 $3NYDA.1993.010.00130 $uhttp://www.cc.columbia.edu/imaging/photocd/3009-1031- 1443/IMG0089.512.gif $uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00217.jpg $2http 856 7 $3NYDA.1993.010.00131 $uhttp://www.cc.columbia.edu/imaging/photocd/3009-1031- 1443/IMP0090.512.gif $uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00345.jpg $2http 856 7 $3NYDA.1993.010.00132$uhttp://www.cc.columbia.edu/imaging /photocd/3009-1031-1443/IMP0091.512.gif $uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00346.jpg $2http 856 7 $3NYDA.1993.010.00133$uhttp://www.cc.columbia.edu/imaging /photocd/3009-1031-1443/IMP0092.512.gif $uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00347.jpg $2http 856 7 $3NYDA.1993.010.00134$uhttp://www.cc.columbia.edu/imaging /photocd/3009-1031-1443/IMP0094.512.gif $uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00349.jpg $2http Option 2: Use of 856 with $8 Note that in subfield $8, code "e" denotes "electronic link" in the field link type. Subfield $8 in field 856 links both to the appropriate 770 field and sequences the 856 fields. ID:NYDA93-F100 RTYP:c ST:s FRN: MS: EL: AD:09-16-93 CC:9114 BLT:gc DCF:a CSC:d MOD:? SNR: ATC: UD:10-18-93 CPR:xx L: INT:? TEQ:? TYPE:s PC:i PD:1989/1993 RUN:??? GPC:? ACMP:????? 043 n-us-ny 100 1 Vergara, Camilo J. 245 10 [136th Street, southeastern section of the Bronx]$h[graphic]. 260 [between 1989 and 1993]. 300 11 slides :$bKodachrome 64 daytime ;$c35 mm. 500 Slides taken by Camilo Vergara in the company of Lenny Hicks. 500 Forms part of the New American Ghetto Collection. 500 Bracketed information supplied by cataloger. 650 7 Expressway.$2aat 650 7 Garden suburbs.$2aat 650 7 Apartment houses.$2aat 650 7 Buildings.$2aat 650 7 Streets.$2aat 650 7 Street maps.$2aat 651 0 Mott Haven (New York, N.Y.)$xPictorial works. 700 1 Hicks, Lenny. 770 00 $81\e$oNYDA.1993.010.00130.$n[DIAPimage].$tMap of area with highlighted street 770 00 $82\e$oNYDA.1993.010.00131.$n[DIAPimage].$tView of Mill Brook Houses from one of the houses,$d89/05 770 00 $83\e$oNYDA.1993.010.00132.$n[DIAPimage].$tView SE from Mill Brook Houses on rooftop on Cypress Ave. between 136st. St. and 137th St.,$d93/05 770 00 $84\e$oNYDA.1993.010.00133.$n[DIAPimage].$tView N from 136th St. roof top of area between Bruckner Expressway and Cypress Ave.,$d93/06 770 00 $85\e$oNYDA.1993.010.00134.$n[DIAPimage].$tView E from rooftop of garden bounded by Bruckner Expressway,136st St. and 135th St.,$d93/06 856 7 $81.1\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009- 1031-1443/IMG0089.512.gif $2http 856 7 $81.2\e$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00217.jpg $2http 856 7 $82.1\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009- 1031-1443/IMP0090.512.gif $2http 856 7 $82.2\e$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/. mosaic/nyc00345.jpg $2http 856 7 $83.1\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009- 1031-1443/IMP0091.512.gif $2http 856 7 $83.2\e$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00346.jpg $2http 856 7 $84.1\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009- 1031-1443/IMP0092.512.gif $2http 856 7 $84.2\e$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00347.jpg $2http 856 7 $85.1\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009- 1031-1443/IMP0094.512.gif $2http 856 7 $85.2\e$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/ .mosaic/nyc00349.jpg $2http