1
00:00:02,240 --> 00:00:04,800
Now that we know what metadata and manage

2
00:00:04,800 --> 00:00:07,750
metadata are, how are they used inside of

3
00:00:07,750 --> 00:00:11,850
SharePoint? In SharePoint, every item can

4
00:00:11,850 --> 00:00:14,970
have metadata attached to it, from list

5
00:00:14,970 --> 00:00:18,460
items to documents, pages, pictures, and

6
00:00:18,460 --> 00:00:22,575
so on. Metadata is found inside columns,

7
00:00:22,575 --> 00:00:26,395
in that list or library. There is also a

8
00:00:26,395 --> 00:00:29,530
type of column called Managed Metadata,

9
00:00:29,530 --> 00:00:31,560
which gets the information from the

10
00:00:31,560 --> 00:00:34,790
central managed metadata service. Or you

11
00:00:34,790 --> 00:00:37,320
can also configure to have the metadata

12
00:00:37,320 --> 00:00:40,450
used in this column only managed at the

13
00:00:40,450 --> 00:00:43,520
site collection level. Before we move

14
00:00:43,520 --> 00:00:46,940
forward, let's also cover some terms.

15
00:00:46,940 --> 00:00:50,675
First of all, the term store is at the

16
00:00:50,675 --> 00:00:52,440
tenant level. You really have one per

17
00:00:52,440 --> 00:00:55,175
tenant and includes all of your terms. In

18
00:00:55,175 --> 00:00:58,130
on‑premise of SharePoint, you could have

19
00:00:58,130 --> 00:01:00,890
multiple, but in SharePoint Online, there

20
00:01:00,890 --> 00:01:05,830
is only one. Next up, the term group. In

21
00:01:05,830 --> 00:01:08,430
SharePoint products, group is a security

22
00:01:08,430 --> 00:01:11,400
term and with respect to manage metadata,

23
00:01:11,400 --> 00:01:14,550
a group is a set of term sets that all

24
00:01:14,550 --> 00:01:17,170
share the same common security

25
00:01:17,170 --> 00:01:19,780
requirements. Only users who have

26
00:01:19,780 --> 00:01:22,110
contributor permissions to a specific

27
00:01:22,110 --> 00:01:25,670
group can manage term sets that belong in

28
00:01:25,670 --> 00:01:28,760
that group or create new term sets within

29
00:01:28,760 --> 00:01:31,580
it. Organizations should really create

30
00:01:31,580 --> 00:01:34,240
groups for term sets that will have unique

31
00:01:34,240 --> 00:01:38,460
access or security needs. Now a term set

32
00:01:38,460 --> 00:01:41,940
is a group of related terms. For example,

33
00:01:41,940 --> 00:01:44,220
an organization might have a term set that

34
00:01:44,220 --> 00:01:46,820
lists the name of business units inside

35
00:01:46,820 --> 00:01:49,805
organizations such as human resources,

36
00:01:49,805 --> 00:01:54,380
marketing, IT, and so on. A term is a

37
00:01:54,380 --> 00:01:57,950
specific word or phrase that you associate

38
00:01:57,950 --> 00:02:00,850
with an item on a SharePoint site. It is a

39
00:02:00,850 --> 00:02:04,050
single item in a term set, and the term

40
00:02:04,050 --> 00:02:07,710
has a unique ID and it can have as many

41
00:02:07,710 --> 00:02:10,780
text label or synonyms as you want. If you

42
00:02:10,780 --> 00:02:13,360
work on a multilingual site, the term can

43
00:02:13,360 --> 00:02:17,740
also have labels in different languages.

44
00:02:17,740 --> 00:02:19,900
Something to remember is that the term

45
00:02:19,900 --> 00:02:23,040
store is always at the tenant level, but

46
00:02:23,040 --> 00:02:24,990
you could also have term groups that can

47
00:02:24,990 --> 00:02:28,630
be at a tenant level or at the site level.

48
00:02:28,630 --> 00:02:31,515
As I have mentioned a bit before, terms

49
00:02:31,515 --> 00:02:35,100
can be entered in multiple languages. So

50
00:02:35,100 --> 00:02:38,010
if your organization is multilingual, you

51
00:02:38,010 --> 00:02:40,600
can make sure that people tag the same

52
00:02:40,600 --> 00:02:43,900
terms correctly in multiple languages. You

53
00:02:43,900 --> 00:02:46,770
can also add synonyms and abbreviations

54
00:02:46,770 --> 00:02:49,070
for terms, so even if somebody enters a

55
00:02:49,070 --> 00:02:55,000
synonym you have, it will be entered correctly.