Cascading plug-ins, data sharing methods, devices and electronic equipment

Abstract

This application proposes a cascading plug-in, a data sharing method, an apparatus, and an electronic device, relating to the field of big data technology. The cascading plug-in is connected to a first system and at least one second system for cascading between the first system and at least one second system. The plug-in is used to acquire data resources from the first system and / or the second system, and to send corresponding data resources to any system in response to a data resource request. Thus, by responding to a data resource request from any system and sending corresponding data resources to that system, the cascading plug-in reduces the impact of different second systems on the first system and lowers the complexity of data resource sharing.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to a cascading plug-in, a data sharing method, an apparatus, and an electronic device. Background Technology

[0002] In cross-regional or cross-departmental scenarios, or between different data sharing and interaction systems, data resources will be connected, i.e., data resources will be shared.

[0003] Because different manufacturers have different data sharing and interaction systems, when sharing data resources with different second systems (third-party systems), the first system (local system) needs to constantly modify the interface method. As the number of second systems increases, the complexity of sharing data resources with different second systems also increases. How to reduce the impact of different second systems on the first system and reduce the complexity of data resource sharing is something that needs to be considered. Summary of the Invention

[0004] A first aspect of this application provides a cascading plug-in, which is connected to a first system and at least one second system for cascading between the first system and at least one second system; the plug-in is used to obtain data resources from the first system and / or the second system, and to send corresponding data resources to the arbitrary system in response to a data resource request from any system.

[0005] The cascading plug-in of this application embodiment connects to a first system and at least one second system. By obtaining data resources from the first system and / or the second system, and responding to data resource requests from any system, it sends the corresponding data resources to any system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing.

[0006] A second aspect of this application provides a data sharing method, comprising: acquiring data resources of a first system and / or at least one second system; and sending corresponding data resources to the arbitrary system in response to a data resource request from any system; wherein the arbitrary system is either the first system or the second system.

[0007] The data sharing method of this application embodiment acquires data resources from a first system and / or at least one second system; in response to a data resource request from any system, the corresponding data resources are sent to the arbitrary system; wherein, the arbitrary system is either the first system or the second system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing.

[0008] A third aspect of this application provides a data sharing apparatus, comprising: a first acquisition module for acquiring data resources of a first system and / or at least one second system; and a first transmission module for transmitting corresponding data resources to the arbitrary system in response to a data resource request from the arbitrary system; wherein the arbitrary system is either the first system or the second system.

[0009] The data sharing device of this application embodiment acquires data resources from a first system and / or at least one second system; in response to a data resource request from any system, it sends the corresponding data resources to the any system; wherein, the any system is either the first system or the second system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing.

[0010] A fourth aspect of this application provides an electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the data sharing method as described in the second aspect.

[0011] The fifth aspect of this application provides a non-transitory computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the data sharing method as described in the second aspect.

[0012] The technical solutions provided in this application have the following beneficial effects:

[0013] The cascading plug-in connects to a first system and at least one second system for cascading between the first system and at least one second system. The plug-in is used to acquire data resources from the first system and / or the second system, and to send corresponding data resources to any system in response to a data resource request. Thus, by responding to a data resource request from any system and sending corresponding data resources to that system, the cascading plug-in reduces the impact of different second systems on the first system and lowers the complexity of data resource sharing.

[0014] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0015] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0016] Figure 1 This is a schematic diagram of the structure of a cascaded plug-in provided in an embodiment of this application;

[0017] Figure 2A flowchart illustrating a data sharing method provided in an embodiment of this application;

[0018] Figure 3 A flowchart illustrating another data sharing method provided in an embodiment of this application;

[0019] Figure 4 A schematic diagram of the format-converted data resources to be shared provided in an embodiment of this application;

[0020] Figure 5 This application provides a schematic diagram illustrating the process of sharing data resources of the first system with the second system in an embodiment of the present application.

[0021] Figure 6 A flowchart illustrating another data sharing method provided in an embodiment of this application;

[0022] Figure 7 A flowchart illustrating another data sharing method provided in an embodiment of this application;

[0023] Figure 8 This application provides a schematic diagram illustrating the process of sharing data resources of the second system with the first system in an embodiment of the present application.

[0024] Figure 9 A flowchart illustrating another data sharing method provided in an embodiment of this application;

[0025] Figure 10 A flowchart illustrating another data sharing method provided in an embodiment of this application;

[0026] Figure 11 This is a schematic diagram of the structure of a data sharing device according to an embodiment of this application;

[0027] Figure 12 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0028] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0029] This application provides a cascading plug-in, a data sharing method, an apparatus, and an electronic device.

[0030] The following is combined with Figure 1 This application provides a detailed description of the cascading plugins provided.

[0031] Figure 1This is a schematic diagram of the structure of a cascaded plug-in provided in an embodiment of this application.

[0032] The cascading plug-in 101 is connected to the first system 102 and at least one second system 103 for cascading between the first system 102 and at least one second system 103; the plug-in (cascading plug-in) 101 is used to obtain data resources from the first system 102 and / or the second system 103, and to send the corresponding data resources to the arbitrary system in response to a data resource request from any system.

[0033] In some embodiments, any system can be either a first system 102 or a second system 103. That is, in response to a data resource request from the first system 102, the corresponding data resource is sent to the first system 102, or in response to a data resource request from the second system 103, the corresponding data resource is sent to the second system 103.

[0034] The first system 102 can be a local system, and the second system 103 can be a third-party system. There can be multiple third-party systems and multiple data resources, which are not specifically limited here.

[0035] In some embodiments, the cascading plug-in 101 can obtain data resources from the first system 102 and / or at least one second system 103 at preset time intervals via a timer, that is, call the interface of the first system 102 and / or at least one second system 103 at preset time intervals to obtain data resources of the first system 102 and / or at least one second system 103.

[0036] The preset time period can be 10 minutes or 15 minutes; there is no specific limitation here, and it can be set according to actual needs.

[0037] In some embodiments, the plug-in 101 includes a main plug-in 1011 and at least one sub-plugin 1012; the main plug-in 1011 is connected to a first system 102 for transmitting data resources with the first system 102; the sub-plugin 1012 is connected to a corresponding second system 103 for transmitting data resources with the second system 103.

[0038] Different second systems 103 correspond to different sub-plugins 1012, and different sub-plugins 1012 transmit the acquired data resources to the corresponding second system 103.

[0039] In some embodiments, the main plugin 1011 is provided with a front-end interface for displaying the data resources of the first system 102; the main plugin 1011, in response to the data resource request of the second system 103, selects the data resources to be shared from the displayed data resources of the first system 102 and transmits them to the corresponding sub-plugin 1012 of the second system 103; the sub-plugin 1012 converts the data resources to be shared according to the target data resource format of the second system 103 and sends the converted data resources to be shared to the second system 103.

[0040] Different data resources can have different data resource formats. That is, the data resource format of the data resource of the first system 102 can be different from the data resource format of at least one second system 103, and the data resource formats of the data resources of at least one second system 103 can be different.

[0041] In some embodiments, the main plugin 1011 can display the data resources of the first system 102 on the corresponding front-end interface according to the data resource format of the first system 102.

[0042] In some embodiments, the sub-plugin 1012 is provided with a front-end page for displaying the data resources of the second system 103 corresponding to the sub-plugin 1012; the sub-plugin 1012, in response to the data resource request of the first system 102, selects the data resource to be shared from the displayed data resources of the second system 103; the sub-plugin 1012, according to the target data resource format of the first system 102, performs format conversion on the data resource to be shared, and transmits the format-converted data resource to be shared to the first system 102 through the main plug-in 1011.

[0043] In some embodiments, the sub-plugin 1012 can display the data resources of the second system 103 on the corresponding front-end interface according to the data resource format of the second system 103.

[0044] In some embodiments, the sub-plugin 1012 is provided with a front-end page for displaying the data resources of the second system 103 corresponding to the sub-plugin 1012; the sub-plugin 1012, in response to a data resource request from another second system 103, selects a data resource to be shared from the displayed data resources of the second system 103; the sub-plugin 1012, according to the target data resource format of the other second system 103, performs format conversion on the data resource to be shared, and transmits the format-converted data resource to be shared to the other second system 103 through the sub-plugin 1012 corresponding to the other second system 103.

[0045] In some embodiments, plug-in 101 is connected to database 104; plug-in 101 is used to store data resources transmitted between the first system 102 and / or the second system 103 into database 104.

[0046] The data resource format of the data resources stored in the database 104 can be the data resource format of the first system 102 or at least the data resource format of the second system 103, without specific limitations here.

[0047] The cascading plug-in of this application embodiment is connected to a first system and at least one second system for cascading between the first system and at least one second system. The plug-in is used to obtain data resources from the first system and / or the second system, and to send corresponding data resources to any system in response to a data resource request. Thus, by responding to a data resource request from any system and sending corresponding data resources to any system, the cascading plug-in reduces the impact of different second systems on the first system and lowers the complexity of data resource sharing.

[0048] Figure 2 This is a flowchart illustrating a data sharing method provided in an embodiment of this application.

[0049] The execution subject of this application embodiment is the data sharing device provided in this application. The data sharing device in this application can be configured in the software of an electronic device, such as a cascade plug-in, to perform data sharing functions. The execution subject of this application embodiment is described using a cascade plug-in as an example.

[0050] like Figure 2 As shown, the data sharing method includes the following steps:

[0051] Step 201: Obtain data resources from the first system and / or at least one second system.

[0052] The first system can be a local system, and the second system can be a third-party system. There can be multiple third-party systems and multiple data resources, which are not specifically limited here.

[0053] Different data resources can have different data resource formats. That is, the data resource format of the data resource of the first system can be different from the data resource format of at least one second system, and the data resource formats of the data resources of at least one second system can be different.

[0054] In some embodiments, the cascading plug-in can obtain data resources from the first system and / or at least one second system at preset time intervals via a timer, that is, call the interface of the first system and / or at least one second system at preset time intervals to obtain data resources from the first system and / or at least one second system.

[0055] The preset time period can be 10 minutes or 15 minutes; there is no specific limitation here, and it can be set according to actual needs.

[0056] Step 202: In response to a data resource request from any system, send the corresponding data resource to the system; wherein, the system is either the first system or the second system.

[0057] In some embodiments, the cascading plug-in may respond to a data resource request from the first system by sending the corresponding data resource to the first system, or it may respond to a data resource request from at least one second system by sending the corresponding data resource to at least one second system.

[0058] The data sharing method provided in this application involves acquiring data resources from a first system and / or at least one second system; and sending corresponding data resources to any system in response to a data resource request from any system, wherein any system is either the first system or the second system. Thus, the cascading plug-in, in response to a data resource request from any system, sends corresponding data resources to that system, thereby reducing the impact of different second systems on the first system and lowering the complexity of data resource sharing.

[0059] In the above embodiments, data resources transmitted between the first system and / or the second system obtained through the cascading plug-in can be stored in the database.

[0060] The data resource format stored in the database can be the data resource format of the first system or at least the data resource format of the second system; no specific limitation is made here.

[0061] To clearly illustrate how to respond to a data resource request from any system and send the corresponding data resources to that system, embodiments of this application provide a possible implementation.

[0062] Figure 3 This is a flowchart illustrating another data sharing method provided in an embodiment of this application. Figure 3 As shown, the above method may include the following steps:

[0063] Step 301: Obtain data resources from the first system and / or at least one second system.

[0064] It should be noted that the execution process of step 301 can be found in the relevant description in the above embodiments, and will not be repeated here.

[0065] Step 302: In response to a data resource request from the second system or other second systems, obtain the target data resource format, wherein the target data resource format is the data resource format of the second system or other second systems.

[0066] The target resource format can include target category, target directory, and target resource, where the target resource can include file resource, library table resource, and interface resource.

[0067] Step 303: Perform format conversion processing on the data resources to be shared selected from the data resources of the first system according to the target data resource format to obtain the format-converted data resources to be shared.

[0068] In some embodiments, the cascading plugin can select a data resource from the data resources of the first system as the data resource to be shared.

[0069] In some embodiments, the process of the cascading plug-in performing format conversion on the data resource to be shared can be as follows: Based on a category query mapping table, obtain the target category corresponding to the category in the mapping table, wherein the mapping table includes the mapping relationship between the target category and the category; when the field description content under the category is inconsistent with the target field description content under the target category, convert the field description content to the target field description content to obtain the format-converted data resource to be shared; or, when the field under the category is inconsistent with the target field under the target category, determine the new field to be added compared to the target field, and add the new field to the field to obtain the format-converted data resource to be shared.

