# US 2017/0251056 A1 · Metadata synchronization system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0251056 A1
- Document ID: US20170251056A1
- Status: Published application
- Kind: A1
- Application number: 15/056,452
- Filed: 2016-02-29
- Published: 2017-08-31
- Earliest claimed: 2016-02-29
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Michelle A. Boston; Ilya Lapsker
- Web page: https://patentgrep.com/patent/US20170251056A1

## CPC

- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- G06F 16/24573: {using data annotations, e.g. user-defined metadata}
- G06F 16/275: {Synchronous replication}
- G06Q 10/10: Office automation; Time management
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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.

## Claims

### Claim 1

A system for synchronizing metadata across a plurality of applications, the system comprising:
the plurality of applications, wherein each application included in the plurality of applications is coupled to an application hub included in a plurality of application hubs, said each application comprising a plurality of metadata elements;
the application hubs, each application hub comprising a data elements baseline metadata, said data elements baseline metadata controlling the plurality of metadata elements associated with each application to which it is coupled;
a federated metadata repository coupled to each application hub, said federated metadata repository configured to receive, from the application hubs, the plurality of metadata elements from each application;
a governed metadata repository coupled to the federated metadata repository, the governed metadata repository configured to receive a subset of metadata elements from the federated metadata repository; and
a crawler configured to crawl the applications to ensure that:
each metadata element included in the pluralities of metadata elements is coupled to the federated metadata repository; and
each metadata element is up to date with a current set of metadata requirements.

### Claim 2 (depends on 1)

The system of claim 1, wherein the plurality of application hubs comprise at least one of:
an enterprise hub;
a customer hub;
a card hub;
a mortgage hub;
a global wealth and investment management hub;
a payments hub; and
a deposits hub.

### Claim 3 (depends on 1)

The system of claim 1, wherein the metadata elements included in the governed metadata repository are entity-critical metadata elements.

### Claim 4 (depends on 3)

The system of claim 3, wherein the metadata elements included in the governed metadata repository comprise greater detail with respect to the metadata elements included in the federated metadata repository.

### Claim 5 (depends on 1)

The system of claim 1, wherein upon identification, by the crawler, of a metadata element in an application, that is not up to date with the current set of metadata requirements, the crawler is configured to transmit a notification message to an owner of the application, the message comprising the metadata element and the current metadata element requirements.

### Claim 6 (depends on 1)

The system of claim 1, wherein the crawler may be further configured to crawl the plurality of applications to identify a new metadata element in an application that is not coupled to the federated metadata repository.

### Claim 7 (depends on 6)

The system of claim 6, wherein:
in response to identification that the new metadata element is not coupled to the federated metadata repository, the crawler is configured to transmit a notification message to persons associated with the owner of the application, the message comprising the new metadata element and the current metadata element requirements; and
in response to the transmission of a notification message to persons associated with the owner of the application, the system is configured to insert the new metadata element into the federated metadata repository according to the current metadata element requirements.

### Claim 8 (depends on 1)

The system of claim 1, wherein:
the crawler is further configured to crawl the plurality of applications to identify an out-of-date metadata element in an application that is coupled to the federated metadata repository;
in response to identification that the out-of-date metadata element is coupled to the federated metadata repository, the crawler is configured to transmit a notification message to persons associated with the owner of the application, the message comprising the out-of-date metadata element and the current metadata element requirements; and
in response to the transmission of a notification message to persons associated with the owner of the application, the system is configured to update the out-of-date metadata element in the federated metadata repository.

### Claim 9 (depends on 1)

The system of claim 1, wherein:
the crawler is further configured to crawl the plurality of applications to identify an extinct metadata element in an application that is coupled to the federated metadata repository;
in response to identification that the extinct metadata element is coupled to the federated metadata repository, the crawler is configured to transmit a notification message to persons associated with the owner of the application, the message comprising the extinct metadata element and the current metadata element requirements; and
in response to the transmission of a notification message to persons associated with the owner of the application, the system is configured to remove the metadata element from the federated metadata repository.

### Claim 10 (depends on 7)

The system of claim 7, wherein, the system is further configured to enable a user, via a user interface, to make changes to the metadata element.

### Claim 11

