CN116521488A - Metadata-based self-defined document tracing method, device, equipment and medium - Google Patents

Abstract

The invention relates to the technical field of data processing, and discloses a metadata-based self-defined document traceability method, device, equipment and medium. The method includes: obtaining a data processing request initiated by a user on a target receipt page; determining the target metadata type corresponding to the data processing request if the user has the operation function authority matching the data processing request; according to the According to the target metadata type, the target metadata to be processed is obtained; according to the data processing authority of the user for the target metadata type, a data processing page corresponding to the target metadata is generated and displayed. The technical solution of the embodiment of the present invention solves the problem that the software system in the related art cannot meet the data tracking analysis requirements of all customers, and can automatically realize the data tracking processing from business documents to various metadata types.

Description

Metadata-based custom document traceability method, device, equipment and media

technical field

The present invention relates to the technical field of data processing, in particular to a metadata-based self-defined document traceability method, device, equipment and medium.

Background technique

In the process of using software products, different customers may have various data tracking and analysis requirements, for example, data tracking requirements between various documents and between documents and basic data. However, the productized software system cannot meet all the data tracking and analysis needs of all customers.

Contents of the invention

The invention provides a metadata-based self-defined document traceability method, device, equipment and medium, which can automatically realize data tracking processing from business documents to various metadata types.

According to an aspect of the present invention, a metadata-based custom document traceability method is provided, including:

Obtain the data processing request initiated by the user on the target receipt page;

If the user has the operation function authority matching the data processing request, determine the target metadata type corresponding to the data processing request;

Obtain the target metadata to be processed according to the target metadata type;

Generate and display a data processing page corresponding to the target metadata according to the user's data processing authority for the target metadata type.

Optionally, if the user has the operation function authority matching the data processing request, determine the target metadata type corresponding to the data processing request, including:

According to the user ID of the user, in the function authority list, query whether there is a target operation function authority matching the data processing request among the operation function authorities possessed by the user;

If it exists, obtain the metadata type corresponding to the target operation function permission in the function permission list as the target metadata type;

Wherein, the function permission list includes the association relationship between the user and the metadata type and the operation function permission on the metadata type.

Optionally, obtain the target metadata to be processed according to the target metadata type, including:

Get the initial metadata page name matching the target metadata type;

Querying the first metadata page whose page name is consistent with the name of the initial metadata page;

If there is a user-defined second metadata page in the first metadata page, then obtain the data in the second metadata page as the target metadata;

If there is no second metadata page configured by the user in the first metadata page, the data in the initial metadata page is acquired as the target metadata.

Optionally, according to the user's data processing authority for the target metadata type, generate and display a data processing page corresponding to the target metadata, including:

Query the data permission list according to the user ID of the user, and obtain the data processing permission of the user for the target metadata type;

If the data processing authority matches the target metadata, a data processing page corresponding to the data processing request will be generated and displayed according to the target metadata;

Wherein, the data permission list includes the association relationship between the user and the metadata type and the data processing permission for the metadata type.

Optionally, before obtaining the data processing request initiated by the user on the target receipt page, further include:

Register preset metadata types and their corresponding metadata in the target software system;

The initial tracking page information and the initial metadata page matching each metadata type are respectively defined; the initial tracking page information includes the name of the initial metadata page.

Optionally, after registering the preset metadata type and its corresponding metadata in the target software system, further include:

Generate configurable manifests based on registered metadata types and send configurable manifests to managers;

In response to the authority assignment operation of the administrator on the function authority allocation page, obtain the operation function authority of each user for each metadata type in the configurable list, and generate a function authority list;

In response to the authority allocation operation of the administrator on the data authority allocation page, the data processing authority of each user for each metadata type in the configurable list is obtained, and a data authority list is generated.

Optionally, obtain the data processing request initiated by the user on the target receipt page, including:

Displaying a menu list including at least one metadata type to be tracked in response to the user triggering the data tracking control on the target receipt page;

In response to the user's hit operation on the target metadata type in the menu list, display an operation function menu corresponding to the target metadata type;

A data processing request is generated in response to the user's hitting operation on a function option in the operation function menu.

According to another aspect of the present invention, a metadata-based custom document traceability device is provided, including:

The request acquisition module is used to acquire the data processing request initiated by the user on the target receipt page;

A data type determination module, configured to determine the target metadata type corresponding to the data processing request if the user has the operation function authority matching the data processing request;

