1. 1 Emerging Standards and Guidelines Concerning Cataloging Charlene Chou Columbia University at the CEAL Committee of Technical Processing meeting Mar. 24, 2010

2. 2 Agenda Goal: the impact of emerging standards on the CJK cataloging or resource description IFLA (International Federation of Library Associations and Institutions) IFLA  International standards  Published guidelines  Emerging standards RDA (Resource Description & Access) RDA  The new, unified standard for resource description and access, designed for the digital world and an expanding universe of metadata users.  Testing  Initial evaluation

3. 3 National Bibliographies in the Digital Age: Guidance and New Directions Published by IFLA Bibliography Section in 2009 Standing Committee planning a satellite meeting prior to the 2011 IFLA conference, focusing on this guideline; International Bibliography Congress, 21-23 September 2010 in St. Petersburg, Russia National Diet Library (Mr. Yokoyama/Ms. Harai) on the SC  Japanese National Bibliography: one of the main activities  An article on the NDL Bibliographic Information Newsletter An article on the NDL Bibliographic Information Newsletter National Library of China  Chinese translation is done; NLC considering a national bibliography project: the guideline is useful for planning National Library of Korea Hopefully, promote the usage of the guidelines in East Asia

4. 4 National Bibliographies in the Digital Age: Guidance and New Directions Classification & Indexing Section Working Group on Guidelines for Subject Access by National Bibliographic Agencies  To publish a comprehensive indexing policy that would assist national bibliographic agencies providing appropriate subject access data in their bibliographies  Open access to national bibliographies (this year’s theme for the Bibliography Section)  Your inputs for CJK are very welcome.

5. 5 Classification & Indexing Section: new publication Guidelines for Multilingual Thesauri  WG: 1999-2008, approved by the Section on 12/12/08  Linking and mapping practice: an example of multilingual linking project: MACS (Multilingual Access to Subjects) European cooperation by Swiss National Library, Bibliotheque nationale de France, British Library & Deutsche Bibliothek Develop a web-based link and search interface through which equivalents between three subject heading languages— SWD/RSWK (German), RAMEAU (French) & LCSH (English) LMI (Link Management Interface) available since 2001  A research model for CJK languages?

6. 6 IFLA Namespaces Task Group Goal:  Preparing a “requirements and options” paper on the management of IFLA bibliographic standards in relation to the Semantic Web Recommendations:  A technical group to coordinate/maintain IFLA standards  Develop a standards portal  Dereferencing services  Version control  Third-party namespace maintenance services

7. 7 Bibliographic Control Division FRSAR Working Group ( Functional Requirements for Subject Authority Records) FRSAR Working Group  Introducing FRSAD and Mapping it with SKOS and other models Introducing FRSAD and Mapping it with SKOS and other models International Cataloguing Principles (ICP)  IFLA Cataloguing Principles: Statement of International Cataloguing Principles (ICP) and its Glossary (print version) IFLA Cataloguing Principles: Statement of International Cataloguing Principles (ICP) and its Glossary  The Statement of ICP (Online version) The Statement of ICP  Translations including CJK languages From FRBR to FRAD: Extending the Model

8. 8 UNIMARC Section UNIMARC, RDA and the Semantic Web by Gordon Dunsire UNIMARC, RDA and the Semantic Web  To discuss the application of RDA, as a content standard for metadata encoded in UNIMARC  Making components of RDA and associated models such as FRBR & FRAD compatible with the Semantic Web  DCMI RDA Task Group: expressing RDA controlled vocabularies in SKOS, and the RDA metadata structure elements in RDFS.  FRBR Review Group: expressing FRBR in RDFS  LC: making LCSH available in SKOS  VMF project: likely to express the extended RDA/ONIX ontology in RDFS and SKOS

9. 9 Information Technology Section Not (just) a Repository, nor (just) a Digital Library, nor (just) a Portal: A Portrait of Europeana as an API Not (just) a Repository, nor (just) a Digital Library, nor (just) a Portal: A Portrait of Europeana as an API  A single access point to the digital contents  So far, more than 4M items  Aggregation organization model—the portal of portal  API is a strong requirement for an interaction between Europeana portal and partners discovery applications Europeana  API interface defines the way by operating with another system requesting information. A research model for the portal of East Asian materials?

