WO2018000395A1

WO2018000395A1 - Method and apparatus for managing data

Info

Publication number: WO2018000395A1
Application number: PCT/CN2016/088038
Authority: WO
Inventors: 吴庭满
Original assignee: 华为技术有限公司
Priority date: 2016-06-30
Filing date: 2016-06-30
Publication date: 2018-01-04

Abstract

A method and apparatus for managing data, which can enable a user to adjust a logical relationship between data according to his/her own requirements. The method comprises: acquiring a plurality of pieces of metadata (210); based on a first user operation, determining at least one piece of main data from the plurality of pieces of metadata (220); based on a second user operation, determining at least one piece of tail data from the plurality of pieces of metadata, and designating a mapping relationship between the at least one piece of tail data and the at least one piece of main data (230); recording the mapping relationship between the main data and the tail data (240); and when a data request carrying indication information about the main data is received, determining the tail data according to the main data and the mapping relationship (250).

Description

Method and apparatus for managing data

Technical field

The present invention relates to the field of human resource management and, more particularly, to a method of managing data.

Background technique

In today's enterprises, the learning development management module in the human resource management system needs to manage a lot of data, for example, the positions, capabilities, and skills of the employees. Different companies have different understandings of the data that needs to be managed. Therefore, the business logic of management data of different management systems also has large differences.

In the prior art, the business logic of the human resource management system is usually created by the R&D technician after data analysis through programming, data structure definition, etc., for data management. Users cannot adjust the logic between data according to their needs.

Summary of the invention

The present application provides a method and apparatus for managing data, which enables a user to adjust the logical relationship between data according to his or her own needs.

In a first aspect, the present application provides a method for managing data, the method comprising: acquiring a plurality of metadata; determining at least one master data from the plurality of metadata based on a first user operation; and based on a second user operation, Determining at least one tail data from the plurality of metadata, and designating a mapping relationship between the at least one tail data and the at least one main data; recording a mapping relationship between the main data and the tail data; When receiving the data request carrying the identifier of the primary data, determining the tail data according to the primary data and the mapping relationship.

In a possible implementation, before determining at least one tail data from the plurality of metadata based on the second user operation, the method further includes: presenting a management interface, where the management interface includes the first area and a second area, the identifier of the at least one primary data is presented in the first area, and an identifier of a plurality of candidate metadata in the plurality of metadata is presented in the second area; and the Two user operations, determining at least one tail data from the plurality of metadata, including: determining the at least one tail data from the plurality of candidate metadata based on a second user operation, and at the first An identifier of the at least one tail data is presented in the area.

In a possible implementation manner, the second user operation includes dragging an identifier of the tail data from the second area to the first area.

In a possible implementation, determining, according to a third user operation, at least one slave data from the plurality of metadata, and designating a first mapping relationship between the at least one slave data and the at least one master data; And determining, based on the second user operation, the at least one tail data from the plurality of metadata, including: determining at least one tail data from the plurality of metadata based on the second user operation, and designating the at least one tail data And a second mapping relationship between the at least one slave data; and the recording a mapping relationship between the master data and the tail data, including: recording a relationship between the master data and the slave data a mapping relationship, and recording a second mapping relationship between the slave data and the tail data; when receiving the data request carrying the identifier of the master data, according to the master data and the mapping Relationship, determining tail data, including: when receiving the data request carrying the identifier of the master data and the identifier of the slave data, according to the master data, the slave data, the first Mapping relationship and the second mapping relation to determine the end of data.

In a possible implementation, before determining at least one slave data from the plurality of metadata based on a third user operation, the method further includes: presenting a management interface, where the management interface includes the first region and a second area, the identifier of the at least one primary data is presented in the first area, and an identifier of a plurality of candidate metadata in the plurality of metadata is presented in the second area; and the The three-user operation, determining the at least one slave data from the plurality of metadata, including: determining the at least one slave data from the plurality of candidate metadata based on a third user operation, and at the first An identifier of the at least one slave data is presented in the area.

In a possible implementation, determining, according to the second user operation, the at least one tail data from the plurality of metadata, including: determining, according to the second user operation, the plurality of candidate metadata At least one tail data and presenting an identification of the at least one tail data in the first area.

In a possible implementation manner, the second user operation includes dragging the identifier of the tail data from the second area to the first area, and associating the identifier of the tail data to the identifier of the at least one slave data. To specify a mapping relationship between the at least one tail data and at least one of the slave data.

In a possible implementation manner, the third operation includes dragging the identification of the slave data from the second area to the first area.

In a possible implementation manner, the primary data is at least two, and the at least two primary data belong to N data structures, N≥2, and the presentation management interface includes: Determining N pages of the data structure, wherein the N data structures are in one-to-one correspondence with the N pages, and each page is used to present an identifier of the main data in the corresponding data structure; The first area presents a page label of the N pages, and at least one of the N pages is presented in the first area.

In a possible implementation, the presenting at least one of the N pages in the first area, including: according to data attribute information of each of the at least two pieces of main data, from the Determining at least one first main data in the at least two main data, wherein the data attribute information of the first main data satisfies a preset condition; and at least one of the N pages is presented in the first area, The main page is a page for presenting the first main data.

In a second aspect, the present application provides an apparatus for managing data for performing the method of the first aspect or any possible implementation of the first aspect. In particular the apparatus comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.

In a third aspect, the present application provides an apparatus for managing data, the apparatus comprising a processor, a display, a memory, a network interface, and a bus system, wherein the processor, the display, the memory, and the network interface are connected to each other through a bus system. The memory is for storing instructions for executing the memory stored instructions, and when the instructions are executed, the processor performs the method of the first aspect or any possible implementation of the first aspect through the network interface.

In a fourth aspect, the present application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.

The method and apparatus for managing data provided by the present application enable a user to adjust data according to his own needs by selecting primary data and tail data, and specifying a mapping relationship between the primary data and the tail data. Between the logical relationship.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

1 is a schematic diagram of a computer system of a method and apparatus for managing data suitable for use in an embodiment of the present invention.

2 is an example of common business logic of a human resource management system in the prior art.

