Resource Description & Access (RDA)

Myth: “You must always record the statement of responsibility exactly as it appears, including all degrees, titles, and affiliations.” Reality: Generally, yes -- and this is the preferred practice for monographs.  But not necessarily.  LC-PCC PS 2.4.1.4 says to “generally” not abridge a statement of responsibility.  But if the statement of responsibility contains a burdensome amount of such information, you may abridge it, provided no essential information is lost. [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  |  LinkedI...

Myth: “A parallel title can only be recorded if it appears on the same source as the title proper.” Reality: No, this is the AACR2 rule.  Under RDA, the parallel title may be recorded without brackets if it appears anywhere within the resource. In RDA a parallel title no longer has to appear on the same source as the title proper to be considered as such. For example, if the romanized title appears on the t.p. verso, it would still be considered a parallel title. [Source : Library of Congress]

Myth: “Other title information may be recorded in brackets if it appears on a source other than the same source for the title proper.” Reality: Wrong.  RDA 2.3.4.2 explicitly states “Take other title information from the same source as the title proper.”  If it appears elsewhere, you may record it in a note, but should not include it in the title area -- not even with brackets.  [Source : Library of Congress]

Myth: “Recording of other title information is optional and a matter of cataloger judgment.” Reality: This statement is true for serials.  But not for LC monograph catalogers!  Although other title information is not a core element in ‘pure’ RDA, it is “LC Core” for monographs.  You must record it if it appears on the same source as the title proper. [Source : Library of Congress]

Myth: “Typos and errors in the titles of serials should be recorded as they appear, and NOT be corrected -- just like monographs.” Reality: Incorrect.  In order to record a consistent title for all issues of a serial and all issues of an integrating resource, such errors SHOULD be corrected (per the exception at 2.3.1.4), and a variant title (246) can be recorded for the title as on the resource (i.e., with the error).  [Source : Library of Congress]

Myth: “When transcribing the title, you can generally do whatever you wish regarding capitalization.” Reality: Not really.  The LC-PCC PS for the first alternative to 1.7.1 states “For capitalization of transcribed elements, catalogers are encouraged (but not required) to follow Appendix A.”  It is permitted to ‘take what you see’ on the resource.  If you choose the option of taking exactly what you see, do that for the entirety of the element.   [Source : Library of Congress]

RDA is divided into ten sections: sections 1–4 cover elements corresponding to the entity attributes defined in FRBR and FRAD; sections 5–10 cover elements corresponding to the relationships defined in FRBR and FRAD. The initial chapter in each section sets out the functional objectives and principles underlying the guidelines and instructions in that section, and specifies core elements to support those functional objectives. Subsequent chapters within each section cover attributes or relationships that support a specific user task as follows: Attributes Section 1  covers the attributes of manifestations and items that are most commonly used to identify a resource (chapter 2), to select a resource appropriate to the user’s requirements with respect to format and encoding (chapter 3), and to obtain a resource (chapter 4).  Section 2  covers the attributes of works and expressions that are most commonly used to identi...

[Click the picture (flow chart) for larger view] [Source: Library of Congress RDA Training]

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

Source of Parallel Title and Title Proper : Best Practices In the BIB record, the note for the source of the parallel title is not necessary.  Only title propers need a note if from outside of t.p.

Included New Section for Feeds of RDA Toolkit Development Blog to Get Notification of New Releases  RDA REVISION When there is a new release for RDA Toolkit, it is made on the second Tuesday of the month. Releases typically contain updates to content and metadata, enhancements to RDA Toolkit functionality, and fixes to existing bugs. The notification of new releases can be had from the above mentioned section "RDA Toolkit Development Blog" of this blog . <<<<<<------------>>>>>> LC-PCC PS REVISION Accessing Current Library of Congress-Program for Cooperative Cataloging Policy Statements (LC-PCC PSs)  : summaries of changes (revisions, additions, deletions).  Library of Congress-Program for Cooperative Cataloging Policy Statements (LC-PCC PS) will be revised and updated in response to the changes in RDA. This revision includes additions and deletions of LC-PCC PSs, corrections of typos, and rewri...

The About This Blog page is modified. Please view and post your comments / feedback / suggestions in the Guest Book . <<<<<---------->>>>> 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 ,...

LC-PCC PS for 1.7.1  (RDA) GENERAL GUIDELINES ON TRANSCRIPTION   (Below is the Table of Contents; for complete text of this LC-PCC PS, click above) Introduction  LC practice/PCC practice: This Policy Statement is an overall statement related to punctuation/spacing conventions. For convenience, it addresses in one place conventions applicable to access points in bibliographic and name authority records and those applicable to other parts of the bibliographic record. Much of the data in a MARC record are explicitly identified by content designation (tags, indicators, subfield codes). Upon output or display, the content designation is used to determine various display conventions including spacing. Internally there is often no spacing at all but instead content designation, particularly subfield codes. In displays that do not show content designation, spacing is substituted. How much spacing is at the discretion of a particular system. However, ...