Metadata calling method, calling device, management device, equipment and medium

Abstract

The invention discloses a metadata calling method and device, a management device, equipment and a medium, and the method comprises the steps: obtaining an initial data set which comprises request data of a plurality of upstream system construction metadata and historical metadata of a plurality of upstream systems; converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; the method comprises the following steps: after a calling request of a downstream business system is obtained, searching corresponding metadata according to the calling request, and sending the metadata to the downstream business system, so that the downstream business system adopts the metadata to carry out business processing. By unifying the metadata of each upstream system, each metadata can be in a unified standard format, and the situation that field names are the same but meanings are different is avoided, so that business errors are avoided; meanwhile, data consistency can be ensured, data redundancy and conflicts are avoided, the data format is uniform, and information can be shared more efficiently and safely.

Description

Background Art

[0002] Metadata is information used to describe the properties of data, and is used to support functions such as indicating storage location, historical data, resource search, and file records. Metadata is a kind of electronic catalog. In order to achieve the purpose of cataloging, metadata contains the content or characteristics of the data that describes and collects them, thereby achieving the purpose of assisting data retrieval. Therefore, proper metadata management can greatly improve the efficiency and manageability of system support.

[0003] As user demands increase, the number of upstream systems that implement different functions is also gradually increasing. Due to the different development requirements of different upstream systems, in order to match each upstream system, it is necessary to build corresponding metadata based on the characteristic information of each upstream system. When the user needs to use it, each user can use its downstream business system to call the corresponding metadata from the upstream system to perform different business processing.

[0004] However, the commonly used methods currently have the following technical problems: since the upstream systems of various functions operate independently, data and information are used independently; and upstream systems with different functions may generate metadata with the same field names but different meanings, which may cause users to call incorrect metadata from different upstream systems, which in turn may lead to information errors or information conflicts in subsequent business processing, affecting the normal use of users and causing inconvenience to business support and management. Summary of the invention

[0005] The present invention provides a metadata calling method, calling device, management device, equipment and medium, and the method can solve one or more of the above technical problems.

[0006] A first aspect of an embodiment of the present invention provides a metadata calling method, the method comprising: Acquire an initial data set, the initial data set comprising: request data for constructing metadata of multiple upstream systems and historical metadata of multiple upstream systems; Convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; After obtaining the call request of the downstream business system, the corresponding metadata is searched according to the call request, and the metadata is sent to the downstream business system so that the downstream business system uses the metadata to perform business processing.

[0007] In combination with the first aspect, in one implementation, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is request data for constructing metadata by an upstream system, extracting a first export feature item of data from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format; Obtaining a numerical value corresponding to the first derived characteristic item to obtain a plurality of first characteristic values; The multiple first feature values ​​are concatenated according to preset construction requirement information to obtain metadata in a standard format.

[0008] In conjunction with the first aspect, in one implementation, the operation of obtaining the preset construction requirement information includes: Acquire mining information of the requested data, where the mining information is information of master data required for the business; After allocating the corresponding data output interface according to the mining information, testing and verifying the mining information in turn; If both the test process and the verification process are passed, the construction requirement information is obtained; If the test process fails or the verification process fails, the mining information is checked.

[0009] In combination with the first aspect, in one implementation, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is historical metadata of an upstream system, cleaning the historical metadata to obtain cleaned data; After splitting the cleaned data to obtain a plurality of split data, determining a data item corresponding to each split data in a preset dynamic configuration form, and obtaining a second export feature item, wherein the second export feature item is a data item in an export standard format; A numerical value corresponding to the second derived feature item is obtained to obtain a plurality of second feature values, and the plurality of second feature values ​​are concatenated to obtain metadata in a standard format.

[0010] In combination with the first aspect, in one implementation, after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method further includes: The metadata is synchronized to a plurality of upstream systems so that the plurality of upstream systems store the metadata.

[0011] In combination with the first aspect, in one implementation, after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method further includes: Acquire interaction information of an external system, wherein the interaction information is information of querying metadata by the external system; After determining the access rights of the external system based on the ID number of the interactive information, querying the format structure of the metadata according to the format number and the custom field of the interactive information; The format structure is fed back to an external system so that the external system can perform structured processing according to the format structure.

[0012] A second aspect of an embodiment of the present invention provides a metadata calling device, the device comprising: A data acquisition module is used to acquire an initial data set, wherein the initial data set includes: request data for constructing metadata of multiple upstream systems and historical metadata of multiple upstream systems; Constructing a metadata module, which is used to convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; The data calling module is used to find the corresponding metadata according to the calling request after obtaining the calling request of the downstream business system, and send the metadata to the downstream business system so that the downstream business system can use the metadata for business processing.

