Monday, June 3, 2013

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]


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

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

Posted by at
Links to this post
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

Posted by at
Links to this post
Labels: , , , , , ,

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

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

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

Posted by at
Links to this post
Labels: , , , , , ,

Thursday, May 23, 2013

Copy Cataloging in RDA documentation -- Library of Congress

Instructions for copycat in RDA>>

 

Copy Cataloging Using RDA



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

Posted by at
Links to this post
Labels: , , ,

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]

Posted by at
Links to this post
Labels: , ,

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

Posted by at
Links to this post
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):
Posted by at
Links to this post
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]


Posted by at
Links to this post
Labels: , , , , , ,

Wednesday, March 6, 2013

Illustrative Content

 
ILLUSTRATIVE CONTENT
  • LC CORE ELEMENT for resources intended for children
  • RDA 7.15
  • Open list of vocabulary terms
  • Recorded in MARC 008/18 as applicable and field 300 $b

This data is recorded in MARC 008/18 as applicable and field 300 $b

Sources: Take information on illustrative content from any source.

Recording Illustrative Content
If the resource contains illustrative content, record illustration or illustrations, as appropriate. Tables containing only words and/or numbers are not considered as illustrative content. Disregard illustrated title pages, etc., and minor illustrations.

Look below at LCPS 7.15.1.3 for the Alternative

“Generally do not record the type of illustrative content in place of or in addition to the term ‘illustration’ or ‘illustrations.’ ”

Optional Addition (7.15.1.3-Recording Illustrative Content)
Record the number of illustrations if their number can be ascertained readily (e.g., when the illustrations are listed and their numbers stated).
EXAMPLE
48 illustrations

<<<<-------->>>>
RDA VS AACR2 (Changes in treatment of illustrations in 300 field)
No abbreviations
“color” (not “col.”)
“sound” (not “sd.”)
“silent” (not “si.”)
“illustrations” (not “ill.”)
Color Content (Not LC Core) (RDA 7.17, LC-PCC PS-7.17.1.3)
Examples
color (illustrations are in color)
some color (10 maps, some of which are in color)
chiefly color (illustrations, most of which are in color)

Sources: Use evidence presented by the resource itself as the basis for recording the presence of color content in the resource. If desired, take additional evidence from any source.

Recording Colour Content
If the content of the resource is in colors other than black and white or shades of grey, record the presence of color using an appropriate term. Disregard colored matter outside the actual content of the resource (e.g., the border of a map).

LC practice: Use the spelling “color” when recording that term.

<<<<------>>>>
LC-PCC PS for 7.15 (RDA)
ILLUSTRATIVE CONTENT
CORE ELEMENT FOR LC
Illustrative content is a core element for LC for resources intended for children.
[2011-09]
LC-PCC PS for 7.15.1.3 (RDA)
ALTERNATIVE
LC practice for Alternative: Generally do not record the type of illustrative content in place of or in addition to the term "illustration" or "illustrations."
(Source: based on information in RDA Toolkit and LC RDA page information)

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

EXAMPLES

300 $b illustrations  [source: RDA RECORDS (JSC)]
300 $b illustrations (chiefly color)  [source: RDA RECORDS (JSC)]
300 $b color illustrations  [source: RDA RECORDS (JSC)]

Comment: includes photographs and other illustrations
300 $a ... : $b ill. ; $c ...
            comment:  if recording, do not abbreviate
_____  300 $a ... : $b illustrations ; $c ...
            comment:  acceptable but not required except for resources for children
LC       no 300 $b
_____  300 $a ... : $b illustrations, photographs ; $c ...
            comment:  acceptable but not required

Comment: includes charts, graphs, and other illustrations
_____  300 $a ... : $b illustrations ; $c ...
            comment:  acceptable but not required
_____  300 $a ... : $b ill. ; $c ...
            comment:  if recording, do not abbreviate
LC       no 300 $b
_____  300 $a ... : $b illustrations, graphs ; $c ...
            comment:  acceptable but not required

Answer from an expert from LC regarding illustrations (Note: LC policy): Under RDA only illustrations for resources intended for children is considered LC CORE in the bibliographic record. It is catalogers judgement to record the illustrations for other types of resources. So please use best judgement in providing this information if it is considered useful for users.

[Sources: RDA Toolkit, LC RDA training material, JSC RDA Records Examples, and transcript of communication from experts at LC]


See also:

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

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

Posted by at
Links to this post
Labels: , , , , , ,
Subscribe to: Posts (Atom)