Parallel Titles in RDA, AACR2 Cataloging & MARC21

Parallel Titles in RDA, AACR2 Cataloging & MARC21

• Questions and Answers on treatment Parallel Titles in RDA, AACR2 and MARC21 in Google+ Community RDA Cataloging

• Join the Google+ Community RDA Cataloging to view, ask, and share information and issues related to Resource Description & Access (RDA) and AACR2 Cataloging

See also following Resource Description & Access (RDA) Blog posts:

• Parallel title in RDA Cataloging
• MARC21 246 tag in RDA Cataloging
• MARC21 245 tag in RDA Cataloging

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

• Comment on  Google+ Community RDA Cataloging

Aaron Kuperman

Yesterday 10:55 PM

+

1
0
1

 

 

At LC, and this is very important for records of works in non-Roman scripts, if there is a parallel title (typically in English or another Latin script langauge) anywhere in the item being cataloged, it ends up both as a parallel title (245, following an "="), and usually as a 246 , often with a $i indicating where the parallel title came from, such as the verso t.p., added title page, the collophon, or whereever.  In the past the 246 would have sufficient if the Roman script title was not on the title page.

Correct Coding of ISBN in MARC21 field 020 in RDA & AACR2 Cataloging with Examples

Several years ago the definition of $z of the 020 (International Standard Book Identifier) was expanded—it is now used for “structurally invalid” ISBNs (those that are too short, too long, wrong check digit, etc.) and also for “application invalid” ISBNs (ISBNs for a manifestation that would be described in a different bibliographic record).

The LC-PCC Policy Statement for 2.15.1.7 provides the following instruction:  

Record ISBNs in $z (Canceled/invalid) of MARC field 020 if they clearly represent a different manifestation from the resource being cataloged and would require a separate record (e.g., an ISBN for the large print version, e-book, or teacher’s manual on the record for a regular trade publication). If separate records would not be made (e.g., most cases where ISBNs are given for both the hardback and paperback simultaneously), or in cases of doubt, record the ISBNs in $a (International Standard Book Number) of MARC field 020

Please remember to use $z for ISBNs when appropriate. For regular print publications, this is most likely to occur when you also have an ISBN for a large print edition or e-book that would be cataloged on a separate record.

When we do not use the correct subfield code in field 020, systems that receive records from LC may incorrectly merge or replace records for the wrong format—we have received several complaints about this, and we hope we can improve the situation with your help.

[Source: Dave Reser, Library of Congress, Policy and Standards Division] 

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

Question: Record ISBNs in 020 $z if they represent a different manifestation from the resource being cataloged.

• If a printed monograph presents different ISBNs for different manifestation, do we have to transcribe them like below given example?

AACR2            020 $a 9780415692847 (hardback: alk. paper)

                                        020 $a 9780203116852 (e-book)

RDA                020 $a 9780415692847 (hardback: alk. paper)

                                      020 $z 9780203116852 (e-book)   (recorded in $z ISBN clearly representing an e-book version of the same manifestation)

Answer: Yes, the example you have given shows LC’s practice documented in LC PCC PS 2.15.1.7 for multiple ISBN:

“…if they clearly represent a different manifestation from the resource being cataloged and would require a separate record (e.g., an ISBN for the large print version, e-book, or teacher’s manual on the record for a regular trade publication). If separate records would not be made (e.g., most cases where ISBNs are given for both the hardback and paperback simultaneously), or in cases of doubt, record the ISBNs in $a”

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

See Also: RDA Blog Labels (Categories) in below links for posts on related information on treatment of ISBN in RDA.

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

David Bigwood

12 hours ago  -  Shared publicly

While not part of the question and answer it would be nice to show subfield q being used. 

RDA                020 $a 9780415692847 $q (hardback: alk. paper)

                                      020 $z 9780203116852 $q (e-book) 

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

Sasha Birman

Yesterday 4:29 PM

+

1
0
1

 

Reply

We use both fields, 440 is former series field. 490 is very current.

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

Sasha Birman

Yesterday 4:29 PM

We use both fields, 440 is former series field. 490 is very current.

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

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

RDA Cataloging Example of Selections & Translations

CASE: Selected plays of a Panjabi language author translated into Hindi language.

Bibliographic Record

The Hindi title when translated into English would read: "Representative plays"

Authority Record

LC control no.:	n 2012217312
LCCN permalink:	http://lccn.loc.gov/n2012217312
HEADING:	Gurasharana Siṅgha, 1929-2011. Plays. Selections. Hindi
000	00528cz a2200133n 450
001	9272751
005	20130618010111.0
008	130524n| azannaabn |a aaa
010	__ |a n 2012217312
040	__ |a DLC |b eng |c DLC |e rda
100	0_ |a Gurasharana Siṅgha, |d 1929-2011. |t Plays. |k Selections. |l Hindi
400	0_ |a Gurasharana Siṅgha, |d 1929-2011. |t Pratinidhi nāṭaka
400	0_ |a Gurasharana Siṅgha, |d 1929-2011. |t Pratinidhi natak
670	__ |a Pratinidhi nāṭaka, 2012: |b title page (Pratinidhi nāṭaka) title page verso (Pratinidhi natak)

[Source: Library of Congress]

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

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)

                          ... ... ... ... ... ... ... 

                          ... ... ... ... ... ... ... 

Source: Subject Headings Manual — Name vs. Subject Authority File — H 405 Establishing Certain Entities in the Name or Subject Authority ; http://lccn.loc.gov/no2014087168 

 

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

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

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

Krishna (Hindu deity) 

[old in Subject Authority File]

 Krishna (Hindu deity)

Use Instead

