This topic provides information on the metadata retention feature in the File Download & Replacement workflow.
File Download and Replace
The Download & Replace functionality allows for the download of errored files to a user's local workstation and provides the ability to replace a discovered file with a different version (often repaired or decrypted). This feature can be found in the Mass action drop-down in the Files tab.
For more information on Download / Replace, see Processing error resolution.
The Metadata retention operation will preserve all metadata associated with a replaced file and its original version for visibility in a workspace. This occurs automatically on completion of replacing a file. The results are visible in two metadata fields, which can be mapped for Publish, and are available in the Details modal of the Files tab.
Source name | Field Type | Description | Example |
---|
Other Metadata Replaced | Long Text
| This field contains newly found, non-empty, metadata values of the replacement file. These metadata values were present in the original file but had changed in the replaced file. | Office/Headings=
Worksheets,2;Office _GUID=Unknown;Excel/HasHiddenRows=True;
Author=SteveBrule |
Other Metadata Original | Long Text | This field contains metadata from the original file as Processing requires them to always be associated to the native record associated to it.
The specific fields included will always be File Type, File Extension, File Size, IsContainer, MD5Hash, SHA1Hash, and SHA256Hash.
| FileType=Outlook Message File;FileExtension=MSG;FileSize=43 520;IsContainer=False;MD5Hash=;S HA1Hash=2E4AF3EEB4D7BD9CF2 97A94788DE17E198D4A1D5;SHA2 56Hash=9249E29E43334DDDDF2A B617FE47B0FD0BA4A034409ED8 AA4132FC74E9CC614 |
The process to manage these fields is slightly different than the regular field catalog. Steps to accomplish this can be found below:
- Open the Fields tab.
- Click New Field or Edit an existing field.
- Provide a name in the Name field. We recommend that you give the field an identical name as the one being mapped to.
- In the Object Type field, select Document. Only document fields are eligible to map to a value in the Source field. Selecting any other object type disables the Source field.
- In the Field Type field, select Long Text.
- When the Field Type is selected, you will see the menus for Field Settings and Advanced Settings. Click Advanced Settings.
- Click Selecton the Source field to display the processing fields to which the Relativity field can be mapped.
- Click the drop-down near the upper left corner of the modal and select the All Fields option.
- Filter for Other Metadata in the Source FIeld Name column.
- Select either option depending on which field is being created at that time.
For more information on field mapping, see Mapping processing fields.
The following table shows the Relativity Processing field names and the associated Metadata retention behavior.
Multiple Replacement Operations
Relativity Processing supports subsequent file replacement operations of the same file. This is the action of replacing a file that has already been replaced. When this action occurs, Processing will compare the original file with the most recent replacement and compute the associated metadata fields without consideration of any replacement operations that have previously occurred.
Special Considerations
Special considerations are as follows:
- The job to populate the metadata fields is not visible on the front end. It is a part of the retry job that automatically occurs after replacing the file. Indications on whether the retry is still in progress can be found in Processing Administration, the Processing Set, or the Error Status field within the Files tab.
- The SavedOriginalFileMetadata field is visible in the File Metadata card of the Details modal within the Files tab. This field will not display relevant information. It is a container to store all metadata associated to the original file for purposes of validation in scenarios of multiple replacements.
- It is not recommended to replace files in workspaces with Discovery jobs running concurrently. This is to avoid potential data collisions where a replacement operation is being executed on the same file being discovered. A potential result would be loss of original metadata.
- When this functionality is not enabled, Processing will replace all existing metadata associated to a file with the metadata collected from the replacement file.