KNOWLEDGE CAPTURE AND DISCOVERY SYSTEM

• US 20140279837A1
• Filed: 03/14/2014
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: BeulahWorks, LLC
• Original Assignee: BeulahWorks, LLC
• Inventors: Johnson, Robert E. III, Guo, Site, Hilton, Blaine Robert, Nevill, David Alan
• Granted Patent: US 9,430,549 B2
• Time in Patent Office: Days
• US Class Current: 707/603
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2428 Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes

Abstract

A system for knowledge capture and discovery comprises a knowledge repository in which all input data is stored as objects and relationships between objects, and which input data may be stored according to more than one storage format. At least two hierarchical user interfaces provide input mechanisms to obtain the input data, object information concerning the input data and relationship information concerning the input data, thereby permitting end user applications to be developed. A controller receives the input data, object information and relationship information from the at least two hierarchical user interfaces and causes the input data to be stored in the knowledge repository as an object based on the object information and the relationship information.

Claims

1. A system for knowledge capture and discovery, the system comprising:

a knowledge repository, implemented by at least one processing device, in which all input data is stored as objects and relationships between objects, and in which input data may be stored according to more than one storage format;

at least two hierarchical user interfaces, implemented by the at least one processing device, providing input mechanisms to obtain the input data, object information concerning the input data and relationship information concerning the input data; and

a controller, implemented by the at least one processing device and operatively connected to the knowledge repository and the at least two hierarchical user interfaces, operative to receive the input data, object information and relationship information from the at least two hierarchical user interfaces and to cause the input data to be stored in the knowledge repository as an object based on the object information and the relationship information.

2. The system of claim 1, wherein the knowledge repository stores all input data in a first database having a first storage format and selectively causes at least a portion of the input data to be converted from the first storage format to at least one second storage format and stored in at least one second database implementing the at least one second storage format, and wherein the first database comprise a triplestore database.

3. The system of claim 2, wherein the second database comprises any one or more of:

a relational database, a columnar database, a graph database, a key-value database, a document database and a file storage database.

4. The system of claim 2, wherein the controller instructs the knowledge repository to convert the portion of the input data from the first storage format to the second storage format based on at least one data characteristic of the input data.

5. The system of claim 4, wherein the at least one data characteristic of the input data comprises any or more of:

data size and data schema.

6. The system of claim 4, wherein the at least one data characteristic of the input data comprises any one or more of:

required data freshness and required data retention.

7. The system of claim 2, wherein the controller instructs the knowledge repository to convert the portion of the input data from the first storage format to the second storage format based on at least one usage characteristic of the input data.

8. The system of claim 7, wherein the at least one usage characteristic of the input data comprises any one or more of:

frequency of data writes, frequency of data updates, frequency of data reads, data read request types and concurrency of users.

9. The system of claim 2, wherein the controller implements an unified interface supporting common operations expressed in a non-database-dependent format, which command operations are converted to one or more database-dependent formats.

10. The system of claim 1, wherein the at least two hierarchical user interfaces comprise at least one major developer interface and a minor developer interface.

11. The system of claim 10, wherein the at least one major developer interface includes a first major developer interface comprising an integrated development environment supporting the development of software components.

12. The system of claim 10, wherein the at least one major developer interface includes a second major developer interface comprising a graphical user interface (GUI)-based platform supporting the development of any one or more of GUI applications and software widgets.

13. The system of claim 10, wherein the minor developer interface comprises a graphical user interface operative to construct an application metafile based on the software widgets.

14. The system of claim 13, further comprising:

a code generator, operatively connected to the controller and the minor developer interface, operative to generate an executable application based on the application metafile.

15. The system of claim 1, wherein the controller further comprises:

a natural language processing component operative to generate machine-readable user data queries based on human-readable user data queries and to generate application metadata based on human-readable application specifications.

16. The system of claim 1, wherein the controller further comprises:

a data mining component operative to retrieve stored data from the knowledge repository based on machine-readable user data queries.