CN113918576B

CN113918576B - Metadata management platform and management method

Info

Publication number: CN113918576B
Application number: CN202111515234.6A
Authority: CN
Inventors: 王亚飞
Original assignee: Beijing Yusys Technologies Group Co ltd
Current assignee: Beijing Yusys Technologies Group Co ltd
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2022-03-22
Anticipated expiration: 2041-12-13
Also published as: CN113918576A

Abstract

The invention provides a metadata management platform and a management method, wherein the platform comprises: the data source processing module responds to a newly added instruction of the newly added data source and adds the data source for the project system; the subsystem configuration module is used for responding to the received subsystem configuration instruction and editing the configuration information of the selected subsystem; the domain creating module is used for creating the service domain for the selected subsystem in response to receiving the instruction for creating the service domain; the field management module is used for managing at least one of the data type, the field type and the standard field in response to receiving the field management instruction; the table operation module is used for responding to the received table operation instruction and operating a plurality of attributes of the table belonging to each service field; and the interface editing module is used for editing the interface attribute in response to the received interface editing instruction. Metadata management required by IT system construction can be completed through page configuration, so that software development efficiency, specification and safety are realized.

Description

Metadata management platform and management method

Technical Field

The invention relates to the technical field of software development in the financial industry, in particular to a metadata management platform and a metadata management method.

Background

Metadata management is the process of managing an organization's data assets. The visual user experience is utilized to realize the maintenance functions of adding, deleting, modifying, releasing and the like of the metadata; and the user can intuitively know the classification, statistics, use condition, change tracing and life cycle management of each metadata. By managing metadata, the creation of data assets within multiple systems can be quickly discovered.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: the existing metadata management platform and method cannot effectively guarantee the construction efficiency of the IT system.

Disclosure of Invention

In view of this, embodiments of the present invention provide a metadata management platform and a metadata management method, which provide data asset management for an IT department and ensure the efficiency, specification and safety of IT system construction.

To achieve the above object, in a first aspect, an embodiment of the present invention provides a metadata management platform, which includes:

the data source processing module is used for responding to a received new instruction for adding a data source, adding the data source for the project system and setting data source information corresponding to the added data source; wherein the data source corresponds to one or more subsystems under the project system;

the subsystem configuration module is used for responding to the received subsystem configuration instruction and editing the configuration information of the selected subsystem;

the domain creating module is used for creating one or more service domains for the selected subsystem in response to receiving an instruction for creating the service domains;

the field management module is used for responding to the received field management instruction and managing at least one of the data type, the field type and the standard field;

the table operation module is used for responding to the received table operation instruction and operating a plurality of attributes of one or more tables under the service field;

and the interface editing module is used for responding to the received interface editing instruction and editing the attribute of the interface belonging to the service field.

In a second aspect, an embodiment of the present invention provides a metadata management method, including:

responding to a received new adding instruction for adding a data source, adding the data source for the project system, and setting data source information corresponding to the added data source; wherein the data source corresponds to one or more subsystems under the project system;

in response to receiving a subsystem configuration instruction, editing the configuration information of the selected subsystem;

in response to receiving an instruction to create a business domain, creating one or more business domains for the selected subsystem;

managing at least one of a data type, a field type, and a standard field in response to receiving the field management instruction;

in response to receiving a table operation instruction, operating a plurality of attributes of one or more tables belonging to each business field;

and responding to the received interface editing instruction, and editing the attribute of the interface belonging to the service field.

In a third aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the metadata management method as described above.

In a fourth aspect, a computer device is provided, comprising:

one or more processors;

storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the metadata management method as described above.

The technical scheme has the following beneficial effects:

metadata management required by IT system construction can be completed through page configuration, so that software development efficiency, specification and safety are guaranteed. And interface definition is completed in the design stage to improve development efficiency.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a functional block diagram of a metadata management platform of an embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating the effect of a data source management page according to an embodiment of the present invention;

FIG. 3 is a diagram illustrating the effect of a subsystem management page according to an embodiment of the present invention;

FIG. 4A is a first diagram illustrating an effect of a domain management page according to an embodiment of the present invention;

FIG. 4B is a diagram illustrating an effect of a domain management page according to an embodiment of the present invention;

FIG. 4C is a third diagram illustrating an effect of a domain management page according to an embodiment of the present invention;

FIG. 5A is a diagram illustrating the effect of a data type management page according to an embodiment of the present invention;

FIG. 5B is a diagram illustrating the effect of a field type management interface according to an embodiment of the present invention;

FIG. 5C is a diagram illustrating the effects of a standard field management interface according to an embodiment of the present invention;

FIG. 6A is a diagram illustrating the effect of table management function according to an embodiment of the present invention;

FIG. 6B is a diagram illustrating standard field editing effects of a table according to an embodiment of the invention;

FIG. 7 is a schematic illustration of the resulting data asset management effect of an embodiment of the present invention;

