Category: Metadata Standards

MARC (MAchine-Readable Cataloging)

Also known as: MARC, MAchine-Readable Cataloging, MARC 21

Simply put

MARC, short for MAchine-Readable Cataloging, is a standardized data format for describing library materials such as books in a way that computers can read and share. It originated from an initiative led by the Library of Congress and is used to structure bibliographic records so that information about an item can be stored, exchanged, and displayed consistently. A record built in this format holds descriptive details such as title and statement of responsibility.

Formal definition

MARC is a family of data format specifications for encoding bibliographic and related cataloging information in machine-readable form, developed through a Library of Congress-led initiative. A MARC record is a machine-readable cataloging record structured to carry bibliographic data elements, including areas such as title and statement of responsibility, in a defined format that supports storage and interchange among systems. The current widely referenced variant is generally known as MARC 21. Note that MARC in this recordkeeping and library context is distinct from unrelated uses of the same term, such as the Maryland Area Regional Commuter rail system or the winemaking sense referring to fruit-pressing residue. MARC is primarily a bibliographic description and interchange format and should not be conflated with records management retention or disposition frameworks.

Why it matters

MARC provides a shared structure that allows bibliographic descriptions to move between library systems without each institution having to reinvent how catalog information is encoded. Because it emerged from a Library of Congress-led initiative and has been widely adopted, it has functioned as a common language for describing library materials so that records created in one system can be understood and displayed in another. For anyone concerned with the long-term findability and interchange of descriptive metadata, this kind of standardized, machine-readable format is what enables consistency across catalogs and over time.

For recordkeeping and information governance professionals, MARC is useful as a reference point for understanding how descriptive metadata standards support interoperability, but its scope should not be overstated. MARC is primarily a bibliographic description and interchange format; it is not a records management retention or disposition framework, and it does not by itself address the lifecycle controls, legal holds, or disposition decisions that govern records as evidence of activity. Treating a bibliographic cataloging format as if it were a governance or retention scheme would conflate two distinct concerns.

One practical reason to note the term carefully is that MARC is also used in entirely unrelated contexts, including the Maryland Area Regional Commuter rail system and a winemaking sense referring to the residue remaining after fruit is pressed. In a professional metadata or cataloging setting, the intended meaning is MAchine-Readable Cataloging, and this distinction matters when searching sources or communicating across domains.

Who it's relevant to

Librarians and cataloging staff

Those responsible for creating and maintaining bibliographic descriptions rely on MARC as the format for structuring catalog records so that details such as title and statement of responsibility are encoded consistently and can be exchanged with other systems.

Archivists and metadata specialists

Professionals working with descriptive metadata may encounter MARC as one of the established, machine-readable standards for bibliographic description and interchange, and should understand its scope as a description format rather than a lifecycle or governance tool.

Records managers and information governance officers

For this audience, MARC is chiefly relevant as a point of contrast: it is a bibliographic cataloging and interchange format and should not be conflated with records management retention or disposition frameworks, which address the control of records as evidence across their lifecycle.

Systems and interoperability staff

Those integrating library or catalog systems benefit from understanding MARC because its standardized structure is what allows bibliographic records to be stored, exchanged, and displayed consistently across different platforms that support the format.

Inside MARC

Bibliographic description fields

MARC provides structured fields for describing an item, typically including elements such as title, author or other responsible parties, edition, and publication information, so that catalog records can be created and exchanged in a consistent, machine-readable form.

Field tags and content designation

MARC organizes data into numbered fields, subfields, and indicators that label the meaning of each element. This content designation allows systems to interpret and process the parts of a record rather than treating it as undifferentiated text.

Access points and authority-controlled headings

The format accommodates access points such as names, subjects, and titles that support retrieval. These are often intended to align with controlled vocabularies or authority files, though the degree of control depends on the cataloging practices applied.

Holdings and location information

Depending on the MARC variant and local implementation, records may carry information about physical or electronic holdings, copies, and location, distinguishing the descriptive record of a resource from the specific items held.

Record structure and leader

MARC records generally include structural components, such as a leader and directory, that convey information about the record itself, for example its type and status, enabling systems to parse and validate the record's construction.

Common questions

Answers to the questions practitioners most commonly ask about MARC.

