extraRendition_definitions.hda File Structure

Working With Image and Video Conversions 4-11

4.3.3.1 extraRendition_definitions.hda File Structure

When defining additional rendition sets, the extraRendition_definitions.hda file should contain a header line and two section types. Section Types The extraRendition_definitions.hda file has two section types using the following format: section_type section_name Section data end The two section types are: ■ Properties Section ■ ResultSet Section In the extraRendition_definitions.hda file, there is one properties section and multiple result set sections. All rendition sets are organized in result sets. Comments are not allowed within a section of an HDA file. However, you can place comments in the HDA file before the first section, between sections, or after the last section. Blank lines within a section of an HDA file are interpreted as a NULL value. Blank lines before the first section, between sections, or after the last section are ignored. Properties Section The properties section of the extraRendition_definitions.hda file defines the path to an external conversion application. In the default file, it also declares the values of Idoc Script variables defining conversion options used by the default rendition result sets. Default Idoc Script variables in the properties section are used by the default rendition sets. They are not required for any additional rendition sets you define and are not discussed in this guide. Conversion options can be specified directly within the result sets. For more information on working with IdocScript, see the Idoc Script Reference Guide. Result Set Sections There are two types of result sets in the extraRendition_definitions.hda file, listed here in order of display in the file: ■ Rendition Result Sets ■ ExtensionFormatMap Rendition result sets organize rendition sets and contain information about creating renditions. There can be many rendition result sets, in any order. They can be added, modified, or deleted, but each name must be unique. The ExtensionFormatMap is an optional result set lists file extensionformat pairs, so that Inbound Refinery can return the correct file format to Content Server for use internally. This is not a required set, as Inbound Refinery uses a different system to map extensions to mime types, but if this result set is defined, the mapping specified in it takes precedence. 4-12 Administrators Guide for Conversion

4.3.3.2 Adding a Rendition Set