Using CUE Semantic
If CUE Semantic is installed and running, then a Semantic Analysis section is added to the CUE content editor's metadata panel, and used to display a list of suggested tags for the content currently displayed in the editor:
The list of suggestions is constantly updated to reflect changes in the content. To tag a content item, all you have to do is select suggestions from this list by clicking on them. When you select a suggestion, it is grayed out to indicate that it is now selected, and it immediately appears in the Tags section of the metadata panel as a tag. Once it is added here as a tag, you can optionally adjust the relevance score suggested by the external service.
When a suggestion is accepted, one of two things can happen:
If the suggestion exactly matches the label of an existing tag in the tag schema to which the suggestion has been mapped, then that tag is used to tag the content item.
If the suggestion does not exactly match the label of an existing tag in the tag schema to which the suggestion has been mapped, then a new tag is added to the tag schema.
The tag label matching is case sensitive. If your tag schema contains a tag called football, accepting a suggestion with the name Football will result in the creation of a new tag.
New tags are always added at the root level of a tag schema.
For these reasons, it may be necessary to periodically tidy up your tag schemas by merging tags and moving them from the root level to the appropriate location in tree-structured tag schemas, especially if you use CUE Semantic to update existing tag schemas that contain tags not suggested by CUE Semantic's external service.
CUE Semantic tries to encourage consistent tagging by:
Marking suggested tags that do not already exist in the tag schema as new (they are marked with a triangular tab as shown in the screenshot above)
Asking for confirmation when you add a new tag.
Before adding a new tag, you should always check to see if there is another semantically equivalent tag that already exists in the tag schema. In this way you will avoid the need for merging tags later.