Example: Creating a taxonomy for a collection of cars

Enable taxonomies for the fields

• Open the FotoWeb site configuration in the Operations Center
• Select the Site settings tab and choose the Metadata node.
• Tick the Taxonomy checkbox for all the above fields and type in 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

• Open the archive properties and go to the Metadata tab
• Enable the Taxonomy navigation checkbox and choose the fields you want to expose in the archive - all five above fields.

Create taxonomy content

Now, 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 be able to edit taxonomy content.

The taxonomies show to the left of the thumbnail grid, and all are currently empty.

Click on 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. Clicking on the manufacturer node (Audi, for example) at the higher level will 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 files' metadata. In reality, it's the taxonomy that 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 (rather, 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 bring up the taxonomy item editor, where you can set the ACL for the item.

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

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

Tagging the files in the archive

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

Before you can do that, you need to create a metadata set that contains the fields you want to expose to users of the archive. 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 may only pick metadata tags from the ones you have predefined in the taxonomy you just made.

The result: