Once a Collection has been created, and items have been collected, you can create a Disk Image of the Collection. A Disk Image enables you to copy all or specific items in a Collection to disk. This can be used to share content in a Collection with individuals or groups outside the Content Server environment.
You can specify settings to control what items are collected, the size of the Disk Image, and the output format. You can also configure email notification to notify interested parties that the Disk Image has been created and provide details about the Disk Image, including how to locate the Disk Image output files.
After the Disk Image has been created, you can browse to the Disk Image location to access the files and to view the Disk Image Manifest file, which provides detailed information about the Disk Collection. For more information about viewing the Disk Image Manifest file, see Reading a Disk Image Manifest File.
Note: | |
Each time a Disk Image is created, information is recorded in the Collection Items Audit tab for the Collection so that you can view all past events that have occurred with the Collection, including the items that have been included in the current and past Disk Image creations. For more information about the Collection Items Audit, see Reviewing the Collection Items Audit.
Note: | |
You can also create a Disk Image for OpenText Enterprise Library items you collected. The metadata of OpenText Enterprise Library Items and the content for OpenText Enterprise Library Variants will be written to the disk.
You can create a Disk Image of specific collected items or of an entire Collection. Depending on settings configured by your administrator, when you create a Disk Image, you can control the amount and type of information included in the Disk Image by setting specific Disk Image settings on the Make Disk Image page.
The following settings and information appear on the Make Disk Image page:
Setting | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Summary | A list of the item types included in the Disk Image and a count of each item type. | ||||||||||||
Notes | Information to include with the Disk Image. | ||||||||||||
Destination Path | The path where the Disk Image will be created. This setting is configured by your administrator. | ||||||||||||
Zip Disk Image | Compress the Disk Image. This is enabled by default to simplify downloading. | ||||||||||||
Available Disk Sizes | Select the expected size of the disk output. If the Collection size exceeds the size you specify from this list, an additional Disk Image is created. | ||||||||||||
Disk File System Format | Select the ISO Format for the outputted information. For more information about file system formats, see Disk File System Formats. | ||||||||||||
Sort Order | How item types are sorted:
| ||||||||||||
Collection |
| ||||||||||||
Content |
| ||||||||||||
Max Objects per Image |
| ||||||||||||
Export a Sample |
| ||||||||||||
Include Custody Details | Provide information in the Chain of Custody Notes section of the Disk Image Manifest File about the Content Server software environment, when the Collection was created, completeness details, etc. For details, see Reading a Disk Image Manifest File. | ||||||||||||
Include EDRM XML 1.2 | Provide a description of the disk image in the manifest using the Electronic Discovery Reference Model standard. | ||||||||||||
Version Handling | How document versions in the Collection should be handled during the Disk Image creation. For more information, see Collecting Items from the Search Results Page. | ||||||||||||
Metadata Language | The metadata information retrieved for the disk image will be in the language you select. | ||||||||||||
Notification area: | |||||||||||||
When | The time in the Disk Image creation process that email notification should be sent. | ||||||||||||
Recipient | The email address of the User creating the Disk Image. If an email address has not been configured for you in Content Server, you can type in your email address. This is a required field. | ||||||||||||
Message Subject | The text that appears in the Subject field of the email notification message. This is a required field. | ||||||||||||
3rd Party Notifications | The additional Content Server Users, Groups, and external email addresses that email notification should be sent to, if any. |
Note: | |
The Disk File System Format determines the folder structure of the outputted Collection information. Each of the Disk Image formats have limitations on the amount of information that can be written to them, and each format has a different limitation. Regardless of the Disk File System Format that you select, Content Server creates additional output directories with additional Disk Images when:
The output content size exceeds the disk size selected in the Available Disk Sizes list on the Make Disk Image page.
The Max Objects per Image setting on the Make Disk Image page is set and is exceeded.
Before you select an option in the Disk File System Format setting on the Make Disk Image page, you should view the Collection and determine which of the output formats you require.
The available Disk File System Formats are: ISO 9660: 1999, ISO 9660 Level 2 and Joliet. The following sections describe the available Disk File System Formats and the limitations of each:
102 characters, including the extension or suffix.
The name template is A_B_C, where A is the Content Server DataID, B is version, and C is the object name. Longer names are truncated at the first 102 characters of the A_B_C combination string. Leading and trailing spaces are removed prior to normalization.
The name template is X_Y, where X is the Content Server DataID, and Y is the directory name. Longer names are truncated at the first 60 characters of the X_Y combination string.
Normalization to Alphanumeric Characters:
Yes – directory and file names.
Normalized to [A-Z 0-9._] characters. Each character out of that range is replaced with an underscore character ‘_’.
31 characters, including the extension or suffix.
The name template is A_B_C, where A is the Content Server DataID, B is the version number, and C is the object name. Longer names are truncated at the first 31 characters of the A_B_C combination string. Leading and trailing spaces are removed prior to normalization. Extension characters outside the range [A-Z 0-9_] are removed.
Longer names are converted into the format ST, where S is the first 4 bytes of the directory name, and T is the last 4 digits of the LES DataID. Leading and trailing spaces are removed prior to normalization. Characters out of that range are replaced with an underscore character ‘_’.
Normalization to Alphanumeric Characters:
Yes – directory and file names
Normalized to [A-Z 0-9_] characters. Each character out of that range is replaced with an underscore character ‘_’.
64 characters, including the extension or suffix.
The name template is S_T_U, where S is the Content Server DataID, T is the version number, and U is the object name. Longer names are truncated at the first 64 characters of the A_B_C combination string.
The name template is X_Y, where X is the Content Server DataID, and Y is the directory name. Longer names are truncated at the first 64 characters of the A_B_C combination string.
Normalization to Alphanumeric Characters:
Yes – directory and file names
If a directory contains the following characters, they are replaced with tilde (~) characters: [@@*:<>?\|.]
If a file name contains the following characters, they are replaced with underscore character ‘_’ characters: [@@*/:<>?\|]
Any characters higher than ASCII 127 are replaced with an underscore character ‘_’.
Understanding Disk Image Creation Notification
When you create a Disk Image, you can select one of two options for the type of email notification that you want to be sent:
An Image Report that is sent with the completion of every Disk Image, including when additional Disk Images are created because a value is exceeded.
A Completion Report that is sent at the completion of the final Disk Image.
During the Disk Image creation, you can also specify which Content Server Users, Groups, or third party individuals receive this notification. For example, if you are creating a Disk Image for a team project, you can notify members of the team that the Disk Image was created.
In addition to receiving notification of the Disk Image creation, the first sentence of the email message body contains a URL to the Disk Image for easy access. The following information is also included in the notification email message: