The Catalog Settings window provides several tabs for different groups of options. The options are valid for the active/selected catalog only. They have no effect on other catalogs.
1 The catalog whose settings are currently displayed. You can select any catalog available to you.
2 Button to save the settings of the current catalog as a catalog template.
3 Button to copy the permissions settings from a different catalog to the current one.
4 Button to copy the trigger settings from a different catalog to the current one.
NOTE: Copying permissions or triggers from a different catalog overwrites the respective setting of the current catalog!
5 Row of tabs for different option groups (details see below).
General Tab
Catalog
1 Catalog file name and path (not editable).
2 Catalog name. Defaults to file name, can be changed. (See “Renaming Catalogs”, for details. Note that catalogs cannot be renamed while set to use the Cumulus Vault in Always and Exclusive mode.)
3 Displays the catalog format
4 Displays the catalog size (actual size/maximum size).
5 If activated, the name of a new category must differ from any existing category name.
IMPORTANT! Do not employ journaling and mirroring for the same catalog! Use one of these mechanisms depending on how the catalog is used.: (See “Securing Catalogs”, for more information.)
Sharing
7 If activated, the catalog is available to Cumulus Clients.
8 If activated, the catalog is available via the Web, e.g. for the Cumulus Web Client.
IMPORTANT! The Allow Web Access option does not affect the availability of catalogs for applications based on the Cumulus Integration Platform(CIP), such as Cumulus Portals!
Copy Asset to Central Location
9 If activated, a Central Asset Location (i.e. a dedicated storage space) is used for newly cataloged assets, according to the selected mode. (If not activated, cataloged assets remain wherever they are stored.)
10 Displays the selected Asset Storage Module and location
11 Opens a dialog for selecting the Asset Storage Module and the location.
12 Opens a menu for selecting how asset are copied to the Central Asset Location. – As Set in Asset Handling Set – the Asset Handling Set employed for cataloging decides whether assets are copied to the selected Central Asset Location, or not. – Always – Assets are always copied to the selected Central Asset Location, regardless of the Asset Handling Set settings. – Always and Exclusive – Assets are always copied to Vault and their asset storage location is Vault exclusively. (This option is available only if Vault is selected as Central Asset Location.)
NOTE: Duplicates control with Central Asset Location! For controlling duplicates with Central Asset Location activated, the record fields Original Asset Identifier, Original Asset Name and Original Asset Reference are required. You have to add these fields to catalogs with Central Asset Location activated if you also want duplicates control.
Record Fields Tab and Category Fields Tab
1 Field name.
2 Field type.
3 Overview on how the field is used for sorting and searching.
4 Overview on whether the user may edit the content of the field. Checkboxes can be activated/deactivated directly.
5 Overview on whether a field is a mandatory field, or whether the field value is checked by a validator. Checkboxes are for display only!
6 Overview on the value mode
7 Opens a menu for selecting the columns to be displayed on this tab.
8 Opens a dialog for defining common properties that apply to all fields in general, e. g. for enabling subscriptions, and configuring the Solr integration. (Record Fields tab only.) For details, see Enabling Subscriptions and Apache Solr integration
NOTE: Catalog Name, Record ID and Category ID are so-called virtual fields. These fields are meant to be used for display and processing purposes only. Therefore you cannot define their properties.
10 Opens dialog for selecting a field to be added.
11 Removes the selected field from the list.
Enabling Subscriptions
Enabling subscriptions in a catalog allows users of the Cumulus Web Client to subscribe to individual files in order to get notified each time the metadata of these files are modified. You can administrate which metadata fields are taken into account for notifications.
To enable subscriptions for a catalog:
1. Make sure the collection window containing the catalog is the active window in Cumulus.
2. Select Cumulus / Edit > Preferences.
3. Click Catalog Settings.
The Catalog Settings window is displayed. If the active collection window contains more than one catalog, select the catalog you want to edit under Catalogs.
4. Click Record Fields.
5. Click Common Properties.
6. In the Common Properties window, select the Subscriptions tab and activate the Enable Subscriptions option.
7. Additionally, select the metadata fields that are to be taken into account. It is strongly recommended to restrict the metadata fields that are taken into account to such fields that are relevant to users or to tasks they have to perform.
NOTE: Cumulus can not create notifications for changed table fields. Therefore, do not select table fields!
8. Click OK to close the Common Properties window. This brings you back to the fields list.
NOTE: Web Client only Files can only be subscribed employing the Web Client. The Desktop Client does not provide this function.
Apache Solr integration
Cumulus indexes the content of string fields for faster searching. However, indexing string fields with lots of data (e.g. the Document text field) and also searching in such indexes can be very time- and resources-consuming. With the (optional) Extended Search Indexing feature, an external indexing and search service, Apache Solr, can be integrated into Cumulus. Solr adds the power of distributed servers to Cumulus, thus making indexing and searching of Cumulus content scalable and, consequently, increasing the overall performance.
To use Solr, the following prerequisites must be met:
• Catalogs on which Solr shall be used must be migrated to the Cumulus 11 catalog format.
• A valid Solr license must be available.
• A Solr installation must be set up and accessible within the network. If you need assistance, contact Canto Professional Services.
To enable Solr integration for a catalog:
1. Make sure the collection window containing the catalog is the active window in Cumulus.
2. Select Cumulus / Edit > Preferences.
3. Click Catalog Settings.
The Catalog Settings window is displayed. If the active collection window contains more than one catalog, select the catalog you want to edit under Catalogs.
4. Click Record Fields.
5. Click Common Properties.
6. In the Common Properties window, select the Apache Solr Integration tab
7. Activate the Enable Solr Integration option.
8. In the Base URL ... field, enter the URL obtained by Solr.
9. Click OK to close the Common Properties window. This brings you back to the fields list.
Usage of the Solr index can now be activated for each string field individually via its Properties.
NOTE: Solr integration for table fields To use of the Solr index for string fields inside of tables, you must enable the Solr integration for each table separately, with an individual base URL for each table!
NOTE: Mirroring and backup of catalogs employing Solr index Mirroring: When mirroring a catalog that uses the Solr index, the mirrored catalog uses the same Solr instance as the original catalog. When using the mirrored catalog, it might be possible that the Solr indexes need to be rebuilt. Using a Backup: All Solr indexes need to be rebuilt.
Asset Relations Tab
Shows the types of asset relations available for the catalog. The asset relation types Contained and Referenced are available by default in any catalog and can not be removed. These relations are detected and set automatically. The relation types Alternates and Variants are also available by default in any catalog but can be removed. In addition to these types you can add asset relations types of your own – so called custom relations. (For more information on how Cumulus deals with asset relations see Managing Related Assets.)
6 Opens a dialog to add a relation type that already exists in an other catalog or catalog template managed by your Cumulus Server.
7 Opens a dialog to add a new custom relation type. (For details about the properties set, see Properties of a Relation Type.) TIP: With Web Client, a custom icon can be displayed for a custom relation. For details see Custom Icons and watch the video tutorial Configuring Asset Relations.)
8 Removes the relation type from the current catalog. Already set relations will be kept but the relation type cannot be assigned any longer.)
9 Opens a menu for selecting the columns to be displayed on this tab.
10 These buttons change the selected entry’s position in the list.
See how creating a custom relation type works ...
and how a custom icon is set for the Web Client
Mirroring Tab
IMPORTANT! Do not employ journaling and mirroring for the same catalog! Use one of the mechanisms depending on how the catalog is used.: (See “Securing Catalogs”, for more information.)
Shows all workflows applied to the catalog. You can add new workflows that are stored at the Cumulus Server, remove existing workflows or update them, if their definition has been modified with the Workflow Manager at the Cumulus Web Server Console.
Applying a workflow to a catalog copies the respective settings to the catalog. For each workflow, 3 fields are added to the catalog:
1 <workflow name> - Workflow Activities
2 <workflow name> - Workflow Assignments and
3 <workflow name> - Workflow State.
As soon as a workflow is assigned to a catalog, it is available to Cumulus users.
NOTE: Updating Workflows Workflows that are applied to a catalog reside there independent of the original definition stored in the Workflow Manager at the Cumulus Server. Thus, editing a given workflow definition in the Workflow Manager does not affect the actual workflow in a catalog. To make modifications to a workflow effective, you must explicitly update the workflow assigned to the catalog to the new definition.
1 Indicates whether a workflow definition is still up-to-date, or whether there is a newer version available at the Cumulus Server.
2 Name of the Workflow.
3 Date when this workflow version was defined first.
4 Date when this workflow was last modified with the Workflow Manager at the Cumulus Web Server Console.
5 Updates the selected workflow. This button is only active if the workflow definition has been updated at the Cumulus Server.
6 Opens a dialog for selecting workflow definitions stored at the Cumulus Server and applying them to the catalog.
7 Removes the selected workflow from the catalog. This also deletes the respective fields from the catalog.
Permissions Summary Tab
Shows what permissions each user or role has for the catalog.
NOTE: You can only view the information, for editing you have to employ the User Manager of the Server Console.
1 List of users (and roles, if Cumulus runs in role mode) the permissions of whom are to be displayed. Initially, no user is displayed in this list. However, available roles are always displayed.
2 Opens a window to search for users and add them to the list.
3 Displays the permissions the above selected user/role has for the catalog.
4 Displays the sets, actions, queries, and templates available for the above selected user/role with that catalog.
Cumulus / 
Edit > Preferences. 
Cumulus / 
Edit > Preferences. 
