This article aims to help you understand the value of taxonomies by applying it to an archive containing a car collection.
At the outset, we have a FotoWeb archive that contains a collection of pictures of cars from different manufacturers. We will be using custom-made fields for tagging these pictures using labels that we define in the associated taxonomies.
Before you begin, these fields must be renamed in Site Configuration > Metadata > Metadata Setup.
|Field number (may not be the same in your configuration)
|2010, 2011, 2012, 2013, 2014, 2015, and so on
|A-class, C-class, E-class, A1, A3, A4, A5, A6, A7
|Number of doors
|4-cylinder, 6-cylinder, 8-cylinder
|White, Black, Blue, Gray, Red, Silver, etc.
Enable taxonomies for the fields
- From the Tools menu (cogwheel icon), go to Site Configuration > Metadata > Metadata Setup.
- 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
- 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 Fotoware SaaS 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.
Select + Add term to start adding the following terms to the taxonomies:
|Number of doors
All of the above taxonomies have only one level.
You also need to create a taxonomy for the Make and model field, an example of a multi-level taxonomy. At the top level, it contains the manufacturer, with model names at the second level, as such:
Since the Make and model field can only store one value, we will store only model information in that field. Selecting 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.
Second level (selecting > in the navigation):
Customizing the Make and model 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 and model 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:
- Select the Pen icon next to the Audi node.
This brings up the taxonomy item editor, where you can set the ACL for the item.
You can remove the Set permission (as shown below) to prevent users from selecting 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 users to click on the node and display assets from all the child nodes. For example, when a user select 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 doing that, you need to 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 may only pick metadata tags from the ones you have predefined in the taxonomy you just made.
Creating a metadata set for the car collection
- From the Tools menu (cogwheel icon), go to Site Configuration > Metadata > Metadata Views.
- Select Add Metadata View.
- Select Add Region to create a region to accommodate the fields used to add tags to the assets in the archive.
- Enter Car info in the Title field and select Quick info from the Zone drop-down list. This means it will be displayed in the column to the left of the asset preview on the asset details page.
- Select Add field to add the Model, Year, and Make,
- The Edit permission allows editing of the field - this still stipulates that the logged-in user has Edit metadata permissions on the archive.
- Required means that the field has to be filled in. It cannot be left empty.
- Taxonomy only means that users may only choose from taxonomy values when adding metadata to the field. If this option is not selected, users can choose tags from the associated taxonomy or enter their own keywords.
Assigning the metadata set to the archive
Having created the metadata view, you need to assign it to the Car collection archive:
- From the Tools menu (cogwheel icon), go to Site Configuration > Archives.
- Select Edit for the Car collection archive.
- On the General tab, in the Metadata management section, select Car collection from the Metadata view drop-down list.
- Select OK to save the changes.
Adding metadata from the taxonomy
When users open the Asset Details page (clicking on a thumbnail in the grid) to edit metadata, they can click on the new fields in the editor and choose from the values you defined in the taxonomy. When adding content to the Make and model field, you will see that you're only able to add model names, not the car makes, because the Set permission was disabled for the taxonomy's top level: