Resource Description & Access (RDA)

RDA Example of Selections and Translations. CASE: Compilations of selected devotional songs of a Kannada saint poet; with Hindi and English translations. See also another example: https://lccn.loc.gov/2015363552

Whenever we recode an AACR2 NAR to RDA, we should also re-evaluate the record (especially the heading) to see if anything needs to be revised.

[546] In Hindi, Kannada ‡b (in Devanagari), and English.

QUESTION: What is  order of subfields k and l in preferred titles.  For example … $t Plays. $k Selections. $l Hindi. ANSWER:  Under RDA it has been determined that $k Selections is an attribute of a work and language ($l) is an attribute of an expression.  So $k must preceed $l [Answer provided by  Ana Lupe Cristán] <<<----->>>>   EXAMPLE: For s elected plays of a Panjabi author, translated into Hindi: [240]-10  ‡a Plays. ‡k Selections. ‡l Hindi.

If the record has both the publication and copyright dates, then the 008/06 should be "t" and the 008/11-14 should have the copyright date. See LC-PCC PS 2.8.6.6 for examples.  LC-PCC PS for 2.8.6.6 -- DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE <<<<<---------->>>>> DtSt Type of Date/Publication Status (OCLC MARC BIBLIOGRAPHIC) t   Publication date and copyright date . The item has a publication, release or production date and a copyright date. Date 1 is the year of publication, release, or production; Date 2 , the year of copyright. Treat deposit dates (preceded by D.L.) as copyright dates. DtSt: t Dates: 1966, 1962 [1966, c1962 ( 1968 printing )]   DtSt: t Dates: 1966,1965 [1966, c1965]   DtSt: t Dates: 1980,1957 [1980 printing, c1957]   DtSt: t Dates: 198u,1979 260 Berlin : ‡b Springer, ‡c [198-?], c1979. DtSt: t Dates: 1982,1949 260 London : ‡b Macmillan, ‡c 1982, c1...

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.

QUESTION: This is in regards to 2011352604, which contains both the original text in Sanskrit and the Hindi translation. In AACR2, we would have had a 240 of Kalyāṇakāraka. $l Hindi & Sanskrit. In RDA, we would not have a 240. Instead, in theory, we would give 2 700s (as in the Mail Carrier example from the class materials): 700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka. 700 02 ‡a Ugrādityācārya, ‡d 8th/9th century. ‡t Kalyāṇakāraka. ‡l Hindi. However, in this case, the 1st 700 would really result in the same N/T string as the 100/245 combo. So is it still required? ANSWER: Yes, two 700 name/title analytics.   In some cases the preferred title may be the same as the 245 title proper, but in many other cases it won't be.  We just thought it would always be easier to say "make the analytics" than to say "sometimes you do, and sometimes you don’t".  So it may be redundant in some cases. (Reproduction of suggestions of exper...

The Classification and Shelflisting Manual (CSM) contains the policies on assigning LC classification numbers and LC book numbers (i.e., shelflisting).  Originally written in the 1980s and last updated in 2010, the CSM reflects the AACR2 environment.   The U.S. national libraries’ decision to implement Resource Description and Access (RDA) led the Policy and Standards Division (PSD) to review the CSM and determine which instruction sheets needed to be revised to reflect RDA instructions.  Generally, the text was updated to ensure consistency with past classification and shelflisting practice, and new examples were chosen. Specialists in PSD also took this opportunity to reevaluate some long-standing practices both to simplify them and to make them more sustainable in today’s linked, global, environment.   The priority was to first revise the instruction sheets that are most heavily affected by the implementation of RDA. Those sheets are now provided ...

The RDA Phase 2 changes to the name authority file were completed on March 27, 2013, so the Library of Congress’ Policy and Standards Division will now begin to update LCSH authority records.  PSD expects to complete the project by the end of April 2013. Personal, corporate, and conference names, as well as titles and geographic headings (MARC 21 fields 100, 110, 111, 130, and 151), that are established in the name authority file and are also printed in LCSH are eligible for revision.  Phrase headings and subdivisions that are based on names or titles (e.g., Food in the Koran; Future life—Koranic teaching) will also be revised as necessary. This is a large project that must be undertaken in a systematic manner in order to find all of the affected records.  LC catalogers and SACO participants are therefore requested to refrain from making proposals to update headings until after PSD announces the completion of the project.   At this time, PSD is not...

LC policies for a few topics recently discussed by the ABA Management Team.  These policies either confirm that the interim policies LC staff have been following are still in place, or note where policies will be different in the post-March period. The topics covered are: Policy 1:  RDA Acceptable Authority Records after March 31, 2013 Policy 2:  Monographs Imported from OCLC (including copy cataloging) Policy 3:  CIP Verification Policy 4:  Working with Existing Serial Records Policy 5: Added Volumes for Multipart Monographs Policy 6:  Manual Hybridization of AACR2 Records with RDA Elements All staff involved with creating and updating LC/NACO authority records should pay particular attention to Policy 1 on the treatment of authority records. Policies 2-6 are primarily applicable to ABA and other processing units choosing to follow them.   These policies are also posted at http://www.loc.gov/aba/rda/pdf/rda-policies-fo...

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

