Tags are flexible and use cases are numerous. But there are some characteristics of Tags in Orchestra and best practices to reduce complication and confusion.
One thing to remember is that Tags are account-based. So if another user in your account creates a Tag, you as a user can also see that Tag and use it. This makes it easier for companies sharing Tags and reduces the need for unnecessary personal Tags.
Do not use spaces in your Tags
Having spaces in a Tag name can create confusion in an exported report. We advise using an underscore (_) or dash (-) to join two terms in your Tag name.
Do not create more than one Tag identifying the same group
If you want to Tag your Subscriptions with a name like “CCTV”, do not use another Tag name such as “Camera” and apply them both to the same group of Subscriptions. Also, tagging a different group of subscriptions using the same tag name can create confusion. Best practice would be to use one common term to group all related Subscriptions.
Use multiple Tags to identify sub-groups of Subscriptions to get more detailed grouping
Let’s say you have different types of camera devices using data and each has an associated Subscription. You can create multiple Tags like “dash_cam”, “CCTV”, “speed_cams” to apply to each group. You can even use a “Cameras” Tag to apply all the groups to create a hierarchical grouping. That way you have the flexibility to select all camera device Subscriptions or only “Dash_cams” Subscriptions from “Cameras” group. Do not build a hierarchy into the Tag name, like “Cameras_Dash_cams”. It is better to have a separate Tag for each group hierarchy and property.
Use the suggested Tags list to apply a Tag that is already created and do not create more than one version
If you start typing a Tag name, let’s say, “ID_645” and the predictive list shows “ID645”, use the pre-assigned Tag if it applies and do not create a new tag to identify the same group of subscriptions. This will help you maintain a streamlined list of Tags and reduce confusion for users. Multiple Tag names for similar subscriptions can create inaccurate results when filtering, e.g., if you filter by one Tag only, it may not include subscriptions that are tagged slightly differently, even though they should be shown together.