Smart Tagging Allowlist - Ability to filter SmartTags for business relevant tags only (exclude non relevat tags)

rwunsch-adobe · 2025-02-06T11:23:16+00:00

Request for Feature Enhancement (RFE) Summary: Currently, Smart Tagging in AEM leverages AI to generate metadata for assets automatically. While this increases efficiency, it can lead to irrelevant or inconsistent tagging. Introducing an allow-list would complement the existing block-tags functionality, providing both restrictive (block) and permissive (allow) controls over tag generation.The ask is the Implementation of an Allow-List Functionality for AEM Smart Tagging based on a Dictionary/JSON File. This feature will ensure that only business-relevant tags, as defined by the organization, are applied to assets, enhancing tagging accuracy and consistency. Use-case: Organizations require precise control over the metadata applied to their digital assets to maintain brand integrity, regulatory compliance, and content relevance. For example, a fashion brand may only want tags related to specific product lines, materials, or styles. An allow-list would enable them to define a set of pre-approved tags, ensuring that only relevant tags are applied, avoiding irrelevant or misleading metadata. Current/Experienced Behavior: Currently, AEM Smart Tagging supports blocking specific tags using the block-tags functionality. However, it does not support the enforcement of a strict set of allowed tags. This leads to inconsistent tagging where irrelevant or non-business-related tags may be applied, requiring additional manual cleanup and review.https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/blocked-tags Improved/Expected Behavior: With the allow-list functionality, Smart Tagging will reference a pre-configured list (in JSON or dictionary format) to determine which tags are permissible. Only tags included in this list will be applied to assets. This will ensure business relevance and compliance with organizational tagging standards. Additionally, a reporting mechanism will track and log the blocked tags and the frequency of their occurrence, providing valuable insights for content governance. Configuration: Admins can upload a JSON file or define a dictionary in the AEM configuration console. Validation: Smart Tagging compares AI-generated tags against the allow-list before applying them. Fallback Logic: If no tags match the allow-list, the system can be configured to either apply no tags or notify the user/admin for manual review. Compatibility: Works seamlessly with existing block-tags for dual-layer tag management. Environment Details (AEM version/service pack, any other specifics if applicable): Applicable to AEM as a Cloud Service with Enhanced Smart Tagging enabled. This feature should also be compatible with other AEM versions that support Smart Tagging through Content Intelligence APIs, ensuring flexibility across different AEM environments. Customer-name/Organization name: need to check with customer if the name can be mentioned. Screenshot (if applicable): Code package (if applicable):

Forum|Forum|1 year ago
February 6, 2025
4 replies
479 views

Request for Feature Enhancement (RFE) Summary:	Currently, Smart Tagging in AEM leverages AI to generate metadata for assets automatically. While this increases efficiency, it can lead to irrelevant or inconsistent tagging. Introducing an allow-list would complement the existing block-tags functionality, providing both restrictive (block) and permissive (allow) controls over tag generation. The ask is the Implementation of an Allow-List Functionality for AEM Smart Tagging based on a Dictionary/JSON File. This feature will ensure that only business-relevant tags, as defined by the organization, are applied to assets, enhancing tagging accuracy and consistency.
Use-case:	Organizations require precise control over the metadata applied to their digital assets to maintain brand integrity, regulatory compliance, and content relevance. For example, a fashion brand may only want tags related to specific product lines, materials, or styles. An allow-list would enable them to define a set of pre-approved tags, ensuring that only relevant tags are applied, avoiding irrelevant or misleading metadata.
Current/Experienced Behavior:	Currently, AEM Smart Tagging supports blocking specific tags using the block-tags functionality. However, it does not support the enforcement of a strict set of allowed tags. This leads to inconsistent tagging where irrelevant or non-business-related tags may be applied, requiring additional manual cleanup and review. https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/blocked-tags
Improved/Expected Behavior:	With the allow-list functionality, Smart Tagging will reference a pre-configured list (in JSON or dictionary format) to determine which tags are permissible. Only tags included in this list will be applied to assets. This will ensure business relevance and compliance with organizational tagging standards. Additionally, a reporting mechanism will track and log the blocked tags and the frequency of their occurrence, providing valuable insights for content governance. Configuration: Admins can upload a JSON file or define a dictionary in the AEM configuration console. Validation: Smart Tagging compares AI-generated tags against the allow-list before applying them. Fallback Logic: If no tags match the allow-list, the system can be configured to either apply no tags or notify the user/admin for manual review. Compatibility: Works seamlessly with existing block-tags for dual-layer tag management.
Environment Details (AEM version/service pack, any other specifics if applicable):	Applicable to AEM as a Cloud Service with Enhanced Smart Tagging enabled. This feature should also be compatible with other AEM versions that support Smart Tagging through Content Intelligence APIs, ensuring flexibility across different AEM environments.
Customer-name/Organization name:	need to check with customer if the name can be mentioned.
Screenshot (if applicable):
Code package (if applicable):

kautuk_sahni

Adobe Employee

@rwunsch-adobe

Thanks for proposing this idea.

This has been reported to the engineering under the internal reference ASSETS-47545. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.

Kautuk Sahni

J

JamesC-1

Adobe Employee

@rwunsch-adobe a solve to this use case is being proposed as part of our enhancement to smart tags roadmap. First phase of this enhancement was just announced at Summit in the Top 10 DAM innovations. It will be tracked internally under ASSETS-45281.

R

rwunsch-adobe

Author

Adobe Employee

Thank you @jamesc-1 !

Yes, there is lots of exciting new features coming, and the improvements in the Tagging space are definetly one of them.

Thanks for getting back and for adding the references, I'll monitor the progress!

kautuk_sahni

Adobe Employee

Changing the state of this Idea as per the comment from James.

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded