Tags help you categorize assets that can be browsed and searched more efficiently. Tagging helps in propagating the appropriate taxonomy to other users and workflows.
Flat lists of controlled vocabularies can become unmanageable over time. Administrators can use the hierarchical tagging structure, which facilitates applying relevant metadata, categorizing assets, supporting search, reusing tags, improving discoverability, and so on.
You can create a namespace at the root-level and create a hierarchical structure of subtags within the namespace. For example, you can create an
Activities namespace at the root-level and have
Running tags within the namespace. You can have further subtags
Tagging provides many benefits, such as:
Tagging allows authors to easily organize dissimilar assets through a common taxonomy. Authors can quickly search and organize assets by common tags.
Hierarchical tags are extremely flexible and are an excellent way of organizing terms in a logical way. Through namespaces, tags, and sub-tags, entire taxonomic systems can be represented.
Tags may evolve over time as an organizational vocabulary changes.
Tags managed in Admin view remain in sync with the tags managed in Assets view, which ensures metadata governance and integrity.
To be able to apply tags to assets, you must first create a namespace and then create and add tags to it. You can also create tags and add them to an existing namespace. Any tags that you create at the root-level are automatically added to the Standard Tags namespace. You can then add the Tags field to the metadata form so that it displays on the Asset details page. After configuring these settings, you can start applying tags to assets.
You need to add the Tags field to the metadata form only if you are not using the default metadata form.
Additional capabilities beyond what is mentioned in this article including merging, renaming, localizing, and publishing tags are available in the Admin view.
A Namespace is a container for tags that can exist only at the root-level. You can start setting up the hierarchical structure of tags by first defining a logical name for the Namespace. If you do not add a tag to any of the existing Namespaces, the tag moves to Standard Tags automatically.
Execute the following steps to create a Namespace:
Taxonomy Management under
Settings to view the list of existing Namespaces. You can also view the last modified date, the user who modified the Namespace or tags under it, and the number of times the tag is used in an asset.
Description for the Namespace. The input that you specify in the
Title field gets displayed at the top of the hierarchy. For example, in the following image, Activities refers to the title of the Namespace.
Execute the following steps to add tags to a Namespace:
Select the Namespace and click
Create to create the tag at the top level under the Namespace. If you need to create a subtag under a tag that exists in a Namespace, select the tag and then click
In this example, the image on the left represents the tag directly under the Namespace
automobile-four-wheeler displayed in the
Path field. The image on the right is an example of subtags added within a tag, as there are more tag names,
jeep-meridian, displayed in the
Path field in addition to the Namespace.
Specify the title, name, and description for the tag and click
Namefields are mandatory while the
Descriptionfield is optional.
Titlefield later but the
Namefield is read-only.
Unstructured Tags or the tags that do no have any hierarchy are stored under
Standard Tags namespace. Moreover, when you want to add additional descriptive terms without affecting governed taxonomy, you can store that value under
Standard Tags. You can move these values under structured namespaces over time. Furthermore, you can use the
Standard Tags namespace as a free form entry for keywords.
To create a standard tag, click
Create Tag at the root-level. Specify title, name, and description and then click
If you delete
Standard Tags namespace using Admin view, the tags created at the root-level do not display in the list of available tags.
In case you store your tags under the wrong hierarchy or your taxonomy changes over the time, you can move the selected tags to maintain data integrity. The following conditions must be considered while moving tags:
Perform the following steps to move tags from one location to another:
Save. The tag displays at its new location.
To edit the title of the tag, select the tag and click
Edit. Specify the new title and click
Nameof a tag cannot be updated. The root path for a tag is also based on the name of the tag. The path remains the same even if you update the
You can delete multiple Namespaces or tags simultaneously. The delete operation cannot be undone.
Perform the following steps to delete tags:
The tags component gets added to the
default metadata form automatically. You can design a Metadata form either by using a template or from scratch. If you are not using an existing Metadata form template, then you can modify your Metadata form and add the tags component. The metadata property mapping is filled in automatically and cannot be modified at this time. Users in the Admin view can update the mapping to store tag values using custom namespaces and expose only subsets of hierarchies using root paths.
Watch this quick video to see how to add the Tags component to your metadata form:
Go to Asset details page and navigate to the
Tags section of Metadata form.
Select the tag picker icon which is next to the Tags field or start typing in a tag name to see suggested results.
Select one or more tags. The subtag is selected automatically along with the parent tag or namespace.
Tags modified in the Assets view are applied in the Admin view as well.
The following advanced taxonomy capabilities are unavailable in Assets view at this time and are only accessible through Admin view: