In the following section we will go through the four main areas of the DigizuiteTM DAM Center:
- Running jobs
- Catalog
- Channels
- System tools
...
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.
To view Running jobs a DigiZuite™ user needs to have at least 1 (or more) of the following Running Jobs-roles assigned to his profile (or be part of a group that has the roles).
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.
...
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.
...
Importing assets can be done either manually or as a batch process automated by the DigiZuite™ DAM Center.
There are two manual ways and an automated process that helps at importing assets into the system.
- DigiZuite™ importer
- DigiZuite™ DigiUpload
- UNC Batchingest (automated)
DIGIZUITETM DAM CENTER IMPORTER
...
Digizuitetm digiupload Different rules can apply for different workflows. It is recommended to use DigiUpload for uploads over 100 Mb. Documentation for DigiUpload is covered in a separate document.
DigiZuite™ DigiUpload is a stand-alone client program which allows you to import assets from a remote location. In order to utilize the DigiZuite™ DigiUpload, the client must be installed first. Installation of the DigiZuite™ DigiUpload can be done from within the DigiZuite™ importer or by stand-alone installer.
The program utilizes several important key points from the standard importer in the DigiZuite™ DAM Center and even adds a few extra:
- DigiUpload can re-start import processes. This means, if connection fails due to technical obstructions, active uploads can be resumed from the DigiUpload client.
- DigiUpload can specify metadata in advance and also works with required fields, to enforce and ensure uniform workflows.
- DigiUpload can be used as a standalone client for users with a desired need only to upload and otherwise no further access to the DigiZuite™ DAM Center.
- Works with custom designed workflows.
DigiZuitetm DAM Center import Automated ingest workflows are custom designed based on feature-requests and technology. Please consult a DigiZuite administrator or the House & Co support team for further information.
File monitoring is a third possibility for importing material in the DigiZuite™ DAM Center. Using plug-ins, the DigiZuite™ can be configured to inspect a given UNC path, in which files will be imported to DigiZuite™.
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.
...
Note: The asset versioning can be enable on any metadata required (title, description, keywords, etc.)
To enable the replace-asset feature, the following DigiZuite™ constants must be present and configured as listed below. (Changes should be made only by an administrator)
Name / Value
DigiZuite_System_AssetReplacer_Search1/DigiZuite_System_AssetReplacer_Search1
DigiZuite_System_AssetReplacer_Search2/DigiZuite_System_AssetReplacer_Search2
Furthermore, the active system configuration determines the replace-logic and updates the archives where the asset is being used. To fully utilize this feature, an administrator needs to review the present system configuration, but also define the extend of the feature by assigning individual roles to each users / user groups.
...
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.
...
The DigiZuiteTM 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.
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:
SEARCH_GOOGLE
SEARCH_GOOGLE_TERMTYPE
- Value should be set to 1, 2 or 3
- Inflectional = 1, Thesaurus = 2, Exact = 3
Filter options
The filter options is configurable. The following fields are defined as standard in the new DAM Center:
- Asset type
- Upload date
- Free text
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.
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.
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.
...
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.
Folder permissions is based on a Linux folder structure, which allows for distinction between read- and write (edit) permissions either on a folder structure or individual folders.
Understanding how to work with folder permissions, requires a basic understanding of how the permissions are set and changed.
When creating a new folder, the rights are automatically inherited from the parent.
...
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.
Below you can see an example of a DAM Center with many channels:
An administrator will typically create the first level and assign metadata templates to this folder. The rights are inherited automatically by all assets in the channel. Templates are attached to the main folder (see section Error! Reference source not found. for more on templates).
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.
...
In order to place an asset in a layout, simply drag it into the requested folder in the Channels area. In this way a reference from an asset in the Catalog area to a layout folder is created.
...
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.
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.
References
References can be defined by all objects in a layout and refer to all objects. In order to create a reference for an object, select the object's 'layout' tab. Then click the 'Create new reference' button.
The system is now in a particular "reference position" where navigation is possible in all the layout folders. To select a reference, double click on the required object, when type and alias/title are shown on the list of references. Exactly the same as when you cut a new video. If you change your mind about a reference, this can be deleted using the small red cross against each reference line.
When you have finished creating references, click "End reference position" and the navigation will return to normal.
Standard tab
The 'standard' tab defines the following fields:
...
Field
...
Type
...
Name
...
Text string
...
Browser text
...
Text string
...
Status bar text
...
Text string
...
Node headline
...
Text string
...
Node text
...
Text
...
Url
...
Text string
...
Sort index
...
Integer
...
Frame target
...
Text string
...
Parameter
...
Text string
...
Meta keywords
...
Text
...
Meta description
...
Text
...
Layout tab
The 'layout' tab defines the following fields:
...
Field
...
Type
...
Description/format
...
Templates
...
MultiComboBox
...
The list of templates which work with the selected object and all subobjects, if there are any (folder).
...
Events
...
MultiComboBox
...
Only folder.List of events which affect the folder. See more in the 'Automation of exports' folder.
...
Public
...
Yes/No
...
States whether the asset is publicly available.
...
Visible
...
Yes/No
...
States whether the asset is available visually.
...
Never expires
...
Yes/No
...
States whether the asset has an expiry date.
...
Start date
...
Date
...
Dating starts with the asset's availability.
...
End date
...
Date
...
Dating stops with the asset's availability.
...
Start time
...
Text string
...
Shows the start time point in the format: 00:00:00.
...
End time
...
Text string
...
Shows the end time point in the format: 00:00:00.
...
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.
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.
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.
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:
- OnDrop_CreatecatalogReferenceThe event creates a reference to the asset(s) which are dropped into the folder.
- OnDrop_CreateCatalogExportThe event exports the asset(s) which are dropped into the folder based on the templates which affect the folder.
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.
...
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.
Note: In order to have the Workflow functionality access or alter metadata, it is required that the "System" user has the required access to the specific metadata field. For example if you want to upload asset to a menu item in DigiZuite™ Video Portal or DigiZuite™ Media Manager, it is required that the System user has read and write access to the underlying Tree metadata field structure.
The following section is a list of the various metadata types used in and by the DigiZuite™ DAM Center:
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.
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.
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.
The figure below shows an example of a hierarchical metadata tree structure:
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.
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 '*'.
EditComboBox
The EditCombox provides the opportunity to add/edit values in the drop down list under editing asset metadata.
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.
Unique
Information in the unique metadata field means only one asset in the DigiZuite™ can have this particular metadata-information.
The unique metadata field is editable by users and can be used for specific validation features on assets, e.g. a part- or serial number within a production line. Only one asset in the DigiZuite™ can carry this certain number or label, rendering it as unique. Any attempts to set a label with the same unique value as another asset will result in a failure.
A Unique metadata fields is created and handled like any other metadata field and can be set as searchable by an administrator.
...
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.
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.
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.
When you select, for instance WebTV, you will have an overview of which metagroups have been created. If you click on one of these groups, you will receive more detailed information about the setup of the metagroups.
Metafields
Navigate to System Tools → Metadata → _Asset → Shared → All asset types{_}.
A metafield is a definition type of a specific metadata element. When you create a metafield you must indicate which type the metafield will be defined. The following types are standard in DigiZuite™ DAM Center:
...
NamE
...
Type
...
Description/format
...
Int
...
Integer
...
-
...
String
...
Text string
...
Max. 4000 characters (DB)
...
Bit
...
Yes/No
...
-
...
Money
...
Currency
...
-
...
DateTime
...
Date and/or time
...
Date field read only, i.e. you can only enter data via the inbuilt calendar. Can be indicated using the support field for the time specification in the format 00:00:00.
...
Metagroup
...
MetagroupOwn tab
...
Used in connection with subgroups.
...
MultiComboValues
...
MultiComboBox
...
Drop down field with the opportunity to select more options from the list. The bottom list shows the options that are selected. Select the options by selecting the option in the top drop down list and clicking the 'plus' button. De-select options by marking them in the bottom list and clicking the 'minus' button.
...
ComboValue
...
ComboBox
...
The traditional drop down which allows selection of only one option.
...
EditComboValue
...
ComboBox
...
Drop down list that allows you to create new, or change existing values under editing asset metadata.
...
Note
...
Notes field
...
Unlimited amount of text data. Can have a WYSIWYG editor attached.
...
Tree
...
Tree
...
Tree structure. Four different representations are possible, according to the configuration.
...
Link
...
Text string
...
Fields which run a link-button function.
...
Master Itemreference
...
...
Master Item Reference registers Items that the actual item 'refers to'.
...
Slave ItemReference
...
...
Slave Item Reference, locates the Master Reference Item that is its own opposite
Administration of metafields consists of some standard settings for representation and validation as well as definition of one or more language elements. Each individual language has its own tab in the metafield. You can create metafields by filling in the relevant information.
The following standard fields define a metafield:
...
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.
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
...
- Tree view – only selectedOnly the selected nodes and their paths are displayed.
- Tree view – entire treeThe whole tree is displayed with all the selected nodes marked.
- List view – only selectedThe selected nodes are displayed as lists.
- List view – full pathThe selected nodes and their paths are displayed as lists.
- List view - only one selected.
- List view – full path only one selected.
...
...
...
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. |
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. |
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. |
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'.
...
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.
For example, let us say that you want to associate one (or more) authors with a PDF-file. One way to solve this would be to create a combo field with the authors' names, and then select the desired author when editing the metadata for the PDF-file. This will work fine on a basic level, but as soon as we need more data and/or functionality regarding the author, the Master/Slave Item Reference is a better choice. Let us say that the authors exist in the DAM Center as members, and are part of the member group "Authors". Instead of creating a combo field and manually typing in the names, we can create a Master/Slave Item Reference that allows us to reference these "Authors" directly when editing the metadata for the asset. This has several advantages, among others:
- The PDF-file has a direct coupling with the members and the members' metadata. We can use this in other contexts (another application), for example to provide write access to only the authors of the PDF-file or show an author's nickname next to the PDF-file.
- When later adding a new member to the "Authors" group, it will automatically be available as a choice when specifying authors in the PDF-file's metadata. This is especially handy when dealing with Active Directory synchronization and large amounts of members.
This is just one of many use cases. The Master/Slave Item Reference is already used in the DAM Center, such as to enable a member to save their favorite assets (Member/Asset reference) or when specifying which asset qualities a specific member group can download (MemberGroup/MediaTranscode reference).
To clarify, the Master/Slave Item Reference consists of two different metafields, the Master Item Reference and the Slave Item Reference. A Master Item Reference can exist without a Slave Item Reference, but not vice versa. If we take the above example with the PDF-file, it will work with just a Master Item Reference. But if we want to be able to see all the different PDF-files that a specific member is the author of – then we need to set up a slave item reference on the member metadata. This Slave Item Reference must then point to the Master Item Reference.
The special setup block as shown on the next page appears in the Label Editing tab, when the label is created (left is Master Item Reference, right is Slave Item Reference). Note that there are additional fields for certain Item Types - those are described further below.
Example of a Master Item Reference setup: Example of a Slave Item Reference setup:
...
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.
The item type can also be set to Undefined, which means that all item types are valid and can be referenced in the field.
...
Related ItemReference 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.
...
Navigate to System Tools → Metadata
The individual language definitions are the elements which determine the metafield's representation in the system. You thereby indicate the name and location of the metafield here. The following fields are defined by a language value:
...
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
...
...
...
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.
...
Local 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.
Roles
The DigiZuite™ DAM Center uses the concept of roles for the general user control. The system contains some standard roles, each of which has specific importance for what the user can do in the system.
...
Roles
...
Description
...
Editor_Catalogs
...
Access to the catalog folders
...
Editor_Old_Interface
...
User has access to the pre 4.0 DAM Center
...
Editor_Portal
...
Has access to channel folders. Can issue and amend data in channels.
...
Editor_SystemTools_AllwaysAllowItemSecurityEdit
...
Gives the user read access to all items and the possibility to always edit rights for these items.
...
Editor_SystemTools_Config
...
Has access to the Config manager
...
Editor_SystemTools_Dam
...
Has access to the DAM administration (Metadata).
...
Editor_SystemTools_Destinations
...
Has access to Destinations.
...
Editor_SystemTools_DigizuiteConfig
...
Has access to allow configuration.
...
Editor_SystemTools_License
...
Admin Rights for License
...
Editor_SystemTools_MediaFormat
...
Can access the Media formats.
...
Editor_SystemTools_MediaFormatType
...
Admin rights for format types
...
Editor_SystemTools_Metadata
...
Can configure the Metadata fields and groups
...
Editor_SystemTools_MetaDataLanguage
...
Admin rights for MataDataLanguages
...
Editor_SystemTools_PlayerTemplate
...
Admin Rights for PlayerTemplates
...
Editor_SystemTools_Profiles
...
Can see and edit profiles.
...
Editor_SystemTools_Status
...
Admin Rights for Status
...
Editor_SystemTools_Stopwords
...
Admin Rights for Stopwords
...
Editor_SystemTools_TranscodeSetting
...
Can see and edit transcode Settings.
...
Editor_SystemTools_UserManager_Groups
...
Can see and edit local and frontend groups
...
Editor_SystemTools_UserManager_Users
...
Can see and edit local and frontend users
...
Editor_SystemTools_Wizard
...
Admin Rights for Wizard
...
Editor_SystemTools_Workflow
...
Admin Rights for Workflow
...
RunningJobs_AdminViewSubmitXML
...
Controls whether the user has the right to see the JobChain xml for the selected job.
...
RunningJobs_ChangePriority
...
Controls whether the user has the right to change the priority of a running JobChain.
...
RunningJobs_EditAll
...
Controls whether the user has the right to modify in any running jobs.
...
RunningJobs_EditOwn
...
Controls whether the user has the right to change the job he has started.
...
RunningJobs_View
...
Controls whether the user has the right to see his running jobs.
...
Controls whether the user has the right to see all running jobs.
...
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.
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.
...
Users and user groups for the portal(s) are created, discontinued and edited in this folder. You can delete and create users and groups using the related icons in the top bar. A new user is not active after creation and has the same password as their username. A new group is not active.
Frontend users
The following fields are administrated for frontend users:
...
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
...
-
...
Lastname
...
Text
...
-
...
Binding user name
...
Text
...
-
...
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
...
...
...
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.
Frontend Groups
This is where the system allocates 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
...
In the following section we will go through the four main areas of the DigizuiteTM DAM Center:
- 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.
To view Running jobs a Digizuite™ user needs to have at least 1 (or more) of the following Running Jobs-roles assigned to his profile (or be part of a group that has the roles).
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 importing multiple files, all files are ingested as individual assets. Importing assets to the Digizuite™ is simple and requires only a valid Digizuite™ username. (User must have upload access)
Importing new assets can be done by right clicking on the desired folder from Catalog. From the opened menu select Import to folder and the importer will be available. You can also edit metadata information for each asset before importing it.
Selecting Begin upload initiates the import of files. During import, the metadata editor is locked and no further metadata can be added / removed.
It is possible to minimize the upload window once the upload has been initiated. To do this, click on the minimize icon in the top right area of the upload window. This will minimize the window and show the process in the top bar of the DAM Center. You may then continue to work with the DAM Center while the upload is in progress (the DAM Center may slow down when uploading large files).
Once complete, the batch system ingests all selected files as assets. Imported files are placed in the selected folder. During processing, files and status can be monitored from the Running jobs menu.
Required Fields
The Digizuite™ has a feature – Required fields. This feature allows for a Digizuite™ SuperUser or administrator to mark one or more metadata fields as required on upload. If not filled in correctly, upload fails. Selecting a metadata field as required can be done through the DAM Console.
There is no limit to what kind of metadata fields or how many of them can be marked as required – any type of metadata field can be set as required, e.g. title, description, language, date, keywords, custom metadata fields etc.
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.
File monitoring is a third possibility for importing material in the Digizuite™ DAM Center. Using plug-ins, the Digizuite™ can be configured to inspect a given UNC path, in which files will be imported to Digizuite™.
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.
The replace-asset feature allows assets to be versioned during upload. When enabled, and if an asset with a title exact equal to a previously uploaded assets is located, the uploader is prompted to decide whether to replace existing asset (hence creating a new version but with same unique ID number), or instead upload the asset as new asset.
Note: The asset versioning can be enable on any metadata required (title, description, keywords, etc.)
To enable the replace-asset feature please follow this guide: /wiki/spaces/DD/pages/42303700.
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:
- Asset type
- Upload date
- Free text
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 /wiki/spaces/DD/pages/42303706 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.
Folder permissions is based on a Linux folder structure, which allows for distinction between read and write (edit) permissions either on a folder structure or individual folders.
Understanding how to work with folder permissions, requires a basic understanding of how the permissions are set and changed.
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.
Below you can see an example of a DAM Center with many channels:
An administrator will typically create the first level and assign metadata templates to this folder. The rights are inherited automatically by all assets in the channel. Templates are attached to the main folder.
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:
Field | Type |
|---|---|
Name | Text string |
Browser text | Text string |
Status bar text | Text string |
Node headline | Text string |
Node text | Text |
Url | Text string |
Sort index | Integer |
Frame target | Text string |
Parameter | Text string |
Meta keywords | Text |
Meta description | Text |
Note: These are language dependent.
7.3.2.3 Layout tab
The Layout tab usually defines the following fields:
Field | Type | Description/format |
|---|---|---|
Templates | MultiComboBox | The list of templates which work with the selected object and all subobjects, if there are any (folder). |
Events | MultiComboBox | Only folder.List of events which affect the folder. See more in the 'Automation of exports' folder. |
Public | Yes/No | States whether the asset is publicly available. |
Visible | Yes/No | States whether the asset is available visually. |
Never expires | Yes/No | States whether the asset has an expiry date. |
Start date | Date | Dating starts with the asset's availability. |
End date | Date | Dating stops with the asset's availability. |
Start time | Text string | Shows the start time point in the format: 00:00:00. |
End time | Text string | Shows the end time point in the format: 00:00:00. |
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:
- OnDrop_CreatecatalogReferenceThe event creates a reference to the asset(s) which are dropped into the folder.
- OnDrop_CreateCatalogExportThe event exports the asset(s) which are dropped into the folder based on the templates which affect the folder.
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.
Note: In order to have the workflow functionality access or alter metadata, it is required that the system user has the required access to the specific metadata field. For example if you want to upload asset to a menu item in Digizuite™ Video Portal or Digizuite™ Media Manager, it is required that the System user has read and write access to the underlying tree metadata field structure.
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.
The figure below shows an example of a hierarchical metadata tree structure:
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.
The unique metadata field is editable by users and can be used for specific validation features on assets, e.g. a part- or serial number within a production line. Only one asset in the Digizuite™ can carry this certain number or label, rendering it as unique. Any attempts to set a label with the same unique value as another asset will result in a failure.
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.
A metafield is a definition type of a specific metadata element. When you create a metafield you must indicate which type the metafield will be defined. The following types are standard in Digizuite™ DAM Center:
Name | Type | Description / Format |
|---|---|---|
Int | Integer | - |
String | Text string | Max. 4000 characters (DB) |
Bit | Yes/No | - |
Money | Currency | - |
DateTime | Date and/or time | Date field read only, i.e. you can only enter data via the inbuilt calendar. Can be indicated using the support field for the time specification in the format 00:00:00. |
Metagroup | MetagroupOwn tab | Used in connection with subgroups. |
MultiComboValues | MultiComboBox | Drop down field with the opportunity to select more options from the list. The bottom list shows the options that are selected. Select the options by selecting the option in the top drop down list and clicking the 'plus' button. De-select options by marking them in the bottom list and clicking the 'minus' button. |
ComboValue | ComboBox | The traditional drop down which allows selection of only one option. |
EditComboValue | ComboBox | Drop down list that allows you to create new, or change existing values under editing asset metadata. |
Note | Notes field | Unlimited amount of text data. Can have a WYSIWYG editor attached. |
Tree | Tree | Tree structure. Four different representations are possible, according to the configuration. |
Link | Text string | Fields which run a link-button function. |
Master Itemreference | Master Item Reference registers Items that the actual item 'refers to'. | |
Slave ItemReference | Slave Item Reference, locates the Master Reference Item that is its own opposite |
Administration of metafields consists of some standard settings for representation and validation as well as definition of one or more language elements. Each individual language has its own tab in the metafield. You can create metafields by filling in the relevant information.
The following standard fields define a metafield:
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.
For example, let us say that you want to associate one (or more) authors with a PDF-file. One way to solve this would be to create a combo field with the authors' names, and then select the desired author when editing the metadata for the PDF-file. This will work fine on a basic level, but as soon as we need more data and/or functionality regarding the author, the Master/Slave Item Reference is a better choice. Let us say that the authors exist in the DAM Center as members, and are part of the member group "Authors". Instead of creating a combo field and manually typing in the names, we can create a Master/Slave Item Reference that allows us to reference these "Authors" directly when editing the metadata for the asset. This has several advantages, among others:
- The PDF-file has a direct coupling with the members and the members' metadata. We can use this in other contexts (another application), for example to provide write access to only the authors of the PDF-file or show an author's nickname next to the PDF-file.
- When later adding a new member to the "Authors" group, it will automatically be available as a choice when specifying authors in the PDF-file's metadata. This is especially handy when dealing with Active Directory synchronization and large amounts of members.
This is just one of many use cases. The Master/Slave Item Reference is already used in the DAM Center, such as to enable a member to save their favorite assets (Member/Asset reference) or when specifying which asset qualities a specific member group can download (MemberGroup/MediaTranscode reference).
To clarify, the Master/Slave Item Reference consists of two different metafields, the Master Item Reference and the Slave Item Reference. A Master Item Reference can exist without a Slave Item Reference, but not vice versa. If we take the above example with the PDF-file, it will work with just a Master Item Reference. But if we want to be able to see all the different PDF-files that a specific member is the author of – then we need to set up a slave item reference on the member metadata. This Slave Item Reference must then point to the Master Item Reference.
The special setup block as shown on the next page appears in the Label Editing tab, when the label is created (left is Master Item Reference, right is Slave Item Reference). Note that there are additional fields for certain Item Types - those are described further below.
Example of a Master Item Reference setup: Example of a Slave Item Reference setup:
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.
The individual language definitions are the elements which determine the metafield's representation in the system. You thereby indicate the name and location of the metafield here. The following fields are defined by a language value:
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. |
...
...
...
...
...
...
...
...
...
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
...
...
...
...
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.
...
...
Field
...
...
Type
...
...
Description
...
...
Group name
...
...
Text
...
...
-
...
...
Standard system language
...
...
Drop Down
...
...
...
User
...
...
MultiComboBox
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
The storage manager can help ensure that the
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
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:
- Updating the title of the DAM Center
- Change the product's default language
- Set-up how many assets per page
- …and so on
All the configuration parameters represent basic configuration that can be done to the installed products to suit your needs.
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
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...