All Collections
For CORE Admins
Tag Structure
How to Build Your Tag Taxonomy: A Step-by-Step Guide
How to Build Your Tag Taxonomy: A Step-by-Step Guide
Updated over a week ago

This is an example and a guide for how to create your own, customized tag schema from scratch.

In this article:


Step 1 - Create Your Domain or Select the Domain You Want to Edit

For a new Domain, in order to build out your taxonomy, you need to do two things:

  1. Associate the Domain with a Structure

  2. Associate Existing Tag Groups or Create New Tag Groups that fit the workflow and metadata requirements you’ve identified for this Domain.

For an existing Domain with a defined taxonomy, you’ll add new Tag Fields or edit existing ones. Follow the same steps below to achieve the results you want. For the purposes of this guide, these instructions are about how to build out a tag taxonomy for a new Domain.

To create a Domain,

  1. Go to the Left Tag Types Panel

  2. Select the button next to the Domain dropdown menu

  3. Enter the name of your Domain. For this guide, we’ll call it “Online.”

  4. Save.

tag-types-16.png

You’ve now completed the first step in building a taxonomy.

Step 2 - Start with the Structure Tag Group

Structure is the most important Tag Group of all the Tag Groups in CORE.

  • Structure defines the Metadata categorization.

  • Files that share the same structure are grouped together like folders.

  • These files are browsable in the Browser Tab’s virtual directory and searchable in the Filter Tab under Structure.

tag-browse-structure-1.png

By setting a Tag Field to Structural, it will be listed in the structural categorization of the Filter and reflected in an Asset Group’s Name.

Step 3 - Pair Your Domain With an Existing Structure

To create a structure for your Domain, you can pair it with an existing Structure and modify it, or build your structure from scratch.

Description

Image

1. In the Left Tag Types Panel, select a top level Tag Field in the Structure Tag Group by clicking on it. In this case, Production.

tag-types-17.png

2. Production becomes an editable field to indicate changes are being made.

tag-types-18.png

3. Next, go to the Tag Field Options Box above the Tag Hierarchy Tree. This area is titled by the Tag Field you are editing, so you always know the Tag Field you are changing. This example is called “Editing Production.”

Under “Editing [Production],” you can choose different options that will reflect how a user will view and interact with the Tag Field.

At the top of the box, there are four check boxes:

  • Structural

  • Restrict values to Domain

  • Available for search filters

  • Restrict tag values by parent values

Structural ensures this Tag Field will be applied to the structural string of an asset group even if it isn’t a part of the Structure Tag Group.

Restrict values to Domain means that the tag values associated with the Tag Field are specific and available to that Domain only.

  • For instance, with this restriction selected, users would see in the Film Domain that the Production Tag Values are The Fantasticals 3 and Daylight, while the TV Domain has Newb Detective, Ugliest Liars Ever, and Babe’s Big Burritos.

tag-values-20.png
  • If this box was not selected, both Film and TV Domains would see all the values: The Fantasticals 3, Daylight, Newb Detective, Ugliest Liars Ever, and Babe’s Big Burritos.

Available for Search Filters shows tags in the Filter tab and Advanced Search as searchable options.

Restricts tag values by parent values means that the tag values of a nested or child tag is restricted by the values of its parent.

  • For example Babe’s Big Burritos is an animated show whereas Ugliest Liars Ever and Newb Detective are not. By choosing “restrict by parent tag values”, the Tag Field Department would show Animation as a Tag Value only when Babe’s Big Burritos was selected. The other two shows wouldn’t have Animation as a Department tag value.

tag-values-21.png

Description

Image

4. In our example with Production, since we are building out our structural hierarchy, we will make sure Structure is checked, and Restrict values to our Domain Purpose.
At the top most level of the tag structure, this first Tag Field is the parent, so it cannot be restricted by parent values.
Therefore, Restrict tag values by parent values is not clickable for top-level Tag Fields.

tag-values-22.png

5. Next, select the top button to the right of the Locked column.

tag-values-23.png

6. In the new, blank field, use the arrow to expand the dropdown menu and select your Domain.

tag-values-24.png

7. Then, check the Required box if this Tag Field is a required tag when a file is uploaded. Required tags mean the user must fill out those Tag Fields when uploading.
This is helpful to ensure users are organizing their files with basic categorization so that files don’t get lost in the mix and go tagless.

tag-values-26.png

8.Next to Required is the Locked column.
If you check Locked, it Locks a Tag Field. This means users can select only the Tag Values that are provided in the tag’s menu.
If this box is left unchecked, it means the Tag Field is unlocked, so when users upload files, they will see a next to the field and be able to add their own values and menu items. For our example, we will Lock this field.

tag-values-26__1_.png

9. Now scroll up and hit the Save button.

tag-values-27.png

You have successfully associated a Tag Field with your Domain. However, there are no tag values in this field’s menu yet. It’s essentially an empty field. To add those, we must add Tag Values.

Description

Image

10. After Saving, next select Tag Values at the top of the section.

tag-value-28.png

11. In Tag Values, select the Domain of your Tag Field. Here you’ll see the Tag Field Production above the Tag Values box.

tag-types-29.png

12.To add the Tag Values a user will see in their menus when tagging a file, select the sign above the box.

tag-types-30.png

13.An empty field appears below the box. Add the first value in your Production Tag Field.

tag-types-31.png

14. Hit the Save button again.

tag-types-32.png

15. Select the sign above the box again, and add another value. Then hit save.

tag-types-33.png

Congratulations. You have just associated your Domain with the Production Tag Field, and given it Tag Values.

CHECK YOUR WORK:

Description

Image

1. Refresh the page.

tag-types-34a.png

2. Go to the Left Tag Types Panel, and select your Domain.

tag-types-34.png

3. The Domain filters what Tag Groups and Fields are associated with it. You should see your selected Tag Field under Structure. Select it.

tag-types-35.png

4. Go to Tag Values.

tag-types-36.png

5. Select your Domain.

tag-types-38.png

6. You should see the Tag Values you entered.

tag-types-39.png

Follow these same steps to pair additional existing Tag Groups and Fields with your Domain.

Step 4 - Create a New Tag Structure with New Tag Fields

To create your own tag Structure,

Description

Image

1. Click on the Structure Tag Group name, and in the Tag hierarchy you will see a new top level empty field at the bottom.

tag-types-40__1_.png

2. Enter your intended name. We will call it Project Name here for training purposes.

tag-types-41.png

3. In the dropdown, choose how a user will select the tag value. For Structure tags, use Dropdown.

tag-types-42.png

4. Then follow the same instructions to associate it with your Domain and Tag Values as you did with an existing Tag Field.
5. Start by scrolling Down to Tag Field Option Box below the Tag Hierarchy Tree.
6. Select Structural
7.Select Restrict value to Domain
8. Add a new Domain row by clicking and select your Domain.
9. Check Required.
10. Leave it unlocked.

tag-types-43.png

11. Scroll up and Save.

tag-types-44.png

12. Go to Tag Values.

tag-types-45.png

13. Select Domain.

tag-types-46.png

14. Click next to Project Name

tag-types-47.png

15. Add Project A
16. Save
17. Add Project B
18. Save
19. Add Project C
20. Save.

tag-types-48.png

Check your Work. Well done.

Step 5 - Create Child or Nesting Tag Fields

Nesting Tag Fields with a parent-child relationship is like creating a folder structure. Tags in direct connection to each other where one is subordinate are a parent and child.

To create child Tag Fields,

Description

Image

1. Go to the Tag Field that will be the parent. In this example, Project Name.
2. Select the next to the field. An indented, new blank field will appear under it. This is the child Tag Field or rather the next step down in your tag hierarchy.

tag-types-49.png

3. Enter your intended name. We will call it Project Name here for training purposes.

tag-types-50.png

4. Then follow the same instructions to associate the tag with your domain and select the various options:
5. Scroll Down to Tag Field Option Box below the Tag Hierarchy Tree.
6. Select Structural.
7. Select Restrict value to Domain.
8. Select Restrict tag values by parent values.
9. Add a new Domain row by clicking and select your Domain.
10. Check Required.
11. Leave it unlocked.

12. Scroll up and Save.

tag-types-52.png

13. Go to Tag Values.

tag-types-53.png

14. Select Domain.

tag-types-54.png

15. Click Project A under Project Name.

tag-types-55.png

16. Select + next to Teams.

tag-types-56.png

17. Add 123.
18. Save.
19. Select next to Teams.
20. Add 456.
21. Save.

tag-types-57.png

22. Go back to Project Name and select Project B.

tag-types-58.png

23. Select next to Teams.

tag-types-59.png

24. Add Alaska.
25. Save.26. Select next to Teams.
27. Add California.
28. Save and check your work.

tag-types-60.png

29. Refresh

tag-types-61.png

30. Select Teams in the Left Tag Types Panel.

tag-types-62.png

31. On the right, select your Domain

tag-types-63.png

32. In the Project Name Tag Value Box, you see that Project A, Project B, and Project C are listed under Project Names.

tag-types-64.png

33. Select Project A. You will see that 123 and 456 are listed in the Teams tag box.

tag-types-65.png

34. Select Project B. It shows Alaska and California.

tag-types-66.png

35.Select Project C. It has nothing.

tag-types-67.png

Tag Values are restricted by parent values. Mission accomplished

Did this answer your question?