Providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery

• US 8,140,494 B2
• Filed: 01/21/2008
• Issued: 03/20/2012
• Est. Priority Date: 01/21/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Raynaud-Richard, Pierre, Pogodin, Andrey
• Primary Examiner(s): Hwa, Shyue Jiunn
• Application Number:
  US12/017,236
• Publication Number:
  US 20090187797A1
• Time in Patent Office: 1,520 Days
• Field of Search: None
• US Class Current: 707/696
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Techniques are provided that enable the display of full text index-ability, indexing, and container extraction status of files in a collection repository in connection with content management. Further, techniques are provided that: guarantee the user knows which files failed to index and explode and which files are not indexable; tell the user which files have not been indexed yet, so they are not omitted from the analysis; allow users to work on the collected files without waiting for maximum possible indexing period; allow users to start working immediately on collected content; allow for displaying indexing and extraction status information relevant only to the search query; allow for automatic and manual update of a list of un-indexable file types; and allow for informing users about the processing status of a collection by sending notifications, displaying alerts, and providing appropriate views.

Claims

1. A method for providing collection transparency information to an end user to achieve a guaranteed quality document search and production in electronic data discovery, comprising the steps of:

providing a content management system configured for performing the steps of;

providing a search results page;

extracting indexing state and text index-ability information from a content repository with regard to files identified on said search results page;

classifying said files in said content repository with regard to text index-ability and indexing state as follows;

not indexable;

types of files that are known not to be indexable and wherein said content management system does not attempt to perform full-text indexing on said types of files to enhance user experience with time;

indexable, but not indexed yet;

indexable files that have not been indexed yet;

failed to index;

files that are considered to be indexable for which an indexing attempt failed; and

indexable and indexed;

files that were successfully indexed;

wherein text index-ability is any of;

not indexable and indexable and wherein indexing state is any of;

indexed, not indexed yet, and failed to index;

collecting statistical information on what file types are not indexable by collecting statistics of indexing failure per file type, said indexing failure per file type based on whether;

a file was of an indexable type but was corrupt;

a file was of an indexable type but indexing failed;

files of different types use a same file extension; and

a file was treated as indexable but it was not an indexable file type;

observing said collected statistics of indexing failure per file type by, over time, collecting the following information per file type;

how many files of each type were indexed successfully;

how many files of each type failed to index; and

how many files of each type have been uploaded;

based on said observance of said collected statistics of indexing failure per file type, calculating a ratio of indexing failure in accordance with the following formula;

ratio of failure of a given type=number of failed files of a given type/number of files of a given type uploaded and attempted to index;

reporting file types having a high indexing failure ratio;

classifying said file types having a high indexing failure ratio as not indexable and adding said file types to a do not index list;

displaying indexing and extraction status of files contained in said content repository and pertaining to a given matter or legal request or a particular search query in the processing status area of the search results page based upon said classifying said files, as well as said extracting indexing state and text index-ability information from said content repository; and

providing a processing status area of said search results page and a file detail information page for displaying a processing status warning next to a file entry to allow a user to see what processing problems occurred with each file;

wherein the steps of the method are performed on one or more computing devices.

2. The method of claim 1, further comprising the step of:

providing a processing area displaying warnings or error messages on files that have not been indexed yet, files that are not indexable, and files that failed to index.

3. The method of claim 2, wherein the processing area displays hyperlinks to affected files.

4. The method of claim 1, further comprising the step of:

providing a processing area displaying as error or warning messages container extraction status of container files residing in said content repository that pertain to a given matter or legal request.

5. The method of claim 1, further comprising the step of:

providing a processing area displaying indexing status or container extraction status warnings and errors only for the files that affect search results.

6. The method of claim 5, said step for providing the processing area displaying indexing status or container extraction status warnings and errors comprising:

returning a set of files to an end user that comprises only;

files that meet all the search criteria;

or

not indexed files that meet said all the search criteria except for keyword search criteria applied to a body of the file;

or

containers that are not exploded that meet said all the search criteria, except for keyword search criteria applied to a body of the files inside the container and file metadata search criteria applied to the body of the files inside the container.

7. The method of claim 1, further comprising the step of:

notifying a user who uploaded containers to said content repository or users responsible for coordinating said electronic data discovery effort that some containers failed to explode.

8. The method of claim 1, further comprising the step of:

providing a processing area comprising any of a search results page and a file detail information page for displaying a processing status warning next to a file entry to allow a user to see what processing problems occurred with each file.

9. The method of claim 1, further comprising the step of:

calculating a ratio of indexing failure in accordance with the following formula;

ratio of failure of a given type=number of failed files of the given type/number of files of the given type successfully indexed.

10. The method of claim 1, further comprising the step of:

automatically updating said do not index list with file types that have high ratio of failure as determined through comparison against a threshold value.

11. The method of claim 1, further comprising the step of:

postponing a decision to update said do not index list until a representative sample of files of a same type are uploaded and attempts to index said files fail.

12. The method of claim 1, further comprising the step of:

providing a separate view containing a list of files that have questionable status.

13. The method of claim 1, the classification of files that failed to index further comprising any of the following subcategories:

files that failed to index due to file corruption;

files that are failed to index because of indexing engine limitations; and

files that are mistakenly considered indexable.

14. The method of claim 1, further comprising the step of:

providing a processing area displaying a list of containers which failed to unpack to a user who uploaded said containers to said content repository.