Showing posts with label RDA CATALOGING. Show all posts
Showing posts with label RDA CATALOGING. Show all posts

Wednesday, July 26, 2017

What are the Benefits of RDA?

What are the Benefits of RDA?

#RDA #CATALOGING #LIBRARIANSHIPSTUDIES

WHAT ARE THE BENEFITS OF RDA? / WHY IS RDA NEEDED?

[Main article: Resource Description and Access https://librarianshipstudies.blogspot.com/2017/07/resource-description-and-access.html]

=> RDA builds on the strengths of AACR2 but has some new features that make it more useful for description as a cataloging code for the digital environment in which libraries now operate.

=> RDA is better at catering for digital resources and for resources with multiple characteristics and will provide more guidance on the creation of authority headings.

=> RDA has been developed with the end-user in mind.

=> RDA provides a consistent, flexible and extensible framework for the description of all types of resources, including digital resources and those with multiple characteristics.
RDA is compatible with internationally established principles, models, and standards.

Friday, July 7, 2017

Resource Description and Access

Resource Description and Access

Glossary of Library & Information Science - RESOURCE DESCRIPTION AND ACCESS (RDA) ➨ RDA stands for “Resource Description and Access” and is the title of the standard, that is the successor to AACR2. Resource Description and Access (RDA) is a standard for descriptive cataloging providing instructions and guidelines on formulating bibliographic data. Resource Description & Access (RDA) is a set of cataloging instructions based on FRBR and FRAD, for producing the description and name and title access points representing a resource. RDA offers libraries the potential to change significantly how bibliographic data is created and used. RDA is a standard for resource description and access designed for the digital world. It provides (i) A flexible framework for describing all resources (analog and digital) that is extensible for new types of material, (ii) Data that is readily adaptable to new and emerging database structures, (iii) Data that is compatible with existing records in online library catalogs. RDA is a package of data elements, guidelines, and instructions for creating library and cultural heritage resource metadata that are well-formed according to international models for user-focused linked data applications.  RDA goes beyond earlier cataloging codes in that it provides guidelines on cataloging digital resources and places a stronger emphasis on helping users find, identify, select, and obtain the information they want. RDA also supports the clustering of bibliographic records in order to show relationships between works and their creators.

READ MORE:

#RDA #CATALOGING #LIBRARIANSHIPSTUDIES

Friday, May 16, 2014

Authorized Access Point - Main Entry - Uniform Title (AACR2) / Preferred Title (RDA) - MARC to RDA Mapping

MARC 21
FIELD
TAG
MARC 21
SUBFIELD CODE
MARC 21 FIELD /
SUBFIELD NAME
RDA
INSTRUCTION
NUMBER
RDA
ELEMENT
NAME
130Main entry—Uniform title
130aUniform title6.2.2Preferred Title for the Work
130aUniform title6.3Form of Work
130aUniform title6.4Date of Work
130aUniform title6.5Place of Origin of the Work
130aUniform title6.6Other Distinguishing Characteristic of the Work
130dDate of treaty signing6.4Date of Work
130fDate of a work6.10Date of Expression
130gMiscellaneous informationN/A
130hMedium6.9Content Type
130kForm subheading6.2.2Preferred Title for the Work
130lLanguage of a work6.11Language of Expression
130mMedium of performance for music6.15Medium of Performance
130nNumber of part/section of a work6.2.2Preferred Title for the Work
130nNumber of part/section of a work6.3Form of Work
130nNumber of part/section of a work6.4Date of Work
130nNumber of part/section of a work6.5Place of Origin of the Work
130nNumber of part/section of a work6.6Other Distinguishing Characteristic of the Work
130nNumber of part/section of a work6.16Numeric Designation of a Musical Work
130oArranged statement for music6.12Other Distinguishing Characteristic of the Expression
130pName of part/section of a work6.2.2Preferred Title for the Work
130pName of part/section of a work6.3Form of Work
130pName of part/section of a work6.4Date of Work
130pName of part/section of a work6.5Place of Origin of the Work
130pName of part/section of a work6.6Other Distinguishing Characteristic of the Work
130rKey for music6.17Key
130sVersion6.12Other Distinguishing Characteristic of the Expression
130tTitle of a workN/A



[Source: RDA Toolkit]

Wednesday, May 7, 2014

The Structure of RDA

General Structure

Remember that RDA has a clear structure:
  • Table of Contents
  • Introduction
  • Specific instructions
o   Entities and their attributes
·            Group 1 (WEMI) (Chapters 1-7)
·            Group 2 (PFC) (Chapters 8-16)
o   Relationships (Chapters 17-22, 24-32)
  • Appendices for
o   Abbreviation
o   Capitalization
o   Relationship designators (more on this later)
  • Glossary with links to the text of the instructions
  • Index

Not Organized Like AACR2

The organization of RDA is very different from AACR2. Instead of separate chapters for classes of materials (books, cartographic materials, printed music, etc.), RDA is principle-based and organized around the FRBR/FRAD tasks to help users “identify” and “relate” the resources they need from our collections. There are general instructions applying to all resources with specific instructions for characteristics unique to certain categories of resources.

The identifying elements for each thing we are describing are addressed separately in each chapter. RDA provides instructions on what identifying elements are needed; for those chapters related to access points, it then provides -- at the end of those chapters -- the instructions on how to assemble those elements to create authorized access points (remember, that’s what AACR2 calls headings). We will see this particularly in chapter 6 and chapters 9-11.

Not a Linear Resource

When you use online tools, you don’t read the content in the same way as you read a printed text.  You don’t generally read linearly from one page to the next. Instead, you read purposefully.  You perform keyword searches (and then view several hits from the results list), follow links, and jump to elements from a Table of Contents or other navigational feature

Some of the “length” of RDA is due to the need for duplicating content to serve the catalogers who will be arriving at that content in these different ways from different starting points.

ALA also publishes a print version of RDA. A print version of the RDA element set (a subset of the RDA content, organized by FRBR and FRAD entity) is also available from ALA Publishing.


“Core-ness”

Some of the RDA elements are designated as “core” elements. The assignment of core status is based on attributes mandatory for a national level record, as documented in the FRBR/FRAD modules. Core-ness is identified at the element level. Some elements are always core (if applicable and the information is available); some are core only in certain situations.

Core elements can be seen in two ways within RDA:
  • They are discussed in general, and listed as a group, in the sub-instructions of RDA 0.6
  • They are clearly labeled in light blue at each core instruction.  See, for example, this label for the core element 2.3.2, “Title Proper.”  If the status of an element as core depends upon the situation, an explanation appears after the “Core element” label.
We will see that LC has identified other elements as “LC Core” for our cataloging.


Alternatives, Options, and Exceptions

RDA designates a number of guidelines and instructions as alternatives, options, or exceptions. All are clearly labeled as such in the Toolkit by the presence of a green vertical bar in the left margin and a green legend in the instruction (“alternative”, etc.).
  • Alternative guidelines and instructions provide an alternative to what is specified in the immediately preceding guideline or instruction.
  • Optional instructions provide for either:
o   the optional addition of data that supplement what is called for in the immediately preceding instruction, or
o   the optional omission of specific data called for in the immediately preceding instruction.
  • Some instructions are ‘scoped’ as being applicable only to certain types of resources (such as serials).
  • Whether to apply the alternatives, options, or exceptions is cataloger judgment, unless an LC practice has been identified in an LCPS (see next section).

Library of Congress Policy Statements

LC has created an extensive body of Library of Congress Policy Statements (LCPS), to facilitate a standard interpretation and application of these alternatives, options, and exceptions.  Think of these as the ‘RDA version’ of the LC Rule Interpretations. Be sure to consult and follow the LCPS in all such cases. To access the LCPS, click on the green “LCPS” link in the RDA Toolkit. [Note: LCPS is now LC-PCC PS]


Examples

The examples in RDA illustrate the application of the specific instruction under which they appear. They illustrate only the data that are addressed by that instruction. They are normally given without showing the preceding or enclosing punctuation that is prescribed for an ISBD presentation. All examples illustrate elements as they would be recorded by an agency whose preferred language is English.

Examples appear in yellow shading, clearly setting them off from the instructions themselves.



[Source: Library of Congress]

CATALOGING & METADATA BLOGS

Popular blogs devoted to Cataloging and Metadata

Resource Description & Access (RDA)

Resource Description & Access (RDA)

Planet Cataloging

Cataloging – The Library Herald

Organization of Cataloging Units in Academic Libraries

Bibliographic Wilderness

Coyle's InFormation

First thus

Cataloguing Aids Blog

Bib Blog

Books and Library stuff

Cataloging Futures

CILIP Cataloguing and Indexing Group

CCDA

Celeripedean

CommonPlace.Net

ISKO UK

Lorcan Dempsey's Weblog

Metadata Matters

Mod Librarian

The Cataloguing Librarian

Problem Cataloger

The Feral Cataloger

Zepheira

RDA Toolkit Blog

Catalogue & Index Blog

Dublin Core Metadata Initiative

Catalogablog