Subfield code $6 - Linkage  (Appendix A:  Control Subfields)

Subfield $6 contains data that links fields that are different script representations of each other.  Subfield $6 may contain the tag number of an associated field, an occurrence number, a code that identifies the first script encountered in a left-to-right scan of the field, and an indication that the orientation for a display of the field data is right-to-left.  A regular (non-880) field may be linked to one or more 880 fields that all contain different script representations of the same data.  Subfield $6 is structured as follows:

$6[linking tag]-[occurrence number]/[script identification code]/[field orientation code]

Subfield $6 is always the first subfield in the field.

Descriptions of multiscript records, with examples, are in Appendix C; specifications for field 880 are under that field; specifications for character sets and repertoires for scripts are found in MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media.

Linking tag and occurrence number - The linking tag part contains the tag number of the associated field.  This part is followed immediately by a hyphen and the two-digit occurrence number part.  A different occurrence number is assigned to each set of associated fields within a single record.  The function of an occurrence number is to permit the matching of the associated fields, not to sequence the fields within the record.  An occurrence number may be assigned at random for each set of associated fields.  An occurrence number of less than two digits is right justified and the unused position contains a zero.

Example:

066  ##  $c)S

110  2#  $6880-15$a[Primary Name]

270  ##  $6880-05$a[Primary Address]

307  ##  $a[Hours, Etc.]

500  ##  $a[General Note]

531  ##  $6880-01$a[Eligibility, Fees, Procedures Note]

700  1#  $6880-22$a[Added Entry - Personal Name]

880  2#  $6110-15/)S$a[Primary Name]

880  ##  $6270-05/)S$a[Primary Address]

880  ##  $6531-01/)S$a[Eligibility, Fees, Procedures Note]

880  1#  $6700-22/)S$a[Added Entry - Personal Name]

[")S" = 29 hex 53 hex = Identification of the first alternate character set that will be encountered in the field.]

When there is no associated field to which a field 880 is linked, the occurrence number in subfield $6 is 00.  It is used if an agency wants to separate scripts in a record.  The linking tag part of subfield $6 will contain the tag that the associated regular field would have had if it had existed in the record.

Example:

110  2#  $6880-01$aHeading in Latin script

880  2#  $6110-01/(2/r$a[Heading in Hebrew script linked to associated field]

880  ##  $6531-00/(2/r$a[Eligibility, fees, procedures information in Hebrew script]

[The second 880 field is not linked to an associated field.  The occurrence number is 00.]

Script identification code - The occurrence number is followed immediately by a slash ( / ) and the script identification code.  This code identifies the alternate script found in the field.  The following codes are used:

Example:

880  1#  $6100-01/(N$a[Primary Name in Cyrillic script]

[The (N identifies the Cyrillic character set.]

These codes have been defined based on the MARC-8 coded character set escape sequences defined in accordance with ISO IEC 2022, "Character Code Structure and Extension Techniques" (equivalent to ANSI X3.41, "Code Extension Techniques for Use with 7-bit and 8-bit Character Sets").  The codes are described in MARC character set documentation.

In a Unicode environment, script identification codes may instead be taken from ISO 15924 "Codes for the representation of names of scripts".  Either the alphabetic values (consisting of four letters) or the numerical values (consisting of three digits) may be used.

Example:

880  1#  $6100-01/Cyrl$a[Primary Name in Cyrillic script]

880  1#  $6100-01/220$a[Primary Name in Cyrillic script]

The entire field need not be in the script identified in subfield $6.  If more than one script is present in the field, subfield $6 will contain the identification of the first alternate script encountered in a left-to-right scan of the field.

Note also that the script identification code is used in field 880, subfield $6, but this data element is not generally used for subfield $6 of the associated regular field.  In the associated field, the data is assumed to be the primary script(s) for the record.

Orientation code - In a MARC record, the contents of field 880 are always recorded in their logical order, from the first character to the last, regardless of field orientation.  For a display of the field, the default field orientation is left-to-right.  When the field contains text that has a right-to-left orientation, the script identification code is followed by a slash ( / ) and the field orientation code.  The MARC field orientation code for right-to-left scripts is the letter r.  The orientation code is only included in fields with right-to-left orientation, since left-to-right orientation is the default orientation in 880 fields.  (See MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media for a detailed description of field orientation.)

Example:

110  2#  $6880-01$a[Heading in Latin script]

880  2#  $6110-01/(2/r$a[Heading in Hebrew script linked to associated field]

[The r indicates the right-to-left orientation of the Hebrew script.]

Note that the orientation code is used in field 880, subfield $6, but this data element is not generally used for subfield $6 of the associated regular field.  In the associated field, the data is assumed to be the usual orientation of the primary script(s) for the record.

To return:

Use the key.

See also:

Appendix A:  Control Subfields