Resource Description & Access (RDA)

RDA Blog or Resource Description & Access (RDA) 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 Cataloguing Rules (AACR2). Free for everyone Forever.

Sunday, January 5, 2014

RDA INDEX - AVAILABLE FREE FROM RDA TOOLKIT

Authorized Access Point - Personal Name - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
100		Main entry—Personal name	19.2	Creator
100		Main entry—Personal name	19.3	Other Person, Family, or Corporate Body Associated with a Work
100 1st indicator 0 or 1	a	Personal name	9.2.2	Preferred Name for the Person
100 1st indicator 0 or 1	b	Numeration	9.2.2	Preferred Name for the Person
100 1st indicator 0 or 1	c	Titles and other words associated with a name	9.4	Title of the Person
100 1st indicator 0 or 1	c	Titles and other words associated with a name	9.6	Other Designation Associated with the Person
100 1st indicator 0 or 1	c	Titles and other words associated with a name	9.15	Field of Activity of the Person
100 1st indicator 0 or 1	c	Titles and other words associated with a name	9.16	Profession or Occupation
100 1st indicator 0 or 1	d	Dates associated with a name	9.3	Date Associated with the Person
100 1st indicator 0 or 1	j	Attribution qualifier	N/A
100 1st indicator 0 or 1	q	Fuller form of name	9.5	Fuller Form of Name
100 1st indicator 0 or 1	u	Affiliation	9.12	Address of the Person
100 1st indicator 0 or 1	u	Affiliation	9.13	Affiliation
100 1st indicator 3	a	Personal name	10.2.2	Preferred Name for the Family
100 1st indicator 3	a	Personal name	10.3	Type of Family
100 1st indicator 3	c	Titles and other words associated with a name	10.5	Place Associated with the Family
100 1st indicator 3	d	Dates associated with a name	10.4	Date Associated with the Family
100 1st indicator 3	g	Miscellaneous information	10.6	Prominent Member of the Family
100 1st indicator 0, 1 or 3	e	Relator term	18.5	Relationship Designator
100 1st indicator 0, 1 or 3	f	Date of a work	6.10	Date of Expression
100 1st indicator 0, 1 or 3	k	Form subheading	6.2.2	Preferred Title for the Work
100 1st indicator 0, 1 or 3	l	Language of a work	6.11	Language of Expression
100 1st indicator 0, 1 or 3	n	Number of part/section of a work	6.2.2	Preferred Title for the Work
100 1st indicator 0, 1 or 3	n	Number of part/section of a work	6.3	Form of Work
100 1st indicator 0, 1 or 3	n	Number of part/section of a work	6.4	Date of Work
100 1st indicator 0, 1 or 3	n	Number of part/section of a work	6.5	Place of Origin of the Work
100 1st indicator 0, 1 or 3	n	Number of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
100 1st indicator 0, 1 or 3	p	Name of part/section of a work	6.2.2	Preferred Title for the Work
100 1st indicator 0, 1 or 3	p	Name of part/section of a work	6.3	Form of Work
100 1st indicator 0, 1 or 3	p	Name of part/section of a work	6.4	Date of Work
100 1st indicator 0, 1 or 3	p	Name of part/section of a work	6.5	Place of Origin of the Work
100 1st indicator 0, 1 or 3	p	Name of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
100 1st indicator 0, 1 or 3	t	Title of a work	6.2.2	Preferred Title for the Work
100 1st indicator 0, 1 or 3	t	Title of a work	6.3	Form of Work
100 1st indicator 0, 1 or 3	t	Title of a work	6.4	Date of Work
100 1st indicator 0, 1 or 3	t	Title of a work	6.5	Place of Origin of the Work
100 1st indicator 0, 1 or 3	t	Title of a work	6.6	Other Distinguishing Characteristic of the Work

[Source: RDA Toolkit]

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, testimonials, likes, +1, tweets and shares ....

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

100 - Main Entry-Personal Name (NR)

First Indicator

Second Indicator

Type of personal name entry element
0 - Forename
1 - Surname
3 - Family name

Subfield Codes

$a - Personal name (NR) $b - Numeration (NR) $c - Titles and words associated with a name (R) $d - Dates associated with a name (NR) $e - Relator term (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $j - Attribution qualifier (R) $k - Form subheading (R) $l - Language of a work (NR)	$n - Number of part/section of a work (R) $p - Name of part/section of a work (R) $q - Fuller form of name (NR) $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)

Undefined
# - Undefined

FIELD DEFINITION AND SCOPE

Personal name used as a main entry in a bibliographic record.

Main entry is assigned according to various cataloging rules, usually to the person chiefly responsible for the work.

See also:

Planning and Preparing for RDA -- eCourse facilitated by Magda El-Sherbini

New eCourse! Planning and Preparing for RDA: Resource Description and Access facilitated by Magda El-Sherbini Now is the perfect time for anyone involved in cataloging and technical services to prepare and put plans in place for implementing RDA. An active participant in development of the RDA instructions, Magda El-Sherbini will lead this 4-week, asynchronous eCourse, beginning February 17, to help you get started. This eCourse features updated content that reflects new developments in RDA. After taking this eCourse you will be able to: Explain the conceptual difference between AACR2 and RDA Craft cataloging policies and procedures Create a staff training plan Draft an RDA implementation plan Craft strategies for communicating about RDA throughout the library
Also of interest
RDA: Strategies for Implementation Magda El-Sherbini	RDA and Serials Cataloging Ed Jones
Introducing RDA bundle Chris Oliver, Karen Coyle	RDA Toolkit The unique and complete source for RDA, and more

Shop the ALA Store for a full selection of products!
Follow ALA Editions on alaeditions.org, Facebook and Twitter!
ALA Store purchases fund advocacy, awareness and
accreditation programs for library professionals worldwide.

Sunday, December 29, 2013

Compilation with the original language and 2 translations : RDA Example

CASE: Compilation with the Original language and Translations in two Languages
Look at the following record from the LC Online Catalog and note the RDA cataloging treatment for preferred title:

010	__ \|a 2013317195
020	__ \|a 9789350870730
025	__ \|a I-San-2013-317195; 15
040	__ \|a DLC \|b eng \|c DLC \|e rda
041	1_ \|a eng \|a hin \|a san \|h san
042	__ \|a lcode
050	00 \|a MLCSA 2013/01309 (P) \|a PK3799.J36
100	1_ \|a Jānī, Jayadeva Aruṇodaya, \|e author.
245	10 \|a Kathākusumadvāṣaṣṭiḥ / \|c Rasarājaviracitā = Rasaraja’s 62 small flowery stories = 62 kathākusuma / Rasarāja- viracitā ; edited with English & Hindi translation by Dr. Gargi C. Pandit, Dr. Kalpana V. Gandhi, Varda A. Vasa, Vaidehi C. Pandit, Kaushalya R. Rajpurohit, Kamakshi H. Jani.
246	31 \|a Rasaraja’s 62 small flowery stories
246	31 \|a 62 kathākusuma
264	_1 \|a Baroda : \|b Savitri Prakashan, \|c 2013.
300	__ \|a xxiv, 348 pages ; \|c 22 cm
336	__ \|a text \|2 rdacontent
337	__ \|a unmediated \|2 rdamedia
338	__ \|a volume \|2 rdacarrier
500	__ \|a Short stories.
546	__ \|a English, Hindi, and Sanskrit.
520	__ \|a Sanskrit short stories with English and Hindi translation.
700	1_ \|a Pandit, Gargi C., \|e editor.
700	12 \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭi.
700	12 \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭi. \|l English.

