Text analysis system5392428Abstract A computer-based system for analyzing textual works is achieved by operating on a model of the text as stored in a relational database. The text is divided into user-defined segments, and the system maintains a series of records, each of which characterizes a segment of the text. The system generates a one-to-one association between each record and the indicia which indicate the length of the record and correspond to the beginning and end points of text segments. The system also includes topic records which maintain a list of topics. The system generates one-to-many associations between topics and records so that a link is established between a particular topic and one or more records. Based on the model, the system manages the text and generates reports for analysis of the text. Claims What is claimed is: Description FIELD OF THE INVENTION
TABLE 1
______________________________________
DATA TYPE MEANING
______________________________________
A Alpha (fixed length character
string).
B Boolean.
D Date.
H Time.
I Integer (2 bytes).
L Long integer (4 bytes).
T Text of any length.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The lines between the boxes of FIGS. 1A and 1B represent the relationships between the files. FIGS. 2A-2C show the structure of the individual files in the database map of FIGS. 1A and 1B. The set of all the files shown in FIGS. 1A, 1B, and 2A-2C constitutes one model. The present system may create additional models utilizing another set of identical files. Therefore, the present invention may be used, for example, for analyzing deposition transcripts from many different litigation cases. A. Case Information The files discussed in the text following immediately below typically contain information which characterizes identifying features of the text, as opposed to the content of the text. The information contained within these files is preferably used as a reference for all other files in the database map so that the system can associate information in the other files of a model with a particular body of source text. 1. Cases File The Cases File 100 contains the identification of one case, such as one litigation case. One case file may contain multiple transcripts. The fields of each record in the Cases File 100 may be defined as shown in Table 2.
TABLE 2
______________________________________
FIELD MEANING
______________________________________
version Version of the system operating on
this model.
dateTime Date and time when this version was
created.
doWarning If the user wants the system to
display a warning (such as a
protective order) before entering
data files.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc
2. Matters File The Matters File 101 contains information which identifies a body of source text for a particular witness or court proceeding. For example, the model may contain one Matters File for each witness in a litigation case. The fields of each record in the Matters File 101 may be defined as shown in Table 3.
TABLE 3
______________________________________
FIELD MEANING
______________________________________
matterType Number indicating witness or
proceeding.
first.sub.-- Judge
First name of the witness or,
for court proceedings such as
a trial or motion hearing,
name of the judge.
last.sub.-- title
Last name of the witness, or
title of the proceeding.
address.sub.-- fullnam
Witness' address, or full name
of the proceeding.
phone.sub.-- tribunal
Witness' phone number, or
tribunal of the proceeding.
fax.sub.-- number
Witness' fax number, or
tribunal file number for
proceeding.
ID Identification number for this
record.
caseID Identification number of the
corresponding record in the
Cases File 100.
topicIds Array of Identification
numbers for all topics
considered for this
transcript.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
3. Transcript Information File The Transcript Information File 106 typically contains identification information for the transcripts of each of the witnesses or proceedings of the Matters File 101. For example, the Matters File 101 may contain one record for a particular witness who was deposed on several different days. The Transcript Information File 106 normally would have a different record for the transcript of the witness' testimony for each of those days. While there is preferably only one record in the Matters File 101 for each witness or proceeding, that record may be linked to several records in the Transcript Information File 106. The fields of each record in the Transcript Information File 106 may be defined as shown in Table 4.
TABLE 4
______________________________________
FIELD MEANING
______________________________________
date Date of the deposition or
court proceeding.
preparedBy Optional name of the person
who is analyzing the
transcript.
matterID Identification number of the
corresponding witness' or
proceeding's record in the
Matters File 101.
location Address where the deposition
or proceeding occurred.
crName Name of the court reporter who
recorded the testimony in the
transcript.
crAddress Court reporter's address.
crFirm Court reporter's employer.
crPhone Court reporter's phone number.
startPage First page number of the
testimony in the transcript.
endPage Last page number of the
testimony in the transcript.
exhibitSetID Identification number of the
corresponding exhibit set
record for this transcript in
the Exhibits File 103.
volumeinfo Volume number (for multi-
volume transcripts).
linesPerPage Number of lines of testimony
per page in the transcript.
referenceCopy Whether it is a reference copy
(if a reference copy was
generated in order to convert
the ASCII file from the court
reporter).
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
4. Appearances File The Appearances File 109 typically contains additional information on each of the transcripts identified in the records of the Transcript Information File 106. Appearances typically means the attorneys present at the deposition or court proceeding. The appearances information preferably is linked to the record of the corresponding transcript in the Transcript Information File 106. The fields of each record in the Appearances File 109 may be defined as shown in Table 5.
TABLE 5
______________________________________
FIELD MEANING
______________________________________
name Name of the
attorney/representative.
otherInfo User-defined textual data.
transcriptID Identification number of the
corresponding record in the
Transcript Information File 106.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
B. Digest Records File The Digest Records File 111 typically contains one or more records for each transcript, and the information in the fields of a particular source text's records characterizes the content of the source text. The user establishes the length of each record, and each record may have a different user-defined length as desired. Each record contains data which identifies the locations in the source text which correspond to the beginning and end points of a record. If the source text is a deposition transcript, for example, the records corresponding to this transcript will contain information entered by the user which characterizes the witness' testimony. By using the Digest Records File 111 in conjunction with other files, the system may manipulate the data in the model to assist the user in analyzing the witness' testimony. These capabilities will be explained in more detail below. The fields of each record in the Digest Records File 111 may be defined as shown in Table 6.
TABLE 6
______________________________________
FIELD MEANING
______________________________________
fromLine Line number which corresponds
to the beginning of this
segment of text in the
transcript.
toLine Line number which corresponds
to the end of this segment of
text in the transcript .
transcriptID Identification number of the
corresponding record for this
transcript in the Transcript
Information File 106.
ID Identification number for this
record.
digest Summary of the testimony
within the beginning and end
points that correspond to this
record.
Comment User-defined annotation.
TopicSentence Sentence which characterizes
the content of the testimony
within the beginning and end
points that correspond to this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
In the preferred system, the fields which establish the length of the record, fromLine and toLine, are line numbers generated by the system which correspond to specific page and line numbers in the transcript or other document. The system preferably converts a page and line number in the transcript to a single line number by knowing the value of the linesPerPage field in the Transcript Information File 106. For example, if the transcript has 25 lines per page, and line number 4 on page 3 is the beginning of the record, this point will be converted in the preferred system to 54 (fromLine=(25 lines/page.times.2 pages)+4). Manipulation and management of the records is facilitated by using single numbers to define the limits of a record, as opposed to two numbers (page and line) for each limit. The comment field contains a user-defined annotation which may be any textual data. For example, the user may enter a note which reminds the user to take additional testimony from this witness on a particular topic. C. Topics Files The Topics File 104 contains a list of topics, one record for each topic. The topics may be subjects which characterize either a particular segment of the source text or items identified in the source text. In order to characterize a portion of the source text with a topic, the topics may be linked to a record in the Digest Records File 111 via the Topic Reference File 107. Topics may also be linked to an exhibit (item) via the TopicToExhibit Reference File 105. The present system may also create subtopics for the model. A subset of master topics, or simply topics, consisting of one or more of the topics, would typically be used with any transcript for a particular case, whereas a set of subtopics would be grouped with one particular topic. The fields of each record in the Topics File 104 may be defined as shown in Table 7.
TABLE 7
______________________________________
FIELD MEANING
______________________________________
topic Name of the topic.
ID Identification number for this
record.
superTopicID If this record is a subtopic,
superTopicID is the identification
number of the record for the topic
associated with this subtopic.
Otherwise, if this record is a
master topic, superTopicID is zero.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Topic Reference File 107 may be defined as shown in Table 8.
TABLE 8
______________________________________
FIELD MEANING
______________________________________
topicID Identification number for the
record containing a topic to
be associated with a record in
the Digest Records File.
digestRecordID Identification number for the
corresponding record in the
Digest Records File.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
As shown in Table 8, the Topic Reference File 107 creates a link between a topic record and a record in the Digest Records File. Since each topic may be linked to more than one record in the Digest Records File, the Topic Reference File 107 may create a one-to-many association between a particular topic and multiple records by having a series of records with the same topic record identification number and different identification numbers of records in the Digest Records File. The fields of each record in the TopicToExhibit Reference File 105 may be defined as shown in Table 9.
TABLE 9
______________________________________
FIELD MEANING
______________________________________
topicID Identification number for the
record containing a topic to be
associated with an exhibit record.
exhibitID Identification number for the
corresponding exhibit record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The model may likewise create a one-to-many association between a topic and multiple exhibits by creating a series of records in the TopicToExhibit Reference File 105 which contain the same topic record identification number and different exhibit record identification numbers. D. Exhibits Files The Exhibits File 103 contains a list of items referred to in the source text, typically one record for each item. The records in this file also contain user-entered information that characterizes the exhibit. Exhibits may be linked to topics as described above. Since the exhibits are referred to in the text, the exhibits may be linked, via the Exhibit Reference File 108, to the record in the Digest Records File which corresponds to that portion of the source text referencing the exhibit. The system may also group exhibits into sets using the Exhibit Sets File 102. The fields of each record in the Exhibit Sets File may be defined as shown in Table 10.
TABLE 10
______________________________________
FIELD MEANING
______________________________________
name Name of the exhibit set in this
record.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Exhibits File 103 may be defined as shown in Table 11.
TABLE 11
______________________________________
FIELD MEANING
______________________________________
setID Identification number of the
corresponding exhibit set
record to which this exhibit
record belongs.
depictor Description characterizing the
exhibit.
exhibitTypeID Identification number of
corresponding exhibit type
record.
addressee Person to whom the exhibit in
this record was addressed.
date Date of the exhibit.
author Author of the exhibit.
title Title of the exhibit.
documentNumber Bates number of the exhibit.
other User-defined textual data.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Exhibit Reference File 108 may be defined as shown in Table 12.
TABLE 12
______________________________________
FIELD MEANING
______________________________________
exhibitID Identification number for the
record containing an exhibit
to be associated with a record
in the Digest Records File.
digestRecordID Identification number for the
corresponding record in the
Digest Records File.
line Line number in the source text
where the exhibit is
referenced.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
Exhibits may also be linked to the Exhibit Types File 260 for characterizing an exhibit. For example, exhibits may be characterized as letters, memos, graphs, or any user-created category. The fields of each record in the Exhibit Types File 260 may be defined as shown in Table 13.
TABLE 13
______________________________________
FIELD MEANING
______________________________________
type Type of exhibit.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
In the preferred system, the user may also group the exhibits according to user-defined classes. Whereas the Exhibit Sets File 102 would typically be used with predefined sets such as plaintiff's deposition exhibits, the Exhibit Class File 261 may be used to create userdefined groupings of exhibits. For example, a user may define a class as "documents authored by Smith," and this class could include documents from any exhibit set. Therefore, classes may also be used to group exhibits across multiple exhibit sets. The fields of each record in the Exhibit Class File 261 may be defined as shown in Table 14.
TABLE 14
______________________________________
FIELD MEANING
______________________________________
Class User-defined classification of
exhibits.
ID Identification Number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
Exhibits may be grouped into a class by linking records in the Exhibits File with records in the Exhibit Class File. The Exhibit Class Reference File 262 establishes the associations between exhibits and classes. The fields of each record in the Exhibit Class Reference File 262 may be defined as shown in Table 15.
TABLE 15
______________________________________
FIELD MEANING
______________________________________
Exhibit Class ID Identification number of an
exhibit class.
Exhibit ID Identification number for a
record of an exhibit to be
included in this exhibit
class.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
E. Dates File The Dates File 116 allows the user to characterize portions of the source text with one or more dates and times or periods of time, expressed as a range of dates or times. This date and time typically refers to the content of the source text. For example, if a witness testified that an event occurred on a certain date, the user could enter this date, and the model would associate this date with the record in the Digest Records File that corresponds to that portion of the witness' testimony in the transcript. By associating dates and times with the records in the Digest Records File, the system may sort and display records in the Digest Records File chronologically. The chronological presentation of data is very useful to a litigator, for example, in seeing how events progress over time. The fields of each record in the Dates File 116 may be defined as shown in Table 16.
TABLE 16
______________________________________
FIELD MEANING
______________________________________
date1 First date, or the beginning
of a period indicated by a
start date and end date, the
date or period, as the case
may be, characterizing a
portion of the source text
represented in a record in the
Digest Records File.
time1 Optional time for date1 or an
unspecified date.
date2 Optional second date
representing the end date if a
period was specified to
characterize the portion of
the source text represented in
a record in the Digest Records
File.
time2 Optional time for date2 or an
unspecified date.
digestRecordID Identification number for the
corresponding record in the
Digest Records File.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
F. Reminders File The Reminders File 117 allows the user to enter reminders, and the system may associate those reminders with a particular record in the Digest Records File via the Reminder Reference File 112. A reminder may be, for example, a note to the user that more work needs to be done on a particular record in the Digest Records File. The fields of each record in the Reminders File 117 may be defined as shown in Table 17.
TABLE 17
______________________________________
FIELD MEANING
______________________________________
reminder Description of the reminder.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Reminder Reference File 112 may be defined as shown in Table 18.
TABLE 18
______________________________________
FIELD MEANING
______________________________________
reminderID Identification number for the
record containing a reminder
to be associated with a record
in the Digest Records File.
digestRecordID Identification number for the
corresponding record in the
Digest Records File.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
G. Priorities File The Priorities File 119 allows the user to enter levels of priority, and the system may associate a level of priority with a particular record in the Digest Records File via the Priority Reference File 118. A priority may be, for example, a degree of importance of the information in the records in the Digest Records File, as determined by the user. The Priorities File 119 and Priority Reference File 118 allows the system to sort and search records in the Digest Records File by importance, which is a useful feature in assessing, for example, various portions of a witness' testimony. The fields of each record in the Priorities File 119 may be defined as shown in Table 19.
TABLE 19
______________________________________
FIELD MEANING
______________________________________
priority Description of the priority.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Priority Reference File 118 may be defined as shown in Table 20.
TABLE 20
______________________________________
FIELD MEANING
______________________________________
priorityID Identification number for the
record containing a priority
to be associated with a record
in the Digest Records File.
digestRecordID Identification number for the
corresponding record in the
Digest Records File.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
H. Work Log/Users Files The Work Log File 115 allows the system to maintain a listing of all work performed on a particular portion of the source text. This may include the name of the person who entered or summarized the text, the dates and times when they worked on the source text, and the duration of time spent working on the source text. This type of information may be useful when, for example, the time spent summarizing a deposition transcript is billed to a litigating attorney's client. In the disclosed system, the Work Log File 115 works in combination with the Users File 114 to keep track of this information. Each user normally has only one record in the Users File 114. Furthermore, each user's record in the User's File 114 may be linked to several records in the Work Log File 115, since the user may work on multiple transcripts or have multiple work log entries. The fields of each record in the Users File 114 may be defined as shown in Table 21.
TABLE 21
______________________________________
FIELD MEANING
______________________________________
lastName Last name of the user.
firstName First name of the user.
ID Identification number for this
record.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
The fields of each record in the Work Log File 115 may be defined as shown in Table 22.
TABLE 22
______________________________________
FIELD MEANING
______________________________________
userID Identification number for the
corresponding record in the Users
File 114 containing the name of the
person who is working on the
transcript.
event Number indicating a particular user
action.
where Identification number indicating
where the event occurred.
date Date when the event occurred.
time Time when the event occurred.
where2 Identification number of further
location information if required
for an event.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
I. Transcripts File The Transcripts File 110 is used for importing the source text from an ASCII file into the model. Along with the hard copy of a transcript, court reporters will usually provide a floppy disk of the transcript in ASCII format. The formatting, however, such as the number of lines per page, may vary among different court reporters. The Transcripts File 110 stores a converted version of the ASCII file. A separate converter module in the system converts the ASCII file to a format compatible with the model so that all imported ASCII files are in the same format in the model. The converter module converts the ASCII file by the steps of: (1) parsing the source text; (2) assigning internal reference numbers to the lines of the source text; (3) refining the source text to remove, for example, blank lines; and (4) obtaining from a user the beginning and end page and line numbers of the source text. The fields of each record in the Transcripts File 110 may be defined as shown in Table 23.
TABLE 23
______________________________________
FIELD MEANING
______________________________________
transcriptID Identification number of the
record in the Transcripts
Information File 106 that
corresponds with this source
text record.
TranscriptText The imported and converted
ASCII text file.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
J. Files for Indexing Transcripts FIG. 2C shows the files of the preferred relational database that are used for indexing the transcripts. These files include the WordList File 113, Indexes File 251, Occurrences File 252, and Transcripts File 253. FIG. 22 shows the interrelationship between these files for the indexing structure of the preferred database. This indexing is used for full-text searching and reporting. Full-text indexing means that the system maintains an alphabetical list of every word in the source text and the corresponding locations of where those words occur in the source text. This type of index provides for a very fast and efficient method of searching imported source text for any word or combinations of words. WordList File 113 contains a list of each unique word contained in all of the indexed transcripts in the model. Each word typically has a unique integer identification number. Preferably, there is only one word list for each case. Indexes File 251 comprises one or more files, typically one file for each transcript that is indexed. In the preferred embodiment, each index contains a long integer entry for every word that is contained in the case at the time that the transcript is indexed, and each entry provides the offset to the occurrences of the particular word in the occurrences file for the transcript. The number of occurrences of a particular word may be obtained by subtracting the value at the word's location from the value at the next word's location in the index. Occurrences File 252 comprises one or more files, normally one occurrence file for each transcript that is indexed. For every word contained in the transcripts, there are one or more integers contained in an occurrence file describing the locations of the word within the transcript. Transcripts File 253 contains a file for each body of source text, for example, one file for each transcript that has been imported into the model. III. MANAGEMENT AND ANALYSIS OF A MODEL In the preferred embodiment, a model primarily comprises a series of records in the Digest Records File 111, which represents and characterizes the source text. The other files in the relational database of FIGS. 1A and 1B provide for associating other information with the records in the Digest Records File. For example, exhibits may be associated with any record in the Digest Records File, so that the system may track exhibits across multiple transcripts. Also, topics may be associated with any record in the Digest Records File, which allows for searching and sorting by a particular topic or grouping of topics. This feature is useful in litigation because it provides for analysis of the data contained in the records in the Digest Records File by issues of fact and law. The present system preferably operates using a graphical user interface. FIG. 11 shows a preferred user interface, dialog window 128, for accessing various modules of the system. Area 129 contains a listing of the source texts, which are identified by name and date. The date is used in conjunction with the name for identification purposes since, for example, one particular witness may have multiple transcripts of deposition testimony. Dialog window 128 allows the user to execute the following functions of the system by selecting the corresponding button: add a new proceeding 130 or new witness 131 to the model; enter a new transcript 132; open the records in the Digest Records File of an existing transcript 133; delete a transcript 134; check the information (edit info. 135) that has been entered for a transcript in the Transcript Information File 106; enter local subjects 136; enter exhibits 137; perform a full-text search 138 of a transcript; enter keywords 139; index transcripts 140; enter a value 141 in the doWarning Field of the Cases File 100; enter master subjects 141; generate reports 142 from the model; close a case file 143; and exit the system 144. A user would typically enter exhibits and topics before creating records in the Digest Records File. Therefore, when records in the Digest Records File are created, the user may associate topics and exhibits with records in the Digest Records File. Selecting the master subjects button 141 will bring up the preferred user interface for entering topics shown as dialog window 147 in FIG. 12. The user may enter topics or subjects in area 145. Area 146 displays the list of master subjects. Upon exiting from dialog window 147, the preferred system writes the new topics into the Topics File 104 and assigns a unique identification number to each topic. After a transcript has been created in the preferred system, a user may enter (batch) all or a portion of the exhibits for that transcript. Selecting the batch exhibits button 137 in the dialog window 128 brings up the preferred user interface for entering an exhibit set shown as dialog window 150 in FIG. 13. Area 151 contains a listing of the current exhibit sets for this model. The user may either use an existing set or enter a new exhibit set. If a user enters a new exhibit set, then the data for the new set is written to the Exhibit Sets File 102 upon exiting from dialog window 150. After selecting an exhibit set, the user will be taken to the preferred user interface for entering the exhibit depictor, and optionally exhibit information shown as dialog window 155 in FIG. 14. Dialog window 155 has several areas, each of which corresponds to a field in the Exhibits File 103. Upon entering each exhibit, the system writes the corresponding information for the exhibit to a new record in the Exhibits File 103 and generates a unique identification number for each exhibit record so that the Exhibits File 103 will contain a series of records, one record for each exhibit. From the main dialog window 128, the user may also access dialog window 160 shown in FIG. 15 for entering keywords, also known as queries. Area 161 contains a list of all indexed words from the transcripts (source text). Area 162 contains a list of the words from area 161 that the user has selected to be keywords. Upon exiting dialog window 160, the preferred system writes the keywords to a file. The preferred system identifies the keywords by assigning a bit to each indexed word. One value of the bit, for example, a value of binary 1 indicates that the indexed work is a keyword, and a value of binary 0 indicates that the indexed word is not a keyword. A. Creating a Record in the Digest Records File The user creates records in the Digest Records File 111 by opening a new or current transcript from dialog window 128, which takes the user to the main window 170 shown in FIG. 16. Window 170 contains: area 174 for displaying the imported source text; area 172 for displaying topics and allowing the user to select topics; area 171 for entering digests which characterize a portion of the source text; area 175 for entering a topic sentence; and control area 173. Control area 173 allows the user to establish the demarcation indicia for a record in the Digest Records File, enter comments, and make exhibit associations. In the preferred embodiment, a user establishes the length of a record by scrolling through the source text in area 174 and selecting the From button 176 and To button 177 at the desired beginning and end locations respectively of a record. The range of a record is defined by the user-entered beginning page and line number and end page and line number for a record in the Digest Records File. When a record is created in the relational database, the values in the From and To areas correspond to the fromLine and toLine Fields respectively of the Digest Records File 111. In the preferred embodiment, the user may alternatively work with a hard copy of the transcript, i.e. without having the transcript on line in area 174 of main window 170. In this case, main window 170 would not contain area 174, and main window 170 would have a control area that allows a user to enter actual page and line numbers into the From and To fields. The values in the From and To fields are written to the FromLine and ToLine fields of Digest Records File 111 to create a record. Creating a representation of the source text by way of a model provides the unique advantage of allowing a user to work with only a hard copy of the source text. Aside from the user manually entering page and line numbers to establish the limits,of a record, all other functions of the control area would remain the same. The user may, among other things, enter a digest to characterize the source text, associate topics with records, enter exhibit references, and add annotations. FIG. 4 shows a preferred data flow for entering additional information into a record in the Digest Records File. The user enters a digest in area 171. The digest may be a summary of the content of the transcript within the limits established by the From and To indicators. The digest may also be actual portions of the source text which the user places in the digest area 171 by moving a portion of the source text from area 174 to area 171. The information in the digest area 171 is stored in the Digest Field of the Digest Records File 111. Selecting the comments button 178 brings up a window (not shown) that allows the user to enter an annotation. The annotation is stored in the Comments Field of the Digest Records File 111. The annotations are linked to records in the Digest Records File as shown in FIG. 1. The annotation is typically in text. However, one skilled in the art will recognize that it is possible for the system to handle other forms of annotations, such as digitized voice. Area 175 allows the user to enter a topic sentence which characterizes the content of the selected portion of the source text. The topic sentence is stored in the Topic Sentence Field of the Digest Records 111. Selecting button 179 brings up a window (not shown) that allows the user to enter chronological information regarding the content of the selected portion of the source text. This chronological information is stored in the Dates File 116 and is linked to a record in the Digest. Records File as shown in FIG. 1. The chronological information may be, for example, dates and times of when events occurred according to the witness' testimony in the transcript. Using main window 170, the user may also enter topic and exhibit references for a particular record. Since the preferred system operates in a windows environment, these associations, or any of the above information, may be entered in any order before the data and references are written to the relational database of FIG. 1. The preferred data flow for the writing the information for a record to the Digest Records File 111 is shown in FIG. 5. B. Topic References A user enters topic references in area 172. The user creates a reference by clicking the cursor on the topic that the user wants to reference to this record in the Digest Records File. When the user clicks on the topic, a check mark appears next to the topic to indicate that it has been selected. When the system writes the digest information entered by the user to the database as shown in FIG. 5, the system looks for selected topics. The identification numbers for the selected topics are written into a series of records in the Topic Reference File 107 along with the identification numbers of the corresponding records in the Digest Records File. A series of records in the Topic Reference File 107 may generate one-to-many associations between topics and records in the Digest Records File, since one topic may be referenced to multiple records in the Digest Records File. This also means that changing a topic will affect all the records in the Digest Records File referenced to that topic in the Topic Reference File 107. C. Exhibit References In the preferred embodiment, selecting the exhibits area 180 in main window 170 brings up window 185 shown in FIG. 17, which allows the user to reference exhibits to the current record in the Digest Records File. The preferred data flow of the system for generating exhibit references in the model is shown in FIG. 6. The user creates an exhibit reference by first selecting one of the exhibits displayed in area 189. Area 189 displays all the available exhibits in a particular set. Next, the user selects the Do button 188. The system then stores, in the Exhibit Reference File 108, the identification numbers for the selected exhibit and corresponding record in the Digest Records File. Exhibit Reference File 108 may contain multiple records for the same exhibit that references different records. This generates a one-to-many association between each exhibit and one or more records in the Digest Records File. Area 187 displays the exhibits which have been referenced for the range of source text that corresponds to the length of the current record in the Digest Records File. The user may display exhibits that have been referenced for a different range by selecting the Show References button 191. Window 185 also allows the user to enter new exhibits by selecting the New button 186. The user may edit the description of a particular exhibit by selecting the Edit Description Button 190. D. Other Functions of Control Area 173 Control Area 173 in FIG. 16 has the following additional functions. Selecting button 205 moves the user to the previous record in the Digest Records File 111. Selecting button 206 moves the user to the next record in the Digest Records File. Selecting either button 205 or 206 initiates the process shown in FIG. 5 of creating a record in the Digest Records File 111 by writing the information entered by the user to a new record and assigning a unique identification number to that record. The Check button 207 allows the user to verify whether the current range setting is valid, since the system does not allow the ranges of records in the Digest Records File to overlap. Selecting the Ranges button 195 brings up a Ranges Window 200 shown in FIG. 18. Ranges Window 200 shows a listing that represents the records in the Digest Records File 111 for the current transcript. Column 210 shows the beginning page and line numbers for each record in the Digest Records File. Column 211 shows the end page and line numbers for each record in the Digest Records File. Column 212 indicates whether each record in the Digest Records File has exhibit references. Column 213 indicates whether a comment has been created for each record in the Digest Records File. Finally, column 214 displays the topic sentence for each record in the Digest Records File. The Ranges Window 200 is a concise and efficient method of displaying a representation of the records in the Digest Records File. IV. GENERATING REPORTS FROM THE MODEL The model of the present invention provides the system with a high degree of flexibility and versatility in generating reports from the model. The reports provide the user with powerful tools to assist in the analysis of the information contained within the source text. The system is capable of generating a variety of output reports which are explained below. The reporting options are accessed via buttons 138 and 142 on the dialog area 129 (see FIG. 11). The user has the option of having the system generate a report on a user interface, such as a monitor, or generating a hard copy of the report. A. Full-Text Searching and Reporting 1. Word/Topic Searching Selecting the Full-Text Search button 138 brings up the Full-Text Search Dialog Window 220 shown in FIG. 19. Dialog window 220 contains areas that allow the user to generate various reports through searching all words contained within one or more transcripts. Areas 221-224 allow the user to enter words to search. Area 231 displays a list of all words in indexed transcripts contained within the case. This shows the user if the user-selected search word is actually contained within the case and is a convenient feature for increasing the efficiency of generating reports. FIG. 7 shows the preferred flow of data for performing a full-text search based upon the terms or topics in areas 221-224. 2. Queries Area 225 allows the user to perform searches in a user-selected search domain, optionally combining user-selected search terms in areas 221-224 in a Boolean logical relationship with user-selected search terms in areas 229-230. The query may also optionally be confined to a character string alone (whole word) or as part of another string (partial word). The search domains are: source text (transcript); comments; digests; and topic sentences. The Boolean logical operators available for searching are as follows: OR function using areas 221-224; AND function using area 226; NOT function using area 227. The preferred system performs Boolean searching according to the pseudo code representation Shown in Table 24.
TABLE 24
______________________________________
pseudo code for Boolean full-text search
______________________________________
Find all occurrences of first word within the
chosen search domain and store them in a list,
wordOneOccurrences.
Find all occurrences of second word within the
chosen search domain and store them in a list,
wordTwoOccurrences.
FOR each occurrence in wordOneOccurrences DO
FOR each occurrence in wordTwoOccurrences DO
IF the combination of the first word
occurrence and the second word occurrence
satisfy the chosen Boolean query
THEN
add a representation of the two occurrences
to a list of occurrences maintained for this
query, queryResults.
______________________________________
.COPYRGT. 1991 Robins Analytics, Inc.
3. Context Searching A context search is available using area 228 (see FIG. 19). The context is a user-defined integer value, and the system performs a full-text context search by searching for one or more terms within the context of one or more other terms in the user-selected search domains described above. In the preferred embodiment, the context is a user-defined number of lines in the transcript. FIG. 8 shows the preferred flow of data for performing a full-text context search and generating a report. FIG. 20 shows an example of full-text search report, showing the results of searching all the source texts for the whole word "acetone" within five words of the partial word "flam." C. Reporting From Selected Fields The preferred system has the capability to report information in the model from user-selected fields in various files of the relational database of FIG. 1. The preferred user interface for generating reports from user-selected fields is shown as dialog window 235 in FIG. 21. Area 240 displays the source text files from which the system may generate the reports. The user may select one or more of the source text files. Area 241 allows the user to select one more fields from which to report information contained within the files of the relational database. FIG. 9 is a preferred flow of data through the system for generating these reports. D. Graphical Reports of Database Relations The system also has the capability to generate a graphical report that shows the relations between files in the database. For example, as shown in FIG. 10, the system may generate a report that shows a graphical relationship between each exhibit set in the Exhibit Sets File 102 and all records in the Exhibits File 103 which are linked to the exhibit sets. While the present invention has been described in connection with the preferred embodiment thereof, it will be understood that many modifications will be readily apparent to those skilled in the art, and this application is intended to cover any adaptations or variations thereof. For example, while the preferred embodiment has been shown to operate on deposition and court proceeding transcripts, the present invention may be used for all types of textual works, including but not limited to, books, periodicals, magazines, documentation of scientific research, and multivolume works. Likewise, the preferred embodiment of the present invention is shown as operating from a Pascal implementation on a Macintosh hardware platform. One skilled in the art will recognize that other programming or hardware environments may be used without departing from the scope of the invention. It is manifestly intended that this invention be limited only by the claims and equivalents thereof.
|
Same subclass Same class Consider this |
||||||||||