[0013] In conjunction with the second aspect, in one implementation, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is request data for constructing metadata by an upstream system, extracting a first export feature item of data from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format; Obtaining a numerical value corresponding to the first derived characteristic item to obtain a plurality of first characteristic values; The multiple first feature values ​​are concatenated according to preset construction requirement information to obtain metadata in a standard format.

[0014] In conjunction with the second aspect, in one implementation, the operation of obtaining the preset construction requirement information includes: Acquire mining information of the requested data, where the mining information is information of master data required for the business; After allocating the corresponding data output interface according to the mining information, testing and verifying the mining information in turn; If both the test process and the verification process are passed, the construction requirement information is obtained; If the test process fails or the verification process fails, the mining information is checked.

[0015] In conjunction with the second aspect, in one implementation, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is historical metadata of an upstream system, cleaning the historical metadata to obtain cleaned data; After splitting the cleaned data to obtain a plurality of split data, determining a data item corresponding to each split data in a preset dynamic configuration form, and obtaining a second export feature item, wherein the second export feature item is a data item in an export standard format; A numerical value corresponding to the second derived feature item is obtained to obtain a plurality of second feature values, and the plurality of second feature values ​​are concatenated to obtain metadata in a standard format.

[0016] In conjunction with the second aspect, in one implementation, the device further includes: The synchronization module is used for synchronizing the metadata to multiple upstream systems after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, so that the multiple upstream systems can store the metadata.

[0017] In conjunction with the second aspect, in one implementation, the device further includes: An interactive information acquisition module, used for acquiring interactive information of an external system after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, wherein the interactive information is information of the external system querying metadata; A query structure module, configured to query the format structure of metadata according to the format number and the custom field of the interactive information after determining the access rights of the external system based on the ID number of the interactive information; The structured processing module is used to feed back the format structure to an external system so that the external system can perform structured processing according to the format structure.

[0018] A third aspect of an embodiment of the present invention provides a metadata management device, the device comprising: a metadata system, a plurality of upstream systems and a plurality of downstream systems; The meta information system is applicable to the calling method of metadata as described above; The meta information system is communicatively connected with the plurality of upstream systems and the plurality of downstream systems respectively; The metadata system is provided with an operation interface for users to perform management operations on the metadata in the operation interface. The management operations include: configuration, adjustment, editing and control.

[0019] Compared with the prior art, the metadata calling method, calling device, management device, equipment and medium provided by the embodiment of the present invention have the following beneficial effects: the present invention can obtain the request data for constructing metadata of multiple upstream systems and the historical metadata of multiple upstream systems; convert each request data and historical metadata into metadata in a standard format based on a preset dynamic configuration form; when the downstream business system needs to call, send the corresponding metadata to the downstream business system for the downstream business system to use the metadata for business processing. By unifying the metadata of each upstream system, the present invention can make each metadata in a unified standard format, avoid the situation where the field names are the same but the meanings are different, and thus avoid business errors, ensure data consistency, avoid data redundancy and conflicts, and because the data format is unified, information can be shared more efficiently and securely. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a flowchart of a metadata calling method provided by an embodiment of the present invention; Figure 2 is a schematic diagram of a preset dynamic configuration form provided by an embodiment of the present invention; Figure 3 is an operation flow chart of a user adjusting a standard format provided by an embodiment of the present invention; Figure 4 is an operational flow chart for obtaining construction requirement information provided by an embodiment of the present invention; Figure 5 is an operation flow chart of external system interaction provided by an embodiment of the present invention; Figure 6 It is a structural diagram of a metadata calling device provided by an embodiment of the present invention; Figure 7 It is a structural diagram of a metadata management device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] Metadata is information used to describe the properties of data, and is used to support functions such as indicating storage location, historical data, resource search, and file records. Metadata is a kind of electronic catalog. In order to achieve the purpose of cataloging, metadata contains the content or characteristics of the data that describes and collects them, thereby achieving the purpose of assisting data retrieval. Therefore, proper metadata management can greatly improve the efficiency and manageability of system support.

[0023] As user demands increase, the number of upstream systems that implement different functions is also gradually increasing. Due to the different development requirements of different upstream systems, in order to match each upstream system, it is necessary to build corresponding metadata based on the characteristic information of each upstream system. When the user needs to use it, each user can use its downstream business system to call the corresponding metadata from the upstream system to perform different business processing.

[0024] However, the commonly used methods currently have the following technical problems: since the upstream systems of various functions operate independently, data and information are used independently; and upstream systems with different functions may generate metadata with the same field names but different meanings, which may cause users to call incorrect metadata from different upstream systems, which in turn may lead to information errors or information conflicts in subsequent business processing, affecting the normal use of users and causing inconvenience to business support and management.

