Templates, Sets, Queries & Actions

Many aspects of Cumulus Core-based systems are created by administrators and even end users (permissions permitting). These "configuration without programming" options enable customers to fine-tune their systems to better suit their specific needs. Three program components that can be easily customized are described below.

Templates & Sets

Using templates & sets, users can customize the appearance of on-screen presentation of metadata (Record and Category View Sets), define the appearance of printed output (Print Templates), and also define default parameters for user permissions (Permissions Templates) and metadata "rubber stamping" (Metadata Templates). Additional options include grouping cataloging options into menu-selectable options, and more.

The Categories pane of the Cumulus 7.1 Native Client interface can be divided to show additional panes. In this image, asset preview and information panes are visible. The three categories assigned to this asset are visible in the Information pane.

Queries

Search queries can be created, saved and shared across organizations. This enables administrators to construct complex queries and make them available to users through descriptive (and easy to understand) menu options. Users can create their own personal queries or save them with others, permissions permitting.

Actions

Cumulus Core Actions are automated processes that occur based on user-request events, time-based events and "edit" events that occur to catalogs and records.

Asset Actions

Usually occurring at the request of a user, such as when an asset is downloaded, Asset Actions perform processing on a selection of assets, such as bit-depth or file format conversions, resizing, and more. Several available third-party plugins extend the possibilities further, offering watermark embedding and advanced image processing. Asset Actions can also be called by the Cumulus Scheduler (below), making it possible to perform unattended, automated asset processing.

This Asset Action performs an image processing task on the incoming asset, and then saves the result out in PowerPoint format to a predefined Internet URL. This might be how a design department gets their high-resolution images into the hands of their Sales team. This Asset Action could be launched nightly by a Scheduler Action for absolute automation.

Trigger Actions

These Actions occur as the result of the addition or deletion of asset records, the editing of certain (or any) metadata fields, and more. They can send email notifications that alert users that changes have occurred, or they can launch customer-created or third-party modules to perform other tasks.

Triggers perform an action the moment an asset record, category or catalog has been modified. Cumulus ships with an email notifier module, but other trigger actions can also be developed. You can choose which field you want to watch, and who you want to receive the email. Leave the rest up to Cumulus.

Scheduler Actions

The Cumulus Core Scheduler executes a Scheduler Action at time intervals you define. In addition to the schedule itself, each Scheduler Action includes a search query that is to be run. The results of the query can be processed by an Asset Action, and/or be updated using Metadata and Permissions Templates.

The Cumulus Scheduler enables catalog administrators to run predefined queries and apply Asset Actions, Metadata Templates and Permissions Templates to the resulting asset records. The example shown searches each night for assets whose licenses have expired, sets their license field to "Invalid" and removes access to the asset for all users in the Production role.

For example, a Scheduler Action could search a catalog for assets whose license has expired, apply a Metadata Template that marks the assets "Unavailable," and also apply a Permissions Template that removes access to the assets for some or all users. The updating of those asset records could then fire off a Trigger Action, which would email an accountant as a reminder to update the licenses.

All Action types can be extended by customers or third-party vendors using the Cumulus Core APIs.