We have built a taxonomy in our AEM DAM based on custom fields for search, filtering and reporting. We are using a namespace to bucket all of these tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. The first level of those tags is a category which pairs up to a custom field used for search. These tags are technically "buckets" as well. We would like to set these up as namespaces as well but have them be children of the overarching namespace for our organization? So the structure would look like this: organization-namespace:category:tag-level-1/tag-level-2
Current/Experienced Behavior:
We have a namespace to bucket all of our custom tags as a top level bucket. Under that we have built out the tag structure for the rest of our taxonomy. However, the first level of those tags is a category which pairs up to a custom field used for search.
Improved/Expected Behavior:
We would like to set these up the second level "buckets" as namespaces as well but have them be children of the overarching namespace for our organization? It'll be so much cleaner if we can have all of our tags in one place at the top instead of spread out among 20 or 30 separate namespaces at the root level.
Environment Details (AEM version/service pack, any other specifics if applicable):
@dmescia2 Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-56548. 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.