[0070] The fields under a category can include: category name, level, and description; newly added fields can be, for example, detection; the description of a field may differ from that of the target field, for example, the description of a field may be "level" while the description of the target field may be "level".

[0071] Therefore, based on the mapping relationship between target category and category in the mapping relationship table, the target category of the data resource format of the data resource to be shared in the first system can be determined, corresponding to the target category of the data resource format of the second system or other second systems. Inconsistent field descriptions and fields can be converted into consistent field descriptions and fields, thereby realizing the format conversion of the data resource to be shared.

[0072] In some embodiments, the process of the cascading plugin performing format conversion on the data resource to be shared can also be as follows: when the field description content under the category is consistent with the target field description content under the target category, the target directory corresponding to the directory in the mapping relationship table is obtained according to the directory query, wherein the mapping relationship table includes the mapping relationship between the target directory and the directory; when the field description content under the directory is inconsistent with the target field description content under the target directory, the field description content is converted to the target field description content to obtain the data resource to be shared after format conversion; or, when the field under the directory is inconsistent with the target field under the target directory, the newly added field compared to the target field is determined, and the newly added field is added to the field to obtain the data resource to be shared after format conversion.

[0073] The fields under the directory can include: directory name, directory description, directory type, directory data items, etc.; newly added fields can be, for example, the directory update time; the field description content is inconsistent with the target field description content, for example, the field description content is type, while the target field description content is category.

[0074] Therefore, based on the mapping relationship between target directories and directories in the mapping relationship table, the target directory of the data resource format of the data resource to be shared in the first system can be determined, corresponding to the data resource format of the second system or other second systems. Inconsistent field descriptions and fields can be converted into consistent field descriptions and fields, thereby realizing the format conversion of the data resource to be shared.

[0075] In some embodiments, the process of the cascading plugin performing format conversion on the shared data resource can also be as follows: when the field description content in the directory is consistent with the target field description content in the target directory, the target resource corresponding to the resource in the resource query mapping table is obtained, wherein the mapping table includes the mapping relationship between the target resource and the resource; and the resource and the target resource are attached to the attachment position of the target resource.

[0076] Therefore, based on the mapping relationship between target resources and resources in the mapping relationship table, the target resource of the second system or other second system corresponding to the data resource format of the data resource to be shared in the first system can be determined. The resource and the target resource are attached to the attachment position of the target resource to realize the format conversion of the data resource to be shared, that is, to realize the merging of the data resource to be shared in the first system and the target resource of the second system or other second system.

[0077] The mapping table can be pre-defined, and different mapping tables can be used for different systems. That is to say, the mapping table between the first system and different second systems can be different.

[0078] The schematic diagram of the data resource to be shared after format conversion can be shown as follows: Figure 4 As shown, in Figure 4 In the context of categories, third-party extended attributes can be new fields added to the target fields compared to the fields under the category; similarly, third-party extended attributes can be new fields added to the target directories compared to the fields under the directories; and local file resources...

[0079] This refers to file resources in a second system or other second-system applications. Third-party file resources refer to file resources in the first system. Local interface resources refer to interface resources in a second system or other second-system applications. Third-party interface resources refer to...

[0080] The interface resources of the first system.

[0081] Step 304: Send the format-converted data resources to be shared to the second system or other second systems.

[0082] The data sharing method in this application embodiment obtains data resources from a first system and / or at least one second system.

[0083] Source; In response to a data resource request from a second system or other second system, obtain the target data resource format, wherein the target data resource format is the data resource format of the second system or other second system; According to the target data resource format

[0084] The data resources selected from the data resources of the first system are converted into shared data resources in a different format. These converted data resources are then sent to the second system or other second systems. Thus, the cascading plugin responds to data resource requests from any system by sending the corresponding data resources to that system, thereby reducing the impact of different second systems on the first system and lowering the complexity of data resource sharing.

[0085] For example, Figure 5 The process for sharing data resources of the first system with the second system provided in the embodiments of this application

[0086] Schematic diagram, as follows Figure 5 As shown, the main plugin in the cascading plugin system acquires data resources from the first system and stores them in the database. In response to data resource requests from the second system, the sub-plugins acquire the data resource format from the second system. Sub-plugins can call the main plugin's interface to obtain the data resources to be shared and format them according to the target data resource format.

[0087] The conversion process yields the format-converted data resources to be shared, which are then sent to the second system.

[0088] Figure 6 This is a flowchart illustrating another data sharing method provided in an embodiment of this application. Figure 6 As shown, the above method may include the following steps:

[0089] Step 601: Obtain data resources from the first system and / or at least one second system.

[0090] The first system can be a local system, and the second system can be a third-party system. The cascading plugin includes a main plugin connected to the first system and sub-plugins connected to the second system. In other words, the cascading plugin includes plugins connected to the local system.

[0091] The main plugin and sub-plugins that connect to third-party systems.

[0092] The main plugin can interact with the local system to obtain data resources from the local system; the sub-plugins can interact with third-party systems to obtain data resources from the third-party system.

[0093] In some embodiments, when the main plugin interacts with the local system, the interfaces provided by the local system are typically basic and general interfaces. These interfaces may include: interfaces for creating, deleting, modifying, and querying directories; interfaces for creating, deleting, modifying, and querying interface resources; interfaces for creating, deleting, modifying, and querying file resources; interfaces for creating, deleting, modifying, and querying library and table resources; and interfaces for applying for and approving data resources.

[0094] The number of third-party systems and data resources can be multiple, and no specific limit is set here.

[0095] Step 602: Display and process the data resources of the first system on the front-end page corresponding to the main plugin.

[0096] In some embodiments, after acquiring data resources from the first system, the main plugin in a cascading plugin displays the acquired data resources on its corresponding front-end page, allowing objects to select data resources to be shared. A diagram illustrating the data resource display process can be shown below. Figure 5 As shown.

[0097] The data resources displayed on the front-end page corresponding to the main plugin are in the data resource format of the first system.

[0098] Step 603: Select a data resource from the data resources displayed on the front-end interface corresponding to the main plugin, and use it as the data resource to be shared in the first system.

[0099] In some embodiments, the cascading plugin obtains the operation of the object on the front-end page corresponding to the main plugin; in response to the object's operation on the front-end page corresponding to the main plugin being a specified operation, it selects a data resource from the data resources displayed on the front-end interface corresponding to the main plugin as the data resource to be shared in the first system.

[0100] The specified operation can be clicking the report button or clicking the select button; no specific limitations are specified here. The data resource to be shared can be one or more data resources displayed on the front-end page corresponding to the main plugin; no specific limitations are specified here.

[0101] Therefore, responding to the operation of the object on the front-end page corresponding to the main plugin is a specified operation, selecting data resources from the displayed data resources as the data resources to be shared, taking into account the needs of different objects, and the object's experience is better.

[0102] Step 604: In response to a data resource request from any system, send the corresponding data resource to the any system; wherein, any system is either the first system or the second system.

[0103] It should be noted that the execution process of step 604 can be found in the relevant description in the above embodiments, and will not be repeated here.

[0104] The data sharing method of this application embodiment acquires data resources from a first system and / or at least one second system; displays the data resources of the first system on the front-end page corresponding to the main plugin; selects data resources from the data resources displayed on the front-end interface corresponding to the main plugin as the data resources to be shared by the first system; and sends the corresponding data resources to any system in response to a data resource request; wherein, any system is either the first system or the second system. Thus, the cascading plugin responds to a data resource request from any system by sending the corresponding data resources to that system, thereby reducing the impact of different second systems on the first system and lowering the complexity of data resource sharing.

[0105] To clearly illustrate how to respond to a data resource request from any system and send the corresponding data resources to that system, embodiments of this application provide a possible implementation.

[0106] Figure 7 This is a flowchart illustrating another data sharing method provided in an embodiment of this application. Figure 7 As shown, the above method may include the following steps:

[0107] Step 701: Obtain data resources from the first system and / or at least one second system.

[0108] The first system can be a local system, and the second system can be a third-party system.

[0109] Step 702: In response to the data resource request of the first system, obtain the target data resource format, wherein the target data resource format is the data resource format of the first system.

[0110] The target resource format can include target category, target directory, and target resource, where target resource can include file resource, library table resource, and interface resource.

[0111] Step 703: Perform format conversion processing on the data resources to be shared selected from the data resources of the second system or other second systems according to the target data resource format to obtain the format-converted data resources to be shared.

[0112] 0 In some embodiments, the cascading plug-in can select data from data resources of a second system or other second systems.

[0113] Resources, as data resources to be shared.

[0114] In some embodiments, the process of the cascading plug-in performing format conversion on the shared data resource can be as follows: querying a mapping relationship table based on categories to obtain the target category corresponding to the category in the mapping relationship table, wherein the mapping relationship table includes...

[0115] The mapping relationship between target categories and categories; when the field description content under a category is inconsistent with the target field description content 5 under the target category, the field description content is converted into the target field description content to obtain the format-converted data resource to be shared;

[0116] Alternatively, when the fields under a category are inconsistent with the target fields under the target category, determine the new fields to be added compared to the target fields, and add the new fields to the fields to obtain the format-converted data resources to be shared.

[0117] The fields under a category can include: category name, level, and description; a new field could be, for example, detection.

[0118] The field description content is inconsistent with the target field description content. For example, the field description content is "level" while the target field description content is "hierarchy".

[0119] Therefore, based on the mapping relationship between the target category and the category in the mapping relationship table, the target category of the data resource format of the data resource to be shared in the second system or other second systems can be determined, and the inconsistent field description content and fields can be converted into consistent field description content and fields, thereby realizing the format conversion of the data resource to be shared.

[0120] 5. In some embodiments, the process of the cascading plug-in performing format conversion on the shared data resource can also be as follows:

[0121] When the field description under a category matches the target field description under the target category, the mapping table is queried to obtain the target directory corresponding to the directory in the mapping table. The mapping table includes the mapping relationship between target directories and directories. When the field description under a directory does not match the target field description under the target directory, the field...

[0122] The description content is converted into the target field description content to obtain the format-converted data resource to be shared; or, if the field in directory 0 is inconsistent with the target field in the target directory, the new field compared to the target field is determined, and the field is added to the target field.

[0123] Add a new field to obtain the formatted data resources to be shared.

[0124] The fields under the directory can include: directory name, directory description, directory type, directory data items, etc.; a newly added field can be, for example, the directory update time; the field description content is inconsistent with the target field description content, for example, the field description content is category, while the target field description content is type.

[0125] Therefore, based on the mapping relationship between the target directory and the directory in the mapping relationship table, the target directory of the data resource format of the data resource to be shared in the second system or other second systems can be determined, and the inconsistent field description content and fields can be converted into consistent field description content and fields, thereby realizing the format conversion of the data resource to be shared.

[0126] In some embodiments, the process of the cascading plugin performing format conversion on the shared data resource can also be as follows: when the field description content in the directory is consistent with the target field description content in the target directory, the target resource corresponding to the resource in the resource query mapping table is obtained, wherein the mapping table includes the mapping relationship between the target resource and the resource; and the resource and the target resource are attached to the attachment position of the target resource.

[0127] Therefore, based on the mapping relationship between target resources and resources in the mapping relationship table, the target resource of the first system can be determined corresponding to the data resource format of the data resource to be shared in the second system or other second systems. The resource and the target resource are then attached to the attachment position of the target resource to realize the format conversion of the data resource to be shared, that is, to realize the merging of the data resource to be shared in the second system or other second systems and the target resource of the first system.

[0128] The mapping table can be pre-defined, and different mapping tables can be used for different systems. In other words, the mapping tables between the first system and different second systems can be different.

[0129] The diagram of the data resource to be shared after format conversion can still be shown as follows: Figure 4 As shown, in Figure 4 In the text, the third-party extended attributes corresponding to the category can be new fields added to the target fields under the target category compared to the fields under the category. The third-party extended attributes corresponding to the directory can be new fields added to the target directory compared to the fields under the directory. Local file resources refer to file resources of the first system, and third-party file resources refer to file resources of the second system or other second systems. Local interface resources refer to interface resources of the first system, and third-party interface resources refer to interface resources of the second system or other second systems.

[0130] Step 704: Send the format-converted data resources to be shared to the first system.

[0131] In some embodiments, there is a need for a third system, such as a district / county level system. When the third system initiates a data resource request, the first system (city level system) can send the data resources to be shared after format conversion to the district / county level system. That is, the first system and the second system (province level system) or other second systems with unified data resource format send the data resources to be shared to the district / county level system.