700	12 \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭi. \|l Hindi. (not provided in bibliographic record by the cataloger, as access for one/first translation is core, as given for English(second analytical); this (third) analytical entry can also be given, but is optional.

NOTE: NAR is created for the first two analytical entries.

LC control no.:	n 2012218836
LCCN permalink:	http://lccn.loc.gov/n2012218836
HEADING:	Jānī, Jayadeva Aruṇodaya. Kathākusumadvāṣaṣṭi
000	00528cz a2200157n 450
001	9350351
005	20130903231643.0
008	130903n\| azannaabn \|a aaa
010	__ \|a n 2012218836
040	__ \|a DLC \|b eng \|c DLC \|e rda
046	__ \|k 2013
100	1_ \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭi
370	__ \|g Vadodara, India
400	1_ \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭiḥ
400	1_ \|a Jānī, Jayadeva Aruṇodaya. \|t 62 kathākusuma
670	__ \|a Kathākusumadvāṣaṣṭiḥ, 2013.

LC control no.:	n 2012218837
LCCN permalink:	http://lccn.loc.gov/n2012218837
HEADING:	Jānī, Jayadeva Aruṇodaya. Kathākusumadvāṣaṣṭi. English
000	00475cz a2200145n 450
001	9350352
005	20130903231854.0
008	130903n\| azannaabn \|a aaa
010	__ \|a n 2012218837
040	__ \|a DLC \|b eng \|c DLC \|e rda
046	__ \|k 2013
100	1_ \|a Jānī, Jayadeva Aruṇodaya. \|t Kathākusumadvāṣaṣṭi. \|l English
370	__ \|g Vadodara, India
400	1_ \|a Jānī, Jayadeva Aruṇodaya. \|t Rasaraja’s 62 small flowery stories
670	__ \|a Kathākusumadvāṣaṣṭiḥ, 2013.

============================================

Question: In which case 240 and 7xx for original title to be there?

Answer: (with remarks from experts from LC) What we have here is a compilation with the original language and 2 translations. The 1st question we have to ask is for the preferred title, do we go 1. with the "commonly known" title (Kathākusumadvāṣaṣṭi … ) or 2. with the conventional collective title (Short stories. Selections … ). Here, it's best practice to go with the "commonly known" title. The 3 analytical 700s that you have given are correct. The 240 should not be used here in these situations (whenever there are more than one language presented).

Friday, December 20, 2013

How Did RDA Come To Be?

AACR3?

In the late 1990’s the Joint Steering Committee for Revision of the Anglo-American Cataloguing Rules decided to make changes for the future of AACR. It realized that the changes that give us a new way to look at our environment also give us new opportunities to improve how we deliver bibliographic information to users.

Resource Description and Access

In 2002, work had begun on a revision of AACR2, called AACR3. However, by April 2005, the plan had changed. The reactions to an initial draft raised particular concerns about the need to move to closer alignment with the FRBR model and to build an element set. It was clear that we could not continue doing cataloging the way we always had. We could no longer produce records in MARC format in systems that could not talk to the rest of the information community.

A new plan was developed and the name was changed to Resource Description and Access to emphasize the two important tasks. Importantly, the Anglo-American emphasis was removed.

Collaboration with Other Communities

The Joint Steering Committee (JSC) for the Development of RDA has paid close attention to developments in IFLA as well as in various metadata communities, and initiated collaborations with the publishers’ community who were developing their own metadata set called ONIX. Together these parties developed controlled vocabularies for media types, content types, and carrier types (called the RDA/ONIX Framework).

In 2007, JSC representatives met with key collaborators and agreed to examine the fit between RDA and other metadata models. Together we have created an initial registry for the RDA elements and controlled terms, available freely on the Web.

In 2008 the JSC started participating in a joint effort to determine what revisions are necessary to accommodate the encoding of RDA in MARC 21. The RDA/MARC Working Group has presented proposals to MARBI (the Machine-Readable Bibliographic Information committee of ALA), many of which have already been approved.

RDA addresses all types of materials collected by libraries, but defers to specialized cataloging manuals for more specific rules needed for some types of materials -- for cultural objects, rare materials, cartographic resources, and more. In some cases, there will be a transition or “bridge” period to move from current practices and formats and systems to the next generation.

A Tool for the Digital World

The Joint Steering Committee stated among the goals for RDA that it was to be a tool designed for the digital world. This had several implications:

RDA was to be a Web-based tool optimized for use as an online product. The result is the RDA Toolkit, which continues to be refined with feedback from users.
RDA was to be a tool that addresses cataloging all types of content and media
RDA was to be a tool that results in records that are intended for use in the digital environment, through the Internet, Web-OPACs, etc.
RDA was intended to result in records with a metadata set of elements intended to be readily adaptable to newly emerging database structures.

RDA Specific Goals

Although not all of the stated goals for RDA have yet been reached, but good progress is being made and proposals for improvements are still welcome. Specifically, RDA rules were to: