A thesaurus, in the metadata sense, is a more structured relative of a synonym ring. Where a synonym ring says a set of terms are equivalent, a thesaurus captures multiple kinds of relationship at once: broader term, narrower term, related term, and preferred term versus non-preferred (use\/used-for). That extra structure is what lets a search engine do more than exact matching or flat equivalence.<\/p>
The practical payoff is hierarchical retrieval. If ‘Vehicle’ is defined as the broader term for ‘Truck’, ‘Sedan’, and ‘Motorcycle’, a search for ‘Vehicle’ can be configured to also return assets indexed only under the narrower terms \u2014 without anyone having tagged those assets ‘Vehicle’ directly. That saves indexers from having to apply every level of a hierarchy manually to every asset.<\/p>
ANSI\/NISO Z39.19 is the reference standard for how to build this correctly \u2014 it defines the relationship types, how to pick a preferred term among near-synonyms, and how to document the whole structure so it stays maintainable. That standard is also why a plain folder tree in a DAM isn’t a thesaurus, even though it looks hierarchical: folders encode containment (this asset lives inside this folder) rather than the semantic broader\/narrower and associative relationships a thesaurus is built to express, so a folder structure can’t support the same kind of expanded retrieval.<\/p>","protected":false},"excerpt":{"rendered":"
A controlled vocabulary defining hierarchical (broader\/narrower) and associative relationships between terms \u2014 not just equivalence \u2014 used to guide consistent indexing and searching.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"How does a metadata thesaurus differ from a synonym ring?","answer":"A synonym ring only captures equivalence between terms; a thesaurus captures multiple relationship types at once \u2014 broader term, narrower term, related term, and preferred versus non-preferred (use\/used-for) \u2014 giving it more structure to work with."},{"question":"What does the broader\/narrower relationship in a thesaurus let a search engine do?","answer":"If 'Vehicle' is defined as the broader term for 'Truck,' 'Sedan,' and 'Motorcycle,' a search for 'Vehicle' can be configured to also return assets indexed only under the narrower terms, without anyone tagging those assets 'Vehicle' directly."},{"question":"What standard specifies how a metadata thesaurus should be built?","answer":"ANSI\/NISO Z39.19 defines the relationship types, how to pick a preferred term among near-synonyms, and how to document the structure so it stays maintainable."},{"question":"Is a folder hierarchy in a DAM the same as a thesaurus?","answer":"No \u2014 a folder structure only encodes containment, meaning this asset lives inside this folder, not the semantic broader\/narrower and associative relationships a thesaurus expresses, so it can't drive the 'search broader term, get narrower results too' behaviour a real thesaurus supports."},{"question":"Why does a thesaurus save indexers work compared to manual hierarchy tagging?","answer":"Because a search for a broader term can automatically surface assets tagged only with narrower terms, indexers don't have to apply every level of a hierarchy manually to every single asset."},{"question":"What's an example of the 'use\/used-for' relationship in a thesaurus?","answer":"'Automobile \u2192 USE Car' \u2014 directing a non-preferred term to the preferred term the vocabulary actually indexes under."}],"checked_date":"2026-08-07","sources":[{"statement":"ANSI\/NISO Z39.19 specifies how to formulate descriptors and establish standardized relationships among terms \u2014 broader, narrower, related, and use\/used-for \u2014 for controlled vocabularies including thesauri.","source_name":"NISO \u2014 ANSI\/NISO Z39.19-2005 (R2010)","url":"https:\/\/www.niso.org\/publications\/ansiniso-z3919-2005-r2010","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"related":[2455,2459,2460,2568,2456,2453],"definition":"A controlled vocabulary defining hierarchical (broader\/narrower) and associative relationships between terms \u2014 not just equivalence \u2014 used to guide consistent indexing and searching.","why":"A properly built thesaurus lets a search for 'vehicle' also surface assets indexed only under narrower terms like 'truck' or 'sedan', because the broader\/narrower relationship is explicit in the structure \u2014 something a flat keyword list or a synonym ring can't do. ANSI\/NISO Z39.19 is the standard that specifies exactly how these relationships (broader term, narrower term, related term, use\/used-for) should be built and documented for this purpose.","example_rows":[{"field":"Broader term (BT)","values":"Vehicle"},{"field":"Narrower terms (NT)","values":"Truck, Sedan, Motorcycle"},{"field":"Related term (RT)","values":"Traffic"},{"field":"Use \/ used for (USE\/UF)","values":"Automobile \u2192 USE Car"}],"mistake":"Teams build a folder hierarchy or nested category tree in the DAM and call it a thesaurus, but a folder structure only encodes one relationship \u2014 containment \u2014 with no equivalence or associative links, so it can't drive the 'search broader term, get narrower results too' behaviour a real thesaurus supports.","deep_link":""},"silo":[24],"class_list":["post-2466","glossary","type-glossary","status-publish","hentry","silo-glossary"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2466","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\/2466\/revisions"}],"predecessor-version":[{"id":3586,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/glossary\/2466\/revisions\/3586"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2466"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2466"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}