[0132] The data sharing method of this application embodiment involves: acquiring data resources from a first system and / or at least one second system; responding to a data resource request from the first system, acquiring a target data resource format, wherein the target data resource format is the data resource format of the first system; performing format conversion processing on the data resources to be shared selected from the data resources of the second system or other second systems according to the target data resource format to obtain the format-converted data resources to be shared; and sending the format-converted data resources to be shared to the first system. Thus, the cascading plug-in responds to data resource requests from any system and sends the corresponding data resources to any system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing. Furthermore, by uniformly distributing the format-converted data resources from the second system and the data resources from the first system to the third system, the third system avoids receiving data resources in multiple formats.

[0133] For example, Figure 8 This is a schematic diagram illustrating the process of sharing data resources of the second system with the first system, as provided in an embodiment of this application. Figure 8As shown, the sub-plugin in the cascaded plugin obtains data resources from the second system and stores them in the database. In response to the data resource request from the first system, the sub-plugin obtains the data resource format of the first system, performs format conversion processing on the data resource to be shared according to the target data resource format, obtains the format-converted data resource to be shared, and sends the format-converted data resource to be shared to the first system through the main plugin.

[0134] Figure 9 This is a flowchart illustrating another data sharing method provided in an embodiment of this application. Figure 9 As shown, the above method may include the following steps:

[0135] Step 901: Obtain data resources from the first system and / or at least one second system.

[0136] The first system can be a local system, and the second system can be a third-party system. The cascading plugin includes a main plugin connected to the first system and a sub-plugin connected to the second system. In other words, the cascading plugin includes a main plugin connected to the local system and a sub-plugin connected to the third-party system.

[0137] The main plugin can interact with the local system to obtain data resources from the local system; the sub-plugins can interact with third-party systems to obtain data resources from the third-party system.

[0138] In some embodiments, when the main plugin interacts with the local system, the interfaces provided by the local system are typically basic and general interfaces. These interfaces may include: interfaces for creating, deleting, modifying, and querying directories; interfaces for creating, deleting, modifying, and querying interface resources; interfaces for creating, deleting, modifying, and querying file resources; interfaces for creating, deleting, modifying, and querying library and table resources; and interfaces for applying for and approving data resources.

[0139] The number of third-party systems and data resources can be multiple, and no specific limit is set here.

[0140] Step 902: Display and process the data resources of the second system on the front-end page corresponding to the sub-plugin.

[0141] In some embodiments, after a sub-plugin in a cascading plugin acquires data resources from the second system, it displays the acquired data resources on the corresponding front-end page of the sub-plugin, so that objects can select data resources to be shared. A schematic diagram of the data resource display process can be shown as follows: Figure 8 As shown.

[0142] The data resource format displayed on the front-end page corresponding to the sub-plugin is the data resource format of the second system. There can be multiple second systems and multiple data resource formats.

[0143] Therefore, based on the fields returned by the sub-plugin backend, the acquired data resources are displayed on the front-end interface to adapt to different data resource formats of the second system and improve flexibility.

[0144] Step 903: Select a data resource from the data resources displayed on the front-end interface corresponding to the sub-plugin, and use it as the data resource to be shared in the second system.

[0145] In some embodiments, the cascading plugin obtains the operation of the object on the front-end page corresponding to the child plugin; in response to the object's operation on the front-end page corresponding to the child plugin being a specified operation, it selects a data resource from the data resources displayed on the front-end interface corresponding to the child plugin as the data resource to be shared by the second system.

[0146] The specified operation can be clicking the report button or clicking the select button; no specific limitation is made here. The data resource to be shared can be one or more data resources displayed on the front-end page corresponding to the sub-plugin; no specific limitation is made here.

[0147] Therefore, in response to the specified operation of the object on the front-end page corresponding to the sub-plugin, the data resource is selected from the displayed data resources as the data resource to be shared, taking into account the needs of different objects, and the object's experience is better.

[0148] In some embodiments, a sub-plugin in a cascading plugin can send an application notification for shared data resources to the second system based on the shared data resources of the second system; upon receiving an approval notification corresponding to the application notification, it displays the applied shared data resources of the second system to the object so that the object can use the shared data resources.

[0149] Step 904: In response to a data resource request from any system, send the corresponding data resource to the any system; wherein, any system is either the first system or the second system.

[0150] It should be noted that the execution process of step 904 can be found in the relevant description in the above embodiments, and will not be repeated here.

[0151] The data sharing method of this application embodiment involves: acquiring data resources from a first system and / or at least one second system; displaying the data resources of the first system on the front-end page corresponding to the sub-plugin; selecting data resources from the data resources displayed on the front-end interface corresponding to the sub-plugin as data resources to be shared by the second system; and sending the corresponding data resources to the arbitrary system in response to a data resource request from any system, wherein the arbitrary system is either the first system or the second system. Thus, the cascading plug-in responds to a data resource request from any system by sending the corresponding data resources to that system, thereby reducing the impact of different second systems on the first system and lowering the complexity of data resource sharing.

[0152] Figure 10 This is a flowchart illustrating another data sharing method provided in an embodiment of this application. Figure 10 As shown, the above method may include the following steps:

[0153] Step 1001: Obtain data resources from the first system and / or at least one second system.

[0154] In some embodiments, the main plugin in the cascaded plugin calls the interface of the first system at preset time intervals to obtain data resources of the first system; the sub-plugin in the cascaded plugin calls the interface of at least one second system at preset time intervals to obtain data resources of at least one second system.

[0155] Step 1002: Display and process the data resources on the front-end pages corresponding to the main plugin and sub-plugins.

[0156] In some embodiments, the data resources of the first system are displayed on the front-end page corresponding to the main plugin; and the data resources of the corresponding second system are displayed on the front-end page corresponding to the sub-plugin.

[0157] Step 1003: Select data resources from the data resources displayed on the front-end interface corresponding to the main plugin and sub-plugins, as the data resources to be shared by the first system and / or at least one second system.

[0158] In some embodiments, data resources are selected from the data resources displayed on the front-end page corresponding to the main plugin as the data resources to be shared in the first system; data resources are selected from the data resources displayed on the front-end page corresponding to the sub-plugin as the data resources to be shared in the second system.

[0159] Step 1004: In response to a data resource request from any system, obtain the target data resource format.

[0160] In some embodiments, in response to a data resource request from a first system, the data resource format of the first system is obtained as the target data resource format; in response to a data resource request from a second system or another second system, the data resource format of the second system or another second system is obtained as the target data resource format.