[0025] In order to solve the above problems, a metadata calling method, calling device, management device, equipment and medium provided in an embodiment of the present application will be introduced and explained in detail through the following specific embodiments.

[0026] Reference Figure 1 , showing a flowchart of a metadata calling method provided by an embodiment of the present invention.

[0027] The metadata calling method may be applicable to a metadata system or a meta-information system. The metadata system or the meta-information system may be connected to an upstream system for communication, or may be connected to a downstream business system for communication.

[0028] The metadata system or meta-information system can construct metadata so that the metadata of different upstream systems can be in a unified format. When the downstream business system needs to call metadata, it can extract metadata through the metadata system or meta-information system and then use the metadata to perform corresponding business processing.

[0029] As an example, the metadata calling method may include: S11. Acquire an initial data set, where the initial data set includes: request data for constructing metadata from multiple upstream systems and historical metadata from multiple upstream systems.

[0030] In one embodiment, an initial data set may be obtained, where the initial data set includes: request data for metadata construction by multiple upstream systems and historical metadata of multiple upstream systems.

[0031] In specific operations, each upstream system needs to build corresponding metadata according to its implementation functions for downstream business systems to call, and can send request data to the metadata system or meta-information system, which can request the metadata system or meta-information system to build corresponding metadata.

[0032] Similarly, the upstream system may have constructed multiple metadata at an earlier time point, and the metadata previously constructed by different upstream systems may be the same or different.

[0033] In order to unify the metadata of the previous build, the historical metadata of the upstream system can also be obtained.

[0034] By obtaining the request data for the current metadata construction and the previous historical metadata, metadata in a unified format can be generated based on the request data. At the same time, historical metadata can also be converted into metadata in a unified format, thereby unifying the format of all metadata, so that the metadata field names can be the same but the meanings can be different, and data and information from different upstream systems can flow freely between systems, making it easier for users to manage data from different systems. Moreover, after the data format is unified, it can also be achieved that data cannot be effectively transmitted between different systems, so as to avoid data transmission errors caused by inconsistent technical standards and incompatible interfaces.

[0035] S12. Convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form.

[0036] After the initial data set is obtained, each data in the initial data set can be converted according to the format items in the preset dynamic configuration form, so that each data in the initial data set is converted into data in a standard format to obtain multiple metadata.

[0037] It should be noted that the preset dynamic configuration form may be a form preset by the user, and the preset dynamic configuration form records various format items of the user-exported metadata.

[0038] In order to facilitate the conversion of each data of the initial data set into metadata of a standard format that meets user requirements, in one operation mode, the preset dynamic configuration form may be a visual operation interface form, in which a plurality of customizable components are arranged.

[0039] Reference Figure 2 , showing a schematic diagram of a preset dynamic configuration form provided by an embodiment of the present invention.

[0040] In an optional embodiment, the preset dynamic configuration form can be as follows Figure 2 As shown, the user can directly select format components in the visual form, and then compose the standard format of metadata, and then perform conversion processing according to the standard format of the form.

[0041] In an optional embodiment, the data to be converted is the request data of the upstream system to construct metadata. The request data can be the request to construct metadata automatically triggered by the upstream system, or can be the request to construct metadata determined offline by the administrator of the upstream system.

[0042] For example, the manager of the upstream system conducts offline mining or discovers that the upstream system finds that certain data belongs to master data and needs to build metadata for the master data. The manager can control the upstream system to generate and send request data, so that the downstream business system can call the master data according to the metadata for related calculations or business applications.

[0043] In order to meet the needs and actual situation of offline data mining of managers of upstream systems, as an example, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form may include the following sub-steps: S21. If the data of the initial data set is request data for constructing metadata by an upstream system, extracting a first export feature item of data from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format.

[0044] S22. Obtain a numerical value corresponding to the first derived feature item to obtain a plurality of first feature values.

[0045] S23. Concatenate the multiple first feature values ​​according to preset construction requirement information to obtain metadata in a standard format.

[0046] Specifically, if the data to be converted is request data for constructing metadata by an upstream system, a first export feature item of the data may be extracted from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format.

[0047] by Figure 2 For example, the data items exported in the standard format include: game ID, game name, project ID, project name, distribution area and source system. The source system can be the upstream system of the main data for which the data is requested.

[0048] After determining the above-mentioned first derived feature items, the numerical values ​​corresponding to the first derived feature items can be obtained, including the numerical value corresponding to the game ID, the numerical value corresponding to the game name, the numerical value corresponding to the project ID, the numerical value corresponding to the project name, etc., so that multiple first feature values ​​can be obtained.

