Importing Data Flashcards
Relativity Desktop Client
Functionality for importing load, image, and production files, as well as exporting production sets, saved searches and folders
Using the RDC
As a litigation support specialist, you need to export a production of email files for the opposing counsel in the Salt vs. Pepper case. You created a production set named “Salt vs. Pepper - Email Production” and ran your production, and now you need to export the production using the RDC. So, you open the RelativityDesktop Client and log in to your Relativity environment.
You select and open the Salt vs. Pepper case and then click Production Set… on the Export menu to open the production export options.
Since this production set consists only of email messages, you include your Bates numbering and email metadata fields in the exported metadata.
The case production format requirements you need to comply with include PDF images with an Opticon data file format and a .csv data file format with Unicode (UTF-8) encoding. On the Destination Files tab, you select the required format options and also select to copy the files from the repository to copy the exported emails to your export network directory.
After selecting your options, you’re ready to click Run on the File menu to complete the production export to be able to send the Salt vs. Pepper emails as PDF images with the required data files to the opposing counsel.
Importing through the RDC - Handling Errors
Rel skips any records with errors and warns that errors were encountered
You can export error files to new document-level load file with only error records
Importing through the RDC - Saving Import Settings
File -> Save Import Settings (as .kwe file)
For identically formatted load file, use saved .kwe
In RDC, open the KWE and select the file to be loaded
Can upload absolute path to document-level load file to be loaded to point to new load file
Load File Specifications Overview
Relativity can load:
1) Metadata, extracted text, and native files
2) Image and extracted text files
3) Processed Data
Load File Specifications - Metadata, Extracted text, and Native Files
Encoding - code by Unicode, UTF8 etc (many
supported)
Header Row - not required but strongly recommended
(don’t need to match field names in workspace)
Fields - Identifier required, all others optional
Accepted Date Formats - Date and Time should be one field
Delimiters - Column/Quote/Newline/Multi-value/Nested-Values
Load File Specs - Useful Fields
- Identifier - required, unique ID
- Group Identifier - family group
- MD5 Hash
- Extracted Text
- Native file path
- Folder Info
- Relativity Native Time Zone Offset
Load File Specs - Image and Extracted Text Files
File formats - Single Page Group IV TIFs (B&W); Single page JPGs (Multi-page TIF and PDF must be loaded as native files)
Load File Format - Opticon load file, each line representing one image - (Page, Volume, Path, Document Marker (Y = new doc), folder, box, page count)
Can import extracted text during image import by setting an option in RDC
Importing Data Through Integration Points
Integration Points has the ability to import a CSV file, LDAP, or load file directly into the workspace
Integration Points - Running the Import Job
- Create the integration point
- Click “Run” from the console
- Status = Pending -> Validation (Validation Failed) -> Processing -> Completed (Completed with Errors)
Simple File Upload - Special Considerations
Relativity Imports Metadata: ArtifactID; Control Number; Extracted Text; Folder Name; Has Images; Has Native; Relativity Native Type; Supported by Viewer; Created By/Created On/Last Modified; File Name; File Size
- can upload any document format also supported by legacy ActiveX Viewer
- can search extracted text with keyword search (not if Data Grid is enabled)
