Example: Creating a taxonomy for a collection of cars

Enable taxonomies for the fields

1. From the Tools menu (cogwheel icon), go to Site Configuration > Metadata > Metadata Setup.
2. Select the Taxonomy checkbox for all the above fields and enter a Plural Name for each field. The plural name will be used as the taxonomy's header in the user interface.

Enable taxonomy navigation in the archive

1. From the Tools menu (cogwheel icon), go to Site Configuration > Archives.
2. Open the General tab.
3. In the Navigation Pane section, turn on the Taxonomy navigation toggle and choose the fields you want to expose in the archive - the five field names mentioned above (not displayed in the example below).

Create taxonomy content

1. Log in to FotoWeb and access the Car collection archive to create content for the taxonomies. The logged-in user must have Manage taxonomy privileges to edit taxonomy content.
2. The taxonomies show to the left of the thumbnail grid, and all are currently empty. Select Add term to start adding terms to the taxonomy.
    

The above taxonomies all have only one level. However, the Make taxonomy is a little different. At the top level, it contains the manufacturer, with model names at the second level, as such:

• Audi
  • A1
  • A3
  • A4
  • A5
  • A6
  • A7
  • A8
• Mercedes-Benz
  • A-class
  • C-class
  • E-class
  • S-class
• BMW
  • 1-series
  • 3-series
  • 5-series
  • 7-series

Since the Make field can only store one value, we will store only model information in that field. Select the manufacturer node (Audi, for example) at the higher level to display the content of all child nodes inside that node (i.e., model names: A1, A3, A4, and so on) even though the term Audi is not written in the file's metadata. In reality, the taxonomy contains the information that Audi is a parent of A1, A2, A3, and so on, even though Audi, BMW, and Mercedes don't exist in the actual XMP metadata in the file.

First level:

Second level (reachable by clicking > in the navigation):

Customizing the Make taxonomy

The values in the taxonomy will also be used when tagging the files in the archive. By default, new entries in a taxonomy will be exposed in metadata editors that incorporate the field in question. Since we don't want users to be able to set Audi, BMW, or Mercedes in the Make field (instead, we want them to set the model: A1, C-class, 3-series), we need to edit the properties of the Audi, Mercedes, and BMW nodes:

• Click on the Pen icon next to the Audi node.

This opens the taxonomy item editor, where you can set the ACL for the item.

You want to remove the Set usage permission to prevent the possibility of users selecting this node when inputting metadata in a field. Do this for the Audi, BMW, Mercedes, and any other nodes you add for car makes at this level of the hierarchy.

The nodes will still have the Query usage permission to allow users to select the node and display assets from all the child nodes. For example, when a user selects Audi, FotoWeb displays all Audi models.

Tagging the files in the archive

Now that the taxonomy has been created, it's time to tag the files in the archive.

Before doing so, you must create a metadata set containing the fields you want to expose to archive users. The metadata set is also used for controlling how the different fields behave. For example, you can create a metadata set with the same fields you have in the taxonomy and dictate that users can only select metadata tags from those you have predefined in the taxonomy you just made.

The result