Jerry Falwell Library RDA Copy Cataloging

Similar documents
RDA Toolkit, Basic Cataloging Monographs

An introduction to RDA for cataloguers

Alyssa Grieco. Cataloging Manual Descriptive and Subject Cataloging Guidelines

Physical description (300)

RDA vs AACR. Presented by. Illinois Heartland Library System

E-Book Cataloging Workshop: Hands-On Training using RDA

RDA: The Inside Story

RDA Ahead: What s In It For You? Lori Robare OVGTSL May 4, 2012

Cataloging Fundamentals AACR2 Basics: Part 1

RDA: Resource Description and Access

Fundamentals of RDA Bibliographic Description for Library Linked Data

3/16/16. Objec&ves of this Session Gain basic knowledge of RDA instructions. Introduction to RDA Bibliographic Description for Library Linked Data

Subject: RDA: Resource Description and Access Constituency Review of Full Draft Workflows Book Workflow

OLA Annual Conference 4/25/2012 2

And why should I care? Denise A. Garofalo. SLMSSENY Conference May 1, 2015

RDA, FRBR and keeping track of trends in cataloguing

RDA for Copy Cataloging

RDA: Changes for Users and Catalogers

Continuities. Serials Catalogers Should Take the Plunge with RDA. By Steve Kelley

18 - Descriptive cataloging form One-character alphanumeric code that indicates characteristics of the descriptive data in the record through

Agenda. Conceptual models. Authority control. Cataloging principles. New cataloging codes

MARC Manual. Created by PrairieCat: August 4, 2014, revised May 11th, P a g e

Copy Cataloging New Monographs: Fields to Check: AACR and Hybrid Records

One example of how technology has made a major difference in library operations is that card catalogs have morphed to

RDA for Copy Catalogers: The Basics. Vicki Sipe Wednesday 9 Sept 2015

DRAFT UC VENDOR/SHARED CATALOGING STANDARDS FOR AUDIO RECORDINGS JUNE 4, 2013 EDIT

RDA Simplified. Available online: 03 Oct 2011

Launching into RDA : Patricia Sayre-McCoy. Head of Law Cataloging and Serials D Angelo Law Library University of Chicago

Not Cataloging an Early Printed Book Using RDA

Development and Principles of RDA. Daniel Kinney Associate Director of Libraries for Resource Management. Continuing Education Workshop May 19, 2014

AACR2 versus RDA. Presentation given at the CLA Pre-Conference Session From Rules to Entities: Cataloguing with RDA May 29, 2009.

RDA FAQ. PALS Acq/Cat/Ser Workday April 9, 2010 Metro State Sarah Quimby

Editing Checklist Books

Differences Between, Changes Within: Guidelines on When to Create a New Record

Cataloging with a Dash of RDA. Part one of Catalogers cogitation WNYLRC, June 20, 2016 Presented by Denise A. Garofalo

Cataloguing Code Comparison for the IFLA Meeting of Experts on an International Cataloguing Code July 2003 PARIS PRINCIPLES

Editing Checklist Sound recordings

RDA is Here: Are You Ready?

Titles. Title Statement and Variant Titles

Professor Suchy, Joliet Junior College Library

Making Serials Visible: Basic Principles of Serials Cataloging

Publication Information

Introduction to FRBR: Functional Requirements for Bibliographic Records

What s New in RDA? Daniel Kinney Associate Director of Libraries for Resource Management. Continuing Education Workshop May 19, 2014

Jumping into RDA Texas Library Association 2013 Annual Conference

An Introduction to FRBR, RDA, and Library Linked Data INFORMATION ORGANIZATION MOVES INTO THE 21 ST CENTURY: FRBR, RDA, LLD

Background. CC:DA/ACRL/2003/1 May 12, 2003 page 1. ALA/ALCTS/CCS Committee on Cataloging: Description and Access

Bibliographic Data: A New Context. Karen Coyle

