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

RDA Relationship Designators Example
Click on image to enlarge

RDA Relationship Designators Example
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 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):

Thursday, May 23, 2013

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



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.
[2012-04]

[Source: RDA Toolkit]