RDA: Resource Description and Access¶

Apply a governed, IFLA-LRM-aligned framework of entities, elements, relationships, recording methods, and policy choices to create reusable library and cultural-heritage metadata without binding that metadata to one encoding format.

Version: v2 · 2026-09-06 · History
Domain-specific #: 2660
Origin domain: library and information science
Subdomain: resource description and bibliographic control
Aliases: Resource Description and Access, RDA

Core Idea¶

RDA: Resource Description and Access is a governed framework standard for creating library and cultural-heritage metadata. It tells a metadata creator or application how to identify the entities being described, select applicable RDA elements, record attributes and relationships through permitted methods, and apply declared options or community policies so that the resulting metadata supports resource discovery and identification.

RDA's official description is deliberately broader than “cataloging rules for books.” It is a package of data elements, guidelines, and instructions designed for metadata that is well formed according to international models and usable in user-focused linked-data applications. The current official RDA implements the IFLA Library Reference Model (LRM), including entities such as Work, Expression, Manifestation, Item, Agent, Person, Nomen, Place, and Timespan, with RDA-specific refinements.

Scope of Application¶

RDA's home domain is descriptive cataloging and bibliographic control in libraries, with intended use across cultural-heritage communities. It applies to monographs, serials, integrating resources, music, moving images, maps, archival or museum resources where an adopting community has defined a suitable application, digital resources, and authority data for persons, corporate bodies, families, works, and other entities.

The standard operates at several layers. Catalogers use it to record statements found on a manifestation, distinguish editions, identify creators and contributors, relate translations to works, and construct or select access data. Metadata designers use RDA Reference to build application profiles and validate element usage.

Clarity¶

Six questions make an RDA claim auditable.

Which RDA version and profile? State official or original RDA, release context where relevant, and the community application profile or policy statements. 2. Which entity is described? Do not place a Work statement on a Manifestation or treat a physical Item characteristic as universal to an edition. 3. Which RDA element applies? Use the element's domain, definition, and scope rather than an approximate natural-language label.

Manages Complexity¶

Cultural-heritage resources generate recurring ambiguities: intellectual content versus physical carrier, original work versus translation, edition versus individual copy, a person versus the names used for that person, a title as transcribed versus a constructed access string, and a relationship versus a display phrase. RDA supplies an entity-and-element framework that makes these distinctions explicit and repeatable.

Abstract Reasoning¶

The abstraction licenses practical inferences.

If two statements use the same visible label but have different RDA element IRIs or entity domains, they are not semantically interchangeable.
If a resource changes carrier while its intellectual content remains the same, at least the Manifestation changes; whether Work or Expression changes depends on the content and expression evidence, not the file extension alone.
If a catalog switches from MARC to RDF while preserving RDA element semantics and values, the encoding changes without necessarily changing the descriptive standard.
If a local policy makes an optional RDA element mandatory, failure to record it violates that application profile even if the unconstrained RDA framework would permit omission.
If two agencies both say “RDA” but use different Toolkit versions, profiles, vocabularies, or string schemes, interoperability cannot be inferred from the label alone.
If an RDA relationship is recorded only as an uncontrolled display phrase, a human may understand it while a machine cannot safely infer the canonical predicate or inverse.
If a record contains a MARC field that can map to several RDA elements, migration requires context and policy; field-to-element substitution is not automatically one-to-one.
If an entity-boundary decision is wrong, adding more accurately transcribed attributes will not repair the description's identity structure.

Knowledge Transfer¶

RDA transfers literally across libraries and related cultural-heritage settings when the same entities, elements, recording methods, and implementation controls are used. A cataloger describing a score, map, film, e-book, or archival publication may encounter different evidence, yet can apply the same distinction between Work, Expression, Manifestation, Item, Agent, and Nomen and record relationships through governed elements.

The standard also transfers between human cataloging and machine-supported workflows. A human may follow Toolkit guidance to choose an element and value; a software application may validate RDF properties against RDA domains and ranges.

Relationships to Other Abstractions¶

Current abstraction RDA: Resource Description and Access Domain-specific

Parents (1) — more general patterns this builds on

RDA: Resource Description and Access presupposes Standardization Prime

Standardization is the minimal live parent relation.

Hierarchy path (1) — routes to 1 parentless root

RDA: Resource Description and Access → Standardization

Neighborhood in Abstraction Space¶

RDA: Resource Description and Access sits in a sparse region of the domain-specific corpus (88^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08