10. 10 RDA Testing Columbia University is one of testing institutions, and includes testing CJK, laws, serials, and non-MARC (metadata) records.

11. 11 RDA Testing RDA Test “Train the Trainer” on 1/15/10 RDA Basecamp (Testers’ website) with all related documents Training manual and documents:  Comparison between AACR2 & RDA RDA core elements (core & core if…)  Choices in RDA LC proposed practice for the RDA test 163 options and alternatives in RDA (alternative/optional omission/optional addition)  Exercises

12. 12 RDA Testing Timeline is changing, probably this summer RDA testing cataloging decisions  Common set titles 25 titles (10 textual monographs; 5 audio-visual; 5 serials-print or other; 5 integrating resources) All titles will be in English; items with parallel languages may be included Each institution catalogs one common set by two different persons—one using RDA; another one using the current codes Only descriptive elements; no subject analysis is to be done No searching of local or national database

13. 13 RDA Testing RDA testing cataloging decisions  Regular materials: 25 titles using RDA Catalog these materials using normal procedures, e.g. perform authority work if normally does so Catalog these materials to accommodate MARC21 changes related to RDA If a testing institution is a PCC member, provide PCC coding  Decisions: LC will host the site containing all the test RDA records, and work with OCLC to resolve the technical issues for record transferring. Submit records for common set and regular titles to LC for analysis by the Testing Coordinating Committee Each institution must submit a survey response for each record Via email, B. Tillett has agreed to include CJK titles for RDA training examples.

14. 14 MARC21 new & updated tags Bibliographic records  Leader/18: “i”  033—Date/Time, and place of event [LC: TBD]  040 $e rda  260 $c—give “copyright date” after publication date  336--content type; 337--media type; 338--carrier type  380-384: Form of work, medium of performance & numeric designation, etc. [LC policy to be decided]  518—Date/Time and place of event note [LC: TBD]  533/776: Wait for LC decision on reproduction policy

15. 15 MARC21 new & updated tags Authority records  008/10—Descriptive cataloging rules: use “z” (other) [A value is not defined for RDA]  040 $e rda  046 $k Beginning or single date created [TBD]  046 $l Ending date created [TBD]  370--Associated place; 371—Address; 372—Field of activity; 373—Affiliation; 374—Occupation; 375— Gender; 376: Family information; 377—Associated languages [used to be 670; implementing the FRAD]  380-384: Form of work; Other characteristics; Medium of performance; Numeric designation of a musical work; key [TBD]  500-530: $4—relationship code; $w/0 “r”—control subfield

16. 16 New: identifying families (authority records) RDA 8.1.2=“two or more persons related by birth, marriage, adoption, etc. Scope:  Now considered creators, contributors, etc.  Important for archives, museums, and special collections Examples:  100 3# Ingebretson (Family) 376 ## Family  Date associated with the family (RDA 10.4) 046 ## 1925 $t 1976 100 3# Pahlavi (Dynasty : $d 1925-1979) 376 ## Dynasty  Place associated with the family 046 ## 1529 $t 1739 100 3# Nayak (Dynasty : $d 1529-1739 : Madurai, India) 370 ## Madurai, India 376 ## Dynasty

17. 17 RDA: my observations and analysis Pros  Transcribe what it appears on piece  No more Latin abbreviations  FRBRized structure  More detailed publishing information  More options  More fields for authority control and manipulation  Flexible for other metadata (non-MARC) Cons  Much more spellings: macros to handle  Technical difficulties RDA Toolkit: no CJK examples More fields to code: really necessary ($0)?  More local decisions?  Confusing: makeup titles; publishing information, etc.  How about legacy data?  Make cataloging process more efficient or harder?

18. 18 Examples: Easier for users: no more S.l. & s.n.  260 [Place of publication not identified] : $b [publisher not identified], $c [date of publication not identified] Confusing for users:  Copyright date 260 [Des Moines?] : $b Iowa Department of Transportation, $c [date of publication not identified], c2009.  Compilation of works by different creators RDA with alternative for devised title  245 [Two political science studies]  245 [Two United States Midwest memoirs] 505 Community band concerts / Sharon Polk. Fall harvest festivals / Terri Swanson. RDA without alternative for devised title  245 Community band concerts /$c Sharon Polk. Fall harvest festivals / Terri Swanson.

19. 19 Thanks! Q & A