Hot answers tagged term-store
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
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.
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 ...
2
There is a new method in the 2010 SP1 API: Microsoft.SharePoint.Taxonomy.TermStore.GetSiteCollectionGroup(SPSite currentSite)
you can use like:
session = new TaxonomySession(site);
//Retrieve all Term stores from site collection
termstores = session.TermStores;
foreach (TermStore ...
2
I can confirm it doesnt look like taxonomy field made it to filter web parts. I think its called an ISV opportunity ;-)
Maybe its somehow related to my queston:
http://www.sharepointoverflow.com/questions/4416/taxonomy-field-doesnt-always-show-up-in-cqwp-filter
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
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
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 ...
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
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
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:
...
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
Yes, that is the simplest way to do it. I have only found two ways to rename a term programmatically:
1) Set the Name property and CommitAll on the Term Store:
var site = SPContext.Current.Site;
var taxonomySession = new TaxonomySession(site);
var termStore = taxonomySession.TermStores[0];
var termGroup = termStore.Groups[0];
var ...
1
I think this will give you what you are looking for...
// get the TaxonomyField from the Site Columns in the sitecollectionTaxonomyField
field = (TaxonomyField)site.RootWeb.Fields[TAXONOMYFIELDID];
// get the Term Store ID from the field
Guid termStoreId = field.SspId;
// Open a taxonomysession and get the correct termstoreTaxonomy
Session session = new ...
1
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/
1
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.
1
So, this is my own approach, it is iterating the site collections, but not their contents. It just checks the TaxonomyHiddenList for the terms it contains.
But if someone has a better idea, I would happily accept it :)
$usedTerms = @{}
Get-SPSite -Limit All | foreach {
$web = $_.OpenWeb()
$list = $web.Lists | where { $_.Title -eq ...
1
Yes and no. So
You can implement your own Refiner inheriting (1 & 2 ) from http://www.threewill.com/2012/04/custom-search-refiners/ or http://www.sharepointanalysthq.com/2010/10/custom-refinement-filters-in-sharepoint-2010/
Use something like this (use MaxNumberOfFilters and NumberOfFiltersToDisplay)
<Category Title="Skill" Description="The skill ...
1
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
1
I dont think this works quite as you expect. I have never seen other than just plain anilla text boxes in people search options...
Do you have a reference that claims this is how it works?
I agree it would make sense, but unfortunately taxonomies are not integrated into every part of the platform (yet)
EDIT:
I researched adding taxonomy fields to the ...
1
The user profile service is dependent on the Managed Metadata service in SharePoint 2010. A lot of profile properties will show as disabled if your Managed Metadata service is not set up correctly.
There is a blog post on setting up a custom property using term sets here.
1
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
1
Question 1:
You can associate more than one Metadata Service to a Web application, and a Metadata Service to more than one web Application. From what you're describing I would guess both Services are in the Default Proxy group, this would explain both term sets being accessable from the Term Store management page. It's also possible that if the associations ...
1
Sorry, but I do not have unlimited time to answer multiple sets of questions, but I will attempt the first one:
When I have multiple Managed Metadata service applications I get the behaviour one would expect in Central Administration. In Site Settings, it seems to pick the one that is set to be the default storage location for keywords, and not necessarily ...
Only top voted, non community-wiki answers of a minimum length are eligible
