Reference Glossary
Metadata crosswalk
A field-by-field table showing which element in one metadata schema corresponds to which element in another, used to convert or exchange records between systems built on different schemas.
Why it matters in a DAM
A DAM rarely lives in isolation — it needs to exchange records with library catalogs (MARC), museum systems (VRA Core, CDWA), or the open web (Schema.org), and none of those schemas line up field-for-field with a DAM's internal schema. Official crosswalks, like the Library of Congress's published Dublin Core-to-MARC mapping, exist precisely because this translation is common enough and error-prone enough to standardize rather than reinvent per project.
A worked example
Common mistake
Assuming a crosswalk is always one-to-one. Schemas differ in granularity — VRA Core allows multiple typed 'agent' roles (photographer, engraver, architect) where Dublin Core has one flat 'Creator' — so a naive crosswalk collapses distinct information into a single field and can't be reversed without loss.
A metadata crosswalk is a translation table, not a piece of software: it documents, element by element, how a record in one schema should be converted into another. The best-known example in library and archive contexts is the Library of Congress’s Dublin Core to MARC crosswalk, which maps each of Dublin Core’s 15 elements to specific MARC 21 bibliographic fields — and, in the reverse direction, maps MARC fields (which are far more granular) down to Dublin Core, discarding detail that unqualified Dublin Core has no room for.
That asymmetry is the core challenge of any crosswalk: converting from a richer schema to a simpler one is straightforward but lossy, while converting from a simpler schema to a richer one leaves many target fields unfillable. A DAM importing records from a MARC-based library catalog gains detail it may not have fields for; a DAM exporting to a Dublin-Core-only repository has to decide which of its own richer fields get folded together or dropped.
In DAM practice, crosswalks matter most at three points: migrating from a legacy DAM to a new one, federating search across a DAM and an institutional repository, and publishing assets to a partner or aggregator with its own required schema. Building the crosswalk before the migration or integration begins — rather than mapping fields ad hoc during the process — is what prevents silent data loss, since a crosswalk gap doesn’t throw an error; it just leaves a field empty.
Frequently asked
What is a metadata crosswalk?
A field-by-field table showing which element in one metadata schema corresponds to which element in another, used to convert or exchange records between systems built on different schemas.
Why do DAMs need crosswalks at all?
A DAM rarely lives in isolation — it needs to exchange records with library catalogs (MARC), museum systems (VRA Core, CDWA), or the open web (Schema.org), and none of those schemas line up field-for-field with a DAM's internal schema.
Are crosswalks something teams typically build from scratch?
Not always — official crosswalks, like the Library of Congress's published Dublin Core-to-MARC mapping, exist precisely because this translation is common enough and error-prone enough to standardize rather than reinvent per project.
What's the risk of assuming a crosswalk is always one-to-one?
Schemas differ in granularity — VRA Core allows multiple typed 'agent' roles (photographer, engraver, architect) where Dublin Core has one flat 'Creator' — so a naive crosswalk collapses distinct information into a single field and can't be reversed without loss.
What does it mean for a crosswalk to lose information during conversion?
When a richer schema's multiple distinct fields all get mapped down into one simpler field in the target schema, the original distinctions can't be recovered afterward, even if the data technically still exists in some form.
What's an example of an official, standardized crosswalk?
The Library of Congress's published Dublin Core-to-MARC mapping, created because the translation between those two schemas is common and error-prone enough to be worth standardizing centrally.
Sources
- The Library of Congress publishes an official Dublin Core to MARC crosswalk mapping each Dublin Core element to specific MARC 21 bibliographic fields. checked 2026-08-07 — Library of Congress: Dublin Core to MARC Crosswalk
- Because MARC is richer in data elements than Dublin Core, the MARC-to-Dublin-Core direction maps multiple MARC fields onto a single Dublin Core element. checked 2026-08-07 — Library of Congress: Dublin Core to MARC Crosswalk