Saturday, December 20, 2014

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

Friday, November 21, 2014

RDA Tookit Release (October 14, 2014) : Changes in and Revision of Resource Description & Access and LC-PCC PS

A new release of the RDA Toolkit was published on Tuesday, October 14.  This message will cover several points you should be aware of related to the release. 

TOPIC 1: Changes in RDA Content
TOPIC 2: Change in Content in LC-PCC PSs
TOPIC 3: Additional Content in the RDA Toolkit

TOPIC 1: Changes in RDA Content

This update only contains  “Fast Track” changes that are relatively minor (these are not flagged in the RDA text with revision history icons).  The linked file 6JSC-Sec-13.pdf contains a complete listing of the Fast Track changes. You’ll note that many of the changes are to examples, including moving some examples to more appropriate instructions, replacing some examples, and adding initial articles to some preferred and variant titles, etc.—note that the addition of the initial articles are intended to exhibit the base instruction at RDA, and that LC/PCC practice is to  OMIT initial articles (per, Alternative, etc.), so do not interpret the revised examples as a policy change.

There are also some new and revised relationship designators for use in Appendices I, J, and K including these:

book artist
graphic novelization of (work)   Reciprocal relationship: adapted as graphic novel (work)
adapted as libretto (work)  [replaces basis for libretto (work)]
adapted as novel (work)  [replaces novelization (work)]
adapted in verse as (work)  [replaces verse adaptation (work)]
digested as (work)  [replaces digest (work)]
modified by variation as (work)  [replaces musical variations (work)]

TOPIC 2: Change in Content in LC-PCC PSs

A summary of LC-PCC PS updates incorporated in this release is linked (LCPCCPS_changes_2014_October.doc).  The changes are fairly minor, except for some revisions/new statements requested by the music cataloging community (e.g.,,,, Alternative).  Some information previously held only in the Descriptive Cataloging Manual section Z1 has moved to policy statements (e.g.,, for profession and/or occupation). Another minor change is related to, well,  “minor changes”!  The PS for introduces a new category for minor changes to corporate body names--the addition, omission, or fluctuation of a frequency word(e.g., annual, biennial) in a conference name.

TOPIC 3: Additional Content in the RDA Toolkit

This release will include the addition of British Library Policy Statements (BL PS). The BL PS icons will be set to display in the RDA text by default, but the links can be turned off in the Toolkit Settings portion of the My Profile page (if you have created your own profile).

The documents attached to this email may also be found on the Web:
[Source: Dave Reser, LC PSD]

[Note: Above message was addressed to Library of Congress catalogers, but it is also a good source for other libraries and cataloging librarians as well]

Thursday, October 30, 2014

RDA Blog Reaches 200000 Pageviews

Hi all, I am pleased to announce that RDA Blog has crossed 200000 pageviews mark. It is interesting to note that the first hundred thousand pageviews came in 3 years, but it took just 8 months to reach another hundred thousand pageviews.
Thanks all for your love, support and suggestions. Please post your feedback and comments on RDA Blog Guest Book. Select remarks will be posted on RDA Blog Testimonials page.

click on image to enlarge


RDA Blog 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 Cataloging Rules (AACR2). This blog lists description and links to resources on Resource Description & Access (RDA). It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on Resource Description and Access, FRBR, FRAD, FRSAD, MARC standards, AACR2, BIBFRAME, and other items related to current developments and trends in library cataloging practice. 


Monday, October 27, 2014

Saturday, October 25, 2014

Transcription in Resource Description & Access (RDA) Cataloging

“Take What You See and Accept What You Get”

This is the overriding principle of RDA concerning the transcription of data. It is consistent with the ICP “Principle of Representation” to represent the resource the way it represents itself. This is a fairly significant change from AACR2, which includes extensive rules for abbreviations, capitalization, punctuation, numerals, symbols, etc., and in some cases directs the cataloger to ‘correct’ data which is known to be wrong (e.g., typos). With RDA we generally do not alter what is on the resource when transcribing information for certain elements. This is not only to follow the principle of representation, but also for a more practical reason: to encourage re-use of found data you can copy and paste or scan or download into your description of the resource.

Let’s see what this principle means for you as an LC cataloger, regarding capitalization, punctuation, and spacing.  It is critical that you understand LCPS 1.7.1; the overriding principles codified there are generally not discussed elsewhere in the specific instructions.

P         In the RDA Toolkit, display RDA 1.7.1

Note that the alternatives at RDA 1.7.1 allow for the use of in-house guidelines for capitalization, punctuation, numerals, symbols, abbreviations, etc. -- in lieu of RDA instructions or appendices.


Regarding capitalization, RDA 1.7.2 directs the cataloger to “Apply the instructions on capitalization found in Appendix A.  But LC policy says that you can follow the capitalization that you find, without adjusting it.

P         In the RDA Toolkit, click on the first LCPS link in the Alternativeto RDA 1.7.1

“For capitalization of transcribed elements, either “take what you see” on the resource or follow [Appendix] A.”

Punctuation, Numerals, Symbols, Abbreviations, etc.

LCPS 1.7.1, First Alternative says “follow the guidelines in 1.7.3 – 1.7.9 and in the appendices.”

Transcribed Elements vs. Recorded Elements

RDA distinguishes between transcribed elements and recorded elements.
  • For transcribed elements, generally accept the data as found on the resource.
  • For recorded elements, the found information is often adjusted (for example, the hyphens in an ISBN are omitted).

Language and Script

The basic instruction for most of the elements for describing a manifestation is to transcribe the data in the language and script found in the resource (“take what you see”).  RDA 1.4 contains a list of elements to be transcribed from the resource in the found language and script.

For non-transcribed elements:
  • When recording all other elements (e.g., extent, notes), record them in the language and script preferred by the agency creating the data (at LC, this is English)
  • When adding information within an element, record it in the language and script of the element to which it is being added
  • When supplying an entire element, generally supply it in English

Regarding non-Latin scripts, LCPS 1.4, First Alternative states the LC policy to record a transliteration instead, or to give both (using the MARC 880 fields)

[Source: Library of Congress]


Also check out following RDA rules in RDA Toolkit for further details:

1.7 Transcription
  • 1.7.1 General Guidelines on Transcription
  • 1.7.2 Capitalization
  • 1.7.3 Punctuation
  • 1.7.4 Diacritical Marks
  • 1.7.5 Symbols
  • 1.7.6 Spacing of Initials and Acronyms
  • 1.7.7 Letters or Words Intended to Be Read More Than Once
  • 1.7.8 Abbreviations
  • 1.7.9 Inaccuracies


[Updated 2014-10-28]

Friday, October 17, 2014

What is FRBR?

What is FRBR? -- RDA Quiz on Google+ Community RDA Cataloging.

Join RDA Cataloging online community / group / forum and share ideas on RDA and discuss issues related to Resource Description and Access Cataloging.

Following are the comments received on this RDA Blog post


Roger Hawcroft
Library Consultant
Salman, FRBR is an acronym for Functional Requirements for Bibliographic Records. It stems from recommendations made by IFLA in 1988. The FRBR represents the departure of bibliographic description from the long-standing linear model as used in AACR... to a muti-tiered concept contemporaneous with current technology and the increasing development of digital formats and storage. These principles underpin RDA - Resource Description & Access..

You may find the following outline useful:

I have also placed a list of readings ( not intended to be comprehensive or entirely up-to-dtate) in DropBox for you:

An online search should relatively easily find you the latest papers / articles / opinion on this concept of cataloguing and I am sure that you will find many librarians on LI that have plenty to say for and against the approach!


Sris Ponniahpillai
Library Officer at University of Technology, Sydney
Salman, Hope the article in the following link would help you to understand what FRBR stands for in library terms. Thanks & Best Regards, Sris


Alan Danskin
Metadata Standards Manager at The British Library
FRBR (Functional Requirements for Bibliographic Records) is a model published by IFLA. RDA is an implementation of the the FRBR and FRAD (Functional Requirements for Authority Data) models. The FRBR Review Group is currently working on consolidation of these models and the Functional Requirements for Subject Authority Data (FRSAD) model. See and


Harshadkumar Patel
Deputy Librarian, C.U. Shah Medical College
Functional Requirements for Bibliographic Records is a conceptual entity-relationship model developed by the International Federation of Library Associations and Institutions that relates user tasks of retrieval and access in online library catalogues and bibliographic databases from a user's perspective.


Erik Dessureault
Library Systems Technician at Concordia University
When I was first introduced to FRBR and RDA in library school, I was immediately struck at how the structure of FRBR lines up nicely with the structure of XML. I am sure that is not a coincidence. Our teacher made us draw out FRBR schemas as part of our assignment, and the parallels with database entity relation diagrams and programming flowcharts were immediately apparent to me. Coming from a information technology background, with some programming and database creation/management experience, FRBR came naturally to me, and struck me as a very rational way to organize information. I can see the potential for automation and standardization and I am eager to see FRBR and RDA become accepted standards in our field.

Sunday, October 12, 2014

RDA Cataloging Example of Selections & Translations

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

Bibliographic Record

Authority Record

LC control no.:n 2012217312
LCCN permalink:
HEADING:Gurasharana Siṅgha, 1929-2011. Plays. Selections. Hindi
00000528cz a2200133n 450
008130524n| azannaabn |a aaa
010__ |a n 2012217312
040__ |a DLC |b eng |c DLC |e rda
1000_ |a Gurasharana Siṅgha, |d 1929-2011. |t Plays. |k Selections. |l Hindi
4000_ |a Gurasharana Siṅgha, |d 1929-2011. |t Pratinidhi nāṭaka
4000_ |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]

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