Outlined below are required considerations for produced data imports, specifically those which utilize a load file.
| Nextpoint Required Specifications |
|---|
| Load file in CSV or DAT formats in UTF-8 format. Ensure that the load file does NOT contain a BOM. |
| Preferred production format includes single page TIFF/JPG, any included natives, and text files named by starting bates number, and a CSV delimited load file with proper relative pathing to native and text files. Image files must be consistently named by their bates numbers without suffixes such as "_CONFIDENTIAL". Confidential coding should be indicated in the load file and stamped onto the face of each image. If page number suffixes (e.g. _0001) are required in image names, then all image files should contain the suffix including the first page such that the image names are a consistent length and sequential. |
| PDF image files with load files are also accepted and should be named by the bates start value of the document without any additional characters (e.g. the suffix "_CONFIDENTIAL"). If PDF image files are not named by bates but the load file contains a path to the image file PDF, the images may be imported, but this may increase load file complexity and limit the ability to import search text. |
| Load file paths included and accurate as to the location of natives (if applicable) and text files. If importing using multipage, document level image files (PDFs), paths to image files must be relative to where the load file resides and should not include starting periods or ending slashes. |
| Text files contain page breaks and are encoded as UTF-8 or ASCII. |
| Replace special characters in field headers with underscores. |
| Field headers are NOT case sensitive. |
See more information on the steps to handle a produced data with load file import here >>
Comments
Please sign in to leave a comment.