MARC 787 Other Relationship Entry
MARC field 787 in the Bibliographic format contains information concerning the work related to the target item when the relationship does not fit any of those defined in fields 760-785. This field is repeatable.
Basic use and searching
Basic use
- Use for linking Hamnet records with uncommon or nonspecific relationships
Searching
- [indicate whether the field is searchable in Hamnet drop-downs, or only in the staff module and Command Line search] To be determined.
Commonly-used tags
Indicators
1st indicator – Note controller
0 - Display note
2nd indicator – Display constant controller
# - Related item 8 - No display constant generated
Subfield delimiters
$i - Relationship information (R) $a - Main entry heading (NR) $t - Title (NR) $d - Place, publisher, and date of publication (NR) $h - Physical description (NR) $n - Note (R) $w - Record control number (R)
Policy and formulation
- Need to determine: will we prefer use of subfield $n or an accompanying MARC 580 Linking Entry Complexity Note to describe the relationship?
- Hamnet is configured so that the presence of a Hamnet Bib ID in 787ǂo automatically creates a "Records for related items" link.
Examples
Record is for printed book.
787 0 ‡a Westerhout, Arnold van, 1651-1725. ‡t Eques Leenae Neapoli. ‡d [Rome?] : [Arnold van Westerhout], [1711?] ‡h 1 plate ; 204 x 139 x 10.5 mm. ‡n Copperplate used to print plate 67 of manifestation. ‡o 340195 ‡w (DFo)340195
Record is for copperplate
787 0 ‡t Ordinum equestrium, ac militarium brevis narratio. ‡d [Venice] : pressò L'Orlandi, 1715. ‡h [2], CXXXXI, [3] p., [246] p. of plates : ill., coats of arms, ports. ; 27 cm (4to) ‡n Manifestation containing, as plate 67, the print made from the copperplate. ‡o 352615 ‡w (DFo)352615
Note from Erin B.: ‡w has to be an exact match for the Hamnet BibID in order for the link to be generated, so instead of deleting "(DFo)" from the ‡w (which is non-standard MARC) I created a new Bibliographic Linking Record Profile in the SysAdmin module that first looks for the BibID in the ‡o, then added that profile to the display1.cfg file that generates the OPAC bib record display result. Note that ‡o is used for Folger call number in some existing records, so those won't create links (773/774 links can only be matched to Bib ID, main entry, or title in Voyager).