New answers tagged term
0
Solved it by setting the navigation to term driven navigation, this however created a new problem with the quick launch not showing the parent terms.
0
You can see if the Web Analytics Web Part is sufficient to you:
http://blogs.msdn.com/b/ecm/archive/2010/03/21/introducing-web-analytics-in-sharepoint-2010.aspx
If not, then you can write your own custom web part that use web analytics to present it to the user.
This blog post might be of interest:
...
0
The Managed Metadata Service, which houses the term store (Groups, TermSets, Terms), is a farm-wide service. Any PowerShell scripts or .Net SharePoint API code that modifies any of these must be executed on one of the servers in the farm, whether it's a Console Application, Windows Form, Webpart, Application (ASPX) page, etc.
Overwriting (i.e. deleting and ...
0
What you could do is convert the list of your terms in something that is querable by LINQ and use it.
For example:
TaxonomyFieldValue v = null;
TermCollection childTerms = null;
var session = new TaxonomySession(site);
if (session.TermStores != null && session.TermStores.Count > 0)
{
var termStore = ...
0
You can create a webpart which can search for collection of terms using this method,
Term.GetTerms Method (String, Int32, Boolean, StringMatchOption, Int32, Boolean)
MSDN Source
Here's some sample code,
TaxonomyFieldValue v = null; // Notsurehowtodothisbit();
TaxonomySession session = new TaxonomySession(site);
if (session.TermStores != ...
Top 50 recent answers are included
