Identifying RDA Records

There are two indications that a record is an RDA bibliographic record:

• Leader/18 contains the value “i” (ISBD punctuation included) 

• Field 040 $e contains the code “rda”

[Source: Library of Congress]

Articles on Resource Description and Access (RDA)

Resource Description and Access (RDA) ➨ Articles

Tech Services on the Web: RESOURCE DESCRIPTION ANDACCESS (RDA) BLOG http://resourcedescriptionandaccess. blogspot. com EY Wong - Technical Services Quarterly, 2014 The frequency of the posts is steady throughout 2013. Some of the posts are extracts from RDA toolkit and other trusted cataloging sources; other posts are snapshots of cataloging records intended to provide interpretations on certain cataloging scenarios. The …

Implementing RDA at the University of Illinois at Urbana-Champaign Library Q Jin, JA Sandberg - Technical Services Quarterly, 2014

Technical Services Report: Cataloging in RDA and Linked Data environments. A Report of the ALCTS Cataloging & Metadata Management Section, Cataloging and … A Guimaraes - Technical Services Quarterly, 2014

Beyond Content, Media, and Carrier: RDA Carrier Characteristics S Bernstein - Cataloging & Classification Quarterly, 2014

RDA Display and the General Material Designation: An Innovative Solution RS Panchyshyn - Cataloging & Classification Quarterly, 2014

RDA: Strategies for Implementation D Sullivan - Australian Academic & Research Libraries, 2014

[PDF] Authors and Authorities in Post-RDA Library Systems: A Case Study HL Moulaison - 2014

RDA Training and Implementation at Duke University Libraries: Minimizing the Distraction AH Turner - Journal of Library Metadata, 2014

[PDF] Preparing LIS Students for a Career in Metadata Librarianship B Mooney Gonzales - SLIS Student Research Journal, 2014

RDA Cataloging Examples for Creating Variant Titles for Portion of Title Proper - Best Practices

Watch this video on YouTube on Resource Description & Access (RDA) Channel of RDA Blog

• For titles proper that contain an alternative title, ensure title access to the complete title proper to the first part of the title proper up-to the word "or" or equivalent in another language that signals an alternative title and to the part following the word "or" or its equivalent in another language.
• If the title proper contains a part or designation of a part, or both, make a variant title usually for the part when it is judged intelligible enough to be a likely candidate for access.
• Make a variant title for a portion of a title proper, when it is judged that some user would consider the portion as the title proper. 

• 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):

DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE - RDA EXAMPLES

DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE - RDA EXAMPLES
CASE	RDA / LC PCC-PS EXAMPLE
approximate date	[2014?]
supplied date	[2014]
date of publication not identified	[date of publication not identified]
two years	[2013 or 2014]
not before	264 #1 $a … $b … $c [not before 1980] 008/06 Type of date - q 008/07-10 - 1980 008/11-14 - uuuu
not after	264 #1 $a … $b … $c [not after 1980] 008/06 Type of date - q 008/07-10 - uuuu 008/11-14 - 1980
betwen years with date	[between March 13, 2000 and July 10, 2014]
betwen years with date	264 #1 $a … $b … $c [between 1993 and 1999] 008/06 Type of date - q 008/07-10 - 1993 008/11-14 - 1999

<<<<<=====>>>>>

Note: Please supply cases and solutions quoting proper RDA rules where date of publication not identified. It will be included in this table along with name of the cataloger. Write your suggestions in the "comments" section of this blog post.

<<<<<=====>>>>>

A. If an item lacking a publication date contains only a copyright date, apply the following in the order listed:

A.1. Supply a date of publication that corresponds to the copyright date, in square brackets, if it seems reasonable to assume that date is a likely publication date.

A.2. If the copyright date is for the year following the year in which the publication is received, supply a date of publication that corresponds to the copyright date.

B. If an item lacking a publication date contains a copyright date and a date of manufacture and the year is the same for both, supply a date of publication that corresponds to that date, in square brackets, if it seems reasonable to assume that date is a likely publication date.

C. If an item lacking a publication date contains a copyright date and a date of manufacture and the years differ, supply a date of publication that corresponds to the copyright date, in square brackets, if it seems reasonable to assume that date is a likely publication date. A manufacture date may also be recorded as part of a manufacture statement, or recorded as part of a Note on issue, part, or iteration used as the basis for identification of a resource (See 2.17.13), if determined useful by the cataloger.

D. If an item lacking a publication date contains only a date of distribution, apply the following in the order listed:

D.1. Supply a date of publication that corresponds to the distribution date, in square brackets, if it seems reasonable to assume that date is a likely publication date. Also record a date of distribution as part of a distribution statement if determined useful by the cataloger.

D.2. If it does not seem reasonable to assume that the distribution date is a likely publication date, supply a date of publication, in square brackets, based on the information provided. Also record the distribution date as part of a distribution statement if determined useful by the cataloger.

E. If an item lacking a publication date contains only a date of manufacture, apply the following in the order listed:

E.1. Supply a date of publication that corresponds to the manufacture date, in square brackets, if it seems reasonable to assume that date is a likely publication date. For books, this means that the item is assumed to be the first printing of the edition. Also record the manufacture date as part of a manufacture statement if determined useful by the cataloger.

E.2. If the date of manufacture given implies that it is not likely the same as the date of publication, supply a date of publication, in square brackets, using the information provided. A manufacture date may also be recorded as part of a manufacture statement, or recorded as part of a Note on issue, part, or iteration used as the basis for identification of a resource (See 2.17.13), if determined useful by the cataloger.

Source with RDA Examples in MARC 21: DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE - LC-PCC PS FOR 2.8.6.6

• 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):

RDA BLOG - NEW UPDATES

1. RDA page: A blog page is added giving brief introduction and overview of Resource Description & Access (RDA).

2. Categories: on the right side has been significantly consolidated and modified. 

3. RDA Resources: page is modified. This page now includes Cataloger's Reference Directory having useful links to web-resources for catalogers.

4. A "scrolling bar": appears at the bottom listing select feedback from the RDA Blog Testimonials page.

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

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

Authorized Access Point - Main Entry - Uniform Title (AACR2) / Preferred Title (RDA) - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
130		Main entry—Uniform title
130	a	Uniform title	6.2.2	Preferred Title for the Work
130	a	Uniform title	6.3	Form of Work
130	a	Uniform title	6.4	Date of Work
130	a	Uniform title	6.5	Place of Origin of the Work
130	a	Uniform title	6.6	Other Distinguishing Characteristic of the Work
130	d	Date of treaty signing	6.4	Date of Work
130	f	Date of a work	6.10	Date of Expression
130	g	Miscellaneous information	N/A
130	h	Medium	6.9	Content Type
130	k	Form subheading	6.2.2	Preferred Title for the Work
130	l	Language of a work	6.11	Language of Expression
130	m	Medium of performance for music	6.15	Medium of Performance
130	n	Number of part/section of a work	6.2.2	Preferred Title for the Work
130	n	Number of part/section of a work	6.3	Form of Work
130	n	Number of part/section of a work	6.4	Date of Work
130	n	Number of part/section of a work	6.5	Place of Origin of the Work
130	n	Number of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
130	n	Number of part/section of a work	6.16	Numeric Designation of a Musical Work
130	o	Arranged statement for music	6.12	Other Distinguishing Characteristic of the Expression
130	p	Name of part/section of a work	6.2.2	Preferred Title for the Work
130	p	Name of part/section of a work	6.3	Form of Work
130	p	Name of part/section of a work	6.4	Date of Work
130	p	Name of part/section of a work	6.5	Place of Origin of the Work
130	p	Name of part/section of a work	6.6	Other Distinguishing Characteristic of the Work
130	r	Key for music	6.17	Key
130	s	Version	6.12	Other Distinguishing Characteristic of the Expression
130	t	Title of a work	N/A

[Source: RDA Toolkit]

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

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

130 - Main Entry - Uniform Title (AACR2) / Preferred Title (RDA) - [NR]

130 - Main Entry-Uniform Title (NR)

First Indicator	Second Indicator
Nonfiling characters 0-9 - Number of nonfiling characters	Undefined # - Undefined

---

Subfield Codes
$a - Uniform title (NR) $d - Date of treaty signing (R) $f - Date of a work (NR) $g - Miscellaneous information (R) $h - Medium (NR) $k - Form subheading (R) $l - Language of a work (NR) $m - Medium of performance for music (R) $n - Number of part/section of a work (R)	$o - Arranged statement for music (NR) $p - Name of part/section of a work (R) $r - Key for music (NR) $s - Version (NR) $t - Title of a work (NR) $0 - Authority record control number or standard number (R) $6 - Linkage (NR) $8 - Field link and sequence number (R)

---

FIELD DEFINITION AND SCOPE

Uniform title used as a main entry in a bibliographic record.

Main entry under a uniform title is used when a work is entered directly under title and the work has appeared under varying titles, necessitating that a particular title be chosen to represent the work. Cataloging rules also prescribe the use of this field when the work is entered directly under title and additions or deletions to the title proper must be accommodated. In this latter case, the title may not actually vary from iteration to iteration. The title that appears on the work being cataloged is contained in field 245. There will be no 100, 110, or 111 field in records with field 130.

---

GUIDELINES FOR APPLYING CONTENT DESIGNATORS