FIG. 3 is a schematic flowchart of a method of managing data according to an embodiment of the present invention.

4 is a schematic diagram of user-defined metadata and business logic in accordance with an embodiment of the present invention.

FIG. 5 is a schematic diagram of a management interface according to an embodiment of the present invention.

6 is an example of an interaction design of a method of managing data according to an embodiment of the present invention.

7 is another example of interaction design of a method of managing data in accordance with an embodiment of the present invention.

FIG. 8 is still another example of interaction design of a method of managing data according to an embodiment of the present invention.

9 is a schematic architectural diagram of a method of managing data in accordance with an embodiment of the present invention.

FIG. 10 is an illustration of a method of managing data in accordance with an embodiment of the present invention.

11 is a schematic structural diagram of an apparatus for managing data according to an embodiment of the present invention.

FIG. 12 is a schematic structural diagram of an apparatus for managing data according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope should fall within the scope of the present invention.

The method, device and device for managing data provided by the embodiments of the present invention can be applied to a computer, which includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.

The operating system may be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.

The application layer includes applications such as browsers, contacts, word processing software, and instant messaging software.

In addition, in the embodiment of the present invention, the computer may be a handheld device such as a smart phone, or may be a terminal device such as a personal computer, and the present invention is not particularly limited as long as the method for recording the compressed data of the embodiment of the present invention can be operated. The program of the code may process the data in a method of compressing data according to an embodiment of the present invention. The execution body of the method for managing data according to the embodiment of the present invention may be a computer device or a functional module of the computer device capable of calling a program and executing the program.