[0049] Since the request data is the metadata used to trigger the construction of the main data for user mining, in order to meet the actual needs of user mining, the user's demand content for constructing metadata can be obtained to obtain the preset construction demand information. Finally, multiple first feature values ​​are spliced ​​according to the preset construction demand information to obtain metadata in a standard format.

[0050] The splicing operation may include the following steps: The first step is to extract the splicing arrangement order from the construction requirement information.

[0051] In the second step, after arranging the multiple first characteristic values ​​according to the arrangement order, the multiple first characteristic value field values ​​are concatenated into corresponding SQL statements.

[0052] The third step is to compress the generated SQL statement, and perform base64 encryption on the compressed byte stream to generate a string to obtain metadata.

[0053] Optionally, if multiple first feature values ​​can be concatenated to obtain multiple SQL statements, the SQL statements of the same type in this operation can be merged to obtain the required SQL statements, and then the SQL statements are compressed and encrypted to obtain metadata. After obtaining the metadata, the metadata can be exported in Schema format to obtain metadata in a standard format.

[0054] Reference Figure 3 , shows an operational flow chart of a user adjusting a standard format provided by an embodiment of the present invention.

[0055] In one embodiment, the user can also adjust the export format of the metadata according to actual needs. Figure 3 , you can add data dictionary components in the metadata system or meta information system in advance, and support binding a certain dictionary type of the database to adjust the data export format.

[0056] Similarly, when the user needs to adjust the numerical value of the first eigenvalue, the user can pull down the binding database field component in the interface of the metadata system or meta-information system. During design, the drop-down box can be bound to the Key\Value field in a certain Schema definition. During runtime, the data set is adjusted to dynamically bind data according to the description of the Schema to adjust the numerical value of the first eigenvalue.

[0057] In an optional embodiment, the request of the upstream system to construct metadata may meet the system requirements of the upstream system, or may exceed the burden or authority of the upstream system.

[0058] In order to determine whether the needs for building metadata meet the requirements, the user's testing and verification can be carried out. Only when the test and verification are passed can it be processed according to the user's building needs.

[0059] Wherein, as an example, the operation of obtaining the preset construction requirement information may include the following sub-steps: S101. Acquire mining information of the requested data, where the mining information is information of master data required for the business.

[0060] S102: After allocating corresponding data output interfaces according to the mining information, test and verify the mining information in sequence.

[0061] S103: If both the test process and the verification process are passed, construction requirement information is obtained.

[0062] S104: If the test process fails or the verification process fails, then the mining information is checked.

[0063] Reference Figure 4 , showing an operational flow chart for obtaining construction requirement information provided by an embodiment of the present invention. In one embodiment, according to the above analysis, the construction of metadata may be that the administrator of the upstream system mines a certain master data offline for the downstream business system to process the business, thus triggering this request. In order to determine whether the mined master data meets the requirements for building metadata, and to determine whether this master data exceeds the burden or authority of the upstream system, the mining information of the requested data can be obtained, and the mining information is the relevant information of the master data required by the business. Including information such as the source, purpose, ID, business scenario, transmission format, and transmission bandwidth of the mined master data.

[0064] Next, a corresponding data output interface can be allocated according to the transmission requirements, bandwidth, quantity, etc. of the master data in the mining information, and the data output interface is used for the subsequent transmission of the master data and the metadata corresponding to the master data. In one embodiment, the data output interface can be an API interface for the subsequent transmission of metadata.

[0065] After the allocation is completed, the mining information can be tested and verified in turn. If both the test and verification processes are passed, it means that the master data meets the system requirements of the upstream system and does not exceed the burden or authority of the upstream system. Then, the information added by the user during the test and verification process can be obtained to obtain the construction requirement information.

[0066] On the contrary, if the test process fails or the verification process fails, it means that the master data does not meet the system requirements of the upstream system, or exceeds the burden or authority of the upstream system, and the mining information is then checked and processed.

[0067] In specific operations, if the data of the initial data set is the request data for the upstream system to build metadata, after obtaining the request data, it can be determined whether the request data is provided by the CUD page of the upstream system, or whether the request data is uploaded and provided by the interface created by the upstream system.

[0068] If the request data is not provided by the CUD page of the upstream system, nor is it provided by the interface created by the upstream system, the request data can be specially processed. The specific process of special processing can be to display the request data to the administrator of the metadata system or meta-information system, so that the administrator of the metadata system or meta-information system can check whether the content of the request data and the scope of the request are reasonable.

[0069] If the request data is provided by the CUD page of the upstream system, or the request data is uploaded by the interface created by the upstream system, the request data can be directly approved. The specific process of approval processing can include the following steps: The first step is to convert the request data into a field in a preset format. After obtaining the request field, a plurality of fields are extracted from the request field in a preset arrangement order to obtain a plurality of extracted fields.

