Facilitated use of column and field data for field record universe in a knowledge store

• US 7,908,240 B1
• Filed: 10/28/2004
• Issued: 03/15/2011
• Est. Priority Date: 10/28/2004
• Status: Active Grant

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Claar, Jane Van Keuren, Mazzagatti, Jane Campbell
• Primary Examiner(s): Fleurantin; Jean B.
• Application Number:
  US10/975,223
• Time in Patent Office: 2,329 Days
• Field of Search: 707 1- 10, 707100-1041, 707200-206
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases

Abstract

Typically, field names are saved separately from tables as metadata in modern databases. Databases did not traditionally get built into interlocking trees datastores that recorded the data as events. However, in cases where one may wish to do that, thus avoiding the need for saving separate metadata from the table data of the data base, a need was found to establish an identity for particular columns or fields when working with databases or sources of data that provide table data in field/record format. So, to build interlocking trees datastores from such records a mechanism to record such data was created, adding a column ID, preferably to each field within each record or sequence that is to be recorded. Putting the column ID or identifier is inserted into the record during particlization between each column variable. In preferred embodiments a delimiter was included between the column ID or field name and the field variable. Appropriate hardware and software systems were employed to implement the invention.

Claims

1. A method of integrating knowledge of data record field contexts into an interlocking trees datastore structure, whereby said field contexts remain distinguishable when said record is recorded into said interlocking trees datastore structure via association of a field identifier with each field variable in said data record, the method comprising:

receiving said data record from a data source,

including a field identifier for each field variable in said record,

particlizing said record in an order such that a field identifier for each variable is included in a particle sequence corresponding to said record, and

sending said particle sequence to a K Engine for recording into an elemental root node of the interlocking trees datastore structure, the interlocking trees datastore structure comprising elemental root nodes, subcomponent nodes and end-product nodes using asCase and asResult bi-directional links for determining paths within the interlocking trees datastore structure, wherein an asCase path comprises a sequence of sub-component nodes linked with bi-directional asCase links ending with an end-product node and where each sub-component node in the asCase path has a bi-directional asResult link to an elemental root node or end-product node comprising an asResult path, wherein said K Engine records said data record by creating a unique node sequence in said interlocking trees datastore structure for each first occurrence of a field identifier, field variable combination during a recording of said data record from a given data source.

2. The method of claim 1 further comprising setting an indicator to cause a learn function to annex said field identifier to each said field variable in said data record received by said learn function.

3. The method of claim 2 wherein said application level component creates a data stream for said learn function from said data source and in so doing associates said field identifiers with each field variable in each record sequence received from said data source.

4. The method of claim 3 wherein said application level component is an Extract Transform and Load or a Filter function component.

5. The method of claim 3 wherein said application level component receives data from said data source in data source sending format and configures it to be in a format that has only the data desired.

6. The method of claim 3 wherein the data desired is determined by an applications developer.

7. The method of claim 3 wherein the data desired is predetermined.

8. The method of claim 3 wherein said application level component removes HTML Tags and delimiters from data from said data source.

9. The method of claim 3 wherein said application level component adds additional coincident reference data to said sequence.

10. The method of claim 1 wherein said including process further comprises inserting a delimiter between said field identifier and said each field variable.

11. The method of claim 1 wherein prior to said creating the unique node sequence, field identifiers are established for each field of said data record.

12. The method of claim 11 wherein establishing said field identifiers for each field of said data record occurs in a Learn Engine, and wherein said Learn Engine is configured by an applications developer directed configuration process, or by an application directed configuration process, prior to said Learn Engine receiving substantially any data from a source for said data record.

13. The method of claim 11 in which said step of establishing field identifiers occurs in an application level component, and wherein a said application level component connects to at least one data source through a process comprising:

data is sent from said at least one data source to said application level component, establishing a set of field identifiers based on said sent data.

14. The method of claim 13 wherein after said data is sent from said at least one data source to said application level component, identifying in said sent data, field identifiers.

15. A computer readable storage medium including digitally encoded data readable by a processing system providing a KStore stored therein, said KStore said KStore comprising a plurality of asCase and asResult paths, wherein an asCase path comprises a sequence of sub-component nodes linked with bi-directional asCase links ending with an end-product node, wherein each sub-component node in the asCase path has a bi-directional asResult link to an elemental root node or end-product node comprising an asResult path, said KStore having a quantity of sets of nodes for identifying field and field variable concatenations, each set of said nodes for identifying, identifying a given field in any record sequence and an associated field variable value, wherein each field and field variable concatenation is recorded into an elemental root node of the interlocking trees datastore structure in an interlocking trees datastore structure comprising elemental root nodes, subcomponent nodes and end-product nodes using asCase and asResult bi-directional links for determining paths within the interlocking trees datastore structure, wherein record data of the record sequence is recorded by creating a unique node sequence in said interlocking trees datastore structure for each first occurrence of a field identifier, field variable combination during a recording of said record data from a given data source.

16. The computer readable storage medium of claim 15 wherein between each field variable in a path from a BOT node to an EOT node a field identifying node is recorded.