Buy Custom CT Summation Scripts

This script deals w/ the need to both import and export into and out-of Summation. Multi-Entry fields use carriage returns and line feeds w/in the field to delimit the list of data values. If you export multi-entry fields from Summation with the expectation of importing the data into other packages, like Excel or Access, you will not have the right number of fields in each line and will have records broken up across multiple lines in your text output. Running the first script replaces the carriage return/line feed with a delimiter of your choosing prior to export. After importing data into Summation with multi-entry field data delimited, the other script is run to replace the delimiters with carriage return/line feeds. The delimiter can be set to any ASCII character desired.

This Multientry Sort script automated sorts the contents of displayed multi-entry fields. The user can run the script on the results of a document summary search. It sorts the values in the multientry fields being displayed in Column View. It optionally deletes any duplicate values in any field.

This script exports all the columns currently displayed for all records in the current found set. It replaces carriage return/line feeds with semicolons and replaces double quotes with carets. This allows them to be properly imported by other programs. The characters can then be changed back in the program into which the data is imported. (This is similar to the replacement scripts described above, but is designed to work with other fields, like Summary or Attorney Notes, which may contain carriage returns and line feeds.)

This script builds an HTML file with search results from OCR documents associated with a found set of Core database records. The HTML report provides a summary of the total number of database records in the original found set, the number of total OCR hits, the DB search phrase and the OCR search phrase. Each hit shows DocID, page number/line no. of hit and 10 line excerpt.

This script allows the user to select multiple fields on which to run a tally. The script was originally designed to provide a tally of all the Name fields for a case, but has been expanded to support all fields. The report can be sorted by the field value or the number of hits. It can even provide a report with separate two listings, one sorted by value and the other by the number of hits.

This process combines multiple scripts to accomplish a tedious task. The first script allows a group of marked or found records to be marked for print. The second script collects the emails and edocs and creates a text file, with proper “page of pages” footer, for printing. This script overcomes the Internet Explorer “feature” that plagues the Summation script intended to provide this functionality.

Writes a DII file from a directory structure with the DOCID as the name of the Multi-Page TIFF file.

This script is designed to operate with single-page images within directories whose names are the DocID. The script creates a DII file with entries for each Directory under the root.

This script can be run on a daily basis. After launching, no operator intervention is required. The script does the following:* Cycles through all the cases in the case list, including those nested in sub folders. After opening them it will...* Backup DB and Notes database in the same manner that Summation doesn't.* Run the check, pack, blaze (If there are no records in the database, it will skip this step and record a message in the run log) Upon completion, the operator is notified if there were any errors reported so they can review the detailed logs.

This script allows the user to mark several items in their document database and enclose the images in an email. The script checks to make sure there is an image in the ImgInfo table, bundles all the pages into a single multi-page tiff, names the file the same thing as the docID, opens a new email and attaches the tiff file.

This script allows the user to mark one or more database records and have the associated images copied to a directory. The script 1) checks to see if an image exists, 2) merges all the pages of the image into a single, multi-page Tiff file, 3) creates a new directory, copies the tiff file(s) named after the docID(s). The user has the option to include annotations. (This feature is only supported under releases after and including 2.5.)

The purpose of the Re-Unitization Dashboard script is to help the user change document breaks for incorrectly unitized documents. Summation handles images on a document by document basis (rather than a page-by-page basis, as many image viewing programs do). Sometimes, documents may be incorrectly combined so that multiple documents are associated with a single record in Summation. This is generally considered a poor practice. In Summation, each document stands on its own. It is important, however, to correlate related documents. This script provides a user-friendly HTML dashboard that allows a user to designate new documents, parents, children and documents that must be combined. It produces a DII file that will update the database AND update the OCRBase, assuming the original txt files have not been deleted. It also provides a button that allows the user to delete any orphan records (due to combined documents). Other features: Validation prior to producing new DII and on-the-fly validation to ensure the user does not create illogical groupings, like a parent designation without children.

This script allows a user to enter the bates number of a document and be taken to that page in a document. The script runs the search to find the appropriate document, opens the document in the image view and jumps to the appropriate page. The script assumes that the bates numbers are being used as the BegDoc#/DocID. It does NOT adjust for suffixed pages, so there may need to be some adjustment once the “logical” page is presented.

This script checks all the records in the Core database and determines if it has a matching image record in the ImgInfo table. A report is generated. It also checks the page count field against the actual number of pages reported in the ImgInfo table and reports on variances. These variances can, optionally, be corrected.

This script checks all the records in the ImgInfo table and deletes those that do not have a related record in the core database. It has the option of either deleting the orphans or simply providing a report with a list of orphans. It also checks the page count field against the actual number of pages reported in the ImgInfo table and reports on variances. These variances can, optionally, be corrected.

This script was written for a client that was required to produce from Summation in a format that could be imported into opposition’s version of Summation. A production set was not acceptable. The script will take a found or marked set of records containing images and create a production set. The production set will include an index file derived from the columns in the current column view, a DII file that utilizes iteration, and copy the images from their current location to a unique directory under the case directory path. If the user does not wish to provide the coding information, they can delete the single file in which this information is stored, since it is NOT provided in the DII file.

This script allows the user to check one or more Transcripts in their Case Explorer and enclose the images in an email. The script encloses the transcripts in an Outlook email which the script creates (requires the user has Outlook on their client, and sets the attachment description as the same thing as the Transcript Description. (This one is under development for a client.)

This script allows the user to check multiple transcripts on their Case Explorer and automatically add links to exhibits based on multiple exhibit descriptions that could be in the transcripts. (i.e. Exhibit 53, Exhibit No. 53, Exhibit Number 53, simply “53”.) When searching for the exhibit number alone, as in “Why don’t we refer back to 53.”, the script prompts the user to make sure that the “53” is an exhibit reference instead of an unrelated term. This eliminates hours of paralegal work summarizing transcripts and preparing them for attorney review.

This script allows the user to check multiple transcripts, right-click on a Transcript Group folder and have the shortcuts for the checked transcripts created in that folder. This eliminates the tedious single drag-and-drop approach that is required today.