[0070] The second step is to compare each of the extracted fields with the corresponding fields in the preset approval list.

[0071] In the third step, if each extracted field is the same as the corresponding field in the preset approval list, the approval process is determined to be passed; otherwise, if any extracted field is different from the corresponding field in the preset approval list, the approval process is determined to be failed.

[0072] By comparing the fields, it is possible to determine whether the request for building metadata initiated by the upstream system complies with the permissions of the upstream system, so as to fit the actual operating status of the upstream system and improve the accuracy of metadata construction.

[0073] Optionally, the request data may also be displayed to administrators of the metadata system or meta-information system, so that the administrators of the metadata system or meta-information system can check whether the content of the request data and the request scope are reasonable, so as to complete the approval process.

[0074] After completing the above processing, the mining information of the requested data can be obtained. The mining information can be the user's needs for constructing metadata based on the requested data, including the transmission interface for constructing metadata, the storage address for constructing metadata, the number of constructing metadata, the calling authority for constructing metadata, etc.

[0075] In one implementation, the technicians can directly input the mining information. In actual operation, the technicians or managers can fill in their requirements for building metadata in the data format template of the metadata system or meta-information system after communicating the actual application requirements to obtain the mining information.

[0076] Next, the mined information can be tested and verified. The test process can be a functional test of the information and data. Since the metadata constructed based on the mined information is a dictionary or field combination, it provides configuration services for a certain system function or business scenario. For example, a business scenario can be constructed, and then it is determined whether the dictionary or field of the metadata corresponding to the mined information can trigger the operation of the business scenario or whether it can be calculated in the business scenario. If the operation of the business scenario can be triggered or the calculation can be performed in the business scenario, the test process is determined to be passed; otherwise, the test process is determined to be failed.

[0077] In another optional implementation, the metadata configuration can support basic logical judgments and expression calculations. The logical judgments or expressions of the test can be constructed, and then the calculated values ​​can be extracted from the mined information. It is then determined whether the extracted values ​​can be used for logical judgments and expression calculations. If so, the test process is determined to have passed; otherwise, the test process is determined to have failed.

[0078] The verification process may be a verification process for the functional test to determine whether there are errors or mistakes in the test to ensure that the test is correct.

[0079] In an optional embodiment, a technician may select a function item for testing in a metadata system or a meta-information system, and then the metadata system or the meta-information system obtains a data set required for the function item, where the data set includes test data and test result data.

[0080] Data acceptance is performed based on the data set. Specifically, a data checklist can be generated based on the data set, and then the data checklist is shown to the technical staff for them to review and check to determine whether the verification process has passed.

[0081] Optionally, after acquiring the data set, the data in the data set may be compared with the user's set value. If the comparison results are the same, the verification process is passed; otherwise, the verification process is not passed.

[0082] If the test process fails or the verification process fails, the mining information is checked. The checking process can be to determine the data items that are different in the data comparison in the verification process, find the corresponding mining information value according to the data item, and then show the above values ​​to the technicians for them to adjust the values ​​so that the mining information can meet the requirements, so that the metadata construction process can be carried out later.

[0083] In another optional embodiment, the data to be converted is the historical metadata of the upstream system. The request data may be metadata constructed by the upstream system at a previous time node. And the metadata is metadata constructed by the upstream system at a previous time node according to its system characteristics.

[0084] For example, the upstream system provides the main task distribution function for the game. Different main tasks for different game characters can be used to build different metadata for different main tasks. The subsequent downstream business system can extract the main task information of the game character from the upstream system based on different metadata.

[0085] The metadata constructed by different upstream systems may have the same field names but different meanings, different field names but the same meanings, the same field names but different value ranges, or the same field names but inconsistent key value numbers.

[0086] In order to integrate the metadata previously constructed by various upstream systems, as an example, converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form may include the following sub-steps: S31. If the data of the initial data set is historical metadata of an upstream system, the historical metadata is cleaned to obtain cleaned data.

[0087] S32. After splitting the cleaned data to obtain a plurality of split data, determine the data item corresponding to each split data in a preset dynamic configuration form to obtain a second export feature item, where the second export feature item is a data item in an export standard format.

[0088] S33: Acquire a numerical value corresponding to the second derived feature item to obtain a plurality of second feature values, and concatenate the plurality of second feature values ​​to obtain metadata in a standard format.

[0089] In one operation mode, if the data of the initial data set is historical metadata of an upstream system, the historical metadata may be cleaned to obtain cleaned data.

[0090] Specifically, cleaning can be to clean various historical metadata into unified metadata. Specifically, data cleaning can be performed in a conventional manner.

