Abstract: A metadata synchronization system is provided. The metadata synchronization system may include a plurality of metadata elements included in a plurality of applications. The plurality of applications may be coupled to a plurality of application hubs. The plurality of application hubs may be coupled to a federated metadata repository. The plurality of application hubs may be coupled to a governed metadata repository. The system may include crawling the plurality of applications, the plurality of application hubs, the federated metadata repository and the governed metadata repository to ensure that the metadata elements are synchronized across all of the components. In the event that a metadata element is not synchronized across any one of the components, the system may notify interested parties and/or resolve the discrepancy.

Abstract: A metadata synchronization system is provided. The metadata synchronization system may include a plurality of metadata elements included in a plurality of applications. The plurality of applications may be coupled to a plurality of application hubs. The plurality of application hubs may be coupled to a federated metadata repository. The plurality of application hubs may be coupled to a governed metadata repository. The system may include crawling the plurality of applications, the plurality of application hubs, the federated metadata repository and the governed metadata repository to ensure that the metadata elements are synchronized across all of the components. In the event that a metadata element is not synchronized across any one of the components, the system may notify interested parties and/or resolve the discrepancy.

Abstract: A metadata synchronization system is provided. The metadata synchronization system may include a plurality of metadata elements included in a plurality of applications. The plurality of applications may be coupled to a plurality of application hubs. The plurality of application hubs may be coupled to a federated metadata repository. The plurality of application hubs may be coupled to a governed metadata repository. The system may include crawling the plurality of applications, the plurality of application hubs, the federated metadata repository and the governed metadata repository to ensure that the metadata elements are synchronized across all of the components. In the event that a metadata element is not synchronized across any one of the components, the system may notify interested parties and/or resolve the discrepancy.

Abstract: A metadata synchronization system is provided. The metadata synchronization system may include a plurality of metadata elements included in a plurality of applications. The plurality of applications may be coupled to a plurality of application hubs. The plurality of application hubs may be coupled to a federated metadata repository. The plurality of application hubs may be coupled to a governed metadata repository. The system may include crawling the plurality of applications, the plurality of application hubs, the federated metadata repository and the governed metadata repository to ensure that the metadata elements are synchronized across all of the components. In the event that a metadata element is not synchronized across any one of the components, the system may notify interested parties and/or resolve the discrepancy.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.

Abstract: Resources for data lineage discovery, data lineage analysis, role-based security, notification. The resources may include or involve machine readable memory that is configured to store a technical data element (“TDE”); a receiver that is configured to receive a query for data lineage information corresponding to a business element identifier; and a processor configured to: register a logical association between the business element identifier and the TDE; and formulate the data lineage information of the TDE associated with the business element identifier. The receiver may be configured to receive a criterion that is required to access one or more technical data elements (“TDEs”) associated with the business element identifier. The receiver may be configured to receive an election to receive a notification of a change of data lineage. The processor may be configured to toggle between a first data lineage graph and a second data lineage graph.