Most cameras supporting Canon CRW files create additional thumbnail files (THM files). The Canon Raw Metadata Support module enables Cumulus to capture metadata from these files and to manage these files. For more information, see “Canon DC Raw Image & Thumbnail File”

The module Cumulus Metadata Support supports the storing of an asset’s metadata in a separate TAG file for each asset. This makes it possible for stored metadata to be used externally (e.g. by other applications). Only if the Cumulus Metadata Support module is activated, will Cumulus be able to create a TAG file for each asset cataloged. (For further information on TAG files, see “Assets/Records” and “Browse for Assets".) You can define the following properties for the Cumulus Metadata Support:

For Directory Categories, Folder TAG files can be created. Remember, Directory Categories are automatically created and resemble the folder hierarchy in which the assets reside. The Folder TAG file for a Directory Category is called Cumulus Metadata.tag and resides in the corresponding folder. If the Cumulus Metadata Support is activated and the option Always is enabled, a Folder TAG file will be created as soon as you change the Category information of a Directory Category.

Folder TAG files are also created if you Drag & Drop a category to your Desktop, or if you employ the menu item Copy Assets Assigned to Category To (for details, see “Copy Assets Assigned to Category To” ). And note that if you use this way of copying assets, the TAG files associated to the assets themselves will not be copied even if the Cumulus Metadata Support module is activated.

The HELIOS AssetProcessor enables you to convert cataloged assets into the following file formats: TIFF, JPEG, EPS, PNG, BMP, Sci­tex CT, Photoshop (PSD), and Macintosh PICT. Considering the ICC (International Color Consortium) profile you can select different color spaces and compressions supported by the OPI system. Rotation, flipping and cropping are also possible. The conversion produces a new file that can be stored wherever you want.

The HELIOS AssetProcessor can be used with Cumulus Clients under Windows or Mac OS X as well as with Cumulus Portals or Web Client and additional EJaPs or applications based on the Cumulus Java Classes. With the Cumulus Options, Web Client and Portals, all functions are also available on the Internet, e.g. prior to a download.

For details on how to use the HELIOS AssetProcessor, see the Cumulus HELIOS Companion Administrator Guide.

The XML Metadata Prefiller module enables Cumulus to capture additional metadata for an asset from a special XML file. When the asset is cataloged, the Prefiller looks for an XML file called “.CumulusPrefill.xml” in the file hierarchy above the asset’s location. If it is found, the metadata from this file is added to the asset’s record. (No properties to be defined.)

The XML MetadataBridge module enables Cumulus to retrieve additional information from an asset during cataloging and store this information within XMD Metadata files in XML format. The XMD Metadata files are stored in the same location as the original asset. The XML MetadataBridge also allows you to write metadata, which has been changed within Cumulus, back to these XMD Metadata files. These files store the metadata in XML format so that it can be viewed in a Web browser.

The XML MetadataBridge module supports the storing of an asset’s metadata in a separate XMD file for each asset. This makes it possible for stored metadata to be used externally (i.e., by other applications). If you catalog assets from a location where you are allowed to save files, the XML MetadataBridge can create an XMD file for each asset cataloged. The file is named the same as the asset but with the extension .xmd added and is saved in the folder where the asset resides. XMD files hold all of the information that can be viewed in the Information window and more. For example, if a particular asset has been cataloged in different catalogs, this information is stored in that asset’s XMD file. XMD files store the metadata in XML format so that it can be viewed in a Web browser.

Writing metadata (e.g. to an XMD file) requires two preparatory steps. First the Asset Handling Set for accessing the asset must be set to allow the writing of metadata. Then each record field - with contents which should be written back as metadata - must have the When Saving Assets option enabled for its field linking.

The XMP Metadata Support module enables Cumulus to manage XMP files (e.g. Adobe Sidecar). (No properties to be defined.)

The XUSR MetadataBridge module is used for the Cumulus User Manager application. It enables Cumulus to import user information from XML structured files. (No properties to be defined.)