Resource Description & Access (RDA)

Following  RDA Blog  posts are revised: Use of 500 and 510 Field to Show Relationships in a Corporate Body Name  [Revised on 2015-04-13] Editor of Compilation vs Compiler  [Revised on 2015-03-31] Conventional Collective title / Uniform title : Questions and Answers  [Revised on 2015-04-03] See also: RDA Blog Testimonials & Reviews  

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 There are two types of changes in the RDA content for this update: 1) the third annual major update to RDA based on the decisions made by the Joint Steering Committee for Development of RDA (JSC) at their November 2013 meeting; and 2)  “Fast Track” changes that are relatively minor and typical of a release update. Revisions from JSC actions: The attached document (Summary of 2014 rda updates.docx) identifies highlights from the changes to RDA due to the JSC update (see link below).  Many of the changes in this update package are due to re-numbering of instructions and references (without a change in actual content) and are not included in the attached listing.  The changes will appear with the “revision history” icon in the RDA Toolkit.  A complete listing of all changes due t...

RDA RELATIONSHIP DESIGNATORS RDA Relationship Designators : Editor of Compilation vs Compiler  The editor of a compilation, as defined in I.3.1, is not a creator of a work and thus has to be treated as a 700, not a 100. On the other hand, a compiler (for example of a dictionary, a directory, a bibliography, etc.) can be considered a creator (see I.2.1) and thus can be treated as a 100. Expert remarks by  Aaron Kuperman ,  Law Librarian, Library of Congress :  A good rule of thumb is that a compilation needs to consist of works that can (and should) be listed in the contents note. According to RDA Toolkit:  I.2.1 Relationship Designators for Creators:  Compiler :  A person, family, or corporate body responsible for creating a new work (e.g., a bibliography, a directory) by selecting, arranging, aggregating, and editing data, information, etc. For a compiler as a contributor, see editor at I.3.1. According to RDA Toolkit: I...

RDA RELATIONSHIP DESIGNATORS Myth: “I must include relationship designators with all access points.” Reality: Wrong.  You may include relationship designators in all access points.  But the only relationship designator that is required is “$e illustrator” for an illustrator of a resource intended for children. Note: LC will soon implement the PCC requirement for relationship designators for all creators.  [Source : Library of Congress] 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,...

Myth: “Creators and contributors perform the same function, and the instructions regarding them are interchangeable and found in the same chapter of RDA” Reality: Absolutely not true!  Creators are involved at the work level, and are covered in Chapter 19; contributors are involved at the expression level, and are covered in Chapter 20.  Further, if you use a relationship designator, be sure to use one appropriate to the “WEMI” level. [Source : Library of Congress] RDA RELATIONSHIP DESIGNATORS

Myth: “You must always record all statements of responsibility.” Reality: Incorrect.  You must record the first statement of responsibility, generally in full.  Recording subsequent statements of responsibility is a matter of judgment -- but of course they are usually helpful for the user.  Also, note this from 2.4.2.3: “If not all statements of responsibility appearing on the source or sources of information are being recorded, give preference to those identifying creators of the intellectual or artistic content. In case of doubt, record the first statement . ” Myth: “But aren’t you required to record a subsequent statement of responsibility if it describes an illustrator of a resource intended for children?” Reality: This is good cataloging practice, but not necessarily required .  You must provide an access point for the illustrator; and that the relationship designator “$e illustrator”. But a statement of responsibility other than the f...

RDA Rule 2.4.1 instructs to record a statement of responsibility identifying an editor of a serial only if the name of the editor is considered to be an important means of identifying the serial.