Friday, September 26, 2014

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


  • 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     

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

Saturday, September 20, 2014

Articles, Books, Presentations on Resource Description and Access (RDA)

Resource Description and Access (RDA) ➨ Articles, Books, Presentations, Thesis, Videos

Awareness, Perceptions, and Expectations of Academic Librarians in Turkey about Resource Description and Access (RDA)

D Atılgan, N Özel, T Çakmak - Cataloging & Classification Quarterly, 2014
Resource Description and Access (RDA), as a new cataloging standard, supports libraries in
their bibliographic description processes by increasing access points. The increasing
importance of RDA implementation requires adaptation to a new bibliographic universe. ...

China's Road to RDA

C Luo, D Zhao, D Qi - Cataloging & Classification Quarterly, 2014
... 9 (2012): 3–5. 8 Jiang Hualin, “Analysis on the Use Method and the Function of Resource
Description and Access Toolkit,” Library Development (Harbin) no. 9 (2012): 24–26. ... 10 Tang
Caixia, “Resources Analysis of RDA Toolkit,” Library Journal (Shanghai) 32, no. ...

RDA in Spanish: Translation Issues and Training Implications

A Garcia - Cataloging & Classification Quarterly, 2014
... Quarterly 49, nos. 7/8 (2011): 572. 17 Library of Congress, “Resource Description
and Access (RDA): Information and Resources in Preparation for RDA,” (accessed January 7, 2014). 18 Library of ...

Are Philippine Librarians Ready for Resource Description and Access (RDA)? The Mindanao Experience

AP Acedera - Cataloging & Classification Quarterly, 2014
This study aimed to find out the level of readiness of Mindanao librarians to use Resource
Description and Access (RDA), which has been prescribed and adopted by the Philippine
Professional Regulatory Board for Librarians (PRBFL). The majority of librarians are ...

The Adoption of RDA in the German-Speaking Countries

R Behrens, C Frodl, R Polak-Bennemann - Cataloging & Classification Quarterly, 2014
... A decision with such far-reaching implications as the adoption of a new code for the cataloging
of resources represents a great challenge for all concerned. ... In the changeover to the international
Resource Description and Access (RDA) standard described here, the ...

RDA: National Library Board Singapore's Learning Journey

K Choi, HM Yusof, F Ibrahim - Cataloging & Classification Quarterly, 2014
... took on the national effort to execute the new principles for description and access. ... 2) NLB's RDA
policies, standards, and decisions; (3) RDA documentation and resources; (4) communication ...
ranged from the availability and access to RDA documents and resource materials to ...

RDA in Israel

M Goldsmith, E Adler - Cataloging & Classification Quarterly, 2014
... As mentioned above, the Israeli practice of cataloging non-Roman script resources in the
vernacular necessitates translating various terms into Hebrew, Arabic, and Russian. ... 10 Library
of Congress, “Testing Resource Description and Access (RDA).” ...

In the Company of My Peers:

Implementation of RDA in Canada

E Cross, S Andrews, T Grover, C Oliver, P Riva - Cataloging & Classification Quarterly, 2014
... countries of RDA: Resource Description and Access, the new standard that supersedes the
Anglo-American Cataloguing Rules, 2nd Edition, Revised (AACR2). ... Canadian libraries took
advantage both of Canadian resources and those made available by other countries. ...

Implementing RDA in a Time of Change: RDA and System Migration at RMIT University

M Parent - Cataloging & Classification Quarterly, 2014
... in greater detail, and to provide training in cataloging translations and resources in multiple ... of
description, how to handle transcription elements (transcribe as found on resource OR according
to ... policy at the outset of training considered type of RDA description (descriptive) and ...

Catalogue 2.0: The future of the library catalogue

D Sullivan - The Australian Library Journal, 2014
... RDA and serials cataloguing is a technical manual for those who need to catalogue serials using
RDA (Resource Description and Access) and as ... of the MARC 21 formats, but not necessarily
as they apply to the cataloguing of serials and on-going integrating resources'. …

Acceptance and Viewpoint of Iranian Catalogers Regarding RDA: The Case of the National Library and Archive of Iran

F Pazooki, MH Zeinolabedini, S Arastoopoor - Cataloging & Classification Quarterly, 2014
... 12 Chris Stanton, “Resource Description & Access (RDA) Update from the National Library”
(2012), ... 13 Farshid Danesh, Mina Afshar, “RDA: A New
Standard for Digital Resources Access,” 2008, ...

RDA Implementation Issues in the Iranian National Bibliography: An Analysis of Bibliographic Records

F Pazooki, MH Zeinolabedini, S Arastoopoor - Cataloging & Classification Quarterly, 2014
... Therefore, Resource Description and Access (RDA) was formed. RDA makes description of, and
access to, print and electronic resources possible based on the Functional Requirements of
Bibliographic Records (FRBR) conceptual model and accordingly, not only will it affect ...

[PDF] Using RDA to Catalog ETDs

J Milligan - 2014
... Page 14. PHYSICAL DESCRIPTION FIXED FIELD, MARC 007 ... publication, release, or issuing
of a resource. Consider all online resources to be published. ... “For all other records make a Mode
of Access note only if the resource is accessed by means other than the World Wide ...

The RDA Workbook: Learning the Basics of Resource Description and Access

KE McCormick - Technical Services Quarterly, 2014
Chapter 2 covers preparing bibliographic records using RDA. This core portion of the book
covers the major RDA changes seen in MARC records. It covers the new publication field,
the 33x fields, relationship designators, etcetera. The exercises in this chapter provide the ...

MAxwell's Handbook for RDA: Examining and Illustrating RDA: Resource Description and AccessUsing MARC 21

PH Lisius - Technical Services Quarterly, 2014
Maxwell's book jumps around the larger sections of RDA. For example,''Describing
Manifestations and Items''(Chapter 2) follows the analogous Section 1 of RDA,''Recording
Attributes of Manifestation & Item.''Maxwell's Chapters 3 through 5 respectively cover the ...

Making the Move to RDA: A Self-Study Primer for Catalogers

LM McFall - Technical Services Quarterly, 2014
... Resource Description and Access, or RDA, has been a hot topic in the world of
cataloging for nearly 10 years. Since its official adoption in 2013, several books have
been written about how to implement and use RDA. The latest ...

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