Tag Info

Hot answers tagged

6

Terms are the basic unit or smallest item in Managed Metadata or Taxonomy. TermSet is just a collection of Terms.Like say if you want to create a taxonomy for countries and their cities. Country will become the TermSet (eg:England) and cities will be Terms inside respective termsets ie London will be term inside England. Tags are special terms , they are ...


4

The big difference between Keywords and Terms are that Terms are controlled by you (normally) and Keywords are controlled by the users. Sometimes Keywords are referred to as Folksonomy whereas Terms are referred to as Taxonomy. To use Terms to tag a document, create a custom Site Column and map that to a TermSet (which is a collection/hierarchy of Terms), ...


2

It seems it occurs due to the naming conflicts for object termStores If to rename variable termStores to, let's say, termStoreColl, then everything is working just fine. The code below works properly: function getTermStores() { var context = SP.ClientContext.get_current(); var session = SP.Taxonomy.TaxonomySession.getTaxonomySession(context); ...


2

According to a few articles, not all types of columns are available/supported via REST in SharePoint 2010, including managed metadata columns. Not Supported Managed Metadata Managed Metadata (Multi) Publishing HTML Publishing Hyperlink Publishing Image Media Field Summary Links Publishing Image Source: ...


2

Backup and restore the Managed Metadata database as well. Make sure to restore the database with the same name as the existing Managed metadata database to overwrite it. Here is a nice guide: http://sharepointtrac.wordpress.com/2013/10/29/backup-and-restore-managed-metadata-term-stores-sharepoint-2010/


1

Have a look at the TaxonomyItem.NormalizeName method Try changing your code to Term trm = trm1.Terms.GetByName(TaxonomyItem.NormalizeName(parentName));


1

Here is an excellent article that outlines many options Synchronize, Import or Copy Term Stores & Managed Metadata in SharePoint Between Environments Which is best for you depends on your exact requirements. For my requirements I found number 5, the PowerShell cmdlets by Gary Lapointe/Aptillon to be very good. It can export/import most things ...


1

Resolution I sent a support ticket to Microsoft and after a few days of phone calls, we found a resolution. Below is the closing transcript of the issue from Microsoft: Issue Statement: Unable to publish Content Types through Content Type Hubs Scope Agreement: High as customer is not able to use the feature of content types on his production sites ...


1

I don't know if my way is cleaner, but it works. I basically format the term the way SharePoint stores it and then check to see if it already exists. http://nickhobbs.wordpress.com/2012/03/29/sharepoint-2010-managed-metadata-converts-ampersand-and-double-quotes-to-unicode/ //set term the way SharePoint stores it so that we can get a good compare with ...


1

Have you tried to use managed metadata. 1. create a new Global Term Group called Global Navigation. 2. Createjavascript and placed inside Style library folder Function.registerNamespace('Mavention.GlobalNavigation');   Mavention.GlobalNavigation.MenuItem = function(title, url) {     this.title = title;     this.url = url; };   ...


1

The link below explains a similar scenario. http://www.sharepointblogs.be/blogs/timmy/archive/2011/12/01/mui-managed-metadata-vs-search.aspx Accordingly: it depends on what the default language is of your web. Therefore please check if the default language of the web is correctly set to french or if it is a multilingual site, then please select the ...


1

Thanks Waqas. I used PowerShell to export my "term sets" within my TermGroupA as a XML file. This XML will preserve all GUID's for "term sets" and "terms" NOTE: As far as I know it doesn't extract the "term group" GUID (which was fine for me). Grab that XML file, take it to UAT application server and again use PowerShell to create these "term sets" and ...


1

With that many terms, I think it would be better to use External Content Types, rather than MMS term sets. Have you considered that possibility? For one thing, I'd imagine that the relevant data is in a database somewhere, given the volume of items. Using external content types also ensures you're not forced to maintain a large volume of metadata that ...


1

I believe you need to use the term in sharepoint list/library item to get it crawled. Content search web part can pick it up once the term is crawled !


1

We finally found a solution: There is a property in the Field tag; Overwrite="TRUE". If this property is set, it will ignore localization of labels, for some reason that I haven't yet figured out. So when I removed this property completely, it worked just fine. Just SharePoint working as designed, I guess!


1

Was discovered that the port used for the service of Managed Meta Data was already being used by Project Server and this was causing the access issue.


1

I got similar exceptions in farm solutions. Normally error was in one of the following setting: TermStore was changed by admin or there were several TermStores in productive server, so there was a problem getting the right TermStore object Current state of did not send right permissions If you are trying to edit TermStore remote: Be sure all former editing ...


1

I have used the "reuse terms" feature on a site I've done. I think that is the better way if you want the links to remain the same. The other option seems to be Pinning, which keeps the structure but apparently does not keep any of the links.


1

Putting together a taxonomy and managed data plumbing needs some planning & effort. There are a few very practical blog posts that can be helpful - Wictor Wilen's Create SharePoint 2010 Managed Metadata with Excel 2010 Fabian Williams' Understanding Managed Metadata in SharePoint 2010: its Impact on Taxonomy, Navigation and Search (2-part series)


1

Working with taxonomy fields can be tricky... In order to clear a value from a field: $taxField = $item.Fields["metadataField"] -as [Microsoft.SharePoint.Taxonomy.TaxonomyField] $taxFieldValue = $taxField.GetFieldValue(""); $taxField.SetFieldValue($fileItem,$taxFieldValue) $fileItem.Update() In order to set a taxonomy field you essentially need to know ...


1

In SharePoint 2013 Enterprise, I followed the steps above, but it still didn't work. Following on from there, I went to the 'Term Store Management Tool' in Central Admin (/_layouts/15/termstoremanager.aspx) and added the user there too. This resolved the permissions issue for me.



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