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, October 28, 2013

MARC Code List for Relators

RDA RELATIONSHIP DESIGNATORS

MARC Code List for Relators [Also Valid as Relationship Designator in Resource Description and Access (RDA) Cataloging]

Relator terms and their associated codes designate the relationship between a name and a bibliographic resource. The relator codes are three-character lowercase alphabetic strings that serve as identifiers. Either the term or the code may be used as controlled values.

URI(s)

http://id.loc.gov/vocabulary/relators

Instance Of

Top Scheme Members

Source URI(s)

http://id.loc.gov/vocabulary/relators

See also: MARC and RDA Relators Reconciled

Note: Above search form is from LC Linked Data Service.

Saturday, October 26, 2013

September Update for RDA Catalogers

Dear RDA catalogers,

This message is to alert you to some information about RDA on these topics:

Topic 1. Interim treatment of "Treaties" under RDA

Topic 2. Reminder on formulating the preferred name and authorized access point for some types of conferences

Topic 3. A typo in an RDA example that has the potential to confuse

Topic 1: Interim treatment of "Treaties" under RDA. Based on a request from the American Association of Law Libraries, the Program for Cooperative Cataloging (PCC) has approved an interim exception to the treatment of authorized access points for treaties under RDA. The legal community is re-evaluating how authorized access points for treaties should be constructed under RDA, and has proposed some major changes to RDA that will be discussed by the Joint Steering Committee at its November meeting. To avoid disruption within the existing NACO file and related bibliographic maintenance until RDA itself is changed, the following guidelines for new and existing authorized access points should be observed until a final solution has been determined:

New authorized access points for treaties: If no authorized access point exists for a treaty, continue to use AACR2 instructions (AACR2 25.16 Treaties, etc., and 21.35 Treaties, Intergovernmental agreements, etc.) to establish the authorized form, except, use the full form of the name of a month when necessary to record a date a treaty was signed instead of the abbreviations from AACR2. Code any new authority record as AACR2 in 008/10 (Descriptive Cataloging Rules) as an exception to the PCC Post RDA Test Guidelines.

Existing authorized access points for treaties (AACR2): Do not revise an existing AACR2 authorized access point in a name authority record for a treaty to the RDA form, continue to use the AACR2 form in RDA bibliographic records.

Existing authorized access points for treaties (RDA): Do not revise an existing RDA authorized access point in a name authority record for a treaty back to AACR2, continue to use the RDA form in bibliographic records.

These exceptions for treaties are also found in the PCC Post RDA Test Guidelines at

http://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html under the heading Exception for Treaties. LC-PCC PSs will also be issued until such time that RDA itself is changed.

Topic 2: Reminder on formulating the preferred name and authorized access points for conferences.

A reminder that under RDA, a date that might appear with the name of a conference that is an initialsm or acronym is *not* included as part of the preferred name for the conference- the date is only used as an addition to the authorized access point for the conference ($d in the X11). From RDA 11.2.2.11: "Omit from the name of a conference, etc., indications of its number, or year or years of convocation, etc. Apply this instruction to the name of a congress, meeting, exhibition, fair, festival, etc. …"

This was a change from how we treated such conferences under the LCRIs for AACR2.

Examples:

Under AACR2/LCRI: CDVE 2011 $d (2011 : $c Hong Kong, China)

Treatment under RDA: CDVE (Conference) $n (8th : $d 2011 : $c Hong Kong, China)

Under AACR2/LCRI: ICT-GLOW 2011 $d (2011 : $c Toulouse, France)

Treatment under RDA: ICT-GLOW (Conference) $n (1st : $d 2011 : $c Toulouse, France)

(Note that under RDA/LC-PCC PS policies, it is now possible to create separate authorities coexisting in the LC/NACO authority file for the "collective" ongoing conference and for individual instances of it, which was not permitted under AACR2/LCRI. Note also that the term "(Conference)" or similar term is added to preferred name for a conference that is an initialism or acronym in order to convey the idea of a corporate body per LC-PCC PS 11.7.1.4 )

Topic 3. A typo in RDA example that has the potential to confuse

Several have noted an unfortunate editing mistake in an example at RDA 9.19.1.6 showing an authorized access point using the new RDA element "Other term of rank, honour or office"-- it will be corrected in the next release (November) of the RDA Toolkit

Wood, Captain, John

should be

Wood, John, Captain

Please don't follow this example!

[Source: Library of Congress]

Associated Institution (Revision of RDA Rule 11.5.1.3 with Question and Answer)

Questions and Answers

Question: This recently revised instruction by which we now are to record the preferred name of the corporate body: what if the NAR for the body has not been set up yet? Must we create the NAR in order to add a 373? Or can we simply record the form as found on the resource?

or this question can be framed as below:

Question: Basically it's the form of the body given in the 373. I understand that it's supposed to be the preferred name (cf. 9.13.1.3). If the body hasn't been set up, do we have to do so, in order to use its preferred form?

Answer: No we do not have to set it up. (same as 370)

According to RDA Rule 11.5.1.3 for Recording Associated Institutions you have to Record the name of an associated institution by using the preferred name for the institution

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