[0161] Step 1005: Perform format conversion processing on the data resource to be shared according to the target data resource format to obtain the format-converted data resource to be shared.

[0162] In some embodiments, the data resources to be shared in the second system or other second systems are converted according to the target data resource format to obtain the converted data resources to be shared; the data resources to be shared in the first system are converted according to the target data resource format to obtain the converted data resources to be shared.

[0163] It should be noted that the specific process of format conversion can be found in the relevant content of the above embodiments, and will not be described in detail here.

[0164] Step 1006: Send the format-converted data resources to be shared to any system.

[0165] In some embodiments, the format-converted data resources to be shared can be sent to a first system, a second system, or another second system.

[0166] In some embodiments, the first system may send the data resources to be shared by the first system and the second system or other second systems in a unified data resource format to a lower-level system, such as a district or county-level system.

[0167] The data sharing method of this application embodiment involves: acquiring data resources from a first system and / or at least one second system; displaying the data resources on the front-end pages corresponding to the main plugin and sub-plugins; selecting data resources from the data resources displayed on the front-end interfaces corresponding to the main plugin and sub-plugins as data resources to be shared by the first system and / or at least one second system; responding to a data resource request from any system by acquiring a target data resource format; performing format conversion processing on the data resources to be shared according to the target data resource format to obtain format-converted data resources to be shared; and sending the format-converted data resources to be shared to any system. Thus, the cascading plugin responds to a data resource request from any system by sending the corresponding data resources to that system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing. Furthermore, by uniformly distributing the format-converted data resources from the second system and the data resources from the first system to the third system, lower-level systems avoid receiving data resources in multiple formats.

[0168] Corresponding to the data sharing methods provided in the above embodiments, one embodiment of this application also provides a data sharing device. Since the data sharing device provided in this embodiment corresponds to the data sharing methods provided in the above embodiments, the implementation methods of the data sharing methods are also applicable to the data sharing device provided in this embodiment, and will not be described in detail here.

[0169] Figure 11 This is a schematic diagram of the structure of a data sharing device according to an embodiment of this application.

[0170] like Figure 11 As shown, the data sharing device 1100 may include: a first acquisition module 1110 and a first transmission module 1120.

[0171] The first acquisition module 1110 is used to acquire data resources of a first system and / or at least one second system; the first sending module 1120 is used to send corresponding data resources to any system in response to a data resource request from any system; wherein, the arbitrary system is the first system or the second system.

[0172] As another possible implementation of this application embodiment, the first sending module 1120 is specifically used to: in response to a data resource request from the second system or other second systems, obtain a target data resource format, wherein the target data resource format is the data resource format of the second system or other second systems; perform format conversion processing on the data resources to be shared selected from the data resources of the first system according to the target data resource format to obtain the format-converted data resources to be shared; and send the format-converted data resources to be shared to the second system or other second systems.

[0173] As another possible implementation of this application embodiment, the target resource format includes a target category, a target directory, and a target resource. The first sending module 1120 is specifically used to: query a mapping relationship table according to the category to obtain the target category corresponding to the category in the mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the target category and the category; when the field description content under the category is inconsistent with the target field description content under the target category, convert the field description content to the target field description content to obtain the format-converted data resource to be shared; or, when the field under the category is inconsistent with the target field under the target category, determine the new field of the target field compared to the field, and add the new field to the field to obtain the format-converted data resource to be shared.

[0174] As another possible implementation of this application embodiment, the device further includes: a first processing module and a second processing module. The first processing module is configured to, when the field description content under the category is consistent with the target field description content under the target category, query the mapping relationship table according to the directory to obtain the target directory corresponding to the directory in the mapping relationship table, wherein the mapping relationship table includes the mapping relationship between the target directory and the directory; the second processing module is configured to, when the field description content under the directory is inconsistent with the target field description content under the target directory, convert the field description content into the target field description content to obtain the format-converted data resource to be shared; or, when the field under the directory is inconsistent with the target field under the target directory, determine the new field added to the target field compared to the field, and add the new field to the field to obtain the format-converted data resource to be shared.

[0175] As another possible implementation of this application embodiment, the device further includes: a third processing module and a first attaching module. The third processing module is used to query the mapping relationship table according to the resource when the field description content under the directory is consistent with the target field description content under the target directory, and obtain the target resource corresponding to the resource in the mapping relationship table, wherein the mapping relationship table includes the mapping relationship between the target resource and the resource; the attaching module is used to attach the resource and the target resource to the attachment position of the target resource.

[0176] As another possible implementation of this application embodiment, the device further includes: a first display module and a first selection module, wherein the first display module is used to display and process the data resources of the first system on the front-end page corresponding to the main plugin; and the first selection module is used to select data resources from the data resources displayed on the front-end interface corresponding to the main plugin as the data resources to be shared by the first system.

[0177] As another possible implementation of this application, the first selection module is specifically used to: obtain the operation of the object on the front-end page corresponding to the main plugin; and, in response to the operation of the object on the front-end page corresponding to the main plugin being a specified operation, select data resources from the data resources displayed on the front-end interface corresponding to the main plugin as the data resources to be shared by the first system.

[0178] As another possible implementation of this application embodiment, the first sending module 1120 is specifically used to: in response to a data resource request from the first system, obtain a target data resource format, wherein the target data resource format is the data resource format of the first system; perform format conversion processing on the data resources to be shared selected from the data resources of the second system or other second systems according to the target data resource format to obtain the format-converted data resources to be shared; and send the format-converted data resources to be shared to the first system.

[0179] As another possible implementation of this application embodiment, the target resource format includes a target category, a target directory, and a target resource. The first sending module 1120 is specifically used to: query a mapping relationship table according to the category to obtain the target category corresponding to the category in the mapping relationship table, wherein the mapping relationship table includes the mapping relationship between the target category and the category; when the field description content under the category is inconsistent with the target field description content under the target category, convert the field description content to the target field description content to obtain the format-converted data resource to be shared; or, when the field under the category is inconsistent with the target field under the target category, determine the new field of the target field compared to the field, and add the new field to the field to obtain the format-converted data resource to be shared.

