...

• Tags do NOT belong to the metadata and thus do not need to be defined in the schema.
• Tags are stored together with the object as value for the system:tags property similar to metadata.
• Pure tag operations do NOT lead to the creation of a new object version.
• Tags can only be attached to the current version of an object, whereas previous versions cannot have tags.
• For version-specific information, metadata provide the suitable options. They have to be defined in the schema.

...

Note: The tag name including the suffix must not exceed the length limit of 128 characters.

Hiding Tags for Certain Users

Not all tags are relevant for the general user, e.g. tags that are needed for automatic data processing. To prevent the general user from seeing these tags, a classification tag can be defined as follows in the schema:

 <classification>tag[tenMyTenant:process,0,1,2,3,4,5,6,10,100]</classification>

Note: Tags will not be validated by the backend. The same tag name can be used by different clients, but the tag can be used differently by these clients. Since this can lead to problems, it is recommended to assign an appropriate name space to the tag, e.g. the tenant name. In the above example, the tag "process" has been assigned to the name space tenMyTenant. 

Summary

This article gave an introduction into the handling of tags as a feature of the lifecycle management of objects in yuuvis® Momentum. In the "Tagging Objects for Processing" tutorial, an exemplary use case is explained.

...