Is MARC a records management standard for controlling records across their lifecycle?

No. MARC is a bibliographic data format used chiefly in library cataloguing to structure descriptive metadata about resources such as books and serials. It is not a recordkeeping standard in the records management sense and does not address lifecycle control, retention, disposition, or the evidential properties that distinguish an authoritative record from other information. Records managers should not treat MARC as equivalent to standards concerned with records as evidence of activity.

Does using MARC mean an organization is managing records rather than merely describing resources?

Not necessarily. MARC provides a way to describe and exchange bibliographic information, but describing a resource is distinct from managing it as a record. A MARC entry is descriptive metadata; it does not by itself establish or maintain the authenticity, reliability, integrity, and usability that characterize an authoritative record. Confusing bibliographic description with recordkeeping can obscure the controls needed for records to serve as evidence.

In practice, where does MARC typically fit within an information environment?

MARC is typically encountered in library and cataloguing contexts, where it structures descriptive metadata to support discovery and exchange between systems. Depending on organizational arrangements, records and information functions may interact with library systems, but MARC generally sits within the descriptive and bibliographic domain rather than within systems designed to control records through capture, classification, retention, and disposition.

How should practitioners relate MARC metadata to recordkeeping metadata requirements?

Practitioners should treat them as serving different purposes. MARC metadata is oriented toward describing resources for discovery and exchange, whereas recordkeeping metadata often needs to capture context, provenance, and the controls that support authenticity and integrity over time. Where the two intersect, it is advisable to map fields deliberately rather than assume that bibliographic description satisfies recordkeeping metadata needs, since the required elements may differ depending on organizational policy.

Can MARC data be reused when materials move into a records or archival context?

Reuse may be possible, but it typically requires careful mapping rather than direct transfer. Descriptive information held in MARC can inform description in other contexts, yet moving materials toward records or archival management often involves additional considerations such as provenance, retention status, and the distinction between an authoritative record, a copy, and transitory information. The extent of reuse depends on the systems and policies involved.

What limitations should be kept in mind when relying on MARC in an information governance program?

The main limitation is scope. MARC addresses bibliographic description and does not encompass the broader accountability concerns of information governance, such as policy, risk, privacy, security, and value, nor the lifecycle controls of records management. Relying on MARC alone would leave these areas unaddressed, so it should be positioned as one descriptive component within a wider framework rather than as a substitute for recordkeeping or governance controls.

Common misconceptions

MARC is a records management format for controlling records as evidence of business activity.

MARC is chiefly associated with library cataloging and bibliographic description of resources. It is oriented toward describing and providing access to catalogued items, which is distinct from the recordkeeping concern of managing records as authentic evidence across their lifecycle. The two domains use the word record differently and should not be conflated.

A MARC record is the same thing as the item it describes.

A MARC record is a structured description or surrogate that stands in for a resource to support discovery and management. It is not the resource itself, nor is it typically the authoritative record of a transaction in the recordkeeping sense. Confusing the descriptive metadata with the object or with an evidential record can lead to errors in scope and control.

MARC is a single fixed standard that behaves identically everywhere.

MARC exists in variants and is implemented within local systems and cataloging conventions, so the fields used, the vocabularies applied, and the treatment of holdings can vary between institutions. Specific structural details and their exact designations depend on the variant and the implementation, and should be verified against authoritative documentation rather than assumed.

Best practices

Be explicit about scope when discussing MARC in a recordkeeping context, distinguishing bibliographic description of resources from the management of records as evidence, so that stakeholders do not conflate the two uses of the term record.

Treat MARC records as descriptive surrogates and maintain a clear link between the description and the resource it represents, rather than assuming the record and the object are interchangeable.

Apply consistent content designation, using field tags, subfields, and indicators as intended, so that records remain machine-readable and can be exchanged reliably between systems.

Support access points with controlled vocabularies or authority files where practicable, and document the cataloging conventions applied, since the degree of authority control depends on local practice.

Distinguish descriptive records from holdings and location information, and record holdings appropriately for the MARC variant and system in use, verifying structural details against authoritative documentation rather than assumption.

Coordinate with records management and information governance functions where library catalog data intersects with organizational recordkeeping, so that responsibilities, retention expectations, and terminology are aligned across the relevant domains and jurisdictions.