Tags functionality use on publish instance

[sandeepk7656774]

As per the reference documentation on tags, the tags should be activated on publish instance. I just did some quick tests to understand more on this

1. Assign tag to DAM Asset, Activate asset (Not pop-up shown to user to activate tags). But publish instance metadata node has "cq:tags" property with required value)
2. Assign tag to Page, Activate asset (Pop-up shown to user to activate rags). But publish instance has jcr:content node of page updated with "cq:tags" property.
3. The tags are not present on publish instance under "/etc/tags"

The query builder is able to get the DAM and Page assets based on cq:tags property. Question is what is the use of tags on publish, if those are not present under "/etc/tags", what is the impact? Just trying to understand what is the role of activation and tags on publish (is there something more than just "cq:tags" property?)

Thanks,
Sandeep

[edubey · Accepted solution]

As long as you keep tags only in cq:tags that should be fine but you do need tags in publish if you want them to get resolved.

Which basically means, from cq:tags will have path to the tag node in /etc but when you need to resolve it to title, tags in /etc should be there.

Also AFAIK, anonymous user does not have access to /etc/tags in publish, if you need to resolve it permission needs to be given or use system user.

Adobe Experience Manager Help | Searching for Adobe Experience Manager Tags using the TagManager API