Hey fellow librarians and catalogers!
If you’ve opened a new Library of Congress record in the past few weeks and thought, “Wait… this looks a little different,” you’re not imagining it. On March 24, 2026, the Library of Congress quietly rolled out what they’re calling “Modern MARC” — a smarter, cleaner way of creating bibliographic records that finally brings MARC up to speed with RDA and the linked-data world we’re all heading toward.
Don’t worry — this isn’t a massive overnight overhaul that’s going to break your workflows. It’s a gradual, organic shift that only affects new records LC catalogers create or heavily edit. No big retrospective conversion. No panic. Just smarter records moving forward.
I’ve read the full LC announcement so you don’t have to, and I’ve broken everything down in plain English. Whether you’re a solo cataloger in a small academic library or part of a big technical services team, here’s exactly what’s changing and why it actually makes our jobs easier in the long run.
Why Is LC Doing This Now?
MARC has been around since 1968 — that’s almost 60 years! Back then it was revolutionary, but over time we kept layering new rules on top of old ones (AACR → AACR2 → RDA). The result? A lot of redundant data that catalogers have to type twice and computers have to process twice.
RDA (Resource Description & Access), which we’ve been using since 2010, prefers clear text over cryptic codes and loves identifiers (those web-like URIs) that make records ready for linked data and BIBFRAME.
LC has decided it’s finally time to stop carrying all that extra baggage. Starting now, their new records will be leaner, more consistent, and future-proof — while still being 100% valid MARC.
Important note: Vendor records, copy-cataloged records, and PCC records have already been doing many of these things for years. LC is simply catching up and making it official policy.
The 8 Big Changes You’ll Start Seeing in New LC Records
1. Less “Coded” Data, More Plain-English Text
Remember those mysterious fixed fields like 007 and 006? LC will now rely much less on them.
Instead, they’ll use the 3XX fields (especially 340, 337, 338) that were created for RDA. Example Old way (coded): 007 kd#bc| New way (textual): 340 ## $a cardboard $d collotype $g black and white
Catalogers already know these fields — now LC will use them consistently.
2. More Identifiers & URIs (The Linked-Data Upgrade)
RDA loves identifiers, and so does the future of cataloging. You’ll see a lot more $0 URIs in new records.
To keep things clear, LC will repeat fields instead of cramming multiple values into one: 340 ## $a cardboard $0 http://id.loc.gov/vocabulary/mmaterial/crd 340 ## $d collotype $0 http://id.loc.gov/vocabulary/mproduction/collo
This feels a bit repetitive at first, but it removes ambiguity and makes records much more powerful for discovery systems.
3. Goodbye to Unnecessary Duplication
During the transition, you might still see some overlap between old fixed fields and new 3XX fields, but LC is actively reducing it. The goal is one clear description, not two.
4. Minimal ISBD Punctuation (PCC Style)
Full ISBD punctuation will now be limited mostly to the 245 and 264 fields. Other fields will use minimal punctuation, just like PCC has been encouraging for years. Leader/18 will be coded “i” (ISBD punctuation included).
5. Better Support for Non-Latin Scripts + BCP47 Codes
LC is expanding non-Latin script handling. You’ll start seeing BCP47 language/script codes (those short codes like ko for Korean or en for English) in the $7 data provenance subfield of 880 fields and sometimes their romanized pairs.
This small addition gives computers much better information about what language and script they’re looking at — super useful for multilingual collections.
6. Cleaner Provision Statements (264 Fields)
No more cramming multiple publication statements into a single 260 field. Each statement (production, publication, distribution, manufacture) now gets its own 264 field with the correct indicator. This matches RDA much more naturally.
7. Series Statements (490) Get Their Own Fields Too
When you have a main series + subseries, or a series title + parallel title, each one will now live in its own 490 field instead of being jammed together.
8. Big Change to Subject Headings: No More LCSH Form Subdivisions ($v)
This is probably the change that will feel most noticeable.
Starting in new records, LC will stop adding genre/form subdivisions ($v) to LCSH strings (because many of those combinations don’t have clean linked-data URIs).
Instead, they’ll assign a separate 655 field using LCGFT (Library of Congress Genre/Form Terms) to describe what the item is.
Example Old: 650 #0 $a Mystery fiction $v Comic books, strips, etc. New: 650 #0 $a Mystery fiction. 655 #7 $a Graphic novels. $2 lcgft
This makes our subject data cleaner and far more compatible with linked data.
What Does This Mean for Your Library Right Now?
- New records coming from LC will look a bit different starting now.
- Legacy records are untouched — no retrospective conversion.
- Your ILS and discovery layers should handle these changes fine because most of these practices are already common in vendor and PCC records.
- If you do copy cataloging or NACO/PCC work, you’re probably already familiar with most of these styles.
The Bright Side
Yes, there’s a small learning curve. But the payoff is huge:
- Less typing of redundant data
- Cleaner, more consistent records
- Better preparation for BIBFRAME and linked data
- Records that actually work better in modern discovery systems
As the announcement says, “these practices can already be observed in LC distributed records and in the broader library community.” LC is simply making it official.
Final Thoughts
Cataloging has always evolved — from AACR2 to RDA, from print cards to MARC, and now from traditional MARC to “Modern MARC.” This change feels like the natural next step toward records that are both human-readable and machine-smart.
If you’re feeling a little overwhelmed, you’re not alone. Most of us have been quietly doing many of these things already. The Library of Congress is just catching the rest of the community up.
Have you started seeing Modern MARC records in your workflow yet? Drop a comment below — I’d love to hear what’s showing up in your catalog and how it’s landing for your team.
Happy cataloging, everyone! We’ve got this.