Return to Topic
Reprocessing Failed Items in Electronic Discovery
This feature will enable reprocessing of records that had one of the following errors during prior Electronic Discovery sessions: Write failed, Attachment Extraction failed, Embedded Image Extraction failed, and/or Compound Doc.Extraction failed.
How to Determine Whether to Process Failed Items
Different Scenarios and Reprocess Behaviors
To Check the ED Loader Session Logs for Processing Errors/Warnings
Select the Failed Items Tab
|
How to Reprocess Failed Items
To reprocess failed items, a new button named Failed Items has been added to LAW Electronic Discovery Loader. Once the button is selected the “$Repository” folder is added to the Source queue.
Before reprocessing failed items through EDLoader, you will need to resolve the cause for the records to error.
Reprocessing Passwords Protected RecordsBrowse to the case folder/$Repository folder. The native files are copied to $Repository \$Files, and the metadata information is copied to the $Repository \$Metadata folder. Open the $Files folder. All files will be listed with a unique identifier that corresponds to the metadata referenced in the $Metadata folder. Opening the file in the $Metadata folder in Notepad will provide the following metadata values: FolderPath, EntryID, SourceID, LawPath, EMailClient, ConversationIndex, ThreadID, ItemGUID, ReprocessedCount, ParentID, SourceFolderPath, SourceFileName, and FileName. The following example has two Windows Explorer windows ($Files and $Metadata) and a $Metadata file open in Notepad.
The $Metadata file can be used to locate the FileName that matches the corresponding unique identifier in the $Files folder. 1.Open the record in $Files using the correct password. 2.Change the security settings disabling the need for a password. 3.Then save the record into the same $Files folder and with the original unique identifier as the filename.
|
|
Reprocessing Records with Other Errors
For records that fail due to processing errors or metadata extraction errors, confirm that your Windows login has read/write permission to the case folder and all subfolders and files, %Temp%, and %appdata%. Ensure that there isn't another program that is trying to access your source files during import. If metadata extraction errors caused a record not to import then you may want to turn off metadata options during import and process post import by Extracting Custom Metadata
|
After Resolving Errors that Generated Failed Items During the Original Import
Select Failed Items in LAW Electronic Discovery Loader. Change any import settings that need to be altered and select Start. The Failed Items that have been resolved will now be imported into the database in the corresponding folder with the rest of the files from that source. If the item is re-processed successfully, then the backed up file and its metadata info will be deleted from the “$Repository” folder. If the item was an attachment, then the Parent document id will be added to the ErrorMsg field. This can be used to manually attach the item back to its parent.
|
Querying for Reprocessed Records in Your Database
You can determine which items were re-processed using the Database Query Builder. 1.Select Search Records on the LAW toolbar. 2.In the Database Query Builder select _DocCat in the Field Name dropdown. 3.On the far right of the field name, click the ellipses button. The Custom Value Selection dialog displays. 4.Select Reprocessed Item. Click Accept to close the Custom Value Selection. 5.Click Execute in the Database Query Builder. Search Results display. 6.Select Field List from the View menu, and make sure you have selected _DocCat so that it will display. 7.The _DocCat field will show the following values for reprocessed documents: •131073 for successfully reprocessed documents •131201 for reprocessed documents that still have errors
|
|
