UNITED STATES GOVERNMENT Memorandum LIBRARY OF CONGRESS TO: Joint Steering Committee for Revision of AACR DATE: FROM: SUBJECT: Barbara B. Tillett, LC Representative RDA Part I Internationalization At the April 2006 JSC meeting, LC was asked to revise 5JSC/LC/5 to incorporate the decisions made at that meeting on some of the proposals in the document and to adjust the remainder of the document in the same context. JSC also made decisions for some instructions being revised for purposes of internationalization to change from transcribing information as found to recording information in a specified way with option(s) for different practice(s). Some of the proposals below (F., P., Q., and R.) were not in the original proposal. Background One of the concerns expressed at the 1997 International Conference on the Principles and Future Development of AACR in Toronto was that the focus of AACR2 on the Anglo-American community caused problems when implementing it in an international context. LC was asked, as the result of its comments related to internationalization for the November 2005 pre-draft of RDA Part I, to propose possible changes to the text of the December 2005 part I draft. Goal of proposal The context of AACR2 is English language, latin script, Western-style arabic numerals, and Gregorian/Julian calendar. The goal is to make RDA open to use by any community with a context other than English language, other than latin script, other than Western-style arabic numerals, and/or other than Gregorian/Julian calendar. Status of progress toward goal in December 2005 RDA Part I draft and draft of chapter 7 The drafts address these aspects in varying degrees of completeness: (1) English language. (a) Instruction 0.1.8 needs no further revision: Agencies preparing description for use in a different language context should modify such guidelines... to reflect their own language preferences and replace the English-language terms... Authorized translations of RDA will do likewise. (b) Instruction a)iv) under the first paragraph of 2.2.2 refers to choosing a source based on the language of that source. It is possible to see any modification of this instruction to be an internationalization issue to be solved by adding an option to use any other order of languages preferred by the agency preparing the description. However, the impact of applying such an option is likely to result in a different title proper (not a different transcribed form of the same title proper), thus affecting the citation/access point for that resource; LC recommends revising that instruction; see F. below.
p. 2 (c) Two instructions in the editor s draft of RDA chapter 7 (7.9.5.1 and 7.9.5.4) specify choosing the primary access point based on the English alphabetic order of the possible access points. Providing an option to use a different language preference will not work in these instructions because the resulting descriptions will have different primary access points. LC recommends revising those instructions, deleting 7.9.5.2, and also revising 7.9.5.3; see Q. and R. below. (2) Language and script of the description. Instruction 1.5 accommodates transcription of specific data elements in the found language/script. However, the option puts conditions on recording a transliterated form. The instruction on interpolations doesn t include supplying the complete data element. See A., B., G., I., J., L., M., and O. below. (3) Numerals/dates. Instructions 1.6.2.1 (Roman numerals), 1.6.2.2 (Numbers expressed as words), and 1.6.2.3 (Oriental numerals) only provide for arabic numerals and do not specify Western-style numerals. JSC decided to delete 1.6.2.1 and 1.6.2.2. JSC decided to change the principle of 2.6.0.3 (numbering of a serial) and 2.9.0.3 (date of publication, distribution, etc.) and to add other instructions to both. JSC decided to retain a revised 1.6.2.3 renumbered as 1.6.2.1 and will consider it again. See C., D., E., H., and K. below. (4) Calendar. Instruction 1.6 lacks an instruction on the calendar in which a date is expressed. However, instructions 2.6.2.3 (chronological designation for a serial), 2.9.0.3 (date of publication, distribution, etc.), and 2.10.6.4 (chronological designation as series numbering) are the only instructions where mention of calendar is appropriate; JSC decided to add a reference to 2.10.6.4 to refer to 2.6.2.3 instead of repeating the calendar information in 2.10.6.4. See N. below. (5) Measurement system. Instruction 3.5.0.4 specifies using metric units or inches depending on the common system of measurement for the particular type of carrier. That instruction goes on to refer to 3.5.0.3 where some categories have specific instructions about metric units or inches other categories refer to instructions later in the chapter. See P. below. A. Proposed revision of 1.5 LC notes that the switch in context from areas in AACR2 to data elements in RDA creates a gap when addressing adding a missing data element as opposed to adding information to a data element. To address that gap and to remove the term interpolations which has been confusing for many catalogers, LC recommends the suggested wording for the third paragraph in 1.5 below in addition to the revisions related to internationalization for that instruction. Also note that we suggest using transliteration in place of romanization as some countries may be going to another script than Latin. We acknowledge it is not technically encompassing (for example for Chinese characters) but could perhaps be explained as a shortcut term that is more neutral and more universal than romanization. 1.5. Language and script of the description Record the following elements in the language and script in which they appear on the sources from which they are taken:
p. 3 Title proper Parallel title Other title information Parallel other title information Variant title Earlier/later title Key title Statement of responsibility Parallel statement of responsibility Edition statement Statement of responsibility relating to the edition Statement relating to a named revision of an edition Statement of responsibility relating to a named revision of an edition Numeric and/or alphabetic designation Chronological designation Publisher, distributor, etc. Place of publication, distribution, etc. Date of publication, distribution, etc. Title proper of series Parallel title of series Other title information of series Statement of responsibility relating to series Numbering within series Subseries Optionally, add or substitute the data element(s) if any of the elements listed above cannot be recorded in the script used on the source from which it is taken, record it in a transliterated form. When adding to an element in the list Record interpolations into the elements listed above, record the addition in the language and script of the other data in the element unless the instructions for a specific element indicate otherwise. When supplying a missing data element, record the addition in the most appropriate language and script. Optionally, record the additions in the language and script preferred by the agency preparing the description. Record all other elements (including notes) in the language(s) and script(s) preferred by the agency preparing the description. When recording within a note a name or title originally in nonroman scripts, use the original script whenever possible rather than a romanization. Exception: Record a title or quotation incorporated into notes in the language and script in which it appears on the source from which it is taken.
p. 4 B. Proposed revision of 1.6.2 1.6.2. Numerals and nnumbers expressed as numerals or as words When transcribing a titles (title proper, parallel title, other title information, variant title, etc.) and a statements of responsibility (including statements of responsibility relating to an edition statement, etc., or to a series, etc.), or an edition statement, transcribe numerals and numbers expressed as numerals or as words in the form in which they appear on the source of information. Follow the guidelines in 1.6.2.1-1.6.2.6 1.6.2.5 below when recording transcribing numerals and numbers expressed as numerals or as words in the following elements: Edition statement Statement relating to a named revision of an edition Numeric and/or alphabetic designation Chronological designation Date of publication, distribution, etc. Numbering within series Optionally, add or substitute numerals in the script preferred by the agency preparing the description. Optionally, for early printed resources [remainder of option as given] [example] C. Proposed deletion of 1.6.2.1 1.6.2.1. Roman numerals Substitute arabic numerals for roman numerals unless the substitution of arabic numerals makes the statement less clear (e.g., when roman and arabic numerals are used in conjunction to distinguish the volume from the number in the series numbering). [example] When using roman numerals, give them in capitals except those used in paging or page references and those appearing in lowercase in the source of information or in quoted notes. Use lowercase roman numerals in paging or page references when capitals appear in the resource. [example] D. Proposed deletion of 1.6.2.2 1.6.2.2. Numbers expressed as words
p. 5 Substitute arabic numerals for numbers expressed as words. E. Proposed revision of 1.6.2.3 and renumbering as 1.6.2.1 (1.6.2.4 and 1.6.2.5 will need to be renumbered as 1.6.2.2 and 1.6.2.3) 1.6.2.13. Oriental Script of numerals Transcribe numerals in the script in which they appear on the source of information. Optionally, When describing Arabic alphabet, Far Eastern, Greek, Hebrew, Indic, etc., resources, add or substitute Western-style Arabic numerals for numerals in the vernacular script preferred by the agency preparing the description. [Note: The terms oriental and vernacular are sensitive terms to some communities, so we hope we ve found a way to avoid them. As noted earlier, 2.9.0.3 is the only specific instruction with an option related to script of numerals. Rather than adding such options to the other instructions (2.6.1.3, 2.6.2.3, 2.10.6.3), JSC decided to include a general instruction with option in 1.6.2 for script. JSC also decided to retain the option for script in 2.9.0.3.] F. Proposed revision of 2.2.2 2.2.2. More than one preferred source of information If there is more than once source of information that qualifies as the preferred source of information for that resource (as specified in 2.2.1), use as the preferred source of information the first occurring of those sources, unless one of the conditions below applies: a) Preferred sources of information in different languages or scripts If the resource contains preferred sources of information in more than one language or script, use as the preferred source of information (in this order of preference): i) the source in the language or script that corresponds to the language or script of the content or the predominant content of the resource ii) the source in the language or script of translation, if the resource contains the same work in more than one language or script and translation is known to be the purpose of the resource iii) the source in the original language or script of the content, if the resource contains the same content in more than one language or script and the original language or script can be identified iv) the first occurring of the sources. the source in the language or script that occurs first in the following list: English, French, German, Spanish, Latin, any other language using the roman alphabet, Greek, Russian, any other language using the Cyrillic alphabet, Hebrew, any other language using the Hebrew alphabet, any other language.
p. 6 [Note: Another approach would be to retain paragraph iv) as is and add option: Optionally, apply the priority order of languages preferred by the agency preparing the description. LC prefers the rule as shown above.] G. Proposed revision of 2.5.1.3 2.5.1.3 Recording edition statements Record the edition statement following the basic instructions on recording edition information (see 2.5.0). If an edition statement consists of a letter or letters and/or a number or numbers without accompanying words, add an appropriate word or abbreviation in the language and script of the title proper. [Note: ALA wanted this to say supply an appropriate word or abbreviation if considered to be important. Do we really need if considered to be important?] H. Proposed revision of 2.6.0.3 2.6.0.3. Transcription Transcribe Record numbering in Western-style arabic numerals as it appears on the source of information, following the general guidelines on transcription given under 1.6. Substitute Western-style arabic numerals for roman numerals unless the substitution makes the statement less clear (e.g., when roman and Western-style arabic numerals are used in conjunction to distinguish the volume from the number in the series numbering). Optionally, add or substitute numerals preferred by the agency preparing the description. [Note: We acknowledge that transcription is Tom s formula for the introductory provision at each data element, but it seems strange now to use it here, because JSC decided to record rather than transcribe. This may apply to other data elements beyond those in this document.] I. Proposed revision of 2.6.3
p. 7 2.6.3 No designation on first issue or part If the first issue or part of a serial lacks any numbering, but subsequent issues or parts define a designation pattern, supply numbering for the first issue or part based on that pattern. If information about designations of subsequent issues or parts is not available, record [No. 1]- (or its equivalent in the language and script of the title proper) or a chronological designation for the first issue or part, as appropriate. J. Proposed revision of 2.6.5 The current third paragraph of 2.6.5 refers to supplying a term in the language of the title proper. However, applying 2.6.1.4 for a numeric designation in more than one language or script can result in numbering not matching the language or script of the title proper. (Instruction 2.6.1.4 says to record the designation that appears first if there is not a designation matching the language and script of the title proper.) If so, the result of then applying the third paragraph of 2.6.5 could be a mixture of different languages and scripts (first sequence not matching the language/script of title proper and supplied term in language of title proper). 2.6.5. New sequence of numbering [retain first/second paragraphs with examples] If a new sequence with the same system as before is not accompanied by wording such as new series, supply [new ser.] or another appropriate term. (or its equivalent in the language of the title proper) [Note: ALA commented that the addition isn t required because it is covered by 1.5. That is true if one doesn t mind the result of a mixture of different languages and scripts (first sequence not matching the language/script of title proper and supplied term in language of title proper). LC does not feel strongly about adding this, and would like to hear from the other constituents.] K. Proposed revision of 2.9.0.3 2.9.0.3. Transcription Transcribe Record the date of publication, distribution, etc., in Western-style arabic numerals. the form in which it appears on the source of information, following the general guidelines on transcription given under 1.6. Optionally, supply a clarification of the date, enclosed in square brackets, as follows: a) add or substitute the date in the script preferred by the agency preparing the description if the date as it appears in the resource is known to be fictitious, follow it with the actual date
p. 8 1798 [i.e. 1883] b) transcribe the date in the form in which it appears on the source of information if the date as it appears in the resource is not in Western-style arabic numerals, follow it with the date in Western-style arabic numerals c) if the date as it appears in the resource is not of the Gregorian or Julian calendar, follow it with the date(s) of the Gregorian or Julian calendar. [Note: As in proposal H. above, we acknowledge that transcription is Tom s formula for the introductory provision at each data element, but it seems strange now to use it here, because the JSC decided that the basic instruction would be to record rather than transcribe. At least one of the options allows for transcription. This may apply to other data elements beyond those in this document.] L. Proposed revision of 2.9.0.4 2.9.0.4. Chronograms If the date of publication, distribution, etc., as it appears on the source of information is in the form of a chronogram, transcribe the chronogram as it appears. and follow it with the date in Western-style arabic numerals in square brackets. [example] Optionally, add or substitute the numerals represented by the chronogram in the script and calendar preferred by the agency preparing the description. Optionally, omit the chronogram from the date of publication, distribution, etc., element, recording only the supplied date in the script and calendar preferred by the agency preparing the description. Western-style arabic numerals in square brackets. Record the chronogram in a note if it is considered to be important for identification (see 2.9.6). M. Proposed addition of new 2.10.6.4 2.10.6 lacks the counterpart provision to 2.6.1.4 (numeric designation is in more than one language or script). The absence of the following provision means that the principle of selecting numbering when present in more than one language or script would vary between that for monographic series as a whole and for an analytic of that whole. The additional instruction will require renumbering of current 2.10.6.4-2.10.6.7. 2.10 6.4. Numeric and/or alphabetic designation in more than one language or script
p. 9 If the numbering appears on the source of information in more than one language or script, record the numbering that is in the language or script of the title proper of the series. If this criterion does not apply, record the numbering that appears first. N. Proposed revision of current 2.10.6.4 and renumbering as 2.10.6.5 2.10.6.54. Chronological designation If the resource has both a numeric and/or alphabetic designation and a chronological designation, record both the numeric and/or alphabetic designation and the chronological designation (see 2.6.2.3). A date of publication, distribution, etc., is not a chronological designation. O. Proposed revision of current 2.10.6.5 and renumbering as 2.10.6.6 2.10.6.65. New sequence of numbering If a new sequence of numbering is accompanied by wording to differentiate the sequence, such as new series, include this wording. If a new sequence of numbering with the same system as before is not accompanied by wording such as new series, supply [new ser.] or another appropriate term. (or its equivalent in the language of the title proper of the series) See also 2.6.5. [Note: As described above under J. for 2.6.5., ALA says the addition isn t required because it is covered by 1.5. That is true if one doesn t mind the result of a mixture of different languages and scripts (first sequence not matching the language/script of the title proper of the series and supplied term in language of title proper).] P. Proposed revision of 3.5.0.4 3.5.0.4. Measurements Record dimensions either in metric units (cm or mm) or in inches depending on the common system of measurement for the particular type of carrier. If there is no common system of measurement for the type of carrier being described, record the dimensions either in centimeters or in inches as indicated in the table under 3.5.0.3. Optionally, use the measurement system preferred by the agency preparing the description. [examples and remainder of instruction as given]
p. 10 Q. Proposed revision of 7.9.5.1, deletion of 7.9.5.2, and revision of 7.9.5.3 The proposed revision of 7.9.5.1 to remove the preference for English alphabetic order results in an instruction with the same outcome as that in 7.9.5.2. The revision below of 7.9.5.1 combines the situations of 7.9.5.1 and 7.9.5.2; because the instructions in 7.9.5.3 refer to 7.9.5.1 and 7.9.5.2 for choosing the primary access point, a revision of 7.9.5.3 is also given below. Renumbering of instructions 7.9.5.3+ as 7.9.5.2+ would be required, too. 7.9.5.1. Treaties, etc., between two or more three national governments For a treaty, or any other formal agreement, between two or three more national governments, 2 use the title (either the title proper or the preferred title for the treaty, see 13.6.X) as the primary access point. (in this order of preference): a) the access point for the government on one side if it is the only one on that side and there are two governments on the other b) the access point for the government whose access point is first in English alphabetic order. [examples to be revised] Provide an additional access point(s) for the other government(s). If the treaty, etc., is the product of an international conference, provide an additional access point for the conference. 2 National governments includes bodies exercising treaty powers such as Native American nations and African tribal governments. 7.9.5.2. Treaties, etc., between four or more governments For a treaty, or any other formal agreement, between four or more national governments, use the title (either the title proper or the preferred title for the treaty, see 13.6.X) as the primary access point. Provide additional access points for the other governments that are signatories to the treaty. If the treaty, etc., is the product of an international conference, provide an additional access point for the conference. 7.9.5.23. Agreements contracted by international intergovernmental bodies For agreements between an international intergovernmental body and a body or
p. 11 bodies falling into one or more of the following categories, use the title (either the title proper or the preferred title for the treaty, see 13.6.X) as the primary access point: choose the primary access point as instructed under 7.9.5.1 or 7.9.5.2 as appropriate: a) other international intergovernmental bodies b) national governments c) jurisdictions other than national governments d) other corporate bodies. [examples to be revised] If an agreement is contracted by the member governments of an international intergovernmental body acting as individual entities rather than collectively, treat the agreement as a treaty between governments following the instructions given under 7.9.5.1 or 7.9.5.2 as appropriate. R. Proposed revision of 7.9.5.4 (renumbered as 7.9.5.3) 7.9.5.34. Agreements contracted by the Holy See For a concordat, modus vivendi, convention, or other formal agreement between the Holy See and a national government or other political jurisdiction, use the title access point for the party whose access point is first in English alphabetic order as the primary access point. [revised examples] Provide an additional access points for the other partyies.