Metadata-based data valuation

1. A method, comprising:

obtaining at least one application data set stored in a data repository;

analyzing the application data set to generate at least one source metadata node, at least one intermediate metadata node and at least one end-user metadata node, the application data set contains data generated by a plurality of application program types comprising: a source type, an intermediate type, and a destination type, wherein at least one source type application generates source data, at least one destination type application generates end-user deliverable data, and at least one intermediate type application generates intermediate data in between the source data and the end-user deliverable data;

analyzing the source data to generate one or more source metadata attributes, the one or more source metadata attributes describing the source data;

performing computations on the source data to generate one or more intermediate metadata attributes, the one or more intermediate metadata attributes describing the intermediate data;

performing computations on at least one of the intermediate data and the source data to generate one or more end-user deliverable metadata attributes, the one or more end-user deliverable metadata attributes describing end-user deliverable data;

populating the at least one or more source metadata attributes into the at least one source metadata node, the at least one or more intermediate metadata attributes into the at least one intermediate metadata node, and the one or more end-user deliverable attributes into the at least one metadata end-user node;

combining the at least one source metadata node, the at least one intermediate metadata node and the at least one end-user metadata node to form a hierarchical data structure, the hierarchical data structure comprising source valuation nodes, intermediate valuation nodes, and at least one end-user valuation node;

determining a data set value for at least a subset of the data set of the hierarchical data structure corresponding to an end-user node value for the at least one end-user valuation node;

traversing the hierarchical data structure from the at least one end valuation node to the intermediate valuation nodes and the source valuation nodes; and

assigning node values to the intermediate level valuation nodes and to the source valuation nodes based on respective contributions to the at least one end-user valuation node;

wherein the steps are implemented via at least one processing device operatively coupled to the data repository.

2. The method of claim 1 , further comprising assigning node values to the source valuation nodes, the intermediate valuation nodes, and the at least one end-user valuation node at each level of the hierarchical data structure, and determining the data set value for the application data set stored in the data repository based on the node values assigned to at least a subset of the source valuation nodes, the intermediate valuation nodes, and the at least one end-user valuation node of the hierarchical data structure.

3. The method of claim 2 , further comprising defining one or more relationships between the source valuation nodes, the intermediate valuation nodes, and the at least one end-user valuation node of the hierarchical data structure.

4. The method of claim 1 , wherein:

the one or more source metadata attributes describe the source data in a native form.

5. The method of claim 1 , wherein:

the one or more source metadata attributes that populate the source level valuation nodes comprise one or more of: source data table definitions, source data view definitions, source data field definitions, and unstructured source data terms;

the one or more intermediate metadata attributes that populate the intermediate level valuation nodes comprise one or more of: intermediate data table definitions, intermediate data view definitions, intermediate data field definitions, and unstructured intermediate data terms; and

the one or more end-user deliverable metadata attributes that populate the end-user level valuation nodes comprise one or more of: end-user data table definitions, end-user data view definitions, end-user data field definitions, and unstructured end-user data terms.

6. The method of claim 1 , wherein the one or more end-user deliverable metadata attributes comprise business type metadata, and the one or more source metadata attributes and the one or more intermediate metadata attributes comprise technical type metadata.

7. The method of claim 1 , wherein a given one of an intermediate valuation node and a source valuation node is assigned a value equal to a product of a weight and the value of the at least one end-user valuation node that functions as a root node to the given one of the intermediate valuation node and the source valuation node.

8. The method of claim 7 , wherein a given source valuation node is assigned a value based at least in part on to a number of the intermediate valuation nodes and the at least one end-user valuation node to which the given source valuation node contributes divided by the total number of intermediate valuation nodes and the at least one end-user valuation node.

9. The method of claim 2 , wherein the assigning step further comprises assigning values by an end user assigning values to at least a portion of the source valuation nodes, the intermediate valuation nodes and the at least one end-user valuation node in the hierarchical data structure.

10. The method of claim 1 , further comprising modifying the hierarchical data structure by at least one of adding a node, deleting a node, and updating a node.

11. The method of claim 1 , wherein the data set value is calculated as a function of at least one of when the data set value is calculated and from where calculation of the data set value is requested.

12. The method of claim 1 , further comprising:

identifying, as a candidate data set from the data repository, an application data set that has a data valuation at or below a given low valuation threshold; and

at least one of deleting one or more candidate data sets from the data repository, and locking one or more candidate data sets to prevent deletion from the data repository.

13. An article of manufacture comprising a processor-readable storage medium having encoded therein executable code of one or more software programs, wherein the one or more software programs when executed by one or more processing devices implement the steps of:

obtaining at least one application data set stored in a data repository;

analyzing the application data set to generate at least one source metadata node, at least one intermediate metadata node and at least one end-user metadata node, the application data set contains data generated by a plurality of application program types comprising: a source type, an intermediate type, and a destination type, wherein at least one source type application generates source data, at least one destination type application generates end-user deliverable data, and at least one intermediate type application generates intermediate data in between the source data and the end-user deliverable data;

