RDA Training I: A Gentle Introduction Wichita State University Libraries Training plans RDA training I: Content covered ◦ ◦ ◦ ◦ ◦ ◦ A gentle introduction to RDA The main changes in RDA Terminology changes The new fields Examples: how to identify the RDA records Quick sheets for copy catalogers, serial catalogers and music catalogers ◦ RDA testing ◦ RDA Toolkit ◦ Discussion: some system and policy issues Training plans Other training sessions to be held at WSU Libraries: ◦ FRBR Training: a thorough introduction with many examples ◦ RDA II training: Get to the details and hands-on Interpretation of RDA rules Creation of RDA records Use of RDA Toolkit How RDA impacts department workflow? What is RDA? Resource Description and Access, is the new, unified cataloging standard; Designed for the digital world and an expanding universe of metadata users; Replace AACR2, but is not AACR3. RDA is based on IFLA’s international conceptual models and principles: ◦ Functional Requirements for Bibliographic Records (FRBR; 1998) ◦ Functional Requirements for Authority Data (FRAD; 2009) ◦ Statement of International Cataloguing Principles (ICP; 2009) RDA is a content standard, not an encoding standard (can use MARC 21, Dublin Core…). Main changes from AACR2 Move more towards international and developed for the future (including future systems) Designed for wider scope of resources (e.g. for non-print, non-text, unpublished resources) Move from classes of materials to elements and values (entities and attributes) Emphasize user needs/user tasks Built on entities “Work, Expression, Manifestation, Item” Emphasize relationships Main changes from AACR2 “Take what you see” (representation principle) Fewer abbreviations (clear for the users) Content, Media, and Carrier types (new) No more “rule of three” Sources for information expanded Controlled vocabularies available as registries for the semantic web Fundamental change: what makes it “RDA” (rather than “AACR3”) RDA is about recording entities, their attributes and relationships among them. Take “attributes” as “characteristics” or “metadata”; Relationships can be between resources, between creators and resources, and between creators. A glimpse into FRBR (Functional Requirements for Bibliographic One example: Records): ◦ Group I Entities: Work, Expression, Manifestation, Item ◦ Group 2 Entities: Persons, Families, Corporate Bodies ◦ Group 3 Entities: Concepts, Objects, Events, Places ◦ Mapping Attributes and Relationships to User Tasks: to Find, identify, select and obtain an entity ◦ w1 L. Frank Baum’s The Wizard of OZ e1 text and illustrations for the first edition m1 the book published in 1956 by Rand McNally i1 copy signed by the author Get an idea of what is in RDA • • RDA structure Section 1: Manifestation & Item Section 2: Work & Expression Section 3: Person, Family, & Corporate Body Section 4: Concept, Object, Event & Place 5 Recording Primary Relationships . . . ◦ Section 5: Between Work, Expression, Manifestation, & Item • 6-7 Recording Relationships to . . . ◦ Section 6: Persons, Families, & Corporate Bodies ◦ Section 7: Concepts, Objects, Events, & Places • AACR2 structure o 1-4 Recording Attributes of ◦ ◦ ◦ ◦ • • 8-10 Recording Relationships between . . . ◦ Section 8: Works, Expressions, Manifestations, & Items ◦ Section 9: Persons, Families, & Corporate Bodies ◦ Section 10: Concepts, Objects, Events, & Places o Chapter 1-13 Description (by categories) Chapter 21-26 Headings, Uniform Titles, and References Level of description AACR2 first level of description – title proper – first statement of responsibility – edition statement – material specific details – first publisher, etc. – date of publication, etc. – extent of item – notes – standard number AACR2 has first, second, and third levels of description; RDA has core elements and core if elements for entities. RDA core elements Identifying manifestations and items – – – – – – – – – – – – – title proper first statement of responsibility designation of edition designation of a named revision of an edition numbering of serials Date of production (for unpublished form) first place of publication first publisher’s name date of publication title proper of series/subseries numbering within series/subseries identifier for the manifestation carrier type Source of information • (AACR2) chief source of information • (RDA) preferred source of specified for each class of material: information specified for three categories of – books, pamphlets, and printed sheets resources: – – – – – – – – – – cartographic materials manuscripts music sound recordings motion pictures and video recordings graphic materials electronic resources three-dimensional artifacts and realia microforms continuing resources – – – Resources consisting of one or more pages, leaves, sheets, or cards moving images other resources • AACR2 specifies a chief source of information for each class of material; • RDA has fewer categories for sources and specifies a preferred source of information for each. Terminology changes: start to get used to RDA • AACR ◦ Physical description ◦ Notes ◦ Heading ◦ Main entry ◦ Added entries ◦ See references ◦ See also references ◦ Author ◦ Uniform title • RDA ◦ Describing carriers ◦ Describing content or Recording relationships ◦ Authorized access points ◦ Authorized access point for creator + preferred title ◦ Access points ◦ Variant access points ◦ Authorized access points for related entities ◦ Creator ◦ Preferred title or conventional collective title How to identify a RDA record MARC coding changes for RDA bibliographic records Leader/18: value “i” (ISBD) if using ISBD punctuation 040 $a ____ $b eng $c ____ $e rda Other clues: ◦ New fields: Content type (336); Media type (337); Carrier type (338) ◦ Spelt out descriptions (e.g. pages, illustrations…) How to identify RDA records: fixed field and 040 How to identify RDA records: new 3XX fields How to identify RDA records: new 3XX fields RDA new fields Three new fields-Replacement of GMD ◦ Content type: 336 ◦ Media type: 337 ◦ Carrier type: 338 Controlled vocabularies ◦ For media type and carrier type; ◦ Developed with ONIX community. Content type Content type ◦ RDA core element for expression ◦ new MARC field 336 Example: 336 $a text $2 rdacontent Can repeat either 336 field or $a. Use one or more of the terms in RDA 126.96.36.199 ◦ Examples: cartographic image, computer dataset, notated music, performed music, sounds, text, three-dimensional moving image… ◦ Other, unspecified Media type Media type ◦ LC core element for manifestation ◦ new MARC field 337 Media Type terms ◦ Audio, computer, microform, microscopic, projected, stereographic, unmediated, video; ◦ If not apply, use “other”; if not certain, use “unspecified”. Example: 337 $a unmediated $2 rdamedia ◦ Can repeat either 337 field or $a. Carrier type Carrier type ◦ RDA core element for manifestation ◦ new MARC field 338 Example: 338 $a volume $2 rdacarrier Can repeat either 338 field or $a. Carrier type terms Audio carriers Microform carriers filmstrip cartridge audio cartridge aperture card overhead transparency audio cylinder microfiche slide audio disc microfiche cassette Stereographic carriers audio roll microfilm cartridge stereograph card audiocassette microfilm cassette stereograph disc audiotape reel microfilm reel Unmediated carriers sound-track reel microfilm roll card Computer carriers microfilm slip flipchart computer card microopaque object computer chip cartridge Microscopic carriers roll computer disc microscope slide sheet computer disc cartridge Projected image carriers volume computer tape cartridge film cartridge video carriers computer tape cassette film cassette video cartridge computer tape reel film reel videocassette online resource film roll videodisc filmslip videotape reel filmstrip Extent The number and type of units and/or subunits making up a resource (MARC 300 subfield $a) No abbreviations for terms, e.g.,: “pages,” “volumes” Use “approximately” (not “ca.”) and “that is” (not “i.e.”) Use “unnumbered” rather than square brackets enclosing the numeral Changes in vocabulary from AACR2, e.g.: ◦ “study score,” not “close score” or “miniature score” ◦ “computer disc” for both “computer disk” and “computer optical disc” ◦ “sheet,” not “broadside” Extent, content and carrier type examples Book: 300 $a 123 pages, 28 unnumbered pages 336 $a text $2 marccontent 338 $a volume $2 marccarrier Music CD: 300 $a 1 audio disc 336 $a performed music $2 marccontent 338 $a audio disc $2 marccarrier DVD: 300 $a 1 DVD 336 $a two-dimensional moving image $2 marccontent 338 $a video disc $2 marccarrier Online PDF: 300 $a 1 online resource (39 pages) 336 $a text $2 marccontent 338 $a online resource $2 marccarrier Extent, content and carrier type examples Score: 300 $a 1 vocal score (xii, 300 pages) 336 $a notated music $2 marccontent 338 $a volume $2 marccarrier Map: 300 $a 1 map 336 $a cartographic image $2 marccontent 338 $a sheet $2 marccarrier Printed textual serial not yet complete: No 300 field 336 $a text $2 marccontent 338 $a volume $2 marccarrier Website (with maps, text, and photographs): 300 $a 1 online resource 336 $a text $a cartographic image $a still image $2 marccontent 338 $a online resource $2 marccarrier How to identify RDA records: lack of abbreviations How to identify RDA records: lack of abbreviations RDA representation principle:“Take what you see” In transcribing information, “Take what you see” and “accept what you get”: ◦ Capitalization, punctuation, abbreviations, inaccuracies, symbols, numerals Transcribe title: ◦ Don’t correct errors for monographs ◦ Do correct errors for serials and integrating resources to have a stable title ◦ For music works, some additions to title will no longer be abbreviated: arranged (not arr.), accompaniment (not acc.), unaccompanied (not unacc.) (e.g. Bennett, Sharon. Vocalises, unaccompanied) RDA representation principle: “Take what you see” Transcribe Statement of Responsibility: ◦ Transcribe as found, do not omit: titles of nobility, address, honour, initials of societies, dates of founding, mottoes… Transcribe edition: ◦ Transcribe as found: do not abbreviate or convert numerals Transcribe serial numbering: ◦ Serial: Transcribe terms and months as on the resource ◦ Alternative: follow local policy How to identify RDA records: capitalization How to identify RDA records: capitalization How to identify RDA records: transcribe typos in title How to identify RDA records: transcribe as found in Statement of Responsibility How to identify RDA records: date Phonogram copyright date Copyright date Use copyright date if neither date of publication nor date of distribution identified; Precede by copyright symbol (©), phonogram symbol (), or words “copyright” or “phonogram” if the symbol cannot be reproduced. Three ways of transcribing copyright date: ◦ 260 …, $c [date of publication not identified], ©2009. ◦ 260 …, $c . ◦ 260 …, $c , ©2009. How to identify RDA records: more than 3 added entries No more “rule of three” Statement of responsibility naming more than one person, family, or corporate body ◦ Transcribe as found, no more AACR2 “rule of three” ◦ Option: transcribe first name and give bracketed summary about information not transcribed (e.g. …[and three others]) ◦ Can have more than three added access points No limitation on recording medium of performance (no longer AACR2 “rule of three”) No “rule of three” when sessions held in three or more locations in creating authorized access points for conferences How to identify RDA records: publication place and publisher name Unidentified publisher, publication place or date If no probable place, give “[Place of publication not identified]” – not “[S.l.]” If no publisher identified, give “[publisher not identified]” – not “[s.n.]” If no probable date (very rare) for singlepart monographs, give “[date of publication not identified]” How to identify RDA records: selections Uniform title and selections RDA does not use “Selections” as a collective title; it is always appended to a preferred or collective title; RDA constructs analytical access points for all the parts individually (700 … $t); A conventional collective title (240) can be used in addition to the 700 fields (240 … $a Works. $k Selections…) How to identify RDA records: series numbering (and no abbreviation) Series numbering Numbering within series may include a numeral, a letter, any other character, or the combination of these, with or without an accompanying caption (volume, number, etc.) and/or a chronological designation; Record the numbering of the resource within the series as it appears on the source of information (e.g. volume 12, part 3, fasc. 1–2); If the series has more than one separate system of numbering, record the systems in the order in which they are presented. How to identify RDA records: the Bible Sacred Scripture and the Bible Choose as the preferred title for a sacred scripture the title by which it is most commonly identified in reference sources… In RDA, individual books and groups of books of the Bible are recorded as a subdivision of “Bible”, rather than as a subdivision of “O.T.”or “N.T.” (no more Bible. $p O.T.). How to identify RDA records: personal name headings Personal name headings: name with title/term Choose the form most commonly known; Variant spellings: choose the form found in the first resource received; For names containing a surname, include words, etc., indicating relationships (e.g., Jr., Sr., IV) -- not just to differentiate. How to identify RDA records: family as creators Family names In RDA, family names can be recorded as creators or others associated with a work, expression, manifestation, or item; In constructing authorized access points to represent a family, use the preferred name of the family, and code the attributes of families in MARC as follows: Type of family (100$a); Date associated with the family (100$d); Place… ($c); Prominent Member of the family (100$g) How to identify RDA records: corporate bodies Corporate bodies Retain frequency in the name of a conference, congress, or meeting; Omit the number and year of convocation from the name of an exhibition, fair, or festival; No “rule of three” when sessions held in three or more locations (separated by semicolons in access point); If conference held online, location is “Online” How to identify RDA records: translations Translations For resources that include expressions in more than one language, each expression will be given a separate access point; “Polyglot” is no longer used to designate a group of languages. How to identify RDA records: Relationship designators Relationship designators Recorded in bibliographic (1XX, 6XX, 7XX, and 8XX) and/or authority data (1XX, 4XX, 5XX). Persons, Families, and Corporate Bodies with resource ◦ Relationship designators in RDA appendix I ◦ Examples: Architect, artist, author, cartographer, choreographer, compiler, composer, designer, filmmaker, photographer, director, illustrator, editor… Between resources ◦ Relationship designators in RDA appendix J ◦ Examples: translation of (work), based on (work), abridgement of (work), adaptation of (work)… Between Persons, Families, and Corporate Bodies ◦ Relationship designators in RDA appendix K ◦ Examples: alternate identity, real identity, family member, sponsor… Other MARC format changes MARC 21 Format for Bibliographic Data ◦ New codes in 008: Code h - chorus score in Music 008/20 (Format of music) Code i - condensed score in Music 008/20 (Format of music) Code j - performer-conductor part in Music 008/20 (Format of music) ◦ New Codes in 007 Approved for Addition to MARC 21 to Accommodate RDA http://www.loc.gov/marc/007008changes-RDA.html MARC authority changes: new fields For RDA ch. 9 (Identifying Persons) elements: ◦ 046: special coded dates ◦ 370: associated place ◦ 371: address ◦ 372: Field of activity ◦ 373: affiliation ◦ 374: occupation ◦ 375: gender For RDA ch. 10 (Identifying Families) elements: ◦ 046: special coded dates ◦ 370: associated place ◦ 376: family information • • For RDA ch. 11 (Identifying Corporate Bodies) elements: 046: special coded dates 370: associated place 371: address 377: associated language Other 380: form of work 381: other distinguishing characteristics of work or expression 382: medium of performance 383: numeric designation of musical work 384: key If no separate MARC Field for a RDA element, give information in 670 field. RDA quick sheet for copy catalogers To identify RDA records, look for: ◦ Leader/18 value “I” (ISBD), 040 $a ____ $b eng $c ____ $e rda ◦ The three new fields: 336, 337 and 338; ◦ Transcribed as found (245 $a $c) (e.g. uppercases and typos in title, lengthy statement of responsibility); ◦ “[publisher not identified] etc in 260; ◦ Copyright symbol (©) and phonogram symbol () in 260 $c; ◦ Lack of abbreviations (300, 250…); ◦ No more “Rule of Three” (e.g. more than three for transcribed creators, added access points, conference locations…) ◦ Relationship designators (e.g. translation of …, adaptation of …) ◦ Search RDA records in OCLC: e.g., dx:rda and mt:bks and yr:2010 and kw:kansas RDA quick sheet for serial catalogers Correct typo in serial title (if encountered), an exception to “Transcribe as found” No supplied other title information (e.g., no $b [proceedings]) Transcribe volume, number, year and month as on the resource ◦ Alternative: follow local policy Record related works (772, 780, 785, 787) Record related expressions and manifestations (775, 776) Same as monographs: ◦ Leader/18 value “I” (ISBD), 040 $a ____ $b eng $c ____ $e rda ◦ The three new fields: 336, 337 and 338; ◦ Lack of abbreviations (300, 250…) ◦ Copyright symbol (©) and phonogram symbol () in 260 $c; ◦ No more “Rule of Three” (e.g. record more than three conference locations…) Search RDA serial records in OCLC: e.g. , dx:rda/ser/2010, or, dx:rda and mt:ser and yr:2010 RDA quick sheet for music catalogers Lack of abbreviations, use “arranged”, “accompanied” etc for additions to title and statement of responsibility; No “rule of three” for recording creators, the medium of performances and adding access points; “Works. Selections” used instead of just “selections” for a collection of works by a single composer containing various types of work for various mediums; Librettos now entered under the writer of the libretto, variant access point made under the composer. Search RDA serial records in OCLC: e.g. , dx:rda/sco/2010, or, dx:rda and mt:sco and yr:2010 (use “rec” for sound recordings and “vis” for visual materials) RDA testing Three national libraries in the U.S. ◦ Library of Congress ◦ National Agricultural Library ◦ National Library of Medicine Test partners ◦ Institutions that produce MARC 21 and/or non-MARC records (e.g. Columbia, Emory, Ohio State); ◦ Library professional associations (e.g. Music Library Association/Online Audiovisual Catalogers, Inc.); ◦ Library educators (e.g. GSLIS Group (Dominican University, University of Wisconsin-Milwaukee, University of Illinois at Urbana-Champaign); ◦ Vendors (e.g. OCLC Metadata Contract Services, Quality Books). RDA testing Timeline ◦ July 1-September 30, 2010 - test partners become familiar with the content of RDA and with navigating the RDA Toolkit ◦ October 1-December 31, 2010 – test partners produce records and share them with the Test Coordinating Committee ◦ January 1-March, 2011 – RDA Test Coordinating Committee analyzes records and prepares report for the three national libraries ◦ Now? Widespread adoption of RDA within the US is not expected until after the evaluation report is released. RDA Test Records: include Common Original Set (25), Common Copy Set (5) and Extra Set. Each test partner will create one record using RDA and one using AACR2 in Connexion. RDA Test Website: http://www.loc.gov/bibliographic-future/rda/ Records download: http://www.loc.gov/catdir/cpso/RDAtest/rdatestrecords.html Search RDA records in OCLC: dx:rda plus other term limits, e.g. dx:rda/2011/dlc, dx:rda and mt:bks and yr:2011 and kw:kansas To copy catalogers Accept RDA records in WorldCat as other records (not a parallel record); Be able to identify RDA records; Get familiar with RDA terminology and new fields; Be cautious in making corrections to RDA records; don’t change the typo in “title” field if it is what displays on the item; Check RDA Toolkit for RDA rules if necessary. RDA Toolkit RDA Toolkit: ◦ www.rdatoolkit.org What you can do in RDA Toolkit: ◦ Read, navigate and search the RDA documents (under “RDA” tab); ◦ Create your own profile; add and save your bookmarks; ◦ Read and search RDA instructions and encodings by entities (Under “Tools- Element set view”); ◦ Search RDA elements through MARC elements, or vice versa (Under “Tools- RDA mappings); ◦ Search MODS syntax through RDA elements. RDA Toolkit ◦ ◦ ◦ ◦ ◦ ◦ Create local workflow and make it sharable; consult shared workflows (under “Tools-Workflows”); Understand entities, attributes and relationships through diagrams (under “Tools- Entity Relationship Diagram (ERD)”); Download the RDA schema for XML data exchange (under “Tools-schemas”); Check old AACR2 rules; Consult Library of Congress Policy Statements (LCPS); Links to other resources including Open Archives Initiative, Open Metadata Registry, Cataloger's Desktop and XC Extensible Catalog. Discussion: some system and policy issues Update tag tables; New fields, their indicators, subfields and the controlled vocabularies; OCLC policy statement on RDA cataloging in WorldCat for the U.S. testing period: ◦ http://www.oclc.org/us/en/rda/policy.htm Do not implement authority changes until NACO testing is complete; How to work with vendor records? How does RDA affect our department workflow? References and resources • • • • • • • • Davis, Renette (2011). Serials & e-books in RDA. Oregon Library Association RDA 101 Preconference, April 6, 2011. Kandarasheva, Irina & Wilson, Mark (2011). Preparing Copy Catalogers for RDA. ALCTS RDA webinar. Maxwell, Robert. RDA in depth: differences between RDA and AACR2. Utah Library Association Annual Conference. Saint George, Utah, USA. May 7, 2010. http://www.rda-jsc.org/docs/RDA_part_2_201005.pdf RDA Documentation in RDA Toolkit: www.rdatoolkit.org RDA Library of Congress RDA test training materials: http://www.loc.gov/catdir/cpso/RDAtest/rdatraining.html Schiff, A. Changes from AACR2 to RDA: a comparison of examples, 2010. In BC Library Conference, Penticton, British Columbia, Canada,22 April 2010. http://eprints.rclis.org/handle/10760/14509 Tillett, Barbara. RDA changes from AACR2 for texts. The Library of Congress webcast. http://www.loc.gov/today/cyberlc/feature_wdesc.php?rec=4863 Tillett, Barbara & Kuhagen, Judith. RDA test “Train the Trainer” webcasts. http://www.loc.gov/bibliographic-future/rda/trainthetrainer.html Training materials created and compiled by Sai Deng, Metadata Cataloger, Wichita State University Libraries. Thanks Nancy Deyoe, Assistant Dean for Technical Services, for providing suggestions and guidance. Thank you!