Resource Description & Access (RDA)

RDA Toolkit Update, August 11, 2015 - Changes in Resource Description and Access (RDA) and Library of Congress - Program for Cooperative Cataloging Policy Statements (LC-PCC PS) and RDA Toolkit TOPIC 1: Changes in RDA Content TOPIC 2: Change in Content in LC-PCC PSs TOPIC 3: Functional Changes in the RDA Toolkit TOPIC 1: Changes in RDA Content : Fast Track changes The PDF file mentioned in the URL below from RDA JSC site identifies the "Fast Track" changes to RDA that will be included in this release (6JSC-Sec-16.pdf); Fast Track changes are not added to the RDA Update History.  While you are encouraged to peruse the changes, there are no significant changes. TOPIC 2: Change in Content in LC-PCC PSs A summary of LC-PCC PS updates incorporated in this release is available at  August 11, 2015 release of the RDA Toolkit .  Catalogers should review the following policy statements: 1.8.2, First Alternative:  revised to include an e...

Questions and Answers on treatment Series in RDA and MARC21  Join the Google+ Community RDA Cataloging  to view, ask, and share information and issues related to Resource Description & Access (RDA) and AACR2 Cataloging

Myth: “The Library of Congress has changed its series policy. Under RDA, all series are now traced.” Reality: Wrong!  LC continues to record all series in original cataloging as 490-0 (when performing Copy Cataloging, the 4XX and 8XX field are ‘pass-through’ elements; do not change a 440 to a 490-0). [Source : Library of Congress] <<<<<---------->>>>> See Also:  Series at the Library of Congress: June 1, 2006 Frequently Asked Questions about Series (LC-PCC) Statement on the Library of Congress Series Authority Record Decision (ALCTS, ALA) [Updated 2014-12-21]

QUESTION: Would the same rules for qualifying a corporate body apply to both the heading and the variants? For example, would this be appropriate under RDA: 110 2_ Progressive Artists Group (Jaipur, India) 410 2_ PAG (Jaipur, India) We would never qualified "PAG" under AACR2 when it's used as a variant form. When it's used as a heading, of course, then we would qualify. What about in RDA? ANSWER: We had a very specific LCRI practice that basically forbade the adding of qualifiers to many kinds of references, we got rid of those restrictions on variants because they represented an exception that wasn't really important and only caused confusion. 11.13.2.1 tells you that you can add the same additions to variants as to authorized access points. For personal names see RDA Rule 9.19.2.1 (Reproduction of Question and Answer from experts from LC) <<<<<---------->>>>> RDA Rule 11.13.2.1 : General Guid...

RDA RELATIONSHIP DESIGNATORS RDA Cataloging Examples of Relationships in a Corporate Body Name : Founder ; Hierarchical superior Click on image to enlarge (note the use of relationship designator in 510 field) (note NAR change from AACR2 to RDA in 410 field) <<<<<---------->>>>> RDA Cataloging Examples of Relationships in a Corporate Body Name :  Successor ; Predecessor ; Hierarchical superior ;  Click on image to enlarge Click on image to enlarge [Revised on 2015-04-13] <<<<<---------->>>>> 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 ...

NUMBER, DATE, AND LOCATION OF A CONFERENCE, ETC. Authority Records for Ongoing Conferences LC practice/PCC practice: For ongoing conferences, separate authority records may be created for the collective conference (typically made when cataloging a serial), an individual instance of an ongoing conference (typically made when cataloging a monograph), or both. These records may coexist in the LC/NACO authority file. A record for the collective conference should always be made to connect the earlier and later names of the collective conference. Individual Instance of an Ongoing Conference LC practice/PCC practice: When creating an authority record for an individual instance of an ongoing conference, the additions for number, date, and location of a conference, etc. are given in the authorized access point. Variant access points may be given for variant names of the individual conference, such as acronyms for a spelled-out form. Generally do not connect an individual in...

RECORDING NAMES OF GOVERNMENT BODIES AND OFFICIALS--Government Bodies Recorded Subordinately--Type 3 See RDA Rule 11 .2.2.19 for Government Bodies Recorded Subordinately See RDA Rule 11 .2.2.20 for Direct or Indirect Subdivision [Source: RDA Toolkit] [Check NAR--n 2012215382--National Data Centre--Office of the Additional Director General of Meteorology (Research), Pune]

Inverted cross-ref in NARs Example (AACR2) 111 2  National Town & County Planners Congress 411 2 County Planners Congress, National Town & 411 2  Town & County Planners Congress, National Note:  Both variants were provided before when cataloging with AACR2 because of RI 26.3A (References from inverted names of Conferences, Exhibitions, Fairs, Festivals, etc.)— These references are no longer needed as variants in RDA .   Reason: Key word search in ILS will resolve this need. Please add all the qualifiers (no.; date; place) just like your 111 field for both RDA variants. LC-PCC PS: When creating an authority record for the collective conference, do not add the numbers/and/or dates to the authorized access point and variants if you are providing variants <<<<<---------->>>>> RDA Blog  :  RDA Blog  is a blog on  Resource Description and Access  ( RDA ), a new...

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