We're really loving the ease with which we can add site columns to content types, and have them propagate through all lower-level sites. This is awesome, especially when combined with taxonomy in the term store!
However, our Intranet is to feature a publishing site with subsites to house inter and intra-departmental, private working groups who develop material outside of the public Taxonomy term store and outside of traditional requirements for taxonomy data. This covers a specific area of navigation; the RED HIGHLIGHTED navigation and sub-navigation (not pictured) should all exist without the taxonomy column requirement required of all other sites and subsites.
In building the site template for the Workspaces sites, I want to remove all requirements for all content types for the public-site-wide-taxonomy. However, when I edit the content types at the sub-site level, there seems to be no ability to break inheritance from the parent information, and thus, all content types require the taxonomy column (as defined at the root-site level).
Given the need to remove the site column from all content types, libraries and lists in this Work
View Complete Post