Hot answers tagged

4

Groups define security boundaries. A group is a set of term sets that all share common security requirements. Only users who are designated as contributors to a specific group can manage term sets that belong to the group or create new term sets within it. Organizations should create unique groups for term sets that will have unique access or security needs. ...


3

Synonyms in Managed Metadata are completely unrelated to synonyms in a thesaurus for Search. You could write a PowerShell script that read the MMS terms and created a formatted thesaurus then periodically Imported/Updated the search thesaurus. In one step traverse your term set and write a thesaurus file in the format: Key,Synonym,Language IE,...


3

When you create you're the second site collection in your fresh Web Application, it typically comes with additional sites in the URL. It doesn't affect the user unless she wants to type the URL directly. The reason for this as that we use a managed path of wildcard inclusion. With wildcard inclusion, you are able to have as many site collections you want (...


2

You can set property of term set as "Open" which will let anyone add a new term to an open term set. So user not necessarily need to go to the path mentioned above. In list/library while selection of term user can provide new terms as well. (same like allow fill in choices for choice field) refer MSDN


2

You may need to recreate the Term Set again. Navigate to http://portal/services/_layouts/15/AreaNavigationSettings.aspx directly or navigate through Site Settings: Make sure you have selected Managed Navigation radio button. Click on Create Term Set and check if that solves the problem. Here is my view from the Services AreaNavigationSettings page:


1

Self answering questions; just wait for a while then it's working properly!


1

You'll need to specify a term set as open to users to be able to add new terms, see https://support.office.com/en-us/article/Introduction-to-managed-metadata-a180fa28-6405-4679-9ec3-81d2028c4efc In addition, you can configure a term set as closed or open. In a closed term set, users can't add new terms unless they have appropriate permissions. In an open ...


1

If you need just a flat list of all terms inside a TermSet you can use GetAllTerms() method. TermCollection terms = termSet.GetAllTerms(); foreach (var t in terms) { Console.Write(t.Name); } EDIT: If you want to preserve the hierarchy , you have to loop through each term as below: TermSet termSet = group.TermSets["MyTermSet"]; TermCollection terms =...


1

SharePoint 2013 does not support managing term set using REST API still now. In that case, JSOM is the one and only way. If your requirement is just to read the term set, then you can follow this. module.getTermSet = function (id, callback) { SP.SOD.loadMultiple(['sp.js'], function () { // Make sure taxonomy library is registered ...


1

Even though the Group Managers description states "Enter user names, group names, or e-mail addresses in order to grant group manager permissions", you cannot use a SharePoint group. From TechNet: SharePoint Group[s are] defined at [the] Site Collection Level while [the] Term Store is defined at [the] Farm Level. Active Directory groups can be used, ...


1

Your best bet is using powershell script to export and import the term set as Paul mentioned. Here are script. To Export Add-PSSnapin Microsoft.SharePoint.Powershell $metadataApp= Get-SpServiceApplication | ? {$_.TypeName -eq "Managed Metadata Service"} $mmsAppId = $metadataApp.Id $mmsproxy = Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "Managed ...


1

Go for the export and import of the term set and then fix the existing items with a PowerShell script. The script should lookup the term in the term store given the text of an old term. Then it should assign the correct term with a new id. Hope it does make sense. I have a PowerShell script for that and if noone else posts an answer, I will upload it here ...



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