Taxonomy
MatchPoint provides support for SharePoint terms. Therefore, terms can be used throughout all MatchPoint controls:
- Within a data provider, a TermCondition can be used to search for items with a specific term.
- Within a Form or Workspace Editor Web Part, a TermChoiceField can be used to select terms, i.e. to apply on a list item or a Workspace.
- Within a Data Grid Web Part, a TermColumn can be used to display terms
- Within a Search Definition Web Part, terms can be used to search for SharePoint content – if this is configured within the search definition scope (see Search Scope Configuration File)
- Within a Refinement Web Part and a CompositeRefinementWebPart, terms can be used to refine search results (see TermRefinementColumn and TermRefinementGroup.
- Terms can be imported by using a term importer timer job.
- Terms can be configured with icons within the MatchPoint configuration file.
- Terms can be accessed within expressions on all SharePoint content by using the taxonomy extensions.
The functionality for term support is part of the feature Colygon.MatchPoint.Server which can only be used within SharePoint Server environments. If the farm is based on SharePoint Foundation, tags cannot be used. For more information, please refer to the document MatchPoint Installation Guide.
Term Importer
MatchPoint includes a term importer timer job that can be used to import terms into the term store. Term importers can be managed on the "Manage Timer Jobs" form, available on the Instance Administration site.
In SharePoint least privilege environments, scheduling and executing timer jobs cannot be triggered from the GUI. For more information please refer to the document MatchPoint Installation Guide. Otherwise, timer jobs can be started and scheduled directly from the Manage Timer Jobs form.
A term importer can be configured with the same data sources available for tag importer timer jobs and schedules that are available for MatchPoint timer jobs.
Within a TermImporterConfiguration file, a TermImportConfiguration element is used to import terms. The parent element can be either another term or a term set.
Term Icons
Just as for standard SharePoint managed properties, icon mappings can be defined for all SharePoint terms. For general information on icon mappings, please refer to "MatchPoint Configuration". The following example shows how the XML for creating icon mappings for the "Document Type" term set and child elements:
<Mapping Pattern="Term Store/Document Type" FileName="EMMGroup.png" />
<Mapping Pattern="Term Store/Document Type/*" FileName="EMMTerm.png" />
Icon mappings defined within the MatchPoint configuration file will only affect the behavior of the property within MatchPoint controls, i.e. within the Search Definition Web Part.
Terms in Expressions and Configuration Files
Taxonomy Extensions
If SharePoint terms are accessed within a MatchPoint expression (e.g. to display terms from a list item within a Composite Web Part), the GetTerms() extension method can be used:
ConnectionData.Data Grid.SelectedRow.GetTerms().Filter("Geography").ToHtml()
TermCollectionConfiguration
Within various configuration files, a
TermCollectionConfiguration
element can be used to specify one or
more terms.
Configuring a Data Provider for Use with Terms
The following table illustrates what properties to use, if a MatchPoint data provider is configured to use terms (either within a term condition or within a term column).
The example uses two "Managed Metadata" columns that are configured on a SharePoint list or document library:
- "Status" - single value term column
- "Countries" - multi value term column
Data Provider | |||
Property | ListDataProvider | SiteDataProvider | SearchDataProvider |
Status | Status | Status | Managed Property* |
Countries | Countries | InternalName of Countries_0 | Managed Property* |
All Terms | TaxCatchAll | (not supported) | Managed Property MATCHPOINTTERMS |
* need to be configured on the search service application manually.
Please note that SharePoint automatically creates managed properties
(i.e. for ows_taxId_Status(Text)
, ows_taxId_Countries(Text)
). However,
these columns do only contain the display name of terms and therefore
cannot be used within a TermColumn.