TeamStation AI System Report LATAM IT Salaries 2024
Spstc2011 managed metadata real world
1. Managed Meta Data Service – Using Term store in the real worldbeyond the taxonomy and tagging.Track – Devp300 ATUL CHHODA MODIS Welcome to SharePoint Saturday—The Conference
2. Welcome to SharePoint Saturday—The Conference Thank you for being a part of the first SharePoint Saturday conference Please turn off all electronic devices or set them to vibrate. If you must take a phone call, please do so in the hall so as not to disturb others. Open wireless access is available at SSID: SPSTC2011 Feel free to “tweet and blog” during the session Thanks to our Diamond and Platinum Sponsors:
3. About Me I am a Microsoft Techie focused on SharePoint and .Net development. I am a SharePoint Consultant with over 8 yrs of industry experience and have been working on SharePoint from 2007 and 2010 from beta times. Currently working at the World Bank, DC Worked at federal, non- profit and member organizations for providing SharePoint based solutions for Intranet, Internet and Extranet scenarios and has performed the roles of administrator, developer, designer, and architect. Blogs at http://atulchhoda.wordpress.com Twitter:@atulchhoda
4. What is Managed Metadata ?Every Site column is Metadata ?Why Managed Metadata? Managed Metadata is a hierarchical collection of centrally managed terms that you can define at FARM level, and then use as attributes for items.
5. Major building block in Enterprise Content Management in SP 2010. Use managed metadata. Share content types across site collections and Web applications SharePoint 2010 Managed Metadata Service Application
6. Term store: A database that stores both managed terms and managed keywords. Group: In the term store, all term sets are created within groups. In other words, group is the parent container for term sets. Term set: A collection of related terms. Term: A word or phrase that can be associated with an item in SharePoint Server 2010. Terminology
7. Managed term: A term that can be created by users only with the appropriate permissions and often organized into a hierarchy. Managed terms are usually predefined. Managed keyword: A word or phrase that has been added to SharePoint Server 2010 items. All managed keywords are part of a single, non-hierarchical term set called the keyword set. Terminology
8.
9.
10. Administrator Experience Steps to Enable Managed Metadata on Your Server The Term Store Management Tool (TSMT) enabled below operations on term sets Create Copy Reuse Move Duplicate (for polyhierarchy) Deprecate Delete merge terms manage permissions on term stores Demo: Administrator Experience
12. Power Shell code Add-PSSnapinMicrosoft.SharePoint.PowerShell-erroractionSilentlyContinue ## Settings you may want to change ## $databaseServerName = “sp2010.contoso.com" $saAppPoolName = "Managed Meta Data Services" $mmdappPoolUserName = “Contosopadmin" ## Service Application Service Names ## $metadataSAName = "Managed Metadata Web Service" Write-Host"Creating Metadata Service and Proxy..."
13. $saAppPool = Get-SPServiceApplicationPool-Identity $saAppPoolName -EA 0 if($saAppPool -eq $null) { Write-Host "Creating Managed Meta Data Service Application Pool..." $appPoolAccount = Get-SPManagedAccount-Identity $mmdappPoolUserName -EA 0 if($appPoolAccount -eq $null) { Write-Host "Please supply the password for the Service Account..." $appPoolCred = Get-Credential $mmdappPoolUserName $appPoolAccount = New-SPManagedAccount-Credential $appPoolCred -EA 0 } $appPoolAccount = Get-SPManagedAccount-Identity $mmdappPoolUserName -EA 0 if($appPoolAccount -eq $null) { Write-Host "Cannot create or find the managed account $mmdappPoolUserName, please ensure the account exists." Exit -1 } New-SPServiceApplicationPool-Name $saAppPoolName-Account $appPoolAccount -EA 0 > $null }
15. Planning Managed Metadata Service Identify term sets. Identify the owner of each term set. Determine term set groups. Define term sets Global term sets vs local term sets
16. Planning Managed Metadata Service Governance and import from Enterprise data( a timer job import) Migrating from DEV,STG,PROD Third party tools Custom apps with csv/xml defined schema storing the GUID’s
17. Plan to import managed metadata Locate the existing data. Organize the data into SharePoint Server managed metadata. Clean up the existing data. Format the existing data into files to be imported. Import the managed metadata. Merge terms and add synonyms and translations
18. Benefits of Using Managed Metadata More consistent use of terminology Better search results Dynamic Centralized management of Taxonomy for Enterprise Availability of Taxonomy for the Enterprise
19. Developer Experience Use the Term store API’s to create programmatically create term sets/terms, add terms Import CSV file to create terms programmatically. Use TaxonomyWebTaggingControl Use TaxomomyFieldControl for rendering existing columns
20. Term Store API’s(Microsoft.SharePoint.Taxonomy) Reference assembly C:rogram Filesommon Filesicrosoft Sharedeb Server Extensions4SAPIicrosoft.SharePoint.Taxonomy.dll TaxonomySession class TermStore class Group class TermSetclass Termclass CommitAllmethod IsAvailableproperty Nameproperty CreateLabelmethod SetDescription method
21. Real World Scenarios Using the TaxonomyWebTaggingControl. Using TaxonomyFieldControl. Tagging Site Collections/webapplications and results through search API’s. Use the term set for navigation for building navigation control. Demo: Sample 0 Sample 1 Sample 2 Sample 3
23. Tips & Tricks User SPManager 2010 for creating Taxonomy Field Columns programmatically or through XML http://spm.codeplex.com Add the event receiver
24. Gotchas TaxonomyHiddenList behind the scenes and everything is GUID The site columns are bound to the GUID( not the term store/set/term value) Import Manager/Import TermSet cannot import labels/synonyms . Available only through TSMT and Taxonomy API( CreateLabel) The GUID’s for all the entities in TSMT will be different in different farms. Third party. Database backup/restore. Custom app with API to have the GUID migrated over.
25. Limitations No Infopath /Workspace Support yet Read only in DataSheet View General issues of restoring global and local term sets across environments. Plan a timer job to write xml with GUID’s on the file system 14 hive for both Global and Local Term sets. Blank site template feature is not activated Enable-SPFeature -Identity " 73EF14B1-13A9-416b-A9B5-ECECA2B0604C " –Url http://sp2010 250 terms per managed columns TaxonomyFieldControl, TaxonomyWebTaggingControl are sealed classes. Need to write custom field control for any custom requirements.
26. References Planning http://technet.microsoft.com/en-us/library/ee530389.aspx Boundaries and Capacity planning for Term store http://technet.microsoft.com/en-us/library/cc262787.aspx#termstore Object Model http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.taxonomy.aspx Term Set API’s http://msdn.microsoft.com/en-us/library/ee832800(office.14).aspx Provisioning Site Columns Taxonomy http://support.microsoft.com/kb/2481844 Search : Querying on managed terms fields http://msdn.microsoft.com/en-us/library/ff625182.aspx TaxonomyPickerControl issue: http://support.microsoft.com/kb/2481844
27. Q&A Thank you very much for joining the presentation. Feedback
28. Thanks to Our Other Sponsors! Thanks to our Sponsors
29. Session Evaluation Please complete and turn in your Session Evaluation Form so we can improve future events. Survey can be filled out at: http://app.fluidsurveys.com/s/spstc2011-Fri-S2C-107/ Presenter: Atul Chhoda Session Name: Managed Meta Data Service – Using Term store in the real world beyond the taxonomy and tagging. Session No.:Fri-S2C-107