KR20140011535A

KR20140011535A - Metadata management system

Info

Publication number: KR20140011535A
Application number: KR1020120071402A
Authority: KR
Inventors: 정장환
Original assignee: 중소기업은행
Priority date: 2012-06-29
Filing date: 2012-06-29
Publication date: 2014-01-29

Abstract

The present invention relates to an automatic metadata management system, which is capable of automatically managing new code or metadata change of a new banking project. To this end, the automatic metadata management system is a central metadata management unit that standardizes all metadata managed by all bank branches, manages them with standard codes, and updates them at a predetermined time unit in the storage medium EDW (Enterprise Data Warehouse). It provides an interworking interface for implementing a request reception interface, a development progress interface, and a banking project completion result for each of the necessary banking projects to the central metadata management unit, and metadata generated from the banking project completion result. Includes; a new system management unit for storing the new code.

Description

Automatic Metadata Management System

The present invention relates to a method for automating metadata management. More specifically, the present invention relates to a method for automating the metadata management process of the new system management unit to match the metadata with the central metadata management unit.

A new system management department that manages projects of new systems such as retirement pension system, securities trust system, IB system, G-CRM system, etc., is newly created during project development, or changes to new systems such as tables, terms, codes, etc. In the case of using metadata differently on its own, it was difficult to verify whether the metadata matched the central metadata management unit.

In addition, there is a problem that the case of inconsistency with the central metadata management unit and the metadata increases as the case where the new system management unit omits the procedure of registering new metadata generated when developing or operating a new system.

In the present invention, all metadata managed by all banks are standardized to solve problems due to inconsistencies in user business activities of the headquarters department and the IT department.

In order to solve the above problems, the automatic metadata management system standardizes all metadata managed by all bank branches, manages them with standard codes, and updates them by a predetermined time unit in the storage medium EDW (Enterprise Data Warehouse). And provide an interworking interface for implementing a request reception interface, a development progress interface, and a banking project completion result for the banking project projects that need to be developed to the central metadata management unit, and in the banking project completion result. And a new system manager for storing a new code, which is generated metadata, wherein the new system manager sends a change request message indicating that the standard code needs to be changed to the central metadata manager through the interworking interface. Central Metade The management unit updates the modified standard code in the EDW upon receiving the change request message, and the central metadata management unit verifies that the new code stored in the new system management unit is identical to the standard code and, if there is a mismatch, the new standard code. Send a notification message to the system manager.

By linking the changed metadata information to the central metadata management unit automatically in each new system and comparing the standard code and the new code for each period, it is possible to automatically prevent the metadata code values from being inconsistent and improve the data quality. Can be.

In addition, by automating the process of verifying whether metadata values match, metadata management systems users can accurately view and utilize metadata information.

1 illustrates a conceptual diagram of an automatic metadata management system as a preferred embodiment of the present invention.
2 illustrates an example of receiving a change request message from the central metadata management unit according to an embodiment of the present invention.
3 shows an example of a new system management unit as an embodiment of the present invention.
Figure 4 is an embodiment of the present invention, shows an example of metadata change in the new system management unit.
5 is a diagram illustrating the internal configuration of an automatic metadata management system according to a preferred embodiment of the present invention.
6 is a flowchart illustrating a management of an automatic metadata management system according to an embodiment of the present invention.
7 to 9 illustrate a process of requesting standardization from the new system management unit to the central metadata management unit according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that the same components of the drawings are denoted by the same reference numerals and signs as possible even if they are shown on different drawings. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

1 illustrates a conceptual diagram of an automatic metadata management system as a preferred embodiment of the present invention.

Automatic metadata management system includes a new system management unit 110 and the central metadata management unit 120.

The new system manager 110 manages a code table for managing metadata of the new system. Examples of new systems are retirement pension systems, securities trust systems, IB systems, and G-CRM systems.

In addition, the new system management unit 110 may be implemented to receive a business development request of banking projects that require development, or to manage all processes until development and termination. To this end, as disclosed in FIG. 5, the new system management unit 110 may be implemented to provide an interworking interface for implementing an interworking of a request reception interface, a development progress interface, and a banking project completion result.

The central metadata management unit 120 standardizes all metadata managed by all bank branches and manages them with standard codes.

The central metadata management unit 120 receives a change request message through an interworking interface supported by the new system management unit 110 when a new code, which is new metadata, is generated in the new system management unit 110. The new code and the changed metadata can be standardized and updated. For this, see FIGS. 7 to 9.

The new system management unit 110 transmits a change request message indicating that the standard code needs to be changed to the central metadata management unit 120 through the interworking interface, and the central metadata management unit 120 receives the change request message to the storage medium. Update the changed standard code to the EDW (Enterprise Data Warehouse, 130). EDW may be integrally implemented in the central metadata management unit 120 or may be implemented as a separate device or equipment.

The central metadata management unit 120 does not receive the change request message from the new system management unit 110, or the new code and the central code stored in the code table of the new system management unit on a specific period basis even after the standardization procedure of the changed new code is already completed. Verification can be performed for matching metadata standard codes.

Specifically, the EDW 130 registers the SQL in the job scheduler in the EDW 130 according to the setting of the administrator for a predetermined period of time or accesses the database of the new system management unit 110 and stores the standard code and the new system management unit 110. Check that the metadata stored in the code table matches. If the check result is inconsistent, the EDW 130 may transmit a notification message informing the new system manager 110 that the metadata stored in the code table does not match the standard code.

In one preferred embodiment of the present invention, an example of inconsistency between the metadata stored in the code table and the standard code is as follows. In the code table of the new system management unit 110, when the door code is set to "001 sales department", "002 Dongdaemun", .... "549 Jamsil Triumium Branch", Munrae Hi-Tech Branch is added to the code table. An additional point code called "550 Munrae Hi-Tech Branch" is required.

In another preferred embodiment of the present invention, an example of inconsistency between the standard code stored in the central metadata management unit 120 or the EDW 130 and the metadata stored in the code table of the new system management unit 110 is as follows. .

Standard codes are set to "001 individual", "002 company", "003 private business", etc., but in the retirement pension system of the new system management unit 110, "001 individual", "002 small business", "003 large company" New code is available.

When the change or inconsistency of the metadata occurs as described above, the new system management unit 110 requests the change to the central metadata management unit 120 to perform standardization or the EDW 130 according to the setting of the manager for a predetermined period or a new manager. Standardization is performed by checking whether the metadata in the code table of the system manager 110 matches the standard code.

2 illustrates an example of receiving a change request message from the central metadata management unit according to an embodiment of the present invention.

The central metadata management unit (FIGS. 1 and 120) may receive a change message due to generation of a new code or change of existing metadata from the new system management unit (FIGS. 1 and 110). For example, referring to FIG. 2, the central metadata management unit provides an interface for checking the change request status 210 or 220 of the new system management unit.

For example, the change request message may be a message for adding a column to the table to change the personal member (TBCB03), personal receipt (TBC19), and personal card (TBC93) tables for the CB_personal card additional information.

Figure 3 is an embodiment of the present invention, shows an example of the development progress interface of the new system management unit.

The new system management unit (FIGS. 1 and 110) may support a development progress interface 310 such as a project plan start date, performance start date, plan end date, performance end date, progress rate, and weight for each project.

Figure 4 is an embodiment of the present invention, shows an example of metadata change in the new system management unit.

The new system management department manages all processes from receiving development requests for development of banking projects that need development, to development and termination. In this case, new metadata, which is new metadata, may be generated or existing metadata may be changed in the project completion result.

For example, in the e-voucher system project, which is an example of a new banking project, the new code shown in FIG. 4 may be generated. According to an exemplary embodiment of the present invention, the newly generated new code or the change of metadata may be managed in the form of the table definition 400.

The table definition 400 may include information such as a column name 410, a type 411, a length 412, a NULL 413, and a KEY 414. In the table definition 400, when a result of performing an e-voucher system project, for example, a voucher code is added or metadata for managing a settlement year date is changed, it may be added or changed as shown.

The metadata information or new code added or changed as described above may be newly standardized by the metadata management unit by transmitting a change request message to the metadata management unit through the interworking interface in the project management unit.

FIG. 6 is a flowchart of automatically reflecting changes in an automatic metadata management system according to an embodiment of the present invention.

As a result of completing the banking project in the new system management unit of the automatic metadata management system, metadata is changed or a new code is generated (S610).

The new system manager transmits a change request message to the metadata manager to reflect the above change or newly generated metadata (S620). When the metadata management unit receives the change request message, the metadata management unit generates a payment request window and registers the project completion result in the payment request window through the interworking interface (S640). In this case, the project completion result registered includes project manager information and may include the entire result, but it may be implemented in a manner that includes only new new code or changed metadata information. The metadata management unit processes the payment request window and standardizes the data generated in the new project (S650).

Thereafter, although not shown in the drawing, the EDW (FIGS. 1 and 130) registers the SQL to the job scheduler in the EDW (FIGS. 1 and 130) according to a setting of a certain period or an administrator, thereby creating a database of the new system management unit (FIGS. 1 and 110). The method may further include checking whether the stored standard code and metadata stored in the code table of the new system manager 110 match with each other.

In addition, if there is a discrepancy in the verification result, the EDW may transmit a notification message informing the new system manager that the metadata stored in the code table is inconsistent with the standard code.

7 to 9 illustrate a process of requesting standardization to the central metadata management unit 120 when a new code is generated by the new system management unit 110.

The central metadata management unit 120 receives a change request message through an interworking interface supported by the new system management unit 110 when a new code, which is new metadata, is generated in the new system management unit 110. In operation 120, a payment request window 700 for requesting standardization of a new code as shown in FIG. 7 is generated.

The central metadata management unit 120 manages the project managed by the new system management unit 110 as shown in FIG. 8 for registering a corresponding banking project completion result generated by generating a new code requiring standardization in the payment request window 700. An interworking interface that supports lists can be used.

The project list 800 may be sorted or categorized by a predetermined period and may be searched by a project name. You can also add subprojects belonging to each project and the person in charge of the subproject.

The central metadata management unit 120 registers the corresponding banking project completion result of generating a new code in the payment request window 700 as shown in FIG. 9 (900) and requests standardization settlement and performs standardization processing.

The present invention can also be embodied as computer-readable codes on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored.

Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like. The computer readable recording medium may also be distributed over a networked computer system so that computer readable code can be stored and executed in a distributed manner.

In the drawings and specification, there have been disclosed preferred embodiments. Although specific terms have been employed herein, they are used for purposes of illustration only and are not intended to limit the scope of the invention as defined in the claims or the claims.

Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

Claims

Central metadata management unit that standardizes all metadata managed by all bank branches, manages them with standard codes, and updates them at predetermined time units in the storage medium EDW; and
It provides an interworking interface for implementing a request reception interface, a development progress interface, and a banking project completion result to the central metadata management unit for each banking project that needs to be developed, and generated from the banking project completion result. New system management unit for storing the new code which is metadata;
The new system manager transmits a change request message indicating that the standard code needs to be changed to the central metadata management unit through the interworking interface, and the central metadata management unit changes the standard to the EDW upon receiving the change request message. Update the code,
The central metadata management unit verifies that the new code stored in the new system management unit and the standard code match, and transmits a notification message to the new system management unit if there is a mismatch.