Container TagsĪ container tag is a node of type cq:Tag containing any number and type of child nodes, which makes it possible to enhance the tag model with custom metadata.įurthermore, container tags (or super-tags) in a taxonomy serve as the sub-summation of all sub-tags. If no namespace is specified, the tag is assigned to the default namespace, which is TagID default (title is Standard Tags) that is /content/cq:tags/default. A namespace is a node of type cq:Tag whose parent is not a cq:Tag node type.Īll tags have a namespace. The tag’s namespace is the first level in the taxonomy subtree, which is the node immediately below the taxonomy root node. tags of a certain namespace) that is applicable to the current content. Namespaces are used in the user interface to only show the subset of tags (i.e. Sites, Assets, Forms) but namespaces can be used for various other needs. public, internal, and portal) or per larger application (e.g. The most typical use case is to have a namespace per site (e.g. In AEM, the base path is /content/cq:tags and the root node is of type cq:Folder. The taxonomy root node must not be a node of type cq:Tag. The taxonomy root node is the base path for all tags in the repository. For example tagging content with fruit is allowed, even if it is a container tag with sub-tags, such as fruit/apple and fruit/banana. Sub-tags can be used to reference tags same as any local TagID. Container tags have sub-tags that represent a hierarchical order in the taxonomy. The TagID consists of a namespace followed by the local TagID. When content is tagged, if it does not yet exist, the cq:tags property is added to the content node and the TagID is added to the property’s string array value. Typically, the TagID is a shorthand starting with the namespace or it can be absolute starting from the taxonomy root node. It is stored in the repository below a base path called the taxonomy root node.Ī TagID identifies a path which resolves to a tag node in the repository.When containing child nodes, it is referred to as a container tag.Optional jcr:title property (the title to display in the UI).The node name is a component of the TagID.The tagging framework also provides the ability to restrict authors and site visitors to use only specific, predefined tags. The title should be displayed in user interfaces instead of the TagID, when present. fruit/apple, meaning both fruits in general and the more specific apple).Ī tag has optional meta information such as a title, localized titles, and a description. fruit) or represent a hierarchical taxonomy (e.g. The declaration of a tag is captured in the repository in a node of type cq:Tag.Ī tag can be a simple word (e.g. The TagID is added to the content node’s cq:tags property and resolves to a node of type cq:Tag.The tagged content node’s NodeType must include the cq:Taggable mixin.The tag must exist as a node of type cq:Tag under the taxonomy root node.To tag content and leverage the AEM tagging infrastructure :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |