Resource Description & Access (RDA)

This was the fourth year of RDA Blog  on Resource Description and Access ( RDA ).  We hope that our posts have been both interesting and helpful to all librarians and catalogers. As 2015 comes to a close, I want to share our most read articles of the year. Top 10 RDA Blog Posts of 2015   RDA Cataloging Rules for Pseudonyms with MARC 21 Examples International Standard Book Number (ISBN) - MARC to RDA Mapping RDA Cataloging Examples Articles, Books, Presentations on Resource Description and Access (RDA) Establishing Certain Entities in the Name or Subject Authority File : RDA Cataloging Libhub Initiative Corrected Titles Proper & Variant Titles : RDA vs AACR2 : Questions and Answers & Best Practices RDA Bibliography LC RDA Implementation of Relationship Designators in Bibliographic Records 33X fields do not necessarily mean RDA Thank you for reading  RDA Blog  on  Resource Description and Access  ( RDA )! Happy New Y...

Library of Congress has begun supplying $b codes for the equivalent terms in $a of fields 336 (Content type), 337 (Media type), and 338 (Carrier type). This is the most efficient manner to start populating a subfield that LC initially chose not to apply. This will allow LC records to conform more to records produced outside of LC (e.g., OCLC generally adds the codes in $b in new records). It will be supplied automatically if cataloger are using the macro or the RDA templates in Voyager—staff are not expected to manually add $b to fields in existing records that lack the subfield. [Source : Library of Congress]

Myth: “If a resource includes multiple components (e.g., a volume and CD, with text, maps, and spoken word), you must describe all, using multiple 33X fields for Content, Media, and Carrier Type.” Reality: Not necessarily.  You must record the predominant term for each 33X field.  If you wish to record additional fields, you may.  Remember that each term is from a controlled vocabulary. [Source : Library of Congress]

October 2012 Contents: MARC 21 Updates 9-15 include all changes to MARC for use with RDA approved through June 2012. Content, Media and Carrier Types and Characteristics RDA Content Types MARC already indicates content type in LDR/06. RDA contains a list of English language content types for which a new field 336 was provided in MARC Bibliographic and in MARC Authority . Field 336 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10. For a table that relates the MARC LDR/06 to the corresponding RDA content terms and MARC codes for RDA content terms see: Term and Code List for RDA Content Types . RDA Media Types MARC already indicates media type in field 007/00. RDA contains a list of English language media types for which a new field 337 is provided in MARC Bibliographic and in MARC Holdings . Field 337 may contain the RDA term ($a) or a code ($b); codes were established in MARC Update 10. For a table that relates the MARC 007/00...

English Non-roman Note: Tags 040/906/925/955 are cataloging agency specific and can be omitted/changed as appropriate <<<<<---------->>>>> See also: RDA Blog  Home About RDA - Resource Description and Access About RDA Blog RDA Resources Cataloger's Reference Directory RDA Blog Testimonials Follow  RDA Blog  in Social Media:  Google+  |  Facebook  |  Google+ Community  |  Twitter  |  YouTube   |  SlideShare  |  Tumblr   |  WordPress  |  Flipboard  |  Pinterest  |  LinkedIn Thanks all for your love, suggestions,  testimonials , likes, +1, tweets and shares .... See also related posts in following  RDA Blog  Categories (Labels):

Recent questions to the Policy and Standards Division prompt this cautionary message about imported records. The presence of fields 336 (Content type), 337 (Media type), and 338 (Carrier type) in a bibliographic record does not in and of itself indicate RDA cataloging, since these fields may be used with non-RDA cataloging.  When these fields are present in a bibliographic record look for positive evidence of RDA cataloging:             Ldr/18 (Descriptive cataloging form) = i (ISBD punctuation included) or c (ISBD                         punctuation omitted)             040 contains $e = rda             If the value in Ldr/18 is neither "i" nor "c" and 040 contains $e = rda, rely on the ...

Resource Description and Access at the Library of Congress (08/29/11) Authority Records RDA Authority Records (September 2010) [DOC, 123 KB] RDA Authority Records (August 2011) [PDF, 89 KB] Bibliographic Records Overview of Changes [DOC, 80 KB] Books [DOC, 82 KB] Language of Expression [DOC, 59 KB] Legal Works [DOC, 59 KB] Preferred title (including compilations) [DOC, 106 KB] Publication, distribution, and/or manufacture statement [DOC, 60 KB] Replacement of GMD and carrier description [DOC, 72 KB] Statement of Responsibility [DOC, 64 KB]

DCM Z1 Update: 1) The update includes agreements between PCC and LC with regard to "best practices" in the new MARC fields for authority records. Note especially the information on the use of subfields $u and $v; the full text on the use of $u and $v is supplied only in the 046 section, but it is referenced in each of the fields where these subfields may be used. Here is an excerpt from that 046 section on the use of subfields $u and $v -- NACO catalogers please take note: The following represents PCC practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670: 1. 670s must be used to support information used as part of a heading in 1XX and 4XX. 2. For 046, 37X, 381: a. use of $v is optional if the same information/source is already cited in the 670 b. use $v if the information/source is not cited in a 670 c. use of $u is optional, and should always be preceded by $v. 2) Catalogers are instructed to no longer supply Conte...