Establishing Certain Entities in the Name or Subject Authority File : RDA Cataloging

-
Subject Headings Manual — Name vs. Subject Authority File — H 405 Establishing Certain Entities in the Name or Subject Authority (Revised)

1. General rule. Whenever a new heading is needed for a named entity, consult the two lists on pp. 5-13 to determine whether the heading is categorized as a Group 1 or Group 2 heading. Follow the procedures appropriate to the group. If neither the precise category, nor a broader category that encompasses the precise category, nor a very closely analogous category is found in either of the two groups, bring the matter to the attention of the Policy and Standards Division (PSD) for an interpretation and possible addition of the category to one of the lists. 
GROUP ONE - NAME AUTHORITY GROUP HEADINGS: Named entities always established according to descriptive cataloging conventions with authority records that always reside in the name authority file.

GROUP TWO - SUBJECT AUTHORITY GROUP HEADINGS: Named entities always established according to subject cataloging conventions with authority records that reside in either the name authority file or the subject authority file.

2.  Group one headings.  First search to determine whether the required heading has already been established as an RDA name heading.  If so, use the heading as established.  If not, establish it as a name heading or request a descriptive cataloger to do so.

If a heading in this category has been established as a subject heading, submit a proposal to delete the subject authority record according to the procedures in H 193 after it has been established it as a name heading.

3.  Group two headings.

a.  Heading required for subject cataloging purposes.  First search to determine whether the entity has already been established as a name heading according to former guidelines.  After making this determination, proceed as follows:
(1) Name authority record not found.  Submit a proposal to establish the entity as a subject heading, following the standard procedures described in H 200, as well as any special procedures described in individual instruction sheets appropriate to particular categories of named entities, for example, H 1334 for buildings and structures, H 1925 for parks, etc. 
Proposals of this type appear in the main alphabetical section of the tentative list and are treated as subject headings.
(2) RDA or AACR2 name authority record found.  If the record does not have a 667 field with the notation Subj Headings Manual/RDA, consult the Policy and Standards Division to determine whether it should be canceled as a name heading and re-established as a subject heading.
(3) Pre-AACR2 name authority record found.  Submit a proposal to establish it as a subject heading, as described in sec. 1.a., above.  Notify the Policy and Standards Division of the invalid name heading so that the name authority record can be deleted.
b.  Heading needed for use as descriptive access point.  Follow the guidelines in the Descriptive Cataloging Manual, Z1, Appendix 1: Ambiguous Entities, sec. 1.2.(e) and sec. 3.1.


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


GROUP ONE - NAME AUTHORITY GROUP HEADINGS: REVISED CATEGORIES OF HEADINGS
  • Cemeteries
  • City sections
  • Comic strips
  • Computer programs and software
  • Events
  • Expeditions, Military
  • Fictitious characters (Individual)
  • Forests (Administrative agencies)
  • Gods (Individual)
  • Legendary characters (Individual)
  • Mythological figures (Individual)
  • Parks (Administrative agencies)
  • Research parks
  • Reserves (Administrative agencies)
  • Software, Computer     


GROUP TWO - SUBJECT AUTHORITY GROUP HEADINGS: REVISED CATEGORIES OF HEADINGS
  • Artists' groups
  • Building details
  • Buildings occupied by corporate bodies 
  • Cemetery sites, Archaeological
  • Composers' groups
  • Events 
  • Expeditions, Military 
  • Fictitious characters (Groups)
  • Forests (Geographic entities)
  • Gods (Groups)
  • Legendary characters (Groups)
  • Mythological figures (Groups)
  • Parks (Geographic entities)

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


Example of a recently revised heading: 

LC control no.: no2014087168
LCCN permalink: http://lccn.loc.gov/no2014087168
HEADING: Vairocana (Buddhist deity)
000 02107cz a2200397n 450
001 9590696
005 20140919155235.0
008 140626n| azannaabn |b aaa c
010 __ |a no2014087168 |z sh2008000264
035 __ |a (OCoLC)oca09893442
040 __ |a NNC-EA |b eng |e rda |c NNC |d DLC |d NNC |d DLC
100 0_ |a Vairocana |c (Buddhist deity)
368 __ |c Buddhist gods |2 lcsh
400 0_ |a Mahavairochana |c (Buddhist deity)
400 0_ |a Vairochana |c (Buddhist deity)
                          ... ... ... ... ... ... ... 
                          ... ... ... ... ... ... ... 
 


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



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




Krishna (Hindu deity) 

[old in Subject Authority File]



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

us:  Krishna (Hindu deity) 