Catalogues and cataloguing standards

Copy Cataloging in ALMA ( )

Hitting the Right Note composing and arranging RDA

Visualizing RDA for Public Services

RECORD SYNTAXES FOR DESCRIPTIVE DATA

What it is and what you need to know. Outline

RDA: Resource Description and Access Part I - Review by other rule makers of December 2005 Draft - Germany

Cataloguing Code Comparison for the IFLA Meeting of Experts on an International Cataloguing Code July 2003

AACR2 s Updates for Electronic Resources Response of a Multinational Cataloguing Code A Case Study March 2002

Serials: FRBR and Beyond

RDA Music Records Comparison

The MARC Record & Copy Cataloging. Introduction ILLINET/OCLC October 2008

RDA Part I - Constituency Review of December 2005 Draft - Response Table

Metadata FRBR RDA. BIBLID (2008) 97:1 p (2008.6) 1

Series Authority Procedures for Copy Cataloging

1. PARIS PRINCIPLES 1.1. Is your cataloguing code based on the Paris Principles for choice and form of headings and entry words?

Updates from the World of Cataloguing

RDA and Music Discovery

Pre-conference Workshop of the NOCALL Spring Institute 2011 Friday, April 8, 2011, 9:00 am - 11:45 am Sir Francis Drake, San Francisco, California

Abstract. Justification. 6JSC/ALA/45 30 July 2015 page 1 of 26

Guidelines for Cataloging Vernacular Music Manuscripts

Discovery has become a library buzzword, but it refers to a traditional concept: enabling users to find library information and materials.

Strategies for implementation

Bibliographic Standards Committee: Saturday, June 26, 8:00am-12:00pm Washington Plaza (Adams)

MARC. stands for MAchine Readable Cataloging. Created according to a very specific

Organization of Knowledge LIS Assignment #3 OCLC & MARC Bibliographic Format Beth Loch February 11, 2012

INFS 427: AUTOMATED INFORMATION RETRIEVAL (1 st Semester, 2018/2019)

ISBD(ER): International Standard Bibliographic Description for Electronic Resources Continued

To: Joint Steering Committee for Development of RDA. From: Damian Iseminger, Chair, JSC Music Working Group

Definition. General or specialized information relating to a work.

Harmonization of AACR and ISBD (CR)

SHARE Bibliographic and Cataloging Best Practices

Catalogs, MARC and Other Metadata

Resource Description and Access (RDA) The New Way to Say,

Authority Control -- Key Takeaways & Reminders

Session 2: Description

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