[0091] The previous historical metadata is also generated by splicing the characteristic information of its upstream system and various characteristic information of the data (such as ID and address, etc.). In order to extract various characteristic information (such as ID and address, etc.) from the historical metadata, the cleaned data can be split, and multiple split data can be obtained after the split.

[0092] The unified standard format may use every data item, or may use several data items in the split. The data item corresponding to each split data item in the preset dynamic configuration form can be determined to obtain the second export feature item, which is the data item of the export standard format. Figure 2 The second derived feature item may also include game ID, game name, project ID, project name, distribution area and source system, etc.

[0093] After determining the second derived feature item, the value corresponding to the second derived feature item can also be obtained, referring to Figure 2 , which may include a numerical value corresponding to the game ID, a numerical value corresponding to the game name, a numerical value corresponding to the project ID, a numerical value corresponding to the project name, etc., so that multiple second characteristic values ​​can be obtained, and finally multiple second characteristic values ​​are concatenated to obtain metadata in a standard format.

[0094] Since new metadata is constructed using historical metadata, in order to fit the previous historical metadata, corresponding values ​​can be directly extracted from the historical metadata to obtain multiple second feature values.

[0095] The splicing method may also refer to the analytical instructions of the above steps.

[0096] In another optional embodiment, the splicing operation may include the following steps: The first step is to concatenate multiple second characteristic values ​​to generate a corresponding first character string.

[0097] The second step is to perform a preset algorithm signature and byte conversion on the first character string to generate metadata.

[0098] For the embodiment of the present invention, when multiple second characteristic values ​​are spliced, the parameter fields of the multiple second characteristic values ​​can be sorted in ascending order according to the size of the ASCII code of the field name; the sorted values ​​are spliced ​​to generate a first character string.

[0099] In one embodiment, new metadata may be generated using historical metadata. After the metadata is generated, each downstream business system may also call metadata from an upstream system. In order to allow the new metadata to replace each historical metadata, as an example, after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method may further include the following sub-steps: S41. Synchronize the metadata to multiple upstream systems so that the multiple upstream systems can store the metadata.

[0100] Specifically, after generating metadata, the metadata system or meta-information system may transmit the metadata to each connected upstream system, so that multiple upstream systems store the metadata and use the new metadata to replace the original historical metadata.

[0101] In one of the embodiments, when performing different business processes, external systems may also be involved. The external systems may be systems that provide different functions, or business systems that provide metadata data. The data source of the external system may be responsible for generating business data; for example, it may be data storage, data encryption, screen background adjustment, transfer, etc. The data source of the external system generally synchronizes project, game, channel, share and other information from the CRM and basic data center API interface. After the new super SDK background is completed, it also needs to be synchronized from the new super SDK.

[0102] When synchronization is required, the external system may also need to call metadata. In order to inform the external system of the data format and structure of the metadata and facilitate the subsequent calling of different functional applications, as an example, after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method may also include the following sub-steps: S51. Obtain interaction information of an external system, where the interaction information is information of metadata queried by the external system.

[0103] S52: After determining the access rights of the external system based on the ID number of the interactive information, query the format structure of the metadata according to the format number and the custom field of the interactive information.

[0104] S53: Feedback the format structure to an external system, so that the external system can perform structured processing according to the format structure.

[0105] Reference Figure 5 , showing an operational flow chart of external system interaction provided by an embodiment of the present invention.

[0106] Specifically, the interaction information of the external system is obtained, and the interaction information is the information of the external system querying metadata. Figure 5 The interactive information may be information about metadata or meta-information queried by an external system, and specifically may be a Schema number, Schema version number, etc. of the queried metadata or meta-information.

[0107] The metadata system or meta-information system can determine whether the external system has access rights based on the ID number of the external system that sends the interactive information. If the external system has access rights, the format structure of the metadata can be queried based on the format number and custom fields of the interactive information.

[0108] Finally, the format structure is fed back to the external system for the external system to perform structured processing based on the format structure.

[0109] S13. After obtaining the call request of the downstream business system, search for corresponding metadata according to the call request, and send the metadata to the downstream business system so that the downstream business system uses the metadata to perform business processing.

[0110] After generating multiple different metadata, the metadata can also be stored in the database of the metadata system or the meta-information system. When the downstream business system needs to use the metadata, it can obtain a call request from the downstream business system, search for the corresponding metadata according to the call request, and send the metadata to the downstream business system so that the downstream business system can use the metadata for business processing.

[0111] Specifically, the corresponding metadata may be matched according to the system source and business type of the call request, and then the metadata may be sent to the corresponding downstream business system.

[0112] In this embodiment, the embodiment of the present invention provides a metadata calling method, and its beneficial effects are: the present invention can obtain the request data for building metadata of multiple upstream systems and the historical metadata of multiple upstream systems; based on the preset dynamic configuration form, each request data and historical metadata are converted into metadata in a standard format; when the downstream business system needs to call, the corresponding metadata is sent to the downstream business system for the downstream business system to use the metadata for business processing. By unifying the metadata of each upstream system, the present invention can make each metadata in a unified standard format, avoid the situation where the field names are the same but the meanings are different, and thus avoid business errors, ensure data consistency, avoid data redundancy and conflicts, and because the data format is unified, information can be shared more efficiently and securely.

[0113] The embodiment of the present invention also provides a metadata calling device, see Figure 6 , showing a schematic structural diagram of a metadata calling device provided by an embodiment of the present invention.

[0114] Wherein, as an example, the metadata calling device may include: The data acquisition module 601 is used to acquire an initial data set, wherein the initial data set includes: request data for constructing metadata of multiple upstream systems and historical metadata of multiple upstream systems; A metadata building module 602 is used to convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; The data calling module 603 is used to find the corresponding metadata according to the calling request after obtaining the calling request of the downstream business system, and send the metadata to the downstream business system so that the downstream business system can use the metadata to perform business processing.

[0115] Optionally, the converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is request data for constructing metadata by an upstream system, extracting a first export feature item of data from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format; Obtaining a numerical value corresponding to the first derived characteristic item to obtain a plurality of first characteristic values; The multiple first feature values ​​are concatenated according to preset construction requirement information to obtain metadata in a standard format.

[0116] Optionally, the operation of obtaining the preset construction requirement information includes: Acquire mining information of the requested data, where the mining information is information of master data required for the business; After allocating the corresponding data output interface according to the mining information, testing and verifying the mining information in turn; If both the test process and the verification process are passed, the construction requirement information is obtained; If the test process fails or the verification process fails, the mining information is checked.

[0117] Optionally, the converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is historical metadata of an upstream system, cleaning the historical metadata to obtain cleaned data; After splitting the cleaned data to obtain a plurality of split data, determining a data item corresponding to each split data in a preset dynamic configuration form, and obtaining a second export feature item, wherein the second export feature item is a data item in an export standard format; A numerical value corresponding to the second derived feature item is obtained to obtain a plurality of second feature values, and the plurality of second feature values ​​are concatenated to obtain metadata in a standard format.

[0118] Optionally, the device further comprises: The synchronization module is used for synchronizing the metadata to multiple upstream systems after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, so that the multiple upstream systems can store the metadata.

[0119] Optionally, the device further comprises: An interactive information acquisition module, used for acquiring interactive information of an external system after the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, wherein the interactive information is information of the external system querying metadata; A query structure module, configured to query the format structure of metadata according to the format number and the custom field of the interactive information after determining the access rights of the external system based on the ID number of the interactive information; The structured processing module is used to feed back the format structure to an external system so that the external system can perform structured processing according to the format structure.

[0120] The embodiment of the present invention also provides a metadata management device, see Figure 7 , showing a schematic structural diagram of a metadata management device provided by an embodiment of the present invention.

[0121] Wherein, as an example, the metadata management device may include: a metadata system, multiple upstream systems and multiple downstream systems; The metadata system is applicable to the metadata calling method as described in the above embodiment; The meta information system is communicatively connected with the plurality of upstream systems and the plurality of downstream systems respectively; The metadata system is provided with an operation interface for users to perform management operations on the metadata in the operation interface. The management operations include: configuration, adjustment, editing and control.

[0122] In one embodiment, the meta-information system may provide front-end services, management back-end services, synchronization services, API services, and push services.

[0123] Front-end service, used to provide a human-computer interaction interface for administrators and ordinary users; Manage backend services to implement relevant logic required by the front end and complete relevant business logic such as data display, editing, design, and storage; Synchronization service is responsible for synchronizing relevant metadata data from the business system data source to local storage; API service, used to provide API query services for downstream systems; Push service is responsible for pushing metadata data to downstream business systems.

[0124] Moreover, the meta-information system can also dynamically configure the data structure: based on the schema standard format (XRender standard) of the dynamic configuration form, the form field structure can be changed to adapt to the diversity of business needs. It can also be combined with dynamic schema configuration to dynamically expand fields without code. After completing the configuration of the data template, the system can automatically obtain the new structure data from the target data source and store it in the database, and provide it to downstream services.

[0125] It should be noted that the metadata system utilizes the data definition capability of JsonSchemas. By formulating metadata definition standards for different needs and aligning the definitions of all parties within the needs, the problem of metadata definition differences can be solved. XRender's visual editing and MongoDB's data structure expansion capabilities implement a metadata dynamic management function to solve the problem of customized development required for different business fields and relationships in daily system development.