[0180] As another possible implementation of this application embodiment, the device further includes: a fourth processing module and a fifth processing module. The fourth processing module is used to, when the field description content under the category is consistent with the target field description content under the target category, retrieve the target directory corresponding to the directory in the directory query mapping relationship table, wherein the mapping relationship table includes the mapping relationship between the target directory and the directory. The fifth processing module is used to, when the field description content under the directory is inconsistent with the target field description content under the target directory, convert the field description content to the target field description content to obtain the format-converted data resource to be shared; or, when the field under the directory is inconsistent with the target field under the target directory, determine the new field of the target field compared to the field, add the new field to the field, and obtain the format-converted data resource to be shared.

[0181] As another possible implementation of this application embodiment, the device further includes: a sixth processing module and a second attaching module. The sixth processing module is used to obtain the target resource corresponding to the resource by querying the mapping relationship table according to the resource when the field description content under the directory is consistent with the target field description content under the target directory. The mapping relationship table includes the mapping relationship between the target resource and the resource. The second attaching module is used to attach the resource and the target resource to the attachment position of the target resource.

[0182] As another possible implementation of this application embodiment, the second display module and the second selection module are configured to display the data resources of the second system on the front-end page corresponding to the sub-plugin; the second selection module is configured to select data resources from the data resources displayed on the front-end interface corresponding to the sub-plugin as the data resources to be shared by the second system.

[0183] As another possible implementation of this application, the second selection module is specifically used to: obtain the operation of the object on the front-end page corresponding to the sub-plugin; and, in response to the operation of the object on the front-end page corresponding to the sub-plugin being a specified operation, select data resources from the data resources displayed on the front-end interface corresponding to the sub-plugin as the data resources to be shared by the second system.

[0184] As another possible implementation of this application embodiment, the device further includes: a second sending module and a third display module. The second sending module is used to send an application notification for the data resources to be shared to the second system according to the data resources to be shared in the second system. The third display module is used to display the applied data resources to be shared in the second system to the object when receiving the approval notification corresponding to the application notification.

[0185] As another possible implementation of this application embodiment, the device further includes: a storage module, used to store the data resources transmitted between the first system and / or the second system obtained through the plug-in into a database.

[0186] The data sharing apparatus of this application embodiment acquires data resources from a first system and / or at least one second system; in response to a data resource request from any system, it sends the corresponding data resources to the any system; wherein, any system is either the first system or the second system, thereby reducing the impact of different second systems on the first system and reducing the complexity of data resource sharing.

[0187] To achieve the above embodiments, this application also proposes an electronic device. Figure 12This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device includes:

[0188] The memory 1201, the processor 1202, and the computer program stored on the memory 1201 and executable on the processor 1202.

[0189] When the processor 1202 executes the program, it implements the data sharing method provided in the above embodiments.

[0190] Furthermore, electronic devices also include:

[0191] Communication interface 1203 is used for communication between memory 1201 and processor 1202.

[0192] The memory 1201 is used to store computer programs that can run on the processor 1202.

[0193] The memory 1201 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0194] The processor 1202 is used to implement the data sharing method described in the above embodiments when executing the program.

[0195] If the memory 1201, processor 1202, and communication interface 1203 are implemented independently, then the communication interface 1203, memory 1201, and processor 1202 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 12 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0196] Optionally, in a specific implementation, if the memory 1201, processor 1202, and communication interface 1203 are integrated on a single chip, then the memory 1201, processor 1202, and communication interface 1203 can communicate with each other through an internal interface.

[0197] The processor 1202 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0198] To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the data sharing method provided in the above embodiments.

[0199] To implement the above embodiments, this application also proposes a computer program product that, when executed by an instruction processor, implements the data sharing method provided in the above embodiments.

[0200] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0201] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0202] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0203] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0204] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0205] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0206] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0207] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A cascading plug-in, characterized by, The plug-in is connected with a first system and at least one second system, and is used for cascading between the first system and the at least one second system; The plug-in is used for acquiring data resources from the first system and / or the second system, and sending corresponding data resources to any system in response to a data resource request of the any system; The plug-in comprises a main plug-in and at least one sub-plug-in; The main plug-in is connected with the first system, and is used for transmitting data resources with the first system; The sub-plug-in is connected with a corresponding second system, and is used for transmitting data resources with the second system; The main plug-in is provided with a front-end interface, and is used for displaying data resources of the first system; The main plug-in selects to-be-shared data resources from the displayed data resources of the first system in response to a data resource request of the second system, and transmits the to-be-shared data resources to a corresponding sub-plug-in of the second system; The sub-plug-in performs format conversion on the to-be-shared data resources according to a target data resource format of the second system, and sends the format-converted to-be-shared data resources to the second system; The sub-plug-in is provided with a front-end page, and is used for displaying data resources of the second system corresponding to the sub-plug-in; The sub-plug-in selects to-be-shared data resources from the displayed data resources of the second system in response to a data resource request of the first system; The sub-plug-in performs format conversion on the to-be-shared data resources according to a target data resource format of the first system, and transmits the format-converted to-be-shared data resources to the first system through the main plug-in.

2. The cascade plug-in of claim 1, wherein, The sub-plug-in is provided with a front-end page, and is used for displaying data resources of the second system corresponding to the sub-plug-in; The sub-plug-in selects to-be-shared data resources from the displayed data resources of the second system in response to a data resource request of another second system; The sub-plug-in performs format conversion on the to-be-shared data resources according to a target data resource format of the another second system, and transmits the format-converted to-be-shared data resources to the another second system through a corresponding sub-plug-in of the another second system.

3. The cascade plug-in of any of claims 1 to 2, wherein, The plug-in is connected with a database; The plug-in is used for storing data resources transmitted between the first system and / or the second system into the database.

4. A data sharing method characterized by, The application is applied to the cascaded plug-in of claim 1, and comprises: acquiring data resources of a first system and / or at least one second system; sending corresponding data resources to any system in response to a data resource request of the any system, wherein the any system is the first system or the second system.

5. The method of claim 4, wherein, The sending of the corresponding data resources to the any system in response to the data resource request of the any system comprises: acquiring a target data resource format in response to a data resource request of the second system or another second system, wherein the target data resource format is a data resource format of the second system or the another second system; performing format conversion on to-be-shared data resources selected from data resources of the first system according to the target data resource format, to obtain format-converted to-be-shared data resources; and Send the format-converted data resource to be shared to the second system or other second system.

