Print this page
In this topic
This procedure applies to both Production templates and General templates.
The application includes a set of predefined system load file templates. We recommend that you customize a system load file template to create a case-specific load file template, instead of creating a new template manually. System templates contain the typical data load settings required for nearly all types of export jobs.
Use the following procedure to create a load file template.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click Add.
3.Type a Name for the load file template.
4.In the Export Type list, select General or Production. For more information about General and Production export job types, see Work with load file templates.
5.In the Template list, select the type of template you are creating. For more information about the types of templates in this list, see System load file template types.
oIf you select the Manual template, you must select either Document or Page in the Document/Page list. For more information about creating a manual template, see Create a manual load file template.
6.Click Save.
The Properties page appears. If you are creating a system template, the case-specific template inherits attributes from the system template. These attributes appear on the pages that are available in the left navigation pane.
This procedure applies to both Production templates and General templates.
A manual template differs from a system template in that a system template provides the key attributes that a load file must have to produce a successful export job. In a manually created load file template, you must specify all of the attributes and values to use in the load file.
Note: Instead of creating a manual load file template, we recommend that you use a system load file template. You can customize a system template as needed to create a case-specific load file template. System templates contain the typical data load attributes required for nearly all types of production export jobs.
Use the following procedure to manually create a load file template.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click Add.
3.Type a Name for the load file template.
4.In the Export Type list, select General or Production. For more information about General and Production export job types, see Work with load file templates.
5.In the Template list, select Manual.
6.In the Document/Page list, select Document or Page.
For more information, see Work with load file templates.
7.Click Save.
The Properties page appears.
8.Enter values for the remaining attributes.
Note: You must enter a value for File extension.
To save time, you can clone an existing load file template.
Use the following procedure to clone an existing load file template.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click the name of the load file template that you want to clone.
3.Click Clone Template.
4.In the Name box, enter a name for the cloned template.
5.Click Save.
You can determine general load file template settings on the Properties page. This procedure applies to both Production templates and General templates.
Note: If you plan to modify a previously saved case-specific load file template, make sure that the template is not in use. Modifications may result in unexpected load file output.
Use the following procedure to modify load file template settings.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click the name of a load file template.
3.On the Properties page, depending on the load file type, you can edit one or more of the following attributes:
oName: The name of the load file template is required. Change the name only if you want to save the template as a different case-specific load file template. Do not use the following characters, because they are reserved for Microsoft Windows file and directory naming: \ /: *? \" <> |
oRow delimiter: Defines the end of a row. For example, <CR><LF>.
oColumn delimiter: Defines the end of a column. For example, a ¶ (paragraph mark) character.
oText delimiter: Defines the end of a block of text.
oReplace instances of row, column, or text delimiter with data: Indicates data that will replace any characters you defined as row, column, or text delimiters. This data must be found within the production data.
oFile extension: Determines the format of the export file. For information about the types of predefined system load file templates, see System load file template types.
oPopulate first row with column names: When this check box is selected, the first row of the data must contain column names.
On the Default Field Formatting page, you can set field formatting defaults so that formatting is consistent across all fields in the template and does not need to be set for each field individually. These format settings are applied only to fields that are added to the template using the Add Columns > From field list option on the Columns page.
Note: These settings do not affect any formatting you defined when setting up a variable builder expression for a column value.
Caution: If you plan to modify a previously saved case-specific load file template, make sure that the template is not in use. Modifications may result in unexpected load file output.
Use the following procedure to set field formatting defaults for the load file template.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click the name of a load file template.
3.In the navigation pane, click Default Field Formatting.
4.On the Default Field Formatting page, depending on the load file type, you can edit one or more of the following attributes:
oDate: Select a date format in the list.
oNumber padding: Type the number of total digits allowed in the field. For example, if you enter the number 4 and have a value of 1, the value would be 0001. If you have a value of 11, it would be 0011.
oBoolean: Select the format for Boolean fields in the list.
oExport: For any one to many fields selected as a load file column, select All if all values in the field should be included in the load file. To export the first alphanumeric value in the field, select Minimum value. To export the last alphanumeric value in the field, select Maximum value.
oTranslations > Service provider preference: To set the preferred translation service provider, click the handle next to the provider and drag it to the top of the list.
Note: You can export only one translated version of a document per language. If a translation exists from the preferred provider, that translation is exported. If a translation from the preferred provider does not exist but a translation from the second priority provider exists, the translation from the second priority provider is exported.
oDelimiter: Type a special character to use to separate data values, such as a comma or semicolon.
oText qualifier: Type characters to indicate that the content enclosed between the characters should be interpreted exactly as it appears. Quotation marks are the most commonly used text qualifiers.
The Columns page lists all fields or expressions that are included in the load file. Column information on this page can include case field type, field format, and delimiter information. Columns define the structure of the load file output. A case-specific load file template inherits the columns and column values from the system template that it is based on.
Note: Document ID and Levels columns are required for .mdb templates, but the remaining columns can be deleted.
Caution: If you plan to modify a previously saved case-specific load file template, make sure that the template is not in use. Modifications may result in unexpected load file output.
Use the following procedure to add and modify load file template column settings.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click the name of a load file template.
3.In the navigation pane, click Columns.
The Columns page appears.
4.To add a column, click Add Columns, and then select From field list or From variable builder.
oFrom field list: Select this option to add multiple fields to the load file template at once.
□In the Add columns from field list dialog box, field names are grouped in the same categories that are used in document searches. To add fields to the template, select the check box next to the field names.
Note: If you select the top level field category, all fields within that category will be added to the template. You can expand a category and select a subset of the fields. Use the Search box at the top of the dialog box to search for specific fields.
□Click Save.
oFrom variable builder: Select this option to add a column using the Loadfile Column Builder, which is a type of variable builder. For more information, see Work with the Variable Builder.
Note: For columns added using the Loadfile Column Builder, the value User defined appears in the Name column by default. We recommend that you update this value.
5.To modify an existing column, on the Columns page, do the following:
oFor columns added using fields, you can click in the column's row and change the values in the Name and One to many columns. For .mdb templates, you can also change the value in the Export field type column.
oFor columns added using the Variable Builder, you can click in the Field column and use the Variable Builder to make changes. For more information, see Work with the Variable Builder.
This procedure applies to general templates. For a Ringtail database load file template (.mdb load file), you can export highlight and redaction data in the load file. You can then use the load file to import the highlight and redaction data into another case.
Use the following procedure to include annotations data in an .mdb load file.
1.On the Case Home page, under Manage Documents, click Load File Templates.
2.Click the name of a load file template.
3.In the navigation pane, click Annotations.
The Annotations page appears.
4.Select the check boxes for the annotations you want to add to the template. Select the blue shaded check mark at the top of the page to include all annotations.