Moreover, various aspects or features of the present invention can be implemented as a method, apparatus, or using standard programming And/or engineering products. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or media. For example, the computer readable medium may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape), and an optical disk (eg, a CD (Compact Disc), a DVD (Digital Versatile Disc). Etc.), smart cards and flash memory devices (eg, EPROM (Erasable Programmable Read-Only Memory), cards, sticks or key drivers, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, without limitation, a wireless channel and various other mediums capable of storing, containing, and/or carrying instructions and/or data.

Hereinafter, the structure of a computer system (specifically, a hardware layer of a computer system) of an embodiment of the present invention will be exemplarily described with reference to FIG.

1 is a schematic diagram of a computer system 100 to which a method of managing data in accordance with an embodiment of the present invention is applied. As shown in Figure 1, the system 100 includes:

At least one processor 110;

At least one memory 120;

At least one display 130;

The processor 110, the memory 120, and the display 130 are communicatively coupled.

In the embodiment of the present invention, a communication interface is disposed in the processor 110, a communication interface is disposed in the memory 120, and a communication interface is disposed in the display 130, so that the processor 110, the memory 120, and the display 130 can communicate through the communication interface.

In the embodiment of the present invention, the processor 110 and the memory 120 and the display 130 may be configured in the same device. In this case, by way of example and not limitation, the computer system 100 may further include a bus 140, and the processor 110 may communicate via An interface is coupled to the bus 140, which may be coupled to the bus 140 via a communication interface, and the display 130 may be coupled to the bus 140 via a communication interface. Thus, the processor 110, the memory 120, and the display 130 can implement a communication connection through the bus 140. The bus 140 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. In this case, the communication interface of the processor 110 may be a communication interface between devices within the computer device. Similarly, the communication interface of the memory 120 and the display 130 may be a communication interface between devices within the computer device.

In the embodiment of the present invention, the processor 110, the memory 120, and the display 130 may be configured in different devices. In this case, the processor 110, the memory 120, and the display 130 may pass through Wired or wireless communication connection. For example, a communication cable (eg, fiber optic or copper wire, etc.) may be disposed between the processor 110 and the memory 120 (specifically, between the communication interface of the processor 110 and the communication interface of the memory 120) for processing. A wired communication connection between the device 110 and the memory 120. In this case, the communication interface of the processor 110 may be a communication interface of the computer device for communicating with the external device, and similarly, the communication interface of the memory 120 may be a communication interface of the computer device for communicating with the external device.

In the embodiment of the present invention, the processor 110 may be one or more, and the multiple processors 110 may be configured in the same device (for example, a server), or the multiple processors 110 may be configured independently. The invention is not particularly limited.

It should be noted that, in the embodiment of the present invention, when there are multiple processors 110 and are configured in the same device, each processor 110 may be connected through a bus 140 (for example, a PCIE bus), that is, may be through the bus 140. Signaling or data transfer between the various processors 110 is implemented. In addition, when each processor 110 is configured in a different device, information or a signal transceiver connected to the process 110 may be configured in each device, and a transceiver in each device is connected through a transmission cable to implement each processor 110. Signaling or data transfer between.

In an embodiment of the invention, the memory 120 includes at least one controller and at least one storage medium.

A storage medium, also referred to as a storage space, is a medium for storing a certain discontinuous physical quantity. By way of example and not limitation, the storage medium may be a memory chip, and the material of the storage medium may be a semiconductor, a magnetic core, a magnetic drum, a magnetic tape, a material matured in the field of laser discs, and the like. The type of the storage medium may be a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, etc., which are mature types of storage media in the field.

In the embodiment of the present invention, the storage medium may be one or more, and the plurality of storage media may be configured in the same device (for example, a server), or the plurality of storage media may be independently configured, and the present invention does not Specially limited.

The controller, which may also be referred to as a memory controller, is configured to allocate a physical address to the storage medium, access the storage medium according to the physical address, and perform a data storage operation on the storage medium.

The controller is communicatively coupled to the processor 110 described above, for example, the controller can be coupled to the bus 140 such that the controller can communicate with the processor 110 via the bus 140.

By way of example and not limitation, the controller can be a central processing unit or other general purpose processor, Digital signal processors, application specific integrated circuits, field programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.

In the embodiment of the present invention, the controller may be one or more, and the multiple controllers may be configured in the same device, or the multiple controllers may be independently configured, and the present invention is not particularly limited.

In the embodiment of the present invention, the memory 120 may be one or more, and the present invention is not particularly limited. When the memory 120 is multiple, each of the memories 120 may be jointly configured, that is, the plurality of memories 120 may be shared. One or more controllers or storage media.

2 is an example of common business logic of a human resource management system in the prior art. Figure 2 shows the business logic 1, business logic 2 and business logic 3. In different human resource management systems, because different enterprises have different understandings of the objects that need to be managed, there is no uniform standard for management methods. For example, business logic one and business logic two are based on post capabilities, and business logic three is based on strategic planning. For example, the business logic 1 and the business logic 2 management logic are the same, that is, the management is performed by the post capability, but the service hierarchy is different, that is, the business logic level of the business logic one is two levels, and the business level of the business logic two is four layers.

Generally, the business logic of the existing human resource management system is usually created by the R&D technicians after the business needs analysis, through the programming, the definition of the data structure, etc., to realize the management of the data. However, the technical requirements are very high. The operability of managing data is poor.

In the following, in order to facilitate understanding and explanation, the process of managing data according to the embodiment of the present invention is applied to the field of human resource management as an example, and the description will be made.

A method of managing data according to an embodiment of the present invention will be described in detail below with reference to FIGS. 3 through 8.

For the sake of easy understanding, the general body of the method for managing data according to the embodiment of the present invention will be described as an example.

FIG. 3 shows a schematic flow diagram of a method 200 of managing data in accordance with an embodiment of the present invention. As shown in FIG. 3, the method 200 includes steps 210 through 250.

210. Applying the Method 200 A computer system (eg, a processor in a computer system) can acquire a plurality of metadata.

By way of example and not limitation, in the embodiment of the present invention, the manner of obtaining metadata may include multiple types. For example, the computer system may configure a human-computer interaction interface, so that the processor can obtain user input through the human-computer interaction interface. Multiple metadata. Or, the computer system can also be equipped A data (or information) transceiver is provided, so that a plurality of metadata transmitted by the external device of the system can be received by the transceiver, which is not limited in the embodiment of the present invention.

In the embodiment of the present invention, the user can customize the system metadata and configure the detailed information of the metadata. When configuring the details of metadata, users can freely add, edit, or delete fields, and set the type of the field (for example, it can be text, options, or drop-down lists, etc.). You can also set the field to be an optional field or a required field.

In addition, when the user customizes the metadata, he can also choose whether the metadata is hidden. Among them, the hidden metadata cannot be associated with other metadata in the time domain of the mapping relationship of the configuration metadata, and is limited to use in a specific scenario.

When the system obtains the metadata input by the user, the system obtains the detailed information of the metadata at the same time.

By way of example and not limitation, in the embodiment of the present invention, in the field of human resource management, the metadata may include, for example, "post", "ability", "knowledge point", "skill", "learning content", " Various types of data such as strategic planning.

220. Determine at least one primary data from the plurality of metadata based on a first user operation.

The computer system (eg, the processor) determines metadata as the main data from the plurality of metadata after acquiring the plurality of metadata. Moreover, in the embodiment of the present invention, the computer system may configure the user to operate the detecting device (for example, a detecting device for input signals such as a mouse, a keyboard or a touch signal), so that when determining the main data, it may be based on the user's operation ( That is, an example of the first user operation is acquired. For example, the system may provide a page for the user to select the main data, and obtain a plurality of user-defined metadata by detecting a user's click, input, or edit operation, and determine the plurality of metadata as the main data.

It should be noted that, in the embodiment of the present invention, the processor may be integrated with the function of the user operation detecting device, or the processor and the user operation detecting device may be independently configured, and the invention is not particularly limited.

230. Determine, according to a second user operation, at least one tail data from the plurality of metadata, and specify a mapping relationship between the at least one tail data and the at least one primary data.

After determining the at least one main data, the system determines at least one tail data for each main data, and specifies a mapping relationship between the main data and the corresponding tail data.

In order to facilitate the understanding of the description, the method for managing data in the embodiment of the present invention will be described in detail below by taking only the tail data of one metadata as an example.

In an embodiment of the present invention, one or more tail data may be directly associated with one master data (ie, Case 1) In this case, the mapping relationship may refer to a direct mapping relationship from data to tail data. Alternatively, one or more tail data may also be associated with one master data (ie, case 2) via one or more slave data, in which case the mapping relationship may include a mapping relationship of autonomous data to slave data (ie, first Mapping relationship), and the mapping relationship from the data to the tail data (ie, the second mapping relationship). In the following, the specific processing flow in the above two cases will be described in detail.

Situation 1

After the system determines a master data, it can determine the tail data by detecting the user's input operation. For example, the system can provide a selection page for the user to present a plurality of alternative metadata for selection in the selection page. The user can customize the tail data by clicking, dragging, etc. on the selection page. Thus, the system determines one or more metadata selected by the user as tail data by detecting a user operation.

Optionally, before determining at least one tail data from the plurality of metadata based on the second user operation, the method further includes:

a management interface, where the management interface includes a first area and a second area, where the identifier of the primary data is presented, and the identifier of the plurality of candidate metadata in the plurality of metadata is presented in the second area; as well as

Determining at least one tail data from the plurality of metadata based on the second user operation, including:

The tail data is determined from the plurality of candidate metadata based on the second user operation, and the identification of the tail data is presented in the first region.

Specifically, the system can present a management interface to the user, wherein the management interface includes the first area and the second area. However, the relative positions of the first region and the second region are not particularly limited. For example, the first area and the second area may be displayed up and down, the first area is located in the upper half of the management interface, the second area is located in the lower half of the management interface, or the second area is located in the upper half of the management interface, first The area is located in the lower half of the management interface. For another example, the first area and the second area may be displayed left and right or other easily conceivable presentation forms and the like. It should be noted that the presentation forms of the first area and the second area should not be limited to the scope of protection of the embodiments of the present invention.

The first area is used to display the identification of the primary data, and the second area is used to display the identification of the plurality of candidate metadata. Here, the plurality of alternative metadata may be part or all of the acquired plurality of metadata.

By way of example and not limitation, in the embodiment of the present invention, the identifier of the data may be a folder or an icon corresponding to the data, and the like, and the user can identify (or can uniquely indicate) one data. Rendering graphics. Also, in the case where a folder is selected as the logo, the folder can implement a graphic change such as expansion or contraction based on a user operation.

The system determines tail data from the plurality of candidate metadata by detecting an operation of the user on the management interface (ie, a second user operation) and presents an identification of the tail data in the first region.

For example, the second user operation may be a click operation, and after detecting the click operation of the user, the system determines the clicked candidate metadata as the tail data of the main data.

Alternatively, the second user operation is a drag operation of the mouse, and the drag operation is used to indicate that one or some candidate metadata is dragged to the first area of the management interface, for example, the first area is presented. The vicinity of the identified area of the primary data, so that the mapping relationship between the primary data and the tail data (ie, the dragged object) can be specified based on the second user operation. After the system detects the drag operation, one or more candidate metadata to be dragged is determined as the tail data of the main data.

Alternatively, the management interface may present the first area and the second area simultaneously. Alternatively, the management interface may also present the first area and the second area separately. For example, the system detects the click operation of the user, presents the first area on the management interface, automatically detects the main data selected by the user, and automatically presents the second area, and presents the identifier of the plurality of candidate metadata in the second area. The one or more candidate metadata determined by the user from the identification of the plurality of candidate metadata is determined as the tail data of the main data by detecting a user operation.

It should be noted that the identifier of the metadata may include various forms. For example, it can be a folder, an icon, or other form that can identify metadata, and the like.

Situation 2

Optionally, the method further includes:

Determining at least one slave data from the plurality of metadata based on a third user operation, and designating a first mapping relationship between the at least one slave data and the at least one master data;

Determining at least one tail data from the plurality of metadata based on a second user operation, and specifying a second mapping relationship between the at least one tail data and the at least one slave data;

Record the mapping relationship between the primary data and the tail data, including:

Recording a first mapping relationship between the primary data and the secondary data, and recording a second mapping relationship between the secondary data and the tail data;

When receiving the data request carrying the indication information of the main data, determining the tail data according to the main data and the mapping relationship, including:

Upon receiving the data request carrying the indication information of the main data and the indication information of the slave data, the tail data is determined according to the main data, the slave data, the first mapping relationship, and the second mapping relationship.

Specifically, in the embodiment of the present invention, the system may also first determine the slave data, and associate the slave data to the master data (ie, generate the first mapping relationship from the autonomous data to the slave data), and then determine the tail data, and The tail data is associated to the slave data (ie, the second mapping relationship from the data to the tail data is generated). Therefore, the mapping relationship in the embodiment of the present invention is formed by the first mapping relationship and the second mapping relationship.

It can be understood that the slave data is used to connect the master data and the tail data. The slave data and tail data are based on the master data.

Optionally, before determining the at least one slave data from the plurality of metadata based on the third user operation, the method further includes:

Determining at least one slave data from the plurality of metadata based on a third user operation, including:

The slave data is determined from the plurality of candidate metadata based on a third user operation, and the identity of the slave data is presented in the first region.

Specifically, the system can provide a management interface to the user to determine user-defined slave data and tail data by detecting user actions.

Similar to the determining tail data described above, the second area of the management interface presents an identifier of a plurality of candidate metadata, and the processor determines from the plurality of candidate metadata when the detecting device detects the user's operation. From the metadata of the data, and associating the selected slave data with the master data, and presenting the determined slave data in the first region, that is, presenting the identity of the master data and the identifier of the slave data simultaneously in the first region.

For example, the third user operation may be a click operation, and after detecting the click operation of the user, the system determines the clicked candidate metadata as the slave data of the main data.

Alternatively, the third user operation is a drag operation of the mouse, and the drag operation is used to indicate that one or some candidate metadata is dragged to the first area of the management interface, for example, the first area is presented. The vicinity of the identified area of the primary data enables the mapping of the primary data to the secondary data (i.e., the dragged object) based on the third user operation. After the system detects the drag operation, the one or more candidate metadata to be dragged is determined as the slave data of the main data.

Optionally, the determining, according to the second user operation, the at least one tail data from the plurality of metadata, including:

It can be understood that when the slave data and the tail data are determined from the plurality of candidate metadata, when the determined tail data is the data of the next level of the determined slave data, the slave data and the tail data can be simultaneously determined.

For example, the user can drag and drop data and tail data to the first area of the management interface by dragging and dropping on the management interface. After the system detects the drag, the main data, the slave data and the tail data are simultaneously presented in the first area.

240. Record a mapping relationship between the primary data and the tail data.

In the above step 230, the processor determines the main data and the tail data, that is, establishes a mapping relationship between the main data and the tail data. The processor records the mapping relationship to the memory to facilitate returning the result of the data request based on the mapping relationship upon receipt of the data request.

250. When receiving a data request carrying the indication information of the primary data, determining the tail data according to the primary data and the mapping relationship.

When the receiver of the computer system receives the data request carrying the indication information of the main data, the processor determines the target main data according to the indication information of the main data. Combined with the mapping relationship between the recorded main data and the tail data, the tail data of the target main data is returned.

It should be understood that the data request must carry the indication information of the main data, so that the processor can determine the main data requested by the data request from the stored plurality of main data according to the indication information (for convenience of explanation, it is called a target). main data). Further, the tail data of the target main data is determined according to the mapping relationship between the main data and the record (or storage).

Optionally, the data request further carries indication information of the slave data.

In this case, the processor receives the indication information carrying the main data and the data request from the indication information of the data, and the processor determines the slave data according to the main data and the first mapping relationship. The tail data is determined based on the slave data and the second mapping relationship.

According to the method for managing data provided by the embodiment of the present invention, the display allows the user to intuitively customize the mapping relationship between the metadata and the metadata of the system through the presentation management interface, thereby visualizing the mapping relationship between the data, and improving the system management data. Maneuverability.

Specifically, the mapping relationship between the main data and the tail data can be passed through the main data and the mantissa. Determine between one or more data from the data. That is, first, a mapping relationship between the main data and the slave data is generated (referred to as a first mapping relationship for convenience of explanation), and a mapping relationship between the data and the tail data is generated (for convenience of explanation, the second mapping relationship is recorded) ).

Correspondingly, when receiving the data request carrying the indication information of the main data, the receiver of the computer system may determine the slave data according to the indication information of the main data and the first mapping relationship. The tail data is determined according to the determined slave data and the second mapping relationship.

Optionally, the primary data is at least two, and at least two primary data belong to N data structures, N≥2, and,

Presentation management interface, including:

Determining N pages according to the number N of the data structures, wherein the N data structures are in one-to-one correspondence with the N pages, and each page is used to present an identifier of the main data in the corresponding data structure;

A page label of the N pages is presented in the first area, and at least one of the N pages is presented in the first area.

In the embodiment of the present invention, the main data may be multiple. When there are a plurality of pieces of main data, N pages are presented on the management interface according to the number N of data structures to which the plurality of main data belong. That is, how many data structures there are and how many pages are presented.

At the same time, N tabs are presented in the first area of the management interface, and each tab corresponds to one page. When the N pages are presented in the first area, only one of the N pages may be presented. Then, by detecting the operation of the user clicking the tab, the page corresponding to the tab selected by the user by clicking is presented.

Alternatively, the first area may also present the N pages simultaneously. For example, the N pages are simultaneously displayed side by side in the first area. This kind of presentation makes the system's various business logics clear at a glance, and visually displays the mapping relationship between the main data and the slave data and the tail data in each page. Alternatively, the N pages may be displayed in an overlapping manner, and when detecting the operation of the user clicking the tab, the system displays the page corresponding to the tab selected by the user at the top layer. The embodiment of the present invention does not limit the presentation form of the page, and may be different according to different application scenarios.

Optionally, presenting at least one of the N pages in the first area, including:

Determining, according to the data attribute information of each of the at least two main data, the at least one first main data from the at least two main data, wherein the data attribute information of the first main data satisfies a preset condition;

Presenting at least one of the N pages in the first area, the main page is for presenting Now the page of the first master data.

In the embodiment of the present invention, the system may select one or more first main data from the plurality of main data according to the data attribute information of the plurality of main data, and present the N pages in the first area. The page of the identification of the first master data is determined to be the main page.

It should be noted that, the data attribute information of the first primary data meets the preset condition, that is, the system determines, according to the user operation, the user-defined metadata for creating the primary service logic as the first primary data.

In the embodiment of the present invention, a user may define one or more business logics according to business needs.

FIG. 4 shows a schematic diagram of user-defined metadata and business logic in an embodiment of the present invention. As shown in Figure 4, the user defines two business logics. The business logic is a post capability model. In the business logic 1, the user-defined master data is a post, and the slave data has two, respectively, the capability and Skills, tail data is a knowledge point. In Business Logic 2, user-defined master data is an annual strategy, with data from being the work target and tail data being the work task.

It should be noted that when the user customizes multiple business logics, one of them may be selected as the main business logic, and the rest as the non-primary business logic.

It can be understood that the user can directly participate in the construction of the underlying data by means of user-defined metadata and metadata business logic, which can improve the flexibility of the configuration of the human resource management system and solve the problem of poor usability in the existing system. problem.

FIG. 5 is a schematic diagram of a management interface according to an embodiment of the present invention. As shown in FIG. 5, in the embodiment of the present invention, the management interface includes a first area and a second. The first area is used to present an identifier of the primary data, and the second area is used to display an identifier of the candidate metadata. In the upper left corner of the management interface, a tab is displayed. The user-defined business logic is displayed in the tab. As described above, if there are multiple user-defined business logics, correspondingly, there are multiple tabs, and each tab corresponds to one business logic. In the management interface shown in Figure 5, the tabs are two. Moreover, the main business logic is directly displayed on the management interface, and the non-primary business logic is displayed in the form of a tab.

In the embodiment of the present invention, after acquiring a plurality of metadata, the processor presents the management interface shown in FIG. 4 to the user. For specific business needs, the user can configure the mapping relationship between the metadata (or the logic of the data) on the management interface. Among them, in a mapping relationship, at least the main data and the tail data should be included. Among them, the main data is one, and the tail data can be one or more. Optionally, one or more slave data may also be included in one mapping relationship. The slave data is used to interface the master data with the tail data.

Hereinafter, a process in which a user configures a mapping relationship between metadata on a management interface is exemplified in conjunction with FIG. 5 and FIG. 6.

For example, the user configures the metadata post A shown in FIG. 5, and the user can associate the slave data and the tail data of the second region to the post A (ie, the main data) by dragging and dropping the mouse. Assume that the user believes that the staff of position A of a certain enterprise needs to have skill A, ability B, knowledge point A and knowledge point B. Then, the user first clicks the tab of the "skill" in the second area, the system detects the click operation of the user, and displays a plurality of candidate metadata corresponding to the plurality of tabs "skills" in the second area of the management interface. The user finds "skill A" and directly drags "skill A" to the first area by mouse, completing the configuration of the mapping relationship between the post A and the skill A. At this time, the system uses "skill A" as the tail data of "post A", and presents the identifier of the tail data "skill A" in the first area. Thereafter, the user clicks the tab of "Capability" in the second area. As described above, the system presents metadata showing a plurality of "capabilities" in the second area in response to the click operation. The user can directly drag the alternative metadata "Capability B" to the first area, and the system detects the drag operation and presents the identifier of the metadata "Capability B" in the first area.

