Manage metadata:
Metadata is the data of data.
Manage metadata helps to provide with central location to store, manage metadata throughout aany site with in that SharePoint farm. This feature in SharePoint 2010 is one one step ahead of content type and site columns which we used in SharePoint 2007, but content type and site column were restricted to site collections.
Term Store: This is a location where we have all our metadata stored in.
Term: It is associated with an item in SharePoint 2010. A term has a unique ID and it can have many different text labels (synonyms).
Term set: It is a collection of related terms. There are two types of Terms available in SharePoint 20010 Managed Terms and Enterprise Terms.
Managed Terms: It is commonly referred to as “Taxonomy” are predefined words or phrases that can only be created by users with the appropriate permissions. We can refer to this special group of users as “Metadata Content Managers”.
Enterprise Terms: It is commonly referred to as “Folksonomy” are words or phrases that have been added by the end user. Now that we have a better understanding on some of the key concepts.
The managed metadata service account should be the part of local admin group, farm admin and should have security admin at DB.
There will be only one DB associated with this service application.
Create Managed Metadata service application:
Central admin --> Application --> Application Management --> Manage service application --> Click New and then select Managed Metadata service --> Enter the Managed metadata service name, enter the existing SQL server name and the Managed metadata DB -->Select the authentication as Windows Authentication --> Enter the new application pool name --> Select configure and select the account name --> select Report syndication import errors from site collections using this service and Add this service application to the farm's default list.--> Create
Now start the managed metadata service through central admin --> Start the Managed Metadata service application through "Start- SPServiceInstance " where GUID is the GUID of Managed metadata application
The Set-SPMetadataServiceApplication cmdlet first erases all accounts, then adds the accounts that you specified. If you only want to modify one value, and you want to use Windows PowerShell to do this, consider writing a script that uses Get-SPMetadataServiceApplication to get the values of the account parameters, assigns the values of all account parameters to temporary variables, modifies the variables you want to change, and then uses Set-SPMetadataServiceApplication to set all four account parameters.
Metadata is the data of data.
Manage metadata helps to provide with central location to store, manage metadata throughout aany site with in that SharePoint farm. This feature in SharePoint 2010 is one one step ahead of content type and site columns which we used in SharePoint 2007, but content type and site column were restricted to site collections.
Term Store: This is a location where we have all our metadata stored in.
Term: It is associated with an item in SharePoint 2010. A term has a unique ID and it can have many different text labels (synonyms).
Term set: It is a collection of related terms. There are two types of Terms available in SharePoint 20010 Managed Terms and Enterprise Terms.
Managed Terms: It is commonly referred to as “Taxonomy” are predefined words or phrases that can only be created by users with the appropriate permissions. We can refer to this special group of users as “Metadata Content Managers”.
Enterprise Terms: It is commonly referred to as “Folksonomy” are words or phrases that have been added by the end user. Now that we have a better understanding on some of the key concepts.
The managed metadata service account should be the part of local admin group, farm admin and should have security admin at DB.
There will be only one DB associated with this service application.
Create Managed Metadata service application:
Central admin --> Application --> Application Management --> Manage service application --> Click New and then select Managed Metadata service --> Enter the Managed metadata service name, enter the existing SQL server name and the Managed metadata DB -->Select the authentication as Windows Authentication --> Enter the new application pool name --> Select configure and select the account name --> select Report syndication import errors from site collections using this service and Add this service application to the farm's default list.--> Create
Now start the managed metadata service through central admin --> Start the Managed Metadata service application through "Start- SPServiceInstance " where GUID is the GUID of Managed metadata application
The Set-SPMetadataServiceApplication cmdlet first erases all accounts, then adds the accounts that you specified. If you only want to modify one value, and you want to use Windows PowerShell to do this, consider writing a script that uses Get-SPMetadataServiceApplication to get the values of the account parameters, assigns the values of all account parameters to temporary variables, modifies the variables you want to change, and then uses Set-SPMetadataServiceApplication to set all four account parameters.
No comments:
Post a Comment