FIG. 8A is a diagram illustrating the effect of editing properties of an interface object according to an embodiment of the present invention;

FIG. 8B is a diagram of an editing interface for interface object fields, in accordance with an embodiment of the present invention;

FIG. 8C is a schematic view of an attribute management page of an interface according to an embodiment of the present invention;

FIG. 8D is a diagram illustrating an interface parameter management interface according to an embodiment of the invention;

fig. 8E is an interface diagram illustrating a parameter type of a standard field when selecting parameters of a newly added interface according to an embodiment of the present invention;

fig. 8F is an interface diagram illustrating the selection of a parameter type as an interface object when adding interface parameters according to the embodiment of the present invention;

FIG. 8G is a mental diagram of interface management of an embodiment of the present invention;

FIG. 9 is a diagram illustrating tables and interfaces assigned to different business domains according to an embodiment of the present invention;

FIG. 10 is a flow chart of a method of metadata management in accordance with an embodiment of the present invention;

FIG. 11 is a functional block diagram of a computer-readable storage medium of an embodiment of the present invention;

fig. 12 is a functional block diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Metadata management enhances consistency and eliminates redundancy by discovering reuse data, thereby improving work efficiency and reducing project lead time.

The metadata repository can be treated as a "single data source" to discover reusable components that developers can leverage. Companies may reduce the number of redundant or unused standard fields, allowing hardware and software integration and cost savings. The risk of knowledge loss due to personnel movement is reduced. If all software API functions are left in the mind of some employees, this knowledge disappears with the key employees when they leave the company. The metadata repository within the metadata management system maintains knowledge of this aspect, thereby mitigating any risk of such information disappearing with the out-of-office employee.

The integration and visibility of metadata can help the IT department know which data is present, the data storage location, and ITs meaning, minimizing the complexity of the information. In addition, this visibility provides a foundation for analyzing the impact of changes by constantly changing business requirements. Data integration developers can rely on this information to easily and accurately determine the data needed for their data integration projects, and the ability to access the effects of potential changes can also help managers quickly assess project implementation time and resource costs.

At least one object of the embodiments of the present invention is to provide a data asset management system for an IT department, which ensures the efficiency, specification and safety of the construction of the IT system.

Example one

FIG. 1 is a functional block diagram of a metadata management platform of an embodiment of the present invention. As shown in fig. 1, a platform 100 according to an embodiment of the present invention mainly includes: a data source processing module 110, a subsystem configuration module 120, a domain creation module 130, a field management module 140, a table operation module 150, and an interface editing module 160.

The data source processing module 110 is configured to, in response to receiving a new instruction for adding a new data source, add the new data source to the project system, and set data source information corresponding to the new data source; wherein the data source corresponds to one or more subsystems under the project system; thereby providing a respective data source to each subsystem under the project system;

the subsystem configuration module 120 is configured to, in response to receiving the subsystem configuration instruction, edit the configuration information of the selected subsystem; the configuration information for each subsystem includes: the name of the data source corresponding to the subsystem, the English name of the subsystem and the Chinese name of the subsystem;

a domain creation module 130, configured to create one or more service domains for the selected subsystem in response to receiving an instruction to create a service domain; the configuration information of each service domain includes: a domain identifier and a domain description;

a field management module 140 for managing at least one of a data type, a field type, and a standard field in response to receiving a field management instruction;

a table operation module 150, configured to, in response to receiving a table operation instruction, operate on a plurality of attributes of one or more tables belonging to a selected or corresponding service domain;

and the interface editing module 160 is configured to edit an attribute of an interface belonging to the service field in response to receiving the interface editing instruction.

Metadata management required by IT system construction can be completed through page configuration, so that software development efficiency, specification and safety are realized.

In a further embodiment, the data source processing module 110 specifically includes:

the data source newly-added module is used for responding to a newly-added instruction received by user operation and configuring at least one data source information of the project system, wherein the data source information comprises: the unique ID, the name of a database instance, the tablespace of the database, the index space of the database, the user name for accessing the database, the password for accessing the database and the database address; the unique ID is a main key of the data source information, the table space of the database is a file position of the data stored in the database, the index space of the database is a file position of the index stored in the database, and the name of the database instance is a schema name. The management of the database table space and the database index space can improve the expansion capability of the metadata platform, and the advantages of the management method specifically include: (1) generating a table building statement is facilitated: in the table building statement of the embodiment, a table space and an index space are necessary, and if not, the generated database table building statement cannot be executed. (2) The basic information management of the system is facilitated: before the software system is built, the basic information of a database depended on by software needs to be registered, and the information of the database table space and the index space needs to be included.

In a further embodiment, the data source processing module 110 may further include: the data source deleting submodule is used for responding to a received deleting instruction for deleting the data source and deleting the data source information corresponding to the deleting instruction; and/or the data source modification submodule is used for responding to a received modification instruction for modifying the data source and modifying the data source information corresponding to the modification instruction.

In a further embodiment, the field management module 140 specifically includes:

a data type management submodule, configured to, in response to receiving an instruction of a unified data type, perform at least one of: unifying a plurality of field types of a plurality of databases related to the character String into a development-state data type related to the character String, such as String; unifying multiple Integer-related field types of multiple databases into an Integer-related development-state data type, such as Integer; unifying various field types related to the decimal of various databases into a data type related to the decimal, such as BigDecimal; unifying a plurality of field types related to texts of a plurality of databases into a development-state data type related to the texts, such as Text; the various date-related field types of the various databases are consolidated into a development-state data type, such as LocalDateTime, that is date-related. The advantages are that: the data type of the development state is the type in the development language used by the programmer during development; the program needs to access various databases, different databases have different data types, and the embodiment of the invention performs unified registration by corresponding the different databases to a certain data type in a development state, so that a metadata platform is compatible with various types of databases.

In a further embodiment, the field management module 140 may further include:

the field type management submodule is used for responding to the received field type configuration instruction and configuring the field length attribute and/or the field precision attribute corresponding to each field type; a standard field management submodule, configured to manage, in response to receiving a standard field configuration instruction, a plurality of attributes of a standard field, where the plurality of attributes of the standard field include: field names, field descriptions, field types, and data dictionaries.

In a further embodiment, the table operation module 150 specifically includes:

the first table attribute operation submodule is used for responding to a received table attribute operation instruction and configuring a plurality of attributes including a table name, a table function description and a table attached subsystem identifier of a table on the basis of a table management operation page;

and the second table attribute operation submodule is used for responding to the click operation of a user on a table field button on the table field management operation page, popping up a table field attribute management page, managing the page based on table field information, and receiving the configuration information corresponding to a plurality of standard fields contained in the table by the user.

In a further embodiment, the table operation module 150 may further include: and the third table attribute operation submodule is used for responding to the clicking operation of a user on a table constraint button on the table management operation page, popping up a table constraint attribute management page, responding to an operation instruction received by the table constraint information management page, and newly adding a constraint prompt condition of the table.

In a further embodiment, the interface editing module 160 specifically includes:

the interface overall attribute editing submodule is used for:

in response to receiving the command of the new interface, generating an editing page of the attribute of the interface, wherein the attribute of the interface comprises: interface name, interface function, interface type, application program interface API, and interface parameters;

receiving configuration information of a user on an interface name, an interface function, an interface type and an API (application program interface) based on an editing page of the attribute of the interface;

and responding to the interface parameter editing instruction, generating an interface parameter editing page, and receiving the configuration information of the user on the interface parameters based on the interface parameter editing page.

In some embodiments, the interface general property editing sub-module may be specifically configured to:

responding to the click operation of a user on a newly added interface parameter button on the interface parameter editing page, and generating a configuration page for newly added interface parameters; the configuration page comprises a plurality of configuration items as follows: parameter name configuration items, parameter type configuration items, field ID configuration items or object class name configuration items and parameter label configuration items; the parameter tag configuration item is used for configuring the newly added interface parameters into input parameters or output parameters; in a further embodiment, the configuration page further comprises the following configuration items: parameter sequence configuration items and configuration items whether belong to the array or not; the parameter sequence configuration item is used for configuring the display sequence of the interface parameters, such as the display sequence on an interface parameter editing page; whether the configuration item belongs to the array is used for identifying whether the interface parameter belongs to the set type;

and responding to the editing operation of the user on the plurality of configuration items on the configuration page of the newly added interface parameters, generating corresponding interface parameters, and displaying the configuration information of the generated interface parameters on the interface parameter editing page.

In a further embodiment, the interface editing module 160 further includes: the interface object editing submodule is used for editing the attribute of the interface object in response to the received attribute editing instruction of the interface object; the attributes of the interface object include: class name, interface description, and standard fields contained in the interface object. An interface object is an attribute of an interface. Since the configuration of the interface object is complex, the present embodiment is configured specifically for the other independent page. Therefore, when the interface is edited, the configured interface object can be selected.

The above technical solution is described in more detail as follows:

the data source processing module:

FIG. 2 is a schematic diagram illustrating the effect of managing pages by a data source according to an embodiment of the present invention. As shown in fig. 2, the data resources managed by the metadata are finally implemented in the database of the project (system), and the data source processing module is used for managing the database information of the project, and includes: database address, user name, password, tablespace (the location of the file where the database stores the data), index space (the location of the file where the database stores the index), schema name (the name of the database instance), unique ID, and the like. The database can be subjected to table structure creation through managed database information. The unique ID is a main key of the piece of data, and data management is facilitated. THIN and ORCl in the database url are standard formats for the database url.

A subsystem configuration module:

fig. 3 is a schematic diagram illustrating an effect of a subsystem management page according to an embodiment of the present invention. As shown in fig. 3, the system construction of IT is divided into different subsystems, each of which requires ITs own data source (provided by the data source processing module), and the management of the subsystem is used to determine the configuration information of the subsystem, which includes: besides the name or the identification of the data source corresponding to the subsystem, the English name of the subsystem and the Chinese name of the subsystem. The ID is the main key of the piece of data, and data management is facilitated. For example, the ID is data of SYS-1622890828773, the english name of a subsystem is RISK, the corresponding chinese name of the subsystem is a wind control system, and the corresponding data source of the subsystem is plus; the ID is data of SYS-1622961837730, the English name CASH of a subsystem, the corresponding Chinese name of the subsystem is a capital system, and the corresponding data source of the subsystem is plus; the ID is data of SYS-1622890846878, the English name COLL of a subsystem, the corresponding Chinese name of the subsystem is an escort system, and the corresponding data source of the subsystem is plus; the ID is data of SYS-1622961851923, the English name BOND of a subsystem, the Chinese name of the corresponding subsystem is a bookkeeping system, and the data source corresponding to the subsystem is plus; the ID is data of SYS-1622990432250, English name of subsystem FRONT, corresponding Chinese name of the subsystem is FRONT system, and data source corresponding to the subsystem is plus. The rightmost side of the operation interface is provided with an operation field, a deletion button and a modification button are configured for each piece of data, the deletion operation can be carried out on the piece of data in response to receiving a deletion instruction, or the modification operation can be carried out on a plurality of fields of the piece of data in response to receiving a modification instruction. The modified data can be modified and returned to be successful, and after the current page receives the successful modification, the page is refreshed to display new modified data. Further, a conditional search control may be further provided on the edit page, and is configured to search and determine the subsystem configuration information corresponding to the keyword based on the keyword input by the user and related to the english name of the subsystem.

A domain creation module:

FIG. 4A is a first diagram illustrating an effect of a domain management page according to an embodiment of the present invention; fig. 4B is a schematic diagram illustrating an effect of the domain management page according to the embodiment of the present invention. As shown in fig. 4A, there are many service domains in a subsystem, and one or more service domains can be created under the subsystem. In one example, the wind control subsystem includes: the method comprises two service fields of wind control rule management and user information management. In another example, an OA office management system is a subsystem that includes two business areas, employee reimbursement and employee leave. In other examples, some subsystems may not have a business domain, for example, the subsystems are planned, but the development time is very tight and the business domain may not be set. As shown in fig. 4B, each business domain mainly includes a domain ID (unique identification), a domain description. The domain description may be understood as a category where data of the same class is placed under a domain description (name). The father ID indicates that the home service field is mounted below the father ID, namely, the edited data is a child node of the resource corresponding to the father ID. See, for example, fig. 4C: for example, in the menu of OA office management system, there is system management business field, which expands the next level sub business fields of user management and leave management; the user management is a sub-service field under the service field of the system management, and when the user management is newly added, the father ID of the user management is the ID of the system management.

A field management module:

the field is the smallest unit in the data asset and the interface definition table defines the dependency standard field. The field management module comprises the following sub-modules: data type management, field type management, standard field management.

Data type management: the field types of various databases are uniformly summarized into the data type of a development state (in the state of program development), and the method has the advantages that: one development type is used, the storage types of the multiple types of databases can be matched through configuration, and development modes are unified.

Each database is of its own stored data type, for example, oracle database String is Varchar2, mysql database String is Varchar, but the program is of a String type during development, so that the same types of different types of databases can be generalized into a unified development-state data type only by one development data type, for example, String data type.

Fig. 5A is a schematic diagram illustrating an effect of the data type management page according to the embodiment of the present invention. As shown in fig. 5A, for example: the oracle database string is Varchar 2; the mysql database string is Varchar; both need only be represented by String at the time of development. FIG. 5A shows the effect of Varchar2 from oracle and Varchar from mysql unifying into the String data type as developed. The program development has its own development language, and different data types can be defined in the development language to correspond to actual business attributes. The database is used for storing data of the service attributes, and different data types can be defined by the database to correspond to the actual service attributes. As an example the following:

the producing area of the watermelon: xinjiang, it is a word, the development language corresponds to String type, and the mysql database corresponds to VARCHAR type.

Price of watermelon: 23, it is a numerical value, corresponding to the Integer type in the development language, and the INTEGER type in the mysql database.

Weight of watermelon (KG): 11.5, it is a number with decimal point, the developing language is correspondent to the BigDecimal type, the mysql database is correspondent to the DOUBLE type.

Product description of watermelon: someone plants Turpan, which is a relatively long string, corresponding to a Text type in the development language and a TEXT type in the mysql database.

Production date of watermelon: 2021/08/07, which is a date in the development language corresponding to the LocalDateTime type and mysql database corresponding to the DATETIME type.

And field type management:

fig. 5B is a schematic diagram of an effect of a field type management interface according to an embodiment of the present invention. And field type management: the attributes of the data types are mainly supplemented, and include field lengths and/or field precisions, for example, the String data types have different length attributes, and the field types varchar32, varchar50 and the like are derived.

And (3) standard field management:

fig. 5C is a diagram illustrating an effect of the standard field management interface according to the embodiment of the present invention. And (3) standard field management: the field type is an attribute of the standard field, and the standard field can be added with the field type. The main attributes of standard field management include: field name, field description, field type, data dictionary.

Table management:

fig. 6A is a schematic diagram illustrating an effect of the table management function according to the embodiment of the present invention. As shown in fig. 6A, the table is mainly composed of standard fields, and table information can be managed by using the standard fields. The main attributes of table management are: table name, table function description, system ID, table field, table constraint. Wherein, clicking the table field button where the row is located can pop up table field information; table constraints are some constraint hints added to the table, such as: primary key uniqueness constraints, and the like. The table field and table constraint are attributes belonging to the table, the table field is composed of a plurality of standard fields, and the table constraint comprises primary key information of the table, index information of the table and the like. In a further embodiment, rebuilding a database table may be performed when the table information of the metadata registry is modified, desirably synchronously modifying the table information of the corresponding database.

FIG. 6B is a diagram illustrating standard field editing effects of a table according to an embodiment of the present invention. As shown in fig. 6B, USE00001 is a data field, and not all standard fields have a data dictionary. For example, the gender is male and female, so the standard field of the gender has a data dictionary, but the salary of each person is different, so the standard field of the salary has no data dictionary. Here, the newly added standard field in fig. 5C is selected and displayed in the table. The standard field is not added again here, but is selected for display.

In the above, the functions of the modules of metadata management are described, and fig. 7 is a schematic diagram of the effect of data asset management finally formed in the embodiment of the present invention.

Interface management is described below:

in the IT system construction process, the service interface is actually grounded. The service interface has its own name, defines the service function of the interface, has the API recognized by the software system, has the input parameters read after the software system recognizes, and the return parameters after the software system completes the processing. The business interface is input into the metadata platform, so that a developer can be standardized to develop the business interface according to the interface function designed by the business. And simultaneously, recording the interfaces in the design stage, and estimating the development time through the number of the interfaces. In one example, the system may count the development cycle of the interfaces, for example, 10 days are consumed before 10 interfaces are registered, 20 interfaces are registered, and the system can estimate the development cycle to be about 20 days with reference to the last time.

FIG. 8G is a mental diagram of interface management of an embodiment of the present invention. The interface management mainly comprises: the overall properties of the interface and the properties of the interface objects are managed.

Fig. 8A is a schematic diagram of effects of properties of an interface object that can be edited and modified according to an embodiment of the present invention. As shown in fig. 8A, the interface object is a summary of standard fields, and the editable attributes of the interface object mainly include: class name (code class name generated during development, which is understood to be a data type that can be recognized by a machine), interface description (parameter description which is beneficial for business personnel to understand), and standard fields contained (the interior of an interface object is composed of one or more standard fields). Each interface object has its own corresponding fields.

Fig. 8B is a diagram of an editing interface for standard fields of interface objects according to an embodiment of the present invention. The user pops up the interface as shown in fig. 8B by a click operation on the object field button on fig. 8A, where in this example, the primary key, the user ID, the user age, the update time, the user status, and the payroll are all the plurality of standard fields included in the interface object. The above is an example of the plurality of standard fields included in the interface object, but the example is not limited to the above, and the plurality of standard fields included in the interface object are different according to different service functions.

Fig. 8C is a schematic diagram of an attribute management page of an interface according to an embodiment of the present invention. As shown in fig. 8C, after the new interface object is created, an interface can be added. The attributes of the interface mainly include: interface name, Interface function, Interface type, API (Application Programming Interface), Interface parameters. An API is a predefined number of interfaces (e.g., functions, HTTP interfaces) that identify the business functions of a piece of software. Because the editing operation of the interface parameters is relatively complex, the embodiment of the invention adopts the mode of popping out a new page to edit the interface parameters.

Fig. 8D is a schematic diagram of an interface parameter management interface according to an embodiment of the present invention. When the user clicks the interface parameter button in FIG. 8C, an interface as shown in FIG. 8D will be generated, with the interface parameters primarily derived from the standard fields and interface objects. The parameter order is increasing from bottom to top, negative numbers are less than positive numbers, so they are ordered first. Interface parameters of the interface are divided into input parameters and output parameters, which respectively correspond to different labels, and the input parameters and the output parameters of the interface can be simultaneously multiple; if the parameter type of the interface is an interface object, only the class name (the file name when the code is generated) but no field name exists; if the parameter type of the interface is a standard field, only the field name (variable name when generating code) and no object class name; whether the array identifies the interface parameter as being of a collection type (e.g., a person is an object, then a crowd is a collection of people, and a crowd is a collection type.

Fig. 8E is an interface diagram illustrating that the parameter type is a standard field when selecting the parameters of the newly added interface according to the embodiment of the present invention. As shown in fig. 8E, the interface when the type of the parameter for selecting the new interface parameter is the standard field is shown. The keywords are input into the keyword input box, and the data meeting the conditions are selected in the selection box.

Fig. 8F is an interface diagram illustrating the selection of a parameter type as an interface object when adding interface parameters according to the embodiment of the present invention. As shown in fig. 8F, the parameter name configuration item of the interface receives the parameter name inputted by the user, the parameter type configuration item is used to receive the parameter type of the interface parameter selected by the user, the parameter types selected by the user in the interface are interface objects, the keyword search box is used for receiving the text information edited and input by the user, for example, when the user enters the letter U, the name of the object beginning with U is pulled down in the selection box below the keyword search box, the object configuration item refers to an interface object searched according to the condition, the parameter sequence configuration item is used for a user to configure the display sequence of the interface object, whether the array configuration item is used for determining whether the current newly-added interface parameter is a set type or not is determined, and the input and output configuration item is used for the user to select the current newly-added interface parameter to belong to the input parameter or the output parameter through a pull-down option.

Fig. 9 is a schematic diagram of dividing tables and interfaces into different service areas according to an embodiment of the present invention. As shown in fig. 9, the metadata management platform can divide tables and interfaces into different business fields for management. The interface belongs to a function of a service field, belongs to a certain service field, and can comprise or mount one or more interfaces under the service field. For example, when developing the design of an OA office system, the embodiment of the present invention refers to the OA office system as a subsystem in the design stage, which has two business fields for user management and reimbursement management. The USER management service field designs USER (USER table) to be mounted under the service field of USER management, and the reimbursement management service field designs DEMO (reimbursement table) to be mounted under the service field of reimbursement management; under the user management service system, there are two API interfaces for user to add and cancel, which are also hung under the service field of user management. The API interface for the metadata registry is a written registry of the actual application API.

The technical scheme has the advantages that:

metadata management required by IT system construction can be completed through page configuration, and system representation and system complexity are obtained. The software development efficiency, the specification and the safety are guaranteed.

And the interface definition is completed in the design stage to improve the development efficiency.

The metadata management platform can divide tables and interfaces into different business fields so as to facilitate management.

Based on interface management, developers can be informed of the complete interface function in the service design stage, and interface parameter documents do not need to be written.

And obtaining the system complexity through the number of the standard fields and the number of the interfaces. The development time can be estimated in the design stage, for example, ten days are used for the previous 10 interfaces, and under the condition that developers are unchanged, the 20 interfaces are recorded for comparison, so that the development is about 20 days, and a reference function is realized.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

Example two

Fig. 10 is a flowchart of a metadata management method according to an embodiment of the present invention. As shown in fig. 10, it includes the following steps:

s210, responding to a received newly added instruction for newly added data sources, newly adding data sources for the project system, and setting data source information corresponding to the newly added data sources; wherein the data source corresponds to one or more subsystems under the project system.

Specifically, the data source information includes: the unique ID, the name of a database instance, the tablespace of the database, the index space of the database, the user name for accessing the database, the password for accessing the database and the database address; the unique ID is a main key of the data source information, the table space of the database is a file position of data stored in the database, the index space of the database is a file position of index stored in the database, and the name of the database instance is a schema name.

The management of the database table space and the database index space can improve the expansion capability of the metadata platform, and the advantages of the management method specifically include: (1) generating a table building statement is facilitated: in the table building statement of the embodiment, a table space and an index space are necessary, and if not, the generated database table building statement cannot be executed. (2) The basic information management of the system is facilitated: before the software system is built, the basic information of a database depended on by software needs to be registered, and the information of the database table space and the index space needs to be included.

And S220, in response to the received subsystem configuration instruction, editing the configuration information of the selected subsystem.

Specifically, the configuration information of each subsystem may include: the name of the data source corresponding to the subsystem, the English name of the subsystem and the Chinese name of the subsystem.

And S230, in response to receiving the instruction of creating the business domain, creating one or more business domains for the selected subsystems.

Specifically, the configuration information of each service domain includes: a domain identification and a domain description.

And S240, in response to receiving the field management instruction, managing at least one of the data type, the field type and the standard field.

Specifically, the above managing the data type in response to receiving the field management instruction specifically includes:

in response to receiving the instruction of the unified data type, performing at least one of:

unifying a plurality of field types related to the character strings of a plurality of databases into a development-state data type related to the character strings; unifying a plurality of field types related to the integer of a plurality of databases into a development-state data type related to the integer; unifying a plurality of field types related to the decimal of a plurality of databases into a development-state data type related to the decimal; unifying a plurality of field types related to texts of a plurality of databases into a development-state data type related to the texts; the date-related field types of the databases are unified into a development-state data type related to the date.

The advantages are that: the data type of the development state is the type in the development language used by the programmer during development; the program needs to access various databases, different databases have different data types, and the embodiment of the invention performs unified registration by corresponding the different databases to a certain data type in a development state, so that a metadata platform is compatible with various types of databases.

And S250, responding to the received table operation instruction, and operating a plurality of attributes of one or more tables under each service field.

And S260, responding to the received interface editing instruction, and editing the attribute of the interface belonging to the service field.

Specifically, the step S260 specifically includes the following steps:

s262, responding to the received instruction of the new interface, generating an editing page of the attribute of the interface, wherein the attribute of the interface comprises: interface name, interface function, interface type, application program interface API, and interface parameters;

s264, receiving configuration information of a user on an interface name, an interface function, an interface type and an API (application program interface) based on an editing page of the attribute of the interface;

s266, responding to the interface parameter editing instruction, generating an interface parameter editing page, and receiving the configuration information of the user on the interface parameters based on the interface parameter editing page.

Specifically, step S266 may include the steps of:

responding to the click operation of a user on a newly added interface parameter button on the interface parameter editing page, and generating a configuration page for newly added interface parameters; the configuration page comprises a plurality of configuration items as follows: parameter name configuration items, parameter type configuration items, field ID configuration items or object class name configuration items and parameter label configuration items; the parameter tag configuration item is used for configuring the newly added interface parameters into input parameters or output parameters;

In some embodiments, before step S262, further comprising:

s261, responding to the received attribute editing instruction of the interface object, and editing the attribute of the interface object; the attributes of the interface object include: class name, interface description, and standard fields contained in the interface object.

The technical scheme has the advantages that:

Interface definition can be completed in the design stage, so that the development efficiency can be improved.

The metadata management method can divide the tables and the interfaces into different business fields so as to facilitate management.

The interface editing management can inform developers of the complete interface function in the service design stage, and interface parameter documents do not need to be written.

The system complexity can be obtained through the number of the standard fields and the number of the interfaces.

EXAMPLE III

FIG. 11 is a functional block diagram of a computer-readable storage medium of an embodiment of the present invention. As shown in fig. 11, a computer program is stored in a computer-readable storage medium, and when executed by a processor, implements the steps of the metadata management method described above.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow of the method according to the embodiments of the present invention may also be implemented by a computer program, which may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.

Example four

An embodiment of the present invention further provides an electronic device, as shown in fig. 12, including one or more processors 301, a communication interface 302, a memory 303, and a communication bus 304, where the processors 301, the communication interface 302, and the memory 303 complete communication with each other through the communication bus 304.

A memory 303 for storing a computer program;

the processor 301 is configured to implement the steps of the metadata management method when executing the program stored in the memory 303.

Processor 301 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), etc.; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

Memory 303 may include mass storage for data or instructions. By way of example, and not limitation, memory 303 may include a Hard Disk Drive (HDD), a floppy Disk Drive, flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Storage 303 may include removable or non-removable (or fixed) media, where appropriate. In a particular embodiment, the memory 303 is a non-volatile solid-state memory. In a particular embodiment, the memory 303 includes Read Only Memory (ROM). Where appropriate, the ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory or a combination of two or more of these.

The communication bus 304 includes hardware, software, or both for coupling the above-described components to each other. For example, a bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus or a combination of two or more of these. A bus may include one or more buses, where appropriate. Although specific buses have been described and shown in the embodiments of the invention, any suitable buses or interconnects are contemplated by the invention.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Although the present application provides method steps as in an embodiment or a flowchart, more or fewer steps may be included based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A metadata management platform, comprising:

the subsystem configuration module is used for responding to the received subsystem configuration instruction and editing the configuration information of the selected subsystem; the configuration information for each subsystem includes: the name of the data source corresponding to the subsystem, the English name of the subsystem and the Chinese name of the subsystem;

the interface editing module is used for responding to the received interface editing instruction and editing the attribute of the interface belonging to the service field; the interface editing module specifically comprises:

the interface overall attribute editing submodule is used for:

in response to receiving a new interface instruction, generating an edit page of the attributes of the interface, wherein the attributes of the interface include: interface name, interface function, interface type, application program interface API, and interface parameters;

receiving configuration information of a user on the interface name, the interface function, the interface type and the API based on the editing page of the attribute of the interface;

responding to an interface parameter editing instruction, generating an interface parameter editing page, and receiving configuration information of a user on the interface parameter based on the interface parameter editing page.

2. The platform of claim 1, wherein the data source processing module specifically comprises:

a data source adding module, configured to configure, in response to receiving a new adding instruction, at least one piece of data source information of the project system, where the data source information includes: the unique ID, the name of a database instance, the tablespace of the database, the index space of the database, the user name for accessing the database, the password for accessing the database and the database address; the unique ID is a main key of the data source information, the table space of the database is a file position of data stored in the database, the index space of the database is a file position of index stored in the database, and the name of the database instance is a schema name.

3. The platform of claim 2, wherein the data source processing module further comprises:

the data source deleting submodule is used for responding to a received deleting instruction for deleting the data source and deleting the data source information corresponding to the deleting instruction; and/or the presence of a gas in the gas,

and the data source modification submodule is used for modifying the data source information corresponding to the modification instruction in response to receiving the modification instruction for modifying the data source.

4. The platform of claim 1, wherein the field management module specifically comprises:

a data type management submodule, configured to, in response to receiving an instruction of a unified data type, perform at least one of: unifying a plurality of field types related to the character strings of a plurality of databases into a development-state data type related to the character strings; unifying a plurality of field types related to the integer of a plurality of databases into a development-state data type related to the integer; unifying a plurality of field types related to the decimal of a plurality of databases into a development-state data type related to the decimal; unifying a plurality of field types related to texts of a plurality of databases into a development-state data type related to the texts; the date-related field types of the databases are unified into a development-state data type related to the date.

5. The platform of claim 4, wherein the field management module further comprises:

the field type management submodule is used for responding to the received field type configuration instruction and configuring the field length attribute and/or the field precision attribute corresponding to each field type;

a standard field management submodule, configured to manage, in response to receiving a standard field configuration instruction, a plurality of attributes of a standard field, where the plurality of attributes of the standard field include: field names, field descriptions, field types, and data dictionaries.

6. The platform of claim 1, wherein the table manipulation module specifically comprises:

and the second table attribute operation sub-module is used for responding to the click operation of a user on a table field button on the table field management operation page, popping up a table field attribute management page, managing the page based on the table field information and receiving the configuration information corresponding to a plurality of standard fields contained in the table by the user.

7. The platform of claim 6, wherein the table manipulation module further comprises:

and the third table attribute operation submodule is used for responding to the clicking operation of a user on a table constraint button on the table management operation page, popping up a table constraint attribute management page, responding to an operation instruction received by the table constraint information management page, and newly adding a constraint prompt condition for the table.

8. The platform of claim 1, wherein the interface global properties editing sub-module is specifically configured to:

responding to the click operation of a user on a newly added interface parameter button on the interface parameter editing page, and generating a configuration page for newly added interface parameters; wherein the configuration page comprises a plurality of configuration items as follows: parameter name configuration items, parameter type configuration items, field ID configuration items or object class name configuration items and parameter label configuration items; the parameter tag configuration item is used for configuring the newly added interface parameters into input parameters or output parameters;

and responding to the editing operation of the user on a plurality of configuration items on the configuration page of the newly added interface parameters, generating corresponding interface parameters, and displaying the configuration information of the generated interface parameters on the interface parameter editing page.

9. The platform of claim 1, wherein the interface editing module further comprises:

the interface object editing submodule is used for editing the attribute of the interface object in response to the received attribute editing instruction of the interface object; the attributes of the interface object include: class name, interface description and standard fields contained in the interface object.

10. A metadata management method, comprising:

in response to receiving a subsystem configuration instruction, editing the configuration information of the selected subsystem; the configuration information for each subsystem includes: the name of the data source corresponding to the subsystem, the English name of the subsystem and the Chinese name of the subsystem;

in response to receiving the table operation instruction, operating a plurality of attributes of one or more tables belonging to the business field;

in response to receiving an interface editing instruction, editing the attribute of an interface belonging to the service field; wherein, the responding to the received interface editing instruction, editing the attribute of the interface belonging to the service field specifically comprises:

11. The method of claim 10, wherein the data source information comprises: the unique ID, the name of a database instance, the tablespace of the database, the index space of the database, the user name for accessing the database, the password for accessing the database and the database address; the unique ID is a main key of the data source information, the table space of the database is a file position of data stored in the database, the index space of the database is a file position of index stored in the database, and the name of the database instance is a schema name.

12. The method of claim 10, wherein managing the data type in response to receiving the field management instruction comprises:

unifying a plurality of field types related to the character strings of a plurality of databases into a development-state data type related to the character strings;

unifying a plurality of field types related to the integer of a plurality of databases into a development-state data type related to the integer;

unifying a plurality of field types related to the decimal of a plurality of databases into a development-state data type related to the decimal;

unifying a plurality of field types related to texts of a plurality of databases into a development-state data type related to the texts;

the date-related field types of the databases are unified into a development-state data type related to the date.

13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the metadata management method according to any one of claims 10 to 12.

14. A computer device, comprising:

one or more processors;

storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the metadata management method of any of claims 10-12.