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.

Friday, October 25, 2013

Library of Congress Subject Headings (LCSH) : Deities and mythological figures

ACQUISITIONS AND BIBLIOGRAPHIC ACCESS DIRECTORATE

POLICY AND STANDARDS DIVISION

SUMMARY OF DECISIONS, EDITORIAL MEETING NUMBER 8

August 19, 2013

SUBJECT HEADINGS

Announcements

Deities and mythological figures

Headings for individual deities and mythological figures (e.g., Thor, Hercules) should now be established in the name authority file using RDA instructions. The RDA heading will be valid for use as a subject heading.

Headings for groups of deities and mythological figures (e.g., Nymphs, the Furies) will continue to be established in LCSH because they cannot currently be established with RDA instructions. The heading God and headings of the type God (name of religion) (e.g., God (Christianity); God (Greek religion)) also continue to be established in LCSH.

The following workflows should be followed when inputting a name authority for an individual deity or mythological figure.

If the heading is needed for subject cataloging and an LCSH heading for the deity or mythological figure already exists, catalogers may continue to assign the existing LCSH heading. In that case, do not make a name authority record.

Optionally, catalogers may make a name authority for the deity or mythological figure if an LCSH heading already exists, but then must also make a proposal to cancel the existing LC subject heading. The proposal should be made through the Subject Proposal System; click the icon next to the heading and select the option “Propose cancelling this heading.”

If the heading is needed for a descriptive access point, it should be input into the name authority file. LCSH should be searched to determine whether the deity or mythological figure has already been established there. If so, a proposal to cancel the subject heading must also be made. The proposal should be made through the Subject Proposal System; click the icon next to the heading and select the option “Propose cancelling this heading.” NACO libraries who do not contribute SACO proposals may email policy@loc.gov to request that PSD make the cancellation proposal for them.

A project to transition all individual deity and mythological figure headings from LCSH to the name authority file will be conducted as resources are available. Catalogers are requested to refrain from unilaterally undertaking projects to convert the LC subject headings to name headings in a wholesale manner. Workload and staffing issues do not permit PSD to process the number of proposals that such projects would generate. SACO libraries wishing to undertake such a project may contact the Coop Section atsaco@loc.gov and the request will be considered.

The SHM will be revised to reflect the new procedures.

See also : LC PCC-PS FOR 9.0

[Blog Post Revised 2016-01-22]

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

http://id.loc.gov/authorities/subjects/sh85073290.html

Krishna (Hindu deity)

[old in Subject Authority File]

Krishna (Hindu deity)

Use Instead

URI(s)

http://id.loc.gov/authorities/subjects/sh85073290
info:lc/authorities/sh85073290
http://id.loc.gov/authorities/sh85073290#concept

Instance Of

Use Instead

Deletion Notes

This authority record has been deleted because the subject heading is covered by an identical name heading (DLC)no2015096049

Change Notes

1986-02-11: new

2015-10-28: deprecated

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

Krishna (Hindu deity)

[new in Name Authority File]

URI(s)

http://id.loc.gov/authorities/names/no2015096049

Instance Of

Scheme Membership(s)

Library of Congress Name Authority File

Collection Membership(s)

Variants

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

Variants

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

Additional Information

Descriptor
Descriptor
Birth Place
Gender

Use For

sh85073290

Exact Matching Concepts from Other Schemes

http://viaf.org/viaf/sourceID/LC%7Cno2015096049#skos:Concept

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̥ṣṇ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̥ṣṇ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----->>>>>

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

Conference Heading - Questions and Answers

Case: In a book title page reads like: Sustainable development in conflict environments: challenges and opportunities : proceedings of the international conference.

Question: Should we give seminar access in cases like this?

Question: Is there any concept of capitalization of seminar name in RDA?

Answer: Suggested treatment is given below:

111	2_ \|a Sustainable Development in Conflict Environments: Challenges and Opportunities (Conference) \|d (2007 : \|c Kathmandu, Nepal)

Regarding capitalization of named conferences, follow appendix A.2-->A10, etc. Basically they are the same rules as under AACR2.
It can also be set up as: Sustainable development in conflict environments: challenges and opportunities (Conference) … Note the absence of quotation marks, i.e. transcribe what you see.
Determination should be if the conference is "named" or not, can be done by applying RDA 8.1.2 and 8.1.3

Special Coded Dates - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
046		Special Coded Dates (R)
046	f	Birth date	9.3.2	Date of Birth
046	g	Death date	9.3.3	Date of Death
046	k	Beginning or single date created	6.4	Date of Work
046	k	Beginning or single date created	6.10	Date of Expression
046	l	Ending date created	6.4	Date of Work
046	l	Ending date created	6.10	Date of Expression
046	o	Single or starting date for aggregated content	6.4	Date of Work
046	p	Ending date for aggregated content	6.10	Date of Expression
046	s	Start period	9.3.4	Period of Activity of the Person
046	s	Start period	10.4	Date Associated with the Family
046	s	Start period	11.4.2	Date of Conference, etc.
046	s	Start period	11.4.3	Date of Establishment
046	t	End period	9.3.4	Period of Activity of the Person
046	t	End period	10.4	Date Associated with the Family
046	t	End period	11.4.2	Date of Conference, etc.
046	t	End period	11.4.4	Date of Termination
046	u	Uniform Resource Identifier	N/A
046	v	Source of information	N/A

[Source : RDA Toolkit]

See also in RDA Blog:

Thursday, October 24, 2013

Conference Heading - Questions and Answers

Case: In a book the name of seminar in introduction is given as national conference titled “Theorizing India’s Pre-Modern Visual Culture: Issues of Class, Caste, Gender and Sexualities” held at the Department of Art, History, and Aesthetics, M.S. University on February 13-15, 2003

Question: In cases like this what should be authorized access for seminar?

National Conference: “Theorizing India’s Pre-Modern Visual Culture: Issues of Class, Caste, Gender and Sexualities” (2003 : Department of Art, History, and Aesthetics, M.S. University)

“Theorizing India’s Pre-Modern Visual Culture: Issues of Class, Caste, Gender and Sexualities” (Conference) (2003 : Department of Art, History, and Aesthetics, M.S. University)

Answer: Suggested treatment is given below:

111	2_ \|a "Theorizing India’s Pre-modern Visual Culture : Issues of Class, Caste, Gender and Sexualities" (Conference) \|d (2003 : \|c Department of Art, History, and Aesthetics, M.S. University)

Note: The first determination should be if the conference is "named" or not, applying RDA 8.1.2 and 8.1.3. If yes, then "Theorizing India’s Pre-Modern Visual Culture: Issues of Class, Caste, Gender and Sexualities" (Conference) (2003 : Department of Art, History, and Aesthetics, M.S. University) would be appropriate.

If no, then "Theorizing India’s Pre-Modern Visual Culture: Issues of Class, Caste, Gender and Sexualities" would just be the theme of the conference.

775 - Other Edition Entry (R) - MARC 21 Bibliographic - Full

775 - Other Edition Entry (R)

FIELD DEFINITION AND SCOPE

Entry for another available edition of the target item (horizontal relationship). When a note is generated from this field, the introductory phrase Other editions available: may be generated based on the field tag for display.

The following types of editions are recorded in this field:

Language editions. When a serial is issued simultaneously in more than one language (usually by the same publisher, as opposed to a translation that is usually issued by another publisher).
Regular-print reprints. When the serial being cataloged is a regular-print reprint, field 775 is used for the original entry.
Other editions. Other editions of the target item. These will generally bear the same title as the target item but have edition information that distinguishes them.

■ EXAMPLES


130	0#$a Cuba economic news. $l Spanish.
245	10$a Cuba noticias económicas.
580	##$a Issued also in English: Cuba economic news.
775	1#$t Cuba economic news $x 0590-2932 $e eng $w(OCoLC)2259984
775	0#$t Cuba economic news $x 0590-2932 $eeng $w(OCoLC)2259984


130	0#$a Modern maturity (NRTA ed.)
245	00$a Modern maturity :$bpublication of the American Association of Retired Persons.
250	##$a NRTA ed.
775	1#$t Modern maturity $x 0026-8046 $w(DLC)###63047860# $w(OCoLC)1758471
775	0#$t Modern maturity $x0026-8046$w(DLC)###63047860# $w(OCoLC)1758471


245	00$a Communist.
260	##$a New York, $b Greenwood Reprint Corp., $c 1968.
580	##$a Reprint of a periodical published weekly in Chicago by the National Organization Committee of the Communist Party of America.
775	1# $t Communist $f ilu
775	0#$t Communist $f ilu


775	1#$t Modern maturity $b NRTA edition
775	0#$t Modern maturity $b NRTA edition


775	0#$t Hospital practice (Office ed.) $x 8750-2836

Saturday, October 19, 2013

International Standard Book Number (ISBN) - MARC to RDA Mapping

MARC 21 FIELD TAG	MARC 21 SUBFIELD CODE	MARC 21 FIELD / SUBFIELD NAME	RDA INSTRUCTION NUMBER	RDA ELEMENT NAME
020		International Standard Book Number
020	a	International Standard Book Number	2.15	Identifier for the Manifestation
020	c	Terms of availability	4.2	Terms of Availability
020	z	Cancelled/invalid ISBN	2.15	Identifier for the Manifestation

[Source : RDA Toolkit]

RDA Background

RDA: Resource Description and Access is the new standard for resource description and access designed for the digital world. Built on the foundations established by AACR2, RDA provides a comprehensive set of guidelines and instructions on resource description and access covering all types of content and media. Benefits of RDA include:

A structure based on the conceptual models of FRBR (functional requirements for bibliographic data) and FRAD (functional requirements for authority data) to help catalog users find the information they need more easily
A flexible framework for content description of digital resources that also serves the needs of libraries organizing traditional resources
A better fit with emerging database technologies, enabling institutions to introduce efficiencies in data capture and storage retrievals

RDA Background [RDA Toolkit]

Friday, October 11, 2013

Date of Publication Not Identified in a Single-Part Resource

For Date of Publication Not Identified in a Single-Part Resource RDA Rule 2.8.6.6 says that If the date of publication is not identified in a single-part resource, supply the date or approximate date of publication.

EXAMPLE

[1998?]

If an approximate date of publication for a single-part resource cannot reasonably be determined, record date of publication not identified. Indicate that the information was taken from a source outside the resource itself.

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

LC-PCC PS for 2.8.6.6 DATE OF PUBLICATION NOT IDENTIFIED IN THE RESOURCE (very useful with many examples)

[Source: RDA Toolkit]

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

008	130424q20072013ii

264	_1 \|a Jayapura : \|b Navajīvana Pablikeśana, \|c [between 2007 and 2013?]

[Source: Library of Congress Catalog]

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

q-Questionable date. A range of years is the only date that can be specified (e.g., between 1824 and 1840). Give the earliest year in Date 1 and latest in Date 2.

DtSt:			q
Dates:			1966,1967
[1966 or 1967]

DtSt:			q
Dates:			1965,1969
[Between 1965 and 1969]

DtSt:			q
Dates:			18uu,19uu
260			Amsterdam : ‡b Elsevier, ‡c [19th century and early 20th century]
[Decade is missing for both earliest and latest date.]

DtSt:			q
Dates:			1963,1966
260			New York : ‡b Hippocrene Books, ‡c [between 1963 and 1966]

DtSt:			q
Dates:			1983,1984
260			Yerushalayim : ‡b E. Fisher, ‡c 744 [1983 or 1984]

[Source: RDA Toolkit and OCLC]

Incomplete Resource

RDA Rule 3.4.1.10 for Incomplete Resource record the term indicating the type of unit without the number. This has to be applied also for a resource when the total number of units issued is unknown.

300 $a volumes
300 $a volumes (loose-leaf)

LC-PCC PS for 3.4.1.10 - INCOMPLETE RESOURCE

Incomplete Multipart Monographs

LC practice: Do not give LC’s local holdings for incomplete multipart monographs in MARC field 300

; ensure that there are item records for each part or unit.

PCC practice: Do not give local holdings for multipart monographs in MARC field 300

Updating Loose-leafs

LC practice/PCC practice: If the updating loose-leaf includes transfer volumes, describe the extent in terms of "loose-leaf" and "transfer."

EXAMPLE

300

$a volumes (loose-leaf), volume (transfer)

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

NOTE: ABOVE PRACTICES ARE "CHANGES FROM AACR2 TO RDA"

[Source: RDA Toolkit]

EXAMPLE OF MARC FIELDS 372, 374 AND QUALIFIER TO 100

LC control no.:	n 2012217915
LCCN permalink:	http://lccn.loc.gov/n2012217915
HEADING:	Singh, Preeti (Researcher in Women’s Studies)
000	00874cz a2200193n 450
001	9305885
005	20130722235808.0
008	130708n\| azannaabn \|a aaa
010	__ \|a n 2012217915
040	__ \|a DLC \|b eng \|e rda \|c DLC \|d DLC
100	1_ \|a Singh, Preeti \|c (Researcher in Women’s Studies)
370	__ \|e Vārānasi, Uttar Pradesh, India
372	__ \|a Women’s studies
373	__ \|a Banaras Hindu University. Centre for Women’s Studies and Development \|2 naf
374	__ \|a Researcher
375	__ \|a female
377	__ \|a eng
400	0_ \|a Preeti Singh \|c (Researcher in Women’s Studies)
670	__ \|a Concept of stridhana in ancient Hindu Law, 2007: \|b title page (Preeti Singh) page 4 of cover (project fellow in the Centre for Women’s Studies and Development, Banaras Hindu University; presently doing Ph.D. on Women’s rights from the Department of Political Science, Banaras Hindu University)