From: Program for Cooperative Cataloging [mailto:PCCLIST@LISTSERV.LOC.GOV] On Behalf Of Reser, Dave Sent: Thursday, February 21, 2013 5:23 PM To: PCCLIST@LISTSERV.LOC.GOV Subject: [PCCLIST] Revised LC-PCC Policy for Fuller form of name (9.19.1.4, option) Dear PCC members-- The policy related to the optional use of the RDA element "Fuller form of name" in authorized access points for persons (RDA 9.19.1.4, option) has been the subject of debate by more than one PCC Task Group, the PCC Policy Committee, and listservs such as PCCLIST.  LC and PCC have agreed to a new shared policy for this instruction (a change from the previous LC policy).  Because of the high level of interest in this topic, and the postponement of the February release of the RDA Toolkit where it would have been published ( http://www.rdatoolkit.org/blog/517 ), we have taken the exceptional step of mounting the revised policy so that it may be applied immediately by catalogers.  Until it is publ...

Library of Congress News from CDS Cataloger's Desktop Now Contains Six RDA-Related Resources Another RDA-related resource has been added to Cataloger's Desktop.  The new resource, RDA training resources, is maintained by the CILIP-BL Committee on RDA and provides links to RDA training from Cambridge University Library, CILIP Cataloguing & Indexing Group, the Australian Committee on Cataloguing, rdacake (RDA CAnadian Knowledge Exchange), Die Deutsche Nationalbibliothek, National Library of New Zealand, and several U.S. contributors.  The following is the current list of RDA-Related resources in Cataloger's Desktop:  *         RDA: Information and Resources in Preparation for RDA (LC) *         RDA: LC Documentation for the RDA Test *         RDA: Resource Description and Access (subscription resource that requires a separate subscrip...

In RDA the instructions for subordinate bodies (11.2.2.14) are the same as in AACR2. Type 3 – Name that is general in nature        •Annual Meeting; Macadamia Nut Association •110 2# $a Macadamia Nut Association. $b Annual Meeting Type 6 – Name that includes the entire name of the higher body           •Annual Meeting of the International Whaling Commission •110 2# $a International Whaling Commission. $b Annual Meeting [Source: Library of Congress RDA Training materials] Thanks all for your love, suggestions,  testimonials , likes, +1, tweets and shares .... See also related posts in following  RDA Blog  Categories (Labels):

l   RDA 11.2.2.2                 Sources of Information:                 “Determine the preferred name for a corporate body from the following sources (in order of preference):                                                 a)   the preferred sources of information (see 2.2.2) in resources associated with the corporate body                                             ...

These events now have the same rules l   RDA 11.2.2.11                 Number or Year of Convocation of a Conference, Etc. :                 “Omit from the name of a conference, congress, meeting, exhibition, fair, festival, etc. […] indications of its number, or year or years of convocation, etc.”   l   No instruction to remove an indication of frequency (Annual, Biennial, etc.) <<<<----------------->>>> Examples: l   Omit year of convocation: •           CAV (Conference) l   NOT •           CAV ’91 l   Retain indication of frequency (Annual, Biennial, etc.): •           Annual Conference on Fishing l   NOT ...

Under RDA a conference name need not contain a word that denotes a conference, to be considered named                 LCRI 21.1.B1 has no equivalent in RDA or in the LC-PCC PS •           LCRI 21.1.B1: •           “… when deciding whether a phrase is a name is that the phrase must include a word that connotes a meeting:  "symposium," "conference," "workshop," "colloquium," etc.” <<<<----------------->>>> A named conference need only fulfill these RDA definitions l   RDA 8.1.2                 Person, Family, and Corporate Body:                 “The term corporate body refers to an organization or group of persons...

RDA Examples of Variant Titles in MARC 21 EXAMPLE 245 10 $a XX centuries & Mt. St. Helens ... 246 3# $a 20 centuries and Mount Saint Helens 246 3# $a Twenty centuries and Mount Saint Helens ABBREVIATION 245 10 $a Messrs. Ives of Bridgeport ... 246 3# $a Messieurs Ives of Bridgeport 245 10 $a Mt. St. Helens ... 246 3# $a Mount Saint Helens ... 245 10 $a St. Louis blues ... 246 3# $a Saint Louis blues ... AMPERSAND 245 10 $a A & B roads & motorways atlas of Great Britain ... 246 3# $a A and B roads and motorways atlas of Great Britain LETTERS AND INITIALISMS (including ACRONYMS) 245 10 $a A.-G. Chemie ... 246 3# $a AG Chemie 245 14 $a The A-B-C-D of successful college writing ... 246 3# $a ABCD of successful college writing ARABIC NUMBERS (Excluding Dates) 101 = one hundred one; use also one hundred and one 425 = four hundred twenty-five, not four hundred and twenty-five 1001 = one thousand one; use also one thousand and...