What I'm trying to do is effectively have a document library content type defined at the site collection level, I then want sites within the Site Collection to be able to edit the defaults for the fields on a site by site basis.
The only way I've been able to remotely get this to work is to create a base content type at the site collection level (without fields that defaults are required), then a new inheriting content type at the site level with the added columns and defaults set. Now this works fine for the site I'm creating and even kind of works if I template the site and create a new site from the template in so much as it all seems to work, except on the site created with the template the custom content type isn't created, instead it just has the columns added and not the custom type so I can't change the defaults at the newly created site level.
The client basically wants a content type that will be applied to all document libraries in a Site Collection, but that they can edit at a site level to affect all document libraries in the site and then further customize on specific document libraries if required. They also want to be able to change the 'original' content type if required and have those changes cascaded down to all sites and sub sites etc.
Anyone got any advice on how to achieve this?