Saturday, September 6, 2014

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

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)


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.



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 (



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



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

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



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.



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

Monday, September 1, 2014

Sources of Information in Resource Description and Access (RDA)


The AACR2 concept of “chief source” has been replaced by the RDA concept of “preferred sources.” This is not only a change of term but also reflects RDA’s expansion from a single source to multiple sources for information. The preferred source of information is still the source where you find the title proper. For most elements, RDA gives you permission to take information from any source, with the choices given in a priority order.

If data is taken from outside the resource, it is enclosed in square brackets. For some elements, the data can come from “any source”; consult the ‘sources’ instruction for each element, or 2.2.4. 
  • Exception: when cataloging a resource that doesn’t typically have bibliographic information on the resource (e.g., photograph, sculpture), you do not need the square brackets. 
The sources given in the AACR2 part I chapters have been condensed into three categories: 
     A. Resources with pages, leaves, etc., or images of pages (
     B. Moving images (
     C.All other resources (

A. Resources with Pages, Leaves, etc., or Images of Pages
RDA provides a priority order for the preferred sources for these materials:
  • Title page, title sheet, etc. (or image) 
  • Cover (or image) 
  • Caption (or image) 
  • Masthead (or image) 
  • Colophon (or image) 
If you have exhausted those sources, you can use the source where the title is located.

If your resource doesn’t have a title page, use a source where the information may be formally presented (e.g., perhaps introductory pages). But these are still within the resource.

  • There is an alternative for microform or digital resources, which says to use an eye-readable label. There is also an exception for early-printed resources, with a different priority order. 
Resources Issued in More Than One Part
RDA provides the instructions for resources issued in multiple parts. This includes serials, multipart monographs, integrating resources, and kits. 
  • If the parts are sequentially numbered, use the lowest-numbered issue or part available 
  • If the parts are unnumbered or not sequentially numbered, use the issue or part with the earliest date of issue 
  • If the concept of sequential numbering is not appropriate (e.g., for a kit), use the resource as a whole; if this is not possible, generally determine the main part 

B. Moving-Image Resources
Moving images are typically contained in carriers such as film, DVD, etc. For these, the source is generally where the title appears.

RDA provides a priority order for the preferred sources for these materials: 
  • Title frames or title screens 
  • Label that is permanently printed on or affixed to the resource, excluding accompanying textual material or a container 
  • embedded metadata in textual form containing a title 
When none of the listed sources apply, use a source where the information is formally presented. 
  • There is an alternative to use a label and skip the title frames so you don’t have to project the image to find the data. 

C. Other Resources
RDA provides a priority order for the preferred sources for resources other than those in the first two categories
  • Label 
  • Embedded metadata in textual form containing a title 
  • If neither of the above is appropriate, use a source where the data is formally presented 

Other Sources of Information
RDA 2.2.4 provides a priority order for the other sources when you can’t find a title from the resource itself: 
  • Accompanying materials 
  • Container not issued as part of the resource (e.g., a case made by the owner) 
  • Other published descriptions of the resource 
  • Any other source (e.g., a reference source that indicates how the resource is commonly known) 

[Source: Library of Congress]

Sunday, August 24, 2014

Temporary / Permanent Date in an Incomplete Multipart Monograph : Questions and Answers in the Google+ Community "RDA Cataloging"

RDA Cataloging is an online community/group/forum for library and information science students, professionals and cataloging & metadata librarians. It is a place where people can get together to share ideas, trade tips and tricks, share resources, get the latest news, and learn about Resource Description and Access (RDA), a new cataloging standard to replace AACR2, and other issues related to cataloging and metadata.

 Questions and Answers in the Google+ Community "RDA Cataloging"


Publication etc., dates (MARC21 264). These conventions do not apply to serials or integrating resources (temporary data not recorded in this field).

Temporary date. If a portion of a date is temporary, enclose the portion in angle brackets.


, 1980-〈1981〉 
v. 1-2 held; v. 2 published in 1981

, 〈1981-〉 
v. 2 held; v. 1-2 published in 1981

, 〈1979〉-1981. 
v. 2-3 held of a 3-volume set

, 〈1978-1980〉 
v. 2-3 held of a 5-volume set

Permanent date. If an entire date is judged to be permanent, record it without angle brackets.


, 1980-
〈1980-〉 or, 1980-〈 〉 
v. 1 held; v. 1 published in 1980

[Source: LC-PCC PS for RDA Rule 1.7.1]

Friday, August 1, 2014

Relationship Designators in Resource Description and Access (RDA) : honouree, host institution, organizer, sponsoring body

RELATIONSHIP DESIGNATORAPPENDIX I.2.2 : Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work
honoureeUse this relationship designator with a person, family, or corporate body honoured by a work (e.g., the honouree of a festschrift or a commemorative volume) (MARC21 tag 700, 710, subfield e)
host institutionUse this relationship designator with a corporate body hosting the event, exhibit, conference, etc., which gave rise to a work, but having little or no responsibility for the content of the work (MARC21 tag 710, subfield e)
organizerUse this relationship designator with a person, family, or corporate body organizing the exhibit, event, conference, etc., which gave rise to a work (MARC21 tag 700, 710, subfield e)
sponsoring bodyUse this relationship designator with a person, family, or corporate body sponsoring some aspect of a work, e.g., funding research, sponsoring an event (MARC21 tag 700, 710, subfield e)

[Questions asked on the use and scope of some RDA Relationship designators, see RDA Toolkit Appendix I for more]

Aaron Kuperman I have found the "honouree" (not just for festscrifts) to be very useful. If they publish someone's essay to honor him, it get a double $e (author, honouree). --- The "Sponsoring party" is good for a law of legal publications where and organization wasn't the publisher, but wasn't an author, but is identified with the book.

Friday, July 25, 2014

Name/Title NAR (Name Authority Record) in RDA : Questions & Answers : RDA Examples

QUESTION: I have to create a N/T NAR for selections of stories of an author, but the NAR for the author is established in AACR2. How to create N/T NAR in this case, can we establish N/T NAR straightaway in RDA?
ANSWER: In order to create a Name/Title Name Authority Record (NAR) for a MARC21 240 tag in Resource Description & Access (RDA), the base  Name Authority Record (NAR) for the person has to be also in RDA first. If the base NAR for the person is in AACR2, then it should be converted to RDA. For example, please see lccn: 2012350684
  • Bibliographic Record

1000_ |a Jayabhikkhu,  |d 1908-1969,  |e author.
24010 |a Children's stories.  |k Selections
24510 |a Jayabhikkhunī śreshṭha bāḷavārtāo =  |b Jaybhikhkhuni shreshtha balvartao / |c śreṇī-sampādako, Yaśavanta Mahetā, Śraddhā Trivedī.
24631 |a Jaybhikhkhuni shreshtha balvartao
250__ |a Pahelī āvr̥tti.
264_1 |a Amadāvāda :  |b Gūrjara Grantharatna Kāryālaya,  |c 2011.
300__ |a 7, 152 pages :  |b illustrations ;  |c 21 cm.
336__ |a text  |2 rdacontent
337__ |a unmediated  |2 rdamedia
338__ |a volume  |2 rdacarrier
4900_ |a Gurjara bāḷavārtāvaibhava
520__ |a Representative collection of children's short stories.
546__ |a In Gujarati.
650_0 |a Children's stories, Gujarati.
[Source: Library of Congress Online Catalog: ]

  • NAR for Author Converted to RDA from AACR2

008920113n| azannaabn |a aaa
010__ |a n 89260083
035__ |a (OCoLC)oca03089021
040__ |a DLC |b eng |c DLC |d DLC |d DLC-ON |d OCoLC |e rda
046__ |f 1908 |g 1969
053_0 |a PK1859.D368
1000_ |a Jayabhikkhu, |d 1908-1969
375__ |a male
377__ |a guj
4000_ |a Jayabhikhkhu, |d 1908-1969
4001_ |a Desāī, Bālābhāī, |d 1908-1969
4000_ |a Bālābhāī Vīracanda Desāī, |d 1980-1969
670__ |a Ṭhakkara, Naṭubhāī. Jayabhikkhu, vyaktitva ane vāṇmaya, 1991: |b t.p. (Jayabhikkhu) t.p. verso (Jayabhikhkhu)
670__ |a New Delhi MARC file, 10/15/91 |b (MLC hdg.: Jayabhikkhu, 1908-1969)
670__ |a New Delhi non-MARC file |b (hdg.: Desāī, Bālābhāī Vīracanda, 1908-1969; usage: Jayabhikkhu)

  • Name/Title NAR Created in RDA
LC control no.:n 2012217901
LCCN permalink:
HEADING:Jayabhikkhu, 1908-1969. Children’s stories. Selections
00000560cz a2200157n 450
008130625n| azannaabn |a aaa
010__ |a n 2012217901
040__ |a DLC |b eng |c DLC |e rda
046__ |k 2012
1000_ |a Jayabhikkhu, |d 1908-1969. |t Children’s stories. |k Selections
370__ |g Ahmadābād, India
4000_ |a Jayabhikkhu, |d 1908-1969. |t Jayabhikkhunī śreshṭha bāḷavārtāo
4000_ |a Jayabhikkhu, |d 1908-1969. |t Jaybhikhkhunishreshtha balvartao
670__ |a Jayabhikkhunī śreshṭha bāḷavārtāo, 2011.

RDA Blog ➨ 150000 Pageviews
Dear all. I am pleased to inform you that RDA Blog has crossed 150000 pageviews. Thanks all for your support and encouragement. The layout of the blog is changed for more convenient browsing. Please provide your feedback/comments if you find RDA Blog helpful, through RDA Blog Guest Book. Please Like/Share on Facebook and do a g+1 on Google+ through widgets on top right side of RDA Blog (Facebook and Google+ widgets shown by arrows in the picture given below).

Tuesday, July 15, 2014

International Standard Serial Number (ISSN) - MARC to RDA Mapping

022International Standard Serial Number
022aInternational Standard Serial Number2.15Identifier for the Manifestation
022mCancelled ISSN-LN/A
022yIncorrect ISSN2.15Identifier for the Manifestation
022zCancelled ISSN2.15Identifier for the Manifestation

[Source: RDA Toolkit]

Friday, July 4, 2014

Identifying RDA Records

There are two indications that a record is an RDA bibliographic record:
  • Leader/18 contains the value “i” (ISBD punctuation included) 

  • Field 040 $e contains the code “rda”

[Source: Library of Congress]

Thursday, June 26, 2014

Articles on Resource Description and Access (RDA)

Resource Description and Access (RDA) ➨ Articles

Tech Services on the Web: RESOURCE DESCRIPTION ANDACCESS (RDA) BLOG http://resourcedescriptionandaccess. blogspot. com

EY Wong - Technical Services Quarterly, 2014
The frequency of the posts is steady throughout 2013. Some of the posts are extracts from
RDA toolkit and other trusted cataloging sources; other posts are snapshots of cataloging
records intended to provide interpretations on certain cataloging scenarios. The

Implementing RDA at the University of Illinois at Urbana-Champaign Library

Q Jin, JA Sandberg - Technical Services Quarterly, 2014

Technical Services Report: Cataloging in RDA and Linked Data environments. A Report of the ALCTS Cataloging & Metadata Management Section, Cataloging and …

A Guimaraes - Technical Services Quarterly, 2014

Beyond Content, Media, and Carrier: RDA Carrier Characteristics

S Bernstein - Cataloging & Classification Quarterly, 2014

RDA Display and the General Material Designation: An Innovative Solution

RS Panchyshyn - Cataloging & Classification Quarterly, 2014

RDA: Strategies for Implementation

D Sullivan - Australian Academic & Research Libraries, 2014

[PDF] Authors and Authorities in Post-RDA Library Systems: A Case Study

HL Moulaison - 2014

RDA Training and Implementation at Duke University Libraries: Minimizing the Distraction

AH Turner - Journal of Library Metadata, 2014

[PDF] Preparing LIS Students for a Career in Metadata Librarianship

B Mooney Gonzales - SLIS Student Research Journal, 2014

Saturday, June 14, 2014


approximate date[2014?]
supplied date[2014]
date of publication not identified[date of publication not identified]
two years[2013 or 2014]
betwen years[between 2005 and 2014?]
not before[not before 2000]
not after[not after 2000]
betwen years with date[between March 13, 2000 and July 10, 2014]


Note: Cells left blank for Catalogers to fill with data. Please supply cases and solutions quoting proper RDA rules where date of publication not identified. It will be included in this table along with name of the cataloger. Write your suggestions in the "comments" section of this blog post.