...
- Running jobs
- Catalog
- Channels
- System tools
7.1 Running jobs
In the 'Running jobs' folder, you can monitor the status and process information for jobs currently in progress. The status of the process changes in 'real time' until the job is complete.
...
Roles can be set individually to allow specific users or groups to view, re-import, re-prioritize and change active jobs as needed. A Digizuite™ administrator is needed in order to change current roles. This provides an overview of the system and also for SuperUsers to adjust active jobs without consulting an administrator.
7.2 Catalog
The Catalog area in the DigizuiteTM DAM Center can be found in the left side menu. The area contains assets structured in folders and subfolders. The DAM Center is based on a single-source strategy: the source of the asset will always be inside the Catalog area and a copy will be published on the other products.
7.2.1 Import
Importing assets can be done either manually or as a batch process automated by the Digizuite™ DAM Center.
There are two ways that helps at importing assets into the system.
- Digizuite™ importer
- UNC Batchingest (automated)
7.2.1.1 DigizuiteTM DAM Center Importer
Allows for ingest of Digizuite™-supported files through the Digizuite™ importer.
...
When marked as required, selected metadata field must be filled in correctly on each selected file in the upload list, before uploading can be initiated.
7.2.1.2 UNC Batch ingest
Batch ingest workflows are custom designed based on feature-requests and technology. Please consult a Digizuite administrator or the support team for further information.
...
In addition, files can be ingested with related XML documents containing metadata for the file, which are automatically filled in for the newly imported asset in relation to the import inside the Digizuite™ DAM Center.
7.2.2 Versioning assets
The Digizuite™ can be configured to allow versioning of the assets. In plain terms this is also referred to as a replace-asset function.
...
To enable the replace-asset feature please follow this guide: Asset Versioning Configuration Guide.
7.2.3 Add asset directly without source material
Dummy-assets (asset with no data) can be created in the Digizuite™, by simply selecting Add → Metadata only directly in the requested catalog folder. Creating dummy-assets can be done for any Digizuite™ approved asset types and allows for metadata editing in advance.
7.2.4 Search
The Digizuite™DAM Center provides the option of an extensive search function. The search runs in the Catalog area, if you have the rights for these. A Digizuite™ SuperUser/Administrator can specify which metadata fields can be used as active search criteria.
...
Searches inside the Digizuite™ DAM Center allow you to select whether the same syntax that you recognize from Google should be used, or whether you want to retain the system's own syntax. This is a question of the configuration in the Digizuite™ DAM Center system area. This setting can be made by a system administrator.
7.2.4.1 Syntax for Searching
The Digizuite™ is by default configured to use its own syntax when performing searches. Alternatively the search engine can be set to use Google syntax. To enable Google syntax the following two Digizuite™ constants must be set:
| Constant | Description |
|---|---|
| SEARCH_GOOGLE |
|
| SEARCH_GOOGLE_TERMTYPE |
|
7.2.4.2 Filter options
The filter options is configurable. The following fields are defined as standard in the new DAM Center:
...
The filter options can easily be adjusted or removed, and new ones can be added if needed. Any asset metafield can be used as a filter. See the Manage Filters Configuration Guide for how to set this up.
7.2.4.3 Publication of search result
When a collection of assets is created, you can find the collection inside Catalog → Collections. A saved collection can always be published by right clicking on the desired collection and selecting Publish this collection.
7.2.4.4 Finding the location of an asset in a collection
The metadata for each asset contains a link to the folder containing the asset. To go to this location, select the asset, click on one of the locations listed under the Catalog location or Channel location (if the asset exists in a channel folder.
7.2.5 Permissions
Administrators with editor permissions (Editor_Catalogs or Editor_SystemTools_AllwaysAllowItemSecurityEdit) can create and edit folder permissions by right-clicking on the desired folder and select Edit folder rights.
...
When creating a new folder, the rights are automatically inherited from the parent.
7.3 Channels
Channels contains all the material that you want to be online and available via an external application. The different channels are defined in this area. A channel is a structure of data and assets.
...
All assets in the channel are only references. This means that you can delete a reference in the channel without influencing the actual asset which is located in the Catalog structure. Assets in the Channel area will always come from the Catalog area. This means that the content in the Channel area, is a reflection of the physical files that are found in the Catalog area. If you delete a published asset in the Catalog area, this will have an effect on the display of the relevant asset in a given Channel.
7.3.1 Publish to different channels
In order to publish an asset to a specific channel, navigate or search inside the Catalog for the asset. Once selected, open the metadata editor and select All asset types → Channel. Now mark the specific channel and press Save.
7.3.2 Channel folders
Channel folders are language dependent. In practice, this means that all folders can be related to all languages in the system.
Which language the individual user sees and/or edits is controlled by the user setup or the user's rights. Language data can naturally also be edited directly via language tabs which are recognized from the general metadata structure. The individual folders have certain data attached. In addition to the sort index which was used for displaying in Digizuite™ DAM Center, these definitions are solely for the destination.
7.3.2.1 Editing metadata
Folders in the Channel area have editable metadata. In order to edit this, right click the chosen folder in the Channel area and select Edit metadata for folder. The metadata for Channel folders contains an additional tab named Layout, which is described below.
7.3.2.2 Standard tab
The Standard tab usually defines the following fields:
...
Note: These are language dependent.
7.3.2.3 Layout tab
The Layout tab usually defines the following fields:
...
Furthermore, references are also defined in the Layout tab.
7.3.3 Publication
The route to getting an asset published to, e.g. a website, is twofold. The asset is firstly exported to the quality/qualities determined in the template, which controls this exact asset. Then, the information on the medium's existence and the metadata are published.
Assets, that haven't been published yet, will have a gray overlay color. The published assets are distinct in color and are furthermore marked with green check marks in the top right corner.
7.3.3.1 Publishing – Export
Exportation only happens when you click on the Publish option in settings menu (the gear icon). You can export many assets in one go, or even an entire folder structure.
Export happens completely automatically based on the definitions that the template define. You can also inspect the export in the 'Running jobs' folder. These exports are marked as 'Portal export' in the 'Running jobs' folder.
7.3.3.2 Publishing – Data
Publishing site XML will take place when there are changes in the layout or the metadata they contain. This also means that it is only necessary to publish site XML if this is amended in the metadata, or if new assets are published.
7.3.3.3 Automation of export
It is possible to set up a Channel folder so that it reacts with automatic export when assets are dropped into it. The following events are standard:
...
The "OnDrop_CreateCatalogExport" event can be used to advantage for, e.g. automatic exports based on templates. In practice this can mean that all assets that are dropped into this folder are automatically transcoded or converted, as well as transported to a specific destination.
7.4 System tools
7.4.1 Metadata
The setup of metadata is fundamental in Digizuite™ DAM Center. Metadata is used for both internal and external purposes. The metadata helps manage digital data. Metadata tells about the content of imported material and also the data that can be searched using the Digizuite™ DAM Center's search tool.
...
The following section is a list of the various metadata types used in and by the Digizuite™ DAM Center:
7.4.1.1 Language
Metadata is language dependent data which describes, categorizes and/or organizes assets. According to the setup, the metadata data structure can be different from language to language. At the bottom of the metadata window is the language tab that can be used to switch to the relevant language.
7.4.1.2 Validation
Validation of metadata data fields in the standard tab is controlled by the administrative setup. Validation helps you enter required metadata in the relevant fields, so that the metadata date agrees with the required data fields. In practice, this means that you enter the relevant metadata data and if you forget a required field, the system reminds the user which fields needs to be filled in.
7.4.1.3 Tree
Tree is a special type of metadata data which provides access to hierarchical divisions and markers. There are four different types of trees. According to administrative setup, these trees can be presented in four different ways. All four ways are compatible with each other, in other words, you can switch between the four different representations without losing data.
...
Note: all changes made here are only saved when you click on the Save button from the upper right side of the pop-up. If you forget to save your metadata, you will be warned of this when you try to navigate away from the relevant tab.
7.4.1.4 MultiComboBox
MultiComboBox is a type of metadata that allows you to select several values via a drop down list. The values are selected by clicking the '+' and can be deselected by clicking the '-'. All values are selected for amends by clicking '*'.
7.4.1.5 EditComboBox
The EditCombox provides the opportunity to add/edit values in the drop down list under editing asset metadata.
7.4.1.6 ItemReference
ItemReference is used to refer/connect one item with another. E.g. you can link items together by creating an ItemReference from an asset to a user/user group, or link a user and a transcoding together.
7.4.1.7 Unique
Information in the unique metadata field means only one asset in the Digizuite™ can have this particular metadata-information.
...
A Unique metadata fields is created and handled like any other metadata field and can be set as searchable by an administrator.
7.5.1 Setting up Metadata
7.5.1.1 Metagroups
Definitions of metagroups are located under System Tools → Metadata. Distribution of metadata takes place in metagroups. A metagroup is normally defined per asset type, e.g. one for video, one for images, one for audio and so on, but it is also possible to have one metagroup for all assets. By default this is labeled as All asset types and contains metafield information which relates to any type of asset such as title, description, date or keywords.
7.5.1.2 Subgroups
A metagroup can operate as a subgroup to another metagroup. A subgroup will be displayed as an extra tab in the metadata structure and can either be defined as iterative or simply as a division.
A subgroup must be added as a metafield in an existing metagroup. This defines the hierarchy. The iterative settings are indicated in the definition of the metafield. See more about this under the definition of metafields.
7.5.1.3 Static Fields
Field | Type | Description |
|---|---|---|
Title | Text | Obligatory fields. |
Reference | Text | Text. |
Description | Text | Text (>4000). |
Sort index | Integer | Sort index can be used in Portal. |
Source | Text | Source text for assets without source (see page 12). |
Identifier | Integer | Indicates the system identity (assettid). |
Keywords | Text | Imported data, e.g. keywords from PowerPoint files. |
It is possible to decide which statistics fields must be shown in the individual metagroup. It is also possible to state simple rules, such as, whether the group is write protected or visible, for example.
7.5.1.4 Metafields
Navigate to System Tools → Metadata → Asset → Shared → All asset types.
...
Field | Type | Description |
|---|---|---|
Name | Text | - |
Description | Text | - |
Max length | Integer | If indicated, this defines the max. number of characters in the field. |
Sort index | Integer | Indicates sorting of metafields. |
Plug-in | Text | Indicates the base name (-ext) for the .dll plug-in which must be imported with the metafield. |
Culture | Text | Indicates an SQL language culture (how characters, currencies and time are defined) which must apply for all language definitions that do not specifically indicate own culture. |
Required | Yes/No | Indicates whether the field is required when metadata is saved. |
System | Yes/No | Reserved. |
Show in list | Yes/No | Indicates whether the field can be displayed in the standard metadata tab as well as the search list. |
Read only | Yes/No | Indicates whether the field can be edited. |
Show Html editor for this field | Yes/No | Allows HTML/WYSIWYG editors in the field. Only applies to the 'Note' type. |
Metagroup | ComboBox | Indicates the metagroup. |
Validation function | ComboBox | Indicates a validation function which runs during validation. The setting applies for all language definitions which have not explicitly defined a validation. |
Restrict to assettype | Drop Down | Indicates the asset types for which the field should be displayed (standard all). |
Type | Drop Down | Indicates which type the field defines. |
7.5.1.5 Tree
The following fields are specific to the Tree field type:
Field | Type | Description |
|---|---|---|
Expand nodes | Yes/No | Indicates whether the user's standard presentation of a metadata tree in the editing function is with open nodes or not. |
Dynamic | Yes/No | Indicates whether the tree should be built dynamically. Thus only visible nodes are imported. |
Height | Integer | Indicates the height in pixels of the tree that will be run on the metadata tab. |
Tree format | ComboBox | Format which indicates how the data is represented in the standard tab.
|
7.5.1.6 DateTime
The following fields are specific to the field type DateTime:
Field | Type | Description |
|---|---|---|
Show support field | Yes/No | Indicates whether the field runs with an extra field for entering time. The time is indicated in the format hh:mm. |
7.5.1.7 Note
The following fields are specific to the field type Note:
Field | Type | Description |
|---|---|---|
Show HTML editor for this field | Yes/No | Indicates whether the field runs with the option of editing the content in an HTML editor. |
7.5.1.8 Reference
The following fields are specific to the field type Reference:
Field | Type | Description |
|---|---|---|
Reference | Text | Indicates the reference that the field defines. |
Format | Drop Down | Format specification. The format will be setup by House & Co. |
7.5.1.9 Item reference
The Master/Slave Item Reference field types are used to register relations between items in the Digizuite™ DAM Center. Master/Slave – Item References hang together in pairs, so that a Slave Item Reference locates the Master Item Reference that is its own opposite. This means that a Slave Item Reference can never exist alone.
Master Item Reference registers items that the actual item 'Refers to' while the Slave Item Reference registers the items that the actual item is 'Referred from'.
7.5.2 Setting up a Master/Slave Item Reference
The Master/Slave Item Reference is a way to have one item reference another in the metadata. There are many different types of items; assets, member and folders are all items to name a few.
...
Field | Description |
|---|---|
Item Type | This is a list with the different item types that can be set up as references (e.g. Asset, Member or Folder). It is effectively a filter, meaning that the chosen item type is the only thing that will be referenced in the field. |
Related ItemReference field | This field depends on whether we are editing a Master Item Reference field or a Slave Item Reference field. |
Filter on meta group | This is where the list of possible items that can be referred is filtered to the items that belongs to a specific metagroup. |
Lookup Label | This is where you can choose which 'Selection Text' will be displayed when editing the references on the metadata. It is a list of metafields that are available for the chosen Item Type (make sure that all the possible items that can be referenced has this metafield). If a reference label has not been selected, the system will use the Title or Name from the Item (e.g. asset title, member username, folder name). |
Select Mode | Drop Down and Text Box currently does the same thing. It displays the Master/Slave Item Reference as a MultiCombo field. |
Max selected items | This is where the maximum number of items that can be referred to is indicated. 0 (zero) is unlimited. |
Show only public items | The list of items that can be selected between will be limited to public items only. |
Only show groupes i am part of | Only does something with MemberGroup as the Item Type. It will filter the possible member groups to just those groups that the current user is a part of. |
Member filter | Member and MemberGroup only. This allows to filter on whether the item belongs to the frontend, backend or both. |
Filter on folder | Member, MemberGroup, MediaTranscode and MediaFormat only. This allows Master/Slave Item Reference to display only those items that resides in the chosen folder. |
Recursive folder filters | Only works with the above setting. If checked, the Folder filter will be extended to match subfolders as well. |
7.5.3 Language definitions
Navigate to System Tools → Metadata.
...
Field | Type | Description |
|---|---|---|
Name | Text | - |
Sort index | Integer | Indicates the sort index for language elements. |
Manifest | Yes/No | Indicates whether the language element appears as metadata in an export of the related asset. This field also applies for Portal exports. |
Public | Yes/No | Indicates whether the language element is displayed in renderings. |
Validation function | ComboBox | Indicates a validation function which runs during validation. This value controls the validation functions in the language independent metafield. |
Embed tag name | ||
View dependency regex | ||
XMP tag name |
7.5.4 Combo, MultiCombo and EditMultiCombo
Definitions Combo and MultiCombo:
Field | Type | Description |
|---|---|---|
ComboBox – Text | Text | Indicates the text that is displayed in a ComboBox option. This field only applies for ComboBox and MultiComboBox field types. |
ComboBox – Value | Text | Indicates the value that is registered in a ComboBox option. This field only applies to ComboBox and MultiComboBox field types. |
ComboBox – Sort | Integer | Indicates the sort index for a ComboBox option. |
Public | When a field is public, it will show up in other applications that gets a list of metafields. If not, it is only available internally in the DAM Center. | |
Visible | Hides the field from the editor, but keeps any data and still allows insert of data via BatchUpdate. | |
Rights | Opens the Item Security editor, enabling you to modify the individual members and member groups access to the metafield. |
7.5.5 Users and groups
Users and user groups for the Digizuite™ DAM Center are created, discontinued and edited in this folder. You can delete and create users and groups using the add button in the toolbar A new user is active after creation and has the same password as their username. A new group is also active after creation. Each user group is allocated rights in the system – roles that define which of the actions in the system the user can carry out.
7.5.5.1 Users
The standard tab administrates the following fields:
Field | Type | Description |
|---|---|---|
User name | Text | User's name in the system. |
Password | Text | Passwords are submitted as saved as MD5 encrypted. It is therefore impossible to read a password, only to re-set it. |
First name | Text | The first name of the member. Displayed instead of the user name sometimes. |
Lastname | Text | The last name of the member. Displayed together with the first name sometimes. |
Binding user name | Text | Used when integrating with AD. Typically this will not be set manually. |
Approved | Yes/No | A non-active user cannot log onto the system. |
Force DigiUpload | Yes/No | If active, the user cannot upload assets from the Digizuite™ DAM Center. Only from DigiUpload. |
Advanced upload | Yes/No | Provides access to advanced settings for web-upload, e.g. selection of metagroup. |
Show install DigiUpload | Shows a button in the upload dialog that enables the user to download DigiUpload. | |
Default metadata language | Drop Down | Indicates the standard metadata language for a user. In other words, the language tab that is selected as standard in a metadata view. If this is not selected, the value will default to a system selected Digizuite™ constant. |
Default system language | Drop Down | Indicates the standard application language. If this is not selected, the value will default to a system selected Digizuite™ constant. |
Groups | MultiComboBox | Indicates the allocated user groups. All roles, rights and transcode settings are inherited from these groups. Specific settings for the user override the settings from any groups. |
Roles | MultiComboBox | The roles that are specific to the individual user are specified here. Selections here override any roles in an attached group. |
7.5.5.2 Groups
This is where the system allocates local roles and users to a specific group. The following fields apply:
Field | Type | Description |
|---|---|---|
Group name | Text | Name for the group. |
Descriptive name | Text | |
Sortindex | Int | |
Approved | ||
Binding group name | Text | |
Advanced upload | Yes/No | Provides access to advanced settings for web-upload, e.g. selecting a metagroup. |
Default metadata language | Drop Down | Indicates the standard metadata language for a group. In other words, the language tab that is selected as standard in a metadata view. If this is not selected, the value will default to a system selected Digizuite™ constant. |
Default system language | Drop Down | Indicates the standard application language. (Defaults to a Digizuite™ constant) |
User | MultiComboBox | Indicates the allocated users. All roles, rights and transcode settings are inherited downwards to these users. Specific settings for the user override the settings from any group. |
Roles | MultiComboBox | The roles that are specific to the individual group are specified here. |
Binding group auto creation | Yes/No | If active, the specific group that is automatically connected to the group in an environment that uses Single Sign On (SSO), e.g. from a Microsoft Active Directory. In an SSO environment the users will, in practice, be created automatically upon their first access to the system. Rights, roles and transcode settings will thus automatically be inherited from the group that is marked in this field. Only one group with these properties can exist. |
Is Binding Group | The group should be used as an automatic reflection of an AD group. |
7.5.6 Profiles
The profiles define a collection of a destination and one or more transcode settings for an asset type. Profiles are typically allocated to a user or user group which thereby receives the option to export assets to administrator specified destinations and qualities. Profiles can thus also be used as pre-determined settings in a portal layout template.
...
Field | Type | Description |
|---|---|---|
Profile name | Text | - |
Asset type | Enum | Indicates the asset type. Cannot be edited after creation. |
Approved | Yes/No | Indicates whether the profile is displayed. |
Use format | Yes/No | |
Qualities | MultiComboBox | List of qualities (Transcode settings). |
7.5.7 Destinations
This folder indicates the destinations that can be used in, e.g. profiles or portal definitions. The Destinations are split into:
...
Field | Type | Description |
|---|---|---|
Name | Text | - |
Approved | Yes/No | Indicates whether the destination appears in the lists. |
Create transcode path | Yes/No | Indicates whether the system will create a transcode path for the destination. A transcode path is an asset determined name for a destination folder. The pre-fix is defined as 'DTC'. |
Destination type | Enum/Drop Down | Indicates the destination type. |
Outfilenamemask | Describes masks that are used for naming the exported files. |
7.5.8 Storage manager
The storage manager provides the Digizuite™ with a possibility to use multiple storage areas and thus keeping track of assets in all areas simultaneously.
...
Should one area run out of space, a Digizuite™ administrator can simply alter the designated storage or add additional storages as needed.In setups with large amounts of data, this provides for a safer and better organized storage setup while also minimizing load per storage-area thus providing a faster and better environment.
7.5.9 Media formats
The individual formats that can be used in the qualities are defined in this folder. The formats are defined from the system-specified base formats or format types. Base formats are not covered in this manual.
...
Note: Transcodings are often carried out from an encoder profile which defines the quality. It is still important to complete all of the above fields correctly even if it is only a copy of the profile's data. The fields also appear in the manifests and can therefore prove to be extremely useful for identification and further processing of exported assets.
7.5.10 Transcode settings
Transcode settings that link formats with a DigiBatch program chain (Progid) and possibly a destination are administered in this folder.
...
Field | Type | Description |
|---|---|---|
Alias | Text | - |
| Text | - |
| Drop Down | Indicates which source format(s) the setting applies to. |
Target format | Indicates which target format(s) the setting applies to. | |
Progid | Enum/Drop Down | Indicates the progid that will be run.ProgID is an identifier primarily for House & Co job types. |
Destinations | MultiComboBox | Indicates the destination(s) for the job. Only necessary if you want to override the normal destinations. E.g. in portal templates or use transcode settings. |
Dynamic source | DropDown | Indicates which source the transcoding/conversion is dependent on. The settings therefore define an inherent dependency between elements of transcode settings. |
Prefix | Text | Specifies a prefix text that will be set for all exports from this setting. |
Export manifest | Yes/No | Indicates whether the setting will export a manifest with the qualities. |
7.5.11 Config Manager
Configuration of the DAM Center and the other additional products is fundamental in order to use any of the products. Therefore the Config Manager was thought to help at easily configuring all the licensed Digizuite products:
...
Each product has beneath its menu tree a configuration version.
7.5.11.1 ConfigManager functionalities
7.5.11.2 Labels
Gives you the possibility of adding new labels to the selected product, edit old labels, and also organize them into folders and subfolders.
Note: in order to save the changes you have to press the Save button.
7.5.11.3 Porduct URLs
This tab is empty as default, but new fields can be added to it in the Metadata section. For example, you just installed a new Media Manager, and you want the URL to be saved in the DAM Center. First, you add a new URL metafield (the name could be "Media Manager") to the Product Urls metagroup in the metadata section. Then you go to the ConfigManager, and enter the URL in the field and save it. You can now always find the URL to the Media Manager from the DAM Center.
Note: in order to save the changes you have to press the Save button.
7.5.11.4 Config Parameters
The fields displayed here varies depending on the current product being configured. In the DAM Center, the following options are present:
...
Note: in order to save the changes you have to press the Save button.
7.5.11.5 Profiles & Destinations
Add as many folders as you need and inside them define a profile with a corresponding destination. The drop down menu will show the available configurations that can be assigned.
Note: in order to save the changes you have to press the Save button.
7.5.11.6 Searches
Add new search criterias by defining a customized search XML.
Note: in order to save the changes you have to press the Save button.
7.5.11.7 Create new version
At any time when a new configuration has been added, edited or deleted, a new version can be created. In addition to this, you can switch from the old version to the new one and vice-versa.
7.5.11.8 Menu
The Menu comes with 3 functionalities:
- Compare – compare different versions and get an overview of the changes done
- Version information – gives an overview of the current version
7.5.11.9 Language
Different language selection is possible if the DAM Center was installed to support multiple languages. You can choose between:
- Danish
- English
- German
- Swedish
7.5.12 Templates
The format for a template is XML. The templates attempt to connect an asset type together with a destination and a profile. This opens the possibility for automatic exports, which is just the concept for distributing layouts. The XML looks for a template that is relevant for the folder you are in. This continues the search through the folder structure and stops at the first relevant master template that allows automatic export. If it doesn't find a master template, it takes the template it finds, which is located as close to the root directory as possible.
...
A template can be linked to any object in the channel, both folders and assets. This way, a truly complex structure is achieved, as objects without template references automatically inherit the settings. Templates can be edited directly in XML format, or controlled using the functions that apply for the individual metadata language definitions. For example, the following templates are displayed:
7.5.12.1 Channel template
The below XML displays which language values will be displayed in the channel when you mark an asset:
...
The definition is also used for exporting the manifest from the layout. In other words, only metadata is specified in the template that appears in the manifest. The manifest provides the basis for content and intentions with the export. The example here defines the export using the profile id=19, to the destination with id=6 and designates the ID for the general metagroup, as well as which field id's are affected.
7.5.12.2 Licenses
The installed licenses are administered in this folder. When you receive a new or updated license, this only needs to be entered in the correct license type. License type, license conditions, etc. are coded in the actual key.
7.5.12.3 Format types
The area for format types classifies the different types of media by things like mime type and extension. This is for the advanced user only and does generally not need to be changed.
7.5.12.4 Status
The status section of system tools lists all the active status plugins in the DAM Center. A status plugin monitors a specific part of the DAM Center. Examples of features monitored by status plugins for the DAM Center:
...
Generally you will not need to modify these, as they come with a standard configuration that should work for most cases. The Status Detail page on /statusdetail.aspx uses the status plugins to determine the data.
7.5.12.5 Workflow / Wizard
This section displays a list of installed workflow plugins (see section 9.2 for a description of each of the plugins). By selecting them in the list you can modify and delete existing configured instances, or you can add new ones. Setting up these plugins is only recommended for the advanced user; however the Wizard function makes creating the most typical workflows a lot easier.
...
The Wizard allows you to set up two of the most commonly used workflows, an Approval workflow and an Upload workflow:
7.5.12.5.1 Approval workflow
This workflow activates when a chosen bit field has its value set to 1 (when a user sets a checkmark in the chosen checkbox). The activated workflow can be one of the three following actions: Publish the asset for every channel it belongs to; move the asset to a chosen catalog folder; or move the asset to a chosen channel folder. Note that unchecking the bit field does not revert the action.
7.5.12.5.2 Upload workflow
The upload workflow periodically (determined by the Survey Period, defaults to 60 seconds) looks for files on a specific UNC-path, optionally filtered by file type (defaults to *.*). When a file is found, it is uploaded to the DAM Center and applies the metafieldgroup defined in the field Metafieldgroup for new assets (defaults to All asset types). If a metadata text field is selected in the UNC Path Metafield field, this field will contain the UNC path of the uploaded asset. An Approval workflow can be configured for when the asset is uploaded.
7.5.12.6 Search stop words
In this section you can add and remove search stop words. A search stop word is text that will be excluded by the search engine. This will typically be words that are used often when searching, but are irrelevant for the search engine. Note that you can see the numbers 0-9 and the entire alphabet in the list. One may think that this will exclude all text you can possibly write, but this is not the case. These numbers and letters will only be excluded if they appear as a "word", meaning they are separated from other text with a space.
7.5.12.7 Digizuite configuration
Here you will find a very comprehensive list of configuration parameters used internally by the DAM Center. These all come pre-configured and there is rarely a need to edit these
...