Automatic Tagging Setup : Prerequisites
   
Prerequisites
In order to make use of the Automatic Tagging feature, some prerequisites concerning licensing, permissions, and catalog settings must be met.
Licensing
A respective license must be purchased, and activated via the Remote Admin module of the Cumulus Server Console or Web Server Console. This can be
EITHER:
A Cumulus Automatic Tagging OEM (one year) license,
OR:
an Automatic Tagging license.
Additionally, you need a valid account with one of the supported Automatic Tagging providers.
Cumulus Automatic Tagging OEM vs. Automatic Tagging
The Cumulus Automatic Tagging is a genuine carefree package that allows to use a ready-configured Automatic Tagging solution out of the box – no need to worry about which Automatic Tagging provider to choose, or contract or licensing details, or configuration specifics.
Automatic Tagging is aimed at Cumulus customers who want to choose a Automatic Tagging provider of their own, or already have a contract with such a provider. There are dedicated Automatic Tagging Connectors for the different providers supported by Cumulus.
Permissions
Only the Cumulus Administrator can set up the Automatic Tagging feature at the Cumulus Server Console or Web Server Console.
Cumulus users who want to use the Automatic Tagging feature must have the Automatic Tagging User permission (Permissions > Catalog Permissions > Automatic Tagging Permissions).
Automatic Tagging User – can start the automatic tagging process
Catalog-related Prerequisites
Automatic Tagging Specific Record Fields
Before using the Cumulus Automatic Tagging feature, make sure that the Automatic Tagging specific fields (provided in the Fields for Automatic Tagging catalog template) are added to each affected catalog! For details on how to add fields to a catalog, see Adding Fields.
The Automatic Tagging feature needs the following fields:
Automatic Tagging Log – table field into which messages related to the Automatic Tagging process are written. Which messages are included depends on the specified logging level (see below)
Automatic Tagging Request – string list field with two possible values, Analyze and Review. This field is required if the Automatic Tagging process is to be started via the Cumulus Scheduler
Scheduler Task
If the Automatic Tagging process is to be started via the Cumulus Scheduler, a Scheduler task with the Cumulus Scheduler action Automatic Tagging must be set up, specifying the catalogs on which the action shall be performed, and its frequency in time (Repeat interval or Cron Notation).
NOTE: Depending, among others, on the number of assets to be tagged and the speed of your Internet connection, the tagging process may take same time. It should only be restarted after it is properly terminated. Also, running the Automatic Tagging may generate expenses. Therefore it is crucial to choose a reasonable repeat interval.
For details on how to set up a Scheduler task, see Setting Up a Scheduler Task.
Other Prerequisites
To make use of the Automatic Tagging feature, it must be ensured that the service URL(s) of the configured Automatic Tagging providers can be reached from any machine on which the Automatic Tagging is evoked. These are the machines on which the Cumulus Clients run, the machine on which the Cumulus Web Solutions run, and the machine on which the Cumulus Server runs.
For the initial configuration, the URLs in question are
https://vision-api.eyeem.com
https://api.clarifai.com.