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

Metadata-based self-defined document tracing method, device, equipment and medium Download PDF

Info

Publication number
CN116521488B
CN116521488B CN202310799874.7A CN202310799874A CN116521488B CN 116521488 B CN116521488 B CN 116521488B CN 202310799874 A CN202310799874 A CN 202310799874A CN 116521488 B CN116521488 B CN 116521488B
Authority
CN
China
Prior art keywords
metadata
target
user
data processing
page
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202310799874.7A
Other languages
Chinese (zh)
Other versions
CN116521488A (en
Inventor
舒元丰
石钟韶
金华利
朱世潮
王燕灵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou New China And Big Polytron Technologies Inc
Original Assignee
Hangzhou New China And Big Polytron Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou New China And Big Polytron Technologies Inc filed Critical Hangzhou New China And Big Polytron Technologies Inc
Priority to CN202310799874.7A priority Critical patent/CN116521488B/en
Publication of CN116521488A publication Critical patent/CN116521488A/en
Application granted granted Critical
Publication of CN116521488B publication Critical patent/CN116521488B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3086—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/121—Restricting unauthorised execution of programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Abstract

The invention relates to the technical field of data processing, and discloses a metadata-based self-defined document tracing method, device, equipment and medium. The method comprises 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. The technical scheme of the embodiment of the invention solves the problem that the software system in the related technology can not meet the data tracking analysis requirements of all clients, and can automatically realize the data tracking processing from business documents to various metadata types.

Description

Metadata-based self-defined document tracing method, device, equipment and medium
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a metadata-based self-defined document tracing method, apparatus, device, and medium.
Background
Various data tracking analysis requirements may be created by different customers during use of the software product, such as data tracking requirements from document to document and from document to underlying data. However, the commercialized software system cannot meet all the data trace analysis requirements set forth by all customers.
Disclosure of Invention
The invention provides a metadata-based self-defined document tracing method, device, equipment and medium, which can automatically realize data tracing processing from business documents to various metadata types.
According to an aspect of the present invention, there is provided a metadata-based self-defined document tracing method, including:
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 type of the target metadata;
and generating and displaying a data processing page corresponding to the target metadata according to the data processing authority of the user for the target metadata type.
Optionally, if the user has the operation function authority matched with the data processing request, determining the target metadata type corresponding to the data processing request includes:
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 authority 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.
Optionally, according to the type of the target metadata, acquiring the target metadata to be processed includes:
acquiring an initial metadata page name matched with a target metadata type;
querying a first metadata page with a page name consistent with the initial metadata page name;
if a second metadata page configured by user definition 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 user definition does not exist in the first metadata page, acquiring the data in the initial metadata page as target metadata.
Optionally, 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 a user identifier of a user, and acquiring a data processing authority of the user for a target metadata type;
if the data processing authority 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.
Optionally, before acquiring the data processing request initiated by the user on the target document page, the method further includes:
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.
Optionally, after registering the preset metadata type and the metadata corresponding to the preset metadata type in the target software system, the method further includes:
generating a configurable list according to the registered metadata types, and sending the configurable list to a manager;
responding to authority allocation operation of a manager on a function authority allocation page, acquiring operation function authorities of each user aiming at each metadata type in a 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 each user aiming at each metadata type in the configurable list, and generating a data authority list.
Optionally, the obtaining a data processing request initiated by the user on the target document page includes:
responding to the triggering operation of the data tracking control on the target bill page by a user, and displaying a menu list comprising at least one metadata type to be tracked;
responding to hit operation of a user on a target metadata type in a menu list, and displaying an operation function menu corresponding to the target metadata type;
in response to a hit operation of a user on a function option in the operation function menu, a data processing request is generated.
According to another aspect of the present invention, there is provided a metadata-based custom document tracing apparatus, including:
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 the data processing page corresponding to the target metadata according to the data processing permission of the user for the target metadata type.
According to another aspect of the present invention, there is provided an electronic apparatus including:
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 tracking method of any of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement the metadata-based custom document tracing method of any embodiment of the present invention when executed.
According to the technical scheme, the data processing request initiated by the user on the target bill page is acquired; 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 type of the target metadata; according to the data processing authority of a user aiming at the target metadata type, a data processing page corresponding to the target metadata is generated and displayed, the problem that a software system in the related technology cannot meet the data tracking analysis requirements of all clients is solved, and the data tracking processing from business documents to various metadata types is automatically realized.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a metadata-based custom document tracing method according to a first embodiment of the present invention;
FIG. 2 is a flow chart of an automatic implementation of a data tracking process according to an embodiment of the present invention;
FIG. 3 is a flowchart of another metadata-based custom document tracing method according to a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a metadata-based custom document tracing device according to a third embodiment of the present invention;
Fig. 5 is a schematic structural diagram of an electronic device for implementing the metadata-based custom document tracing method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "object," "first," "second," and the like in the description and the claims of the present invention and the above drawings are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of a metadata-based custom document tracing method according to an embodiment of the present invention, where the embodiment may be applicable to a case of tracing metadata of specified service data in a service document, where the method may be performed by a metadata-based custom document tracing device, where the device may be implemented in hardware and/or software, and where the device may be configured in an electronic device, for example, a terminal device in which a target software system is installed. As shown in fig. 1, the method includes:
s110, acquiring a data processing request initiated by a user on a target bill page.
The target bill can be a business bill generated by a user in the target software, such as a purchase warehouse entry bill. The target document includes business data of various metadata types, such as business data of "supplier" metadata types, business data of "operator" metadata types, business data of "warehouse" metadata types, and the like, included in the purchase inventory. The target bill page refers to a display page of the business bill. The data processing request may be a metadata tracking processing request initiated by a user for a metadata type corresponding to the specified service data in the target document, for example, a vendor information viewing request initiated by the user for vendor data in a purchase inventory, or a vendor information modification request, etc.
Optionally, the obtaining a data processing request initiated by the user on the target document page includes: responding to the triggering operation of the data tracking control on the target bill page by a user, and displaying a menu list comprising at least one metadata type to be tracked; responding to hit operation of a user on a target metadata type in a menu list, and displaying an operation function menu corresponding to the target metadata type; in response to a hit operation of a user on a 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 a user clicks the data tracking control on the target document page, a menu list is popped up, where the menu list includes all the traceable metadata types in the target document, or includes all the metadata types in the target document, where the traceable metadata types are displayed in an operable state and the non-traceable metadata types are displayed in an inoperable state. When the user clicks the target metadata type in the menu list or moves the mouse to the target metadata type in the menu list, the operation function menus such as information addition, information viewing, information modification, information deletion and the like corresponding to the target metadata type are displayed. When the user performs clicking operation on a certain function option in the operation function menu, a data processing request corresponding to the target metadata type is generated. Illustratively, if the user clicks on the "information view" function option in the operational function menu corresponding to the "vendor" metadata type, a vendor information view request is generated.
S120, if the user has the operation function authority matched with the data processing request, determining the target metadata type corresponding to the data processing request.
In this embodiment, whether a user can track metadata of one metadata type in response to a data processing request depends on whether the user has operation function authority of the corresponding metadata type. For example, metadata of a vendor metadata type may be tracked and provided to a user for modification in response to a vendor information modification request only if the user has vendor information modification rights.
Optionally, if the user has the operation function authority matched with the data processing request, determining the target metadata type corresponding to the data processing request includes: 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 authority possessed by the user in a function authority list; if so, acquiring the metadata type corresponding to the target operation function authority in the function authority list as a target metadata type.
In this embodiment, the function authority list includes an association relationship between a user and a metadata type and an operation function authority for the metadata type. Illustratively, user A-vendor information review, vendor information modification. As shown in fig. 2, after a data processing request of a user is acquired, a user identifier is acquired according to the data processing request, all operation function rights possessed by the user are found according to a user identifier query function rights list, and the data processing request is compared with the operation function rights possessed by the user. If the target operation function authority which is consistent in comparison is found, the user has authority to use the metadata tracking function, and at the moment, the metadata type corresponding to the target operation function authority in the function authority list can be used as the target metadata type for tracking metadata. If the target operation function authority which is consistent in comparison is not found, the user does not have the authority to use the metadata tracking function, and the data processing request can be ended.
S130, acquiring target metadata to be processed according to the target metadata type.
The target metadata to be processed are description information of business data of the target metadata type in the target document page. For example, the target metadata type is "provider", and the service data corresponding to the metadata type "provider" in the target document page is "company B", so that the target metadata may include information such as unit code, unit name, unit abbreviation, location area, legal representative, operation range and the like of company B.
Optionally, according to the type of the target metadata, acquiring the target metadata to be processed includes: acquiring an initial metadata page name matched with a target metadata type; querying a first metadata page with a page name consistent with the initial metadata page name; if a second metadata page configured by user definition 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 user definition does not exist in the first metadata page, acquiring the data in the initial metadata page as target metadata.
In this embodiment, as shown in fig. 2, after determining a target metadata type corresponding to a data processing request, the initial metadata page name built in the system is found according to the target metadata type, and the first metadata page with the page name being the initial metadata page name is queried. The first metadata page at least comprises an initial metadata page built in the system, and because the user can perform custom configuration on the initial metadata page and the custom metadata page name is the same as the initial metadata page name, the first metadata page may also comprise metadata pages configured by different users. Further inquiring whether a second metadata page which is configured by user definition exists in the first metadata page, and if so, acquiring data in the second metadata page as target metadata. If not, the data in the initial metadata page is acquired as target metadata.
And S140, generating and displaying a data processing page corresponding to the target metadata according to the data processing authority of the user for the target metadata type.
In this embodiment, whether the user can use the corresponding data manipulation function for the tracked metadata depends on whether the user has data processing authority that can hit the metadata. For example, if the user has data processing authority to view the provider associated with the home gate, and the obtained provider information is tracked to just belong to the provider associated with the home gate according to the type of the target metadata, the user may view the obtained target metadata.
Optionally, 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 a user identifier of a user, and acquiring a data processing authority of the user for a target metadata type; and 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.
In this embodiment, the data authority list includes an association relationship between a user and a metadata type and a data processing authority for the metadata type. Illustratively, user A-vendor-views vendor information associated with this division, views vendor information for Jiang Zhe Hu. As shown in fig. 2, after target metadata to be processed is acquired according to a target metadata type, a data authority list is queried according to a user identifier, all data processing authorities possessed by the user for the target metadata type are found, and whether the data processing authorities hit the tracked target metadata exist or not is determined. If the data processing request exists, the user has permission to perform corresponding data operation on the target metadata, a data processing page corresponding to the data processing request can be automatically constructed according to the target metadata, the page is rendered and then displayed to the user, and therefore the user can conveniently perform data operation allowed by operation function permission on the target metadata on the page. If the data is not available, the user does not have permission to perform corresponding data operation on the target metadata, and the data processing request can be ended.
According to the technical scheme, the data processing request initiated by the user on the target bill page is acquired; 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 type of the target metadata; according to the data processing authority of a user aiming at the target metadata type, a data processing page corresponding to the target metadata is generated and displayed, the problem that a software system in the related technology cannot meet the data tracking analysis requirements of all clients is solved, and the data tracking processing from business documents to various metadata types is automatically realized.
Example two
Fig. 3 is a flowchart of another metadata-based custom document tracing method according to a second embodiment of the present invention, where the data tracing process from a business document to a specified metadata type is further explained on the basis of the above embodiment. As shown in fig. 3, the method includes:
s310, registering preset metadata types and corresponding metadata thereof in a target software system, and respectively defining initial tracking page information and initial metadata pages matched with the metadata types.
Wherein the metadata types include a base data type and a document data type. The underlying data types include organizations, suppliers, employees, contracts, etc., and are commonly referred to as underlying data tables. Metadata of the underlying data type is used to describe the underlying data type in relation, typically as a field in an underlying data table. For example, metadata of the base data type "vendor" includes: vendor number, vendor name, legal representative, unified social credit code, etc. The document data type is a business related table such as a materials warehouse entry table. The metadata of the document data type is used to describe the document data type in relation, typically the fields in a table. For example, metadata for the document data type "materials warehouse entry" includes: warehouse number, warehouse location, material name, material quantity, warehouse time, etc. The initial tracking page information includes an initial metadata page name.
In this embodiment, in order to implement the data tracking process from the business document to the metadata type, all the trackable metadata types may be registered in the target software system in advance through the metadata registration function of the development tool platform, and metadata that each metadata type may be tracked may be registered one by one. Specifically, tables (i.e., metadata types) and fields (i.e., metadata corresponding to the metadata types) in the database are registered in the target software system one by one. And then respectively defining corresponding initial tracking page information aiming at each registered metadata type, wherein the initial tracking page information comprises the name, suite, chinese title, english title, chinese service and the like of the tracked initial metadata page. The initial metadata page name is a page built-in aspx name. According to the initial tracking page information, an initial metadata page corresponding to the metadata type is defined, namely, a page display initial style of each metadata of the metadata type is defined. The initial metadata page is rich in function, and all contents in the page can be customized by users. The user can also adjust the page typesetting according to the own needs in the using process.
Optionally, after registering the preset metadata type and the metadata corresponding to the preset metadata type in the target software system, the method further includes: generating a configurable list according to the registered metadata types, and sending the configurable list to a manager; responding to authority allocation operation of a manager on a function authority allocation page, acquiring operation function authorities of each user aiming at each metadata type in a 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 each user aiming at each metadata type in the configurable list, and generating a data authority list.
In this embodiment, in order to protect private information or important information of a client, operation function rights and data processing rights need to be set for each user to restrict the data tracking processing capability of the user for different metadata types in the target software system. A configurable manifest may be generated from all metadata types registered and provided to an administrator of the target software system to assign corresponding operational function rights and data processing rights to users using the target software system by the administrator. Specifically, in response to the authority allocation operation of the manager on the function authority allocation page, the operation function authority of each user for each metadata type in the configurable list is obtained, for example, the allocation user a has the provider information viewing authority and the provider information modification authority for the provider metadata type, and a function authority list is generated. Whether the user has operation function authority of a certain metadata type or not is determined, whether the user can use the function of tracking metadata of the metadata type or not is determined, and the user is convenient to control the behavior of each user in the metadata tracking process by distributing the operation function authority to each user. And responding to the authority allocation operation of the manager on the data authority allocation page, acquiring the data processing authority of each user for each metadata type, for example, allocating the authority of the user A to the provider with the business relation with the local gate for the provider metadata type, and checking the authority of the provider of Jiangzhe Shanghai, and generating a data authority list. Whether the user has the data processing authority capable of hitting the tracked metadata or not determines whether the user can use the corresponding data operation function for the tracked metadata or not. The manager can modify the operation function authority and the data processing authority of the user according to the requirements on the function authority distribution page and the data authority distribution page.
S320, acquiring a data processing request initiated by a user on a target document page.
In this embodiment, an add tracking data control may be set in the target document page, and when the user clicks the add tracking data control, a menu including all registered metadata types is popped up, and the user selects one or more metadata types that want to be tracked in the menu, and adds the selected metadata types to a menu list associated with the data tracking control of the target document page. When the user clicks the data tracking control, the associated menu list is popped up, and when the user clicks the target metadata type in the menu list or moves the mouse onto the target metadata type in the menu list, the operation function menus such as information addition, information viewing, information modification, information deletion and the like corresponding to the target metadata type are displayed. When the user performs a click operation on a certain function option in the operation function menu, a data processing request corresponding to the target metadata type, for example, a vendor information viewing request is generated.
S330, if the user has the operation function authority matched with the data processing request, determining the target metadata type corresponding to the data processing request.
In this embodiment, a user identifier is obtained according to a data processing request, and all operation function rights possessed by the user are found according to a function rights list queried by the user identifier. If the user is inquired to have the target operation function authority consistent with the data processing request, for example, the supplier information viewing authority consistent with the supplier information viewing request is inquired, the metadata type corresponding to the target operation function authority in the function authority list is used as the target metadata type for tracking metadata. If the user is inquired that the user does not have the target operation function authority consistent with the data processing request, the data processing request is ended.
S340, acquiring an initial metadata page name matched with the target metadata type, and acquiring the target metadata according to the metadata page with the page name consistent with the initial page name.
In this embodiment, an initial metadata page name built in the system is found according to the target metadata type, and a first metadata page with the same page name as the initial metadata page name is queried. And if the first metadata page comprises the second metadata page which is configured by user definition, acquiring data in the second metadata page as target metadata. And if the first metadata page does not comprise the second metadata page which is configured by user definition, acquiring data in an initial metadata page built in the system as target metadata.
S350, 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.
In this embodiment, by querying the data authority list, all the data processing authorities that the user has for the target metadata type are found, and it is determined whether there is a data processing authority that hits the tracked target metadata. If not, the data processing request is ended. If so, automatically constructing a data processing page corresponding to the data processing request according to the target metadata. The data processing page further comprises buttons corresponding to various operation functions, the initial state of the buttons is an unavailable state, operation function authorities possessed by a user can be searched again, then the buttons corresponding to the operation function authorities possessed by the user in the data processing page are set to be available states, and the buttons corresponding to the operation function authorities not possessed by the user are kept in the unavailable states. Rendering the data processing page and displaying the data processing page to a user so as to facilitate the user to perform allowable data operation on the target metadata on the page.
According to the technical scheme, the data processing request initiated by the user on the target bill page is acquired; 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 type of the target metadata; according to the data processing authority of a user aiming at the target metadata type, a data processing page corresponding to the target metadata is generated and displayed, the problem that a software system in the related technology cannot meet the data tracking analysis requirements of all clients is solved, and the data tracking processing from business documents to various metadata types is automatically realized.
Example III
Fig. 4 is a schematic structural diagram of a metadata-based custom document tracing device according to a third embodiment of the present invention. As shown in fig. 4, the apparatus includes:
a request acquisition module 410, configured to acquire a data processing request initiated by a user on a target document page;
a data type determining module 420, configured to determine a target metadata type corresponding to the data processing request if the user has an operation function right that matches the data processing request;
the metadata acquisition module 430 is configured to acquire target metadata to be processed according to a target metadata type;
and the display module 440 is used for 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.
According to the technical scheme, the data processing request initiated by the user on the target bill page is acquired; 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 type of the target metadata; according to the data processing authority of a user aiming at the target metadata type, a data processing page corresponding to the target metadata is generated and displayed, the problem that a software system in the related technology cannot meet the data tracking analysis requirements of all clients is solved, and the data tracking processing from business documents to various metadata types is automatically realized.
Optionally, the data type determining module 420 is configured to:
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 authority 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.
Optionally, the metadata acquisition module 430 is configured to:
acquiring an initial metadata page name matched with a target metadata type;
querying a first metadata page with a page name consistent with the initial metadata page name;
if a second metadata page configured by user definition 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 user definition does not exist in the first metadata page, acquiring the data in the initial metadata page as target metadata.
Optionally, the display module 440 is configured to:
inquiring a data authority list according to a user identifier of a user, and acquiring a data processing authority of the user for a target metadata type;
If the data processing authority 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.
Optionally, the method further comprises:
the registration module is used for registering a preset metadata type and corresponding metadata thereof in the target software system before acquiring a data processing request initiated by a user on a target bill page;
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.
Optionally, the method further comprises: the authority configuration module is used for registering 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 authority allocation operation of a manager on a function authority allocation page, acquiring operation function authorities of each user aiming at each metadata type in a 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 each user aiming at each metadata type in the configurable list, and generating a data authority list.
Optionally, the request acquisition module 410 is configured to:
responding to the triggering operation of the data tracking control on the target bill page by a user, and displaying a menu list comprising at least one metadata type to be tracked;
responding to hit operation of a user on a target metadata type in a menu list, and displaying an operation function menu corresponding to the target metadata type;
in response to a hit operation of a user on a function option in the operation function menu, a data processing request is generated.
The metadata-based self-defined document tracing device provided by the embodiment of the invention can execute the metadata-based self-defined document tracing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 5 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant 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, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various 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, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the metadata-based custom document tracing method.
In some embodiments, the metadata-based custom document tracing method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the metadata-based custom document tracing method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the metadata-based custom document tracing method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The 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 that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (8)

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; the data processing request is a metadata tracking processing request initiated aiming at a metadata type corresponding to the specified service data in the target bill;
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; the target metadata is descriptive information of service data specified in the target document page;
generating and displaying a data processing page corresponding to the target metadata according to the data processing authority of the user for the target metadata type;
wherein if the user has the operation function authority matched with the data processing request, determining the target metadata type corresponding to the data processing request comprises the following steps:
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;
the generating and displaying the data processing page corresponding to the target metadata according to the data processing permission 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; the data processing authority is used for determining whether the corresponding data operation function can be used for the target metadata.
2. 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.
3. 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.
4. A method according to claim 3, 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.
5. 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.
6. 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 processing request is a metadata tracking processing request initiated aiming at a metadata type corresponding to the specified service data in the target bill;
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; the target metadata is descriptive information of service data specified in the target document page;
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;
wherein, the data type determining module is used for:
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;
the generating and displaying the data processing page corresponding to the target metadata according to the data processing permission 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; the data processing authority is used for determining whether the corresponding data operation function can be used for the target metadata.
7. 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-5.
8. 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-5 when executed.
CN202310799874.7A 2023-07-03 2023-07-03 Metadata-based self-defined document tracing method, device, equipment and medium Active CN116521488B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310799874.7A CN116521488B (en) 2023-07-03 2023-07-03 Metadata-based self-defined document tracing method, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310799874.7A CN116521488B (en) 2023-07-03 2023-07-03 Metadata-based self-defined document tracing method, device, equipment and medium

Publications (2)

Publication Number Publication Date
CN116521488A CN116521488A (en) 2023-08-01
CN116521488B true CN116521488B (en) 2024-03-26

Family

ID=87403273

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310799874.7A Active CN116521488B (en) 2023-07-03 2023-07-03 Metadata-based self-defined document tracing method, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN116521488B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112364110A (en) * 2020-11-17 2021-02-12 深圳前海微众银行股份有限公司 Metadata management method, device and equipment and computer storage medium
CN113885985A (en) * 2021-09-29 2022-01-04 平安国际智慧城市科技股份有限公司 Page rendering method, device, equipment and medium based on dynamic authority control
CN114372240A (en) * 2022-01-11 2022-04-19 平安普惠企业管理有限公司 Data acquisition method, device, terminal and computer readable storage medium
CN114528504A (en) * 2022-02-21 2022-05-24 北京达佳互联信息技术有限公司 Data processing method, device, electronic equipment and medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108280365B (en) * 2017-09-19 2019-04-12 平安科技（深圳）有限公司 Data access authority management method, device, terminal device and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112364110A (en) * 2020-11-17 2021-02-12 深圳前海微众银行股份有限公司 Metadata management method, device and equipment and computer storage medium
CN113885985A (en) * 2021-09-29 2022-01-04 平安国际智慧城市科技股份有限公司 Page rendering method, device, equipment and medium based on dynamic authority control
CN114372240A (en) * 2022-01-11 2022-04-19 平安普惠企业管理有限公司 Data acquisition method, device, terminal and computer readable storage medium
CN114528504A (en) * 2022-02-21 2022-05-24 北京达佳互联信息技术有限公司 Data processing method, device, electronic equipment and medium

Also Published As

Publication number Publication date
CN116521488A (en) 2023-08-01

Similar Documents

Publication Publication Date Title
CN107798038B (en) Data response method and data response equipment
EP3657358A1 (en) Method, device and system for persistent data processing, and readable storage medium
CN111695156A (en) Service platform access method, device, equipment and storage medium
CN110716951B (en) Label configuration method, device and equipment convenient to configure and storage medium
US20150347630A1 (en) Method, apparatus, and system for processing call requests
CN109491733B (en) Interface display method based on visualization and related equipment
CN111460496A (en) Permission configuration method based on user role, electronic device and storage medium
CN113282591A (en) Authority filtering method and device, computer equipment and storage medium
CN116521488B (en) Metadata-based self-defined document tracing method, device, equipment and medium
US10313284B1 (en) Upload and share files to a sharing service using a messaging client
CN108197253B (en) Equipment query method, device and equipment of cloud monitoring platform
CN111752964A (en) Data processing method and device based on data interface
US10104007B1 (en) Stored views of web service application programming interfaces (APIs)
CN114153438A (en) API automatic generation system
CN110532457B (en) Method and system for acquiring network segment ID
KR20180007792A (en) Apparatus and method for providing data based on cloud service
WO2015183900A1 (en) Method, apparatus, and system for processing call requests
CN112256820A (en) Document positioning method and device
CN114143187B (en) Intelligent platform interface network address management method, system, terminal and storage medium
US11436214B2 (en) Preventing search fraud
CN117632161A (en) Terminal software processing method and device and electronic equipment
CN113779551A (en) Authority management method and device
CN112561629A (en) Method and device for processing household orders
CN116451272A (en) Git-based code library control method and device and electronic equipment
CN113568541A (en) Page function determination method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant