Taxonomy Extension for Microsoft SharePoint enables documents and list items in a SharePoint-based portal to be organized cross-site as part of a connected content network and knowledge model. SharePoint items are associated by category using one or more custom taxonomies by tagging.

Users can organize documents and other portal contents in the way that they think and work – independend of the storage location. With that extension the SharePoint portal really can become a place to share knowledge as well as content. This version is the first release on CNET Download.com

Build a teams search app using aequos MDV, Microsoft Graph extensions, and SharePoint taxonomy¶

In this step-by-step tutorial, we demonstrate how to build a search center allowing to browse teams from Microsoft Teams using a dedicated application, SharePoint taxonomy terms, and aequos MDV.

The technologies used for this tutorial are:

• Microsoft Graph schema extensions (to add custom properties to teams)
• SharePoint taxonomy (to define classification values)
• aequos Modern Data Visualizer solution (for the search experience)

Step 1: Create taxonomy term sets¶

For this example, we will create two SharePoint taxonomy term sets for our teams’ classification. Go to the SharePoint term store and create the following term sets and terms:

• “Group type”: the type of team created (Project, Community, Organizational)
• “Department”: the organization department associated with the team
  

  Step 2: Create Microsoft Graph schema extensions¶

  To be able to set custom metadata for your Teams, you will need first to create a Microsoft Graph schema extension on the underlying group resource. Microsoft Graph extensions are a way provided by Microsoft to add custom data on Microsoft 365 resources (ex: group, user, etc.)

  Why use a schema extension instead of an open extension?

  Simply because only schema extension can be filtered using the OData $filter expression. To build a search center, this could be pretty useful ;).

  Warning

  As of today, Microsoft Schema extensions does not support complex property types like arrays and string values are limited to 256 characters. It means teams can only be tagged with a single value per metadata.

  Create a schema extension using Microsoft Graph Explorer¶

  • In the same Azure Tenant where the teams you want to tag belong, create a blank Azure AD application and save its ID for later.
    

    Step 3: Tag your teams with your new extension and taxonomy values¶

    Using the “aequos – Group/Team metadata” Web Part¶

    Since the 1.4.0, we’ve added the aequos – Group/Team metadata editor to help you in this task. The Web Part can be used in a SharePoint page or as a tab in a team to calssify “on-demand”. This way, team owners can directly update the team classification using taxonomy values (or not). Refer to the Web Part usage for more information.

    Taxonomy API design

     

    Scenarios and personas

    These APIs are designed for basic create/read/update/delete (CRUD) operations of the taxonomy service within Project Cortex. The scenarios include providing basic functionality so that some functionality of the UI for the term store can be built around the APIs. In addition, the APIs can be used by third party developers so that they could do CRUD on the term store. Scenarios like creating a term, modifying its properties and deleting a term are to be supported.

    CRUD operations for Taxonomy

    The APIs cover basic CRUD operation for taxonomy term store in SharePoint.

    Details and schema changes

    There are 5 main entities that we define.

    1. store
    2. termGroups
    3. sets
    4. terms
    5. relations

    The above entities allows the user to perform operations that relevant to the taxonomy service. Details of these entities are below.

    New entity types

    {microsoft.graph.termStore.store}
    This is the top-level entity containing the resources to manage a taxonomy (meta-data tagging) for a tenant.

    Properties

    Property	Type	Description	Key	Required	ReadOnly
    id	string	Unique identifier of termStore.	Yes		Yes
    defaultLanguageTag	string	Default language tag for all meta-data in the system.	No		No
    languageTags	Collection(string)	List of working language tags of termStore.	No		No

    Relationships

    Property	Type	Description	Contained Navigation Property	Nullable	ReadOnly
    groups	Collection(microsoft.graph.termStore.group)	Collection of all termsGroups available in the termStore.	Yes	Yes	No
    sets	Collection(microsoft.graph.termStore.set)	Collection of all sets within the termStore.	No	Yes	No

    Supported functionality

    Operation	Supported	Method	Success	Notes
    Get	✓	GET	200
    Create	X	POST	201
    Update	✓	PATCH	204
    Delete	X	DELETE	204 Enable site classification in your tenant To benefit from site classification, you need to enable this capability at the Azure AD level, in your target tenant. After you have enabled this capability, you see an additional field How sensitive is your data? while creating new “modern” sites. In the following figure, you can see what the site classification field looks like.