Saturday, April 19, 2014

Authorized Access Point - Meeting Name - MARC to RDA Mapping

111Main entry—Meeting name19.2Creator
111Main entry—Meeting name19.3Other Person, Family, or Corporate Body Associated with a Work
111aMeeting name or jurisdiction name as entry element11.2.2Preferred Name for the Corporate Body
111aMeeting name or jurisdiction name as entry element11.3.3Location of Headquarters, etc.
111aMeeting name or jurisdiction name as entry element11.4.3Date of Establishment
111aMeeting name or jurisdiction name as entry element11.4.4Date of Termination
111aMeeting name or jurisdiction name as entry element11.5Associated Institution
111aMeeting name or jurisdiction name as entry element11.7Other Designation Associated with the Corporate Body
111cLocation of meeting11.3.2Location of Conference, etc.
111cLocation of meeting11.5Associated Institution
111dDate of meeting11.4.2Date of Conference, etc.
111dDate of meeting6.4Date of Work
111eSubordinate unit11.2.2Preferred Name for the Corporate Body
111fDate of a work6.10Date of Expression
111gMiscellaneous informationN/A
111jRelator term18.5Relationship Designator
111kForm subheading6.2.2Preferred Title for the Work
111lLanguage of a work6.11Language of Expression
111nNumber of part/section/meeting6.2.2Preferred Title for the Work
111nNumber of part/section/meeting6.3Form of Work
111nNumber of part/section/meeting6.4Date of Work
111nNumber of part/section/meeting6.5Place of Origin of the Work
111nNumber of part/section/meeting6.6Other Distinguishing Characteristic of the Work
111nNumber of part/section/meeting11.6Number of a Conference, etc.
111pName of part/section of a work6.2.2Preferred Title for the Work
111pName of part/section of a work6.3Form of Work
111pName of part/section of a work6.4Date of Work
111pName of part/section of a work6.5Place of Origin of the Work
111pName of part/section of a work6.6Other Distinguishing Characteristic of the Work
111qName of meeting following jurisdiction name entry element11.2.2Preferred Name for the Corporate Body
111tTitle of a work6.2.2Preferred Title for the Work
111tTitle of a work6.3Form of Work
111tTitle of a work6.4Date of Work
111tTitle of a work6.5Place of Origin of the Work
111tTitle of a work6.6Other Distinguishing Characteristic of the Work
111uAffiliation11.9Address of the Corporate Body

[Source: RDA Toolkit]

Saturday, March 29, 2014

RDA: What it is --

A Content Standard

RDA provides instructions on recording the content of records.
  • It does not provide instruction on how a given library system (e.g.) should display the bibliographic information (although there is information about displaying RDA content).
  • Nor does it provide instruction on encoding the information. RDA is schema-neutral. You can use it with any schema, including MARC, or Dublin Core.

More International

RDA is less Anglo-centric than AACR2.  It focuses on user needs, as stressed in the International Cataloguing Principles.

In addition, the agency preparing the description can make choices regarding the:
  • language of additions to access points
  • language of supplied data
  • script and transliteration
  • calendar
  • numeric system

Wider Scope of Resources

RDA also covers the wider scope of resources being acquired in libraries today. It provides for more elements for:
  • non-printed text resources
  • non-text resources
  • unpublished resources

But RDA defers appropriately to the specialist manuals of collaborative communities in situations where more detailed description is wanted than the general view provided by RDA (e.g., music, sound recordings, moving images, electronic resources, cartographic materials).

Authority Data

RDA includes instructions on authority data, based on attributes and relationships in the FRAD model. There were no AACR2 rules for authority data and authority records. RDA doesn’t indicate how authority data should be encoded; but for now, that information will continue to be documented by most libraries in authority records.

Controlled Vocabularies

RDA has many controlled vocabularies. Only a few of the vocabularies are closed (e.g., content type; media type; carrier type; mode of issuance). Most of the vocabularies are open; you can either supply your own term as needed, or suggest a term be added to the vocabulary (or do both).

Libraries may decide to include some of these controlled vocabulary terms in templates; ILS vendors could provide them in drop-down lists.  And so on. 

The RDA vocabularies are now registered on the Web. The existence of those machine-readable controlled vocabularies will allow more machine manipulation of data than is now possible, including the mapping of RDA to other metadata schemes.

[Source: Library of Congress]

Thursday, March 20, 2014



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.

Wednesday, March 12, 2014

RDAExpress : a service to convert any library catalog to RDA

A clean database is the key to providing library users the best possible searching experience and catalogers have dedicated years of service in cultivating and maintaining their databases to this end. The new RDA standard has great benefits, providing enriched content and priming libraries for a Linked Data environment, but it also has an impact on workflow, budgets and patron experience. RDA holds the promise for libraries to restructure its data to provide a better searching experience for users and ultimately link outside the library to be more competitive in today’s digital world.  Most integrated library systems are compliant with RDA, in that they can handle a mixed database of AACR2 and RDA records, but is that really helpful to your users? A mixed database results in a mixed display, with your newer records providing more specific information than your legacy records, disrupting search and discovery.

