Tag Info

Hot answers tagged

9

Firstly, you need to know that Managed Metadata Service can be responsible as a Content Type Hub. Content Type Hub is a location where you can manage and publish content type across site collection, web application and farm. One more terminology you need to know is Content Type Subscriber, which will subscribe to Content Type Hub. Once you publish Content ...


3

If I understood the scenario correctly, you have TERM SET called Department that contains TERMS like IT, Economy. In this case you could create new term inside the term set "Department", and name it "SUPPORT". Then you should merge the IT term to the new "SUPPORT" term. Note! This will remove term IT, so you can no longer use IT when you create new ...


2

Finally I achieved it with following code. $navigationSet = $group.CreateTermSet($termsetName) $navigationSet.SetCustomProperty("_Sys_Nav_IsNavigationTermSet", "True") $navigationSet.SetCustomProperty("_Sys_Nav_AttachedWeb_SiteId", $site.ID.ToString()) $navigationSet.SetCustomProperty("_Sys_Nav_AttachedWeb_WebId", $site.RootWeb.ID.ToString()) ...


2

You have to connect to the term store and then construct a TaxonomyFieldValue and then use the target field's SetFieldValue() method to assign the value. See here: http://social.technet.microsoft.com/Forums/da-DK/sharepointadminprevious/thread/4c63fff1-8681-42a1-9fd2-256f1f80935b regards, KS


2

One word: PowerShell Check google or start here http://get-spscripts.com/2010/06/create-new-term-with-synonym-in.html


2

There is a hidden taxonomy list at site collection level which is populated with terms as they are used. The default is for all users to have read access on this list. However, if you start with something like a blank site template and then retro fit MMD then it seems this permission does not always get applied. Navigate to the hidden list at ...


1

I think you want to know about the term set scope, Term set has two scope level Local and Global(read below for more details). Term Set A Term set is a group of related terms. Terms sets can have different scope, depending on where you create the term set. Local term sets are created within the context of a site collection, and are available for use ...


1

Basically selection of submission policy (Open or close) will define whether a user can add new terms in the term store or term store managed by the Managers. Anyone can add a new term to an open term set. For Closed Term set only administrator can add it. Only people who were identified as contributors to a term set group can add terms to a closed term ...


1

I have this little powershell function you can try it out... function SetManagedMetadaService { Param( [parameter(Mandatory=$true)][string]$ServiceName, [parameter(Mandatory=$true)][string]$HubSiteUrl ) Write-Host "Setting contenttype hub Url" #Get-SPServiceApplication | ForEach-Object { # if ...


1

You can change it via PowerShell. See this article: http://www.sharepointanalysthq.com/2010/11/how-to-change-the-content-type-hub-url/ They basically show how to use this cmdlet: Set-SPMetadataServiceApplication -Identity "<ServiceApplication>" -HubURI "<HubURI>"


1

It's completley correct. The GetChildTermsInTermSet method returns a string and not a complex type.


1

To get to those four checkboxes, highlight the MM Service Connection(just below the Managed Metadata Service), and select "Properties" from the ribbon.


1

Run the following PowerShell to find out what the name is of your TermStore asnp Microsoft.SharePoint.PowerShell $tx = Get-SPTaxonomySession -Site http://<yoursiteurl> $tx.TermStores | ft This should list all TermStores available for the MMS SA connected to the Site Coll (for which you provides the URL in the second line)


1

that is an interesting one.. ALthough i don't have an answer on your solution, please keep in mind that your strategy of removing site collection admin permissions from the mySite "owner" will be reverted by some timerjob!


1

There are no way to implement an eventhandler on Managed Metadata terms.


1

I used this tool from Codeplex, and entered in the import CSV the column LCID with german language (LCID=1031). Worked smooth when transferring from SharePoint 2010 to SharePoint 2012 As a hint for german speaking areas, please keep in mind to use Unicode settings and the comma instead the semicolon as list separator, then this works smooth as silked ...


1

Make sure that you have started the Managed Metadata Web Service by going to Central Administration -> Application Management -> Service Applications -> Manage Services on Server. Ideally you need to do this before creating the service application, or you get an error. It needs to be running on at least one server in the farm. If you create the service app ...



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