Tag Info

Hot answers tagged

5

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), ...


3

Radu Tut wrote the post Managed Metadata Navigation for Multiple Site Collections in SharePoint 2013, stating: "When you try to bind the same navigation term set to a new site, you will get a message that says the term set is already bound to a different site, and if you choose to proceed, the navigation settings for the other site will be broken." I don't ...


3

Term store (database) is identified by you managed metadata service, and you choose the name of your service upon creation in Central Admin. I have my own descriptive name in my development environment: You can also see the name in Central Administration > Manage service applications (in Application management section) > Highlight Managed Metadata Servie ...


2

In this case I would recommend you to add the new department names to the manage metadata store and merge the old departments with the new values. You shoul check out the following blog post http://term-management.com/2012/10/11/merging-terms-in-the-sharepoint-2010-term-store-2/


2

In order to add term under a any parent term, you should be needing two things: The Term store ID and relevant Term set The Parent Term ID (to which the new child term will be added) The update code will be following: function execOperation() { //Current Context var context = SP.ClientContext.get_current(); //Current ...


2

Did you run your power shell as run as administrator ? If still the problem persists, then Run the powershell with the user which has full admin rights. Also sometimes The error is caused by an incorrect “TermsStore administrator account”. To resolve the issue: •Go the Central Administration •Go to : “Manage service applications” ( ...


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

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

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

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

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

To get the peer page of the page that you are currently in Use the below method:- ReadOnlyCollection<VariationLabel> spawnedLabels = Variations.Current.UserAccessibleLabels; foreach (VariationLabel label in spawnedLabels) { try { if (!currentUrl.StartsWith(label.TopWebUrl, ...


1

In order to use a Term Store in SharePoint 2010 you need to create a Managed Metadata Service Application for the farm. When you create this service application, a database will be created to host the term store. You will be prompted for a name for the database. That is the database that will store the term store. For details about creating a Manged Metadata ...


1

It depends on how you set up your managed metadata, since both ways are possible. Using enterprise keywords enables a tagging system where users can select existing keywords or create new ones. It's similar to tagging a question here, where you select existing tags or, if you have 300 reps, create new ones if they are needed. Keywords have no hierarchy, so ...


1

make sure that the values are correct for CSV. In your csv file how is is seperated? like so? hello "," blah "," magic "," sweet as you can see between each text is "," or , now looking at your csv format I can see an issue with: Political Geography,"A sample term set",,True,"One of the 7 continents","Continent","Asia" instead ammend it and try: ...



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