analyzing the source data to generate one or more source metadata attributes, the one or more source metadata attributes describing the source data;

performing computations on the source data to generate one or more intermediate metadata attributes, the one or more intermediate metadata attributes describing the intermediate data;

performing computations on at least one of the intermediate data and the source data to generate one or more end-user deliverable metadata attributes, the one or more end-user deliverable metadata attributes describing end-user deliverable data;

populating the at least one or more source metadata attributes into the at least one source metadata node, the at least one or more intermediate metadata attributes into the at least one intermediate metadata node, and the one or more end-user deliverable attributes into the at least one metadata end user node;

combining the at least one source metadata node, the at least one intermediate metadata node and the at least one end-user metadata node to form a hierarchical data structure, the hierarchical data structure comprising source valuation nodes, intermediate valuation nodes, and at least one end-user valuation node;

determining a data set value for at least a subset of the data set of the hierarchical data structure corresponding to an end-user node value for the at least one end-user valuation node;

traversing the hierarchical data structure from the at least one end valuation node to the intermediate valuation nodes and the source valuation nodes; and

assigning node values to the intermediate level valuation nodes and to the source valuation nodes based on respective contributions to the at least end-user valuation node.

14. The article of manufacture of claim 13 , wherein a given source valuation node is assigned a value based at least in part on to a number of the intermediate valuation nodes and the at least one end-user valuation node to which the given source valuation node contributes divided by the total number of intermediate valuation nodes and the at least one end-user valuation node.

15. The article of manufacture of claim 13 , wherein:

the one or more source metadata attributes that populate the source valuation nodes comprise one or more of: source data table definitions, source data view definitions, source data field definitions, and unstructured source data terms;

the one or more intermediate metadata attributes that populate the intermediate valuation nodes comprise one or more of: intermediate data table definitions, intermediate data view definitions, intermediate data field definitions, and unstructured intermediate data terms; and

the one or more end-user deliverable metadata attributes that populate the end-user valuation nodes comprise one or more of: end-user data table definitions, end-user data view definitions, end-user data field definitions, and unstructured end-user data terms.

16. A system comprising:

one or more processors operatively coupled to one or more memories configured to:

obtain at least one application data set stored in a data repository;

analyze the application data set to generate at least one source metadata node, at least one intermediate metadata node and at least one end-user metadata node, the application data set contains data generated by a plurality of application program types comprising: a source type, an intermediate type, and a destination type, wherein at least one source type application generates source data, at least one destination type application generates end-user deliverable data, and at least one intermediate type application generates intermediate data in between the source data and the end-user deliverable data;

analyze the source data to generate one or more source metadata attributes, the one or more source metadata attributes describing the source data;

perform computations on the source data to generate one or more intermediate metadata attributes, the one or more intermediate metadata attributes describing the intermediate data;

perform computations on at least one of the intermediate data and the source data to generate one or more end-user deliverable metadata attributes, the one or more end-user deliverable metadata attributes describing end-user deliverable data;

populate the at least one or more source metadata attributes into the at least one source metadata node the at least one or more intermediate metadata attributes into the at least one intermediate metadata node, and the one or more end-user deliverable attributes into the at least one metadata end-user node;

combine the at least one source metadata node, the at least one intermediate metadata node and the at least one end-user metadata node to form a hierarchical data structure, the hierarchical data structure comprising source valuation nodes, intermediate valuation nodes, and at least one end-user valuation node;

determine a data set value for at least a subset of the data set of the hierarchical data structure corresponding to an end-user node value for the at least one end-user valuation node;

traverse the hierarchical data structure from the at least one end valuation node to the intermediate valuation nodes and the source valuation nodes; and

assign node values to the intermediate level valuation nodes and to the source valuation nodes based on respective contributions to the at least one end-user valuation node.

17. The system of claim 16 , wherein a given source valuation node is assigned a value based at least in part on a number of the intermediate valuation nodes and the at least one end-user valuation node to which the given source valuation node contributes divided by the total number of intermediate valuation nodes and the at least one end-user valuation node.

18. The system of claim 16 , wherein:

the one or more source metadata attributes that populate the source level valuation nodes comprise one or more of: source data table definitions, source data view definitions, source data field definitions, and unstructured source data terms;

the one or more intermediate metadata attributes that populate the intermediate level valuation nodes comprise one or more of: intermediate data table definitions, intermediate data view definitions, intermediate data field definitions, and unstructured intermediate data terms; and

the one or more end-user deliverable metadata attributes that populate the end-user level valuation nodes comprise one or more of: end-user data table definitions, end-user data view definitions, end-user data field definitions, and unstructured end-user data terms.

19. The system of claim 16 , wherein a given one of an intermediate valuation node and a source valuation node is assigned a value equal to a product of a weight and the value of the at least one end-user valuation node that functions as a root node to the given one of the intermediate valuation node and the source valuation node.

20. The system of claim 16 , wherein the one or more end-user deliverable metadata attributes comprise business type metadata, and the one or more source metadata attributes and the one or more intermediate metadata attributes comprise technical type metadata.