Resource Description & Access (RDA)

Listed below are some of the main differences in terminology between AACR2 and RDA. Some of the changes reflect our turning away from the catalog card environment, while others reflect terminology in the FRBR/FRAD models and the International Cataloguing Principles. AACR2 RDA Notes heading authorized access point “heading” reflects outmoded ‘catalog-card-speak’ author, composer, artist, etc. creator main entry preferred title and, if appropriate, the authorized access point for the creator “main entry” reflects outmoded ‘catalog-card-speak’, related to cards in a file cabinet uniform title Two RDA counterparts: 1.       the preferred title and any differentiating information; 2.       a conventional collective title such as “Works” see reference variant access point see also reference authorized access point for related entity phys

MARC 21 FIELD TAG MARC 21 SUBFIELD CODE MARC 21 FIELD / SUBFIELD NAME RDA INSTRUCTION NUMBER RDA ELEMENT NAME 110 Main entry—Corporate name 19.2 Creator 110 Main entry—Corporate name 19.3 Other Person, Family, or Corporate Body Associated with a Work 110 a Corporate name or jurisdiction name as entry element 6.22 Signatory to a Treaty, etc. 110 a Corporate name or jurisdiction name as entry element 11.2.2 Preferred Name for the Corporate Body 110 a Corporate name or jurisdiction name as entry element 11.2.3 Location of Headquarters, etc. 110 a Corporate name or jurisdiction name as entry element 11.4.3 Date of Establishment 110 a Corporate name or jurisdiction name as entry element 11.4.4 Date of Termination 110 a Corporate name or jurisdiction name as entry element 11.5 Associated Institution 110 a Corporate name or jurisdiction name as entry element 11.7 Other Designation Associated with the Corporate Body 110 b Subordinate unit 11.2.2 Preferred Name for the Corpo

110 - Main Entry-Corporate Name (NR) First Indicator Second Indicator Type of corporate name entry element 0 - Inverted name 1 - Jurisdiction name 2 - Name in direct order Undefined # - Undefined Subfield Codes $a - Corporate name or jurisdiction name as entry element (NR) $b - Subordinate unit (R) $c - Location of meeting (R) $d - Date of meeting or treaty signing (R) $e - Relator term (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $k - Form subheading (R) $l - Language of a work (NR) $n - Number of part/section/meeting (R) $p - Name of part/section of a work (R) $t - Title of a work (NR) $u - Affiliation (NR) $0 - Authority record control number or standard number (R) $4 - Relator code (R) $6 - Linkage (NR) $8 - Field link and sequence number (R) FIELD DEFINITION AND SCOPE Corporate name used as a main entry in a bibliographic record. According to various cataloging rules, main entry under corporate name is assigned to

RDA is based on two international conceptual models, FRBR and FRAD, developed by working groups of the International Federation of Library Associations and Institutions (IFLA). You have already had classes on FRBR and FRAD, so we will only provide a little more background.  Another IFLA activity from 2003-2008 resulted in the Statement of International Cataloguing Principles (ICP). From the FRBR and FRAD models, RDA gets the entities, the identifying attributes for each entity, the relationships, and the user tasks. From ICP, RDA gets basic principles, such as the principle of representation and the principle of convenience of the user. International Cataloguing Principles It is important to note that, in the International Cataloguing Principles, the user comes first and should always be kept in mind when providing bibliographic descriptions and access points:  Convenience of the user  Representation  Common usage  Accuracy  Sufficiency and necessity  Signific

Following RDA example shows how RDA differs from AACR2 in regards to  books with text in both the original language and its translation(s) . This book has both the original work (in Sanskrit) and its English translation. Under AACR2, it would have been easier to see that there's a translation as there would have been a 240 of: 240 10 ‡a Pūyamēhavijñāna. ‡l English & Sanskrit Under RDA, there is no longer a 240 for this situation. Rather, there are 2 700s: 700 12 ‡a Koṭīśvaraśāstrī, Vēmpaṭi. ‡t Pūyamēhavijñāna. [for the original in Sanskrit] 700 12 ‡a Koṭīśvaraśāstrī, Vēmpaṭi. ‡t Pūyamēhavijñāna. ‡l English. [for the English translation] 010 __  |a  2009345913 025 __  |a  I-E-2009-345913; 44 040 __  |a  DLC  |b  eng  |c  DLC  |d  DLC  |e  rda 041 1_  |a  eng  |a  san  |h  san 042 __  |a  lcode  |a  pcc 050 00  |a  RC202  |b  .K67 2007 100 1_  |a  Koṭīśvaraśāstrī, Vēmpaṭi. 245 10  |a  Aupasargikatantrāntar

  http://resourcedescriptionandaccess.blogspot.com 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. RDA Blog  History:   RDA Blog  was created by  Salman Haider , a Cataloging & Metadata Libr