Descriptions of the first indicator position and all subfield codes, as well as input conventions for the 130 field, are given in the X30 Uniform Titles-General Information section. Because the second indicator is different for various X30 fields, it is not described in the general information section, but is described below.

■ INDICATORS

Second Indicator - Undefined

Undefined and contains a blank (#).

See also: 

• Library of Congress >> MARC >> Bibliographic >> 1XX >> 130 [LC]
• 130  Main Entry–Uniform Title (NR) [OCLC]

The Structure of RDA

General Structure

Remember that RDA has a clear structure:

• Table of Contents
• Introduction
• Specific instructions

o   Entities and their attributes

·            Group 1 (WEMI) (Chapters 1-7)

·            Group 2 (PFC) (Chapters 8-16)

o   Relationships (Chapters 17-22, 24-32)

• Appendices for

o   Abbreviation

o   Capitalization

o   Relationship designators (more on this later)

• Glossary with links to the text of the instructions
• Index

Not Organized Like AACR2

The organization of RDA is very different from AACR2. Instead of separate chapters for classes of materials (books, cartographic materials, printed music, etc.), RDA is principle-based and organized around the FRBR/FRAD tasks to help users “identify” and “relate” the resources they need from our collections. There are general instructions applying to all resources with specific instructions for characteristics unique to certain categories of resources.

The identifying elements for each thing we are describing are addressed separately in each chapter. RDA provides instructions on what identifying elements are needed; for those chapters related to access points, it then provides -- at the end of those chapters -- the instructions on how to assemble those elements to create authorized access points (remember, that’s what AACR2 calls headings). We will see this particularly in chapter 6 and chapters 9-11.

Not a Linear Resource

When you use online tools, you don’t read the content in the same way as you read a printed text.  You don’t generally read linearly from one page to the next. Instead, you read purposefully.  You perform keyword searches (and then view several hits from the results list), follow links, and jump to elements from a Table of Contents or other navigational feature

Some of the “length” of RDA is due to the need for duplicating content to serve the catalogers who will be arriving at that content in these different ways from different starting points.

ALA also publishes a print version of RDA. A print version of the RDA element set (a subset of the RDA content, organized by FRBR and FRAD entity) is also available from ALA Publishing.

“Core-ness”

Core Elements ➨ Core elements in Resource Description &amp; Access (RDA) are minimum elements required for describing resources. Core elements are a new feature of RDA which allowed for certain metadata elements to be identified as “required” in the cataloging process. The assignment of core status is based on attributes mandatory for a national level record, as documented in the FRBR/FRAD modules. ... ... ... ... (Visit below link to read complete article)

Read now complete article: Core Elements : Glossary of Library & Information Science

Alternatives, Options, and Exceptions

Contents:

• Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know
• What are RDA Alternatives?
• Example of RDA Alternatives
• What are RDA Options?
• Example of RDA Optional Additions
• Example of RDA Optional Omissions
• What are RDA Exceptions? 
• Example of RDA Exceptions
• How to decide whether to apply the alternatives, options, or exceptions?
• Note on the use of screen images from RDA Toolkit (Following RDA and RDA Toolkit Copyright Statement and guidelines)

Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know

RDA contains a number of guidelines and instructions that are marked as alternatives, options (optional additions, optional omissions), and exceptions. Each of these is clearly identified by an italicized label, which in the RDA Toolkit appears in green color in the instruction (alternative, optional addition, optional omission, exception). A green vertical bar also appears in the left margin next of an alternative, optional, or exceptional instruction in RDA Toolkit. These allow individual libraries or cataloging agencies to make decisions based on individual considerations in cases where two or more provisions are equally valid. Guidelines for alternatives and options are provided in RDA rule 0.8, and instructions for applying exceptions is at RDA 0.9 of chapter 0. ... ... ... 

Read now complete article: Alternatives Options and Exceptions in RDA : What Every Cataloger Needs to Know

Library of Congress Policy Statements

LC has created an extensive body of Library of Congress Policy Statements (LCPS), to facilitate a standard interpretation and application of these alternatives, options, and exceptions.  Think of these as the ‘RDA version’ of the LC Rule Interpretations. Be sure to consult and follow the LCPS in all such cases. To access the LCPS, click on the green “LCPS” link in the RDA Toolkit. [Note: LCPS is now LC-PCC PS]

Examples

The examples in RDA illustrate the application of the specific instruction under which they appear. They illustrate only the data that are addressed by that instruction. They are normally given without showing the preceding or enclosing punctuation that is prescribed for an ISBD presentation. All examples illustrate elements as they would be recorded by an agency whose preferred language is English.

Examples appear in yellow shading, clearly setting them off from the instructions themselves.