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.

Monday, June 3, 2013

Choosing the Preferred Name in Conferences, Seminars, Workshops, etc

l RDA 11.2.2.2

Sources of Information:

“Determine the preferred name for a corporate body from the following sources (in order of preference):

a) the preferred sources of information (see 2.2.2) in resources associated with the corporate body

b) other formal statements appearing in resources associated with the corporate body

c) other sources (including reference sources)”

l RDA 11.2.2.5

Different Forms of the Same Name:

“If different forms of a corporate body's name appear in resources associated with the body, apply the general instructions given below. When appropriate, apply the special instructions given under 11.2.2.5.1–11.2.2.5.4 as well.”

l RDA 11.2.2.5

Different Forms of the Same Name:

Order of preference:

• Form appearing in preferred sources of information

• Form presented formally on preferred source, if more than one

• Most commonly found form

• Brief form that would differentiate the body

l RDA 11.2.2.5.1

Variant Spellings :

“If variant spellings of the name appear in resources associated with the body, choose the form found in the first resource received.”

l RDA 11.2.2.5.2

More Than One Language Form of the Name:

Order of preference:

• Form in the official language of the body.

l LCPS: If there is more than one official language and one of these is English, choose the form in English

• Form in language used predominantly in resources

• Form that is presented first in the first resource received

[Source: Library of Congress RDA Training materials]

Conferences, meetings, exhibitions, fairs and festivals

These events now have the same rules

l RDA 11.2.2.11

Number or Year of Convocation of a Conference, Etc.:

“Omit from the name of a conference, congress, meeting, exhibition, fair, festival, etc. […] indications of its number, or year or years of convocation, etc.”

l No instruction to remove an indication of frequency (Annual, Biennial, etc.)

<<<<----------------->>>>

Examples:

l Omit year of convocation:

• CAV (Conference)

l NOT

• CAV ’91

l Retain indication of frequency (Annual, Biennial, etc.):

• Annual Conference on Fishing

l NOT

• Conference on Fishing [with “Annual” omitted]

[Source: Library of Congress RDA Training materials]

Named Conferences

Under RDA a conference name need not contain a word that denotes a conference, to be considered named

LCRI 21.1.B1 has no equivalent in RDA or in the LC-PCC PS

~~• LCRI 21.1.B1:~~

~~• “… when deciding whether a phrase is a name is that the phrase must include a word that connotes a meeting: "symposium," "conference," "workshop," "colloquium," etc.”~~

<<<<----------------->>>>

A named conference need only fulfill these RDA definitions

l RDA 8.1.2

Person, Family, and Corporate Body:

“The term corporate body refers to an organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit.”

l RDA 8.1.3

Name:

“The term name refers to a word, character, or group of words and/or characters by which a person, family, or corporate body is known.”

<<<<----------------->>>>

l Conference names eligible for use as an authorized access point (111 or 711)

• Freedom & Faith

• Digital Library Futures: User Perspectives and Institutional Strategies

l Considered unnamed under AACR2, but named under RDA

l May not convey the idea of a corporate body (conference)

<<<<----------------->>>>

Additions to names

l RDA 11.7.1.4

Names Not Conveying the Idea of a Corporate Body:

“If the preferred name for the body does not convey the idea of a corporate body, record a suitable designation in the language preferred by the agency creating the data.”

l Examples:

• Freedom & Faith (Conference) (1984 : Saint Charles, Ill.)

• Digital Library Futures: User Perspectives and Institutional Strategies (Conference) (2009 : Milan, Italy)

<<<<----------------->>>>

See also LC-PCC PS for 11.7.1.4

l Initialisms and Acronyms

• “If the name chosen for the authorized access point for a corporate body is an initialism or acronym written in all capital letters (with or without periods between them), add a qualifier to the name.”

l Example:

CICA (Conference) (2011 : Hangzhou, China)

<<<<----------------->>>>

[Source: Library of Congress RDA Training Materials]

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

Thursday, May 30, 2013

RECORDING VARIANT TITLES IN RDA

RDA Examples of Variant Titles in MARC 21

EXAMPLE

245 10 $a XX centuries & Mt. St. Helens ...
246 3# $a 20 centuries and Mount Saint Helens

246 3# $a Twenty centuries and Mount Saint Helens

Monday, May 27, 2013

Use of 500 and 510 Field to Show Relationships in a Corporate Body Name

RDA RELATIONSHIP DESIGNATORS

RDA Cataloging Examples of Relationships in a Corporate Body Name : Founder ; Hierarchical superior

