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


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.


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

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

Lukie, 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/


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

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

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


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

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

Try activating BOTH of the following features: Enable-SPFeature -id "73EF14B1-13A9-416b-A9B5-ECECA2B0604C" -Url <Site-URL> Enable-SPFeature -id "7201D6A4-A5D3-49A1-8C19-19C4BAC6E668" -Url <Site-URL>


3

If you started with Blank site Template, it will not appear. Please verify that the link exists for sites created other than blank site template (Team Site, Document Workspace, publishing portal etc). If not, something else needs to done!


3

I can confirm it doesn't look like taxonomy field made it to filter web parts. I think its called an ISV opportunity ;-) Maybe its somehow related to my question: Taxonomy field doesnt always show up in CQWP filter


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

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


2

The by far easieast way to move the MMS between environment is to use a backup->restore approach. remove the MMS SA from your destination farm restore the db to your destination sql create new MMS SA using the restored db name Voila


2

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


2

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


2

Yes I would customise the "Project" site column. Instead of looking at the 1st level (Client Name) I would start it at the 2nd level (Project name) and then within each site/library ensure that column is configured against the correct Client. This can be done either via the UI or via code (in case you have an event handler that fires when creating a ...


2

If you want to use query string parameters to set metadata, you're going to need some script that parses the query string and sets the field values. I've done this in the past with jQuery and SPServices. Marc has created a dead simple to use query string parser in the SPServices project. Here's an example from a project I worked on that got 2 query ...


2

As it seems this is a limitation of the managed metadata columns in SharePoint 2010. Let's hope a future SharePoint version will improve this behaviour.


2

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


2

Caching is always advisable when you are building a site with heavy traffic. In addition, you also have to think of the gradual increase in traffic over a period of time. A while ago, I have written about the different caching options available in SharePoint 2010. See if it helps you in any way: ...


2

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


2

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


2

You will need to reference the Microsoft.SharePoint.Taxonomy assembly. Then you can open a Taxonomy Session and do what you need to do. var site = SPContext.Current.Site; var taxonomySession = new TaxonomySession(site); var termSet = taxonomySession.DefaultKeywordsTermStore.KeywordsTermSet; EDIT MSDN has this documented in detail: ...


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



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