Resource Description & Access (RDA)

RDA Toolkit Update, October 13, 2015 - Changes in Resource Description and Access (RDA) and Library of Congress - Program for Cooperative Cataloging Policy Statements (LC-PCC PS) and RDA Toolkit A new release of the RDA Toolkit is published on Tuesday, October 13.  This message will cover several points you should be aware of related to the release.  Changes in RDA Content Change in Content in LC-PCC PSs Functional Changes in the RDA Toolkit Changes in RDA Content : Fast Track changes This includes changes to some instruction captions, but there is no actual change in practice.  There are a few new relationship designators for Appendix I , the term “ researcher ” may be one of broad interest. According to I.2.2  Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work:  Researcher: A person, family, or corporate body who does research in support of the creation of a work. Change in Content i...

RDA Cataloging Examples  of use of Extended Date Time Format (EDTF) in  MARC 21 field 046 for Special Coded Dates  in  Resource Description and Access  ( RDA ) Name Authority Records   DCM Z1 046 update in Cataloger's Desktop 2015 Issue 3 release Cataloger's Desktop 2015 Issue 3 was released on August 11, 2015. This release includes an important update to DCM Z1 instruction sheet  046 , Special Coded Dates.  LC/NACO catalogers: please note that the formatting of dates in the 046 field has changed. When supplying dates in field 046 , use the Extended Date Time Format (EDTF) schema in all cases except for centuries; supply dates using the pattern yyyy, yyyy-mm, or yyyy-mm-dd; always add subfield $2 edtf except after a century . The more consistent use of $2 edtf is based on a PCCLIST discussion suggestion to simplify the use of $2 (always use except for centuries). Examples: 046 ## $f 1884-10-11$g 1962-11-07...

There are two indications that a record is an RDA bibliographic record: Leader/18 contains the value “i” (ISBD punctuation included)  Field 040 $e contains the code “rda” [Source: Library of Congress ]

MARC 21 FIELD TAG MARC 21 SUBFIELD CODE MARC 21 FIELD / SUBFIELD NAME RDA INSTRUCTION NUMBER RDA ELEMENT NAME 046 Special Coded Dates (R) 046 f Birth date 9.3.2 Date of Birth 046 g Death date 9.3.3 Date of Death 046 k Beginning or single date created 6.4 Date of Work 046 k Beginning or single date created 6.10 Date of Expression 046 l Ending date created 6.4 Date of Work 046 l Ending date created 6.10 Date of Expression 046 o Single or starting date for aggregated content 6.4 Date of Work 046 p Ending date for aggregated content 6.10 Date of Expression 046 s Start period 9.3.4 Period of Activity of the Person 046 s Start period 10.4 Date Associated with the Family 046 s Start period 11.4.2 Date of Conference, etc. 046 s Start period 11.4.3 Date of Establishment 046 t End period 9.3.4 Period of Activity of the Person 046 t End period 10.4 Date Associated with the Family 046 t End period 11.4.2 Date of Conference, etc. 046 t End period 11.4.4 Date of Terminatio...

RDA Blog  posts on Special Coded Dates in MARC 21 Field 046: RDA LC-PCC PS Revision EDTF Date - 046 - RDA Cataloging Examples Special Coded Dates - MARC to RDA Mapping Example of a Name-Title Authority Record : Best Practices - MARC 046, 370, 380, 381 MARC 21 encoding to accommodate new RDA elements 046 and 3XX in NARs and SARs DCM Z1 Update See also: Library of Congress >> MARC >> Authority >> 01X-09X >> 046  [LC] 046  Special Coded Dates (R)  [OCLC]

Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 043 043  Geographic Area Code (NR) The 043 is a subect field, and while presently connected to place names used in the 6xx fields, has absolutely nothing to do with RDA. -- Aaron Kuperman

Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 042 042  Authentication Code (NR)

Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 041  [LC] 041  Language Code (R)  [OCLC]

Add subfield $d {MARC 21 code} when modifying NARs or SARs unless your institution's is already the last MARC subfield $d in the 040 field. For example if LC is modifying agency, when making revisions to a NAR, we should add a $d DLC to the 040, if that is not the latest subfield present.

RDA Blog  posts on Cataloging Source - MARC 21 Field 040: 040 - Cataloging Source (NR) Identifying RDA Records 040 - Cataloging Source - MARC Field 040 Subfield Order See also:  Library of Congress >> MARC >> Bibliographic >> 01X-09X >> 040  [LC] 040  Cataloging Source (NR)  [OCLC]

LC control no.:  n 2012216691 LCCN permalink:  http://lccn.loc.gov/n2012216691 HEADING: Mahāpātra, Nityānanda, 1912-2012. Novels. Selections 000 00584cz a2200169n 450 001 9250467 005 20130620032123.0 008 130425n| azannaabn |a aaa 010 __ |a n 2012216691 040 __ |a DLC |b eng |c DLC |e rda |d DLC 046 __ |k 2012 100 1_ |a Mahāpātra, Nityānanda, |d 1912-2012. |t Novels. |k Selections 370 __ |g Bhubaneswar, India 380 __ |a Novel 381 __  |a Selections 400 1_ |a Mahāpātra, Nityānanda, |d 1912-2012. |t Nityānanda upanyāsatraẏī 400 1_ |a Mahāpātra, Nityānanda, |d 1912-2012. |t Nityananda upanayastrayee 670 __ |a Nityānanda upanyāsatraẏī, 2012. Comments from experts:   370 and 380 were OK - place work was created and form of a work.  However, the 381 should be removed. "Selections" is a part of the work, not a characteristic and should not be used in this field.  The M...

Field 040 Subfield Order in Serial RDA Records The correct 040 subfield order for CONSER RDA serials in OCLC is:  $a   $b   $e   $c   $d  Example: 040   DLC ǂ b eng ǂ e rda ǂ c DLC ǂ d OCLCQ ǂ d CLU ǂ d DLC Field 040 Subfield Order in LC RDA Records (Bibliographic) 040 ‡a DLC ‡b eng  ‡e rda ‡c DLC Field 040 Subfield Order in LC RDA Records (Authority) 040 ‡a DLC ‡b eng  ‡e rda ‡c DLC 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 ...

MARC 21 encoding to accommodate new RDA elements 046 and 3XX in NARs and SARs This document records the recommended interim practice when giving the information in authority records. The information will be updated as ‘best practice’ decisions are adopted by the PCC and changes to the MARC 21 Format for Authority Date are implemented. LC/PCC will use the authority format when creating records for works and expressions. Thanks all for your love, suggestions,  testimonials , likes, +1, tweets and shares .... See also related posts in following  RDA Blog  Categories (Labels):

<<<<<---------->>>>> RDA Blog  :  RDA Blog  is a blog on  Resource Description and Access  ( RDA ), a new  library cataloging  standard that provides instructions and guidelines on formulating data for resource description and discovery, organized based on the  Functional Requirements for Bibliographic Records  ( FRBR ), intended for use by libraries and other cultural organizations replacing  Anglo-American Cataloging Rules  ( AACR2 ). This blog lists description and links to resources on  Resource Description & Access (RDA) . It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on  Resource Description and Access ,  FRBR ,  FRAD ,  FRSAD ,  MARC standards ,  AACR2 ,  BIBFRAME , and other items related to current developments and trends in  library cataloging  practice...

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...