Process for representing data in a computer network to facilitate access thereto

• US 9,792,347 B2
• Filed: 04/11/2016
• Issued: 10/17/2017
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: BeulahWorks, LLC
• Original Assignee: BeulahWorks, LLC
• Inventors: Guo, Site, Johnson, Robert E., Hilton, Blaine Robert, Nevill, David A.
• Primary Examiner(s): VO, TRUONG V
• Application Number:
  US15/095,689
• Publication Number:
  US 20160224647A1
• Time in Patent Office: 554 Days
• 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 process for representing data in a computer network to facilitate access thereto via at least one user interface, the process comprising:

at a controller implemented by at least one processing device, storing input data, received via at least a first hierarchical user interface implemented by the at least one processing device, in a first storage format in at least a first database of a knowledge repository, the input data being stored as objects and relationships between objects;

converting, by the controller, at least a portion of the input data stored in the first database to at least a second storage format and storing the input data in a second database of the knowledge repository, the first and second storage formats being different storage formats; and

receiving, by the controller from the first hierarchical user interface or at least a second hierarchical user interface, queries to access the input data, object information concerning the input data, and information concerning the input data in the first and second databases.

2. The process of claim 1, further comprising using interrelationships between objects and using network discovery techniques to create a social network representation of the objects and relationships therebetween.

3. The process of claim 1, wherein the converting step is initiated by analyzing patterns of the queries and updates of the input data.

4. The process of claim 1, further comprising updating, by the controller, the input data in the first and second databases.

5. The process of claim 1, wherein at least one of the first and second databases comprises a triplestore database.

6. The process of claim 5, wherein at least one of the first and second databases 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.

7. The process of claim 1, wherein the controller converts 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.

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

data size and data schema.

9. The process of claim 7, wherein the at least one data characteristic of the input data comprises any one or more of:

required data freshness and required data retention.

10. The process of claim 1, wherein the controller converts 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.

11. The process of claim 10, 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.

12. The process of claim 1, further comprising implementing, by the controller, a unified interface supporting common operations expressed in a non-database-dependent format, which command operations are converted to one or more database-dependent formats.

13. The process of claim 1, wherein the first hierarchical user interface comprises at least one major developer interface and the second hierarchical user interface comprises a minor developer interface.

14. The process of claim 1, wherein the queries are human-readable user data queries and the process further comprises, by the controller, generating machine-readable user data queries based on the human-readable user data queries and generating application metadata based on human-readable application specifications.

15. The process of claim 1, further comprising, by the controller, data mining to retrieve the input data from the knowledge repository based on machine-readable user data queries.

16. The process of claim 1, further comprising, by the controller, monitoring the queries and data patterns resulting therefrom.

17. A process for representing data in a computer network to facilitate access thereto via at least one user interface, the process comprising:

storing input data in a knowledge repository using at least one processing device, the input data being stored in the knowledge repository as objects and relationships between objects, the knowledge repository comprising at least two databases each storing the input data in a different storage format;

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

receiving, by a controller that is implemented by the at least one processing device, the input data, the object information, and the information from the at least two hierarchical user interfaces and causing, by the controller, the input data to be stored in the knowledge repository as an object based on the object information and the information.