We recommend preparing and outlining your database field structure in advance. This may involve discussions with a lead attorney and key people involved in the case. Making changes to the database structure once data has been loaded has a high potential for database corruption, so careful preparation helps minimize the need for changes later.
Use the database checklist to assist you when you first begin creating and indexing databases to ensure that you understand each step of the process and don't forget to verify critical data.
|
Making changes to your database template is the number one way to corrupt your database. It is important to prepare and outline your field structure in advance to avoid changes after data has been loaded. |
Database Capacities
The Database Capacities table lists the capacities for each of the database elements.
Database |
Capacity |
|---|---|
Number of documents |
500,000 |
Concatenated databases |
128 |
Document size |
3 billion characters |
Fields |
250 |
Characters per field |
12 million |
Database .ivt file |
6 gigabytes |
Database dictionary |
6 gigabytes |
Database file path name |
199 characters in length |
Database Checklist
Data Review |
|
|
Do you know how many documents or gigabytes (GB) of data have been received? |
|
Are your files converted to types that are recognized by Concordance Desktop? |
|
Do you understand Concordance Desktop field structure and how it affects importing data? |
Review Load Files |
|
|
Have you reviewed the contents of the data volume you are about to load? |
|
Have you reviewed your data load file for acceptable delimiters and date formats? |
|
Do you have fields set in place for data that you are importing? |
|
Have you verified that the bates number for the first record to be loaded does not overlap with the last bates number used in the existing collection? If it does overlap, a correction should be requested from the source prior to loading. |
|
Did you receive an image load file along with your images? If not, you can create one. |
|
Did you adjust the directory path of your image load files, if need be? |
|
Have you verified that your alias in the image load file matches the Image field in the Concordance Desktop database? |
|
Have you reviewed how your OCR has been formatted, named and organized? Do you know which CPL to use for import if the OCR was not included in the .dat file? |
|
Importing a .pst file requires that a user profile is set up for each user in Microsoft Outlook. Have you completed this process? |
Database Structure |
|
|
Did you create a database template that includes administrative fields? |
|
Did you select an image key field for your images? |
|
Did you validate the EDITTRAIL and CREATEDATE fields? |
|
Did you index all fields needed for full-text searching? |
|
Did you create additional miscellaneous fields? |
CPLs |
|
|
Did you verify supported CPLs for your current Concordance Desktop version by reviewing the ...\ProgramData\LexisNexis\Concordance Desktop\CPL folder, or Concordance Desktop Scripts Help topic? |
Case Review |
|
|
Have you reviewed case records to understand what types of files you are importing? |
|
Did you review case records to plan your field structure? |
|
Do you understand what types of reports you may be generating for maintenance and to support reviewers? |
|
Do you understand the file and media requirements for print productions, especially for opposing counsel? |
Ongoing Maintenance |
|
|
Have you outlined maintenance processes and schedules that affect your new databases? |