•  This authority record has been deleted because the subject heading is covered by an identical name heading
• http://id.loc.gov/authorities/names/no2015096049

• URI(s)

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

• Instance Of

  • MADS/RDF Topic
  • MADS/RDF Variant
  • SKOSXL Label 
  • MADS/RDF DeprecatedAuthority

• Use Instead

  •  This authority record has been deleted because the subject heading is covered by an identical name heading
  • http://id.loc.gov/authorities/names/no2015096049

• 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

  • MADS/RDF PersonalName
  • MADS/RDF Authority
  • SKOS Concept 

• Scheme Membership(s)

  • Library of Congress Name Authority File

• Collection Membership(s)

  • Names Collection - Authorized Headings
  • LC Names Collection - General Collection

• 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

    Hindu deity

  • Descriptor

    (lcsh) Hindu gods

  • Birth Place

    (naf) India

  • Gender

    male

• 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̥ṣṇ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----->>>>>

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

Question on RDA Relationships asked at Google+ Community "RDA Cataloging"

Question on Relationships in Resource Description & Access on Google+ Community RDA Cataloging - Answers from Experts at RDA-L

CATALOGUING A REVIEW:

I face a difficulty when recording a work relationship for a work which is a review of a critical edition of another work.

Ideally, I would like to be able to connect between a work (the review) and the expression of another work (the critical edition).

Here is an example:

WORK A: Baalbaki, Ramzi, born 1951. [Review of] Harun's edition of Sibawayhi's Kitab (2010)

WORK B: Sībawayh, died 796?. Al-Kitāb (ca. 780)

EXPRESSION B1: Sībawayh, died 796?. Al-Kitāb (ca. 780). (Critical edition by H. Derenbourg, 1881‒1885). Text. Arabic

EXPRESSION B2: Sībawayh, died 796?. Al-Kitāb (ca. 780). (Critical edition by A. S. Hārūn, 1966‒1977 ). Text. Arabic

WORK A1 is a review of EXPRESSION B2.

What do you suggest I should do? It seems that the relationship designators (here, "review of") apply either between two works or between two expressions but not between a work and the expression of another work.

But here, WORK A itself, not one of its expressions, is a review of EXPRESSION B2. How should I record this relationship?

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

Response by Heidrun Wiesenmüller, Professor of library science at the Stuttgart Media University (Germany)

Salman,

I have no easy solution, but I agree there is an oddity here.

RDA indeed seems to restrict relationships to work-work and expression-expression, with no "cross-overs". Whereas this may be o.k. for other types of relationships, it doesn't fit descriptive relationships of the type you mentioned.

You're quite right to think that the review of a certain edition is a work in its own right. Of course, the review work has at least one expression of its own. But it would be weird to record the relationship only between one expression of the review work and the reviewed edition. This would miss the point that *all* expressions of the review work describe the reviewed edition. So the relationship should indeed be recorded between a work (the review) and an expression of another work.

It's interesting to compare the situation on expression level to the descriptive relationships on the level of manifestation and item (J.4.4 and J.5.2):
- description of (manifestation) A manifestation described by a describing work.
- description of (item) An item described by a describing work.

So in these cases, RDA allows to record a relationship between a describing work and a manifestation, and a describing work and an item. It seems to me that the same should be possible for a relationship between a describing work and an expression. So perhaps J.3.3 needs to be changed according to the pattern of J.4.4 and J.5.2 (I assume a proposal would be needed for this).

By the way, one might argue that these "descriptive relationships" between group 1 entities are really subject relationships, and shouldn't be here at all. They do stand out rather.

Heidrun

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

Response by Gordon Dunsire, Chair, Joint Steering Committee for Development of RDA

Salman, Heidrun and others

These issues are addressed in a submission from the JSC Technical Working Group to the JSC for its November 2014 meeting:

6JSC/TechnicalWG/3  High-level subject relationship in RDA (http://www.rda-jsc.org/docs/6JSC-TechnicalWG-3.pdf)

Cheers

Gordon

Gordon Dunsire
Chair, Joint Steering Committee for Development of RDA

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

Response by Heidrun Wiesenmüller, Professor of library science at the Stuttgart Media University (Germany)

Thanks, Gordon, that's great.
I haven't worked my way through all the documents yet, so had missed the fact that the proposal is already there :-)

Do I understand correctly that the descriptive relationship designators (with the proposed revisions and additions) would stay in Appendix J, i.e. still belong to section 8 (Relationships between works, expressions, manifestations, and items). So there is no plan to move them to section 7 (subject relationships)?

Heidrun

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

Response by Gordon Dunsire, Chair, Joint Steering Committee for Development of RDA

Heidrun

The JSC will discuss any improvements to RDA Toolkit associated with the Technical Working Group's recommendations in due course. There are no current plans to move the designators - but I think there are other submissions affecting relationship designators (I haven't had time myself to read all of the submissions).

Cheers

Gordon

Gordon Dunsire
Chair, Joint Steering Committee for Development of RDA

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

Response by Robert L. Maxwell, Ancient Languages and Special Collections Cataloger, Harold B. Lee Library, Brigham Young University

I would do:

Review of (expression): Sībawayh, ʻAmr ibn ʻUthmān, active 8th century. Kitāb. Arabic (Hārūn)

It should also be possible to use this access point in a subject field.

RDA doesn’t explicitly recognize a relationship between a work and an expression, but they happen all the time. In my opinion we should be able to record relationships between any FRBR entity and any other FRBR entity, as appropriate.

Bob

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

RDA Blog Thanks Heidrun Wiesenmüller, Gordon Dunsire, and Robert L. Maxwell for their valuabe remarks

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