Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

Conflict scenario while moving tags

Avatar

Level 3

We have a use case where the taxonomy is altered as per requirements and tags are moved (from Tag A to Tag B) by marketing team.

This creates a need to publish all the associated assets (images/fragments/pages) associated with the above moved tag to keep author and publish in sync.

But more often than not, many assets are still under review workflows (awaiting approvals from different groups) and not ready to be published as such. This causes a  data mismatch in author and publish environments.

Is there a logical way out of this scenario ? Something where we can publish only the metadata of the assets, and not the content ? (And also keep the current running workflow of the assets untouched.)

4 Replies

Avatar

Level 10

Why is it you ahve to move tags once they are established in AEM?

Avatar

Level 3

Hi Mac,

The business team is regularly moving the tags due to ongoing taxonomy changes approved by business owners.

There are multiple teams who own their own tag namespaces in AEM and insist that they keep changing.

Thanks,

Riju

Avatar

Level 10

Moving only metadata and not the tag node itself is not possible solution. It could break the tag and cause problems.

I recommend looking at the Tag Manager API and see if there is a way to build custom AEM Services that can move them or even merge tags when necessary.

TagManager ("The Adobe AEM Quickstart and Web Application.")

The functionality offered in this API may meet your requriements.

Avatar

Level 4

you can also write a custom service/workflow process to replicate only the metadata nodes using replicator service(Replicator ("The Adobe AEM Quickstart and Web Application.") )