RDAExpress ( promises to help address this disruption and take the headache out of retrospective conversion of your database to RDA - an undertaking that is nearly impossible for catalogers to do while still keeping up with new titles. It is an RDA Conversion service to upgrade your existing records without worrying what kind of ILS you currently have. 
"Our service is going to unleash greater discoverability in library catalogs" says Heather Powers, eBiblioFile Product Owner. “Library records will have more and better relationships and descriptions. The catalog will be ready for FRBR. And the best part is that RDAExpress does all the work to make this possible now.”

Saturday, March 8, 2014

Additional information on use of $b in fields 336-338

Library of Congress has begun supplying $b codes for the equivalent terms in $a of fields 336 (Content type), 337 (Media type), and 338 (Carrier type). This is the most efficient manner to start populating a subfield that LC initially chose not to apply. This will allow LC records to conform more to records produced outside of LC (e.g., OCLC generally adds the codes in $b in new records). It will be supplied automatically if cataloger are using the macro or the RDA templates in Voyager—staff are not expected to manually add $b to fields in existing records that lack the subfield.

[Source : Library of Congress]

Appendix I : New Relationship Designators

There are three new relationship designators Appendix I

organizer [I.2.2]
cartographer (expression) [I.3.1]
minute taker [I.3.1]

[Source : RDA Toolkit]

Comments by Aaron Kuperman, Law Librarian, Library of Congress : This list is flexible. It is expected that new terms will be constantly added. Consider it as being similar to how LCSH grows, rather than the former system under LCRI under changes were few and far between.

Editor of Compilation vs Compiler

The editor of a compilation, as defined in I.3.1, is not a creator of a work and thus has to be treated as a 700, not a 100.

On the other hand, a compiler (for example of a dictionary, a directory, a bibliography, etc.) can be considered a creator (see I.2.1) and thus can be treated as a 100.

Expert remarks by Aaron KupermanLaw Librarian, Library of Congress A good rule of thumb is that a compilation needs to consist of works that can (and should) be listed in the contents note.

Conventional Collective title / Uniform title : Questions and Answers

Question : Is it allowed to give 240 conventional collective title / uniform title in following example:

010__ |a 2012352243
020__ |a 9788179171615 (hb)
020__ |z 9788179171623 (pb)
025__ |a I-H-2012-352243; 21-92
037__ |b Library of Congress -- New Delhi Overseas Office
040__ |a DLC |b eng |c DLC |e rda |d DLC
0411_ |a hin |h hin |h nep
042__ |a lcode |a pcc
043__ |a a-np---
05000 |a DS495.6 |b .P67 2011
1000_ |a Pracaṇḍa, |d 1944- |e interviewee.
24010 |a Interviews. |k Selections
24510 |a Evaresṭa para Lāla jhaṇḍā : |b Nepāla ke Māovādī netā Pracaṇḍa se bātacīta / |c sampādaka Ānanda Svarūpa Varmā.
264_1 |a Dillī : |b Grantha Śilpī (Iṇḍiyā) Prāiveṭa Limiṭeḍa, |c 2011.
300__ |a 357 pages ; |c 22 cm
336__ |a text |2 rdacontent
337__ |a unmediated |2 rdamedia
338__ |a volume |2 rdacarrier
520__ |a Collection of interviews with Pracanda, born 1944, Nepali politician and chairman of the Nepāla Kamyunishṭa Pārṭī (Māovādī) on the current political scene, Maoist movement, civil war, and insurgency in Nepal.
546__ |a In Hindi; includes articles translated from English and Nepali.
60000 |a Pracaṇḍa, |d 1944- |v Interviews.
650_0 |a Politicians |z Nepal |v Interviews.
61020 |a Nepāla Kamyunishṭa Pārṭī (Māovādī) |v Interviews.
651_0 |a Nepal |x Politics and government |y 1990-
651_0 |a Nepal |x History |y Civil War, 1996-2006.
650_0 |a Insurgency |z Nepal

Answer : The relevant RDA rule for this case is - Complete Works in a Single Form which prescribes to Record one of the conventional collective titles as the preferred title for a compilation of works that consists of, or purports to be, the complete works of a person, family, or corporate body, in one particular form such as: Correspondence, Novels, Speeches, Lyrics, etc ...

Comment : Remember that is not a closed list so you can choose whatever term is appropriate if it’s not already listed there. As this a compilation of Pracanda’s interviews, the 240 is correct. Under RDA, the decision to create a conventional collective title (formerly “uniform title”) based on whether the title proper is adequate or not (as we used to under AACR2, .cf LCRI 25.10) no longer applies.

[Source: LC online catalog and RDA Toolkit]

Corporate Body Relationship Designator : Questions & Answers

Question: What would be the relationship designator for organizer of a conference.

Answer: organizer : A person, family, or corporate body organizing the exhibit, event, conference, etc., which gave rise to a work.

Please note that is a new addition in Appendix A I.2.2 - Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work

[Source: RDA Toolkit]

Wednesday, February 26, 2014

RDA Terminology

Listed below are some of the main differences in terminology between AACR2 and RDA. Some of the changes reflect our turning away from the catalog card environment, while others reflect terminology in the FRBR/FRAD models and the International Cataloguing Principles.

authorized access point
“heading” reflects outmoded ‘catalog-card-speak’
author, composer, artist, etc.

main entry
preferred title and, if appropriate, the authorized access point for the creator
“main entry” reflects outmoded ‘catalog-card-speak’, related to cards in a file cabinet
uniform title
Two RDA counterparts:
1.      the preferred title and any differentiating information;
2.      a conventional collective title such as “Works”

see reference
variant access point

see also reference
authorized access point for related entity

physical description
carrier description

general material designator
three elements:
1.      content type
2.      media type
3.      carrier type
GMD was an inconsistent presentation of different categories of information
chief source
preferred sources
This is not only a change in terminology; ‘sources’ have been expanded from a single source to multiple sources

[Source: Library of Congress]