Page History

...

The Tags app is a central place to manage content tags – keywords or terms assigned to an item of content, see Content tagging.

Configuration

The app is installed by the Content Tags Module and is configured at Configuration > /modules/content-tags .

Usage

In AdminCentral, the app can be launched from the Tools app group, which is accessible only to the users with the the superuser role role. The Tags app is thus inaccessible to the editors since for them the main means of editing tags should be the tag fields in a content app's browser subapp or detail subapp, see How to enable content tags for a content app.

...

.

...

Configuration

The app is installed by the Content Tags Module and is configured at Configuration > /modules/content-tags .

...

The app has two subapps:

• The tag browser: Provides a tree/list view of all tags stored in the JCR repository's tags workspace:
  
  The browser allows:
  • Adding new tags (Add tag action in the Action bar).
  • Renaming tags (Rename item action).
  • Deleting one or multiple tags (Delete item action).
  • Accessing the dependency viewer which displays content items a tag is applied to. The viewer can be launched by selecting a tag and clicking Show tagged content in the action bar.

  • Searching a tag or tags. 
    The search is case-insensitive, forward-looking and its logic is applied not to the actual name of a tag, but to its node representation in the JCR repository's tags workspace. Thus, having defined the history and History tags, the following may occur:

    Search string	Returned result(s)
    	Name column	Path column
    history	history History	/h/hi/history /h/hi/History
    History	history History	/h/hi/history /h/hi/History
    hi	history History Mgnl f hi	/h/hi/history /h/hi/History /h/hi
    h	history History Mgnl f h Mgnl f hi	/h/hi/history /h/hi/History /h /h/hi
    /h	Mgnl f h	/h
    /hi	<no results>*
    story	<no results>

    * Zero results even in the Path column because no path begins with /hi .

...