{"id":1962,"date":"2012-03-23T06:12:58","date_gmt":"2012-03-23T06:12:58","guid":{"rendered":"https:\/\/poiseddevelopers.com\/reality-tech\/?p=1962"},"modified":"2024-04-26T12:16:10","modified_gmt":"2024-04-26T12:16:10","slug":"taxonomy-site-collection-internals","status":"publish","type":"post","link":"https:\/\/poiseddevelopers.com\/reality-tech\/taxonomy-site-collection-internals\/","title":{"rendered":"Taxonomy Site Collection internals"},"content":{"rendered":"<p>People sometimes run into Managed Metadata Taxonomy fields that show hash signs, semi-colons, numbers; what gives?<\/p>\n<p>What you are seeing, for example in a datasheet view, is a reflection of the internal representation of Taxonomy fields in SharePoint, which admittedly is a bit quirky to show users. It\u2019s our call as solution designers whether to recommend or even expose Datasheet view for end-users.<\/p>\n<p>The small numbers you see associated with metadata fields in datasheet view is the order in which the field value was referenced and first used in your site collection.<\/p>\n<p>Each taxonomy tag is stored internally as three values in one run-on string, with the ;# separating them, and can be seen with debugging tools in a hidden list stored in the root of each site collection:<\/p>\n<p>An internal reference number that is generated and tracked separately within each site collection. Each tag used has a reference number that is going to be different from the same tag in a different site collection<br \/>\nThe text name<br \/>\nThe text name in a language (1033=U.S. English)<br \/>\nA GUID (really long statistically unique identifier) that maps to the same value stored centrally in a Managed Metadata Database associated with the Managed Metadata Service<br \/>\nThe reason for the internal reference number is for SharePoint\u2019s scalability. A Taxonomy could have a million values, and the Managed Metadata Service housing this Taxonomy could have thousands of site collections using this Taxonomy. To avoid a massive bottleneck for Taxonomy lookups, the taxonomy values in use are cached, and every reference to a value carries the small identifier that allows the field to be resolved and referenced without leaving the site collection, avoiding heavy load on the central Managed Metadata Service.<\/p>\n<p>The hidden list is called \u201cTaxonomyHiddenList\u201d stored in the root web of the site collection; it\u2019s not visible in the browser. To see it, try the CodePlex solution called SharePoint Manager\u201d and navigate to the Site Collection.<\/p>\n<p>To learn more about manipulating taxonomies in PowerShell, please see this MSDN article.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>People sometimes run into Managed Metadata Taxonomy fields that show hash signs, semi-colons, numbers; what gives? What you are seeing, for example in a datasheet view, is a reflection of the internal representation of Taxonomy fields in SharePoint, which admittedly is a bit quirky to show users. It\u2019s our call as solution designers whether to [&hellip;]<\/p>\n","protected":false},"author":8,"featured_media":1966,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[62],"tags":[],"class_list":["post-1962","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-taxonomy"],"acf":[],"_links":{"self":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/1962","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/comments?post=1962"}],"version-history":[{"count":1,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/1962\/revisions"}],"predecessor-version":[{"id":1968,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/posts\/1962\/revisions\/1968"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/media\/1966"}],"wp:attachment":[{"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/media?parent=1962"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/categories?post=1962"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/poiseddevelopers.com\/reality-tech\/wp-json\/wp\/v2\/tags?post=1962"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}