Custom Search Solution – Part 2
This is the 2nd in a multi-post series where we explore a custom Enterprise Search solution I designed for one of my clients.
In Part 1, I described the series, the client environment, an overview of the project requirements and presented an overview of the implementation steps. The company name we will use here is “NALCO”. We will also reference the account name of the SharePoint Team Lead (fictional), Sandy Jones, as NALCO\sjones. Even though the requirements are that the Enterprise Search Solution be managed by Sandy Jones, who is NOT a Farm Administrator, the interaction with the Farm Administrator will be required for many of the actual steps. We hope to show how the ongoing maintenance can still be done by Sandy.
In Part 2, we begin Step 1 – Managed Metadata Configuration.
The first step in the solution is to standardize the terms used for the metadata that will be used in the document libraries for use as queryable and refinable terms.
The first step in implementing this solution will be to standardize the metadata used in the various document libraries. To do this we set up the global term sets. Follow the steps below in order to implement this standardization through Managed Metadata.
This step is performed primarily by a SharePoint Administrator with Farm Administrator permissions.
1.In Central Administration
2.Navigate to Application Management > Service Applications > Manage Service Applications > Managed Metadata Service
3.In the section of Taxonomy Term Store create a new Group. It is named NALCO in this document, but may be named anything you wish.
4.Grant NALCO\sjones permissions as Group Manager
5.Create a new term set in the NALCO group
Name: Brand
6.Enter the language terms that should be in this term set
7.Create a new Term set and add terms for the following:
Country
DocTypeCode
Document Type
Language Code
Market Segment
NIC Code
Product Line
Region
8.Do not create a Term Set for Language. We will use the existing default site column for Language when we configure the Content Type Hub.
We continue in the next article with Step 2 – Create and Configure a Content Type Hub
