Arabic Script Cataloging

INTRODUCTION (published 11/2010)

An increasing number of MELA member libraries are using Arabic script in bibliographic records, despite the conspicuous absence of cataloging rules that apply specifically to Arabic-script fields.

In order to resolve this issue, most catalogers have tried to mirror the cataloging practices observed in Romanized fields, with slight adaptations. This has proven to be a workable solution, but has also resulted in some real variation of practice, particularly in non-Romanized, cataloger-supplied subfields (such as qualifiers).

The present document aims to regularize Arabic-script cataloging practice by setting down clear principles and by providing specific instructions for catalogers.

It is to be expected that the guidelines given here will eventually be superseded by new standards and methods of authority control, but we hope that in the meantime, the principles and instructions in this draft will be widely adopted and adhered to.

The benefits are obvious: library users searching in Arabic script will gain more reliable, and predictable access points; library professionals will find it easier to exchange bibliographic data.

  1. Scope

1.1. The guidelines in this document pertain to the descriptive fields in the bibliographic record which contain (or might contain) Arabic or Persian text in Romanization, as well as their subfields, regardless of language.

1.2. It does not therefore pertain to parts of the record that are peculiar to the catalog as a whole, such as Subject headings, or display constants in title added entries.

  1. Mandatory and optional elements

2.1. It is recommended that parallel script fields be provided for the MARC fields listed below, or their equivalents. Note that parallel script fields for notes and MARC 6xx fields are optional.

  1. Guidelines

3.1 Overriding Principles for all fields

  • Create parallel fields in original script using the same elements, in the same order as the Romanized form.
  • Do not apply this principle if would entail a violation of the grammatical or logical structure of the target language

3.2. Personal Name Headings (MARC 100/600/700)

  • Unless controlled by reference to an authority file, formulate name headings in original scripts according to the general principles and specific instructions set out below.

3.2.1 General principles:

  • Create parallel fields using the same elements, in the same order as the authorized form. Follow this principle also for names like “Avicenna” which are established in a commonly-used English form or nonstandard romanization.
  • Do not mix elements in original script with English ones. Wherever possible, provide equivalents for all non-transliterated elements in the Romanized field.
  • Refer to the appendices for a standardized listing of these elements (A.1.1-A.1.4 for Arabic, A2.1-A.2.4 for Persian).
  • If no standardized equivalent is given in the documentation, formulate a script element according to the principles set out herein, and alert the authors of the online cataloging manual.
  • Use Western Arabic numerals (1234567890 for ١٢٣٤٥٦٧٨٩٠)

3.2.2. Exception to general principles:

  • Do not follow the order of the authorized transliterated heading if its content or structure violates the nature of the name in the original language.
    • This situation may occur with names which are established from a commonly-used English form. When possible, rearrange the elements of the name. Do not provide additional elements.
  • For guidelines on formulating the title parts of author/ title entries, refer to 3.5. (‘Controlled Title Entries’) below.

3.2.3. Examples:

3.3. Corporate/ Conference Name Headings (MARC 110/111)

Unless controlled by reference to an authority file, formulate name headings in original scripts according to the general principles and specific instructions set out below.

3.3.1. General principles:

  • Do not mix elements in original script with English ones. Wherever possible, provide equivalents for all non-transliterated elements in the Romanized field.
  • Refer to the appendices for a standardized listing of these elements (A.1.1 through 4 for Arabic, A2.1. through 4 for Persian).
  • If no standardized equivalent is given in the documentation, formulate a script element according to the principles set out herein, and alert the authors of the online cataloguing manual.
  • Use Western Arabic numerals (1234567890 for ١٢٣٤٥٦٧٨٩٠)

3.3.2. Exception to general principles:

  • Do not follow the order of the authorized transliterated heading if its content or structure violates the nature of the name in the original language.
  • This situation may occur with corporate names which are established from a commonly-used English form. Whenever possible, restitute the original elements of the name. Do not provide additional elements.

3.3.3. Examples:

3.4. Uncontrolled Title Entries (MARC 245/ 246/ 247/ 740)

3.4.1. General principles:

  • Do not provide equivalents for display constants such as medium descriptors (MARC 245 $h) and display text (MARC 246 $i).
  • Enumeration and dates appearing in any of the subfields should be given in the form which appears on the source.

3.4.2. Examples:

A.1. Specific Instructions for Arabic language records:

A.1.1. Enumeration: Spell out ordinals, thus:

A.1.2. Titles: Use Arabic qualifiers. Follow usage when available, if supplied by the cataloger, qualifiers should be grammatically definite.

A.1.3. Dates: If present, mirror the use of dates in the Romanized field: Use Common Era dates in Western Arabic numerals (or, where present, Hijri dates in Western Arabic numerals). Use Arabic qualifiers, and expand alternative dates, thus:

A.1.4. Relator terms: Use Arabic relator terms, thus:

A.1.5. Form subheadings:

A.1.6. Arabic qualifiers for language subheadings:

A.2. Specific Instructions for Persian language records:

[to be provided]

Scroll to Top