a metadata acquisition module, configured to acquire target metadata to be processed according to the target metadata type;

The display module is configured to generate and display a data processing page corresponding to the target metadata according to the user's data processing authority for the target metadata type.

According to another aspect of the present invention, an electronic device is provided, and the electronic device includes:

at least one processor; and

memory communicatively coupled to at least one processor; wherein,

The memory stores a computer program executable by at least one processor, and the computer program is executed by at least one processor, so that at least one processor can execute the metadata-based custom document traceability method in any embodiment of the present invention.

According to another aspect of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the metadata-based automatic Define the document traceability method.

The technical solution of the embodiment of the present invention obtains the data processing request initiated by the user on the target receipt page; if the user has the operation function authority matching the data processing request, then determines the target metadata type corresponding to the data processing request; according to the target metadata Data type, to obtain the target metadata to be processed; according to the user's data processing authority for the target metadata type, generate and display the data processing page corresponding to the target metadata, which solves the problem that the software system in related technologies cannot satisfy all customers' data tracking Analyze requirements, and automatically implement data tracking and processing from business documents to various metadata types.

It should be understood that the content described in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will be easily understood from the following description.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

Fig. 1 is a flow chart of a metadata-based self-defined document traceability method provided according to Embodiment 1 of the present invention;

FIG. 2 is a flow chart for automatically implementing data tracking processing applicable according to Embodiment 1 of the present invention;

Fig. 3 is a flow chart of another metadata-based custom document traceability method provided according to Embodiment 2 of the present invention;

Fig. 4 is a schematic structural diagram of a metadata-based self-defined document traceability device provided according to Embodiment 3 of the present invention;

Fig. 5 is a schematic structural diagram of an electronic device implementing the metadata-based self-defined document traceability method according to an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only It is an embodiment of a part of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

It should be noted that the terms "object", "first", "second" and the like in the specification and claims of the present invention and the above drawings are used to distinguish similar objects, and not necessarily used to describe a specific order or sequentially. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

Embodiment one

Fig. 1 is a flow chart of a metadata-based self-defined document traceability method provided according to Embodiment 1 of the present invention. This embodiment is applicable to the case of tracking and processing the metadata of specified business data in a business document. The method It can be implemented by a custom document traceability device based on metadata, which can be implemented in the form of hardware and/or software, and which can be configured in electronic equipment, such as terminal equipment installed with a target software system. As shown in Figure 1, the method includes:

S110. Obtain a data processing request initiated by the user on the target receipt page.

Wherein, the target document may be a business document generated by the user in the target software, such as a purchase receipt or the like. The target document includes business data of various metadata types, for example, the purchase receipt document includes business data of the metadata type of "supplier", business data of the metadata type of "operator", and business data of the metadata type of "warehouse". business data, etc. The target document page refers to the display page of the business document. The data processing request can be a metadata tracking processing request initiated by the user for the metadata type corresponding to the specified business data in the target document. Supplier information modification requests, etc.

Optionally, acquiring the data processing request initiated by the user on the target receipt page includes: displaying a menu list including at least one metadata type to be tracked and processed in response to the user's trigger operation on the data tracking control on the target receipt page; In response to the user's hit operation on the target metadata type in the menu list, an operation function menu corresponding to the target metadata type is displayed; in response to the user's hit operation on the function option in the operation function menu, a data processing request is generated.

In this embodiment, a data tracking control is set on each business document page, and when the user clicks on the data tracking control on the target document page, a menu list will pop up, which includes all the trackable metadata in the target document type, or the menu list includes all the metadata types in the target document, where the traceable metadata types are displayed as operable, and the untraceable metadata types are displayed as inoperable. When the user clicks on the target metadata type in the menu list, or the user moves the mouse over the target metadata type in the menu list, display information increase, information viewing, information modification and information corresponding to the target metadata type Delete and other operation function menus. When the user clicks on a function option in the operation function menu, a data processing request corresponding to the target metadata type is generated. Exemplarily, if the user clicks the "information viewing" function option in the operation function menu corresponding to the "supplier" metadata type, a supplier information viewing request is generated.

S120. If the user has the operation function authority matching the data processing request, determine the target metadata type corresponding to the data processing request.

In this embodiment, whether a user can track metadata of a metadata type in response to a data processing request depends on whether the user has the operation function authority of the corresponding metadata type. Exemplarily, only when the user has the right to modify the supplier information, the supplier information modification request can be responded to, the metadata of the supplier metadata type can be tracked and provided to the user for modification.

Optionally, if the user has the operation function authority matching the data processing request, determine the target metadata type corresponding to the data processing request, including: according to the user ID of the user, query the operation function authority possessed by the user in the function authority list Whether there is a target operation function permission matching the data processing request in ; if it exists, obtain the metadata type corresponding to the target operation function permission in the function permission list as the target metadata type.

In this embodiment, the function authority list includes associations between users and metadata types and operation function authority on the metadata types. Exemplarily, user A-supplier-supplier information viewing, supplier information modification. As shown in Figure 2, after the user's data processing request is obtained, the user ID is obtained according to the data processing request, and all operation function permissions of the user are found by querying the function permission list according to the user ID, and the data processing request is combined with the user's Compare the operation function permissions. If a consistent target operation function permission is found, the user has permission to use the metadata tracking function. At this time, the metadata type corresponding to the target operation function permission in the function permission list can be used as the target metadata type for tracking metadata. If no consistent target operation function permission is found, the user does not have permission to use the metadata tracking function and can end this data processing request.

S130. Acquire target metadata to be processed according to the target metadata type.

Wherein, the target metadata to be processed is description information of the business data of the target metadata type in the target document page. For example, if the target metadata type is "supplier", and the business data corresponding to the metadata type "supplier" on the target document page is "B company", the target metadata can include company B's unit code, unit name, unit abbreviation , location, legal representative, business scope and other information.

Optionally, according to the target metadata type, obtain the target metadata to be processed, including: obtaining the name of the initial metadata page matching the target metadata type; querying the first metadata page whose page name is consistent with the name of the initial metadata page ; If there is a second metadata page of user-defined configuration in the first metadata page, obtain the data in the second metadata page as the target metadata; if there is no second metadata page of user-defined configuration in the first metadata page If the binary data page is used, the data in the initial metadata page is obtained as the target metadata.

In this embodiment, as shown in Figure 2, after the target metadata type corresponding to the data processing request is determined, the name of the initial metadata page built into the system is found according to the target metadata type, and the first metadata page name whose page name is the initial metadata page name is queried. Unary data page. Among them, the first metadata page includes at least the initial metadata page built in the system. Since the user can customize the configuration of the initial metadata page, and the name of the customized metadata page is the same as the name of the initial metadata page, therefore, the first A metadata page may also include metadata pages of different user-defined configurations. It is further inquired whether there is a second metadata page configured by the user in the first metadata page, and if it exists, the data in the second metadata page is acquired as the target metadata. If not present, get the data in the initial metadata page as target metadata.

S140. Generate and display a data processing page corresponding to the target metadata according to the user's data processing authority for the target metadata type.

In this embodiment, whether the user can use the corresponding data operation function on the tracked metadata depends on whether the user has the data processing authority to hit the metadata. Exemplarily, if the data processing authority of the user is to view the suppliers associated with the department, and the supplier information acquired according to the target metadata type happens to belong to the supplier associated with the department, the user can edit the obtained Target metadata to view.

Optionally, according to the user's data processing authority for the target metadata type, generate and display the data processing page corresponding to the target metadata type, including: query the data permission list according to the user ID of the user, and obtain the user's permission for the target metadata type Data processing authority; if the data processing authority matches the target metadata, a data processing page corresponding to the data processing request is generated and displayed according to the target metadata.

In this embodiment, the data permission list includes associations between users and metadata types and data processing permissions for metadata types. Exemplarily, user A-supplier-checks the supplier information associated with this department, and checks the supplier information of Jiangsu, Zhejiang and Shanghai. As shown in Figure 2, after obtaining the target metadata to be processed according to the target metadata type, query the data permission list according to the user ID, find all the data processing permissions that the user has for the target metadata type, and determine whether there is a hit Data processing authority for tracked target metadata. If it exists, the user has the right to perform corresponding data operations on the target metadata, and can automatically build a data processing page corresponding to the data processing request according to the target metadata, and render the page and display it to the user, so that the user can conveniently use the target metadata. Perform data operations allowed by the operation function permission on the target metadata on the page. If it does not exist, the user does not have permission to perform corresponding data operations on the target metadata, and this data processing request can be ended.

The technical solution of the embodiment of the present invention obtains the data processing request initiated by the user on the target receipt page; if the user has the operation function authority matching the data processing request, then determines the target metadata type corresponding to the data processing request; according to the target metadata Data type, to obtain the target metadata to be processed; according to the user's data processing authority for the target metadata type, generate and display the data processing page corresponding to the target metadata, which solves the problem that the software system in related technologies cannot satisfy all customers' data tracking Analyze requirements, and automatically implement data tracking and processing from business documents to various metadata types.

Embodiment two

Fig. 3 is a flow chart of another metadata-based self-defined document traceability method according to Embodiment 2 of the present invention. This embodiment further explains the data from business documents to specified metadata types on the basis of the above-mentioned embodiments. Track processing. As shown in Figure 3, the method includes:

S310. Register preset metadata types and corresponding metadata in the target software system, and respectively define initial tracking page information and initial metadata pages matching each metadata type.

Among them, metadata types include basic data types and document data types. Basic data types include organizations, suppliers, employees, contracts, etc., usually referred to as basic data tables. The metadata of the basic data type is used to describe the basic data type, usually the fields in the basic data table. For example, the metadata of the basic data type "supplier" includes: supplier number, supplier name, legal representative, unified social credit code, etc. The data type of the document is a table related to the business, such as a material storage table. The metadata of the document data type is used to describe the document data type, which is generally a field in a table. For example, the metadata of the document data type "material storage" includes: warehouse number, warehouse location, material name, material quantity, storage time, etc. The initial tracking page information includes the initial metadata page name.

In this embodiment, in order to implement data tracking from business documents to metadata types, all traceable metadata types can be pre-registered in the target software system through the metadata registration function of the development tool platform, and each metadata type The metadata to which the data type can be traced is also registered one by one. Specifically, it is to register the tables (that is, the metadata type) and fields (that is, the metadata corresponding to the metadata type) in the database into the target software system one by one. Then define the corresponding initial tracking page information for each registered metadata type. The initial tracking page information includes the name, package, Chinese title, English title, Chinese business, etc. that are tracked to the initial metadata page. Wherein, the initial metadata page name is the built-in aspx name of the page. According to the initial tracking page information, define the initial metadata page corresponding to the metadata type, that is, define the initial style of displaying the page of each metadata of the metadata type. The initial metadata page is feature-rich, and all content on the page can be customized by the user. Users can also adjust the page layout according to their own needs during use.

Optionally, after registering the preset metadata type and its corresponding metadata in the target software system, it also includes: generating a configurable list according to the registered metadata type, and sending the configurable list to the manager; responding Based on the permission assignment operation of the administrator on the function permission assignment page, obtain the operation function permission of each user for each metadata type in the configurable list, and generate a list of function permissions; respond to the permission of the manager on the data permission assignment page Assign operations to obtain the data processing permissions of each user for each metadata type in the configurable list, and generate a list of data permissions.

In this embodiment, in order to protect the customer's private information or important information, it is necessary to set the operation function authority and data processing authority for each user, so as to restrict the user's ability to track and process data of different metadata types in the target software system. A configurable list can be generated according to all registered metadata types, and provided to the management personnel of the target software system, so that the management personnel can assign corresponding operation function rights and data processing rights to users using the target software system. Specifically, in response to the authority assignment operation of the administrator on the function authority allocation page, obtain the operation function authority of each user for each metadata type in the configurable list, for example, assign user A to have supplier information for the supplier metadata type View permissions and modify permissions for supplier information, and generate a list of functional permissions. Among them, whether the user has the operation function authority of a certain metadata type determines whether the user can use the function of tracking the metadata of the metadata type. By assigning the operation function authority to each user, it is convenient for the customer to control each metadata tracking process. user behavior. In response to the authority assignment operation of the administrator on the data authority assignment page, obtain the data processing authority of each user for each metadata type, for example, assign user A to the supplier metadata type to view suppliers that have business relationships with this department permission, as well as the permission to view suppliers in Jiangsu, Zhejiang and Shanghai, and generate a list of data permissions. Among them, whether the user has the data processing authority to hit the tracked metadata determines whether the user can use the corresponding data operation function on the tracked metadata. Among them, the administrator can modify the user's operation function authority and data processing authority according to the requirements on the function authority allocation page and the data authority allocation page.

S320. Obtain a data processing request initiated by the user on the target receipt page.

In this embodiment, the Add Tracking Data control can be set on the target document page. When the user clicks the Add Tracking Data control, a menu including all registered metadata types will pop up, and the user can select one or more metadata to be tracked in the menu. Data type, and add the selected metadata type to the menu list associated with the data tracking control on the target document page. When the user clicks the data tracking control, the associated menu list pops up, and when the user clicks on the target metadata type in the menu list, or when the user moves the mouse over the target metadata type in the menu list, the target metadata type is displayed. Operation function menus such as information addition, information viewing, information modification, and information deletion corresponding to the type. When the user clicks on a function option in the operation function menu, a data processing request corresponding to the target metadata type is generated, for example, a supplier information viewing request.

S330. If the user has the operation function authority matching the data processing request, determine the target metadata type corresponding to the data processing request.

In this embodiment, the user ID is obtained according to the data processing request, and all operation function permissions possessed by the user are found by querying the function authorization list according to the user ID. If it is found that the user has the target operation function authority consistent with the data processing request, for example, the supplier information viewing authority consistent with the supplier information view request is found, then the metadata type corresponding to the target operation function authority in the function authority list will be used as Target metadata type, used for tracking metadata. If it is found that the user does not have the target operation function authority consistent with the data processing request, this data processing request is ended.

S340. Acquire the name of the initial metadata page matching the target metadata type, and acquire the target metadata according to the metadata page whose page name is consistent with the initial page name.

In this embodiment, the system built-in initial metadata page name is found according to the target metadata type, and the first metadata page whose page name is the same as the initial metadata page name is queried. If the first metadata page includes the user-defined second metadata page, the data in the second metadata page is acquired as the target metadata. If the first metadata page does not include the user-defined second metadata page, the data in the initial metadata page built in the system is obtained as the target metadata.

S350. Generate and display a data processing page corresponding to the target metadata according to the user's data processing authority for the target metadata type.

In this embodiment, all data processing permissions of the user for the target metadata type are found by querying the data permission list, and it is determined whether there is a data processing permission for the target metadata that is hit and tracked. If not, end this data processing request. If it exists, a data processing page corresponding to the data processing request is automatically constructed according to the target metadata. Among them, the data processing page also includes buttons corresponding to various operation functions, and the initial state of the button is unavailable, you can search again for the operation function authority possessed by the user, and then compare the data processing page with the operation function authority possessed by the user The corresponding button is set to the available state, and the button corresponding to the operation function authority that the user does not have remains unavailable. Render the data processing page and display it to the user, so that the user can perform allowed data operations on the target metadata on the page.

The technical solution of the embodiment of the present invention obtains the data processing request initiated by the user on the target receipt page; if the user has the operation function authority matching the data processing request, then determines the target metadata type corresponding to the data processing request; according to the target metadata Data type, to obtain the target metadata to be processed; according to the user's data processing authority for the target metadata type, generate and display the data processing page corresponding to the target metadata, which solves the problem that the software system in related technologies cannot satisfy all customers' data tracking Analyze requirements, and automatically implement data tracking and processing from business documents to various metadata types.

Embodiment three

Fig. 4 is a schematic structural diagram of a metadata-based self-defined document traceability device provided according to Embodiment 3 of the present invention. As shown in Figure 4, the device includes:

A request acquisition module 410, configured to acquire a data processing request initiated by the user on the target receipt page;

The data type determination module 420 is configured to determine the target metadata type corresponding to the data processing request if the user has the operation function authority matching the data processing request;

A metadata acquisition module 430, configured to acquire target metadata to be processed according to the target metadata type;

The presentation module 440 is configured to generate and display a data processing page corresponding to the target metadata according to the user's data processing authority for the target metadata type.

The technical solution of the embodiment of the present invention obtains the data processing request initiated by the user on the target receipt page; if the user has the operation function authority matching the data processing request, then determines the target metadata type corresponding to the data processing request; according to the target metadata Data type, to obtain the target metadata to be processed; according to the user's data processing authority for the target metadata type, generate and display the data processing page corresponding to the target metadata, which solves the problem that the software system in related technologies cannot satisfy all customers' data tracking Analyze requirements, and automatically implement data tracking and processing from business documents to various metadata types.

Optionally, the data type determining module 420 is used for:

According to the user ID of the user, in the function authority list, query whether there is a target operation function authority matching the data processing request among the operation function authorities possessed by the user;

If it exists, obtain the metadata type corresponding to the target operation function permission in the function permission list as the target metadata type;

Wherein, the function permission list includes the association relationship between the user and the metadata type and the operation function permission on the metadata type.

Optionally, the metadata acquisition module 430 is configured to:

Get the initial metadata page name matching the target metadata type;

Querying the first metadata page whose page name is consistent with the name of the initial metadata page;

If there is a user-defined second metadata page in the first metadata page, then obtain the data in the second metadata page as the target metadata;

If there is no second metadata page configured by the user in the first metadata page, the data in the initial metadata page is acquired as the target metadata.

Optionally, demonstrate module 440 for:

Query the data permission list according to the user ID of the user, and obtain the data processing permission of the user for the target metadata type;

If the data processing authority matches the target metadata, a data processing page corresponding to the data processing request will be generated and displayed according to the target metadata;

Wherein, the data permission list includes the association relationship between the user and the metadata type and the data processing permission for the metadata type.

Optionally, also include:

The registration module is used to register the preset metadata type and its corresponding metadata in the target software system before obtaining the data processing request initiated by the user on the target receipt page;

The initial tracking page information and the initial metadata page matching each metadata type are respectively defined; the initial tracking page information includes the name of the initial metadata page.

Optionally, it also includes: a rights configuration module, configured to register the preset metadata type and its corresponding metadata in the target software system,

Generate configurable manifests based on registered metadata types and send configurable manifests to managers;

In response to the authority assignment operation of the administrator on the function authority allocation page, obtain the operation function authority of each user for each metadata type in the configurable list, and generate a function authority list;

In response to the authority allocation operation of the administrator on the data authority allocation page, the data processing authority of each user for each metadata type in the configurable list is obtained, and a data authority list is generated.

Optionally, the request acquisition module 410 is used for:

Displaying a menu list including at least one metadata type to be tracked in response to the user triggering the data tracking control on the target receipt page;

In response to the user's hit operation on the target metadata type in the menu list, display an operation function menu corresponding to the target metadata type;

A data processing request is generated in response to the user's hitting operation on a function option in the operation function menu.

The metadata-based custom document traceability device provided by the embodiments of the present invention can execute the metadata-based custom document traceability method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method.

Embodiment four

FIG. 5 shows a schematic structural diagram of an electronic device 10 that can be used to implement an embodiment of the present invention. Electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smartphones, wearable devices (eg, helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are by way of example only, and are not intended to limit implementations of the inventions described and/or claimed herein.

As shown in FIG. 5 , the electronic device 10 includes at least one processor 11 and a memory communicatively connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores There is a computer program executable by at least one processor, and the processor 11 can operate according to a computer program stored in a read-only memory (ROM) 12 or loaded from a storage unit 18 into a random-access memory (RAM) 13 Various appropriate actions and processes are performed. In the RAM 13, various programs and data necessary for the operation of the electronic device 10 are also stored. The processor 11 , ROM 12 , and RAM 13 are connected to each other through a bus 14 . An input/output (I/O) interface 15 is also connected to the bus 14 .

Multiple components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

Processor 11 may be various general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various dedicated artificial intelligence (AI) computing chips, various processors that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes various methods and processes described above, for example, a custom document traceability method based on metadata.

In some embodiments, the metadata-based custom document traceability method can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as the storage unit 18 . In some embodiments, part or all of the computer program may be loaded and/or installed on the electronic device 10 via the ROM 12 and/or the communication unit 19 . When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the metadata-based custom document traceability method described above can be executed. Alternatively, in other embodiments, the processor 11 may be configured in any other appropriate way (for example, by means of firmware) to execute a custom document traceability method based on metadata.

Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip Implemented in a system of systems (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor Can be special-purpose or general-purpose programmable processor, can receive data and instruction from storage system, at least one input device, and at least one output device, and transmit data and instruction to this storage system, this at least one input device, and this at least one output device an output device.

Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the computer program causes the functions/operations specified in the flowcharts and/or block diagrams to be implemented when executed by the processor. A computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer readable storage medium may be a tangible medium which may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus or device. A computer readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer readable storage medium may be a machine readable signal medium. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM or flash memory), fiber optics, compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

To provide for interaction with the user, the systems and techniques described herein can be implemented on an electronic device having a display device (for example, a CRT (cathode ray tube) or LCD (liquid crystal display)) for displaying information to the user monitor); and a keyboard and pointing device (eg, a mouse or a trackball) through which a user can provide input to an electronic device. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be in any form (including Acoustic input, voice input, or tactile input) to receive input from the user.

The systems and techniques described herein can be implemented on a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or web browser through which a user can interact with embodiments of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system can be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

A computing system can include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also known as a cloud computing server or a cloud host. It is a host product in the cloud computing service system to solve the problems of difficult management and weak business expansion in traditional physical hosts and VPS services. defect.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, each step described in the present invention may be executed in parallel, sequentially, or in a different order, as long as the desired result of the technical solution of the present invention can be achieved, there is no limitation herein.

The above specific implementation methods do not constitute a limitation to the protection scope of the present invention. It should be apparent to those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A metadata-based self-defined document tracing method is characterized by comprising the following steps:

acquiring a data processing request initiated by a user on a target bill page;

if the user has the operation function authority matched with the data processing request, determining a target metadata type corresponding to the data processing request;

acquiring target metadata to be processed according to the target metadata type;

And generating and displaying a data processing page corresponding to the target metadata according to the data processing permission of the user for the target metadata type.

2. The method of claim 1, wherein determining the target metadata type for the data processing request if the user has operational function rights that match the data processing request comprises:

according to the user identification of the user, inquiring whether a target operation function authority matched with the data processing request exists in the operation function authorities possessed by the user in a function authority list;

if yes, acquiring a metadata type corresponding to the target operation function authority in the function authority list as a target metadata type;

the function authority list comprises an association relation between a user and a metadata type and an operation function authority of the metadata type.

3. The method according to claim 1, wherein the obtaining target metadata to be processed according to the target metadata type includes:

acquiring an initial metadata page name matched with the target metadata type;

Querying a first metadata page with a page name consistent with the initial metadata page name;

if the second metadata page which is configured by the user in a user-defined mode exists in the first metadata page, acquiring data in the second metadata page as target metadata;

and if the second metadata page which is configured by the user in a self-defining way does not exist in the first metadata page, acquiring data in the initial metadata page as target metadata.

4. The method according to claim 1, wherein the generating and displaying the data processing page corresponding to the target metadata according to the data processing authority of the user for the target metadata type includes:

inquiring a data authority list according to the user identification of the user, and acquiring the data processing authority of the user for the target metadata type;

if the data processing permission is matched with the target metadata, generating a data processing page corresponding to the data processing request according to the target metadata, and displaying the data processing page;

the data authority list comprises an association relation between a user and a metadata type and between the user and data processing authorities of the metadata type.

5. The method of claim 1, further comprising, prior to said obtaining a data processing request initiated by a user on a target document page:

registering a preset metadata type and corresponding metadata in a target software system;

respectively defining initial tracking page information matched with each metadata type and an initial metadata page; the initial tracking page information includes an initial metadata page name.

6. The method according to claim 5, further comprising, after the registering of the preset metadata type and the corresponding metadata in the target software system:

generating a configurable list according to the registered metadata types, and sending the configurable list to a manager;

responding to the authority allocation operation of the manager on a function authority allocation page, acquiring the operation function authorities of each user aiming at each metadata type in the configurable list, and generating a function authority list;

and responding to the authority allocation operation of the manager on the data authority allocation page, acquiring the data processing authorities of all users aiming at all metadata types in the configurable list, and generating a data authority list.

7. The method of claim 1, wherein the obtaining a data processing request initiated by a user on a target document page comprises:

responding to the triggering operation of the user on the target document page on the data tracking control, and displaying a menu list comprising at least one metadata type to be tracked;

responding to the hit operation of the user on the target metadata type in the menu list, and displaying an operation function menu corresponding to the target metadata type;

and generating a data processing request in response to the hit operation of the user on the function options in the operation function menu.

8. The utility model provides a self-defining bill traceability device based on metadata which characterized in that includes:

the request acquisition module is used for acquiring a data processing request initiated by a user on a target bill page;

the data type determining module is used for determining a target metadata type corresponding to the data processing request if the user has the operation function authority matched with the data processing request;

the metadata acquisition module is used for acquiring target metadata to be processed according to the target metadata type;

And the display module is used for generating and displaying a data processing page corresponding to the target metadata according to the data processing permission of the user for the target metadata type.

9. An electronic device, the electronic device comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,,

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the metadata-based custom document tracing method of any one of claims 1-7.

10. A computer readable storage medium storing computer instructions for causing a processor to implement the metadata-based custom document tracing method of any one of claims 1-7 when executed.