INTRODUCTION TO. prepared by. Library of Congress Acquisitions and Bibliographic Access Directorate. (Internet:

Basic Cataloging of Scores in RDA

Cooperative Cataloging in Academic Libraries: From Mesopotamia to Metadata

They Changed the Rules Again?

Editing Checklist Audio recordings

6JSC/Chair/8/DNB response 4 October 2013 Page 1 of 6

RDA RESOURCE DESCRIPTION AND ACCESS

SCIS STANDARDS FOR CATALOGUING AND DATA ENTRY

Converting and Reconciling. Sally McCallum, Library of Congress European BIBFRAME Workshop Florence, Italy September 2018

Do we still need bibliographic standards in computer systems?

Preparing for RDA at York University Libraries. Wednesday, May 1, 2013 Marcia Salmon and Heather Fraser

Implementation of RDA in the OPAL Consortium

Report. General Comments

MINITEX/OCLC MAILING

Resource Description and Access

Transcription:

Liberty University DigitalCommons@Liberty University Faculty Publications and Presentations Jerry Falwell Library 3-2014 Jerry Falwell Library RDA Copy Cataloging Anne Foust Liberty University, adfoust2@liberty.edu Follow this and additional works at: http://digitalcommons.liberty.edu/lib_fac_pubs Part of the Cataloging and Metadata Commons Recommended Citation Foust, Anne, "Jerry Falwell Library RDA Copy Cataloging" (2014). Faculty Publications and Presentations. 94. http://digitalcommons.liberty.edu/lib_fac_pubs/94 This Presentation is brought to you for free and open access by the Jerry Falwell Library at DigitalCommons@Liberty University. It has been accepted for inclusion in Faculty Publications and Presentations by an authorized administrator of DigitalCommons@Liberty University. For more information, please contact scholarlycommunication@liberty.edu.

JERRY FALWELL LIBRARY RDA Copy Cataloging Guidelines

About RDA RDA stands for Resource Description Access. It is a set of guidelines and instructions covering all types of content and media, the cataloging standard which now replaces AACR2. It was implemented by the Library of Congress April 1, 2013. Underlying RDA are the conceptual models FRBR (Functional Requirements for Bibliographic Records) and FRAD (Functional Requirements for Authority Data). RDA is designed for the digital world. Unlike AACR2, it is optimized for use as an online product. This means that items cataloged according to the RDA guidelines will be usable on the Internet, Web, OPACs, and so forth. For more information on RDA see The Joint Steering Committee (JSC) for development of RDA website on RDA: http://www.rda-jsc.org/rda.html

Introduction The following cataloging guidelines are taken from the Library of Congress s training guide for copy cataloging in RDA, Copy Cataloging Using RDA Manual (CCURM) and the RDA chapters available in PDF in the RDA folder (RDA). These are available online at: http://www.loc.gov/catworkshop/rda%20training%20materials/lc%20rda%20trainin g/lc%20rda%20course%20table.html These guidelines are to be used when creating records according to the RDA standard or for updating records to this standard. Given here is a summary which emphasizes certain principles as well as giving directives particular to our practices at the Jerry Falwell Library; all the guidelines given in the CCURM should be followed and practiced. In the guidelines given, not every fixed and variable field in a MARC record will be discussed; the fields in which the practices are different from AACR2 are given, with emphasis on what needs to be present in a RDA record. Links to examples of full MARC records cataloged according to RDA will be given in the slide RDA MARC Field Examples after the guidelines.

General Guidelines AACR2 Records that Should be Converted to RDA Any new MARC record created should be cataloged according to RDA standards. Any record that is being updated with table of contents or summary should be updated to RDA. RDA Records An imported RDA record should be kept as RDA. Most RDA records imported from OCLC will be full or fuller-level records. If an RDA record is found that is at encoding levels K, M, 3, 5, and 7, please inform the Cataloging Librarian.

Abbreviations In transcribed fields, use only the abbreviations that appear on the resource. In other fields, generally accept abbreviations as recorded in the imported record, unless directed otherwise in this document (e.g., extent). For example, et al. should only be used if that is what is recorded on the resource. But in the case where that is recorded, you are free to apply the Optional Omission in RDA 2.4.1.5 proper and use the construction [and others].

Punctuation Punctuation (LCPS 1.7.1 and International Standard Bibliographic Description (ISBD)) End of 245, 250, and 260/264 fields: add a period, even if it ends with an abbreviation 245 --... / c written by S.N.. 250 -- 2nd ed.. 260 --..., c 1960. LC practice: in the 260/264 field, do not add a period when the date ends with a hyphen, closing bracket, question mark, or hyphen LC practice: in the 264-4 field (copyright date), do not add a period End of 300 field If 490 is absent, do not add a period 300 --... ; c 26 cm 300 --... ; c 4 3/4 in. If 490 is present, add a period, even if 300 field ends with an abbreviation or closing parenthesis 300 --... ; c 32 cm. 490 1-... 300 --... ; c 12 in.. 490 1-... 300 --... + e 1 CD-ROM (4 3/4 in.).

RDA GUIDELINES FOR MARC MARC Fields defined, and select Fixed Fields and Variable Fields

MARC Fields Defined 010 Library of Congress Control Number (LCCN) 020 International Standard Book Number (ISBN) 050 Library of Congress Call Number 100 Main entry: personal name 110 Main entry: corporate name 130 Main entry : uniform title 245 Title statement 246 Varying form of title 250 Edition statement 264 Production, Publication, Distribution, Manufacture and copyright notice 300 Physical description 336 Content type 337 Media type 338 Carrier type 490 Series statement 5xx Content notes 6xx Subject added entry 7xx Added entry 775 Other edition entry 8xx Series added entry: personal/uniform title 856 Electronic location and access

Fixed Fields Desc use the letter i, not a Ills If there are illustrations, use a; a can only be used by itself. If there are more specific descriptors such as maps, charts or photographs, you are not to use a in combination with the letter representing the map or chart, etc. For example,f it has illustrations plus a map, only use b, not a and b. You can only use a combination of letters for descriptors other than illustrations. For example, if it has maps and photographs, b and o. For a list of all the descriptors see: http://www.oclc.org/bibformats/en/fixedfield/ills.html

Variable Fields MARC Field Number Name RDA action 020 ISBN Spell out what the binding is, for example (paperback). Do not use (pbk.) Add ISBN if it appears on the resource but is not on the record Do not add or delete ISBNs which reflect other bindings, formats, etc. 040 Cataloging source Add a $b eng if not present Add a $e rda OCLC subfield order: VLB $b eng $e rda 050 Call number Make sure there is a LOC call number that corresponds with the first subject field The call number date is to reflect the copyright date of the item unless the publishing date reflects a change in content.

MARC Field Number Name RDA action 1xx Main entry (Creator) Add a creator if missing For compilations, remove creator if the resource contains works by more than one creator (they are all to be listed in 7xx fields). 130/240 Uniform (preferred) title If the resource is a translation, ensure the presence of the preferred title of the original If the resource is a compilation of works by one creator, record the correct form of the conventional title if appropriate If the resource is a revised expression or manifestation with a different title proper, ensure the presence of the preferred title for the original work For compilations, remove the field if it represents only the first work in the compilation Languages in Uniform titles Only one language name in subfield $l Do not record Polyglot or multiple languages in subfield $l

MARCFiel d Number Name RDA action 245 Title proper Record what you see do not correct errors or typos Delete [sic] or [i.e., ]. Remove $h if present (GMDs are now recorded in MARC fields 336, 337, and 338). Add missing title information (present in resource but not on record) Add missing parallel titles from any source in the resource Record full statement of responsibility; do not abridge Replace [et al.] with a full transcription of the statement or use [and others] (supplying appropriate number) Brackets around the statement of responsibility are no longer necessary if information found somewhere on the resource For capitalization of words, see Capitalization; for more information on the statement of responsibility see RDA 2.4 246 Variant title If [sic] or [i.e., ] was removed from the title proper, add the corrected form of the title here. Add later titles of a multipart monograph

MARCField Number Name 250 Edition statement 264 Publication Information RDA action Do not abbreviate any words; expand any abbreviated words Do not convert words to numbers or numbers to words Use in place of the 260 field. If updating a record to RDA, it is acceptable to leave the 260 field, and expand any abbreviated words Follow the guidelines given for the first and second indicators, and find examples of subfields here The first publisher listed in the resource is the publisher to be listed first in this field. It is not necessary to list additional publishers in separate 264 fields, but it is acceptable to do so. Expand abbreviations when applicable, and add missing words; if date is in roman numerals, record it in roman numerals. Provide a publishing date; if one is identified in the resource, use that; if not, use the copyright with a question mark in brackets [2009?] When there is no publishing place, publisher, or date noted use: [Place of publication not identified] [Publisher not identified] [Place of distributor not identified] [Date of publication not identified]

MARC Field Number Name 264 con t Publication information 300 Physical description RDA action Distributor elements are only to be used when no publication data can be identified Manufacture elements are only to be used when both publication and distribution data cannot be identified There is no requirement to list a place within the United States, but it is acceptable to do so. Do not put c in front of the date in a 264 1 field (if using the copyright date as publication date in brackets). To record the copyright date, create a second 264 4 field. This field will only contain: $c 2009. (supply correct date) If there are multiple copyright dates, use only the latest one The symbol for phonogram can be used in place of the copyright date when recorded by the resource for sound recordings Examples of the 264 field can be found at CCURM, p.30-33. Expand abbreviations when applicable Use approximately for ca., and that is for i.e. Use unnumbered rather than brackets enclosing the numeral There is no period after the cm in the $c subfield

MARC Field Number Name 300 con t Physical description 336 Content type RDA action In subfield $b, do not use the word illustrations in combination with any other descriptor, such as map, graph, etc. If there are specific descriptors, they are to be used in place of the word illustrations. The following is a list of acceptable alternatives to the word illustrations: Charts, Coats of arms, Facsimiles, Forms, Genealogical tables, Graphs, Illuminations, Maps, Music, Photographs, Plans, Portraits, and Samples. Accept $b if present, and other $a if appropriate Use constant data records provided to record these in resource 337 Media type Accept $b if present, and other $a if appropriate Use constant data records provided to record these in resource 338 Carrier type Accept $b if present, and other $a if appropriate Use constant data records provided to record these in resource

MARC Field Number Name RDA action 344 Sound characteristics Use this field when cataloging a sound recording, or if there are specific sound characteristics (like surround sound) in a video recording. For field characteristics, see 344. 347 Digital file characteristics Use this field when cataloging a digital encoding of text, image, audio, or video. For field characteristics, see 347. 490 Series statement Record the ISSN and/or numbering of the series All series statements in the resource are to be recorded If updating an imported record, delete any series statements not found in the resource If typos found in the imported record, correct and add any missing data elements 504 Bibliography Needs to be present if resource contains references and/or indexes Do not use abbreviations; for example, Includes bibliography (pages 267-273) 505/520 Contents and summary Each record updated or created needs to contain either a 505 or 520. There are no special RDA actions for these.

MARC Field Number Name RDA action 521 Intended audience Record if resource is intended for children; though this is primarily used by the curriculum library, we sometimes put books in the main collection that need this field, so be on the look out for this. 546 Language/script If the resource is in another language, or is written in more than one language, record them here. 7xx Added entry You must provide a 7XX field for the illustrator of a resource intended for children; this is a core element If the resource is a compilation, add a 700 field for the first or principal work if it is substantial You may combine multiple relationships designators in one access point; for example, if a person has both written the text and provided the illustrations for a resource: 100 1# $a [Name],$e author,$e illustrator Beyond this core requirement, all other 7XX fields are cataloger judgment Remember to base these judgments upon the consideration of user needs

MARC Field Number Name RDA action 7xx con t Added entry Any subfield $i is to be the first subfield, and must contain an Appendix J designator Use the Appendix I designator in $e for an illustrator of a resource intended for children. If the field already contains the relationship code ill in $4, add the relationship term $e preceding $4, i.e.: $e illustrator. $4 ill Accept the presence or absence of relationship designators in access points, unless the term is incorrect. If the resource indicates person or entity whose relationship cannot be found in Appendix I or J, see Appendix K 775 Other edition entry For a reproduction, reprint, or other edition. give information about the original publication when the earlier record is available; otherwise use bibliographic history note (500). See 775 and 775 examples. All other fields See the CCURM, especially pages 28-36, and RDA in brief; for any questions not answered here, please see the Cataloging Librarian.

RDA MARC Field Examples To compare records that are correct by RDA standards to those that are not see these two links: Incorrect (pages 146-154) Correct For examples from the Library of Congress: RDA Record examples Slides, Manuals, Exercises Test yourself!

Copy Cataloging Resources Library of Congress Classification Outline Library of Congress Subject Headings MARC FAQ RDA in MARC October 2012 update MARC and FRBR