Wednesday, February 26, 2014

RDA Terminology

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

physical description
carrier description

general material designator
three elements:
1.      content type
2.      media type
3.      carrier type
GMD was an inconsistent presentation of different categories of information
chief source
preferred sources
This is not only a change in terminology; ‘sources’ have been expanded from a single source to multiple sources

[Source: Library of Congress]

Sunday, February 23, 2014

Authorized Access Point - Corporate Name - MARC to RDA Mapping

MARC 21
FIELD
TAG
MARC 21
SUBFIELD CODE
MARC 21 FIELD /
SUBFIELD NAME
RDA
INSTRUCTION
NUMBER
RDA
ELEMENT
NAME
110Main entry—Corporate name19.2Creator
110Main entry—Corporate name19.3Other Person, Family, or Corporate Body Associated with a Work
110aCorporate name or jurisdiction name as entry element6.22Signatory to a Treaty, etc.
110aCorporate name or jurisdiction name as entry element11.2.2Preferred Name for the Corporate Body
110aCorporate name or jurisdiction name as entry element11.2.3Location of Headquarters, etc.
110aCorporate name or jurisdiction name as entry element11.4.3Date of Establishment
110aCorporate name or jurisdiction name as entry element11.4.4Date of Termination
110aCorporate name or jurisdiction name as entry element11.5Associated Institution
110aCorporate name or jurisdiction name as entry element11.7Other Designation Associated with the Corporate Body
110bSubordinate unit11.2.2Preferred Name for the Corporate Body
110cLocation of meeting11.3.2Location of Conference, etc.
110cLocation of meeting11.5Associated Institution
110dDate of meeting or treaty signing11.4.2Date of Conference, etc.
110dDate of meeting or treaty signing6.4Date of Work
110eRelator term18.5Relationship Designator
110fDate of a work6.10Date of Expression
110gMiscellaneous information11.7Other Designation Associated with the Corporate Body
110kForm subheading6.2.2Preferred Title for the Work
110lLanguage of a work6.11Language of Expression
110nNumber of part/section/meeting6.2.2Preferred Title for the Work
110nNumber of part/section/meeting6.3Form of Work
110nNumber of part/section/meeting6.4Date of Work
110nNumber of part/section/meeting6.5Place of Origin of the Work
110nNumber of part/section/meeting6.6Other Distinguishing Characteristic of the Work
110nNumber of part/section/meeting11.6Number of a Conference, etc.
110pName of part/section of a work6.2.2Preferred Title for the Work
110pName of part/section of a work6.3Form of Work
110pName of part/section of a work6.4Date of Work
110pName of part/section of a work6.5Place of Origin of the Work
110pName of part/section of a work6.6Other Distinguishing Characteristic of the Work
110tTitle of a work6.2.2Preferred Title for the Work
110tTitle of a work6.3Form of Work
110tTitle of a work6.4Date of Work
110tTitle of a work6.5Place of Origin of the Work
110tTitle of a work6.6Other Distinguishing Characteristic of the Work
110uAffiliation11.9Address of the Corporate Body

[Source: RDA Toolkit]

See also:

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

110 - Main Entry-Corporate Name (NR) - MARC21

110 - Main Entry-Corporate Name (NR)

First IndicatorSecond 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 works that represent the collective thought of a body.
Conference and meeting names that are entered subordinately to a corporate body are contained in this field rather than in field 111.

See also:

Saturday, February 8, 2014

FRBR as a Foundation of RDA

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 
  • Significance 
  • Economy 
  • Consistency and standardization 
  • Integration 
  • Defensible, not arbitrary 
If you wish to contradict one of these principles, you must devise a defensible, practical solution.


FRBR and RDA


FRBR offers a structure to address user tasks, and FRBR entities and elements translate into RDA as the data elements for bibliographic description and access, and the relationships among entities. RDA combines the FRBR conceptual model with cataloging principles to provide the foundations to build cataloger judgment and better systems for the future. FRBR is not itself a cataloging code. But it demonstrates how users can benefit from a well-structured system designed around the FRBR entities and relationships. 


Collocation


In today’s environment, we still want systems to fulfill the collocation objectives we had for catalogs in the past. We still want them to display: 
  • the works associated with a person 
  • the expressions of the same work 
  • the manifestations of the same expression 
  • the items or copies of the same manifestation 
  • related works 
We want all of this, and more. We want to utilize “linked data systems” to guide a user through our rich collections and beyond. RDA helps make this possible, and encourages the designers of systems to make use of the model and data in new ways.

[Source: Library of Congress]

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

RDA Example : Translations in RDA : RDA vs AACR2 : Book with both the Original Work and its Translation

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
0411_ |a eng |a san |h san
042__ |a lcode |a pcc
05000 |a RC202 |b .K67 2007
1001_ |a Koṭīśvaraśāstrī, Vēmpaṭi.
24510 |a Aupasargikatantrāntargata Pūyamēha vijn̄ānam / |c Vempati Kōṭēśvara Śāstri Gāru, Nāgalingam Viśvanāṭha Śāstri Gāru ; translation with critical commentary, M. Srinivasulu, C. Narmada Reddy ; chief editor, G.S. Lavekar ; editor, A. Narayana.
2463_ |a Pūyamēha vijn̄ānam
250__ |a First edition.
264_1 |a Nai Dilli : |b Central Council for Research in Ayurveda & Siddha, |c 2007.
300__ |a xvii, 228 pages ; |c 25 cm
336__ |a text |2 rdacontent
337__ |a unmediated |2 rdamedia
338__ |a volume |2 rdacarrier
546__ |a In English and Sanskrit |b (Sanskrit in roman and Devanagari).
520__ |a Gonorrhea management within the theoretical and practical framework of ayurvedic principles.
504__ |a Includes bibliographical references (page 228).
650_0 |a Gonorrhea |x Ayurvedic treatment.
650_0 |a Medicine, Ayurvedic.
7001_ |a Viśvanāthaśāstri, Nāgalingam.
7001_ |a Lavekar, G. S.
7001_ |a Nārāyaṇa, Alā.
7001_ |a Srinivasulu, M.
7001_ |a Narmada Reddy, C.
70012 |a Koṭīśvaraśāstrī, Vēmpaṭi. |t Pūyamēhavijñāna.
70012 |a Koṭīśvaraśāstrī, Vēmpaṭi. |t Pūyamēhavijñāna. |l English.
7102_ |a Central Council for Research in Ayurveda and Siddha (India)


When you do shelflisting, look out for clues such as the above that will help you know that there is a translation involved. And remember to apply the Translation Table from G 150 to the call number.

[Source: http://lccn.loc.gov/2009345913]



Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Sunday, February 2, 2014

Weekly Insights for the Resource Description and Access (RDA) Blog

 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 AccessFRBRFRADFRSADMARC standardsAACR2BIBFRAME, 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 Librarian Blogger & Online Social Media Expert from India. RDA Blog embarked on its journey to provide useful information to Resource Description and Access (RDA) in August 2011. It received good response from librarians, catalogers, and library professionals from all around the world. It is interesting to note that the first hundred thousand pageviews to RDA Blog came in 3 years, but it took just 8 months to reach another hundred thousand pageviews. At present it is viewed at a rate of fifteen to twenty thousand times per month. RDA Blog is widely followed in social media.

See also:

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):