Hot answers tagged

2

One reason to beware of many content types is the impact it has on general site collection creation times. Each time a new site collection is created, all syndicated content types in connected hubs are copied down to it. So the more content types you have the slower it becomes to create site collections. In our staging environment, we found that once we ...


2

So if this is happening to you you should first publish your content type, at your content type hub. From there you should click "Manage publishing for this content type" and you will see 3 options: Publish Make this content type available for download for all Web Applications (and Site Collections) consuming content types from this location. Unpublish ...


2

Couple of things to check: Make sure that MMS proxy associated with the web app.( Central admin > Application management > web app and from ribbon select service connection) Also check if MMS services is running on at least one server in the farm.( Central admin > Managed Services on server.) Also browse the MMS from central admin and see if it working ...


2

You would need to create a site collection scoped feature that would create them and add them to the content type gallery if you are not going to use a content type hub. This makes upkeep much more complex, so I'd encourage the use of a hub if possible.


2

The Content Type Hub will not be visible in the sitecollection listing. But however you can access it from https://mydomain.sharepoint.com/sites/contentTypeHub


1

it is not visible but default content type is their and can be access via site collection named /sites/contentTypeHub. But here is one issue. only the original Office 365 account creator has access to the site collection. Accessing it with another user will get you an access denied error message even if you are a global administrator. fix: Unfortunately, ...


1

This is how i fixed it. In Central Admin > Manage Service Applications > Managed Metadata Service (The Service Connection, not just the service) > Highlight and Click Properties. At this point you have 4 check boxes. This service application is the default storage location for Keywords. This service application is the default storage location for ...


1

Lookup columns will only lookup data in lists in the same site/web. When the content type hub functionality deploys your content type to other sites, the lookup list does not exist there, so the column is removed. The best way to do this is to use a managed metadata term set instead. The term set is globally available to all site collections. So you can add ...


1

Alternatively, you can provision your lookup column with a feature receiver everytime you create a new website. You just need to make sure you have the lookup list available somewhere (which, by the way, CAN BE in a different web site). There is a quick and easy to implement guide which you can find here: ...


1

I think it would be best to have them follow a standard naming convention for the Content Type names, like VendorName(or abbrev) Document, VendorName Project, etc and use separate groups. They could then use a singular CT hub and would reduce collisions. This gives total visibility to everyone and can help with governing it too. I would fear that if it was ...


1

Your interpretation is correct. A Managed Metadata Service application can be used to share content types across site collections by associating a Content Type Hub with it. A content type hub site is generally created as it's own site collection and is purely used to store custom site columns and content types and publish these to subscribing site ...


1

I think that's the default behavior of publishing content types (as a whole, I think that's the idea), I don't know a way to publish the content type excluding columns, so my recommendation is unsubscribe your special subsite from the Content Type Hub or everytime you publish your content type it'll erase your special choices and you'll have to recreate it ...


1

From an administrative and cost savings perspective, this makes total sense. I'd try make sure that each of the old farms has their own host name to give them the feeling nothing has changed regardless of where the farm and content resides. The biggest barrier that you said is really the organizational and political aspect. It is technically possibly to ...


1

Their is no OOTB way to merge the two Content Type Hub. Rather you can think about manually moving the Content type from one Farm to other and then republish them. check these resources for more idea: http://www.balestra.be/2012/09/content-type-hub-limitations-in-sharepoint-2010.html ...


1

The answer depends in large part on who is in charge of managing content types. Or, am I really just rephrasing your question? If the creation and management of content types is in the hands of a business user, then the manual labor approach, while potentially problematic, is fine. IT folks may flinch at this strategy, but but not every company has the IT ...


1

Two things to make sure: Make sure you have published the content types in the hub (as described here) Run the timer job called "Content Type Hub Subscriber" for the web application that the site you want the content type on belongs to from Central Adminstration. Note: This is not possible in Office 365 (SharePoint Online), since you can not manually run ...



Only top voted, non community-wiki answers of a minimum length are eligible