Granted Patent B2

US 12,468,541 · App. 18/343,930 · Granted Nov 11, 2025

Inventors: Ofir Ezrielev (Beer Sheva, IL); Hanna Yehuda (Acton, MA); Kristen Jeanne Walsh (Austin, TX)

Assignee: Dell Products L.P.

G06F9/3867G06F9/3895

Abstract

Claims (52)

1 . A method of curating data by a data manager, the method comprising:

making an identification that data obtained from a data source associated with a data pipeline comprises an anomalous data point;

identifying a feature of a set of features associated with the anomalous data point that meets importance criteria;

obtaining a final data point based on the feature and through an interaction with the data source; and

populating the data pipeline with the final data point to provide the final data point to a downstream consumer of the data pipeline using one or more application programming interfaces (APIs) associated with the data pipeline, wherein populating the data pipeline with the final data point comprises storing the final data point in a data repository associated with the data pipeline, and

wherein the final data point is populated into the data pipeline to prevent the anomalous data point from being provided to a data consumer and negatively impacting operations and functionalities of a data processing system that uses the data in the data pipeline in one or more processes executed by the data processing system for providing computer-implemented services to the downstream consumer.

2 . The method of claim 1 , wherein the anomalous data point is subject to multiple valid but contrasting interpretations.

3 . The method of claim 2 , wherein the final data point is based on one of the multiple valid but contrasting interpretations as selected by the data source through the interaction.

4 . The method of claim 1 , wherein the interaction comprises presenting information regarding the feature to the data source, the information being usable to confirm whether the feature is expected by the data source.

5 . The method of claim 4 , wherein obtaining the final data point comprises:

obtaining a response from the data source that is responsive to the information;

in a first instance of the obtaining where the response confirms that the anomalous data point is expected:

using the anomalous data point as the final data point; and

in a second instance of the obtaining where the response rejects the anomalous data point as being expected:

using a data source supplied data point from the response as the final data point.

6 . The method of claim 1 , further comprising:

removing the anomalous data point from the data pipeline.

7 . The method of claim 1 , further comprising:

providing computer-implemented services using the final data point from the populated data pipeline.

8 . A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations for curating data by a data manager, the operations comprising:

making an identification that data obtained from a data source associated with a data pipeline comprises an anomalous data point;

identifying a feature of a set of features associated with the anomalous data point that meets importance criteria;

obtaining a final data point based on the feature and through an interaction with the data source; and

populating the data pipeline with the final data point to provide the final data point to a downstream consumer of the data pipeline using one or more application programming interfaces (APIs) associated with the data pipeline, wherein populating the data pipeline with the final data point comprises storing the final data point in a data repository associated with the data pipeline, and

wherein the final data point is populated into the data pipeline to prevent the anomalous data point from being provided to a data consumer and negatively impacting operations and functionalities of a data processing system that uses the data in the data pipeline in one or more processes executed by the data processing system for providing computer-implemented services to the downstream consumer.

9 . The non-transitory machine-readable medium of claim 8 , wherein the anomalous data point is subject to multiple valid but contrasting interpretations.

10 . The non-transitory machine-readable medium of claim 9 , wherein the final data point is based on one of the multiple valid but contrasting interpretations as selected by the data source through the interaction.

11 . The non-transitory machine-readable medium of claim 8 , wherein the interaction comprises presenting information regarding the feature to the data source, the information being usable to confirm whether the feature is expected by the data source.

12 . The non-transitory machine-readable medium of claim 11 , wherein obtaining the final data point comprises:

obtaining a response from the data source that is responsive to the information;

in a first instance of the obtaining where the response confirms that the anomalous data point is expected:

using the anomalous data point as the final data point; and

in a second instance of the obtaining where the response rejects the anomalous data point as being expected:

using a data source supplied data point from the response as the final data point.

13 . The non-transitory machine-readable medium of claim 8 , wherein the operations further comprise:

removing the anomalous data point from the data pipeline.

14 . The non-transitory machine-readable medium of claim 8 , wherein the operations further comprise:

providing computer-implemented services using the final data point from the populated data pipeline.

15 . A data processing system, comprising:

a processor; and

a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations for curating data by a data manager, the operations comprising:

making an identification that data obtained from a data source associated with a data pipeline comprises an anomalous data point;

identifying a feature of a set of features associated with the anomalous data point that meets importance criteria;

obtaining a final data point based on the feature and through an interaction with the data source; and

populating the data pipeline with the final data point to provide the final data point to a downstream consumer of the data pipeline using one or more application programming interfaces (APIs) associated with the data pipeline, wherein populating the data pipeline with the final data point comprises storing the final data point in a data repository associated with the data pipeline, and

wherein the final data point is populated into the data pipeline to prevent the anomalous data point from being provided to a data consumer and negatively impacting operations and functionalities of a data processing system that uses the data in the data pipeline in one or more processes executed by the data processing system for providing computer-implemented services to the downstream consumer.

16 . The data processing system of claim 15 , wherein the anomalous data point is subject to multiple valid but contrasting interpretations.

17 . The data processing system of claim 16 , wherein the final data point is based on one of the multiple valid but contrasting interpretations as selected by the data source through the interaction.

18 . The data processing system of claim 15 , wherein the interaction comprises presenting information regarding the feature to the data source, the information being usable to confirm whether the feature is expected by the data source.

19 . The method of claim 1 , wherein populating the data pipeline with the final data point further comprises:

removing the anomalous data point from the data pipeline while the data pipeline is being populated with the final data point.

20 . The method of claim 19 , wherein removing the anomalous data point from the data pipeline comprises deleting the anomalous data point from the data repository associated with the data pipeline.

Assignments (1)

Continuity (1)

References Cited (64)