DATE: June 8, 2001
REVIEW PERIOD: June 8-July 21
REVISED:
NAME: Multilingual Authority Records in the MARC 21 Authority Format
SOURCE: MARBI Multilingual Record Task Force
SUMMARY: This paper explores how to handle multilingual records in the MARC 21 authority format. Three models are discussed, along with recommendations from the MARBI Multilingual Record Task Force
KEYWORDS: Field 4XX (AD), Field 7XX (AD); Heading linking entry fields (AD); See from tracing fields (AD); Multilingual authority records
RELATED: 96-10 (July 1996), 97-10 (May 1997), DP100 (June 1997), DP108 (May 1998), DP109 (May 1998)
STATUS/COMMENTS
05/07/01 - Made available to the MARC 21 community for discussion.
6/18/01 - Results of the MARC Advisory Committee discussion - The majority of the participants favored the context marker model as the most productive approach. Further exploration and experimentation should be considered using the context marker model to ensure its usefulness and long-term applicability for libraries. Some wanted to explore a single record approach with Model C to allow for more flexibility. Another consideration is how the model works for subject records. A new discussion paper will be written that further explores the context marker model and the use of single or multiple records for the midwinter meeting.
Discussion Paper No. 2001-DP05: Multilingual authority records
MARBI asked the Multilingual Record Task Force to address the following questions, as they relate to the MARC 21 formats:
Among the aspects the Task Force was asked to consider are: exhibited needs, widely used cataloging standards, format changes, system implications, and retrospective conversion issues; the Task Force was also asked to be sensitive to the cost of implementing its suggestions.
As background the Task Force used MARC Discussion Papers 100, 108, 109, and 111. The Task Force analyzed a diverse group of issues, including current MARC 21 coding possibilities and limitations. The Task Force looked in detail at the need for coding the language of a heading, the language of a catalog, the script in which a heading is represented, the rules used to formulate a heading, the nationality of the entity represented by the heading, and the transliteration standards used to construct the heading-and the need for coding all of these at the subfield, field, and record levels. Members of the Task Force prepared complex examples of authority records showing various coding models. The majority of the members of the Task Force agreed on the following task definition, and general conclusions from which the recommendations emanate.
Task:
General conclusions:
The following terminology is used in this paper.
Established heading - A heading considered logically a 1XX in an authority record.
Alternative established headings (or alternative headings) - multiple equivalent established headings.
Language of catalog (or cataloging) - The language of the expected user population for the catalog. The language of the catalog establishes the foundation for the accompanying reference structure. The language found in heading qualifiers and record notes are usually indicative of the language of catalog for the record. The language(s) found in the heading itself may be a mix of languages, including the language of the catalog and other possibilities. In the MARC 21 format the primary way to indicate the language of catalog (or cataloging) is in the 040 $b subfield.
Language of heading - The language(s) used for the words of a heading.
The following examples illustrate the difference between the two language designations.
| William I, German Emperor, 1797-1888 | |
| Language of catalog: English Language of heading: English Source: Library of Congress NAF |
|
| Wilhelm, Deutsches Reich, Kaiser I, 1797-1888 | |
| Language of catalog: German Language of heading: German Source: Die Deutsche Bibliothek |
|
| Musee d'art et d'histoire de Fribourg | |
| Language of catalog: English Language of heading: French Source: Library of Congress NAF |
|
| Spain. Ministerio de Cultura. | |
| Language of catalog: English Languages of heading: English (place name) and Spanish (corporate body name) Source: Library of Congress NAF |
|
| Henry VIII, roi d'Angleterre, 1491-1547 | |
| Language of catalog: French Languages of heading: English and French Source: National Library of Canada, French catalog form |
|
| Soviet Union. Posolstvo (Egypt). Maktab al-Sihafah | |
| Language of catalog: English Languages of heading: English, Russian (transliterated), and Arabic (transliterated) Source: Library of Congress NAF |
2 MODELS EXAMINED
The Task Force began by examining two different families of record configurations,
those employing single authority records (this family of configurations is called
here Model A) and those employing linked authority records (Model B). After
looking in great detail at the implications of these models, the Task Force
developed a consensus for Model B because it is easier to manage different reference
structures that are appropriate when different cataloging codes or thesauri
are used in establishing headings. This recommendation is compatible with recent
conclusions of an IFLA working group on authorities. The Task Force also realized
that Model B may not be the preferred approach for some. To add flexibility,
the Task Force expanded the language centricism of Model B (as presented here)
to include the whole context of a heading. The expanded model is labeled Model
C below. The discussion below sketches Models A and B before discussing the
recommended Model C.
Model A
One authority record is constructed for each entity. The one established heading in the 1XX field is appropriate for a catalog using the language designated at the record level by the code in subfield $b (Language of cataloging) of the 040 field. The 4XX and 5XX traced reference headings constitute the reference structure for the 1XX heading.
Different forms of the 1XX heading (in other languages, scripts, etc.) are treated as variant reference headings and are traced in the 4XX fields. These 4XX variants may include the following types (parenthetical numbers refer to fields in the example below):
In this example, subfield $? contains an identification of the language
of catalog for the form described in (c) above. Subfield $? is only attached
to an alternate established heading intended for a catalog built around a different
language; its related reference tracings for the same language of catalog
are not so marked. (Diacritical marks are not shown in any of the examples in
this discussion paper.)
(1) 040 $a XXX $b eng $c XXX
(2) 100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.
[Form used in the Library of Congress catalog]
(3) 400 0# $a Cleopatre, $c Queen of Egypt, $d d. 30 B.C.
(4) 400 0# $a Kilyubatra, $c Queen of Egypt, $d d. 30 B.C.
(5) 400 0# $a Kleopatra, $c Queen of Egypt, $d d. 30 B.C.
(6 400 0# $a Kliyubatra, $c Queen of Egypt, $d d. 30 B.C.
(7) 400 0# $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? fre
[Form used in the Bibliotheque Nationale de France catalog]
(8) 400 0# $a Cleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
(9) 400 0# $a Kleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
(10) 400 0# $a <arabic form of name romanized according to French convention> $b VII
$c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
(11) 400 0# $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger
[Form used in the Deutsche Bibliothek catalog]
(12) 400 0# $a Cleopatra, $c Agypten, Konigin, $b VII
(13) 400 0# $a Kleopatra, $c die Grosse
(14) 400 0# $a <arabic name romanized according to German convention>, $c Agypten, Konigin,
$b VII
(15) 400 0# $a <name in Arabic script>, $c Agypten, Konigin, $b VII
(16) 400 0# $a <heading for Cleopatra in an Arabic catalog, formulated according to
appropriate convention> $? ara
[Form used in an Arabic language catalog]
(17) 400 0# $a <reference tracing(s) for heading in Arabic>
(18) 400 0# $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre
[Form used in the National Library of Canada French language catalog]
The complexity of the authority record grows considerably as additional alternate language of catalog forms, and variants of those forms, are added as reference tracings.
Model A has a number of limitations. It could lead to a very large number of reference tracing fields since several reference structures might be combined in a single record. This makes difficulties both for record management and for displays. There was also the feeling that cooperative maintenance of such records would be complicated. The model does not provide an easy way to distinguish multiple variants in the same language of catalog, such as a French form used in the National Library of Canada catalog and the form used in the Bibliothèque Nationale catalog.
Model B
An authority record is constructed for each separate established heading for an entity. The heading in the 1XX field is appropriate for a catalog in the language designated at the record level by the code in subfield $b of the 040 field. The 4XX and 5XX traced headings constitute the reference structure for the 1XX heading in that catalog.
As necessary, a cataloging agency constructs separate records that contain parallel 1XX established headings that differ in the language of the catalog into which they fit-for example, the French catalog version of a heading elsewhere represented for an English catalog. (If the heading and its reference structure would be the same for the different language catalogs, then one record might serve both purposes; but that is an implementation decision. For this discussion, Model B assumes that there are separate records.) Each authority record contains 4XX and 5XX reference tracing fields and 6XX note fields appropriate to the record level language of catalog coding in the 040 field.
Note: Separate records for alternative headings are not required, but if there are such records, the associated record numbers (subfield $0) may be recorded in 7XX fields. If there is no separate record then the 7XX may be primarily intended for alternative displays in OPACs. In this example the $? is again used to identify the language of catalog and since there are separate records with record numbers, the $0 has been included.
001 ea55555 040 ## $a XXX $b eng $c XXX 100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. 400 0# $a Cleopatre, $c Queen of Egypt, $d d. 30 B.C. 400 0# $a Kilyubatra, $c Queen of Egypt, $d d. 30 B.C. 400 0# $a Kleopatra, $c Queen of Egypt, $d d. 30 B.C. 400 0# $a Kliyubatra, $c Queen of Egypt, $d d. 30 B.C. 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? fre
$0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger 700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to appropriate convention> $? ara $0 aa66666 700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre
$0 cfa77777 001 fa44444 040 $a XXX $b fre $c XXX 100 0# $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) 400 0# $a Cleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) 400 0# $a Kleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) 400 0# $a <Arabic name romanized according to French convention> $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) 700 04 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? eng $0 ea55555 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger
$0 ga33333 700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to appropriate convention> $? ara $0 aa66666 700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre
$0 cfa77777 001 ga33333 040 $a XXX $b ger $c XXX 100 0# $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 400 0# $a Cleopatra, $c Agypten, Konigin, $b VII 400 0# $a Cleopatra, $c die Grosse 400 0# $a <Arabic name romanized according to German convention> $c Agypten, Konigin,
$b VII 700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? eng $0 ea55555 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? fre
$0 fa44444 700 04 $a <Heading for Cleopatra for an Arabic catalog, formulated according to appropriate convention> $? ara $0 aa66666 700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre
$0 cfa77777 001 aa66666 040 $a XXX $b ara $c XXX 100 0# $a <Heading for Cleopatra for an Arabic catalog, formulated according to
appropriate convention> 400 0# $a <Reference tracing(s) for heading in Arabic> 700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? eng $0 ea55555 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? fre
$0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger $0 ga33333 700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? fre
$0 cfa77777 001 cfa77777 040 $a XXX $b fre $c XXX 100 0# $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. 400 0# $w na $a Cleopatre $c reine d'Egypte, $d m. 30 av. J.-C. 700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? eng $0 ea55555 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? fre
$0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? ger $0 ga33333 700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate
convention> $? ara $0 aa66666
Model B has the advantage of separating the reference structures for the various headings for an entity, facilitating record maintenance and intelligible displays. A version of this model (without the language subfield) is used successfully by the National Library Canada today. However, Model B as shown above is designed as a method for handling records for headings in different languages of catalogs, and is therefore limited to that need. This distinction may not be the one needed, thus the Task Force developed Model C described below.
Model C (recommended)
Model C is the linked record model presented of Model B, but rather than defining the established headings and equivalent established headings solely in terms of the language of the catalog, they are defined by a catalog context. The context of a catalog is a composite entity. The primary component of the context is the body of rules under which the heading was formulated (e.g., AACR2, LCSH, RAK, RAMEAU, etc.). Additional components could be added; these might include an explicit indication of the language of catalog into which the heading fits (e.g., hun, eng, ger), or the audience for which the heading is useful (e.g., children, popular). In many cases there could be a default value for most elements that constitute the context-the default values being implicit in the rules themselves. (For example, RAK is a German cataloging code, which implies a German language catalog, so an indication of the catalog as German-when the language of catalog is indeed German-is not needed. But if RAK were the basis of a catalog designed for users of some other language the language of catalog would have to be indicated explicitly.)
As with Model B, an authority record is constructed for each separate established heading for an entity. Each heading is appropriate for the context designated at the record level by a combination of elements:
The 4XX and 5XX reference tracings in the record are appropriate to the 1XX heading in that context.
A cataloging agency may decide to include headings for the entity that are suitable in other contexts. These alternative established headings would be recorded in the 7XX fields in the authority record, along with an indication of the context in which they are appropriate. A cataloging agency may separately decide to create additional authority records in which the alternative heading(s) are the 1XX heading; such authority records would contain reference structures and 6XX note fields appropriate to the alternative context.
Note: Separate records for alternative context headings are not required, but if there are such records, the associated record numbers (subfield $0) may be recorded in 7XX fields. If there is no separate record then the 7XX may be primarily intended for alternative displays in OPACs.
In the following example, the context marker is contained in subfield $? with <context> its content. The possible content of this subfield is described in the subsequent section called Context Marking Technique. Since there are separate records with record numbers, the $0 has been included.
001 ea55555
008/10 (Cataloging rules): c (AACR2)
008/11 (Subject system/thesaurus rules): a (LCSH)
040 $b (Language of cataloging): eng (English)
100 0# $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.
400 0# $a Cleopatre, $c Queen of Egypt, $d d. 30 B.C.
400 0# $a Kilyubatra, $c Queen of Egypt, $d d. 30 B.C.
400 0# $a Kleopatra, $c Queen of Egypt, $d d. 30 B.C.
400 0# $a Kliyubatra, $c Queen of Egypt, $d d. 30 B.C.
700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
$? <context> $0 fa44444
700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context>
$0 ga33333
700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate
convention> $? <context> $0 aa66666
700 06 $a Cleopatre $b VII $c reine d'Egypte, $d 30 av. J.-C. $? <context>
$0 cfa77777
The 100 heading is appropriate for display in an English-language AACR2 catalog. The headings in the 700 fields are appropriate for display in catalogs whose contexts are identified in subfield $?.
001 fa44444
040 $e (Cataloging rules): ncafnor
040 $f (Subject system/thesaurus rules): ram (RAMEAU)
040 $b (Language of cataloging): fre (French)
100 0# $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
400 0# $a Cleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
400 0# $a Kleopatra $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
400 0# $a <Arabic name romanized according to French convention> $b VII
$c (reine d'Egypte ; $d 0069-0030 av. J.-C.)
700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? <context> $0 ea55555
700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context>
$0 ga33333
700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate
convention> $? <context>$0 aa66666
700 06 $a Cleopatre $b VII $c reine d'Egypte, $d 30 av. J.-C. $?<context>
$0 cfa77777
The 1XX heading is appropriate for display in a French-language catalog constructed using the Normes de catalogage publiees par l'AFNOR. The headings in the 700 fields are appropriate for displays in catalogs whose contexts are identified in subfield $?.
001 ga33333
040 $e (Cataloging rules): rak (RAK)
040 $b (Language of cataloging): ger (German)
100 0# $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30
400 0# $a Kleopatra $c Agypten, Konigin, $b VII
400 0# $a Cleopatra $c Agypten, Konigin, $b VII
400 0# $a Cleopatre $c Agypten, Konigin, $b VII
400 0# $a <Arabic name romanized according to German
convention> $c Agypten, Konigin, $b VII
700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C.
$? <context> $0 ea55555
700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030
av. J.-C.) $? <context> $0 fa44444
700 04 $a <Heading for Cleopatra in Arabic, formulated
according to appropriate convention> $? <context> $0 aa66666
700 06 $a Cleopatre $b VII $c reine d'Egypte, $d 30 av. J.-C. $? <context>
$0 cfa77777
The 100 heading is appropriate for display in a German-language Regeln fur die alphabetsche Katalogisierung catalog. The headings in the 700 fields are appropriate for displays in catalogs whose contexts are identified in subfield $?.
001 aa66666 040 $a XXX $b ara $c XXX 100 0# $a <Heading for Cleopatra for an Arabic, formulated according to appropriate
convention> 400 0# $a <Reference tracing(s) for heading in Arabic> 700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? <context> $0 ea55555 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? <context> $0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context> $0 ga33333 700 06 $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. $? <context>
$0 cfa77777 001 cfa77777 008/10 (Cataloging rules): c (AACR2) 008/11 (Subject system/thesaurus rules): v (Repertoire de vedettes-mati�re) 040 $b (Language of cataloging): fre (French) 100 0# $a Cleopatre $b VII, $c reine d'Egypte, $d m. 30 av. J.-C. 400 0# $w na $a Cleopatre $c reine d'Egypte, $d m. 30 av. J.-C. 700 00 $a Cleopatra, $c Queen of Egypt, $d d. 30 B.C. $? <context> $0 ea55555 700 04 $a Cleopatre $b VII $c (reine d'Egypte ; $d 0069-0030 av. J.-C.) $? <context> $0 fa44444 700 04 $a Kleopatra, $c Agypten, Konigin, $b VII $d av69-v30 $? <context>
$0 ga33333 700 04 $a <Heading for Cleopatra in Arabic, formulated according to appropriate
convention> $? <context> $0 aa66666
The 1XX heading is appropriate for display in a French-language catalog constructed using the AACR2 rules. The headings in the 700 fields are appropriate for displays in catalogs whose contexts are identified in subfield $?.
Because the notion of "context" may be adjusted to suit various situations, Model C is extensible and flexible, and has the following additional advantages:
3 CONTEXT MARKING TECHNIQUE
The "context" of a catalog was loosely defined by the Task Force to be the "view or user group for which the heading in the fields is appropriate." The context marker is a compound code that represents the context in which an equivalent heading might be substituted for the 1XX established heading in OPAC displays.
The proposed components of the context marker are the rules, audience or user population, and the language of the catalog. The components of the context marker could be carried in separate subfields, or combined into one. Since there are not sufficient subfields left in some heading fields, the Task Force recommends combining the components into a single subfield.
There is a technique already used with MARC 21 code lists to essentially identify the context of a code. A related technique could be used for the catalog context marker. In MARC Code Lists for Relators, Part IV: Subject/Index Term Sources, the source code is composed as follows:
<thesaurus>/<edition>/<language of thesaurus>
And in Part VI: Descriptive Conventions, the source code is composed as follows:
<rules>/<edition>
The thesaurus or rules code tells the context of the terms in a field, and the second (and third) parts of the designation essentially tell the context of the thesaurus or rules.
The context marker code needed for the Model C application could follow a similar model, along these lines:
<rules=cataloging code or thesaurus designation>/<audience>/<language of catalog>
Elements in the marker that do not apply will be omitted, but the neighboring slashes remain as place holders, with terminal slashes are omitted. For example, the code "rak" specifies the cataloging rules; this code does not contain an audience or language element; the code "aacr//fre" specifies the cataloging rules and language of catalog, but does not contain an audience element. Alternatively, the allowed codes could be considered one large list, in which case order would not matter but processing could be more complex.
The definition of a new subfield $7 (Context marker) in the authority 7XX fields is recommended to hold context information. Consideration was given to use of the existing subfield $2 (Source), but the Task Force felt it was important to preserve a distinction between the source of the heading and its context. The source indicates which thesaurus or file the heading comes from (e.g., the NAF file of name headings, South African National Bibliography file of headings, or the LCSH thesaurus of subjects). The context marker specifies the environment in which a heading is appropriate for display. In the case of the NAF file and the SANB file headings, the environment would be AACR data. In the case of LCSH, the environment would be subjects that follow the LCSH rules, since for that particular thesaurus the file and the rules have the same name. In addition the context marker needs to be repeatable whereas the source marker does not.
The context marker subfield would need to be repeatable so that a heading appropriate on multiple contexts will not need to be repeated. For example, many name headings without qualifiers might be valid in several different catalogs built for different languages. This argues also for making the record and 1XX heading level context markers repeatable. Thus 040 $b, $e, and $f would need to be made repeatable.
4 EXAMPLES
For simplicity, the following examples illustrative of Model C do not include subfield $0 in the 7XX fields (appropriate when a separate authority record exists for the alternate heading). Because they were easier to exhibit, these examples mostly show headings in different languages of cataloging; but the technique described here is intended to deal with alternate headings of all types: in different languages, in different scripts, different audiences, etc.
Example 1 - Multilingual name headings (no linked records illustrated)
008/10 (Cataloging rules): c (AACR2)
008/11 (Subject system/thesaurus rules): a (LCSH)
040 $b (Language of cataloging): eng (English)
100 0# $a John Paul $b II, $c Pope, $d 1920-
400 0# $a Joannes Paulus $b II, $c Pope, $d 1920-
400 0# $a Juan Pablo $b II, $c Pope, $d 1920-
400 0# $a Jean Paul $b II, $c Pope, $d 1920-
400 0# $a Johannes Paul $b II, $c Pope, $d 1920-
400 0# $a Joann Pavel $b II, $c Pope, $d 1920- <etc.>
510 2# $a Catholic Church. $b Pope (1978-: John Paul II)
700 04 $a Juan Pablo $b II, $c Papa, $d 1920- $7 aacr//spa
700 06 $a Jean Paul $b II $c pape, $d 1920- $7 aacr//fre
700 04 $a Jean Paul $b II $c (Pape), $d 1920- $7 ncafnor
700 04 $a Johannes Paul $c Papst, $b II $7 rak
700 04 $a <Chinese heading for John Paul> $b II $c <Chinese designation for Pope>
$d 1920- $7 aacr//chi
The 1XX heading is appropriate for use in an English-language AACR2 catalog. Three headings are appropriate for AACR-based but non-English language; "Johannes Paul <Papst, II>" is appropriate for a (German-language) RAK catalog; and "Jean Paul II (Pape), 1920-" is appropriate in a French-language AFNOR catalog.
Example 2 - Multilingual subject headings (no linked records illustrated)
008/10 (Cataloging rules): n (not applicable) 008/11 (Subject system/thesaurus rules): a (LCSH) 040 $b (Language of cataloging): eng (English) 150 ## $a Child psychology 450 ## $a Behavior, Child 450 ## $a Child behavior 450 ## $a Child study 550 ## $a Child development 550 ## $a Developmental psychology 550 ## $a Psychology 550 ## $a Child psychiatry 550 ## $a Child rearing 550 ## $a Educational psychology 750 #4 $a Kinderpsychologie $7 swd [Schlagwortnormdatei] 750 #4 $a Psicologia del nino $7 lcsh//spa 750 #4 $a <Korean translation of LCSH heading> $7 lcsh//kor 750 #2 $a Child Psychology $7 mesh
The 150 heading is appropriate for use in an English-language LCSH catalog. Two headings are appropriate for catalogs using simple translated LCSH headings; the heading "Kindpsychologie" is appropriate in a (German-language) Schlagwortnormdatei catalog; the heading "Child Psychology" is the equivalent MeSH heading.
Example 3 - Multilingual headings (linked records)
English-language heading
008/10 (Cataloging rules): c (AACR2)
008/11 (Subject system/thesaurus rules): a (LCSH)
040 $b (Language of cataloging): eng (English)
110 2# $a National Library of Canada. $b General Reference and Bibliography Section
410 2# $a National Library of Canada. $b Public Services Branch. $b General Reference
and Bibliography Section
510 2# $a National Library of Canada. $b Bibliography Section
510 2# $a National Library of Canada. $b General Reference Section
510 2# $a National Library of Canada. $b Reference and Bibliography Section
710 25 $a Bibliotheque nationale du Canada. $b Section de la consultation generale et de
la bibliographie $7 aacr//fre
The 110 heading is appropriate for display in an English-language AACR2 catalog. The 710 heading is the appropriate heading in a French-language AACR2 catalog.
French-language heading
008/10 (Cataloging rules): c (AACR2)
008/11 (Subject system/thesaurus rules): v (Repertoire de vedettes-mati�re)
040 $b (Language of cataloging): fre (French)
110 2# $a Bibliotheque nationale du Canada. $b Section de la consultation generale
et de la bibliographie
410 2# $a Bibliotheque nationale du Canada. $b Direction des services au public.
$b Section de la consultation generale et de la bibliographie
510 2# $a Bibliotheque nationale du Canada. $b Section de bibliographie
510 2# $a Bibliotheque nationale du Canada. $b Section de la consultation et de la
bibliographie
510 2# $a Bibliotheque nationale du Canada. $b Section de la consultation generale
710 25 $a National Library of Canada. $b General Reference and Bibliography Section.
$7 aacr//eng
The 110 heading is appropriate for display in a French -language AACR2 catalog. The 710 heading is the appropriate heading in an English-language AACR2 catalog.
Example 4 - Popular usage subject heading (no linked records)
008/10 (Cataloging rules): n (not applicable) 008/11 (Subject system/thesaurus rules): a (LCSH) 040 $b (Language of cataloging): eng (English) 150 ## $a Myocardial infarction 450 ## $a Heart $x Infarction 450 ## $a Heart attack 450 ## $a MI (Myocardial infarction) 550 ## $a Coronary heart disease 750 #4 $a Heart attack $7 local/popular/engThe 750 heading is appropriate for a catalog that uses locally-created popular terms.
Example 5 - Popular usage name heading (no linked records)
008/10 (Cataloging rules code): a (AACR2) 008/11 (Subject system/thesaurus): a (LCSH) 040 $b (Language of cataloging): eng (English) 100 10 $a Mellencamp, John, $d 1951- 400 10 $a Cougar, John, $d 1951- 400 10 $a Cougar, Johnny, $d 1951- 700 04 $a Mellencamp, John Cougar $7 local/popular/eng
The heading "Mellencamp, John, 1951-" is appropriate for use in an English-language AACR2 catalog. The heading "Mellencamp, John Cougar" would be more appropriate headings in an English-language catalog displaying locally-created popular language terms.
5 QUESTIONS
Library of Congress