[new in Name Authority File]





  • URI(s)

  • Instance Of

  • Scheme Membership(s)

  • Collection Membership(s)

  • Variants

    • us:  Christna (Hindu deity)
    • us:  Gopal (Hindu deity)
    • us:  Kr̥ṣṇa (Hindu deity)
    • us:  Govinda (Hindu deity)
    • us:  Mohan (Hindu deity)
    • us:  Gopala (Hindu deity)
    • us:  Bal Gopal (Hindu deity)

  • Variants

    • us:  Christna (Hindu deity)
    • us:  Gopal (Hindu deity)
    • us:  Kr̥ṣṇa (Hindu deity)
    • us:  Govinda (Hindu deity)
    • us:  Mohan (Hindu deity)
    • us:  Gopala (Hindu deity)
    • us:  Bal Gopal (Hindu deity)

  • Additional Information

    • Descriptor

        Hindu deity

    • Descriptor

        (lcsh) Hindu gods

    • Birth Place

        (naf) India

    • Gender

        male

  • Use For

  • Exact Matching Concepts from Other Schemes

  • Sources

    • found: Reyes, E. Christopher. In His name, 2010: p. 307 (Christna, earlier English spelling of Krishna, who came upon earth to redeem man by his sufferings; Jesus and Krishna parallels)
    • found: Wikipedia, viewed November 12, 2014 (Krishna, also called Kr̥ṣṇa, Govinda, Mohan, and Gopala, is a deity, worshipped across many traditions of Hinduism. Many Vaishnava groups recognize him as an avatar of the god, Vishnu; however, some traditions within Krishnaism, consider Krishna to be svayam bhagavan, or the Supreme Being. Bhagavad gita and many other puranas considers that Krishna is source of all the vedas. Krishna belonged to the Vrishni clan of Yadavas from Mathura, and was the eighth son born to the princess Devaki, and her husband Vasudeva; Gopal; the child form of Krishna, also known as Bal Gopal)

  • Change Notes

    • 2015-07-22: new
    • 2015-11-06: revised
<<<<<---------->>>>>

Record in OCLC Connexion

010  no2015096049 ǂz sh 85073290 
040  CU-SB ǂb eng ǂe rda ǂc CU-SB ǂd MnSST ǂd DLC
1000 Krishna ǂc (Hindu deity)
368  ǂc Hindu deity
368  ǂc Hindu gods ǂ2 lcsh
370  India ǂ2 naf
375  male
4000 Christna ǂc (Hindu deity)
4000 Gopal ǂc (Hindu deity)
4000 Kr̥ṣṇa ǂc (Hindu deity)
4000 Govinda ǂc (Hindu deity)
4000 Mohan ǂc (Hindu deity)
4000 Gopala ǂc (Hindu deity)
4000 Bal Gopal ǂc (Hindu deity)
670  Reyes, E. Christopher. In His name, 2010: ǂb p. 307 (Christna, earlier English spelling of Krishna, who came upon earth to redeem man by his sufferings; Jesus and Krishna parallels)
670  Wikipedia, viewed November 12, 2014 ǂb (Krishna, also called Kr̥ṣṇa, Govinda, Mohan, and Gopala, is a deity, worshipped across many traditions of Hinduism. Many Vaishnava groups recognize him as an avatar of the god, Vishnu; however, some traditions within Krishnaism, consider Krishna to be svayam bhagavan, or the Supreme Being. Bhagavad gita and many other puranas considers that Krishna is source of all the vedas. Krishna belonged to the Vrishni clan of Yadavas from Mathura, and was the eighth son born to the princess Devaki, and her husband Vasudeva; Gopal; the child form of Krishna, also known as Bal Gopal)


<<<<<-----Revised on 2015-01-22----->>>>>


Comments

Post a Comment

RDA Blog is DISCONTINUED

RDA Blog is discontinued. Visit below link for updated information on RDA:

Resource Description and Access (RDA)


Popular posts from this blog

Date of Publication Distribution Copyright in RDA & MARC 21 Field 264 Examples

-
Image
Date of Publication, Distribution, and Copyright in Resource Description and Access (RDA) Cataloging Rules  & MARC 264 Examples Table of Contents: Core Element How Date of Publication is defined Where the Rules are for Date of Publication in RDA What are the Sources of Information for Date of Publication in RDA How is Date of Publication Transcribed / Recorded in Resource Description and Access (RDA) Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram RDA Examples What to do if the date on the resource is incorrect Multipart Monographs, Serials, and Integrating Resources Date of Publication not Identified in a Single-Part Resource RDA Cataloging Examples of Dates Supplying Dates (Date of Publication Not Identified in the Resource) Importance of Supplying Probable Place and Date of Publication Examples of Supplying Publication Data Other RDA Examples of Dates Date of Distribution Where the Rules are for Date of Distribution in RDA
Read more

Place of Publication in RDA & AACR2 & MARC 21 Examples

-
Image
Place of Publication in Resource Description and Access ( RDA ) & Anglo-American Cataloging Rules ( AACR2 ) with MARC 21 Examples Table of Contents: CORE ELEMENT How is Place of Publication defined Where are Rules for Place of Publication in RDA What are the Sources of Information for Place of Publication in RDA How is Place of Publication Transcribed / Recorded in Resource Description and Access (RDA) More than One Place of Publication Language or Script Place of Publication Not Identified CORE ELEMENT: Place of Publication is a core element; if more than one place of publication appears on the source of information, only the first recorded is required. How is Place of Publication defined:  According to the  Glossary of Library and Information Science  of  Librarianship Studies and Information Technology  blog, the  place of publication  is the place associated with the publication, release, or issuing of a resource or document. There are the special se
Read more

RDA -- INTRODUCTION BACKGROUND AND HISTORY

-
Resource Description and Access ( RDA ) is a standard for cataloguing that provides instructions and guidelines on formulating data for resource description and discovery. Intended for use by libraries and other cultural organizations such as museums and archives, RDA is the successor to the Anglo-American Cataloguing Rules, Second Edition (AACR2), the current cataloging standard set for English language libraries. RDA was initially released in June 2010. In March 2012, the Library of Congress announced it will have fully implemented RDA cataloging by March 31, 2013. Several other national libraries including the British Library, Library and Archives Canada, National Library of Australia, and Deutsche Nationalbibliothek also planned to implement RDA in 2013. Background RDA emerged from the International Conference on the Principles & Future Development of AACR held in Toronto in 1997. It was quickly realised that substantial revision of AACR2 was required, which
Read more