Dublin Core is a metadata standard of fifteen general-purpose descriptive elements, title, creator, subject, date, and so on, designed to describe almost any kind of resource. It is not specific to images the way IPTC is; it is broader and simpler, which makes it a common interoperability baseline.
Why it matters
Standards make metadata portable. Mapping your fields to a recognized standard like Dublin Core or IPTC means information survives migrations and exchanges cleanly between systems instead of being trapped in one platform.
How it shows up in practice
A library or archive describing mixed content, documents, images, datasets, often uses Dublin Core because its elements apply across types. Many DAMs map custom fields to Dublin Core or IPTC behind the scenes so exports and integrations stay standards-compliant.
Common mistakes
- Inventing proprietary fields when a standard element already fits.
- Assuming one standard covers every need, rather than combining where useful.
- Mapping to a standard once and never validating that exports preserve it.
Stacks covers standards within its metadata guide.