Skip to main content

Tags

Tags are a simple but important organizational tool in SVRunner. They help operators group assets, search large content libraries more effectively, and apply consistent structure across recurring workflows.

When To Use Tags​

Use tags when you need to organize assets by:

  • campaign
  • client
  • location
  • season
  • content type
  • operational status or workflow grouping

Tags do not schedule content by themselves. Their main value is helping operators find, filter, and manage assets consistently.

What A Tag Contains​

A tag currently has a small core configuration surface, including:

  • a name
  • an optional extension association in the tag editor
  • an asset association list

The tag list also surfaces counts so operators and admins can see how widely a tag is used.

Creating A Tag​

To create a tag:

  1. open the Tags area
  2. create a new tag
  3. give it a clear, reusable name
  4. save it before assigning assets if needed

Choose names that make sense across the whole deployment, not just for one operator's local workflow.

Tag Naming Guidance​

Good tag systems are:

  • consistent
  • easy to scan
  • limited to useful categories
  • shared across operators

Examples of useful tag styles:

  • Lobby
  • Holiday
  • Client A
  • Emergency Messaging

Avoid near-duplicate tags that differ only by punctuation, capitalization, or spelling.

Associating Tags With Assets​

Tags are most commonly applied from the asset editing workflow.

In the asset UI, operators can:

  • add tags to an asset
  • remove tags from an asset
  • reuse existing tags while editing metadata

This makes tags part of the normal asset preparation process.

See Assets.

Managing Assets From The Tag View​

The tag editor also supports managing asset membership from the tag side.

Current behavior includes:

  • viewing the assets currently associated with a tag
  • opening an asset-selection modal to add assets
  • removing assets from the tag directly in the tag sidebar

This is useful when operators want to manage a whole grouping from one place rather than editing each asset individually.

Tag Sidebar Assets Stub screenshot: tag sidebar with the associated assets list and the Add Assets action visible. Save final image at packages/docs/screenshots/app-tag-sidebar-assets.png.

Tag List And Counts​

The tags table currently shows:

  • tag name
  • asset count
  • created date

The asset count helps answer questions like:

  • is this tag actually in use?
  • how large is this content grouping?
  • should this tag be merged, cleaned up, or retired?

Tags Table Stub screenshot: tags table showing tag name, asset count, and created date for several real tags. Save final image at packages/docs/screenshots/app-tags-table.png.

Search And Filter Workflows​

Tags are especially valuable in larger libraries.

The current search and list behavior supports tag-aware filtering across resource views, which means operators can use tags to narrow content sets quickly during:

  • asset selection
  • content review
  • scheduling preparation
  • cleanup workflows

If the team works with many recurring campaigns or locations, tag discipline can save significant time.

Extensions And Tag-Driven Workflows​

Some deployments connect tags to extension-backed UI behavior or extension field choices.

That means tags can do more than simple grouping when the installation includes project-specific schema logic.

If that applies in your deployment, document the local rules clearly for operators.

Common Mistakes​

  • creating duplicate tags with slightly different names
  • using tags as a substitute for proper asset naming
  • applying tags inconsistently across operators
  • letting outdated tags remain in active use without cleanup
  • assuming tags affect scheduling directly