UNITED STATES GOVERNMENT Memorandum LIBRARY OF CONGRESS

Similar documents
UNITED STATES GOVERNMENT Memorandum LIBRARY OF CONGRESS. Some of the proposals below (F., P., Q., and R.) were not in the original proposal.

SUBJECT: Language and Script instructions for Chapters 6 and 7. Related documents: 6JSC/MusicWG/13/LC response; RSC/LC/2/Appendix

SUBJECT: Revision to RDA (Number, date, location, of a conference, etc.)

RDA? GAME ON!! A B C L A / B C C A T S P R E C O N F E R E N C E A P R I L 2 2, : : 0 0 P M

[Draft] RDA Resource Description and Access

INTRODUCTION. RDA provides a set of guidelines and instructions on recording data to support resource discovery.

Meeting with UK Book Industry Representatives

Reconsidering DCRM in the light of RDA: A Discussion Paper

Barbara B. Tillett, LC Representative

RDA: a new cataloging standard for a digital future

6JSC/Chair/8 25 July 2013 Page 1 of 34. From: Barbara Tillett, JSC Chair To: JSC Subject: Proposals for Subject Relationships

Standards Committee, 15 June This report fulfills item 1 of the Task Force s charge:

Recommendations. A. Containers in RDA and JSC/ALA/21 August 8, 2012 page 1 of 9

REVISION LOG FOR PDF UPLOADS OF INSTRUCTION MANUAL FOR BRAILLE TRANSCRIBING UEB EDITION 2015

Background. Recommendations. SAC13-ANN/11/Rev. SAC/RDA Subcommittee/2013/1 March 8, 2013; rev. July 11, 2013 page 1 of 7

RECORD SYNTAXES FOR DESCRIPTIVE DATA

CMPS 10 Introduction to Computer Science Lecture Notes

Joint Steering Committee for Development of RDA. Related document: 5JSC/RDA/Scope/Rev

Standards Designation and Organization Manual

RDA ESSENTIALS. t h o m a s b r e n n d o r f e r. Chicago 2016

GIORGIANA TECUCI. Capacity Building Committee FIDIC

AACR3: Resource Description and Access

The print draft does appear long & redundant. (This was one of the criticisms voiced at ALA Midwinter 2006.)

Revision Log for Uploads of AN INTRODUCTION TO BRAILLE MATHEMATICS Using UEB and the Nemeth Code Provisional Online Edition 2017

Joint Steering Committee for Development of RDA

Comments Received and Their Disposition

5JSC/ACOC/1/Rev 7 August Joint Steering Committee for the Revision of AACR

Guidelines & Instructions for Manuscript Preparation

Joint Steering Committee for Development of RDA Dave Reser, LC Representative

Mary Lynette Larsgaard, Chair ALA/ALCTS/CCS Committee on Cataloging: Description and Access (CC:DA)

Research in Ireland Conference (THRIC)

UTF and Turkish. İstinye University. Representing Text

Kate Harcourt, Chair, Task Force on the Review of ISBD(G), 2003 revision. Report of the Task Force on the Review of ISBD(G), 2003 revision

RDA Serials Cataloging Update

IMPLICIT RELIGION Guidelines for Contributors March 2007

8.2. Name authority records and rules

Joint Steering Committee for Development of RDA. The attached document contains the guidelines followed by the Editor in drafting RDA.

Instructions for OCLC Local Holdings Maintenance

INTERNATIONAL STANDARD

Paper guidelines for the 7 th International Congress on Transportation Research

Joint Steering Committee for Development of RDA. Related document: 5JSC/RDA/Scope/Rev/4

AN INTRODUCTION TO BRAILLE MATHEMATICS

RDA Resource Description and Access

Transliteration of Tamil and Other Indic Scripts. Ram Viswanadha Unicode Software Engineer IBM Globalization Center of Competency, California, USA

Conversion of Cyrillic script to Score with SipXML2Score Author: Jan de Kloe Version: 2.00 Date: June 28 th, 2003, last updated January 24, 2007

6JSC/ALA/Discussion/4 [Transcription issues associated with the Production Statement (RDA 2.7]

Graduate School website:

E2.0 WRITING GUIDELINES for SPECIAL PROVISIONS (SPs)

Representing Characters and Text

TABLE OF CONTENTS. Reminder to Print or Save the June OPUS Report New Union List Migration Website...01

PCC BIBCO TRAINING. Welcome remarks and self introduction.

I want to start by reporting some of the most recent revisions to RDA, made by the JSC

EXAMPLES CATALOGING ELECTRONIC RESOURCES USING RDA RDA 201 CREATED BY BOBBY BOTHMANN

The Unicode Standard Version 11.0 Core Specification

Character Encodings. Fabian M. Suchanek

Task Force on Harmonization of ISBD(ER) and AACR2. Final Report

ICANN IDN TLD Variant Issues Project. Presentation to the Unicode Technical Committee Andrew Sullivan (consultant)

Joint Steering Committee for Development of RDA

How to Make Headers for APA, Section Breaks, Line Spacing, and Hanging Indents

The metadata content standard: RDA

Appendix C. Numeric and Character Entity Reference

Dissertation Formatting Rules. Basic Format

ISO TC46/SC4/WG7 N ISO Information and documentation - Directories of libraries and related organizations

Glossary AACR2. added entry ALA ALA character set ANSI. ANSI/NISO Standards for Holdings Data. accession number. archive record ASCII.

Wiley-Blackwell Geographical Analysis (GA) Content Style Sheet THIS DOCUMENT LAST UPDATED ON: 16/JUN/2011. Journal house style points

Conference Proposals Interface CPI Guidelines

Association for Library Collections and Technical Services (A division of the American Library Association) Cataloging and Classification Section

INSTRUCTIONS FOR TYPESETTING MANUSCRIPTS USING TEX OR L A TEX

Background and Implementation Issues

Checking and modifying I-level copy. Fields Checking Changing: AACRII Changing:RDA

R. Panchyshyn , rev

Committee on WIPO Standards (CWS)

TECHNICAL ADVISORY GROUP ON MACHINE READABLE TRAVEL DOCUMENTS (TAG/MRTD)

ICANN November Tina Dam Director, IDN Program

Communication Skills Center

Technical Writing. Professional Communications

Interdisciplinary Journal of Best Practices in Global Development Final Manuscript Preparation Guidelines

CP-147 Date 1999/01/30. Name of Standard: PS 3.3,

Friendly Fonts for your Design

RDA Editor s Guide. 2.1 Chapter numbers 2.2 Section numbers. 4.1 Hyphens and dashes 4.2 Lists 4.3 Examples

1. Overview of issues addressed in this document. 2. Discussion of some of the Issues. 2.1 Issues of internationalization

Joined up data and dissolving catalogues

World Digital Library Metadata with Crosswalks and Instructions *Bold elements are required

Two distinct code points: DECIMAL SEPARATOR and FULL STOP

Association for Library Collections and Technical Services (A Division of the American Library Association) Cataloging and Classification Section

Copyright. Trademarks Attachmate Corporation. All rights reserved. USA Patents Pending. WRQ ReflectionVisual Basic User Guide

A B Ɓ C D Ɗ Dz E F G H I J K Ƙ L M N Ɲ Ŋ O P R S T Ts Ts' U W X Y Z

RDA: Resource Description and Access

data elements (Delsey, 2003) and by providing empirical data on the actual use of the elements in the entire OCLC WorldCat database.

International Cataloging: Use Non-Latin Scripts

National Library 2

Title: Application to include Arabic alphabet shapes to Arabic 0600 Unicode character set

Using the RDA Toolkit

Localization Language Feature (5.3)

ISO/IEC JTC 1 N Replaces: ISO/IEC JTC 1 Information Technology

1. Introduction 2. TAMIL DIGIT ZERO JTC1/SC2/WG2 N Character proposed in this document About INFITT and INFITT WG

Cindex 3.0 for Windows. Release Notes

National Electrical Safety Code Manual of Style

Alignment of the ISBD: International Standard Bibliographic Description element set with RDA: Resource Description & Access element set

Background. 6JSC/ALA/22 June 17, 2013 page 1 of 11. Joint Steering Committee for Development of RDA John Attig, ALA Representative

Transcription:

UNITED STATES GOVERNMENT Memorandum LIBRARY OF CONGRESS 5JSC/LC/5 TO: Joint Steering Committee for Revision of AACR DATE: FROM: SUBJECT: Barbara B. Tillett, LC Representative RDA Part I Internationalization 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 The December 2005 draft addresses these aspects in varying degrees of completeness: (1) English language. 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. (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 II. below for the proposal for 1.5 and related instructions. (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. Although the second paragraph of 1.6.2 includes several elements where the guidelines in 1.6.2.1-1.6.2.5 apply, 2.9.0.3 (date of publication, distribution, etc.) is the only specific instruction to mention method of giving numerals. See I.A.-I.D., I.F. below for proposals related to numerals/dates. (4) Calendar. Instruction 1.6 lacks an instruction on the calendar in which a date is expressed. Instructions 2.6.0.3 (chronological designation for a serial) and 2.9.0.3 (date of publication, distribution, etc.) are the only instructions dealing with calendar. See I.E.-I.F. below for proposals related to calendar.

p. 2 I. Proposed revisions, etc. of 1.6 instructions and related rules in chapter 2 A. Proposed revision of 1.6.2 1.6.2. Numerals and nnumbers expressed as words and numerals When transcribing any titles (title proper, parallel title, other title information, variant title, etc.) and any statements of responsibility (including statements of responsibility relating to an edition statement, etc., or to a series, etc.), and any statement relating to edition, transcribe numerals and numbers expressed as words and numerals 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 words and numerals 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] Note: LC will recommend the deletion of Edition statement and Statement relating to a named revision of an edition from the list in the second paragraph above (and the addition to the first paragraph) in our response to the Draft of RDA Part I. We continue to support take what you see transcription of statements. Note: To allow the most flexibility in the option being proposed for addition to this instruction and in sub-instructions of 1.6.2, both add and substitute are included. LC acknowledges that the impact of replacing substituted information when doing copy cataloging may indicate that the option should be only to add information; however, we wish to allow institutions to either add or substitute. Instruction 1.6.2.3 in the current draft has substitute but not add. Note: LC reminds JSC that 1.6.2 will need to display with all the 1.6.2 sub-instructions in the Web version to indicate to which elements the sub-instructions apply. The alternative would be to add wording to each 1.6.2 sub-instruction referring to 1.6.2: for example, 1.6.2.2. Substitute Western-style arabic numerals for numbers expressed as words in the data elements listed in 1.6.2, second paragraph. B. Proposed revision of 1.6.2.1

p. 3 1.6.2.1. Roman numerals Substitute Western-style arabic numerals for roman numerals unless the substitution of arabic numerals 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). [example] Optionally, add or substitute numerals in the script preferred by the agency preparing the description. 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 uppercase roman numerals capitals appear in the resource. [example] C. Proposed revision of 1.6.2.2 1.6.2.2. Numbers expressed as words Substitute Western-style arabic numerals for numbers expressed as words. For chronograms, see 2.9.0.4. Optionally, add or substitute numerals in the script preferred by the agency preparing the description. D. Proposed revision of 1.6.2.3 1.6.2.3. Oriental Script of numerals Transcribe numerals in the script in which they appear on the source of information. Optionally, wwhen describing Arabic alphabet, Far Eastern, Greek, Hebrew, Indic, etc., resources that present numerals in a script not used by the agency preparing the description, add or substitute the 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), LC recommends deleting the option in 2.9.0.3. Either these instructions or an earlier instruction for the category of information already has wording following the general guidelines on transcription given under 1.6. See the proposed revision of 2.9.0.3 as given below under I.E.

p. 4 E. Proposed addition of 1.6.2.6 and revisions of 2.6.2.3 and 2.9.0.3 1.6.2.6. Calendar Transcribe dates as in 1.6.2. Optionally, when describing resources that present dates in a calendar not used by the agency preparing the description, add or substitute the dates in the calendar preferred by the agency preparing the description. Note: As noted earlier, 2.6.2.3 and 2.9.0.3 are the only two specific instructions with an option related to calendar. Rather than adding such an option to the other instruction (2.10.6.3) where it would be appropriate (not appropriate for 2.6.1.3), LC recommends deleting the options in 2.6.2.3 and 2.9.0.3 as shown below. Either these instructions or an earlier instruction for the category of information already has wording following the general guidelines on transcription given under 1.6, as noted above. 2.6.2.3. Recording chronological designations If the first and/or last issue or part of a serial is identified by a chronological designation, record it following the basic instructions on recording numbering (see 2.6.0.3). If the description is based on an issue or part other than the first and/or last, do not record the chronological designation. Optionally, if the chronological designation includes dates not of the Gregorian or Julian calendar, add the corresponding dates of the Gregorian or Julian calendar in square brackets. [remainder of instruction as given] 2.9.0.3. Transcription Transcribe the date of publication, distribution, etc., in the form in which it appears on the source of information, following the general guidelines on transcription given under 1.6. Optionally, if the date as it appears in the resource is known to be fictitious, follow it with the actual date. Supply a clarification of the date, enclosed in square brackets, as follows: a) if the date as it appears in the resource is known to be fictitious, follow it with the actual date 1798 [i.e. 1883] b) 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

p. 5 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. F. 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). II. Proposed revisions of 1.5 and related rules in chapter 2 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. LC also recommends the deletion of the paragraphs as shown because they could be read to be in conflict with each other and they are covered by the paragraph on notes. Proposed revisions for specific instructions related to the addition of information to a data element are given in II.B. below; the revision of 2.6.3 (adding a missing date) is given in II.C. below. 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. A. Proposed revision of 1.5

p. 6 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: 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. 7 B. Proposed revisions of chapter 2 instructions for adding information to a data element 1. 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. 2. Proposed revision of 2.6.5 2.6.5. New sequence of numbering [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) in the language and script of the new sequence of numbering. If this criterion does not apply, supply the term in the language and script of the title proper. Note: 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). 3. Proposed addition of new 2.10.6.4 and proposed revision of current 2.10.6.5 (as 2.10.6.6) Instruction 2.10.6.5 addresses new sequences of numbering for series. It refers to supplying a term in the language of the title proper of the series. It is the same situation as addressed in 2.6.5 above except that 2.10.6 lacks the counterpart provision to 2.6.1.4 (numeric designation is in more than one language or script). Below is the proposed 2.10.6.4 counterpart to 2.6.1.4 and then the proposed revision of current 2.10.6.5 (renumbered as 2.10.6.6). The additional instruction will require renumbering of current 2.10.6.4-2.10.6.7.

p. 8 2.10 6.4. Numeric and/or alphabetic designation in more than one language or script 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. 2.10.6.6. 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) in the language and script of the new sequence of numbering. If this criterion does not apply, supply the term in the language and script of the title proper of the series. See also 2.6.5. C. Proposed revision of 2.6.3 for adding a missing data element 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. Note: In its response to the Draft of RDA Part I, LC will include a general comment, for purposes of consistency, that language or script as found in some instructions (e.g., 2.6.2.4) should be changed to language and script.