Step 3.14

From AC Wiki
Revision as of 15:38, 4 April 2013 by Nate (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

JACKPHY Vernacular

The information in this section does not pertain directly to the profile steps, but it is important to your understanding of MARS 2.0 authority control processing.

MARS 2.0 provides special processing for JACKPHY bibliographic records: Japanese, Arabic, Chinese, Korean, Persian, Hebrew, Yiddish.

The MARS 2.0 process is designed to preserve all characters in bibliographic records that are designated for use in MARC records, including non-Roman sets.

JACKPHY Vernacular and 880 fields

The heading text of non-Roman headings is not converted during MARS 2.0 authority control due to the lack of a standard vernacular JACKPHY authority file.

The links between the vernacular headings (880) and romanized heading fields are maintained during MARS 2.0 processing.

If romanized heading fields are deleted or added (e.g., due to a split) the occurrence number in the $6 linkage is modified appropriately. Similarly, the linking tag portion of the $6 linkage is modified to reflect any tag conversions in the romanized heading fields.

An Associated Linked Field in $6 Not Found report (see Step 5.2, R18) is generated. This report lists all 880 fields which do not link to a romanized heading field due to incorrect data in the $6 linkage. All other 880 field data is untouched during processing.

MARS 2.0 processing does not convert the romanized portions of 880 headings due to the lack of integrity of the resulting headings.

However, a Linked Field in $6 Changed Heading (see Step 5.2, R86) report is available, which reports all tags that are linked to a vernacular tag with its linked romanized version of the tag changed in the MARS 2.0 process.

 original bib headings:
 100 1  $6 880-1 $a Atiman, Adriano, $d ca. 1864-1956.
 880 1  $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.
 The bibliographic heading in field 100 would match the See From tracing in the following LC n 82027709:
 100 1  $a Atiman, Adriano, $d 1864 (ca.)-1956
 400 1  $a Atiman, Adriano, $d ca. 1864-1956

MARS 2.0 converts the roman heading to the current form. The vernacular (880) heading would not be changed.

 The updated bibliographic record would contain the following headings and an entry would be added to report R86:
 100 1  $6 880-1 $a Atiman, Adriano, $d 1864 (ca.)-1956.
 880 1  $6 100-1 $a <chinese characters for Atiman, Adriano>, $d ca. 1864-1956.

Diacritics in JACKPHY

For JACKPHY personal names, MARS 2.0 includes certain diacritics to enhance the matching capability.

Often the only difference between two JACKPHY personal name headings is the presence or absence of a diacritic. A special JACKPHY normalization routine is used for JACKPHY bibliographic records.

MARS 2.0 assumes a bibliographic record may contain JACKPHY romanized headings if at least 1 out of the following 3 criteria is present:

  • Specific values in an 066 character set presence field that indicate use of a JACKPHY graphic character set: $1 in $a or $)1 in $b:
    • 066 $a $1
    • 066 $b $)1
  • 880 alternate graphic represent field exists
  • Non-roman language codes in field 008[35-37]

Diacritics retained

When a bibliographic record is identified as a probable JACKPHY record, the following diacritics (normally disregarded due to the normalization routine) are retained in the normalized headings:

  • Alif
  • Ayn
  • Breve
  • Circumflex
  • Hyphen
  • Macron
  • Umlaut

The preservation of these diacritics prevents matching a normalized JACKPHY personal name heading to the incorrect LC authority record.


3.1 - 3.2 - 3.3 - 3.4 - 3.5 - 3.6 - 3.7 - 3.8 - 3.9 - 3.10 - 3.11 - 3.12 - 3.13 - 3.14 - 3.15 - 3.16
1.0 - 2.0 - 3.0 - 4.0 - 5.0 - 6.0