Data exporting method and device of resource management system and electronic equipment

Abstract

The invention provides a data exporting method and device of a resource management system and electronic equipment. The method comprises the steps that a first data table, a system column name mapping relation and a standard column name mapping relation corresponding to the resource management system are obtained; converting the column name of the first data table into a system column name based on a system column name mapping relation to obtain a second data table; converting the column name of the second data table into a standard column name based on a standard column name mapping relation to obtain a third data table; and based on the third data table, exporting data from the resource management system to generate a target data table. By acquiring the first data table needing to be exported by a user and converting the first data table into the second data table which can be identified by the system, data export of different resource management systems can be realized, and finally the data is converted into the third data table with a unified standard, so that subsequent steps of identification, summarization, analysis and the like are facilitated, the cost of subsequent data processing can be saved, and the data processing efficiency is improved. And meanwhile, the method is suitable for large data volume.

Description

Technical Field

[0001] The present disclosure relates to the field of big data technology, and in particular to a data export method, device and electronic device for a resource management system. Background Art

[0002] The Enterprise Resource Planning (ERP) system is an information system that integrates the logistics, capital flow, and information flow of an enterprise, and is used to manage all aspects of a company, such as production, sales, procurement, inventory, finance, etc. The ERP system can effectively integrate the existing production resources of an enterprise and promote the real-time and lean management of the enterprise.

[0003] There are many popular EPR systems on the market. Different ERP system types use completely different technologies, and the underlying data models are also completely different. In the current technology, it is necessary to manually develop corresponding data export rules for different EPR systems, which increases the cost of data export. Especially when the amount of data is large and there are many types of ERP systems, the efficiency is very low. Summary of the invention

[0004] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

[0005] To achieve the above-mentioned purpose, the first aspect of the present disclosure proposes a data export method for a resource management system, including: obtaining a system column name mapping relationship between a first data table to be exported and the resource management system to which data needs to be exported, and a standard column name mapping relationship corresponding to the resource management system; based on the system column name mapping relationship, converting the column names of the first data table into system column names to obtain a second data table; based on the standard column name mapping relationship, converting the column names of the second data table into standard column names to obtain a third data table; based on the third data table, exporting data from the resource management system to generate a target data table.

[0006] According to one embodiment of the present disclosure, based on the third data table, data is exported from the resource management system to generate a target data table before it also includes: obtaining a system startup mapping, the system startup mapping being a mapping relationship between system information, a driver, and a dialect; based on the system information of the resource management system, determining a target driver and a target dialect that match it from the system startup mapping; and starting the resource management system based on the target driver and the target dialect.

[0007] According to one embodiment of the present disclosure, based on a third data table, data is exported from a resource management system to generate a target data table, including: obtaining user information in the third data table; based on the user information, exporting user data matching the user information from the resource management system; and importing the user data into the third user table to generate a target data table.

[0008] According to an embodiment of the present disclosure, obtaining a first data table to be exported includes: obtaining input column names to be exported; and arranging the column names to be exported to obtain the first data table.

[0009] According to one embodiment of the present disclosure, arranging the column names to be exported to obtain the first data table includes: obtaining the priorities of the column names to be exported; and arranging the column names to be exported in descending order based on the priorities to obtain the first data table.

[0010] According to one embodiment of the present disclosure, based on the system column name mapping relationship, the column names of the first data table are converted into system column names to obtain the second data table, including: obtaining the data type of the data to be exported in the first data table; based on the data type, determining a first column name conversion rule that matches the data type from the system column name mapping relationship; based on the first column name conversion rule, converting the column names of the first data table into system column names to obtain the second data table.

[0011] According to one embodiment of the present disclosure, based on the system column name mapping relationship, the column names of the first data table are converted into system column names to obtain the second data table, including: in response to the system column names corresponding to multiple first candidate column names in the first column name conversion rule, the column names of the first data table are matched with the candidate column names; in response to a successful match, the system column names corresponding to the successfully matched candidate column names are determined to be the system column names that need to be converted.

[0012] According to one embodiment of the present disclosure, based on the standard column name mapping relationship, the column names of the second data table are converted into standard column names to obtain a third data table, including: based on the data type, determining a second column name conversion rule that matches the data type from the system column name mapping relationship; based on the second column name conversion rule, converting the column names of the second data table into standard column names to obtain the third data table.

[0013] According to one embodiment of the present disclosure, based on the standard column name mapping relationship, the column names of the second data table are converted into standard column names to obtain a third data table, including: in response to the system column names corresponding to multiple second candidate column names in the second column name conversion rule, the column names of the second data table are matched with the candidate column names; in response to a successful match, the standard column names corresponding to the successfully matched candidate column names are determined to be the standard column names that need to be converted.

[0014] To achieve the above-mentioned purpose, the second aspect embodiment of the present disclosure proposes a data export device for a resource management system, including: an acquisition module, used to obtain the system column name mapping relationship between a first data table to be exported and the resource management system to which data needs to be exported, and the standard column name mapping relationship corresponding to the resource management system; a first conversion module, used to convert the column names of the first data table into system column names based on the system column name mapping relationship to obtain a second data table; a second conversion module, used to convert the column names of the second data table into standard column names based on the standard column name mapping relationship to obtain a third data table; and a generation module, used to export data from the resource management system based on the third data table to generate a target data table.

[0015] According to one embodiment of the present disclosure, the generation module is also used to: obtain a system startup map, which is a mapping relationship between system information, a driver and a dialect; based on the system information of the resource management system, determine a target driver and a target dialect that match it from the system startup map; and start the resource management system based on the target driver and the target dialect.

[0016] According to one embodiment of the present disclosure, the generation module is also used to: obtain user information in the third data table; based on the user information, export user data matching the user information from the resource management system; import the user data into the third user table to generate the target data table.

[0017] According to an embodiment of the present disclosure, the acquisition module is further used to: acquire input column names to be exported; and arrange the column names to be exported to acquire the first data table.

[0018] According to one embodiment of the present disclosure, the first conversion module is further used to: obtain the data type of the data to be exported in the first data table; based on the data type, determine a first column name conversion rule that matches the data type from the system column name mapping relationship; based on the first column name conversion rule, convert the column name of the first data table into a system column name to obtain the second data table.

[0019] According to one embodiment of the present disclosure, the first conversion module is further used for: in response to the system column name corresponding to multiple first candidate column names in the first column name conversion rule, matching the column names of the first data table with the candidate column names; in response to a successful match, determining that the system column name corresponding to the successfully matched candidate column name is the system column name that needs to be converted.

[0020] According to one embodiment of the present disclosure, the second conversion module is also used to: based on the data type, determine a second column name conversion rule that matches the data type from the system column name mapping relationship; based on the second column name conversion rule, convert the column name of the second data table into a standard column name to obtain the third data table.

[0021] According to one embodiment of the present disclosure, the second conversion module is also used for: in response to the system column name corresponding to multiple second candidate column names in the second column name conversion rule, matching the column names of the second data table with the candidate column names; in response to a successful match, determining that the standard column names corresponding to the successfully matched candidate column names are the standard column names that need to be converted.

[0022] To achieve the above-mentioned purpose, the third aspect embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to implement the data export method of the resource management system as described in the first aspect embodiment of the present disclosure.

[0023] To achieve the above-mentioned purpose, the fourth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to implement the data export method of the resource management system as described in the first aspect embodiment of the present disclosure.

[0024] To achieve the above-mentioned purpose, the fifth aspect of the present disclosure proposes a computer program product, including a computer program, which, when executed by a processor, is used to implement the data export method of the resource management system as described in the first aspect of the present disclosure.

[0025] By obtaining the first data table that the user needs to export and converting it into a second data table that the system can recognize, data export from different resource management systems can be achieved, and finally converted into a third data table with unified standards, which is convenient for subsequent identification, aggregation, analysis and other steps, can save the cost of subsequent data processing, and is also suitable for situations where the amount of data is relatively large. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 is a schematic diagram of a data export method for a resource management system according to an embodiment of the present disclosure;

[0027] Figure 2 is a schematic diagram of another data export method of a resource management system according to an embodiment of the present disclosure;

[0028] Figure 3 is a schematic diagram of a system startup mapping according to an embodiment of the present disclosure;

[0029] Figure 4 is a schematic diagram of another data export method of a resource management system according to an embodiment of the present disclosure;

[0030] Figure 5 is a schematic diagram of another data export method of a resource management system according to an embodiment of the present disclosure;

[0031] Figure 6 is a schematic diagram of another data export method of a resource management system according to an embodiment of the present disclosure;

[0032] Figure 7 is a schematic diagram of a data export device of a resource management system according to an embodiment of the present disclosure;

[0033] Figure 8 is a schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0035] Figure 1 A schematic diagram of an exemplary implementation of a data export method for a resource management system proposed in the present disclosure is shown as follows: Figure 1 As shown, the data export method of the resource management system includes the following steps:

[0036] S101, obtaining a mapping relationship between a first data table to be exported and a system column name of a resource management system for which data needs to be exported, and a mapping relationship between standard column names corresponding to the resource management system.

[0037] The data export of the resource management system of the embodiment of the present application can be applied to the scenario of reading the data of the resource management system. For example, the scenario can be to export the data of the resource management system of the pharmaceutical business site. The execution subject of the data export of the resource management system of the embodiment of the present application can be the data export device of the resource management system of the embodiment of the present application, and the device can be set on an electronic device.

[0038] In the embodiment of the present disclosure, the first data table is pre-set, and the data table can be set by the user according to the data requirements actually exported, or it can be a standard data table module in the system. The first data table may include multiple data columns, and different data columns are used to store different data. For example, the data columns may include name, purpose, amount, etc. The user can select some or all of the data columns to form the first data table according to their own needs.

[0039] It should be noted that, since the resource management system may include multiple preset system tables, the system column name mapping relationship may include multiple mappings to correspond to the system tables. For example, the system tables may include financial tables, warehouse entry and exit tables, and the like.

[0040] The system column name mapping relationship is pre-set, and is a mapping relationship between the system's preset column names and the column names input by the user. The system column name mapping relationship can be stored in the storage space of the electronic device for easy retrieval and use during use.

[0041] It should be noted that the system column name mapping relationship corresponding to different systems may be different, and no limitation is made here. The specific needs depend on the actual situation.

[0042] The standard column name mapping relationship is pre-set and calibrated in this solution. The standard column name mapping relationship can be changed according to actual design needs, and no limitation is made here.

[0043] S102: based on the system column name mapping relationship, convert the column names of the first data table into system column names to obtain a second data table.

[0044] It should be noted that after the column names of the first data table are converted into system column names, the column names in the second data table already have the preset rules in the data table in the resource management system. In this way, the data table required by the user can be converted into the system data table that needs to be obtained, thereby realizing data acquisition for different systems.

[0045] At the same time, by converting the first data table into a second data table that can be recognized by the resource management system, data export from different resource management systems can be achieved.

[0046] S103: based on the standard column name mapping relationship, convert the column names of the second data table into standard column names to obtain a third data table.

[0047] It should be noted that based on the standard column name mapping relationship, all data can be converted into a standard data table to unify the data tables of different systems into a standard data table, which is convenient for subsequent identification, aggregation, analysis and other steps and can save the cost of subsequent data processing.

[0048] S104: Based on the third data table, export data from the resource management system to generate a target data table.

[0049] In the disclosed embodiment, firstly, the system column name mapping relationship between the first data table to be exported and the resource management system to which the data needs to be exported, as well as the standard column name mapping relationship corresponding to the resource management system are obtained, and then based on the system column name mapping relationship, the column names of the first data table are converted into system column names to obtain the second data table, and then based on the standard column name mapping relationship, the column names of the second data table are converted into standard column names to obtain the third data table, and finally based on the third data table, the data is exported from the resource management system to generate the target data table. In this way, by obtaining the first data table that the user needs to export and converting it into the second data table that the system can recognize, data export from different resource management systems can be realized, and finally converted into a third data table of unified standards, which is convenient for subsequent identification, aggregation, analysis and other steps, can save the cost of subsequent data processing, and is suitable for situations where the amount of data is relatively large.

[0050] In the above embodiment, based on the third data table, before exporting data from the resource management system to generate the target data table, the following steps are also included: Figure 2 The steps shown are as follows Figure 2 As shown:

[0051] S201, obtaining a system startup map, where the system startup map is a mapping relationship between system information, a driver, and a dialect.

[0052] In implementation, different resource management systems may correspond to different resource management systems and dialects. Therefore, when acquiring data for different resource management systems, it is first necessary to determine the system driver and dialect corresponding to the current resource management system.

[0053] It should be noted that the system startup mapping is a mapping relationship between system information, driver program and dialect. Different resource management systems may correspond to different system startup relationships, which is not limited here.

[0054] The system information is the identification information of the resource management system. The system information of different resource management systems may be different or the same, depending on the actual situation. However, in the same resource management system, there is only one system information.

[0055] Taking the pharmaceutical industry as an example, suppose there is a pharmaceutical manufacturer YC1, which sells a drug M1 to pharmacies across the country. Each pharmacy has its own inventory management software, namely ERP, to manage inventory. The ERP software used by each pharmacy may not be the same, and the corresponding system startup mapping may also be different.

[0056] The mapping relationship between system information, driver program and dialect can be a one-to-one mapping relationship or a many-to-many mapping relationship, which is not limited here. Figure 3 As shown, the system information corresponding to resource management system A is relational database management system (MySQL), the corresponding driver is component object model (COM) mysql, Java database connection (JDBC), driver driver, the dialect is generic top-level domain name (Organizations, org), object-relational mapping framework hibernate, dialect dialect, database dialect MySQL5dialect, and the system information corresponding to resource management system B is relational database management system (Structured Query Language server, SQLserver), the corresponding driver is COM, Microsoft Microsoft, SQL server, JDBC, relational database management system driver (Structured Query Language server, SQL server driver, SQLServerDriver). The system information corresponding to resource management system C is Oracle, the corresponding driver is oracle, JDBC, driver, Oracle driver OracleDriver, and the corresponding dialect is org, hibernate, dialect, Oracle dialect Oracle10gDialect.

[0057] S202: Based on the system information of the resource management system, determine a matching target driver and target dialect from a system startup mapping.

[0058] In the embodiment of the present disclosure, after obtaining the system information of the resource management system, the system information can be matched with the system information in the system startup map to determine that the dialect and driver corresponding to the successfully matched system information are the target dialect and target driver. Figure 3 As shown, there can be multiple target dialects and target drivers.

[0059] S203, starting the resource management system based on the target driver and the target dialect.

[0060] In the disclosed embodiment, the system startup map is first obtained, which is a mapping relationship between system information, driver and dialect. Then, based on the system information of the resource management system, the target driver and target dialect that match it are determined from the system startup map. Finally, the resource management system is started based on the target driver and target dialect. By setting the system startup map, different resource management systems can be started, providing a basis for realizing data reading of different resource management systems.

[0061] In an embodiment of the present disclosure, a data adaptation layer may be set, and the data adaptation layer may include the system startup mapping in the above embodiment. When starting the resource management system, the data adaptation layer may start the resource management system by calling the system startup mapping, obtaining the target driver and the target dialect.

[0062] It should be noted that, in some implementations, only the data of a single user or certain users need to be exported. In the summary of the embodiments of the present disclosure, the user information in the third data table can be obtained, and then based on the user information, user data matching the user information is exported from the resource management system, and finally the user data is imported into the third user table to generate a target data table.

[0063] It should be noted that the user information in the third data table may be the user's verification information, identity identification, etc., and no limitation is made here.

[0064] In the above embodiment, the first data table to be exported can be obtained by Figure 4 Explaining further, the method includes:

[0065] S401, obtaining the input column name to be exported.

[0066] In the embodiment of the present disclosure, the column name to be exported may be input by the user or generated by the system by default, and no limitation is made here, and the specific limitation may be made according to actual design requirements.

[0067] Optionally, a table or text for which data needs to be exported may be provided by the user, and the table or text may be analyzed to determine the column names to be exported.

[0068] Take the pharmaceutical industry as an example. Suppose there is a pharmaceutical manufacturer, YC1, which sells a drug, M1, to pharmacies across the country. Now it is necessary to summarize the sales of M1. Then it is necessary to formulate a column name to be exported in advance to achieve unified data acquisition. For example, the column name to be exported may include primary key, sales code, product number, sales quantity, sales price, sales amount, etc.

[0069] S402: Arrange the column names to be exported to obtain a first data table.

[0070] There are many ways to arrange the column names to be exported, which are not limited here and can be set according to actual needs.

[0071] In some implementations, in order to facilitate users to browse and understand the table, a sorting priority may be set for the column names to be exported. For example, the sequence number may have the highest priority, followed by the name, and so on.

[0072] In the embodiment of the present disclosure, the priority of the column names to be exported can be first obtained, and then the column names to be exported are arranged in descending order based on the priority to obtain the first data table. The priority is set in advance and can be set according to the actual needs of the user, and no limitation is made here.

[0073] In the above embodiment, based on the system column name mapping relationship, the column name of the first data table is converted into the system column name to obtain the second data table, and the second data table can also be obtained by Figure 5 Explaining further, the method includes:

[0074] S501: Obtain the data type of the data to be exported in the first data table.

[0075] In the embodiments of the present disclosure, the data types may be multiple. For example, taking the pharmaceutical industry as an example, the data types may include pharmacy income tables, warehouse in and out tables, drug sales tables, etc., without any limitation here.

[0076] S502: Based on the data type, determine a first column name conversion rule that matches the data type from a system column name mapping relationship.

[0077] It should be noted that the conversion rules corresponding to data tables of different data types may be different. For example, the column name to be exported in the first data table may include "quantity", the column name corresponding to the sales volume may be "amount", and the column name corresponding to the in-and-out warehouse table may be "number of pieces". Therefore, it is necessary to determine the first column name conversion rule that matches the data type.

[0078] S503: Based on the first column name conversion rule, convert the column names of the first data table into system column names to obtain a second data table.

[0079] In the disclosed embodiment, the data type of the data to be exported in the first data table is first obtained, and then based on the data type, a first column name conversion rule matching the data type is determined from the system column name mapping relationship, and finally based on the first column name conversion rule, the column name of the first data table is converted into a system column name to obtain the second data table. In this way, by setting different conversion rules in the system column name mapping relationship and determining the conversion rules based on the data type, the first data table is converted into a second data table that meets the resource management system standard.

[0080] In the implementation, due to different language habits and styles of users, conversion is performed for different column names. It is required that the system column name in the first column name conversion rule has corresponding multiple first candidate column names, and then the column name of the first data table is matched with the second candidate column name. In response to a successful match, the system column name corresponding to the successfully matched candidate column name is determined to be the system column name that needs to be converted.

[0081] It should be noted that there are multiple first candidate column names corresponding to the system column names which are preset in advance and can be updated and replaced according to the user's design needs, and no limitation is made here.

[0082] In the above embodiment, based on the standard column name mapping relationship, the column names of the second data table are converted into standard column names to obtain the third data table. Figure 6 Explaining further, the method includes:

[0083] S601: Based on the data type, determine a second column name conversion rule matching the data type from a system column name mapping relationship.

[0084] In implementation, different resource management systems may have different corresponding system column names. Therefore, when converting the data table, a second column name conversion rule matching the data type is determined from the system column name mapping relationship. For example, the column name to be exported in the second data table may include "quantity", and the corresponding column name in resource management system A may be "amount", and the corresponding column name in resource management system B may be "number of items". Therefore, it is necessary to determine a second column name conversion rule matching the data type.

[0085] S602: Based on the second column name conversion rule, convert the column names of the second data table into standard column names to obtain a third data table.

[0086] In an embodiment of the present disclosure, in response to a system column name corresponding to multiple second candidate column names in the second column name conversion rule, the column names of the second data table are matched with the candidate column names, and in response to a successful match, the standard column names corresponding to the successfully matched candidate column names are determined to be the standard column names that need to be converted.

[0087] In a possible implementation of the present disclosure, taking drug sales statistics as an example, the drugstores that need to be counted can be first determined, and for any of the drugstores, the resource management system used by the drugstore is obtained, and then based on the type of the resource management system, the system column name mapping relationship between the first data table to be exported and the resource management system that needs to export data, and the standard column name mapping relationship corresponding to the resource management system are obtained, and then based on the system column name mapping relationship, the column name of the first data table is converted into the system column name to obtain the second data table, and then based on the standard column name mapping relationship, the column name of the second data table is converted into the standard column name to obtain the third data table, and based on the third data table, the data is exported from the resource management system to generate a target data table. The target data tables of all drugstores are obtained and summarized to obtain the drug sales data. In this way, the sales data of drugstores in different resource management systems are exported and finally converted into a third data table of unified standards, which can improve the efficiency and accuracy of statistics, reduce the cost of data processing, and is suitable for situations where the amount of data is relatively large.

[0088] Corresponding to the data export methods for resource management systems provided in the above-mentioned embodiments, an embodiment of the present disclosure further provides a data export device for a resource management system. Since the data export device for a resource management system provided in the embodiment of the present disclosure corresponds to the data export methods for resource management systems provided in the above-mentioned embodiments, the implementation methods of the data export methods for the above-mentioned resource management systems are also applicable to the data export device for a resource management system provided in the embodiment of the present disclosure, and will not be described in detail in the following embodiments.

[0089] Figure 7 A schematic diagram of a data export device for a resource management system proposed in the present disclosure, such as Figure 7 As shown, the data export device 700 of the resource management system includes: an acquisition module 710, a first conversion module 720, a second conversion module 730 and a generation module 740.

[0090] The acquisition module 710 is used to acquire the mapping relationship between the first data table to be exported and the system column name of the resource management system whose data needs to be exported, and the standard column name mapping relationship corresponding to the resource management system.

[0091] The first conversion module 720 is used to convert the column names of the first data table into system column names based on the system column name mapping relationship to obtain the second data table.

[0092] The second conversion module 730 is used to convert the column names of the second data table into standard column names based on the standard column name mapping relationship to obtain a third data table.

[0093] The generating module 740 is used to export data from the resource management system based on the third data table to generate a target data table.

[0094] In one embodiment of the present disclosure, the generation module 740 is also used to: obtain a system startup map, which is a mapping relationship between system information, drivers, and dialects; based on the system information of the resource management system, determine the target driver and target dialect that match it from the system startup map; and start the resource management system based on the target driver and target dialect.

[0095] In one embodiment of the present disclosure, the generation module 740 is also used to: obtain user information in the third data table; based on the user information, export user data matching the user information from the resource management system; and import the user data into the third user table to generate a target data table.

[0096] In one embodiment of the present disclosure, the acquisition module 710 is further used to: acquire input column names to be exported; and arrange the column names to be exported to acquire a first data table.

[0097] In one embodiment of the present disclosure, the acquisition module 710 is further used to: acquire the priority of the column names to be exported; and arrange the column names to be exported in descending order of priority to acquire the first data table.

[0098] In one embodiment of the present disclosure, the first conversion module 720 is also used to: obtain the data type of the data to be exported in the first data table; based on the data type, determine a first column name conversion rule that matches the data type from the system column name mapping relationship; based on the first column name conversion rule, convert the column name of the first data table into a system column name to obtain a second data table.

[0099] In one embodiment of the present disclosure, the first conversion module 720 is further used to: in response to a system column name corresponding to multiple first candidate column names in the first column name conversion rule, match the column name of the first data table with the candidate column name; in response to a successful match, determine that the system column name corresponding to the successfully matched candidate column name is the system column name that needs to be converted.

[0100] In one embodiment of the present disclosure, the second conversion module is also used to: based on the data type, determine a second column name conversion rule that matches the data type from the system column name mapping relationship; based on the second column name conversion rule, convert the column name of the second data table into a standard column name to obtain a third data table.

[0101] In one embodiment of the present disclosure, the second conversion module is also used to: in response to the system column name corresponding to multiple second candidate column names in the second column name conversion rule, match the column name of the second data table with the candidate column name; in response to a successful match, determine that the standard column name corresponding to the successfully matched candidate column name is the standard column name that needs to be converted.

[0102] By obtaining the first data table that the user needs to export and converting it into a second data table that the system can recognize, data export from different resource management systems can be achieved, and finally converted into a third data table with unified standards, which is convenient for subsequent identification, aggregation, analysis and other steps, and can save the cost of subsequent data processing.

[0103] In order to implement the above embodiment, the present disclosure also provides an electronic device 800, such as Figure 8 As shown, the electronic device 800 includes: a processor 801 and a memory 802 communicatively connected to the processor, the memory 802 stores instructions executable by at least one processor, and the instructions are executed by at least one processor 801 to implement a data export method for a resource management system as in the first aspect of the embodiment of the present disclosure.