6. The method of claim 5, wherein, The target resource format includes a target category, a target directory, and a target resource. The format conversion processing of the selected data resource to be shared from the data resource of the first system according to the target data resource format includes: According to the category query mapping relationship table, the target category corresponding to the category in the mapping relationship table is obtained, wherein the mapping relationship table includes the mapping relationship between the target category and the category. When the field description content under the category is inconsistent with the target field description content under the target category, the field description content is converted into the target field description content to obtain the format-converted data resource to be shared. Or, When the field under the category is inconsistent with the target field under the target category, the added field of the target field compared with the field is determined, and the added field is added to the field to obtain the format-converted data resource to be shared.

7. The method of claim 6, wherein, The method further includes: When the field description content under the category is consistent with the target field description content under the target category, the target directory corresponding to the directory in the mapping relationship table is obtained according to the directory query, wherein the mapping relationship table includes the mapping relationship between the target directory and the directory. When the field description content under the directory is inconsistent with the target field description content under the target directory, the field description content is converted into the target field description content to obtain the format-converted data resource to be shared. Or, When the field under the directory is inconsistent with the target field under the target directory, the added field of the target field compared with the field is determined, and the added field is added to the field to obtain the format-converted data resource to be shared.

8. The method of claim 7, wherein, The method further includes: When the field description content under the directory is consistent with the target field description content under the target directory, the target resource corresponding to the resource in the mapping relationship table is obtained according to the resource query, wherein the mapping relationship table includes the mapping relationship between the target resource and the resource. The resource and the target resource are hung on the hanging position of the target resource.

9. The method of claim 4, wherein, The cascade plug-in includes a main plug-in connected with the first system and a sub-plug-in connected with the second system. After the data resource of the first system is obtained, the method further includes: Display processing of the data resource of the first system is performed on the front-end page corresponding to the main plug-in. Select the data resource from the data resource displayed on the front-end interface corresponding to the main plug-in as the data resource to be shared of the first system.

10. The method of claim 9, wherein, The method of selecting the data resource from the data resource displayed on the front-end interface corresponding to the main plug-in as the data resource to be shared of the first system includes: Obtain the operation of the object on the front-end page corresponding to the main plug-in. In response to the object's operation on the front-end page corresponding to the main plug-in being a specified operation, a data resource is selected from data resources displayed on the front-end interface corresponding to the main plug-in as a data resource to be shared by the first system.

11. The method of claim 4, wherein, The sending of the corresponding data resource to the arbitrary system in response to the data resource request of the arbitrary system comprises: In response to the data resource request of the first system, a target data resource format is acquired, wherein the target data resource format is a data resource format of the first system; The data resource to be shared selected from the data resource of the second system or other second system is subjected to format conversion processing according to the target data resource format, to obtain a format-converted data resource to be shared; The format-converted data resource to be shared is sent to the first system.

12. The method of claim 11, wherein, The target resource format comprises a target classification, a target directory, and a target resource, and the format conversion processing of the data resource to be shared selected from the data resource of the second system or other second system according to the target data resource format comprises: According to a classification query mapping relationship table, a target classification corresponding to the classification in the mapping relationship table is acquired, wherein the mapping relationship table comprises a mapping relationship between a target classification and a classification; When field description content under the classification is inconsistent with target field description content under the target classification, the field description content is converted into the target field description content, to obtain a format-converted data resource to be shared; Or, When a field under the classification is inconsistent with a target field under the target classification, an added field of the target field compared with the field is determined, and the added field is added to the field, to obtain a format-converted data resource to be shared.

13. The method of claim 12, wherein, The method further comprises: When the field description content under the classification is consistent with the target field description content under the target classification, a target directory corresponding to the directory in the mapping relationship table is acquired according to a directory query mapping relationship table, wherein the mapping relationship table comprises a mapping relationship between a target directory and a directory; When field description content under the directory is inconsistent with target field description content under the target directory, the field description content is converted into the target field description content, to obtain a format-converted data resource to be shared; Or, When a field under the directory is inconsistent with a target field under the target directory, an added field of the target field compared with the field is determined, and the added field is added to the field, to obtain a format-converted data resource to be shared.

14. The method of claim 13, wherein, The method further comprises: When the field description content under the directory is consistent with the target field description content under the target directory, the target resource corresponding to the resource is acquired according to the mapping relationship table, wherein the mapping relationship table comprises a mapping relationship between a target resource and a resource; The resource and the target resource are hung on a hanging position of the target resource.

15. The method of claim 4, wherein, The cascade plug-in comprises a main plug-in connected with the first system and a sub-plug-in connected with the second system, and further comprises the following steps after the data resource of the second system is acquired: performing display processing on the data resource of the second system on the front-end page corresponding to the sub-plug-in; selecting a data resource from the data resource displayed on the front-end interface corresponding to the sub-plug-in as the to-be-shared data resource of the second system.

16. The method of claim 15, wherein, The step of selecting a data resource from the data resource displayed on the front-end interface corresponding to the sub-plug-in as the to-be-shared data resource of the second system comprises the following steps: acquiring an operation of an object on the front-end page corresponding to the sub-plug-in; in response to the operation of the object on the front-end page corresponding to the sub-plug-in being a specified operation, selecting a data resource from the data resource displayed on the front-end interface corresponding to the sub-plug-in as the to-be-shared data resource of the second system.

17. The method of claim 16, wherein, The method further comprises the following steps: sending an application notification of the to-be-shared data resource of the second system to the second system according to the to-be-shared data resource of the second system; when an audit pass notification corresponding to the application notification is received, displaying the to-be-shared data resource of the second system applied by the object.

18. The method of claim 4, wherein, The method further comprises the following steps: storing the data resource transmitted between the first system and / or the second system through the plug-in into a database.

19. A data sharing apparatus, comprising: The cascade plug-in according to claim 1 comprises the following steps: a first acquisition module is configured to acquire data resources of a first system and / or at least one second system; a first sending module is configured to send corresponding data resources to an arbitrary system in response to a data resource request of the arbitrary system, wherein the arbitrary system is the first system or the second system.

20. An electronic device, comprising: The cascade plug-in comprises the following steps: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the data sharing method according to any one of claims 4-19 when executing the program.

21. A non-transitory computer-readable storage medium having stored thereon a computer program, wherein, The program is executed by the processor to implement the data sharing method according to any one of claims 4-19.

22. A computer program product, characterised in that, The computer program is executed by the processor of the electronic device to enable the electronic device to perform the data sharing method according to any one of claims 4-19.

Images