Configuring the Tridion Connector for Taxonomy Space

Connecting from Content Delivery to a taxonomy in Taxonomy Space requires you to edit the Connector for Taxonomy Space's JSON configuration file. These settings define your connection of Tridion Docs with a specific instance ofPoolParty Semantic Suite, which is available to you through Taxonomy Space.

Before you begin

Before beginning the connector setup process, be sure you have the following:

  • A Taxonomy Space user account with the ApiUser role
  • For Content Delivery capabilities, the PCA extension (connector-framework-pca-extension) for the Tridion Integration Framework is installed to the Content Service

Procedure

  1. In the connectors\ subfolder of the Content Deployer root location, open PoolParty Connector.json for editing.
  2. Set the configuration properties as follows:
    • The configuration section includes the following required details from the Taxonomy Space project:
      baseUrl
      The base URL to the Taxonomy Space instance that you received from RWS, which refers to your specific instance of the PoolParty Semantic Suite (not a URL that points to a PoolParty API endpoint). Example: https://rws.poolparty.biz/. Set this property to the same value you set in the Tridion Docs PoolParty integration.
      projectId
      The identifier of a project in Taxonomy Space, such as 1E26021B-1C2E-0001-A0C3-17E0FDDD13B6. Set this property to the same value you set in the Tridion Docs PoolParty integration.
    • In the namespaces section, configure one subsection for each concept scheme to which you have mapped a field in the Tridion Docs PoolParty integration. Give each subsection a unique name, respresenting the namespace, and a configuration section within it, containing a conceptSchemeUri property, set to one of the concept schemes you have mapped a field to. So, for example, if you have mapped two fields to concepts scheme in the PoolParty integration, you configure the two concept schemes as follows:
      "namespaces": {
        "namespace1": {
          "configuration" : {
      		    "conceptSchemeUri": "http://eurovoc.europa.eu/100142"
      		  }
        },
      		"namespace2": {
      		  "configuration" : {
      		    "conceptSchemeUri": "http://eurovoc.europa.eu/100143"
      	   }
        }
      }
      You can ignore the following properties in the sample file, because they are not used in Tridion Docs: stubCategories, displayName, useFeature and customProperties.
    • The useUserLanguage property, which must always be set to the value true.
    • The Content Delivery environment name (for example 'staging', 'live').

Results

After the Connector for Taxonomy Space setup is complete. If you plan to use the Smart Tagging feature, proceed to the next step to configure your Schemas for that feature.