[0104] In order to implement the above embodiments, the embodiments of the present disclosure also propose a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to implement a data export method for a resource management system as in the first aspect of the embodiments of the present disclosure.

[0105] In order to implement the above embodiments, the embodiments of the present disclosure further propose a computer program product, including a computer program, which, when executed by a processor, implements the data export method of the resource management system as in the first aspect of the embodiments of the present disclosure.

[0106] In the description of the present disclosure, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present disclosure and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be understood as a limitation on the present disclosure.

[0107] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present disclosure, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0108] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0109] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.

Claims

1. A data export method for a resource management system, characterized in that: include: Obtaining a mapping relationship between a first data table to be exported and a system column name of a resource management system for which data needs to be exported, and a mapping relationship between standard column names corresponding to the resource management system; Based on the system column name mapping relationship, the column names of the first data table are converted into system column names to obtain a second data table; Based on the standard column name mapping relationship, the column names of the second data table are converted into standard column names to obtain a third data table; Based on the third data table, data is exported from the resource management system to generate a target data table.

2. The method according to claim 1, characterized in that Before the method of exporting data from the resource management system based on the third data table to generate a target data table, the method further includes: Obtaining a system startup map, wherein the system startup map is a mapping relationship between system information, a driver, and a dialect; Based on the system information of the resource management system, determining a target driver and a target dialect matching the system from the system startup mapping; The resource management system is started based on the target driver and the target dialect.

3. The method according to claim 2, characterized in that The step of exporting data from the resource management system based on the third data table to generate a target data table includes: Acquire user information in the third data table; Based on the user information, exporting user data matching the user information from the resource management system; The user data is imported into the third user table to generate the target data table.

4. The method according to claim 1, characterized in that: The step of obtaining a first data table to be exported includes: Get the input column name to be exported; The to-be-exported column names are arranged to obtain the first data table.

5. The method according to claim 4, characterized in that: The step of arranging the to-be-derived column names to obtain the first data table includes: Obtaining the priority of the column name to be exported; The to-be-derived column names are arranged based on the order of the priorities from large to small to obtain the first data table.

6. The method according to claim 1, characterized in that The converting the column names of the first data table into system column names based on the system column name mapping relationship to obtain the second data table includes: Obtain the data type of the data to be exported from the first data table; Based on the data type, determining a first column name conversion rule matching the data type from the system column name mapping relationship; Based on the first column name conversion rule, the column names of the first data table are converted into system column names to obtain the second data table.

7. The method according to claim 6, characterized in that The converting the column names of the first data table into system column names based on the system column name mapping relationship to obtain the second data table includes: In response to the system column name corresponding to a plurality of first candidate column names in the first column name conversion rule, matching the column name of the first data table with the first candidate column names; In response to a successful match, the system column name corresponding to the successfully matched candidate column name is determined to be the system column name that needs to be converted.

8. The method according to claim 6, characterized in that The converting the column names of the second data table into standard column names based on the standard column name mapping relationship to obtain a third data table includes: Based on the data type, determining a second column name conversion rule matching the data type from the system column name mapping relationship; Based on the second column name conversion rule, the column names of the second data table are converted into standard column names to obtain the third data table.

9. The method according to claim 8, characterized in that The method further comprises: In response to the system column name corresponding to a plurality of second candidate column names in the second column name conversion rule, matching the column name of the second data table with the candidate column names; In response to a successful match, the standard column name corresponding to the successfully matched second candidate column name is determined to be the standard column name that needs to be converted.

10. A data export device for a resource management system, characterized in that: include: An acquisition module, used to acquire a mapping relationship between a first data table to be exported and a system column name of a resource management system for which data needs to be exported, and a mapping relationship between a standard column name corresponding to the resource management system; A first conversion module, configured to convert the column names of the first data table into system column names based on the system column name mapping relationship to obtain a second data table; A second conversion module, configured to convert the column names of the second data table into standard column names based on the standard column name mapping relationship, so as to obtain a third data table; A generating module is used to export data from the resource management system based on the third data table to generate a target data table.

11. An electronic device, characterized in that: Including memory and processor; The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the method according to any one of claims 1 to 9.

12. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-9.

Images