NAME: Defining Field 774 as a Component Item Entry Field in the USMARC Bibliographic Format
SOURCE: Research Libraries Group; Avery Arts and Architecture Library; Athenaeum of Philadelphia
SUMMARY: This paper explores the definition of field 774 to contain information about items that are constituents or elements of the item being cataloged or contained in the collection, group, or set being cataloged. RLIN currently uses a local field 789 for such data in the cataloging of graphic materials, which are linked to electronic images. It summarizes the data elements that the field might contain for description and gives options for linking to the image. These are: 1) using a URL in a subfield of the linking field; 2) providing a link between each 774 field and separate 856 field using the subfield $8 linking technique; and, 3) using repeatable 856 fields with $3 to show which 774 field it relates to.
KEYWORDS: Field 774; Component Item Entry
RELATED: DP87 (June 1995); DP80 (Feb. 1995); 94-15 (June 1994)
STATUS/COMMENTS:
5/26/95 - Forwarded to USMARC Advisory Group for discussion at the June 1995 MARBI meetings.
6/25/95 - Results of USMARC Advisory Group discussion - LC will prepare a proposal to define field 774 for Component Item Entry. Discussion centered on the questions posed in the discussion paper.
1. Definition of component part. The definition should be revised to take out the restriction of being "physically" a part of another item. The Leader definition also needs to be reviewed to ensure consistency with the definition in the linking entry fields.
2. Subfield $i and 2nd indicator defined in 774 only or across 76X-78X fields. There was no consensus, especially on the need for the second indicator.
3. 774 to include all subfields of 76X-78X? Yes, all subfields available in linking entry fields should also be available in 774.
4. Which option for linking to electronic item. Some participants thought it desirable to have more than one option. Since the discussion on URL's in linking entry fields will not result in defining a subfield as such, the other two options could be alternative techniques. It was felt that Option 3 was the least disruptive. It was suggested that needs of the music community for component item entry and linking to the item also be considered.
5. Subfield $8 code definition across linking entry fields? We have been restricting use of the code in $8 by type, not by field. Again, the music examples will need to be considered.
6. Necessity for sequencing 774 fields. If using option 2, the link number will also sequence them. If using option 3 ($3 technique), subfield $8 has been defined across bibliographic fields and can still be used for sequencing if necessary.
DISCUSSION PAPER NO. 89: Defining Field 774 as a
Component Item 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.
Discussion Paper No. 80 (Defining a Component Item Entry Field in
the USMARC Bibliographic Format) was considered by the USMARC
Advisory Group in February 1995. Although there are several
cataloging options for description of component items, 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. Since the RLIN 789 field was created for both
description and linkage to an image before the definition and
implementation of field 856, the issue of linking needs to be
reconsidered. The Group recommended that a second discussion paper
be written to further discuss these issues with options for
providing the link to the image.
Participants in the discussion also felt that the definition in
USMARC for component part needed to be revised considering this new
application. The following definition from USMARC, Fields 76X-79X,
does not address collections of the type being cataloged by AVIADOR
and PACSCL.
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).
2. CURRENT APPLICATION OF RLIN'S 789 FIELD
RLIN local field 789 was modeled primarily on the linking fields
76X-79X. Although only three subfields were defined for this
field, it was implemented in such a way that institutions could
define their own subfields in addition to the defined subfields, so
that they could experiment with the field and use it as they saw
fit.
The three RLIN-defined subfields are:
$i Component item number or accession number (R)
$w Control number (R)
$6 Linkage (R)
The component item number is any number chosen by the cataloging
agency. It is indexed in the RLIN Component item number (CIN)
index. The control number is the RLIN ID of a related record. It
is indexed in the Related record ID (RID) index. Both indexes are
general indexes that are available to all users.
Projects. To date at least two institutions have used the 789
field extensively in their RLIN records: The Avery Architectural
and Fine Arts Library at Columbia University for their Avery
Videodisc Index of Architectural Drawing on RLIN (AVIADOR) project
(as well as for subsequent projects), and The Athenaeum of
Philadelphia Architectural Archives for their Philadelphia Area
Consortium of Special Collections Libraries (PACSCL) Graphics
Cataloging Project. Both projects use the 789 to provide
additional descriptive information specific to a graphic item, and
to provide a mechanism for linking the written description with a
representation of the graphic image in analog or digital form.
AVIADOR.
AVIADOR (Avery Videodisc Index of Architectural Drawings on RLIN)
is an interactive system that links videodisc images of 41,000
architectural drawings from the Avery Architectural and Fine Arts
Library to their online catalog descriptions on RLIN, the
information network of the Research Libraries Group (RLG).
With AVIADOR, a user can browse through the architectural images on
the videodisc and, upon finding an image of interest,
simultaneously display the RLIN catalog record describing the
drawing. Conversely, the user can search RLIN for catalog
descriptions of drawings in the Avery collection and instantly view
the corresponding architectural images on the videodisc.
AVIADOR comprises 1) an analog videodisc containing images of
41,000 architectural drawings from the Avery Library, 2) RLIN
LaserLink software -- specially developed software based on
Microsoft Windows that links the images on the videodisc via a
personal computer to the online catalog record. This is done
through the use of tables matching the accession number stored in
subfield $i of the 789 field to the electronic address of the
corresponding drawing in the videodisc, and 3) a user's manual.
AVIADOR is designed for a PC workstation that includes an IBM PC AT
or compatible computer, a monitor, a mouse, a printer, an analog
videodisc player, and a videodisc monitor. Telecommunications
software connects the system to the RLIN database.
In the online bibliographic records, 789 fields contain detailed
information about items within a set. Where the body of the record
contains collective information for the set as a whole, the 789
allows for individual treatment of each drawing. Multiple 789
fields can be used to list or name the individual drawings in a
set, providing as little or as much descriptive information as
desired for each item. None of the subfields listed below is
required. At Avery, though, subfields $l and $i are always used
for sets of drawings. Subfields $t, $n, $c, and $d are always
used if the pertinent information exists on the drawing. For sets,
a title (subfield $t) is always devised if no title information
appears on the item. In the case of a record for a single drawing,
only subfield $i (the accession number) is used. Data appears in
the subfields of 789 only if it differs from the main bibliographic
description. Access points for the individual items are included
in the record for the set.
The subfields defined for project AVIADOR are as follows:
$l Locally assigned ordinal number for the drawing within
the collection (used primarily to keep track of the
number of drawings in a particular record)
$i Accession number. This is a unique number created for
each drawing in Avery's collection. Preceded by the
symbol NYDA, the number is composed of three groups of
digits separated by a period. The first group (4 digits)
is the year of acquisition, the second (3 digits) is the
sequential number of the collection in that year, and the
third (5 digits) is the sequential number of the drawing
within that collection. One more digit can be added at
the end, when necessary, to indicate whether the drawing
is the recto or the verso of a particular sheet. For
instance "NYDA.1989.003.00053v" is the accession number
for the drawing on the verso of the 53d drawing of the
third collection accessioned in 1989.
$t Title of individual drawing
$n Creator's number for the individual drawing
$c Names associated with that drawing other than the main
entry
$d Dates and qualifying date phrases associated with the
drawing
$p Physical description of the drawing
$o Other information not appropriate for the subfields above
$v A way to indicate whether an image is available. This
subfield was added when it was realized that Avery would
continue using the 789 in cataloging architectural
drawings after the end of project AVIADOR and needed a
way to distinguish records for drawings with an without
images. For AVIADOR the phrase "AVERYimage" was used.
For images created for the RLG Digital Image Access
Project (DIAP) the phrase "DIAPimage" was used. In other
records, the 789 is used but no image is available.
These alternatives are illustrated in the samples below.
PACSCL.
The Athenaeum of Philadelphia, a research library specializing in
architecture and the decorative arts, collects and provides for its
researchers relevant materials in a variety of formats. As part of
the PACSCL "Initiative for the 1990s," the Athenaeum is engaged in
the cataloging of its architectural drawings in RLIN. Based upon
Elizabeth Betz Parker's "Graphic Materials: Rules for Describing
Original Items and Historical Collections", this cataloging uses
unique strategies modeled after the AVIADOR Project. For the most
part, drawings are cataloged in architectural project sets, defined
by the architect's own commission/project number, if available, for
drawings representing either new construction or later alterations
and additions. An architectural project set may contain only one
drawing or hundreds, depending upon the holdings for that
particular project. (Excerpted from "Documentation and Retrieval
of Historic American Buildings Survey Drawings: Work in Progress,"
by Rebecca J. Mayne, Architectural Cataloger/Archivist, The
Athenaeum of Philadelphia, PACSCLnews, March, 1993, page 2.)
The Athenaeum uses a "call number" for each individual item
described in a particular bibliographic record, in a unique 789
field and subfield $i. The subfield $i may be repeated in the 789
field, when the item is described as part of two different sets
with conflicting numbers. Data in this subfield can have four
elements: Creator mnemonic; Creator project number, if known, or
locally assigned project number; Count within the set; Second, or
third, etc., accession or representation of a set for this project,
for this creator.
The Athenaeum uses these additional subfields in field 789 (listed
generally in order of use within the field):
$n Creator-assigned drawing or sheet number
$t Title
$p Subpart or subtitle
$c Creator
$d Date
$o Other, notes
$m Media
$s Size
3. DEFINITION OF FIELD 774
In the discussion of Discussion Paper No. 80 it was agreed
that a standard USMARC field should be considered for the data
currently being recorded in RLIN's field 789. The subfields of the
linking fields could be used effectively in component item entry
fields; some of them overlap with those defined by the AVIADOR and
PACSCL projects.
The following shows a mapping of 789 subfields (as defined for
the Aviador and PACSCL
projects) to 76X-78X subfields. One new subfield would be needed
to accommodate the data.
789 subfield Element 76X-78X subfield
$i Item or accession number $i [new]
$w Control subfield $w
$6 Linkage $6
$l Sequence number $8
$t Title $t
$n Creator's number $i [new]
$c Names other than main $a
entry
$d Date $d
$p Physical description $h
$p Subpart or subtitle $t or $n
$o Other information $n
$v Image availability $n
$m Media $h or $m
$h Size $h or $m
Note that subfield $8 was defined as a general technique in
bibliographic fields with Proposal No. 94-15; and subfields $h, $m,
and $n were defined in 76X-78X fields with Proposal No. 94-17A.
Field 774 would use the indicators and subfields defined for the
Linking Entry fields, 76X-78X. In addition, the following new
elements would be needed:
Subfield $i - Other identifier
Second Indicator - Display constant controller
Subfield $8 link codes: "e" for electronic and "s" for
sequencing
Which link codes would need to be defined depends on the choice of
options for linking to the electronic item.
Subfield $i. This subfield contains numbers other than standard
identifiers associated with the component item, for example
accession numbers or creator's numbers. The subfield contains text
that describes the number (i.e., a qualifier). An accession number
that provides access to an electronic version of the component item
might be recorded as part of a URL in subfield $l (if this subfield
is defined). The subfield might be applicable to other linking
entry fields where it is desirable to include other standard or
non-standard identifiers that do not have specific subfields. 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. See Discussion Paper No. 87
(Addition of Subfield $l (Uniform Resource Locator) in Linking
Entry Fields 76X-78X in the USMARC Bibliographic Format) for
further discussion of including a URN in the linking entry fields.
Second Indicator. The second indicator, currently undefined, is
needed for controlling display constants. 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 is "Component item". It was defined so
that users would have the option of suppressing it. It is possible
that other display constants might be desirable and other values
defined.
Subfield $8 codes. Subfield $8 had been defined in bibliographic
fields for a link and sequence number with a code indicating its
use. 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. If $8 is not needed for linking with an 856
field, it could be used to indicate the sequence of occurrences of
field 774 for display. This kind of sequence number aids the user
in discriminating between occurrences of field 774 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. See
also below under part 4 for a further discussion of linking. Note
that when $8 is used for linking, it also serves to sequence the
774 fields.
See Attachment A for a description of the linking entry fields with
the proposed new elements.
4. LINKING THE COMPONENT PART 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
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. Other options may be considered to provide
such access information.
OPTIONS
Option 1: URL in linking entry field. The URL could be recorded
in the linking entry field 774. Note that Discussion Paper No. 87
(Addition of Subfield $l (Uniform Resource Locator) in Linking
Entry Fields 76X-78X in the USMARC Bibliographic Format) suggests
the definition of a subfield across linking entry fields for a URL.
If this subfield is defined, each 774 field would contain a URL for
access to the electronic item. This is a good example of a
situation where a separate record might not be created for the
item, but the 774 field would provide descriptive information.
There would be no 856 to contain the URL of each part, since the
separate record would not be created.
Assuming that the URL subfield is defined, this approach could only
be used if a URL is available for the item. Currently an accession
number is recorded in some situations as the link to the videodisc,
so such a subfield would not be an appropriate place to store the
data. The linking entry fields do not have enough unused subfields
to allow for the definition of separate data elements similar to
what is in field 856. In a case where no URL is available, either
additional subfields would need to be defined to accommodate the
link, or another method used. Alternatively, the proposed subfield
$i (Other identifier) in field 774 could be used in these
situations where a URL is not available; that data is used in
RLIN's 789 field currently to provide the link.
Option 2: Subfield $8 link to 856 field. The 856 field could be
linked to a component item 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 774 field using a subfield $8, which
would match the $8 in the 774 field.
Option 3: Subfield $3 in 856 field. Subfield $3 (Materials
specified) could be used in field 856 to specify (perhaps by
accession number) 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 is
also recorded in 774 $i, and electronic location information could
be recorded in other appropriate 856 subfields.
See Attachment B for an example of how each option would be used.
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.
5. QUESTIONS
The following questions need to be considered in order to formulate
a proposal to add field 774 to the USMARC Bibliographic Format.
1. How should the definition of component part be revised in
USMARC to include the applications detailed in this paper?
2. Should any new data elements needed for field 774
(subfield $i and second indicator) be defined across the
linking entry fields or be restricted to this field?
3. Should field 774 be defined to include all of the
subfields of the Linking Entry fields 76X-78X? Or should some
subfields not be defined for 774?
4. Which option is preferred for linking the 774 field to the
electronic item? Is it necessary to have more than one
technique depending upon the situation?
5. If option 2 ($8 technique) is selected, should the
subfield $8 link code be defined across linking entry fields,
across bibliographic fields, or restricted to field 774?
6. Is it necessary to sequence the 774 fields? If Option 2
is selected, will the link number to the 856 field also serve
to sequence the 774 fields, or is another element (i.e.,
sequence number) needed? If Option 1 or 3 is selected, should
subfield $8 with a link code "s" be used? Should the data
include a whole number if it is not also linking to another
field in the record?
7. Should the second indicator for Display constant
controller be used? In all 76X-78X fields or only in field
774? Should other display constants be defined?
------------------------------------------------------------------
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 Entry
772 Parent Record Entry
773 Host Item Entry
<774 Component 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
<774 Display constant controller
# No information provided
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
<$8 Link and sequence no.>
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)
$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]
<$i 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).
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).
------------------------------------------------------------------
ATTACHMENT B
Example 1. DIAP record.
Option 1: 774 field with $l and URL
Note that subfield $8 in 774 is used to sequence the fields (code
"s").
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.
774 0 $81\s$iNYDA.1993.010.00130.$n[DIAPimage].$tMap of area
with highlighted street
$lhttp://www.cc.columbia.edu/imaging/photocd/3009-1031-
1443/IMG0089.512.gif
$lhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00217.jpg
774 0 $82\s$iNYDA.1993.010.00131.$n[DIAPimage].$tView of Mill
Brook Houses from one of the houses,$d89/05
$lhttp://www.cc.columbia.edu/imaging/photocd/3009-1031-
1443/IMP0090.512.gif
$lhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00345.jpg
774 0 $83\s$iNYDA.1993.010.00132.$n[DIAPimage].$tView SE from
Mill Brook Houses on rooftop on Cypress Ave. between
136st. St. and 137th St.,$d93/05
$lhttp://www.cc.columbia.edu/imaging/photocd/3009-1031-
1443/IMP0091.512.gif
$lhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00346.jpg
774 0 $84\s$iNYDA.1993.010.00133.$n[DIAPimage].$tView N from
136th St. roof top of area between Bruckner Expressway
and Cypress Ave.,$d93/06
$lhttp://www.cc.columbia.edu/imaging/photocd/3009-1031-
1443/IMP0092.512.gif
$lhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00347.jpg
774 0 $85\s$iNYDA.1993.010.00134.$v[DIAPimage].$tView E from
rooftop of garden bounded by Bruckner Expressway,136st
St. and 135th St.,$d93/06
$lhttp://www.cc.columbia.edu/imaging/photocd/3009-1031-
1443/IMP0094.512.gif
$lhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00349.jpg
Option 2: Use of 856 with $8
Note that in subfield $8, code "e" denotes "electronic link" in
the field link type.
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.
774 0 $81\e$iNYDA.1993.010.00130.$n[DIAPimage].$tMap of area
with highlighted street
774 0 $82\e$iNYDA.1993.010.00131.$n[DIAPimage].$tView of Mill
Brook Houses from one of the houses,$d89/05
774 0 $83\e$iNYDA.1993.010.00132.$n[DIAPimage].$tView SE from
Mill Brook Houses on rooftop on Cypress Ave. between
136st. St. and 137th St.,$d93/05
774 0 $84\e$iNYDA.1993.010.00133.$n[DIAPimage].$tView N from
136th St. roof top of area between Bruckner Expressway
and Cypress Ave.,$d93/06
774 0 $85\e$iNYDA.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\e$uhttp://www.cc.columbia.edu/imaging/photocd/3009-
1031-1443/IMG0089.512.gif $2http
$uhttp://www.cc.columbia.edu/imaging/diap/jfif00/.mosaic/
nyc00217.jpg $2http
856 7 $82\e$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 $83\e$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 $84\e$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 $85\e$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 3:
Note that subfield $8 in 774 is used to sequence the fields (code
"s), since it is not used in this option to link to field 856.
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.
774 0 $81\s$iNYDA.1993.010.00130.$n[DIAPimage].$tMap of area
with highlighted street
774 0 $82\s$iNYDA.1993.010.00131.$n[DIAPimage].$tView of Mill
Brook Houses from one of the houses,$d89/05
774 0 $83\s$iNYDA.1993.010.00132.$n[DIAPimage].$tView SE from
Mill Brook Houses on rooftop on Cypress Ave. between
136st. St. and 137th St.,$d93/05
774 0 $84\s$iNYDA.1993.010.00133.$n[DIAPimage].$tView N from
136th St. roof top of area between Bruckner Expressway
and Cypress Ave.,$d93/06
774 0 $85\s$iNYDA.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
Library of Congress