Archive data display method and device, equipment, storage medium and program product
By obtaining and analyzing user permission data and finely controlling the display of archive data, the security problem of archive data caused by the confusion of permission management logic in the existing technology is solved, and higher security is achieved.
Patent Information
- Application Number
- CN202411994030.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-31
- Publication Date
- 2025-04-22
AI Technical Summary
In the prior art, the permission management logic is chaotic, complex or missing, resulting in the security of archival data being unable to be guaranteed.
By obtaining the permission data of the current user, including node permission records, function button permission records and data permission records, the permission information of each node in the entire tree is determined based on these records, and the display of archive data is controlled.
A refined permission management is realized to ensure that users only see authorized content, thereby improving the security of archive data.
Smart Images
Figure CN119862156A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, device, equipment, storage medium and program product for displaying archive data. Background Art
[0002] As enterprises are becoming more and more popular with the informatization of archive management, more and more enterprises are gradually increasing their requirements for the authority management of archive management. However, in the prior art, due to the confusion of authority management logic, the complexity of authority management or the lack of authority conditions, the security of archive data cannot be guaranteed. Summary of the invention
[0003] The present application provides a method, apparatus, device, storage medium and program product for displaying archival data, which realizes refined permission management, can accurately control the display of archival data, ensure that users only see authorized content, and thus improve the security of archival data.
[0004] In a first aspect, an embodiment of the present application provides a method for displaying archival data, comprising: obtaining permission data of the current user; wherein the permission data comprises node permission records, function button permission records and data permission records; determining node permission information of each node in the entire archive tree based on the node permission records; determining function button permission information of each module under each node based on the function button permission records; determining rule permission information of each module under each node based on the data permission records; and displaying corresponding archival data based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module.
[0005] In a second aspect, an embodiment of the present application also provides a display device for archival data, comprising: a permission data acquisition module, used to acquire the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records; a node permission information determination module, used to determine the node permission information of each node in the entire archive tree based on the node permission records; a function button permission information determination module, used to determine the function button permission information of each module under each node based on the function button permission records; a rule permission information determination module, used to determine the rule permission information of each module under each node based on the data permission records; and an archival data display module, used to display the corresponding archival data based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module.
[0006] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for displaying archival data as described in the embodiment of the present application.
[0007] In a fourth aspect, an embodiment of the present application further provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute the method for displaying archival data as described in the embodiment of the present application.
[0008] In a fifth aspect, an embodiment of the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the method for displaying archival data as described in the embodiment of the present application.
[0009] The technical solution of the embodiment of the present application obtains the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records; node permission information of each node in the entire archive tree is determined based on the node permission records; function button permission information of each module under each node is determined based on the function button permission records; rule permission information of each module under each node is determined based on the data permission records; corresponding archive data is displayed based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module. The embodiment of the present application realizes refined permission management, can accurately control the display of archive data, ensure that users only see authorized content, and thus improve the security of archive data. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.
[0011] Figure 1 A schematic diagram of a method for displaying archive data provided in an embodiment of the present application;
[0012] Figure 2 A schematic diagram of the structure of a display device for archive data provided in an embodiment of the present application;
[0013] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0014] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0015] It should be understood that the various steps recorded in the method implementation of the present disclosure can be performed in different orders and / or in parallel. In addition, the method implementation may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect. The term "including" and its variations used herein are open inclusions, that is, "including but not limited to". It should be noted that the concepts of "first", "second", etc. mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units. It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative and not restrictive, and those skilled in the art should understand that unless otherwise clearly stated in the context, it should be understood as "one or more". It is understandable that the data involved in the present technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of the corresponding laws, regulations and relevant provisions.
[0016] It should be noted that the technical solution provided in the embodiment of the present invention is applied to the Electronic Document and Records Management System (EDRMS) to manage the permissions involved in the EDRMS archive management system.
[0017] Figure 1 The present invention provides a flow chart of a method for displaying archive data provided by an embodiment of the present invention. The method can be executed by an archive data display device, which can be implemented in the form of software and / or hardware, and optionally, by an electronic device, which can be a mobile terminal, a PC, or a server. Figure 1 As shown, the method includes:
[0018] S110: Obtain the authority data of the current user.
[0019] The permission data includes node permission records, function button permission records and data permission records.
[0020] Among them, the node permission record can be represented by the first permission configuration table, which records the node permission information of each user for each node. The first permission configuration table is used to store the node permission relationship between users and nodes. The first permission configuration table includes user identity information and node identity information as well as node permission information between users and nodes, such as user A has permission for node A. The function button permission record can be represented by the second permission configuration table, which records the function button permission information of each user for each module. The second permission configuration table is used to store the function button permission relationship between users and modules. The second permission configuration table includes user identity information and module identity information as well as function button permission information between users and modules, such as user A has permission for function button A and function button B in module A. The data permission record can be represented by the third permission configuration table, which records the rule permission information of each user for each module. The third permission configuration table is used to store the data permission relationship between users and modules. The third permission configuration table includes user identity information and module identity information as well as rule permission information between users and modules, such as user A has 30-day viewing permission for archive data of module A.
[0021] In this embodiment, the permission data in the database can be loaded into the cache in advance, and when the current user logs into the EDRMS archive management system, the permission data of the current user is directly obtained from the cache.
[0022] Optionally, obtaining the permission data of the current user includes: reading the node permission record of the current user from a first permission configuration table in the cache; reading the function button permission record of the current user from a second permission configuration table in the cache; and reading the data permission record of the current user from a third permission configuration table in the cache.
[0023] In this embodiment, the node permission record of the current user is read from the first permission configuration table in the cache; the function button permission record of the current user is read from the second permission configuration table in the cache; and the data permission record of the current user is read from the third permission configuration table in the cache. This method can improve the efficiency of reading permissions.
[0024] Optionally, after displaying the corresponding archive data based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module, it also includes: if the permission records in the first permission configuration table, the second permission configuration table and / or the third permission configuration table in the cache are changed, clearing the cache; loading the changed first permission configuration table, the changed second permission configuration table and / or the changed third permission configuration table into the cache, so that the latest permission data can be obtained from the cache next time.
[0025] Exemplarily, if the permission record in the first permission configuration table in the cache changes, the cache of the first permission configuration table is cleared; if the permission record in the second permission configuration table in the cache changes, the cache of the second permission configuration table is cleared; if the permission record in the third permission configuration table in the cache changes, the cache of the third permission configuration table is cleared.
[0026] Exemplarily, the changed first permission configuration table is loaded into the cache, so that the latest permission data can be obtained from the cache next time.
[0027] Exemplarily, the changed second permission configuration table is loaded into the cache, so that the latest permission data can be obtained from the cache next time.
[0028] Exemplarily, the changed third permission configuration table is loaded into the cache, so that the latest permission data can be obtained from the cache next time.
[0029] S120. Determine the node authority information of each node in the entire tree based on the node authority record.
[0030] The fonds tree can be understood as a tree data structure. The fonds tree includes a fonds node (i.e., a top-level node, which is a virtual node) and multiple child nodes of the fonds node. It should be noted that the nodes in the subsequent embodiments are child nodes of the fonds node.
[0031] In this embodiment, the node permission information of each node in the entire tree can be determined by the permission data of the current user (such as the node permission record), or the node permission information of each node in the entire tree can be determined by the role permission data or the department permission data.
[0032] Optionally, the node permission information of each node in the entire tree is determined based on the node permission record, including: for each node, if the node permission record includes the identity information corresponding to the current user and includes the identity information of the node, then the node permission information of the node in the node permission record is used as the node permission information of the node; for each node, if the node permission record includes the identity information corresponding to the current user and does not include the identity information of the node, then the node permission information of the node is determined based on the node path corresponding to the node; if the node permission record does not include the identity information corresponding to the current user, then the node permission information of the node is determined based on the role permission data or department permission data associated with the current user.
[0033] In this embodiment, for each node, if the node authority record includes the identity information corresponding to the current user and the identity information of the node, it means that the node has authority, and the node authority information of the node in the node authority record can be directly used as the node authority information of the node. Node authority information can be understood as having node authority. For each node, if the node authority record includes the identity information corresponding to the current user and does not include the identity information of the node, it means that the node has no authority, and the node authority information of the node can be determined based on the node path corresponding to the node, that is, the node authority information is queried from multiple upper nodes of the node. If the node in the node path has node authority information, it can be considered that the node has authority, which is equivalent to the node inheriting the authority of the upper node. If the node authority record does not include the identity information corresponding to the current user, the node authority information of the node is determined based on the role authority data or department authority data associated with the current user. For example, if the role authority data of the current user has the node authority information of the node, it can be considered that the node has authority; if the department authority data of the current user has the node authority information of the node, it can be considered that the node has authority.
[0034] The node path includes the node and multiple upper-level nodes of the node.
[0035] Optionally, the node authority information of the node is determined based on the node path corresponding to the node, including: traversing from the node to the multiple upper-level nodes in sequence; during the traversal process, if the node authority record includes the identity information of the traversed node, then the node authority information of the traversed node in the node authority record is used as the node authority information of the node.
[0036] Exemplarily, the node path takes node 1, node 2, and node 3 as an example, node 3 represents the current node (the node authority record does not include the identity information of the current node), and node 2 and node 1 are the superior nodes of node 3. If the node authority record includes the identity information of node 2, the node authority information of node 2 in the node authority record is used as the node authority information of node 3. If the node authority record does not include the identity information of node 2, node 1 is traversed, and if the node authority record includes the identity information of node 1, the node authority information of node 1 in the node authority record is used as the node authority information of node 3.
[0037] In this embodiment, by traversing the upper-level nodes and taking the permissions of the upper-level nodes as the permissions of the current node, it is possible to implement inheritance of permissions between hierarchical nodes, thereby reducing the complexity of permission configuration and optimizing permission logic. There is no need to configure permissions for each node, thereby reducing the amount of permission configuration data, achieving flexible configuration of permissions, and effectively enhancing data security.
[0038] Optionally, the node permission information of the node is determined based on the role permission data or department permission data associated with the current user, including: if the role permission data includes the identity information of the node, then the node permission information of the node in the role permission data is used as the node permission information of the node; or; if the department permission data includes the identity information of the node, then the node permission information of the node in the department permission data is used as the node permission information of the node.
[0039] In this embodiment, there is no restriction on the role, for example, it can be a team leader, manager, director, etc. In this embodiment, there is no restriction on the department, as long as it is the department where the current user is located.
[0040] In this embodiment, if the role authority data includes the identity information of the node, the node authority information of the node in the role authority data is used as the node authority information of the node; if the role authority data does not include the identity information of the node, the node authority information of the node is determined based on the department authority data associated with the current user. If the department authority data includes the identity information of the node, the node authority information of the node in the department authority data is used as the node authority information of the node, thereby improving the efficiency and flexibility of authority reading.
[0041] S130. Determine function button permission information of each module under each node based on the function button permission record.
[0042] In this embodiment, the function button permission information of each node in the entire tree can be determined by the current user's permission data (such as function button permission record), or the function button permission information of each node in the entire tree can be determined by role permission data or department permission data.
[0043] Optionally, the function button permission information of each module under each node is determined based on the function button permission record, including: for each module, if the function button permission record includes the identity information corresponding to the current user and the identity information of the module, then the function button permission information of the module in the function button permission record is used as the function button permission information of the module; for each module, if the function button permission record includes the identity information corresponding to the current user and does not include the identity information of the module, then the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the function button permission record does not include the identity information corresponding to the current user, then the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0044] It should be noted that each node includes multiple modules, and each module has multiple function buttons. For example, the module may be an archive collection module, a department sorting module, etc. The function buttons may include a file adding button, a file duplicate checking button, a file deleting button, a file browsing button, etc.
[0045] In this embodiment, for each module, if the function button permission record includes the identity information corresponding to the current user and the identity information of the module, the function button permission information of the module in the function button permission record is used as the function button permission information of the module (a module can include the permission information of at least one function button, that is, at least one function button has permission); for each module, if the function button permission record includes the identity information corresponding to the current user and does not include the identity information of the module, the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the function button permission record does not include the identity information corresponding to the current user, the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0046] Exemplarily, the specific process of determining the function button permission information of the module based on the role permission data or department permission data associated with the current user is as follows: if the role permission data includes the identity information of the module, the function button permission information of the module in the role permission data is used as the function button permission information of the module; if the role permission data does not include the identity information of the module, the function button permission information of the module is determined based on the department permission data associated with the current user. If the department permission data includes the identity information of the module, the function button permission information of the module in the department permission data is used as the function button permission information of the module.
[0047] S140. Determine the rule permission information of each module under each node based on the data permission record.
[0048] In this embodiment, the rule permission information of each node in the entire tree can be determined by the permission data of the current user (ie, data permission record), or the rule permission information of each node in the entire tree can be determined by the role permission data or department permission data.
[0049] Optionally, the rule permission information of each module under each node is determined based on the data permission record, including: for each module, if the data permission record includes the identity information corresponding to the current user and the identity information of the module, then the rule permission information of the module in the data permission record is used as the rule permission information of the module; for each module, if the data permission record includes the identity information corresponding to the current user and does not include the identity information of the module, then the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the data permission record does not include the identity information corresponding to the current user, then the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0050] In this embodiment, there is no restriction on the rule permission information, for example, it may include the validity period of data viewing. In this embodiment, for each module, if the data permission record includes the identity information corresponding to the current user and the identity information of the module, the rule permission information of the module in the data permission record is used as the rule permission information of the module; for each module, if the data permission record includes the identity information corresponding to the current user and does not include the identity information of the module, the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the data permission record does not include the identity information corresponding to the current user, the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0051] Exemplarily, the specific process of determining the rule permission information of the module based on the role permission data or department permission data associated with the current user is as follows: if the role permission data includes the identity information of the module, the rule permission information of the module in the role permission data is used as the rule permission information of the module; if the role permission data does not include the identity information of the module, the rule permission information of the module is determined based on the department permission data associated with the current user. If the department permission data includes the identity information of the module, the rule permission information of the module in the department permission data is used as the rule permission information of the module.
[0052] In this embodiment, when reading or configuring the rule permission information of the current module of the current node, the metadata of all the upper nodes of the current node can be selected as the rule permission information of the current module to achieve flexible configuration of rule permissions. The source of metadata can include case files, files, electronic originals, and specific metadata can include file number, confidentiality level, original serial number, creation date, creation mark, etc.
[0053] S150: Display corresponding archive data based on the node authority information of each node, the function button authority information of each module, and the rule authority information of each module.
[0054] In this embodiment, the corresponding nodes can be displayed based on the node permission information of each node, that is, the nodes with permission can be displayed, and the corresponding function buttons can be displayed based on the function button permission information of each module, that is, the function buttons with permission under each module can be displayed. The corresponding archive data can be displayed based on the rule permission information of each module, that is, the archive data with permission can be displayed.
[0055] The technical solution of the embodiment of the present application obtains the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records; node permission information of each node in the entire archive tree is determined based on the node permission records; function button permission information of each module under each node is determined based on the function button permission records; rule permission information of each module under each node is determined based on the data permission records; corresponding archive data is displayed based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module. The embodiment of the present application realizes refined permission management, can accurately control the display of archive data, ensure that users only see authorized content, and thus improve the security of archive data.
[0056] Figure 2 A schematic diagram of a display device for archive data provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the device includes: an authority data acquisition module 210, a node authority information determination module 220, a function button authority information determination module 230, a rule authority information determination module 240 and a file data display module 250;
[0057] The permission data acquisition module 210 is used to acquire the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records;
[0058] A node authority information determination module 220, for determining the node authority information of each node in the fonds tree based on the node authority record;
[0059] A function button permission information determination module 230, configured to determine the function button permission information of each module under each node based on the function button permission record;
[0060] A rule permission information determination module 240, configured to determine the rule permission information of each module under each node based on the data permission record;
[0061] The archive data display module 250 is used to display corresponding archive data based on the node authority information of each node, the function button authority information of each module and the rule authority information of each module.
[0062] The technical solution of the embodiment of the present application obtains the permission data of the current user through the permission data acquisition module; wherein the permission data includes node permission records, function button permission records and data permission records; the node permission information determination module determines the node permission information of each node in the entire tree based on the node permission records; the function button permission information determination module determines the function button permission information of each module under each node based on the function button permission records; the rule permission information determination module determines the rule permission information of each module under each node based on the data permission records; the archive data display module displays the corresponding archive data based on the node permission information of each node, the function button permission information of each module and the rule permission information of each module. The embodiment of the present application realizes refined permission management, can accurately control the display of archive data, ensure that users only see authorized content, and thus improve the security of archive data.
[0063] Optionally, the permission data acquisition module is specifically used to: read the node permission record of the current user from the first permission configuration table in the cache; read the function button permission record of the current user from the second permission configuration table in the cache; read the data permission record of the current user from the third permission configuration table in the cache.
[0064] Optionally, the above-mentioned device also includes a cache cleaning module, which is used to clean the cache if the permission records in the first permission configuration table, the second permission configuration table and / or the third permission configuration table in the cache are changed; and load the changed first permission configuration table, the changed second permission configuration table and / or the changed third permission configuration table into the cache so that the latest permission data can be obtained from the cache next time.
[0065] Optionally, the node authority information determination module is specifically used for: for each of the nodes, if the node authority record includes the identity information corresponding to the current user and includes the identity information of the node, then the node authority information of the node in the node authority record is used as the node authority information of the node; for each of the nodes, if the node authority record includes the identity information corresponding to the current user and does not include the identity information of the node, then the node authority information of the node is determined based on the node path corresponding to the node; if the node authority record does not include the identity information corresponding to the current user, then the node authority information of the node is determined based on the role authority data or department authority data associated with the current user.
[0066] The node path includes the node and multiple upper-level nodes of the node.
[0067] Optionally, the node authority information determination module is specifically used to: traverse from the node to the multiple upper-level nodes in sequence; during the traversal process, if the node authority record includes the identity information of the traversed node, then the node authority information of the traversed node in the node authority record is used as the node authority information of the node.
[0068] Optionally, the node authority information determination module is also used to: if the role authority data includes the identity information of the node, then the node authority information of the node in the role authority data is used as the node authority information of the node; or; if the department authority data includes the identity information of the node, then the node authority information of the node in the department authority data is used as the node authority information of the node.
[0069] Optionally, the function button permission information determination module is specifically used for: for each module, if the function button permission record includes the identity information corresponding to the current user and includes the identity information of the module, then the function button permission information of the module in the function button permission record is used as the function button permission information of the module; for each module, if the function button permission record includes the identity information corresponding to the current user and does not include the identity information of the module, then the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the function button permission record does not include the identity information corresponding to the current user, then the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0070] Optionally, the rule permission information determination module is specifically used for: for each module, if the data permission record includes the identity information corresponding to the current user and the identity information of the module, then the rule permission information of the module in the data permission record is used as the rule permission information of the module; for each module, if the data permission record includes the identity information corresponding to the current user and does not include the identity information of the module, then the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user; if the data permission record does not include the identity information corresponding to the current user, then the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user.
[0071] The display device for archival data provided in the embodiment of the present application can execute the display method for archival data provided in any embodiment of the present disclosure, and has functional modules and beneficial effects corresponding to the execution method.
[0072] Figure 3 A schematic diagram of an electronic device 10 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.
[0073] like Figure 3 As shown, the electronic device 10 includes at least one processor 11, and a memory 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 a computer program that can be executed by at least one processor, and the processor 11 can 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 to the random access memory (RAM) 13. In the random access memory (RAM) 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the read-only memory (ROM) 12 and the random access memory (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.
[0074] A number of components in the electronic device 10 are connected to an input / output (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 disk, an optical disk, etc., and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. 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.
[0075] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the display of method archive data.
[0076] In some embodiments, the display of method archive data may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a 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 a read-only memory (ROM) 12 and / or a communication unit 19. When the computer program is loaded into a random access memory (RAM) 13 and executed by the processor 11, one or more steps of the display of the method archive data described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the display of method archive data in any other suitable manner (e.g., by means of firmware).
[0077] 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), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0078] The computer programs for implementing the methods of the present application 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, a special-purpose computer, or other programmable data processing device, so that when the computer programs are executed by the processor, the functions / operations specified in the flow charts and / or block diagrams are implemented. The computer programs may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0079] In the context of the present application, a computer readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device or equipment. A computer readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer readable storage medium may be a machine readable signal medium. A more specific example of a machine readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0080] To provide interaction with a user, the systems and techniques described herein may 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 the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types 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 input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0081] The systems and techniques described herein may be implemented in a computing system that includes backend 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 frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0082] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0083] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements a method for displaying archival data as provided in any embodiment of the present application.
[0084] In the process of implementation, the computer program product can be written in one or more programming languages or a combination thereof to perform the computer program code of the present application, and the programming language includes an object-oriented programming language, such as Java, Smalltalk, C++, and also includes a conventional procedural programming language, such as "C" language or similar programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).
[0085] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present application is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present application. Therefore, although the present application is described in more detail through the above embodiments, the present application is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims
1. A method for displaying archive data, characterized in that: include: Obtaining the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records; Determining node authority information of each node in the whole tree based on the node authority record; Determine the function button permission information of each module under each node based on the function button permission record; Determine the rule permission information of each module under each node based on the data permission record; The corresponding archive data is displayed based on the node authority information of each node, the function button authority information of each module, and the rule authority information of each module.
2. The method according to claim 1, characterized in that Get the current user's permission data, including: Reading the node permission record of the current user from the first permission configuration table in the cache; Reading the function button permission record of the current user from the second permission configuration table in the cache; The data permission record of the current user is read from the third permission configuration table in the cache.
3. The method according to claim 2, characterized in that After displaying the corresponding archive data based on the node authority information of each node, the function button authority information of each module, and the rule authority information of each module, the method further includes: If the permission records in the first permission configuration table, the second permission configuration table and / or the third permission configuration table in the cache are changed, clearing the cache; The changed first permission configuration table, the changed second permission configuration table and / or the changed third permission configuration table are loaded into the cache, so that the latest permission data can be obtained from the cache next time.
4. The method according to claim 1, characterized in that Determining the node authority information of each node in the whole tree based on the node authority record includes: For each of the nodes, if the node authority record includes the identity information corresponding to the current user and the identity information of the node, the node authority information of the node in the node authority record is used as the node authority information of the node; For each of the nodes, if the node authority record includes the identity information corresponding to the current user but does not include the identity information of the node, determining the node authority information of the node based on the node path corresponding to the node; If the node authority record does not include the identity information corresponding to the current user, the node authority information of the node is determined based on the role authority data or department authority data associated with the current user.
5. The method according to claim 4, characterized in that in, The node path includes the node and multiple upper-level nodes of the node; Determining node authority information of the node based on the node path corresponding to the node includes: From the node, traverse to the multiple upper-level nodes in sequence; During the traversal process, if the node authority record includes the identity information of the traversed node, the node authority information of the traversed node in the node authority record is used as the node authority information of the node.
6. The method according to claim 5, characterized in that Determining the node authority information of the node based on the role authority data or department authority data associated with the current user includes: If the role authority data includes the identity information of the node, the node authority information of the node in the role authority data is used as the node authority information of the node; or; If the department authority data includes the identity information of the node, the node authority information of the node in the department authority data is used as the node authority information of the node.
7. The method according to claim 1, characterized in that Determining the function button permission information of each module under each node based on the function button permission record includes: For each module, if the function button permission record includes the identity information corresponding to the current user and the identity information of the module, the function button permission information of the module in the function button permission record is used as the function button permission information of the module; For each module, if the function button permission record includes the identity information corresponding to the current user but does not include the identity information of the module, the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user; If the function button permission record does not include the identity information corresponding to the current user, the function button permission information of the module is determined based on the role permission data or department permission data associated with the current user.
8. The method according to claim 1, characterized in that Determining the rule permission information of each module under each node based on the data permission record includes: For each module, if the data permission record includes the identity information corresponding to the current user and the identity information of the module, the rule permission information of the module in the data permission record is used as the rule permission information of the module; For each module, if the data permission record includes the identity information corresponding to the current user but does not include the identity information of the module, the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user; If the data permission record does not include the identity information corresponding to the current user, the rule permission information of the module is determined based on the role permission data or department permission data associated with the current user.
9. A display device for archival data, characterized in that: include: The permission data acquisition module is used to acquire the permission data of the current user; wherein the permission data includes node permission records, function button permission records and data permission records; A node authority information determination module, used to determine the node authority information of each node in the whole tree based on the node authority record; A function button permission information determination module, used to determine the function button permission information of each module under each node based on the function button permission record; A rule permission information determination module, used to determine the rule permission information of each module under each node based on the data permission record; The archive data display module is used to display corresponding archive data based on the node authority information of each node, the function button authority information of each module and the rule authority information of each module.
10. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method for displaying archival data as described in any one of claims 1-8.
11. A storage medium comprising computer executable instructions, wherein the computer executable instructions are used to perform the method for displaying archival data according to any one of claims 1 to 8 when executed by a computer processor.
12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the method for displaying archival data according to any one of claims 1 to 8.