Introduction to SharePoint 2013 terminology and term sets

Managed metadata is a hierarchical collection of centrally managed terms, and we are able to define terms and term sets and then use them as properties for projects in SharePoint Server 2013. To put it simply. The term is a word or phrase that can be associated with a project in SharePoint Server 2013. The term set is a collection of related terms.

Below, let's learn about terminology and term sets in practice, as well as the role in SharePoint 2013.

1, first, we need to create "Managed Metadata service", Chinese is called Meta Data Management Services, terminology and terminology set is based on this service;

Introduction to Managed metadata. It is a hierarchical collection of centrally managed terms that we can define and then use as properties for projects in SharePoint Server 2013;

2, enter the creation page, first enter the name and database name, respectively, the name of the service and the names of databases, for example.

3. Create a new application pool. And give the configuration account. Then click OK below. You can do it! For example, with:

4, wait a moment. Create complete! We are able to see the newly created service from the service, for example:

5, do not be too excited, points can be error oh ~ i here on the error, see the hint is said managed Metadata service does not start, for example:

6, know the problem, solve this problem is much more easy. Go to the Server service, find related services, start on it can! For example, with:

7, start the service, found still error, then you have to check whether your account has the right to connect the service, assuming that no, on the increase of permissions. We can. For example, with:

Of course. I would think a little tiger, because I am using this account to create the service, unexpectedly found that the permissions do not have this account, quite depressed, just add the account is OK;

8, click on the service, access to the management page, for example. Finally normal, good good!

9. Then, we can click the down arrow on the Managed Metadata service to create a new group. For example, with:

My new group name is named Custom, it is suggested to use English, in case there will be a problem in the future, of course, there is interest to try, I usually in the name of the time. Will choose English. Even if the future changes, but also the initial English;

10, we can continue to create the term set in the new group, for example:

11, in fact, the creation of the term set. Or relatively simple, fill the right side of the property, you can:

One thing to note is whether the term set is used as a navigation. We do not navigate here. Meta-data navigation is another application, I have introduced other blogs, interested in being able to read;

12. When the term set is created, we should try to use the term set in the list. Create a column, for example, with a. Fill in the column name, select the column type is "Managed Metadata";

13. Select our datasets, for example by:

14, for the difference. Let's create a column again. Select a two-level term set, for example:

15, create a complete list, we can try to join a project. Then look at the selection field, which is quite novel, for example:

In particular, not every term set can be selected. When we created the right side of the property to be able to set can not be selected, this can make the classification is not selected, we can try to:

16, level Two term Set column selection, the discovery options are less. It's interesting; Of course, we can set the value to be single or multi-select. I'm here on the radio, see what you need:

17, the dataset has a very special concept, called synonyms, we can enter a synonym in the new, and then create the data. When this is joined. Synonyms are prompted, for example, by:

18, hint synonym, suggest you choose subjects, not choose synonym. Of course, we can be stubborn. Oh:

19. Can synonyms be blurred with subjects? The answer is yes, but the concept does not have much to do with meta data. is a feature of SharePoint search, which is a synonym search, which we need to enable with PowerShell commands, for example:

One particular point to note is that the path to the command is a UNC path. If you choose a local path, it is not possible. Error when running the command;

$SEARCHAPP = get-spenterprisesearchserviceapplicationimport-spenterprisesearchthesaurus- SearchApplication $searchApp-filename \\DEV\SITE\WORD.SCV

View the file for the synonym. Format should be SCV, I have the wrong file type here, the operation process error. Careful look only to find. and the file format must be utf-8, otherwise it will also error:

20, the search page, we can see, in fact, the second article does not have a relationship with the key words, is because the synonym plays a role, only to be searched out;

We can look at the details of the second article. There's really no place for Linyu to have a relationship:

Summary

After I have read the term set this concept. Suddenly think of the site column, think very similar. Can avoid the two semantics of data for use throughout the site collection. But. The term set is created through central administration. In fact, the site collection can be shared. Or, cross-application use is possible.

Also, use term sets to get better search results. Keep the entire content of the site consistent. And. Dynamic maintenance and changes. is a very good concept.

Appendix

Http://technet.microsoft.com/zh-cn/library/jj219579.aspx

http://technet.microsoft.com/zh-CN/library/ee424402 (v=office.15). aspx

SharePoint 2013 managed navigation and related configurations

SharePoint 2013 managed navigation and related configuration II

Introduction to SharePoint 2013 terminology and term sets