[0126] Those skilled in the art can clearly understand that, for the sake of convenience and brevity of description, the specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0127] Furthermore, an embodiment of the present application also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the metadata calling method as described in the above embodiment is implemented.

[0128] Furthermore, an embodiment of the present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer-executable program, and the computer-executable program is used to enable a computer to execute the metadata calling method as described in the above embodiment.

[0129] It should be noted that the orientation or positional relationship indicated by the terms "upper", "lower", etc. is based on the orientation or positional relationship shown in the accompanying drawings, which is only for the convenience of describing the embodiments of the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation of the present invention. When an element such as a layer, region or substrate is referred to as being "on" or "above" another element, it can be directly on the other element, or there can also be an intermediate element. On the contrary, when an element is referred to as "directly on" or "above" another element, there is no intermediate element. It should also be understood that when an element is referred to as being "under" or "below" another element, it can be directly under or below the other element, or there can also be an intermediate element. On the contrary, when an element is referred to as being "directly under" or "below" another element, there is no intermediate element. Unless otherwise clearly specified and limited, the terms "installed", "connected" and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0130] Those skilled in the art will appreciate that the embodiments of the present application may also provide computer program products. Therefore, the present application may adopt the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the present application may adopt the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program codes.

[0131] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), apparatuses, and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0132] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0133] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0134] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the technical principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A metadata calling method, characterized in that: The method comprises: Acquire an initial data set, the initial data set comprising: request data for constructing metadata of multiple upstream systems and historical metadata of multiple upstream systems; Convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; After obtaining the call request of the downstream business system, the corresponding metadata is searched according to the call request, and the metadata is sent to the downstream business system so that the downstream business system uses the metadata to perform business processing.

2. The metadata calling method according to claim 1, characterized in that: The method of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is request data for constructing metadata by an upstream system, extracting a first export feature item of data from a preset dynamic configuration form according to the request data, wherein the first export feature item is a data item in an export standard format; Obtaining a numerical value corresponding to the first derived characteristic item to obtain a plurality of first characteristic values; The multiple first feature values ​​are concatenated according to preset construction requirement information to obtain metadata in a standard format.

3. The metadata calling method according to claim 2, characterized in that: The operation of obtaining the preset construction requirement information includes: Acquire mining information of the requested data, where the mining information is information of master data required for the business; After allocating the corresponding data output interface according to the mining information, testing and verifying the mining information in turn; If both the test process and the verification process are passed, the construction requirement information is obtained; If the test process fails or the verification process fails, the mining information is checked.

4. The metadata calling method according to claim 1, characterized in that: The method of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form includes: If the data of the initial data set is historical metadata of an upstream system, cleaning the historical metadata to obtain cleaned data; After splitting the cleaned data to obtain a plurality of split data, determining a data item corresponding to each split data in a preset dynamic configuration form, and obtaining a second export feature item, wherein the second export feature item is a data item in an export standard format; A numerical value corresponding to the second derived feature item is obtained to obtain a plurality of second feature values, and the plurality of second feature values ​​are concatenated to obtain metadata in a standard format.

5. The metadata calling method according to claim 1, characterized in that: After the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method further includes: The metadata is synchronized to a plurality of upstream systems so that the plurality of upstream systems store the metadata.

6. The metadata calling method according to claim 1, characterized in that: After the step of converting each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form, the method further includes: Acquire interaction information of an external system, wherein the interaction information is information of querying metadata by the external system; After determining the access rights of the external system based on the ID number of the interactive information, querying the format structure of the metadata according to the format number and the custom field of the interactive information; The format structure is fed back to an external system so that the external system can perform structured processing according to the format structure.

7. A metadata calling device, characterized in that: The device comprises: A data acquisition module is used to acquire an initial data set, wherein the initial data set includes: request data for constructing metadata of multiple upstream systems and historical metadata of multiple upstream systems; Constructing a metadata module, which is used to convert each data of the initial data set into metadata in a standard format based on a preset dynamic configuration form; The data calling module is used to find the corresponding metadata according to the calling request after obtaining the calling request of the downstream business system, and send the metadata to the downstream business system so that the downstream business system can use the metadata for business processing.

8. A metadata management device, characterized in that: The device comprises: a meta information system, a plurality of upstream systems and a plurality of downstream systems; The metadata system is applicable to the metadata calling method as described in any one of claims 1 to 6; The meta information system is communicatively connected with the plurality of upstream systems and the plurality of downstream systems respectively; The metadata system is provided with an operation interface for users to perform management operations on the metadata in the operation interface. The management operations include: configuration, adjustment, editing and control.

9. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the metadata calling method as described in any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer-executable program, and the computer-executable program is used to enable a computer to execute the metadata calling method according to any one of claims 1 to 6.

Images