Linking entry fields provide a machine link among related record in a file. Examples of related records include preceding titles, succeeding titles, reproductions, other editions, supplements, translations, etc. Machine links allow a user to search a title and to retrieve records for that title and for related records.

Linking entry fields also provide a bibliographic note that is generated form the linking field. This feature eliminates the necessity of rekeying the title in a note. Example:

Linking entry fields may be used to provide notes and computer access for related titles for which there is no record online (e.g., a 780 field may be given for the earlier title when the title is known, even though there is no record on the database).

Background:

1. Relationships represented by linking entry fields:

Linking entry fields include the following relationships: Example:

In most cases, linking entries are made from one record to its related record, and the related record is linked to the first record. In the example given below, the Annual law review is succeeded by the University of Western Australia law review. That continuation is noted in the 785 linking field of the record for the Annual law review. Likewise, the University of Western Australia law review is preceded by the Annual law review, and that continuation is noted in the 780 linking field of the latter record. Example:

2. Linking entry first indicator and field 580 (Linking entry complexity note):

The 765-787 field can be used without an accompanying 580 field whenever the display constant associated with the field accurately defines the relationship between the publications. Set the first indicator of the linking field to value "0" to print the bibliographic note. Example:

When the display constant does not adequately define the relationship, input a note in field 580. Input the 765-787 field to provide the machine linkage and set the first indicator to value "1" to suppress the printing of a note. Example:

Further instructions for the setting of the first indicator are provided with the specific linking entry fields.

3. Added entries:

When an added entry is needed for a title used in a linking field, input the added entry in the appropriate 7XX field (700-730). Linking fields do not take the place of added entries because linking fields do not generate tracings. Likewise, an added entry in field 700-730 does not take the place of a linking field, because the added entry field does not generate a note. Example:

4. Monographs:

When a serial is related to a monograph or other non-serial format publication, input the title of the related record in a 580 note. No linking entry (field 765-787) is provided for the monographic title, but an added entry (field 700-730) may be given. Example:

Editing instructions:

1. Punctuation:

Punctuation may be generated on output by a user's print program and should not be input except where indicated. Apply the following guidelines:

a. Input a period following subfield $a, $s and $t (when followed by $b).

b. Do not input a period at the end of any other subfield. (Exception: NLC inputs a period at the end of subfield $t. Participants using NLC records should not remove the period.)

c. Do not input a comma preceding subfield $x (ISSN) or subfield $g (Relationship information). Example:

2. Subfielding:

Do not add delimiters and subfield codes to individual components of the name in subfield $a or the title in subfield $t. Example:

3. Initial articles:

All initial articles in the entry of the related record are omitted in the linking entry field with the exception of the personal or geographic names that file on the article. Example:

Form of entry:

When linking to an existing AACR2 record for a related publication, use the form of entry as found on that record.

However, when using a name-title entry in a link from a pre-AACR2 record, change the form of the name, but not the choice of entry, to AACR2 form. Change also the form of the name in the main entry heading on the related record.

When linking to a pre-AACR2 record that is distinguished from other records of the same title by an edition statement, include in the linking entry field the edition statement. (Under AACR2, a serial issued in multiple editions is linked to a related title by a uniform title.)

When no record exists for a related publication, construct a link based on AACR2 choice and form of entry.

For instructions on linking to latest entry records, see instructions for subfield $w.

1. Related entry is AACR2. Example:

2. Related entry is pre-AACR2. Example:

3. No online record for related title. Example:

The following chart lists the possible forms of linking entries, with the appropriate subfield codes and corresponding tags in the related record.

FORM OF LINKING ENTRY

RELATED RECORD

765-787 LINK

a) Title proper, and if needed for identification, edition statement

245

245/250

$t

$t $b

b) Main entry name heading.title/proper, and if needed for identificaiton, edition statement

1XX/245

1XX/245/250

$a $t

$a $t $b

c) Main entry name heading/uniform title

1XX/240

$a $s

d) Main entry name heading/uniform title/title proper (legal materials, translations, and other language editions)

1XX/240/245

$a $s $t

e) Main entry uniform title

130

$t

f) Main entry uniform title/title proper (translations and other language editions)

130/245

$t

Examples:

These examples present different forms of main entries and illustrate the proper transcription of these main entries in linking fields on related records.

Title proper, and if needed for identification, edition statement. Example:

Main entry name heading/title proper, and if needed for identification, edition statement. Example:

Main entry name heading/uniform title. Example:

Main entry name heading/uniform title/title proper (legal materials, translations, and other language editions). Example:

Main entry uniform title. Example:

Main entry uniform title/title proper.

For translations and other language editions, both field 130 (Main Entry- -Uniform Title) and field 245 (Title Proper) are used in the link and are coded as subfield $t. Example:

Subfield codes:

To determine the input order of subfields, refer to the individual listings of subfield codes for each linking entry field.

$a Main entry heading

$b Edition

$c Qualifying information

$d Place, publisher, and date of publication

$e Language code

$f Country code where issued

$g Relationship information

$k Series data for related item

$r Report number

$s Uniform title

$t Title

$u Standard Technical Report Number (STRN)

$w Record control number

Linking to latest entry records (See C10)

Linking to NLC French-language records:

CONSER members should not link NLC French-language cataloging records to English-language cataloging records, or vice versa. Only NLC may provide links between French-language cataloging records, or between French-language and English-language cataloging records that are authenticated by NLC only. Links to NLC French-language cataloging records will be deleted form records subsequently authenticated by LC or NSDP.

$x International Standard Serial Number

$y Coden designation

$z International Standard Book Number

$6 Linkage

$7 Control subfield

Special instructions- -Numerous related records:

In cases where numerous titles are related to the serial, each cataloged separately, it may be impractical to list each in a separate linking field. When this occurs, the following method may be applied.

Create a 580 note providing an explanation of the related titles associated with the serial.

If each related title has the same common title, given the common title in the linking field. Use the mark of omission for the section title. Add the LC control number (or the OCLC control if there is no LC number) of each related title in separate subfields $w.

If the related titles do not have a common title, give as much information as possible in the 580 field and omit the linking fields. Example:

See also:

76X-78X Linking Entries