Every book, journal, map, or digital resource in a modern library carries a hidden layer of structured data that makes it findable. This layer is written in MARC 21, a standard that turns a physical item into a machine-readable record. When you search an online library catalogue and instantly see the author, title, publisher, and subject of a book, you are looking at the visible output of MARC tags working behind the scenes. Understanding how these tags, indicators, and subfields fit together is one of the core skills of practical cataloguing, and it is far less intimidating than it first appears once you break it into parts.
Table of Contents
What MARC 21 actually is
MARC stands for MAchine-Readable Cataloging. It is a standard for representing and communicating bibliographic information, developed and maintained by the Library of Congress in consultation with the MARC Advisory Committee. The “21” signals the harmonised format that merged the older US and Canadian versions for use in the twenty-first century.
The purpose is exchange. A record created by one library can be shared with thousands of others without anyone having to re-type the details. To make that possible, MARC describes a document not in plain sentences but in a coded structure that any compatible library system can read. Instead of storing the words “place of publication” or “name of publisher” in every single record, the format uses short codes to mark each piece of information, which keeps records compact and consistent across systems.
A complete MARC record has three broad parts: the Leader, a fixed 24-character section that carries processing information; the Directory, which lists where each field begins and how long it is; and the variable fields, which hold the actual bibliographic data such as author and title. As an OCLC overview of the format explains, the Leader is fixed in length and always comes first, while the Directory maps out the fields that follow. For everyday cataloguing, most of your attention goes to those variable data fields.
The tagging system
The heart of MARC 21 is its three-digit tag. Every field in a record begins with a number from 001 to 999, and each number has a fixed, agreed-upon meaning. The tag tells the system what kind of information follows. For example, 100 always means a personal name used as the main entry, 245 always means the title statement, and 650 always means a topical subject heading. A cataloguer in Delhi and a cataloguer in Toronto both use 245 for the title, which is exactly why records can travel.
The tags are not assigned randomly. They are grouped into blocks by the first digit, and each block covers a category of information. A teaching guide on major MARC fields describes this grouping clearly: the 0XX block holds identification and classification numbers such as the ISBN and call number, the 1XX block holds main entries like the author, the 2XX block covers titles and publication details, the 3XX block covers physical description, the 6XX block holds subject access, and the 8XX block handles series and holdings. Once you internalise these “neighbourhoods,” you can often guess roughly what a tag does even before you look it up.
Why the structure matters in practice
Because tags are standardised, library software can do useful things automatically. It can pull all the 245 fields to build a title index, gather every 650 to create subject browsing, or sort author entries from the 100 fields. The numbering is the shared language that lets the machine know which piece of data is which, without ever reading the words themselves.
Indicator values
Right after the three-digit tag come two single-character positions called indicators. Indicators are special markers that modify how a tag is interpreted or processed. Each indicator can hold a digit (0-9) or a blank, and the two positions are independent of each other. A blank indicator usually means “undefined” or “no information,” and in printed examples it is often shown with a hash symbol (#) or an underscore so you can see it.
A classic example is the second indicator in the 245 title field, which counts non-filing characters. When a title begins with an article such as “The” or “A,” the catalogue should ignore those letters when alphabetising. So in a record for the book The Robe, the second indicator is set to 4, telling the system to skip the four characters “T-h-e-space” and file the title under “R” instead. The Library of Congress guide to understanding MARC uses this exact example to show how a single digit changes the way data behaves.
Reading indicators correctly
Indicators are easy to overlook because they are just one or two characters, but they carry real meaning. In the 100 personal name field, the first indicator describes the type of name: 0 for a forename, 1 for a single surname, and 3 for a family name. As the Library of Congress 100 field documentation notes, the second indicator in this field is undefined and is left blank. The key habit to build is this: never assume both indicators are blank. Always check what each position means for the specific tag you are working with, because the same digit can mean different things in different fields.
Subfields and delimiters
A single field often contains several distinct pieces of information. The title field, for instance, may hold a main title, a subtitle, and a statement of responsibility all together. To keep these separate, MARC divides a field into subfields, and each subfield is introduced by a delimiter followed by a single-letter subfield code.
The delimiter is a special character that tells the computer a new piece of information is starting. Different systems display it differently, but the most common symbol shown in teaching examples is the dollar sign ($), so you will see codes written as $a, $b, $c, and so on. As a basic MARC terms tutorial explains, the delimiter signals to the system that a different element follows, and within the 245 field, $a marks the title while $c marks the statement of responsibility.
The meaning of a subfield code is tied to its field. In the 245 field, $a is the title proper, $b is the remainder of the title (the subtitle or other title information), and $c is the statement of responsibility. The order matters too. According to the Library of Congress documentation for field 245, once subfield $c has been recorded, no further ordinary subfield coding is possible in that field, because $c marks the end of the descriptive sequence.
Examples of MARC tags
Seeing the pieces assembled makes the system click. Below are four of the most common fields you will meet when cataloguing books, shown with their tag, indicators, and subfields.
Personal name (100)
The 100 field records the personal name used as the main entry, usually the author chiefly responsible for the work. A typical entry looks like this:
100 1# $a Naipaul, V. S., $d 1932-2018.
Here the tag is 100, the first indicator 1 means a single surname, and the second is blank. Subfield $a holds the name in inverted form, and $d holds the dates associated with the person. The field 100 specification confirms that this field is not repeatable, because a record can have only one main entry.
Title statement (245)
The 245 field is the most heavily used field for books. It carries the title and statement of responsibility:
245 14 $a The robe / $c Lloyd C. Douglas.
The first indicator 1 signals that a title added entry should be made, and the second indicator 4 tells the system to ignore the four non-filing characters at the start. Subfield $a holds the title proper and $c holds the author statement.
Publisher details (260)
The 260 field carries the imprint, meaning the publication and distribution details. Its structure is straightforward:
260 ## $a New York : $b Charles Scribner’s Sons, $c 1925.
As set out in the field 260 documentation, $a is the place of publication, $b is the name of the publisher, and $c is the date. In current cataloguing under RDA, many libraries now use the newer field 264 for the same information, but understanding 260 remains essential because countless existing records use it.
Subject headings (650)
The 650 field provides topical subject access, helping users find resources on a particular theme. A subject heading can be broken into a main term and several subdivisions:
650 #0 $a English literature $x 20th century.
Here $a holds the main topical term and $x holds a general subdivision. The second indicator is meaningful: a value of 0 means the heading comes from the Library of Congress Subject Headings, while 2 points to Medical Subject Headings. According to the Library of Congress guidance on subject access fields, other subfields refine the heading further, with $z for geographic subdivisions and $y for chronological ones, so a single 650 field can express a fairly precise subject.
Putting it all together
When you read a full bibliographic record, you are reading a stack of these fields, each one following the same logic: a three-digit tag, two indicators, and one or more subfields introduced by delimiters. The tag names the category, the indicators fine-tune the processing, and the subfields carry the specific data. The format was designed to facilitate the exchange of bibliographic information while staying compatible with other national formats, which is why the same record can move between library systems anywhere in the world. Once you can decode one field confidently, the rest follow the same pattern, and what looked like a wall of numbers becomes a readable description of a document.
What do you think? If you were cataloguing a translated novel with a long subtitle and an editor in addition to its author, which tags and subfields would you reach for first? And how might consistent indicator values change the way readers in your library search for and discover books?
References
- https://www.loc.gov/marc/bibliographic/
- https://www.oclc.org/bibformats/en/about/introduction.html
- https://csi.pressbooks.pub/cataloging/chapter/major-marc-fields-subfields-and-indicators/
- https://www.loc.gov/marc/umb/
- https://www.loc.gov/marc/bibliographic/bd100.html
- https://lili.org/forlibs/ce/able/course8/06terms2.htm
- https://www.loc.gov/marc/bibliographic/bd245.html
- https://www.loc.gov/marc/bibliographic/bd260.html
- https://www.loc.gov/marc/bibliographic/bd6xx.html
- https://loc.gov/marc/96principl.html

Leave a Reply