Jump to content

Search the Community

Showing results for tags 'load file'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Technical Support
    • General Technical Information
    • Intella 10/100/250/Pro/Team
    • Intella Connect/Node
    • Wishlist
  • News and announcements
    • Announcements
  • Talking Tech with Vound
    • Webinars
  • Archive
    • Archived threads

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. Are there any plans to incorporate RSMF as an export format for Relativity load file exports? We have seen an increase in requests for this format.
  2. My team is performing production import tests. Despite achieving some positive results, we still have some problems: 1. When checking for errors in the "match loadfile fields with Intella" portion, we encounter the following image, suggesting problems with the opt file, even though the preview of the items with redaction appeared to be correct. The loadfile can be proccessed even with these errors. The Map fields options were filled as in the following image. 2. After processing the loadfile, we realize that some items that should have a redacted image in the visualization panel do not have a image to display. All other files had their images preview displayed properly. Are there any particularities regarding the import of items with redaction we are missing? The dat and opt files are available in the attachments. export.dat export.opt
  3. We have received a few support tickets from users who have had issues with ingesting a load file into Intella. There are two common issues being reported by our users. These two common issues are discussed below, but we will add updates to this post if other issues come up in the future. Note: In this post we are discussing Relativity and Concordance type load files that use .dat and .opt files. Issues 1) The user says that either the 'Load file preview' tab, or the 'Image preview' tab is not working and they can't see their load file, or image entries (respectivley) in these tabs. Basically one tab is fine, while the other tab does not show the data in the load file. 2) The user says that Intella is reporting a 'File can not be read: Input length = 1' error when they click the 'Check for errors' button in the Map Fields window. Both of these issues have the same cause. It relates to an encoding mismatch between the .dat file, the .opt file and the extracted text files. Note: The 'Detect encoding' button in the Intella interface detects the encoding in the .dat file. That encoding setting is then used for the .opt file and the extracted text. Currently as of this writing (version 2.3.1) there is no way to ingest a load file where different encoding exists for these components. We will improve Intella to allow for more flexibility for this in a future release. Also note that the Detect encoding button may not work in some cases. In these cases the user will need to set the encoding manually from the list of options. For Issue 1 above, there is a coding mismatch between the .dat file and the .opt file. Note that the 'Load file preview', and the 'Image preview' tabs work independently. This is based on the information in the .dat and .opt files, and their respective encoding. Therefore, if you have different encoding for the .dat and .opt files, only the file that matches the file encoding which has been selected in the interface will display properly. In the example below, the encoding is set to UFT-16. The .dat file is encoded UTF-16, but the .opt file is encoded as UTF-8. You can see that the Load file preview works fine, but the Image preview does not display the images. To resolve this issue, the encoding for the .dat and .opt files need to be the same, and that encoding needs to be set in the 'File encoding' field. Issue 2 is also an encoding problem. This time there is a mismatch between the .dat file and the extract text files. It looks like there are a few possibilities why there could be a mismatch with these files. Either, a) some load file creation tools allow different encoding for the .dat file and the extracted text when a load file is created. b) the .dat file, or the extracted text files have been converted to another encoding after the load file had been created. In either case, there is an encoding mismatch, and this mismatch is shown by a 'File can not be read: Input length = 1' error when the user clicks the Check for errors button in the Map Fields window. To fix this issue, again the user needs to make sure that the encoding for the .dat file and the extracted text are the same. When looking at these issues through support, we have noticed that the extracted text is usually in UTF-8 encoding, but the .dat file is in a different encoding. In this case it would be a lot easier to change the encoding for the .dat file, than to change the encoding for all of the extracted text files. If you do change the encoding for the .dat file, make sure that you also change the encoding for the .opt file if that file needs to be changed.
  4. I have received a load file with TIFF images and extracted text instead of a native document set. What is the best way to deal with/process these? Thanks in advance...
  • Create New...