Metadata Templates are used to add information to the metadata information that is stored on an asset or a category. Each Metadata Template lists the affected fields, together with the respective values and the fill mode to be used. There are separate tabs for record fields and for category fields. Metadata Templates can be used while cataloging or for applying metadata information to records of already cataloged assets.
Header (1 - 7)
1 Displays the selected Metadata Template.
2 Opens a list of available Metadata Templates for selecting one. Shared Metadata Templates are displayed in italics.
3 Opens the Properties dialog for the selected template – providing two tabs:
On the Description tab you may enter or modify language-specific display names and descriptions.
The Sharing tab allows you to define whether you want to share the template with others. Additionally you may restrict the usage to specific users or roles.
4 Opens a dialog to create a new Metadata Template by copying the selected one.
5 Opens a dialog to rename the selected Metadata Template.
NOTE: When renaming a shared template remember to update users’ permissions for this template.
6 Deletes the selected Metadata Template.
7 Sets the selected Metadata Template as default.
8 Tabs to switch between record metadata and category metadata. Both tabs provide the same columns.
Fields (9 - 15)
The Fields section contains a list of the fields that are included in the Metadata Template The list provides several columns
9 Use– Activate this option for each field that should be filled or modified when the Metadata Template is used.
10 Field Name – Name of the field that should be filled or modified.
11 Value– Displays the value that will be filled in. Click a value to modify it or enter a new one.
NOTE: For date field types, the current date is shown initially, illustrating the date format to be entered. A date may be entered manually in the given format or selected with a date picker.
12 If a field of type String List is selected, the arrow opens a list containing the values of the String List field.
13 Fill Mode – Defines how the new value will be applied (default: Replace). Depending on the field type, several possibilities are offered: Replace, Set if Empty, Add, Remove, Insert Before, Insert After, Clear Value. Click the Fill Mode entry for any field to get a list of available options.
14 Opens a list of available fields. Available fields are the fields that are provided by filters or by currently opened catalogs (except Binary fields). Select the field(s) you want to add and click OK.
TIP: Prefill Record Fields The list of fields contains an entry Fields of record XYZ, where XYZ is the name of the currently selected record. Selecting this entry will add all valid record fields to the metadata template and prefill them with the values from the current record.
15 Removes the selected field from the template.
TIP: String List Fields with Different Values
When adding fields that are contained in more that one of the catalogs you have access to, be carefully with string list fields that seem to be identical (same GUID), but have different string list values. Cumulus gives you the impression that you can select the catalog from which you want the field to be added via the Catalogs module. However, this is not the case — actually, Cumulus takes the field (and its values) from the catalog that was opened last at the server, not from the catalog you have selected. Therefore the metadata template will probably not include the string list field values that you want to be included (the ones from the catalog you have chosen as the origin of the field to be inserted). As a consequence, the new or modified Metadata Template will work only for the catalog from which Cumulus has taken the field values. However, if you are in that situation to have two seemingly identical, but in fact different fields (same GUID, but different string list values), there is a workaround that helps to get exactly the field and the values you want to add to a Metadata Template: Create a special user just for creating/modifying metadata templates. This user may have permissions for one catalog only — the catalog from which you want to take the field. Then log in as this user and add the respective field to the Metadata template. Because the user can access one single catalog only, the field and its values will always be taken from this specific catalog.
