Includes information on various plug-ins, as well as examples of XML, searches and more.
8.1 Adaptive Bitrate
Digizuite™ DAM Center comes with support for Adaptive Bitrate for video playback. This is done using industry standard Synchronized Multimedia Integration Language (SMIL) files. You can setup any quality combination in the Adaptive Bitrate HQ profile or create your own. The system comes predefined with the following bitrates that matches current industry recommendations:
...
Video width is calculated to keep aspect ratio and frame-rate is defined by the source.
8.2 Plug-ins
Digizuite™ DAM Center contains a number of different plug-ins which increase automation and make the workflow easier.
Plug-in Name | Description | Assumptions |
|---|---|---|
ItemWatcher | The plug-in inspects all events from DigiMonitor, which it subscribes to. Upon receipt, validation is carried out based on the instance's criteria and if OK a new user defined event is sent with the category/type you want to receiving plug-in(s) to manage. | DigiMonitor |
ItemHandler | The plug-in is used to send events to display values for the given metadata. | DigiMonitor |
AutoPublish | Publishes site XML after all assets in a layout structure are published. | DigiMonitor |
DigiFileWatcher | Inspects a folder structure and sends events when a change has taken place in the folder. Can be set to wait a certain time between the last activity and sending the event. | DigiMonitor |
DigiFileWatcherHandler | Takes a file from a library and uploads via the upload web service to Digizuite™ DAM Center. Can also merge an audio file with a video file during the upload. | DigiMonitor |
FlipFactory | Manages uploads and publication of assets where FlipFactory (3rd part SW) is used as the transcode engine. | DigiMonitor FlipFactory Service |
FolderMaintenance | Takes care of holding two folder structures in sync. | DigiMonitor |
ImportSRTSubtitle | Imports an SRT file, such as an EDL list and attaches the EDL list to the relevant asset. | DigiMonitor |
LiveRecord | Records a live stream and reels in the stream assets in Digizuite™ DAM Center. These assets can have metadata completed from live Assets metadata, the asset can therefore be published to a given portal extremely quickly after live streaming. | DigiMonitor |
LiveAsset | Records a live stream and reels in the stream assets in Digizuite™ DAM Center. These assets can have metadata completed from live Assets metadata, the asset can therefore be published to a given portal extremely quickly after live streaming. | DigiMonitor |
MemberSynch | When a local user is created, an ftp and ftp user are created with the same name and password as for the local user. If the password is changed for one of the users, then the plug-in ensures that this is changed for the other as well. | DigiMonitor |
RegexTitleToMetadata | Transfer parts of an asset's title to a metadata field. | DigiMonitor |
SendMail | For sending e-mails when one or more of the assets are dropped into a given folder. The plug-ins generates events on the basis of rules. | DigiMonitor |
SqlMonitor | Responsible for monitoring the database. A requirement for most of the above to work. | DigiMonitor |
IngestImporter_XML2Metadata | Imports file, if there is also a corresponding XML file for a given file, which contains the file's metadata. This metadata will be loaded into Digizuite™ DAM Center. | DigiMonitor |
IngestImporter_HttpReq2metadata | Imports file. Does this directly after an http has called to receive metadata. This data in imported in Digizuite™ DAM Center 's metadata structure. | DigiMonitor |
IngestImporter_DB2Metadata | Imports file. Then calls a database to collect metadata to import into Digizuite™ DAM Center's metadata structure. | DigiMonitor |
IngestImporter_FolderToFolder | Imports file. Takes the folder structure in which the file is located and includes, for example, DAM Catalogs. | DigiMonitor |
AssetHandler_MoveByRegex | Move assets around based on masks against the assets title of some metadata. | DigiMonitor |
IngestImporter_Splitter | Take a file and split it into its component parts. Then take these files and import to Digizuite via another hot folder. | DigiMonitor |
AssetSyncFolder | Hold two folder structures in sync with assets. | DigiMonitor |
AdMetadataSynch | Take data from AD and place it in a metadata field. | DigiMonitor |
8.3 Examples
8.3.1 Format XML for mapping metadata to job properties.
This example covers the XML format field. The following XML shows how the XML format on media format pages could appear.
...
All reserved words are case sensitive, which means that the above examples must be written in lowercase as shown.
8.3.1.1 Setting up Master/Slave Item Reference
For this example, we would like to be able to reference which employees appear in an image (also known as tagging people in an image). We start off with creating a new Master Item Reference field called Employees on Picture. For the sake of this test, let us say that we have a CompanyPhoto metagroup, a metagroup that is applied to all company pictures. We will be creating the field on this metagroup. The below screenshot shows the create dialog:
...
Under the Metafield Label tab, we change the Item Type to member (because our employees are members in the DAM Center and we want to reference them):
8.3.1.1.1 Filter on Metagroup
This field is changed to point to the EmployeeInfo metagroup, as our Employee members belongs to this metagroup. This will make sure that we cannot select members that are not employees.
8.3.1.1.2 Lookup label
This field controls what will be displayed when a reference is selected in the metadata. If nothing is selected here, the title of the referenced item will be displayed. In this example with our employees, their Username will be displayed if we do not choose otherwise in the combo field.
8.3.1.1.3 Max selected items
We keep this value as 0 (unlimited), as we do not have a requirement for how many employees that can be tagged in a picture. If we were instead doing this for profile images (where we know that there will ever only be one employee on a picture), it would make sense to set the Max selected items to 1.
8.3.1.2 Setting up Master/Slave Item Reference
Now we have the possibility to reference employees when editing the metadata for images. But we also want to be able to look up a member (an employee) and see all the images that this employee is referenced in. To do this we need the Slave Item Reference. First we create a Slave Item Reference on our "EmployeeInfo" metagroup:
...
Now that we have the general setup done, we switch to the language tab and enter the following (if a field is not mentioned it means that there was no need to change it).
8.3.1.2.1 Item Type
Here we choose Asset as the Item Type, as we are referencing the images that the employees appear in:
8.3.1.2.2 Related ItemReference field
Here we choose the Master Item Reference that we created previously called "Employees on Picture". For the Slave Item Reference, this field is required, as they cannot exist without a Master Item Reference.
8.3.1.2.3 Lookup label
This label governs what will be displayed, when a reference is selected. If nothing is selected, the title of the item selected is displayed (asset title in this case). We choose to display the "Image Title" instead, which is a custom metafield we created for company photos:
This is the end of the configuration of our Master/Slave Item Reference fields and it is now possible to add references to employees in all company photos.
8.3.2 Text search
8.3.2.1 Free text search
You should generally avoid free text searches as the metadata structure allows you to easily specify more accurate searches with more accurate and therefore also more useable results. If more than one word is indicated in a free text search the system will assume that you want to search for the combination in all metadata fields. If, for example, you use 'Hollywood Greats' in the free text field, the search will only return assets that have these two words in a given metadata, as the title or description. It will therefore not return assets which have the words 'Greats' in the title and 'Hollywood' in the description. You are then required to be more specific, e.g. search for the word 'Greats' in the free text field and the word 'Hollywood' in the description field.
There are also two different search engines in Digizuite™. Both methods are case-insensitive. The difference between the two methods is explained using these three examples:
Example 1:
- Requires: Assets with the word 'Film':
- Search string: 'film'
- Example of results: 'Film no 1 of 2'
- Example not found in the results: 'Hollywood films'
Example 2:
- Requires: Assets that start with the string 'film':
- Search string: 'film*'
- Example of results: 'Films from Hollywood'
- Example not found in the results: 'Hollywood B-films'
Example 3:
- Requires: Assets that use the string 'film':
- Search string: 'film'
- Example of results: 'Hollywood action films', 'Hollywood films'
8.3.3 Full Text Indexing
This engine is based on a full text catalog defined by the SQL server. Therefore, we refer you to documentation for Microsoft SQL server Full-Text index search.
...