MARC 773 Host Item Entry: Difference between revisions

No edit summary
m (→‎Examples: format)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Draft}}
MARC field 773 in the Bibliographic format contains information concerning the host item for the constituent unit described in the record (vertical relationship), for example, the host volume for a journal article when the article is cataloged separately. It is used in the child record to give information about the host volume, and may have reciprocal [[MARC 774 Constituent Unit Entry|774 fields]] in the parent record.
MARC field 773 in the Bibliographic format contains information identifying the target of a vertical relationship, for example, the host volume for a journal article when the article is cataloged separately. Originally intended to allow users to find the published volume that contains the component described in the record, MARC field 773 has come to be used by special collections libraries for copy-specific purposes as well, for example linking record for items in a collection to the parent record for the collection, and linking records for individual items in an extra-illustrated volume to the record for the parent volume.
 
It is intended to allow users to find the physical volume that contains the component described in the record, although the Folger has occasionally used MARC fields 773/774 to create reciprocal links between a collection and its separate component parts.  


This field is repeatable.
This field is repeatable.
Line 10: Line 11:
'''Indicators'''<br>
'''Indicators'''<br>
1st indicator – Note controller <br>
1st indicator – Note controller <br>
  0 - Display note
  0 - Display note [Current Folger policy: can only be used when the link is made by a unique ǂt; must not be used when linking by Bib ID]
  1 - Do not display note
  1 - Do not display note
2nd indicator – Display constant controller
2nd indicator – Display constant controller
Line 28: Line 29:


==Policy and formulation==
==Policy and formulation==
* Routinely add 773 fields to records for items that contain or are associated with constituent units.
* Routinely add 773 fields to child records, keeping in mind the consequences of the Voyager configuration.
* Currently, this means doing one of two things:
** Adding a 773 containing only $o (which gives the Bib ID for the parent record)
** Adding a 773 containing only $t (which must exactly match the unique character string of the parent record's title, as given in the parent record's 245$a)


==Voyager configuration==
==Voyager configuration==
Line 38: Line 42:


==Examples==  
==Examples==  
<pre></pre>
773 1_ ǂo 224602
(Item is a letter bound in the collection of manuscript letters described by Bib ID 224602)
 


<pre></pre>
773 0_ ǂt Babette Craven collection of theatrical memorabilia
(Item is an object that forms part of the Babette Craven collection of theatrical memorabilia)</br>
''Note: this example illustrates former practice. Current practice for physically separate items forming part of a [[Named collections|named collection]] is to make a title added entry for collection name.''


==External links==
==External links==

Latest revision as of 12:26, 30 August 2021

MARC field 773 in the Bibliographic format contains information concerning the host item for the constituent unit described in the record (vertical relationship), for example, the host volume for a journal article when the article is cataloged separately. It is used in the child record to give information about the host volume, and may have reciprocal 774 fields in the parent record.

It is intended to allow users to find the physical volume that contains the component described in the record, although the Folger has occasionally used MARC fields 773/774 to create reciprocal links between a collection and its separate component parts.

This field is repeatable.

Searching

  • [indicate whether the field is searchable in Hamnet drop-downs, or only in the staff module and Command Line search]

Commonly-used tags

Indicators
1st indicator – Note controller 

0 - Display note [Current Folger policy: can only be used when the link is made by a unique ǂt; must not be used when linking by Bib ID] 
1 - Do not display note

2nd indicator – Display constant controller 

# - In
8 - No display constant generated

Subfield delimiters

ǂa - Main entry heading
ǂd - Place, publisher, and date of publication
ǂg - Related parts
ǂh - Physical description
ǂi - Relationship information
ǂn - Note
ǂo - Other item identifier
ǂt - Title
ǂw - Record control number

Policy and formulation

  • Routinely add 773 fields to child records, keeping in mind the consequences of the Voyager configuration.
  • Currently, this means doing one of two things:
    • Adding a 773 containing only $o (which gives the Bib ID for the parent record)
    • Adding a 773 containing only $t (which must exactly match the unique character string of the parent record's title, as given in the parent record's 245$a)

Voyager configuration

  • As of December 5, 2017, Hamnet is set so that links to "Related records" are automatically generated when any of the following is true:
    • the 773$t in the child record matches the 245$a of the parent record
    • the 773$o in the child record matches the Bib ID of the parent record
    • the 774$o in the parent record exactly matches the 773$t of the child record (remember to code the first indicator so that the note does not display)
    • each 774$o of the parent record contains the Voyager bib ID of a child record (remember to code the first indicator so that the note does not display)

Examples

773 1_ ǂo 224602

(Item is a letter bound in the collection of manuscript letters described by Bib ID 224602) 


773 0_ ǂt Babette Craven collection of theatrical memorabilia

(Item is an object that forms part of the Babette Craven collection of theatrical memorabilia)
Note: this example illustrates former practice. Current practice for physically separate items forming part of a named collection is to make a title added entry for collection name.

External links