RDA Blog Pages

RDA Blog Pages (Click image to enlarge)

| About Me | RDA | About RDA Blog | RDA Resources | Cataloger’s Reference Directory | Contact Us | RDA Blog Testimonials |

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

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

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]