4-- Linking Entry Block

Definition and Scope of Fields

STRUCTURE OF LINKING ENTRY FIELDS

This structure applies to all 4-- linking entry fields.

"The primary purpose of UNIMARC is to facilitate the international exchange of bibliographic data in machinereadable form between national bibliographic agencies. UNIMARC may also be used as a model for the development of new machinereadable bibliographic formats" - Purpose and Scope of UNIMARC.

It is therefore important that the UNIMARC format be hospitable to other MARC formats: otherwise conversion to and from UNIMARC is difficult or even impossible.

For this reason the technique of embedded fields has been supplemented by a technique using standard subfields. The structure of the agency's records will determine which system of linking entry fields is used.

Where there is a choice of system, the agency should weigh the advantages of the linking entry system, which allows fuller although more complex entries, against the advantages of the standard subfield system, which is easier to implement.

A statement that linking fields are present or absent together with a note of the type of contents in such linking fields, should be given in the documentation to accompany exchange records. For details, see Appendix K.

Within the Linking Entry Fields Section, both methods are described in the order: (A) embedded fields technique then (B) the standard subfields technique. All examples illustrate both methods.

Each linking entry field in a record will contain subfields that identify the item to which the link is being made. The data in this field should be sufficient to identify the record for the item being linked to, or, if there is no record, to identify the item itself.

In the following list the fields are labelled by the type of record to which the link is being made, e.g. 410 SERIES is used in a subseries record to link to the series of which it is a part.

Fields

41- Series, supplements, etc.

410 Series

411 Subseries

421 Supplement

422 Parent of Supplement

423 Issued with

43- Preceding entries

The specifications below are in addition to those given at the beginning of the block under 4-- STRUCTURE OF LINKING ENTRY FIELDS.

The above fields are used to link a serial being catalogued to a preceding title. Fields 431-437 are used in preference to 430 when it is required to elaborate on the 'preceding' relationship. Where an agency uses the above fields they should be distinguished as follows:

Continues: the new title replaces the earlier title without a change in numbering;

Supersedes: the new title replaces the earlier title and the numbering of the earlier one is not continued;

Absorbed: a serial was in existence before it absorbed an earlier serial and it continues with its own numbering.

Separated from: the new title was once a part of a still existing title.

430 Continues

431 Continues in Part

432 Supersedes

433 Supersedes in Part

434 Absorbed

435 Absorbed in Part

436 Formed by Merger of

437 Separated From

44- Succeeding entries

The specifications below are in addition to those given at the beginning of the block under 4-- STRUCTURE OF LINKING ENTRY FIELDS

The above fields are used to link a serial being catalogued to its succeeding title. Fields 441-445 are used in preference to 440 when it is desired to elaborate on the 'succeeding' relationship. Where an agency uses the above fields they should be distinguished as follows:

Continued by: the new title replaces the earlier title without a change in numbering;

Superseded by: the new title replaces the earlier title and the numbering of the earlier one is not continued;

Absorbed by: the serial being catalogued ceases to exist but is continued by the serial referred to in field 444 or 445, although this serial continues it previous numbering.

440 Continued by

441 Continued in Part by

442 Superseded by

443 Superseded in Part by

444 Absorbed by

445 Absorbed in Part by

446 Split into

447 Merged with xxx to form

448 Changed back to

45- Other editions

451 Other Edition in Same Medium

452 Edition in a Different Medium

453 Translated as

454 Translation of

455 Reproduction of

456 Reproduced as

46- Levels

461 Set Level

462 Subset Level

463 Piece Level

464 Piece-Analytic Level

47- Other

470 Item reviewed

481 Also Bound With this Volume

482 Bound With

488 Other Related Works

Notes on Field Contents

Each linking field is formatted as follows:

It is recommended that embedded fields are entered in numerical order of tag within each field. In the case of an embedded 001 field, neither indicators nor subfield identifiers are defined so that the subfield data includes only the tag and the number (EX 1).

If a linking field contains the record control number of the linked record, this record should be included in the same file for distribution purposes.

Linking fields constructed from a full record should contain the following required data when present:

001 RECORD IDENTIFIER

500 UNIFORM TITLE

OR (if 500 not present in the record)

200 $a Title Proper

7-- Primary Intellectual Responsibility (if present)

206 MATERIAL SPECIFIC AREA: CARTOGRAPHIC MATERIALS - MATHEMATICAL DATA

The following fields may optionally be included:

010 ISBN

011 ISSN

040 CODEN

101 LANGUAGE OF THE WORK

102 COUNTRY OF PUBLICATION OR MANUFACTURE

123 CODED DATA FIELD: CARTOGRAPHIC MATERIALS - SCALE AND COORDINATES

130 CODED DATA FIELD: MICROFORMS - PHYSICAL ATTRIBUTES

200 $a Title proper [if not already included]

200 $f First Statement of Responsibility

200 $h Number of Section or Part

200 $i Name of Section or Part

200 $v Volume Designation

205 EDITION STATEMENT

210 PUBLICATION, DISTRIBUTION ETC.

215 PHYSICAL DESCRIPTION

225 SERIES

510 PARALLEL TITLE PROPER

530 KEY TITLE

856 $u URL

In some cases these optional fields may be needed to identify the item, e.g. 210 PUBLICATION, DISTRIBUTION, ETC. for 45- OTHER EDITIONS.

It is not recommended that additional fields be included.

Linking fields not constructed from a full record should contain as much of this data as possible, given the practices of the source agency.

At the least they should contain the data listed above, but need not include the record identifier.

Fields or other related entities

311 Notes Pertaining to inking fields

Field 311 may be used to express any of the linking relationships appearing in this block when a note is required which cannot be generated from a 4-- field. If field 311 is used, the second indicator of the corresponding 4-- field is set to 0.

Examples

Ex. 1:

Embedded fields technique

461 #0$100177-10346$12000#$aCountries of Europe$vvol. 2

Field components:

#0 Indicators for field 461

$1 Subfield identifier

001 Tag of embedded field

77-10346 Data of 001 field

$1 Subfield identifier

200 Tag of embedded field

0# Indicators of embedded 200 field

$a Subfield identifier for 200 field

Title Data of 200 field

$v Subfield identifier for 200 field

vol. 2 Data of 200 field

Ex. 2:

Standard subfields technique

461 #0$077-10346$tCountries of Europe$vvol. 2

This example illustrates a link from a volume to a multivolume monograph that is at the set level. The item being catalogued vol. 2 is one piece of the set. The record for the set should be present in the same file and will have as its 001 record identifier:

77-10346. The agency creating the record does not make a note relating to the set in the record for the volume being catalogued and has therefore set the second indicator to 0. To produce an access point from this field, it may be necessary to find the record referred to in the 001 field. An access point point generated from the record to which this field points would appear as follows:

Countries of Europe, vol. 2

Ex. 3:

Embedded fields technique

422 #1$12001#$aWorld of knowledge

Ex. 4:

Standard subfields technique

422 #1$tWorld of knowledge

A serial World of knowledge has an annual supplement entitled World of knowledge annual. In the record describing the World of knowledge annual, a note is required to indicate this relationship. The source format records this information by linking to the item World of knowledge by means of a bibliographic title entered in UNIMARC Field 422 PARENT OF SUPPLEMENT. The note created from this field might read as follows:

Supplement to: World of knowledge

Ex. 5:

Embedded fields technique

430 #1$1001RI976423$1011##$a0199-4797$15301#$aLigand quarterly

Ex. 6:

Standard subfields technique

430 #1$0RI976423$x0199-4797$tLigand quarterly

A serial with a keytitle Journal of clinical immunoassay continues Ligand quarterly which had ISSN 0199-4797. In the record for Journal of clinical immunoassay a link is made to the previous title using key title and ISSN for identification. The record for that serial need not be in the same file. A note generated from this field might read:

Continues: Ligand quarterly. ISSN 0199-4797

or when the note is generated by a French language database:

Fait suite ŕ: Ligand quarterly. ISSN 0199-4797

Ex. 7:

Embedded fields technique

311 ##$aIncludes alternate issues of Mythprint. ISSN 0146-9347

423 #0$1011##$a0146-9347$12001# $aMythprint

Ex. 8:

Standard subfields technique

311 ##$aIncludes alternate issues of Mythprint. ISSN 0146-9347

423 #0$x0146-9347$tMythprint

A note which cannot be generated automatically from the linking field 423 is entered in a note field 311. The second indicator is set to 0.The note is not embedded in the 423 field.

Ex. 9:

Embedded fields technique

200 1#$aIm Auftrag des Königs$edie gefährlichen Abenteuer des Quentin Durward$fWalter Scott$gmit einem Nachwort von Traude Dienel$g[Bearbeitung einer Übersetzung von Oelkers aus dem Jahre 1831]

454 #1$150010$aQuentin Durward

700 #1$aScott,$cSir$bWalter,$f1771-1832

Ex. 10:

Standard subfields technique

200 1#$aIm Auftrag des Königs$edie gefährlichen Abenteuer des Quentin Durward$fWalter Scott$gmit einem Nachwort von Traude Dienel$g[Bearbeitung einer Übersetzung von Oelkers aus dem Jahre 1831]

454 #1tQuentin Durward

700 #1$aScott,$cSir$bWalter,$f1771-1832

Im Auftrag des Königs is a translation of Sir Walter Scott's Quentin Durward. A record for that work need not be in the same file. As a translation is catalogued under the name of the original author, the agency has not thought it necessary to include the author's name in the 454 field. A note generated from this field might read:

Translation of : Quentin Durward

Ex. 11:

Embedded fields technique

200 1#$aVariations on a theme of Bartók$efor string quartet$fMalcolm Lipkin

311 ##$aVariations on Bartók's Concertos, viola, orchestra, op.posth. Movement 1

488 #0$1700#1$aBartók,$bBéla,$f1881-1945$150010$aConcertos,$rviola, orchestra,$nop.posth. $hMovement 1

700 #1$aLipkin,$bMalcolm

Ex. 12:

Standard subfields technique

200 1#$aVariations on a theme of Bartók$efor string quartet$fMalcolm Lipkin

311 ##$aVariations on Bartók's Concertos, viola, orchestra, op.posth. Movement 1

488 #0$aBartók, Béla, 1881-1945$tConcertos, viola, orchestra, op.posth. Movement 1

700 #1$aLipkin,$bMalcolm

A note which cannot be generated automatically from the linking field 488 is entered in a note field 311. The second indicator of field 488 is set to 0.