A system for synchronizing metadata across a plurality of applications, the system comprising:
the plurality of applications, wherein each application included in the plurality of applications is coupled to an application hub included in a plurality of application hubs, each of said applications comprising a plurality of metadata elements, each application hub comprising data elements baseline metadata, said data elements baseline metadata controlling the plurality of metadata elements associated with each application to which it is coupled;
a federated metadata repository, the federated metadata repository coupled to each application hub, the federated metadata repository configured to receive the pluralities of metadata elements;
a governed metadata repository, the governed metadata repository coupled to the federated metadata repository, the governed metadata repository configured to receive a subset of the pluralities of metadata elements;
a technical discrepancy processor coupled to the federated metadata repository and the governed metadata repository, the technical discrepancy processor configured to determine technical discrepancies between metadata elements stored in the federated metadata repository and the governed metadata repository;
a technical notification processor coupled to the technical discrepancy processor, the technical notification processor configured to transmit a technical notification message to an execution team, the technical notification message comprising the determined technical discrepancies;
a business discrepancy processor coupled to the federated metadata repository and the governed metadata repository, the business discrepancy processor configured to determine business discrepancies between metadata elements stored in the federated metadata repository and the governed metadata repository; and
a business notification processor coupled to the business discrepancy processor, the business notification processor configured to transmit a business notification message to the execution team, the business notification message being triggered by a determination of the business discrepancies.

### Claim 12 (depends on 11)

The system of claim 11, wherein the federated metadata repository is coupled to each application hub via a landing zone and a loading process.

### Claim 13 (depends on 11)

The system of claim 11, further comprising a crawler, wherein the crawler is configured to ensure that:
each metadata element included in the pluralities of metadata elements is coupled to the federated metadata repository; and
each metadata element satisfies a current set of metadata requirements.

### Claim 14 (depends on 13)

The system of claim 13, wherein upon identification, by the crawler, of a metadata element in an application, that does not satisfy the current set of metadata requirements, the crawler is configured to transmit a notification message to an owner of the application, the message comprising the metadata element and the current metadata element requirements.

### Claim 15 (depends on 14)

The system of claim 14, wherein, in response to an identification of a metadata element by the crawler, said metadata element that is not coupled to the federated metadata repository, the crawler is configured to transmit a notification message to persons associated with the owner of the application, the message comprising the metadata element and the current metadata element requirements.

### Claim 16 (depends on 14)

The system of claim 14, wherein the crawler may be further configured to crawl the plurality of applications to identify a metadata element in an application that is not coupled to the federated metadata repository.

### Claim 17 (depends on 11)

The system of claim 11, wherein the metadata elements included in the governed metadata repository are entity-critical metadata elements.

### Claim 18 (depends on 11)

The system of claim 11, wherein the metadata elements included in the governed metadata repository comprise a greater magnitude of fields than the metadata elements included in the federated metadata repository.

### Claim 19

A method for metadata synchronization comprising:
receiving, at a federated metadata repository, a plurality of metadata elements, said plurality of metadata element being transmitted from a plurality of applications, said plurality of applications being coupled to a plurality of application hubs;
receiving, at a governed metadata repository, a subset of the plurality of metadata elements;
crawling, via a crawler, the plurality of applications, to determine that each metadata element included in the plurality of metadata elements has been received at the federated metadata repository;
transmitting a first notification message to a first user in the event that a metadata element is not received at the federated metadata repository;
crawling, via the crawler, the federated metadata repository and the governed metadata repository to determine whether each metadata element that is included in both of the federated metadata repository and the governed metadata repository are identified using the same data type;
upon identification of a metadata element which is identified using one data type in the federated metadata repository and another data type in the governed metadata repository, conforming, via a processor, the data type of identified metadata element included in the federated metadata repository and the data type of the identified metadata element included in the governed metadata repository.

### Claim 20 (depends on 19)

The method of claim 19, further comprising:
transmitting a second notification message to a second user upon completion of the conforming;
crawling, via the crawler, the federated metadata repository and the governed metadata repository to determine which metadata elements, included in the plurality of metadata elements should be assigned a governed status;
notifying the user which metadata elements were determined to be governed metadata elements.

### Claim 21 (depends on 20)

The method of claim 20, wherein the first user is an application owner associated with the metadata element that has not been received at the federated metadata repository.

### Claim 22 (depends on 21)

The method of claim 21, further comprising crawling, via the crawler, the plurality of applications, to ensure that a data type associated with each of the metadata elements, included in the plurality of metadata elements, is the same in the federated metadata repository, the governed metadata repository and the plurality of applications.

### Claim 23 (depends on 22)

The method of claim 22, further comprising upon determination by the crawler that at least one data element is not the same data type in the federated metadata repository, governed metadata repository and the plurality of applications, transmitting a third notification message to a third user, the third notification message comprising the discrepancy.

### Claim 24 (depends on 23)

The method of claim 23, wherein, upon determination by the crawler that at least one data element is not the same data type in the federated metadata repository, the governed metadata repository and the plurality of applications, transmitting a third notification message to the first user and the second user, the third notification message comprising the discrepancy.
