Consolidator platform to implement collaborative datasets via distributed computer networks

• US 10,515,085 B2
• Filed: 06/19/2016
• Issued: 12/24/2019
• Est. Priority Date: 06/19/2016
• Status: Active Grant

• Current Assignee: Data.World, Inc.
• Original Assignee: Data.World, Inc.
• Inventors: Jacob, Bryon Kristen, Griffith, David Lee, Le, Triet Minh, Keen, Arthur Albert, Zelenak, Alexander John, Loyens, Jon, Hurt, Brett A., Reynolds, Shad William, Boutros, Joseph
• Primary Examiner(s): Beausoliel, Jr., Robert W
• Assistant Examiner(s): Hoang, Hau
• Application Number:
  US15/186,515
• Publication Number:
  US 20170364564A1
• Time in Patent Office: 1,283 Days
• CPC Class Codes: G06F 16/24575 using context
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries

Abstract

Various embodiments relate generally to data science and data analysis, computer software and systems, and wired and wireless network communications to provide an interface between repositories of disparate datasets and computing machine-based entities that seek access to the datasets, and, more specifically, to a computing and data storage platform that facilitates consolidation of one or more datasets, whereby a collaborative data layer and associated logic facilitate, for example, efficient access to, and implementation of, collaborative datasets. In some examples, a system may include data ingestion controller configured to format datasets to form a first and a second atomized dataset, the second atomized dataset including the first atomized dataset and one or more other atomized datasets. The system may include a dataset query engine configured to identify a portion of a dataset relevant to a query, and to retrieve query results from at least one of different data repositories.

Claims

1. A system comprising:

a data ingestion controller configured to receive multiple data files as differently-formatted datasets,

wherein at least a subset of disparate data repositories include differently-formatted datasets from which one or more atomized datasets are generated and stored in one or more repositories, at least one of which includes a triplestore; and

a dataset query engine configured to receive data representing a query associated with a user account identifier to access a dataset, the dataset being associated with another user account identifier and stored in the triplestore, and to identify datasets relevant to the query, the datasets being disposed in disparate data repositories, the dataset query engine further configured to identify a level of authorization associated with the user account identifier to facilitate access by the query of a secured set of protected data in the dataset associated with the another user account identifier, to generate one or more sub-queries based on the query to transmit a sub-query via a network to access the disparate data repositories, the sub-query being configured to access the secured set of protected data in the dataset stored in the triplestore based on the level of authorization, to retrieve data representing query results from the accessed disparate data repositories, at least two of the disparate data repositories being associated with different entities, and to

generate a notification of execution of the query associated with the user account identifier to transmit the notification via the network for presentation as activity data in a user interface associated with the another user identifier to notify a user associated with the another user account identifier that another user associated with the user account identifier accessed the dataset to facilitate collaborative data-related activity among different entities,

wherein the level of authorization associated with the user account identifier is configured to facilitate per-dataset authorization to provide access to the secured set of protected data, which is less than a total number of datasets associated with the another user account identifier,

wherein the datasets comprise atomized datasets that include one or more subsets of linked data points.

2. The system of claim 1 comprising a collaborative dataset consolidation system that comprises:

one or more memory devices storing modules of executable instructions; and

one or more processors configured to execute a module of executable instructions to implement the dataset query engine.

3. The system of claim 1 wherein the dataset query engine is further configured to retrieve the data representing the query results from an accessed external repository external to the system.

4. The system of claim 1 wherein the dataset query engine is further configured to determine a subset of data attributes associated with the query to identify the datasets relevant to the query, and to retrieve a subset of atomized datasets that include data associated with one or more of the data attributes.

5. The system of claim 4 wherein the dataset query engine is further configured to search for a derived attribute as at least one of data attributes to determine a data attribute associated with the query.

6. The system of claim 5 wherein the dataset query engine is further configured to analyze a plurality of datasets associated with the collaborative dataset consolidation system to infer data representing the derived attribute.

7. The system of claim 1 wherein the dataset query engine is configured to:

receive data representing another query into the collaborative dataset consolidation system, the another query being associated with the another user account identifier;

identify the datasets relevant to the another query; and

deny access to datasets to perform the another query if the level of authorization is absent.

8. The system of claim 1 wherein the dataset query engine is configured to:

receive data representing another query into the collaborative dataset consolidation system, the another query being associated with the another user account identifier;

identify the datasets relevant to the another query; and

grant access to at least one dataset to perform the another query if the level of authorization is present.

9. The system of claim 1 wherein dataset query engine is configured to generate the one or more queries as a federated query.

10. The system of claim 9 wherein the federated query is a query of disparate data stores.

11. The system of claim 9 wherein the federated query is a query of different triplestores.

12. A system comprising:

a data ingestion controller configured to;

receive a data file including a dataset, and to

format the dataset to form an atomized dataset including atomized data points each including data representing at least two objects and an association between the two objects, the data ingestion controller is further configured to

form another atomized dataset including the atomized dataset and other atomized datasets, wherein the data ingestion controller is configured to receive multiple data files, including the data file, as differently-formatted datasets, and format the differently-formatted datasets to form atomized datasets and stored in one or more repositories, at least one of which includes a triplestore, the another atomized dataset including data originating from the differently-formatted datasets, at least two of the differently-formatted datasets being associated with different entities; and

a dataset query engine configured to

receive data representing a query being associated with a user account identifier to access a dataset, the dataset being associated with another user account identifier and stored in the triplestore, the dataset query engine further configured to

identify a subset of the another atomized dataset relevant to the query, wherein portions of the another atomized dataset are disposed in different data repositories storing data as the differently-formatted datasets, the dataset query engine also configured to

identify a level of authorization associated with the user account identifier to facilitate access by the query of a secured set of protected data in the dataset associated with the another user account identifier,

generate a plurality of sub-queries each of which is configured to access to transmit a sub-query via a network at least one of the different data repositories, the sub-query being configured to access the secured set of protected data in the dataset stored in the triplestore based on the level of authorization, to

retrieve data representing query results via at least a portion of the atomized datasets from a subset of the different data repositories that store the data as the differently-formatted dataset, and to

generate a notification of execution of the query associated with the user account identifier to transmit the notification via the network for presentation in a user interface associated with the another user identifier to notify a user associated with the another user account identifier that another user associated with the user account identifier accessed the dataset to facilitate collaborative data-related activity among different entities,

wherein the level of authorization associated with the user account identifier is configured to facilitate per-dataset authorization to provide access to the secured set of protected data, which is less than a total number of datasets associated with the another user account identifier,

wherein the datasets comprise atomized datasets that include one or more subsets of linked data points.

13. The system of claim 12 wherein the data ingestion controller is configured to classify query portions.

14. The system of claim 13 wherein the data ingestion controller is further configured to identify a classification type to classify a portion of the query.

15. The system of claim 12 wherein the datasets comprise linked data points.

16. The system of claim 15 wherein linked data points comprise triples.

17. The system of claim 16 wherein at least one triple of the triples are formatted to comply with a Resource Description Framework (“

RDF”

) data model.