Click on image to enlarge

(note the use of relationship designator in 510 field)
(note NAR change from AACR2 to RDA in 410 field)

<<<<<---------->>>>>

RDA Cataloging Examples of Relationships in a Corporate Body Name : Successor ; Predecessor ; Hierarchical superior ;

Click on image to enlarge

[Revised on 2015-04-13]

<<<<<---------->>>>>

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:

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

Thursday, May 23, 2013

Copy Cataloging in RDA documentation -- Library of Congress

Instructions for copycat in RDA>>

Copy Cataloging Using RDA

Trainee Manual (May 2013) [Word : 6.28 MB]
Instructor Manual (May 2013) [Word : 6.30 MB]
Exercise Answers (May 2013) [Word : 6.17 MB]

(Source: Library of Congress (LC) RDA Training Materials)

Tuesday, May 21, 2013

Single Portfolio or Case

RDA Rule 3.4.5.15 is for Single Portfolio or Case. According to this rule for a resource consisting of one or more sheets, etc., housed in a single portfolio or case, extent may be recorded as:

300 $a 1 portfolio or

300 $a 1 case

Optionally it can be given as:

1 portfolio (502 leaves)

For cases consisting of two or more volumes RDA Rule is 3.4.5.16.

Example: https://lccn.loc.gov/2012324300

[Source: Based on information from RDA Toolkit and LC online catalog]

Monday, May 20, 2013

Field 040 Subfield Order

Field 040 Subfield Order in Serial RDA Records

The correct 040 subfield order for CONSER RDA serials in OCLC is: $a $b $e $c $d

Example:

040 DLC ǂb eng ǂe rda ǂc DLC ǂd OCLCQ ǂd CLU ǂd DLC

Field 040 Subfield Order in LC RDA Records (Bibliographic)

040 ‡a DLC ‡b eng ‡e rda ‡c DLC

Field 040 Subfield Order in LC RDA Records (Authority)

040 ‡a DLC ‡b eng ‡e rda ‡c DLC

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

Using Wikipedia in Authority Work

PSD, Library of Congress guidelines on Using Wikipedia in Authority Work

(click picture to enlarge)

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

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

Saturday, May 11, 2013

RECORDING SCRIPTS IN RDA

LC-PCC PS for 7.13.2

SCRIPT

CORE ELEMENT FOR LC/PCC

Script is a core element for LC if a language is commonly written in more than one script, and if the resource is in a script other than the primary one for the language.

[2012-05]

LC-PCC PS for 7.13.2.3

RECORDING SCRIPTS

Form of Script Name

LC practice/PCC practice: Use the English language names of scripts found at: 〈http://www.unicode.org/iso15924/iso15924-en.html

〉. Generally do not include the parenthetical information found in the list when recording the script name.

If a resource is in a language that is commonly written in more than one script, name both the language and the script.

EXAMPLE

546

$a Konkani $b Kannada.

546

$a Konkani $b Devanagari.

546

$a Serbian $b Latin.

546

$a Serbian $b Cyrillic.

546

$a Syriac $b Nestorian.

Applicability

LC practice/PCC practice: If the resource is in a script other than the primary one for the language, name both the language and the script in the language note (MARC field 546

EXAMPLE

546

$a Panjabi.

For a publication using the Gurmukhi script

but

546

$a Panjabi $b Devanagari.

For a publication using the Devanagari script

546

$a Sindhi.

For a publication using the Persian script

but

546

$a Sindhi $b Gurmukhi.

For a publication using the Gurmukhi script

546

$a Azerbaijani.

For a publication using the Latin script

but

546

$a Azerbaijani $b Arabic.

For a publication using the Arabic script

546

$a Azerbaijani $b Cyrillic.

For a publication using the Cyrillic script

546

$a Church Slavic.

For a publication using the Cyrillic script

but

546

$a Church Slavic $b Glagolitic.

For a publication using the Glagolitic script

For complex notes involving multiple languages and scripts, see Policy Statement 7.13.2.4

[2012-04]

LC-PCC PS for 7.13.2.4

Details of Scripts

LC practice/PCC practice: When recording complex notes involving multiple languages, record information about both the language and script in $a (Language note) of MARC field 546

(language and script in same subfield because $a is not repeatable).

EXAMPLE

546 ##

$a Kazakh, Uighur (Cyrillic), and Chagatai (Cyrillic and Arabic script).

EXAMPLE

546 ##

Sanskrit (Latin and Devanagari) and English.