MARC, short for Machine-Readable Cataloging, is a standardized data format for encoding bibliographic records so that different library systems can exchange catalog data consistently, developed by the Library of Congress beginning in the 1960s as one of the earliest applications of computing to library cataloging.
A MARC record represents each piece of bibliographic information, such as the title, author, or subject headings, in a numbered field, with further subfields distinguishing specific components within that field, such as separating a main title from a subtitle. This rigid, well-defined structure allows software from different vendors to reliably parse and display MARC records consistently, regardless of which system originally created the record.
Historical Significance
MARC fundamentally transformed library cataloging by enabling the distribution of catalog records between institutions, allowing libraries to share cataloging work rather than each library creating original records for the same commonly held items independently, which dramatically reduced the overall labor required to catalog widely held publications across many libraries.
Structure and Fields
MARC fields are organized by broad categories, with number ranges designated for different kinds of information, such as fields for title and edition information, fields for subject access points, and fields for added entries representing additional contributors. Catalogers and systems librarians must understand this numeric field structure to correctly interpret or edit MARC data.
Transition Toward Newer Formats
Despite its age, MARC remains deeply embedded in library systems worldwide, though the library community has increasingly explored newer, more flexible data models better suited to linked data and web-based discovery, with transition efforts proceeding gradually given the enormous installed base of MARC-dependent systems and the substantial cost of fully replacing them.
Economic Considerations
Access to shared MARC record pools through bibliographic utilities typically involves subscription or per-record fees, which libraries weigh against the substantial labor savings of downloading an existing record rather than creating original cataloging for every commonly held publication independently.
International Perspectives
MARC has been adapted into national variants in a number of countries to accommodate local cataloging rules and language requirements, while international cooperation efforts have worked to keep these variants close enough to the core standard that records remain reasonably exchangeable across different national MARC implementations.
Practical Guidance
Systems librarians working with MARC data are generally advised to validate records against the format specification before bulk-loading them into a catalog, since malformed MARC data can cause display errors or broken search indexing that may not become apparent until patrons encounter the problem directly.
Related Specialties
Working with MARC data effectively combines cataloging knowledge with systems librarianship skills, since troubleshooting display or indexing problems often requires understanding both the correct bibliographic content of a field and the technical way a particular integrated library system interprets and renders MARC-encoded data.
Looking Ahead
Discussion within the cataloging community about eventually moving beyond MARC toward more flexible, linked-data-friendly data models continues, though any full transition would require coordinated change across an enormous number of interdependent systems, making gradual, incremental evolution more likely than an abrupt wholesale replacement of the format.
Shared Bibliographic Utilities
MARC records are widely exchanged through shared bibliographic utilities, cooperative databases that pool catalog records contributed by many member libraries, allowing a library to search for and download an existing record created elsewhere rather than originating one independently. This cooperative model, enabled directly by the common MARC structure, has dramatically reduced the duplicated cataloging effort that would otherwise occur if every library had to describe the same widely held publications entirely on its own.
Participation in these shared utilities typically involves membership fees and adherence to shared quality standards, reflecting the collective governance required to keep a cooperative cataloging resource of this scale functioning reliably for all member libraries.
Encoding Special Characters and Scripts
MARC supports encoding for a wide range of writing systems and special characters, which matters considerably for libraries cataloging multilingual collections, though handling non-Latin scripts correctly requires careful attention to character encoding standards to avoid display errors across different systems.
Libraries serving multilingual communities must therefore ensure their systems and staff correctly handle these encoding requirements, since a mishandled script can render titles or names unreadable even when the underlying MARC record itself is otherwise complete and accurate.
Local Customization Within MARC
While MARC defines a shared standard structure, individual libraries often use certain fields for locally defined purposes, such as recording local item notes or holdings information, meaning not every MARC field carries identical meaning across every implementing institution despite the shared underlying format.
Awareness of this local variation matters particularly when migrating data between different library systems, since fields used informally at one institution may not carry the same meaning, or may be absent entirely, within another library records.
Clear internal documentation of any locally customized field usage therefore remains an important practice for libraries hoping to migrate their catalog data smoothly to a new system in the future.
Systems librarians who maintain this documentation carefully tend to encounter far fewer surprises during a system migration than those who discover undocumented local customizations only after data has already been transferred.
A small amount of documentation effort now can save considerable troubleshooting time down the road.
Many systems librarians maintain a simple shared wiki or reference document specifically for this purpose within their own institution.
Keeping this reference updated as conventions change is a small but meaningful part of good systems stewardship.
Even brief notes recorded at the time a local field convention is adopted can save considerable confusion for whoever manages the system years later.
Key facts
- Array
Quick checkWhat problem was the MARC format originally created to solve?Show answer
MARC was created to let libraries represent bibliographic records in a consistent, machine-readable structure, so that catalog data could be exchanged between different library systems and processed automatically by computers rather than requiring manual re-entry.
Sources
- Array
Editorially reviewed by Specialty Digest Editorial TeamLast reviewed November 3, 2026Researched and drafted with AI assistanceReport an issue