CloudNine Discovery Portal's self-service loading provides a simple solution for loading already processed data and load files into CloudNine Review.
CloudNine Discovery Portal is the gateway to getting your data into CloudNine Review and other CloudNine applications. It provides simple, easy-to-use workflows for loading data to CloudNine's suite of products.
When you have already processed data such as load files, natives, text, and/or images CloudNine Discovery Portal is used to perform a self-service load of the data or to transfer your data to CloudNine's Client Services team to load the data for you.
Charges may apply when data is sent to the Client Services team for loading. Please consult with your sales representative or call CloudNine at 713-462-6464 to determine fees and review options.
This article provides the videos, workflows, and steps for loading processed data into CloudNine Review using CloudNine Discovery Portal.
CloudNine Discovery Portal to CloudNine Review Workflow
Before you Begin: What is Processed Data?
Processed/Production Data is data that has undergone processing to expand containers, messages, and embedded files, and to extract text, native files, and metadata to be used to investigate the data fully.
Whether you processed the data yourself or received processed data, typically data is delivered in Volume folders based on an agreed data size.
- Volume Root: Contains subfolders for the images, text, and natives. On the root, the supporting load files, and supporting files such as privilege logs and exception reports may exist or they may reside in a data subfolder. The following subfolders in the volume may exist.
- DATA: Subfolder containing the load files necessary to batch load your images, text, and native files. We recommend: .DAT file for metadata and .OPT or .LFP for images. Other supporting files may also exist here such as the privilege log and exception reports.
- IMAGES: If files have been imaged, this folder contains either single-page Group IV Tiff with 300 DPI, JPEG with 32-bit file compression, PDF, or multi-page PDF files based on the agreed-upon delivery format.
- NATIVE: Output of corresponding native files. This may be limited to specific file types such as Excel files, large text files, or files that could not be processed to image format.
- TEXT: Corresponding extracted or OCR text.
Step 1: File System-CloudNine Review – Production/Processed Data
When you launch CloudNine Discovery Portal you are presented with several workflows. The File System to CloudNine Review workflow is used when you have already processed data with load files to import into CloudNine Review.
- Double-click the CloudNine Discovery Portal shortcut to launch CloudNine Discovery Portal. The Welcome to CloudNine Discovery Portal Home screen appears.
- On the left, below Select Data From: choose File System (e.g. File Share, Hard Drive, Forensic Image, etc).
- When File System is selected, options become available on the right under Review Data Using: the CloudNine Review option is selected by default. Verify File-System to CloudNine Review is selected and then click Continue.
- The CloudNine Discovery Portal login prompt appears. Enter the Email address and Password you use to log in to CloudNine Review then click Continue. The Verify Your Identity prompt appears. Confirm your identity with the two-factor authentication method you established in CloudNine Review, verify your identity accordingly. See Creating Your Multi-Factor Authentication to learn more about multi-factor authentication.
- Once your identity is verified, the What kind of data are you uploading? overlay appears. Two options exist:
- Native/Raw Data: Data that has not undergone any processing to expand container files, extract metadata, extract native files, or extract text files. This is eDiscovery data in its original collected format.
- Production/Processed Data: Data has had processing and contains the corresponding .DAT load files for metadata along with links to the native and text files. If images exist, a .LFP or .OPT file should be available for image uploads.
Step 2: Upload to CloudNine Review: Case Selection and Upload Name
In CloudNine Discovery Portal, you have selected the File System - CloudNine Review workflow, connected to CloudNine Review, and chosen Production/Processed Data to load to CloudNine Review. You are now on the Upload to CloudNine Review: Select a CloudNine Review Case screen. On this screen, you will select the CloudNine Review Project and enter an Upload Name.
Overview Upload to CloudNine Review
- Upload Name (Required): Enter an Upload name to use as a reference for the volume/load. The maximum number of characters is 100. The Upload name should follow the naming procedures you have implemented for CloudNine Review. For example, you might choose to name the upload with a combination of a date and volume name i.e., <Date>_<Volume>.
- Search Cases...: Use this option to quickly locate the CloudNine Review project (case) you wish to load the data to. The search is fuzzy and begins returning results in the case names list that relates to the character(s) entered in the search box.
- Create Case: If the case does not already exist in CloudNine Review, you can Create a Case through CloudNine Discovery Portal. The case is temporary and not actually created until CloudNine Review receives the data.
- Case Name (Required): List of CloudNine Review cases you have Admin rights to access and load data. If you do not see the case name you wish to load to, most likely you do not have Admin user rights in CloudNine Review for the project (case).
- Selected: The case selected is indicated here with a check mark.
- Next: Advances you to the next screen, Select Processed Data and Supporting Files.
Upload to CloudNine Review - Existing Case
Now that you are familiar with the Upload to CloudNine Review screen, you can proceed with entering an Upload name for the data you are loading and selecting the CloudNine Review Case Name you will load the processed data to.
👥 You must have Admin rights in the CloudNine Review project you are loading data to. If you do not have Admin rights, you will not see the project (case) in the Case Name list.👥
- Enter the Upload name. The Upload name should follow the naming policy you have implemented for uploading data to CloudNine Review.
- Scroll through the Case Name list, and left-click to highlight and select the CloudNine Review case (project) you want to import the data.
- Use the Search Cases... option to search for the case name you are looking for quickly. The search is fuzzy and updates the list as you type in the search box.
- Create Case: Use this option if the case is not listed and you have verified that the case is a new case and does not currently exist in CloudNine Review.
- Once you have inputted an Upload name and selected the CloudNine Review Case, click Next to advance to Step 3: Select Processed Data and Supporting Files.
Create a New Case for CloudNine Review
It is possible to create a CloudNine Review case (project) in CloudNine Discovery Portal.
Before you create a CloudNine Review case in CloudNine Discovery Portal:
- Verify that the case (project) doesn't already exist in CloudNine Review. To Load data to an existing CloudNine Review project, you must have Admin rights. If you do not have Admin rights, the CloudNine Review project will not be listed under Case Name in CloudNine Discovery Portal.
- Verify you have the correct permissions in CloudNine Review. You must have Admin or User rights to create a new case (project) through CloudNine Discovery Portal.
- Maintain the Case (project) naming policies you have implemented for CloudNine Review.
- When a CloudNine Review case is created via CloudNine Discovery Portal the case is temporary. The case is not created until the data is received by CloudNine Review.
- On the Upload to CloudNine Review screen, click the button at the right. The Create New Case overlay appears.
- Enter a Case Name for the CloudNine Review project; based on your CloudNine Review project naming policy.
- Review the Time Zone displayed if it is incorrect, use the drop-down to select the desired Time Zone for the CloudNine Review project.
- Click Create. The Create New Case overlay closes and you are returned to the Upload to CloudNine Review screen. The case appears in the Case Name list and is selected by default. The new case is italicized indicating it is a temporary case. The case is not created as a CloudNine Review project until the data is received by CloudNine Review.
- Enter an Upload name, verify the Case Name is selected, then click Next to proceed to Step 3: Select Processed Data and Supporting Files.
⚠️ When creating a CloudNine Review case in CloudNine Discovery Portal, the case is temporary. The case (project) is created when the data is received by CloudNine Review. At that time you will see the project in CloudNine Review.
Step 3: Select Processed Data and Supporting Files
You have chosen to load Processed/Production data to CloudNine Review. You have entered an Upload name and selected the CloudNine Review Case Name to load the data into. It is now time to determine how you will load your data. See Before You Begin: What is Processed/Produced Data for more information about processed/produced data.
There are two options for loading your processed/production data to CloudNine Review:
- Self-Service Loading: Loads the data directly into CloudNine Review. You can use self-service loading to load data, natives, text, and images into an existing CloudNine Review case or a new case. The self-service loading can also be used to overlay data to existing records in the CloudNine Review case.
- CloudNine Client Services: Sends the data to our Client Services team for loading.
👥 You must have ADMIN rights in the CloudNine Review case (project) to load data to an existing project. To create a new case you must have admin or user rights. 👥
Self-Service Loading - New Records
If desired, you can follow along with the CloudNine Discovery Portal -Self-Service Loading to CloudNine Review video.
You have processed data and want to upload the data into the case you selected or created in Step 2: Upload to CloudNine Review: Case Selection and Upload Name. You have decided to use the self-service loading feature in CloudNine Discovery Portal to load processed data into CloudNine Review.
- At the top of the Select Process Data and Supporting Files screen, click the Browse button, located below Select the Native .DAT load file, navigate, and select the DAT file for the volume you are loading. The DAT file will load the data as new records. If native and text paths exist it will also load the natives and text-provided the correct fields are selected for mapping. To learn more information about DAT files, click here.
- If you have images, under Select the Image .OPT or .LFP load file, click Browse to navigate, and select the OPT or LFP file. If you do not have images, skip to #3. Images can also be loaded and linked at a later time. See Importing Images Only. To learn more about OPT and LFP files, click here.
- Next, you will choose how the data is loaded to the CloudNine Review project. There are two options:
- Load Data as New Records: Create a new record for each line item found in the DAT load file. This is the only option available when loading data to a new CloudNine Review project.
- Overlay Data onto Existing Records: This option is available when records exist in the selected CloudNine Review project and you wish to overlay new or updated data to the records. Click here to learn about overlaying data.
- Click Next to advance to Step 4: Field Selection and Mapping.
The DAT (Metadata) Load File and CloudNine Review Recommendations
About DAT Files
Sample DAT Load File
Native and OCR Text Protocol
The OPT or LFP (Image) Load File and CloudNine Review Supported Formats
About Image Load Files (.OPT or .LFP)
- Image load files provide directions to where the images reside and where the document boundaries are for the images.
- Supported image types included black and white, color, and mixed in a single-page or multi-page format. The supported file types for CloudNine Review are:
- Single-Page Group IV TIFF at 300 DPI,
- Single-Page JPEG 32-Bit file compression,
- Single-Page PDF, or
- Multi-Page PDF.
Sample Image Load Files
Single-Page LFP with TIFF and JPEG
Multi-Page LFP - PDF
Single Page OPT with TIFF and JPEG
Importing Images Only
It is not uncommon to load the DAT file with metadata, natives, and text before loading images, especially with larger data collections. This allows you to start reviewing data sooner, while imaging is taking place. Or, it allows you to review data natively, and only image files you know will need to be redacted and/or produced saving time and expenses.
With CloudNine Discovery Portal you can load images to an existing CloudNine Review project provided the record exists and there is a common unique identifier in the OPT load file and CloudNine Review case. Learn more about OPT and LFP files by clicking here.
To Import Images to Existing Records:
You have launched CloudNine Discovery Portal, selected the File System- CloudNine Review, connected to CloudNine Review, selected Production/Processed Data, entered an Upload name, and selected the existing CloudNine Review case you wish to load images to. In CloudNine Discovery Portal you should be on the Select Processed Data and Supporting Files screen.
- Below Select the Image .OPT or .LFP load file click Browse... to navigate and select the OPT or LFP load file to load and link the images to the selected CloudNine Review case.
- Select Overlay Data onto Existing Records.
- The drop-down becomes available, select Beg Bates (BegDoc), CloudNine DocId, or Production Beg Bates (available if productions have been ran). This is the unique identifier that exists in both the image load file and the CloudNine Review project.
- Click Next to advance to Step 5: Confirm & Upload.
Overlay Data to Existing Records
If desired, follow along with the CloudNine Discovery Portal - CloudNine Review Overlay Data video.
There will be times you will need to overlay data to already existing records in the CloudNine Review Project. Overlaying to existing records is simple with CloudNine Discovery Portal.
- Launch CloudNine Discovery Portal, on the Welcome to CloudNine Review home screen, select File System and CloudNine Review (Step 1). Connect and Authenticate to CloudNine Review, then select Processed/Produced Data.
- On the Select a CloudNine Review Case screen, enter the Upload name and select the existing CloudNine Review Case (Step 2) you wish to overlay your data to. Click Next to advance to the Select Processed Data and Supporting Files screen.
- Click Browse under Select the Native .DAT load file and browse to locate the .DAT file containing the data you wish to overlay.
- Choose Overlay Data onto Existing Records, the field selection option is unavailable for selection. This is done in Step 4.
- Click Next to advance to the Field Selected / Not Yet Mapped screen. On this screen, you will map the common unique field that exists in both the load file and the CloudNine Review project. Step 4: Field Selection and Field Mapping.
📝 At this time Text Overlays are not re-indexed. If you need to have your CloudNine Review project re-indexed, please reach out to the CloudNine Services team at 713-462-6464. Note: This may be subject to charges.
Sending Your Data to CloudNine Client Services Team
If you prefer, you can send your data to the CloudNine Client Services team to load into your CloudNine Review case (fees may apply). The CloudNine Client Services team is here to help you.
- In the CloudNine Client Services section at the bottom, select the Bypass manual loading, and send the data to our Client Services team for loading option.
- Once enabled, click the Browse button located under Processed Data Path. Navigate and select the Volume (root) folder that contains your natives, text, images, and load files of the processed data.
- Click Next to advance to the Confirm & Upload screen.
📝When sending data to the CloudNine Services team for loading changes may occur. Please contact your CloudNine sales representative at 713-462-6464 for more information.
Step 4: Field Selection and Field Mapping
In CloudNine Discovery Portal, you selected the File System - CloudNine Review, connected to CloudNine Review via the Auth0 authentication method, selected Production/Processed data, entered your Upload name, selected or created the CloudNine Review case (project) to load to, and selected the load files to load the data, natives, text, and images. The next step is to select and map the fields from your data file to fields in the CloudNine Review case (project).
The selection and mapping of fields is an important process in your workflow. On this screen, you will map header fields located in your DAT file to the fields in CloudNine Review. When fields are mapped properly, you are able to take full advantage of CloudNine Review features.
Field Selection/Field Mapping Overview
The Field Selection/Field Mapping Overview section provides details about this screen and notes the required fields and why.
- Dat File Fields: Provides a list of fields found in the DAT column header.
- Search DAT Fields: A dynamic search that can be used to quickly locate specific fields from the DAT file for mapping to CloudNine Review fields.
- Dat File Fields Settings: When selected, a popup appears with the opportunity to change Data Delimiters/Characters, Text/File Encoding, and Date Format. It also provides a preview of the column headers and data found in the load file. See Customization of Data Delimiters.
- "X" Fields Selected- "X" Not Yet Mapped: Identifies the number of fields selected from the DAT field list (#5 on the overview screenshot) and the number of fields that are not mapped to a CloudNine Review field (#6 in the above screenshot).
- Selected Dat File Fields: Displays a list of fields selected from the DAT load file for import to CloudNine Review.
- Mapped CloudNine Review Fields: The selected CloudNine Review field the load file field data will import to. A Not Mapped message indicates the CloudNine Review field needs to be selected. Until all selected fields from the DAT field list are mapped to a CloudNine Review field you will not be able to advance to the next screen.
- Import: Imports a saved Field Mapping Template to save time during the Field Selection - Mapping step. See Saving and Importing Field Mapping Templates.
- Save: Save templates of the Fields selected and mapped to use with future load file imports. See Saving and Importing Field Mapping Templates.
- CloudNine Review Fields: List of CloudNine Review Fields available for mapping. These are Mappable system fields and any user-created global fields that exist in the selected CloudNine Review case (project).
- Auto Map: The Auto Map option will map any field named the same in the DAT load file and CloudNine Review case.
- Save Review Fields: Saves a list of the CloudNine Review fields and property information in a CSV format.
- Create Custom Fields: Used to create fields in the CloudNine Review case (project). See Create Custom Fields.
- Message Display: Provides messages related to field mapping. An error message appears when the key field is not mapped. This is the unique identifier that will sync data, natives, and text and is commonly fields like BegDoc, DocID, BegBates, ProdBates, etc. Once the key field is mapped, a reminder message is displayed to remind you to map native and text paths as well as attachment fields to maintain family relationships.
- Back: Returns you to the previous screen. Note: Selecting Back to return to the previous screen(s) will cause you to lose any field selection/mapping work you have completed. If you need to go back, consider saving a Field Mapping Template (#8) so your work is saved and available for importing.
- Next: Advances you to the Confirm & Upload screen.
Field Selection and Mapping
When you first arrive at the Field Selection and Mapping screen, the left column lists all fields found in the DAT file. The right column lists the available CloudNine Review fields to map to. The center provides the list of fields selected and mapped.
- Begin by mapping the Key field, in CloudNine Review this field is Beg Bates (BegDoc). The key field is the unique identifier used to link data, images, native, and text and is the only required field for loading data.
- Continue mapping fields found in the DAT file to the desired CloudNine Review fields by selecting the DAT file field, then the CloudNine Review field.
- Once all desired fields have been selected and mapped, review your selections and then click Next to advance to Step 5: Confirm & Upload.
📝Notes About Field Mapping
- If the fields from the DAT file do not appear listed, the delimiters or encoding may not be correct. See Customization of Data Delimiters.
- To preserve family relationships in CloudNine Review, you will need to map the 'Parent Beg Doc' field in the DAT file to the BegAttached field.
- If you are loading to an older CloudNine Review project, the BegAttached field may not exist. If it does not exist in CloudNine Review, create BegAttached as one of your custom fields.
- To load Native and Text files, you must map the relevant DAT file field to the Native File Path and Text File Path fields in CloudNine Review.
- The AutoMap feature can be used if the field names in the DAT load file and field names in CloudNine Review are identical (save the field list to see field names in the CloudNine Review).
- If there is no corresponding CloudNine Review field you can create a custom field to map to. See Create Custom Fields.
- After mapping fields, you can save a Field Mapping Template to use for future imports into the case (project).
- If Next is unavailable, verify all selected fields are mapped. The "X" Not Yet Mapped at the top of the Selected Fields - Fields Not Yet Mapped displays the number of fields that still need to be mapped.
- Always QC to ensure the selected field data will be mapped to the correct field in CloudNine Review.
Customization of Data Delimiters, Text/File Encoding, and Date Formats
In Step 3: Select Processed Data and Supporting Files you selected the Native .DAT load file to load data into mapped fields in the CloudNine Review case. CloudNine Discovery Portal requires a load file with a .DAT file extension. While the recommended delimiters for the .DAT are Field separator: (020) and Text: þ(254), as long as the file extension is .DAT you are able to select the file and customize the delimiters in the load file.
If you select a .DAT load file that doesn't match the default delimiters or text/file encoding, the Field Selection / Mapping screen will not display the field list properly. This is your clue that you will need to change the data delimiters or text/file encoding.
The above screenshot illustrates an issue with the selected data load file. Each field should be listed separately not as one field.
To resolve this issue:
- Click the Dat File Fields icon at the top right corner of the Dat File Fields column. A popup appears.
- 1. Data Delimiters/Characters: You can change the delimiters for the load file here. In the sample above the Comma/Column field should be changed to a comma ,(034) and quote "(044).
2. Text/File Encoding: CloudNine Discovery Portal will attempt to interpret the encoding for the selected load file. If you need it, you can use the drop-down to select the Text/File Encoding format.
- 3. Date Format: Date fields are loaded in a MM/DD/YYYY format. Use the Date Format drop-down to change how the date fields are loaded into CloudNine Review.
- 4: Preview: Provides a preview of the fields, the delimiters, and data. When the correct data delimiters are selected, the fields and data preview display in column format.
- 5. Cancel: Cancels any selections and closes the popup.
- 6. OK: Saves the changes, then closes the popup.
- In the sample screenshot, you can see in the preview section the default delimiters are incorrect. The preview shows the delimiters are Comma/Column ,(034) and Quote "(044). Use the Data Delimiters/Characters drop-downs to select the correct delimiters for the load file.
- With the correct delimiters selected, the preview displays column field breaks and data. Review the delimiter changes and make any Text/File Encoding or Date Format changes using the preview to confirm the changes.
- When you are satisfied with your changes, click OK to save the results and close the popup.
- On the Field Selection/Mapping screen, the Dat File Fields column displays the fields in the expected list format. You can now proceed with mapping your fields. Start by selecting a field from the .DAT file, then select the corresponding CloudNine Review Field.
- Continue mapping the fields, then click Next to advance to the Confirm & Upload page.
Create Custom Fields
When loading data with CloudNine Discovery Portal the Create Custom fields option allows you to create custom fields in the CloudNine Review project (case).
📝Custom fields are temporary and are not created in the CloudNine Review project (case) until CloudNine Review receives the data.
To Create Custom Fields:
- In the CloudNine Review Fields column section, click the Create Custom Fields icon at the column's top right corner. The Manage CloudNine Review Custom Fields popup appears.
- Click Create at the top right. The Field name, Type, and Scope options become available. Enter a Field Name, and choose the field Type and Scope. Click Add. The Field, Type, and Scope are listed with an option to Delete. Repeat the process until all custom fields are added.
- Once you have created your custom field(s), click OK to return to the Field Selection/Mapping screen. The fields now appear in the CloudNine Review fields list.
- Proceed with selecting fields from the Dat File Fields and mapping to the CloudNine Review Fields. Once all selected fields are mapped, click Next to advance to the Confirm & Upload screen.
- While the field names in the DAT may be different, do not create custom fields for the Unique ID (Beg Bates), BegAttached, Native File Path, and Text File Path. Select the appropriate DAT field and map accordingly.
- An exception is for older CloudNine Review projects where the BegAttached field did not exist. If this is the case, after verifying in CloudNine Review, the field should be created.
- Use Bulk Add to create more than one field at the same time. A CSV file with Field Name, Type, and Scope values is needed for bulk adding.
- Click the help option to learn the Scope of field and Type of field values.
Saving and Importing Field Mapping Templates
You can save templates of the selected and mapped fields. This feature is useful when you anticipate multiple loads into the same project, or you have a standard field mapping/naming practice for all load files going into your CloudNine Review projects. The use of templates can save time and may help to ensure consistency when loading data to CloudNine Review.
Saving Field Mapping Templates
- Once you have selected all of the Dat File Fields, mapped to their corresponding CloudNine Review Fields, and Created Custom Fields click the Save As option at the top right of Fields Selected - Not Yet Mapped section (Note: the Save As option is not available until at least one field has been selected and mapped).
- The Save As to Review field mapping template appears, browse to the location you wish to save the tempate, enter a File name, then click Save. The Field Mapping template (*.json) file is saved for future use.
Importing Field Mapping Templates
- On the Field Mapping screen, in the middle Field Selected - Not Yet Mapped section, select the Import option.
- Browse and select the <template>.json that has been saved for loading to CloudNine Review. Click Open.
- All fields are mapped, provided the selected Dat file fields and mapped CloudNine Review Fields exist. An Unmappable Imported Fields popup displays field selection / mapping that exists in Field Mapping <template>.json but does not exist in either the Dat File Fields, CloudNine Review Fields, or both. The field is Green if it exists in one but not the other and Red if it does not exist.
- Note fields that need selected and mapped and or created, then click Close.
- Proceed with Field Selection - Mapping the remaining DAT File Fields to existing CloudNine Review Fields or Create Custom Fields for CloudNine Review.
- When you are satisifed with the fields selected and mapped, click Next to proceed to the Step 5: Confirm and Upload.
Step 5: Confirm & Upload
The Confirm & Upload screen is the final screen in CloudNine Discovery Portal and your last chance to verify the upload to CloudNine Review. Spend some time reviewing this screen to ensure the accuracy of the data and files selected for loading into CloudNine Review.
- Uploading From-Processed Data: Provides a summary of the data selected for import. Only information relevant to the specific upload is displayed. If you are loading data only, you will not see image information, likewise, an image-only import will not display data, native, and text information.
- .DAT file: Name of the .DAT file selected for import.
- Image Load File: Name of the .OPT or.LFP file selected for import.
- Upload Name: The name you inputted in Step 2: Upload to CloudNine Review: Case Selection and Upload Name.
- Number of Records Identified in the .DAT: <N>: Displays the number of new records that will be added to the CloudNine Review project (case). Or, if you are overlaying the data the number of records that will be updated.
- ✔️QC the number of records by opening the .DAT file in a text editor program (Ultra Edit, TextPad, Notepad++, etc) and confirm the number of line items, minus the header row.
- Number of Mapped Fields: The number of fields selected from the .DAT file and mapped to the CloudNine Review project (case).
- ✔️QC by counting the number of fields in the header row of the .DAT, minus any fields excluded.
- Number of Native Documents Identified in the Load File: If you have mapped the Native File Path, this will tell you how many native files are in the load file.
- ✔️QC the native file count by browsing to the upload volume and running a property check on the Native folder. If natives are in the same directory as the text and/or images you will need to subtract the additional files.
- ✔️QC the .DAT file and tally the number of records in the native file field.
- Number of Text Documents Identified in the Load File: Based on the mapped text file path this will indicate the number of expected text files that will be loaded.
- ✔️QC the text file count in the Text folder of the selected volume. If text files exist with the natives or images you will need to sort and total just the text files. If native files exist in the folder, it is possible the native is a text file. You will need to subtract the native text file count.
- ✔️QC the .DAT file and tally the number of records in the text file field.
- Number of Image Documents Identified in the Load File: The number of records that will have images, based on the image load file.
- ✔️This count may be the number of records in the DAT load file if all records were imaged. If multi-page PDF import confirm the number of PDF files that are being imported. If this is single-page page images, you will need to add the number of document flags in the .OPT or .LFP to determine the number of documents.
- ✔️Check the data files provided, a summary file may exist that tells you the expected number of natives, text and images.
- Number of Image Pages identified in the load file: Provides the total number of pages within the images.
- ✔️If single-page images the load file will list each page individually. The total number of images will match the number of records in the .OPT or .LFP.
- ✔️If multi-page PDF there will be one line per record.
- ✔️Navigate to the image folder and run a property check to verify the number of files. For single-page images, the total count should match the number of pages.
- Number of Fields Being Created in CloudNine Review: Total number of fields you created using the Create Custom Fields option during the Select and Mapping fields process.
- ✔️Confirm the number of fields is correct.
- Uploading To: This section identifies the CloudNine Review project (case) you are importing to as well as Action, Delimiters, Encoding, and Date Formats.
- CloudNine Review - <Case Name>: Displays the CloudNine Review project you will be loading to.
- ✔️Verify you are loading to the intended CloudNine Review project (case).
- Timezone: The timezone the CloudNine Review project is set for.
- ✔️Verify the timezone is correct. This option is only displayed if you have created a new case for CloudNine Review.
- Action: Create New: indicates new records will be added to the selected CloudNine Review project. Overlay: indicates existing records in the CloudNine Review project will be updated with the new data.
- ✔️Confirm the expected action is taking place.
- DAT Field Delimiters: Delimiters from the DAT file.
- DAT File Encoding: Encoding in the DAT file.
- DAT Date Field Format: The format of any date fields in the DAT file.
- CloudNine Review - <Case Name>: Displays the CloudNine Review project you will be loading to.
- Notes & Comments: Add any information about the load file import you would like to track. If you have bypassed self-service loading and are asking CloudNine's Client Services team to load the data this is the perfect place to provide project specifications.
- Import Notes: If you have project specifications or other project information in a text file you can use this feature to import notes about the project.
- Start Upload: Kicks off the loading process.
When you are satisfied with the Confirm & Upload screen, select Start Upload to begin the loading process. The upload begins, and the Global Monitoring Console appears. Here you are able to monitor the upload progress.You will receive a series of emails when CloudNine Review receives the data and the import is complete.
- At this time, we do not recommend running multiple imports into the same CloudNine Review project at the same time. Multiple imports could cause the documents to import out of order.