{"id":2449,"date":"2026-08-08T01:46:10","date_gmt":"2026-08-07T22:46:10","guid":{"rendered":"https:\/\/picajet.com\/articles\/glossary\/structured-metadata\/"},"modified":"2026-08-08T03:46:43","modified_gmt":"2026-08-08T00:46:43","slug":"structured-metadata","status":"publish","type":"glossary","link":"https:\/\/picajet.com\/articles\/glossary\/structured-metadata\/","title":{"rendered":"Structured metadata"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Whether a metadata field counts as structured depends on the field definition, not the DAM platform generally \u2014 the same system can hold a rigorously structured &#8220;Usage Rights&#8221; dropdown alongside a completely free-text &#8220;Notes&#8221; field. Structure is a property of the individual field: a defined data type (date, number, single-select, multi-select) with, ideally, a controlled vocabulary constraining what values are allowed.<\/p>\n<p class=\"wp-block-paragraph\">The payoff for structure is machine reliability: a structured date field can be sorted chronologically and filtered by range without ambiguity, while a free-text date typed as &#8220;March 2026,&#8221; &#8220;03\/2026,&#8221; or &#8220;early spring 2026&#8221; defeats any of that. This is why DAM implementations spend disproportionate effort structuring a small number of high-value fields \u2014 rights status, expiration date, approval state \u2014 even when the bulk of an asset&#8217;s description stays as free-text caption or notes.<\/p>\n<p class=\"wp-block-paragraph\">Structured metadata is also what most downstream integrations depend on. A PIM, CMS, or e-commerce platform pulling assets via API typically expects specific structured fields in specific formats; unstructured description, however rich, generally can&#8217;t be consumed programmatically without extraction \u2014 which is where structured and unstructured metadata increasingly meet through AI-assisted tagging.<\/p>","protected":false},"excerpt":{"rendered":"<p>Metadata stored in discrete, typed fields \u2014 a date field, a controlled picklist, a number \u2014 that software can reliably query, filter, and validate, as opposed to free-text description.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"What makes metadata structured rather than free text?","answer":"Structured metadata is stored in discrete, typed fields \u2014 a date field, a controlled picklist, a number \u2014 that software can reliably query, filter, and validate, as opposed to a sentence of free-text description."},{"question":"Why does faceted filtering depend on structured metadata specifically?","answer":"A filter like 'Rights: Cleared AND Format: Vector' only works if 'Rights' is a defined field with a fixed set of possible values, not a sentence someone wrote. The moment the field becomes free text, that filter breaks silently."},{"question":"Why can free-text values silently break a filter?","answer":"Because 'cleared for use,' 'OK to use,' and 'rights cleared' all mean the same thing to a person but are three unrelated strings to a database query \u2014 a structured field with a fixed value avoids that fragmentation entirely."},{"question":"What's the risk when migrating free-text captions into a field labeled structured?","answer":"Teams sometimes migrate legacy free-text captions into a schema field labeled as structured without actually mapping the values into that field's defined option set. The field looks structured in the interface, but it still holds inconsistent free-text strings underneath, so filtering on it silently returns incomplete results."},{"question":"Does labeling a field structured in the interface guarantee the data inside it is structured?","answer":"No \u2014 as above, a field can be presented as structured while still holding unmapped free-text values underneath, because the migration never converted the actual data into the field's defined options."},{"question":"What's an example of a structured field commonly used for DAM filtering?","answer":"A rights-status field limited to a fixed set of values like 'Cleared,' 'Restricted,' or 'Expired' is a typical example \u2014 its value set is controlled, so a search filter on it returns reliable, complete results every time."}],"checked_date":"2026-08-07","sources":[],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2396,2505,2504,2580,2408,2394],"definition":"Metadata stored in discrete, typed fields \u2014 a date field, a controlled picklist, a number \u2014 that software can reliably query, filter, and validate, as opposed to free-text description.","why":"Structured metadata is what makes faceted filtering in a DAM work at all: a filter for \"Rights: Cleared AND Format: Vector\" only functions if \"Rights\" is a defined field with a fixed set of possible values, not a sentence someone wrote. The moment a field becomes free text, that filter breaks silently \u2014 \"cleared for use,\" \"OK to use,\" and \"rights cleared\" all mean the same thing to a person but are three unrelated strings to a database query.","example_rows":[{"field":"Rights Status (structured, picklist)","values":"Cleared \/ Pending \/ Expired"},{"field":"Date Captured (structured, date type)","values":"2026-03-14"},{"field":"Caption (unstructured, free text)","values":"\"Shot on location, cleared for use through end of Q3\""}],"mistake":"Teams migrate legacy free-text captions into a schema field labeled as structured without actually mapping the values into that field's defined option set \u2014 the field looks structured in the interface, but it still holds inconsistent free-text strings underneath, so filtering on it silently returns incomplete results.","deep_link":""},"silo":[24],"class_list":["post-2449","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2449","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/glossary"}],"version-history":[{"count":3,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2449\/revisions"}],"predecessor-version":[{"id":3629,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2449\/revisions\/3629"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2449"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}