Text auto-tagging settings moved to Assets configuration

Issue

After installing 7.2 fix pack 1, text auto-tagging settings for Documents and Web Contents do not apply any longer.

The affected settings enabled/disabled the available tagging services that can be used to automatically tag Documents and Web Contents. Settings pages were available in Control Panel → Configuration → System Settings → Documents and Media as well as Control Panel → Configuration → System Settings → Web Content respectively. In both cases, there existed two subsections named OpenNLP Text Auto Tagging and Google Cloud Natural Language Text Auto Tagging. These configurations have been deduplicated into the corresponding tagging service configuration page, and need to be manually enabled.

Resolution

Text auto tagging for Documents, Web Contents and other assets is now enabled from the Asset section of System Settings. Enabling the tagging service and configuring the auto-tagging for each kind of asset is now in one location.

As a result, configuration steps just depend on the tagging service(s) you want to enable:

  1. As a portal administrator, go to: Control Panel → Configuration → System Settings → Assets
  2. To enable OpenNLP text tagging service:
    1. Select OpenNLP Text Auto Tagging under "Virtual Instance Scope" section
    2. Ensure right values are set for service parameters (Confidence Threshold)
    3. Go to "Enable OpenNLP Text Auto Tagging For" dropdown at the bottom of the page
    4. Select the kind of asset you'd like to be auto-tagged with OpenNLP. If more than one kind of asset is to be auto-tagged, click on + icon to add more.
    5. Save
  3. To enable Google Cloud Natural Language tagging service:
    1. Select Google Cloud Natural Language Text Auto Tagging under "Virtual Instance Scope" section
    2. Ensure right values are set for service parameters (API Key, Classification Endpoint Enabled, Confidence, etc.)
    3. Go to the "Enable Google Cloud Natural Language Text Auto Tagging For" dropdown at the bottom of the page
    4. Select the kind of asset you'd like to be auto-tagged with Google Cloud. If more than one kind of asset is to be auto-tagged, click on + icon to add more.
    5. Save

Additional Information

In 7.2 fix pack 1 it is possible to apply auto-tagging on blog entries (see LPS-96625). That enhancement entailed more configuration pages similar to the existing ones for Documents and Web Content.

In order to leave room for more asset types and even to custom asset types, and to simplify the user experience when configuring auto-tagging, it was decided that such configurations would be deduplicated into the corresponding tagging service configuration. This required some enhancement in the configuration system to support dynamic options to be populated at run time according to the text extractors available for the different asset types. See LPS-100917 for additional details.

As a result, the new configurations are not compatible with the existing ones.

¿Fue útil este artículo?
Usuarios a los que les pareció útil: 0 de 0