It can be understood that if the metadata "Capability B" includes 3 seed capabilities, that is, "Sub-Capabilities 1", "Sub-Capabilities 2", and "Sub-Capabilities 3". When the user drags "capability B" from the second area to the first area, "sub-capability 1", "sub-capability 2", and "sub-capacity 3" also form a mapping relationship with "post A". The system presents the identifiers of "sub-capabilities 1", "sub-capabilities 2", and "sub-capabilities 3" in the first region. If the user thinks that "sub-ability 2" needs to master "skill 1", "skill 2" and "skill 3", you can drag "skill 1", "skill 2" and "skill 3" from the second area to the first The area is associated with "sub-capability 2". Similarly, the user believes that "skill 2" needs to be obtained by learning "knowledge point 1" and "knowledge point 2", then the user can click on the tab of the second area "knowledge point", and "knowledge point 1" and " Knowledge Point 2" is dragged from the second area to the first area and associated with "Skill 2". Finally, the user directly drags "Knowledge Point A" and "Knowledge Point B" from the page corresponding to the tab of the second area "Knowledge Point" to the first area, and associates with "Post A". So far, the user has completed the configuration of the mapping relationship for the main data "Post A". The system presents the mapping in the first region, see Figure 6.

It should be understood that the order of the mapping relationship between the user configuration metadata described above is only illustrated as an example. In the embodiment of the present invention, the order of the configuration is not particularly limited.

It should be understood that the "post family" and the "capability family" shown in FIG. 5 are each an example of a data structure in the embodiment of the present invention.

The processor determines the main data, the slave data, and the tail data by detecting a drag operation of the user on the management interface, and generates a mapping relationship between the master data, the slave data, and the tail data, and records the mapping relationship.

FIG. 6 illustrates still another example of interaction design of a method of managing data in accordance with an embodiment of the present invention. As shown in FIG. 6, the first area of the management interface currently presents a page corresponding to the "Capability Position Model" tab. The second area of the management interface currently presents the page corresponding to the "Capabilities" tab. In the mapping relationship shown in the first area, "post A" is the main data, and the tail data is "skill A", "knowledge point A", "knowledge point B", "knowledge point 1", and "knowledge point 2" ". The slave data is "Capability B", "Sub-Capabilities 1", "Sub-Capabilities 2", "Sub-Capabilities 3", "Skill 1", "Skill 2", and "Skill 3". In this page, the data structure is "post family". Further, in the mapping relationship shown in the first region, "skill A", capability B", "knowledge point A", and "knowledge point B" are located at the first level of the main data "post A", "sub-capabilities" 1", "Sub-Capabilities 2", "Sub-Capabilities 3" are located at the second level, "Skill 1", "Skill 2" and "Skill 3" are located at the third level, "Knowledge Point 1" and "Knowledge Point 2" are located The fourth level is also the last level.

In order to make rational use of the management interface and to reflect the difference between the same data and different data, the level of metadata is clearly displayed in the management interface. The expansion of multiple levels of a metadata is illustrated in the first area of the management interface in Figure 5. Also, the indentation of the metadata of the same level is the same.

It should be noted that, in the embodiment of the present invention, different types of metadata (for example, skill A, capability B, knowledge point A, and knowledge point B) are displayed at the same level after being associated with the same metadata, and The amount of indentation remains the same. See Figure 5.

It should also be noted that a "√" icon is displayed in the upper right corner of the first area. In the embodiment of the present invention, after clicking the “√” icon, the following effects are triggered:

All the data of the first area is followed by a "√" option for selecting the data. After selecting the main data, all the data associated with the main data is selected;

A drop-down list is displayed next to the "√" icon in the upper right corner of the first area, and is used to perform corresponding operation processing on the selected metadata. For example, operation 1 is to derive a learning plan.

It should be noted that the “√” icon described above is only an example, and it is obvious that the icon can also be designed in any other shape, but should fall within the protection scope of the embodiment of the present invention.

7 is still another example of interaction design of a method of managing data in accordance with an embodiment of the present invention. As shown in Figure 7, on the management interface, the following mainly involves the following operations on metadata:

Expanding or stowing: In the embodiment of the present invention, "+" of each metadata front end is used to expand one metadata, and "-" is used to collapse one metadata.

Display summary information: If the user is operating on a personal computer and the mouse slides over a piece of metadata, it stays for a while and can display summary information of the metadata.

It should be noted that in this operation, only the required fields of the metadata are displayed here.

In addition, this part of the operation is not involved on the phone or tablet. However, on a mobile phone or tablet, the summary information of the metadata can be displayed by pressing.

Click: After clicking a metadata, multiple action options are displayed after the metadata. Taking Figure 6 as an example, click on the metadata "skill A" to display three operation options, namely "edit", "delete" and "add". It is used for the user to select the operation processing for editing and deleting the metadata.

The operation of clicking on metadata can also be done on mobile phones and tablets.

Double-click: After double-clicking on a metadata, a layer pops up on the current page to render the edit window. At the same time, the page behind the edit window adds a transparent gray mask to highlight the layer that pops up. Among them, a close button is displayed in the upper right corner of the edit window. See Figure 8.

FIG. 8 shows still another example of the interaction design of the method of managing data according to an embodiment of the present invention. As shown in FIG. 8 , in the embodiment of the present invention, the editing window can be opened in a tab of the browser, so as to avoid input efficiency caused by frequent switching between multiple tabs when the user performs the metadata mapping relationship configuration. Low problems can improve the efficiency of data configuration for users.

9 is a schematic system architecture diagram of a method of managing data in accordance with an embodiment of the present invention. As shown in Figure 9, the system mainly includes the following parts:

Access device: Users can access the system using electronic devices such as personal computers, laptops, tablets or mobile phones.

Cloud server: divided into two parts: data logic and database. Data logic is used to process user metadata requests and to identify associations between metadata. The database is used to store data generated by the user during the configuration process.

Server hardware: Universal server hardware can be used, including not limited to x86 servers, Unix servers, or virtual machines. Storage can use the server's own storage or a generic disk array. Network devices can use a common Ethernet switch or virtual network switch.

The methods for accessing the system are not identical for different access devices. The personal computer accesses the Hypertext Markup Language (HTML) page through a browser, and the HTML page is accessed through the encapsulated Web Interface. Flat plate Computers and mobile phones are accessed through native applications, and native applications are accessed through a packaged Software Development Kit (SDK).

In the embodiment of the present invention, the communication between the foregoing devices may be implemented by using the prior art, and details are not described herein.

In order to facilitate the understanding of the method for managing data in the embodiment of the present invention, an example will be described below with reference to FIG.

FIG. 10 is an example of a method of managing data according to an embodiment of the present invention. As shown in FIG. 10, in this embodiment, a learning plan of a solution development manager is taken as an example. According to the method for managing data according to an embodiment of the present invention, a user first needs to define a plurality of metadata according to a service requirement, and define an association relationship of the plurality of metadata.

First, the user defines multiple metadata for positions, abilities, skills, and knowledge points. Among them, the user defines the position as the main data, defines the ability and skill as the slave data, and defines the knowledge point as the tail data.

The solution development manager has three capabilities, namely solution development capabilities, project management capabilities, and communication capabilities. Detailed development of solution development capabilities, including three skills, LEVEL1's skills to use commercial canvas, LEVEL 2's skills to use CHARTER templates and LEVEL3's skills to use MKT tools. The LEVEL 1 uses the commercial brush skills to expand, which includes two knowledge points, namely what is a commercial canvas (ie, a commercial canvas introduction) and how to use a commercial canvas.

After the metadata and the business logic are defined, the mapping relationship between the metadata can be configured through the user interaction modes of FIG. 5 to FIG. 8.

The method for managing data in the embodiment of the present invention enables a user to select a primary data and a tail data, and specify a mapping relationship between the primary data and the tail data, thereby allowing the user to adjust data between the data according to his own needs. Logical relationship.

The method for managing data according to an embodiment of the present invention is described in detail above with reference to FIGS. 2 through 10. Referring to FIG. 11 and FIG. 12, an apparatus and apparatus for managing data according to an embodiment of the present invention will be described.

FIG. 11 shows a schematic block diagram of an apparatus for managing data according to an embodiment of the present invention. As shown in Figure 11, the device includes:

The obtaining unit 510 is configured to acquire a plurality of metadata.

The processing unit 520 is configured to determine at least one main data from the plurality of metadata when the detecting unit 530 detects the first user operation;

The processing unit 520 is further configured to: when the detecting unit 530 detects the second user operation, determine at least one tail data from the plurality of metadata, and specify between the at least one tail data and the at least one main data Mapping relations;

The processing unit 520 is further configured to: when the receiving unit 540 receives the data request of the indication information of the primary data, determine the tail data according to the primary data and the mapping relationship.

The units in the apparatus 500 for managing data and the other operations or functions described above in accordance with an embodiment of the present invention are respectively implemented to implement respective processes in the method 200. For the sake of brevity, it will not be repeated here.

FIG. 12 is a schematic structural diagram of an apparatus 700 for managing data according to an embodiment of the present invention. As shown in FIG. 12, the device 700 includes a processor 710, a display 720, a memory 730, and a transceiver 740, wherein the processor 710, the display 720, the memory 730, and the transceiver 740 are connected by a bus system 750, which is used by the memory 730. For storing instructions, the processor 710 is configured to execute instructions stored by the memory 730 to control the transceiver 740 to transmit or receive signals. among them,

The transceiver 740 is configured to acquire multiple metadata.

The processor 710 is configured to determine at least one main data from the plurality of metadata when the first user operation is detected;

The processor 710 is further configured to: when detecting the second user operation, determine at least one tail data from the plurality of metadata, and specify a mapping relationship between the at least one tail data and the at least one main data;

The processor 710 is further configured to determine the tail data according to the primary data and the mapping relationship when the transceiver 740 receives the data request carrying the indication information of the primary data.

It should be understood that, in the embodiment of the present invention, the processor 710 may be a central processing unit ("CPU"), and the processor 710 may also be other general-purpose processors, digital signal processors (DSPs). , an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, and the like. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 730 can include read only memory and random access memory and provides instructions and data to the processor 710. A portion of the memory 730 may also include a non-volatile random access memory. For example, the memory 730 can also store information of the device type.

The bus system 740 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 740 in the figure.

In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 710 or an instruction in a form of software. The steps of the method for managing data disclosed in the embodiments of the present invention may be directly implemented as hardware processor execution completion, or performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in memory 730, and processor 710 reads the information in memory 730 and, in conjunction with its hardware, performs the steps of the above method. To avoid repetition, it will not be described in detail here.

The units in the device 700 for managing data and the other operations or functions described above are respectively for the respective processes in the method 200, in accordance with an embodiment of the present invention. For the sake of brevity, it will not be repeated here.

Therefore, the device for managing data according to the embodiment of the present invention enables the user to adjust the mapping relationship between the main data and the tail data by selecting main data and tail data, thereby allowing the user to adjust according to his own needs. The logical relationship between the data.

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices, and The method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

The functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A method of managing data, characterized by:

Get multiple metadata;

Determining at least one master data from the plurality of metadata based on a first user operation;

Determining at least one tail data from the plurality of metadata based on a second user operation, and designating a mapping relationship between the at least one tail data and the at least one master data;

Recording a mapping relationship between the main data and the tail data;

When receiving the data request carrying the indication information of the main data, determining the tail data according to the main data and the mapping relationship.
The method of claim 1, wherein the method further comprises: before determining at least one tail data from the plurality of metadata based on the second user operation, the method further comprising:

Presenting a management interface, where the management interface includes a first area and a second area, wherein the first area presents an identifier of the at least one primary data, and the second area presents a plurality of the plurality of metadata The identification of the alternative metadata;

Determining at least one tail data from the plurality of metadata based on the second user operation, including:

Determining the at least one tail data from the plurality of candidate metadata based on a second user operation and presenting the identification of the at least one tail data in the first region.
The method of claim 2 wherein said second user operation comprises dragging an identification of said at least one tail data from said second region to said first region.
The method of claim 1 further comprising:

Determining at least one slave data from the plurality of metadata based on a third user operation, and designating a first mapping relationship between the at least one slave data and the at least one master data;

Determining at least one tail data from the plurality of metadata based on the second user operation, including:

Determining at least one tail data from the plurality of metadata based on a second user operation, and designating a second mapping relationship between the at least one tail data and the at least one slave data;

Recording a mapping relationship between the primary data and the tail data, including:

Recording a first mapping relationship between the primary data and the secondary data, and recording a second mapping relationship between the secondary data and the tail data;

When receiving the data request carrying the indication information of the main data, according to the main Data and the mapping relationship, determining the tail data, including:

When receiving the data request carrying the indication information of the main data and the indication information of the slave data, according to the main data, the slave data, the first mapping relationship, and the second mapping relationship, Determine the tail data.
The method according to claim 4, wherein the method further comprises: before determining the at least one slave data from the plurality of metadata based on the third user operation, the method further comprising:

Presenting a management interface, where the management interface includes a first area and a second area, wherein the first area presents an identifier of the at least one primary data, and the second area presents a plurality of the plurality of metadata The identification of the alternative metadata;

Determining at least one slave data from the plurality of metadata based on the third user operation, including:

The at least one slave data is determined from the plurality of candidate metadata based on a third user operation, and an identification of the at least one slave data is presented in the first region.
The method according to claim 5, wherein determining at least one tail data from the plurality of metadata based on the second user operation comprises:

Determining the at least one tail data from the plurality of candidate metadata based on a second user operation and presenting the identification of the at least one tail data in the first region.
A method according to claim 5 or claim 6, wherein said second user operation comprises dragging an identification of said tail data from said second area to said first area and said tail data The identifier is associated with at least one of the slave data identifiers to specify a mapping relationship between the at least one tail data and the at least one of the slave data.
The method according to any one of claims 5 to 7, wherein the third user operation comprises dragging the identification of the slave data from the second area to the first area, and The identifier of the slave data is associated with an identifier of the at least one of the master data to specify a mapping relationship between the at least one slave data and at least one of the master data.
The method according to any one of claims 1 to 8, wherein the main data is at least two, and the at least two main data belong to N data structures, N≥2, and

The presentation management interface includes:

Determining N pages according to the number N of the data structures, where the N data structures are in one-to-one correspondence with the N pages, and each page is used to present an identifier of the main data in the corresponding data structure;

Presenting a page label of the N pages in the first area, and presenting at least one of the N pages in the first area.
The method according to claim 9, wherein the presenting at least one of the N pages in the first area comprises:

Determining at least one first primary data from the at least two primary data according to data attribute information of each of the at least two primary data, wherein the data attribute information of the first primary data meets a preset condition;

Presenting at least one of the N pages in the first area, the main page being a page for presenting the first main data.
An apparatus for managing data, the apparatus comprising:

An obtaining unit for acquiring a plurality of metadata;

When the detecting unit detects the first user operation, the processing unit is configured to determine at least one main data from the plurality of metadata;

And when the detecting unit detects the second user operation, the processing unit is configured to determine at least one tail data from the plurality of metadata, and specify between the at least one tail data and the at least one main data Mapping relationship;

The processing unit is further configured to record a mapping relationship between the main data and the tail data;

When the receiving unit receives the data request carrying the indication information of the main data, the processing unit determines the tail data according to the main data and the mapping relationship.
The device according to claim 11, wherein the device further comprises:

a display unit, configured to: before the processing unit determines at least one tail data from the plurality of metadata, present a management interface, where the management interface includes a first area and a second area, where the first area is presented An identifier of the at least one primary data, the identifier of the plurality of candidate metadata in the plurality of metadata being presented in the second region;

The processing unit is specifically configured to determine the at least one tail data from the plurality of candidate metadata based on the second user operation, and present an identifier of the tail data in the first area.
The apparatus of claim 12 wherein said second user operation comprises dragging an identification of said at least one tail data from said second area to said first area.
The device according to claim 11, wherein the processing unit is specifically configured to:

Determining at least one slave data from the plurality of metadata based on a third user operation, and specifying a first mapping relationship between the at least one slave data and the at least one master data;

Determining at least one tail data from the plurality of metadata based on a second user operation, and designating a second mapping relationship between the at least one tail data and the at least one slave data;

Recording a first mapping relationship between the primary data and the secondary data, and recording a second mapping relationship between the secondary data and the tail data;

The processing unit is further configured to, when the receiving unit receives the data request carrying the indication information of the main data and the indication information of the slave data, according to the main data, the slave data, the The first mapping relationship and the second mapping relationship determine the tail data.
The device according to claim 14, wherein the device further comprises:

a display unit, configured to present a management interface before the processing unit determines at least one slave data from the metadata, where the management interface includes a first area and a second area, where the primary is presented in the first area An identifier of the data, wherein the identifier of the plurality of candidate metadata in the plurality of metadata is presented in the second area;

The processing unit is further configured to determine the at least one slave data from the plurality of candidate metadata based on a third user operation, and the display unit is specifically configured to present the at least the first area An identification from the data.
The apparatus according to claim 15, wherein the processing unit is specifically configured to determine the at least one of the plurality of candidate metadata when the detecting unit detects the second user operation Tail data, and the display unit is specifically configured to present an identifier of the at least one tail data in the first area.
The apparatus according to claim 15 or 16, wherein said second user operation comprises dragging an identification of said at least one tail data from said second area to said first area, and said An identification of the at least one tail data is associated with an identification of the at least one of the slave data to specify a mapping relationship between the at least one tail data and the at least one of the slave data.
The apparatus according to any one of claims 15 to 17, wherein the third user operation comprises dragging the identification of the slave data from the second area to the first area, and The identifier of the slave data is associated with an identifier of the at least one master data to specify a mapping relationship between the at least one slave data and the at least one master data.
The apparatus according to any one of claims 11 to 18, wherein the main data is at least two, and the at least two main data belong to N data structures, N≥2, and

The processing unit is specifically configured to determine N pages according to the number N of the data structures, where The N data structures are in one-to-one correspondence with the N pages, and each page is used to present an identifier of the main data in the corresponding data structure;

The display unit is specifically configured to present a page label of the N pages in the first area, and present at least one of the N pages in the first area.
The apparatus according to claim 19, wherein the processing unit is configured to determine at least one of the at least two main data according to data attribute information of each of the at least two main data First primary data, wherein the data attribute information of the first primary data meets a preset condition;

The display unit is specifically configured to present at least one of the N pages in the first area, where the main page is a page for presenting the first main data.