Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
9

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


8

I've recently written a post on how to access Term Store in SharePoint 2013 using the javascript "SP.Taxonomy.js" Hope it helps you. http://cann0nf0dder.wordpress.com/2013/04/09/accessing-taxonomy-term-store-with-jsom/


7

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 (...


6

JSOM or REST API = no. BUT you can use JavaScript to call the Taxonomy Web Service to effectively accomplish client-side access. It's definitely more cumbersome than using the CSOM or REST API, though, but it works. Try this out: http://spandps.com/tag/web-services/ The taxonomy picker with suggestions uses this web service client-side. UPDATE: See the ...


6

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


5

There is no tool for this in the UI. It is pretty straightforward using the object model. I have seen code samples in C# that could be adapted to PowerShell. Alternatively you could try downloading the termset import/export tool from Codeplex.


5

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


5

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” ( _admin/...


5

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


4

check this link: http://www.kowalski.ms/2011/03/31/sharepoint-2010-export-managed-metadata-terms-from-the-term-store/ you might need to do some changes in the script given on that URL


4

Every time you use expensive operation to get data on public site, you should definitely go for caching. There is no difference between query to DB or using term store in Sharepoint. If you feel this operation is called often (each page load) and is expensive you should cache. There is quite a big chance that terms will not be changed very often, so you ...


4

I don't think you can get rid of the textbox. But the other two requirements may be solved by modifying the Refinement Panels Filter Category Definition. Here is the valid option for the Refinement Panel XML Schema. SortBy="Name" SortDirection="Descending" should give you the ordering you need. MaxNumberOfFiltersToDisplay="50" ShowMoreLink="False" should ...


4

We were finally able to resolve the issue. In short - to work you need to change the way how OOTB Filter code works to way that it thinks that it is operating with SPFieldLookup. To achieve this you need 3 steps. 1.Create copy of Filter.aspx file located from Sharepoint Root Directory. This aspx is responsible for rendering items in filter view. 2. ...


4

When you create a site column of type managed metadata, select "Allow Fill-in Choices" as "Yes". This would allow users to add new terms while selecting terms in the edit properties screen of the document. Note this would work only after you marked the termset "Open".


4

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


4

You cannot create Site Collection specific Term Stores, but you can create Site Collection specific (local) Term Sets. Details here.


4

You cannot edit the Name directly, because the Name of the TermStore is simply the name of the MetadataWebServiceApplicationProxy. So what you have to do is to rename that one instead. In your example, you have to get the SPMetadataServiceApplication first, find the right proxy and rename it. This should look like this, assumed that your ...


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

To set a taxonomy field you should use TaxonomyFieldValue or TaxonomiFieldValueCollection You first need to find the term in your term store: TaxonomyField taxonomyField = item.Fields[field] as TaxonomyField; TaxonomyFieldValue taxValues = new TaxonomyFieldValue(taxonomyField); TaxonomySession session = new ...


3

If you have got hold of Term object, you can call its GetPath method to get a list of its ancestor separated by semi column(;). You can then split and find the index of last item in the split array. Check GetPath method here: http://msdn.microsoft.com/en-us/library/ee584878.aspx


3

The problem is that the SharePoint site is running on http://mysite internally, but is exposed as https://mysite using Microsoft Forefront. This breaks the ValidateTerms AJAX method call, because the call is made to http://mysite while surfing on https://mysite, which violates the same-origin policy of XMLHttpRequest calls. So the JSON AJAX call to ...


3

As @PirateEric mentioned, an easy way to set metadata fields using a query string is by using JavaScript. I maintain SPUtility.js which can help with setting and getting SharePoint fields. For example: SPUtility.GetSPField('Document Category').SetValue(urlValue).MakeReadOnly(); You probably won't be able to use an event receiver because it won't have ...


3

There is a new method in the 2010 SP1 API: Microsoft.SharePoint.Taxonomy.TermStore.GetSiteCollectionGroup(SPSite currentSite) you can use like this source code: session = new TaxonomySession(site); //Retrieve all Term stores from site collection termstores = session.TermStores; ...


3

Unfortunately you cannot filter the managed metadata for the parent and also return child terms when creating a view. An alternative is to turn on metadata navigation. This would give you a navigation control on the left hand side of the page to filter by fields. Clicking on a top level term here would also show all the items with sub terms. This can be ...


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


3

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; };   Mavention.GlobalNavigation....


3

Recently I found solution for this problem by myself. Problem was with attribute ControlId="QuickLaunchDataSource", that was overriding part of my attributes in SiteMapDataSource. ControlId is a part of navigation feature,that stores settings in NavigationSiteSettings.xml It is located in C:\Program Files\Common Files\microsoft shared\Web Server ...


3

You can put the specific term store name in the Site property bag and in the feature receiver fetch it from there.


3

I have been looking for the answer to this one too. The following should retrieve the extra properties: //paste code on one line context.load(tsTerms, 'Include(IsRoot, Labels, TermsCount, CustomSortOrder, Id, IsAvailableForTagging, Name, PathOfTerm, Parent, TermSet.Name)'); The following blog had some good examples that have helped me get my code working. ...


3

Basically it depends on the following settings: a Default Language of Term Store selected language while creating Term Set Assume English(1033), Finnish(1035) and Russian(1049) languages are installed and the following code is used for retrieving term sets: var ctx = SP.ClientContext.get_current(); var taxSession = SP.Taxonomy.TaxonomySession....


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