WO2019056705A1 - 数据访问权限管理方法、装置、终端设备及存储介质 - Google Patents

数据访问权限管理方法、装置、终端设备及存储介质 Download PDF

Info

Publication number
WO2019056705A1
WO2019056705A1 PCT/CN2018/077473 CN2018077473W WO2019056705A1 WO 2019056705 A1 WO2019056705 A1 WO 2019056705A1 CN 2018077473 W CN2018077473 W CN 2018077473W WO 2019056705 A1 WO2019056705 A1 WO 2019056705A1
Authority
WO
WIPO (PCT)
Prior art keywords
folder
report
user class
user
target
Prior art date
Application number
PCT/CN2018/077473
Other languages
English (en)
French (fr)
Inventor
谭志杰
梁永健
张川
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Priority to SG11201809880RA priority Critical patent/SG11201809880RA/en
Priority to US16/098,129 priority patent/US11093631B2/en
Publication of WO2019056705A1 publication Critical patent/WO2019056705A1/zh

Links

Images

Classifications

    • 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/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • 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/60—Protecting data
    • G06F21/604—Tools and structures for managing or administering access control systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2457—Query processing with adaptation to user needs
    • G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G06F16/288—Entity relationship models
    • 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • 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

Definitions

  • the present application relates to the field of rights management technologies, and in particular, to a data access rights management method, apparatus, terminal device, and storage medium.
  • Tableau is a simple Business Intelligence (BI) tool for desktop systems that help people view and understand data.
  • Tableau includes Tableau Desktop and Tableau Server, Tableau Desktop is the client that uses Tableau, and Tableau Server is Tableau's server.
  • Tableau Desktop is a software application that analyzes any structured data that actually exists to produce beautiful charts, graphs, and dashboards and reports in minutes.
  • Tableau Server is enterprise intelligence software that provides browser-based analytics that anyone can learn and use.
  • Tableau Server is a software application that makes sharing the latest interactive data visualizations, dashboards, reports, and workbooks in Tableau Desktop quick and easy.
  • Tableau is a very popular BI tool that can visualize pre-stored reports. However, Tableau Server currently manages permissions on reports.
  • the application provides a data access authority management method, device, terminal device and storage medium to solve the problem that the current Tableau lacks a powerful rights management mechanism.
  • the application provides a data access rights management method, including:
  • report metadata in Tableau, the report metadata including a report ID;
  • Creating folder data in the Portal platform the folder data including at least one folder, the folder including a folder ID;
  • the user class permission configuration is performed based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the application provides a data access authority management apparatus, including:
  • a report metadata obtaining module configured to obtain report metadata in Tableau, where the report metadata includes a report ID;
  • a folder data creation module configured to create folder data in the portal platform, the folder data including at least one folder, the folder including a folder ID;
  • An association relationship creating module configured to create an association relationship between the report ID and the folder ID in the portal platform
  • a user class request obtaining module configured to obtain a user class permission configuration request input by the user, where the user class rights configuration request includes a user class ID and a target folder ID;
  • the user class permission configuration module is configured to perform user class permission configuration based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has a report element corresponding to the report ID corresponding to the target folder ID. Permissions for data.
  • the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions The following steps are implemented:
  • report metadata in Tableau, the report metadata including a report ID;
  • Creating folder data in the Portal platform the folder data including at least one folder, the folder including a folder ID;
  • the user class permission configuration is performed based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the present application provides a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the following steps:
  • report metadata in Tableau, the report metadata including a report ID;
  • Creating folder data in the Portal platform the folder data including at least one folder, the folder including a folder ID;
  • the user class permission configuration is performed based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the user class corresponding to the user class ID is configured to have access to the folder corresponding to the target folder ID in the Portal platform, so that the user class is enabled.
  • the user class corresponding to the ID has access to the report folder associated with the report ID and stored in Tableau's report metadata, so that the user class corresponding to each report metadata in Tableau Server corresponds to the user class instead of a single user.
  • Embodiment 1 is a flow chart of a data access authority management method in Embodiment 1.
  • FIG 2 is another flow chart of the data access authority management method in the first embodiment.
  • Embodiment 3 is a schematic block diagram of a data access authority management apparatus in Embodiment 2.
  • FIG. 4 is a block diagram showing another principle of the data access authority management apparatus in the second embodiment.
  • FIG. 5 is a schematic diagram of a terminal device in Embodiment 4.
  • FIG. 1 is a flow chart showing a data access authority management method in this embodiment.
  • the data access rights management method is used to improve the inflexibility of Tableau Server's rights management, so as to flexibly manage the enterprise's report access rights.
  • the data access rights management method includes the following steps:
  • Tableau is a software application that analyzes any structured data that actually exists to generate beautiful charts, graphs, dashboards, and reports in minutes.
  • Report metadata is raw data that needs to be processed using Tableau, which exists as a report.
  • the report ID is an identifier for uniquely identifying the report metadata, and each report metadata corresponds to a report ID.
  • the user can obtain report metadata by using the new report metadata method on the Tableau Desktop displayed by the client, and upload the report metadata to Tableau Server, so that Tableau Server can obtain the report metadata.
  • the user can import the created report metadata on the Tableau Desktop displayed by the client and send the report metadata to Tableau Server so that Tableau Server can obtain the report metadata and then according to the user selected chart. Visualization of coordinate charts, dashboards, and reports to improve the display of report metadata.
  • step S11 specifically includes: obtaining report metadata in Tableau, storing the report metadata in a PostgreSQL database, and forming a report relationship table, where the report relationship table includes at least one report metadata information, and report metadata information. Includes report ID and report name.
  • PostgreSQL is a free object-relational database server (database management system).
  • PostgreSQL supports most SQL standards and provides many other modern features such as complex queries, foreign keys, triggers, views, transaction integrity checks and more.
  • Features such as the version parallel control system (MVCC).
  • the report relation table is a relational table for information management of report metadata stored in a PostgreSQL database.
  • the report relationship table includes at least one report metadata information to manage report metadata stored in the PostgreSQL database based on the report metadata information.
  • the report metadata information includes, but is not limited to, the report ID and the report name in the embodiment, and may also include the producer name, the producer ID, and the upload time of the report metadata.
  • S12 Create folder data in the Portal platform, the folder data includes at least one folder, and the folder includes a folder ID.
  • the Portal platform refers to the portal platform, which is an information management platform that integrates various application programs, data resources and Internet resource sets.
  • the portal platform provides users with a unified user interface, so that users can quickly establish information channels between enterprises, customers, internal employees and business-to-business to store various information related to the enterprise.
  • the folder ID is an identifier for uniquely identifying a folder, and each folder corresponds to a folder ID, and the corresponding folder can be obtained by searching according to the folder ID. It is understood that the folder includes not only the folder ID but also the folder name for folder management based on the folder ID and the folder name.
  • the folder data created in the Portal platform includes a plurality of nested folder groups, and each layer folder group includes at least one folder. It can be understood that in the multi-level nested folder group, each upper folder group is nested with at least one lower folder group.
  • the first layer folder group can be first divided according to the subsidiary company of the group company; if the Ping An Group has two subsidiaries of bank and insurance, the first layer folder
  • the folder names of the group are "Bank" and "Insurance”
  • the corresponding folder IDs are W01 and W02.
  • the first layer folder group of "insurance” it can be divided into the second layer folder group corresponding to "production insurance” and "life insurance” according to the different business organizations, and the corresponding folder IDs are W0201 and W0202.
  • the third-level folder group of “Property Insurance” the fourth-level folder group corresponding to “Guangdongzhou” and “Shanghai” can be divided according to the area, and the corresponding folder IDs are W020101 and W020102 respectively.
  • This type of push is based on the folder corresponding to the smallest team in the enterprise to store the report metadata corresponding to the minimum team.
  • step S12 specifically includes: creating folder data in the Portal platform, storing the folder data in the Oracle database, and forming a folder relationship table, where the folder relationship table includes at least one folder information, and a file
  • the folder information includes the folder ID and the folder name.
  • Oracle database (Oracle Database, also known as Oracle RDBMS, or Oracle for short) is a relational database management system.
  • the relational database management system is portable, easy to use, and powerful. It is suitable for all kinds of large, medium and small. Microcomputer environment.
  • Oracle database is a database with high efficiency, good reliability, high data security and strong stability.
  • the folder relationship table is a relation table for managing folder data stored in an Oracle database.
  • the folder relationship table includes at least one folder information.
  • the folder information includes, but is not limited to, a folder ID and a folder name in the embodiment, and may also include a producer name, a producer ID, and an upload time for creating the folder.
  • the association relationship between the report ID and the folder ID is created in the portal platform, so that the folder corresponding to each folder ID can store the report metadata corresponding to the report ID, so as to be based on the association relationship and the determined folder.
  • the ID finds the report metadata corresponding to the corresponding report ID, or searches for a folder corresponding to the corresponding folder ID based on the association relationship and the determined report ID.
  • step S13 specifically includes: creating an association relationship information table in the portal platform, where the association relationship information table includes at least one association information, where the association information includes a report ID and a folder ID, so as to create a report in the portal platform. The association between the ID and the folder ID.
  • the association relationship information table is an information table for storing an association relationship between the report ID and the folder ID.
  • the association information table includes at least one association information, and each association information includes, but is not limited to, a report ID and a folder ID, so that the report metadata corresponding to the report ID created in Tableau and the folder created in the Portal platform are created.
  • the folder corresponding to the ID establishes an association relationship.
  • the related information may further include a producer name, a producer ID, and a production time of the relationship information table.
  • association information table is created in the portal platform, so that the corresponding report ID is obtained based on each associated information in the association information table and the determined folder ID, and the report metadata corresponding to the report ID is obtained; or A folder corresponding to the folder ID may be obtained by searching for a corresponding folder ID based on each associated information in the association information table and the determined report ID.
  • S14 Acquire a user class permission configuration request input by the user, and the user class permission configuration request includes a user class ID and a target folder ID.
  • the user class permission configuration request is used to request an access permission request of the user class corresponding to the user class ID in the folder corresponding to the target folder ID.
  • the user class ID is an identifier for uniquely identifying the user class.
  • the user class is a class that can be set according to the user's role during the permission configuration process, and can be represented by the User Class.
  • the target folder ID is the folder ID determined in this user class permission configuration request.
  • the administrator of the enterprise may input a user class permission configuration request in the portal platform, and allocate a permission to access the folder corresponding to the target folder ID to the user class corresponding to the user class ID according to the user class permission configuration request.
  • the user corresponding to the user class corresponding to the user class ID can access the report metadata corresponding to the folder corresponding to the target folder ID.
  • S15 Perform user class permission configuration based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • a user class information table may be created in the portal platform, where the user class information table includes at least one user class information, and each user class information includes not only a user class ID and a target folder ID, but also a permission configuration time or other information. It can be understood that each time the Portal platform receives a user class permission configuration request, a user class information is created in the user class information table, so that the user class corresponding to the user class ID has access to the folder corresponding to the target folder ID (ie, The permission of the target folder), that is, the access to the report metadata corresponding to the report ID in the target folder.
  • the target folder ID ie, The permission of the target folder
  • the user class of the folder corresponding to the target folder ID (ie, the target folder) is set as the holder of the target folder, such as the user class.
  • the target folder ID ie, the target folder
  • the user class of the folder corresponding to the target folder ID is set as the holder of the target folder, such as the user class.
  • the target folder Generally can be described as XX company XX department XX organization XX team.
  • each layer folder group includes at least one folder; when the user class rights are configured, the user class can be multi-level Nested configuration to match multiple nested folder groups to increase the flexibility and efficiency of rights management.
  • the user class is configured in multiple levels, it can be configured as a first-level user class, a second-level user class, a third-level user class, an N-level user class, etc., so as to perform subsequent rights management control.
  • the first-level user class includes at least one second-level user class
  • each second-level user class includes at least one third-level user class.... such that each superior user class can include at least one sub-user class.
  • the user with the upper-level user class can view the report metadata in the folder corresponding to the target folder ID corresponding to the lower-level user class (that is, the target folder), and the user with the lower-level user class cannot view the superior.
  • the report metadata in the folder corresponding to the target folder ID corresponding to the user class ie, the target folder.
  • the report metadata corresponding to the report ID is obtained in Tableau to store the report metadata; and the folder data corresponding to the folder ID is created in the Portal platform. And establishing an association relationship between the report ID and the folder ID, so that the folder corresponding to the folder ID can store the report metadata corresponding to the report ID; and then in the Portal platform, the user class is configured based on the user class permission configuration request input by the user. Privilege configuration, so that the user class corresponding to the user class ID has the right to access the folder corresponding to the target folder ID (ie, the target folder), that is, the report metadata corresponding to the report ID stored in the target folder. Permissions.
  • the user class corresponding to the user class ID in the Portal platform has the right to access the folder corresponding to the target folder ID (ie, the target folder), so that the user class ID is obtained.
  • the corresponding user class has access to the report metadata associated with the report ID and created by Tableau in the target folder, so that the user class corresponding to each report metadata in Tableau Server corresponds to the user class instead of a single user, to achieve Tableau Flexible management of report access rights in Server to improve the application range of Tableau.
  • the data access rights management method further includes the following steps:
  • S16 Acquire a personal rights configuration request input by the user, where the personal rights configuration request includes a user ID and a target user class ID.
  • the user ID is an identifier for uniquely identifying the user, and the user ID can be used to uniquely identify the employee number of the company employee.
  • the target user class ID is an identifier for uniquely identifying the user class to which the user corresponding to the user ID belongs.
  • the user class of the folder corresponding to the target folder ID ie, the target folder
  • the user class of the folder corresponding to the target folder ID is set as the holder of the target folder, such as the user class.
  • the user's employee can be assigned the authority of the report metadata in the folder that he or she can access according to the user class to which he belongs.
  • the user ie, the administrator
  • the user can log in to the permission configuration interface of the Portal platform, and the user (ie, the administrator) can input the user ID, and select the corresponding target user class ID in the created user class ID list, and then click “ Submit the button, you can
  • the Portal platform obtains the corresponding personal rights configuration request, so as to complete the permission configuration for any company employee (ie, the user corresponding to the user ID) based on the personal rights configuration request.
  • S17 Configure personal rights based on the personal rights configuration request in the Portal platform, so that the user corresponding to the user ID has the user class rights corresponding to the target user class ID.
  • a personal information table may be created in the Portal platform, the personal information table including at least one personal information, each personal information including but not limited to personal information such as a user ID and a user name, and a target user class associated with the user ID. ID.
  • each personal information including but not limited to personal information such as a user ID and a user name, and a target user class associated with the user ID. ID.
  • the corresponding user has the authority of the user class corresponding to the target user class ID.
  • the folder data includes at least one folder, and the report ID corresponding to each report metadata created in Tableau is associated with the folder ID;
  • the permission configuration is such that the user class corresponding to each user class ID can correspond to a folder corresponding to a target folder ID (ie, a target folder), so that the user class corresponding to the user class ID is a folder corresponding to the target folder ID.
  • the holder of the target user class ID is configured by the personal rights configuration, and the user corresponding to the target user class ID is configured for the user corresponding to the user ID, so that the user corresponding to the user ID has the user class corresponding to the target user class ID. Permission to access the report metadata corresponding to the report ID in the target folder.
  • the data access rights management method further includes:
  • S21 Obtain a data access request input by the user, where the data access request includes a user ID and a target folder ID.
  • the data access request refers to a request for requesting access to corresponding report metadata in the target folder.
  • the target folder ID refers to the folder ID corresponding to the target folder that the user wants to access.
  • the user corresponding to any user ID can log in to the portal platform, so that all requests input by the user on the Portal platform carry the user ID. After logging in to the Portal platform, the user can directly enter the target folder ID, or enter the target folder ID by dragging and dropping, and then click the "Submit" button to enter the data access request.
  • the target user class ID is a user class ID corresponding to the user class to which the user corresponding to the user ID belongs. It can be understood that each time the Portal platform receives a data access request, the user ID in the data access request is obtained, and the pre-created personal information table is queried based on the user ID, and the target user class ID associated with the user ID is obtained. It can be understood that, due to the cross-setting of employee positions in the enterprise, a company employee can correspond to a target user class ID, and may also correspond to multiple target user class IDs.
  • S23 Determine whether the user class corresponding to the target user class ID has the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the portal platform obtains the target folder ID in the data access request when receiving the data access request, and obtains the corresponding target user class ID in step S22, and can query the user class information table pre-created in the portal platform. It is determined whether the target user class ID and the target folder ID are in the same user class information. If the target user class ID and the target folder ID are in the same user class information, it is determined that the user class corresponding to the target user class ID has the right to access the folder corresponding to the target folder ID (ie, the target folder), that is, has access and The target folder ID has the authority of the report metadata corresponding to the report ID of the association relationship. If the target user class ID and the target folder ID are not in the same user class information, it is determined that the user class authority corresponding to the target user class ID does not have the permission to access the folder corresponding to the target folder ID (ie, the target folder).
  • the portal platform may display the report ID corresponding to the target folder ID.
  • Report metadata Specifically, the report metadata displayed on the Portal platform may use the table metadata created in Tableau to enable multiple users to access the same report metadata on the Tableau through the Portal platform.
  • the corresponding target user class ID may be determined based on the user ID, and then the user class corresponding to the target user class ID is determined to have the access target folder ID.
  • the permission of the folder ie, the target folder
  • the report element corresponding to the report ID corresponding to the target folder ID may be displayed on the Portal platform.
  • the user class corresponding to the authority of each report metadata in Tableau Server is used instead of a single user, so as to implement flexible management of report access rights in Tableau Server and improve the application range of Tableau.
  • Fig. 3 is a block diagram showing the principle of the data access authority management apparatus corresponding to the data access authority management method in the first embodiment.
  • the data access authority management apparatus includes a report metadata acquisition module 11, a folder data creation module 12, an association relationship creation module 13, a user class request acquisition module 14, a user class authority configuration module 15, and an individual request acquisition. Module 16 and personal rights configuration module 17.
  • the implementation functions of the report metadata acquisition module 11, the folder data creation module 12, the association relationship creation module 13, the user class request acquisition module 14, the user class rights configuration module 15, the individual request acquisition module 16, and the personal rights configuration module 17 Steps S11-S17 corresponding to the data access rights management method in the first embodiment are in one-to-one correspondence. To avoid redundancy, the present embodiment will not be described in detail.
  • the report metadata obtaining module 11 is configured to obtain report metadata in Tableau, and the report metadata includes a report ID.
  • the folder data creating module 12 is configured to create folder data in the portal platform, the folder data includes at least one folder, and the folder includes a folder ID.
  • the association relationship creating module 13 is configured to create an association relationship between the report ID and the folder ID in the portal platform.
  • the user class request obtaining module 14 is configured to obtain a user class permission configuration request input by the user, and the user class rights configuration request includes a user class ID and a target folder ID.
  • the user class permission configuration module 15 is configured to perform user class permission configuration based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has access to the report metadata corresponding to the report ID corresponding to the target folder ID. permission.
  • the data access right management device further includes a personal request acquisition module 16 and an individual rights configuration module 17.
  • the personal request obtaining module 16 is configured to obtain a personal rights configuration request input by the user, where the personal rights configuration request includes a user ID and a target user class ID.
  • the personal rights configuration module 17 is configured to perform personal rights configuration based on the personal rights configuration request in the Portal platform, so that the user corresponding to the user ID has the user class rights corresponding to the target user class ID.
  • the report metadata obtaining module 11 is further configured to store the report metadata in the PostgreSQL database, and form a report relation table, where the report relationship table includes at least one report metadata information, and the report metadata information includes a report ID and a report name.
  • the folder data creating module 12 is further configured to store the folder data in the Oracle database, and form a folder relationship table.
  • the folder relationship table includes at least one folder information, and the folder information includes a folder ID and a folder name.
  • the association relationship creation module 13 is further configured to create an association relationship information table in the portal platform, where the association relationship information table includes at least one association information, where the association information includes a report ID and a folder ID.
  • the folder data includes a plurality of nested folder groups, and each layer folder group includes at least one folder.
  • the data access authority management apparatus further includes a data access request acquisition module 21, a target user class ID acquisition module 22, a user authority determination module 23, and a report data display module 24.
  • the implementation functions of the data access request acquisition module 21, the target user class ID acquisition module 22, the user authority determination module 23, and the report data display module 24 correspond to the steps S21-S24 corresponding to the data access authority management method in the second embodiment. In order to avoid redundancy, the present embodiment will not be described in detail.
  • the data access request obtaining module 21 is configured to obtain a data access request input by the user, where the data access request includes a user ID and a target folder ID.
  • the target user class ID obtaining module 22 is configured to acquire a corresponding target user class ID based on the user ID.
  • the user authority judging module 23 is configured to determine whether the user class corresponding to the target user class ID has the right to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the report data display module 24 is configured to: if the user class permission corresponding to the target user class ID is the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID, display the report ID corresponding to the target folder ID. Report metadata.
  • the embodiment provides a computer readable storage medium having computer readable instructions stored thereon.
  • the data access authority management method in Embodiment 1 is implemented. I won't go into details here.
  • the functions of the modules/units in the data access authority management device in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • the computer readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read- Only Memory), Random Access Memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media.
  • FIG. 5 is a schematic diagram of a terminal device 50 according to an embodiment of the present application.
  • the terminal device 50 of this embodiment includes a processor 51, a memory 52, and computer readable instructions 53 stored in the memory 52 and operable on the processor 51.
  • the processor 51 executes the computer readable instructions 53 to implement the various steps of the data access authority management method provided by the above-described Embodiment 1, such as steps S11-S17 shown in FIG. 1, or steps S21-S24 shown in FIG.
  • the processor 51 executes the computer readable instructions 53, the functions of the modules/units in the data access authority management apparatus provided in the above embodiment 2 are implemented.
  • the report metadata acquisition module 11, the folder data creation module 12, the association relationship creation module 13, the user class request acquisition module 14, the user class authority configuration module 15, the personal request acquisition module 16, and the personal rights configuration module are shown in FIG.
  • computer readable instructions 53 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 52 and executed by processor 51 to complete the application.
  • the one or more modules/units may be an instruction segment of a series of computer readable instructions 53 capable of performing a particular function, which is used to describe the execution of computer readable instructions 53 in the terminal device 50.
  • the computer readable instruction 53 may be divided into the report metadata acquisition module 11 , the folder data creation module 12 , the association relationship creation module 13 , the user class request acquisition module 14 , and the user class authority configuration module 15 illustrated in FIG. 3 .
  • the individual request acquisition module 16 and the personal rights configuration module 17 have the following specific functions:
  • the report metadata obtaining module 11 is configured to obtain report metadata in Tableau, and the report metadata includes a report ID.
  • the folder data creating module 12 is configured to create folder data in the portal platform, the folder data includes at least one folder, and the folder includes a folder ID.
  • the association relationship creating module 13 is configured to create an association relationship between the report ID and the folder ID in the portal platform.
  • the user class request obtaining module 14 is configured to obtain a user class permission configuration request input by the user, and the user class rights configuration request includes a user class ID and a target folder ID.
  • the user class permission configuration module 15 is configured to perform user class permission configuration based on the user class permission configuration request in the portal platform, so that the user class corresponding to the user class ID has access to the report metadata corresponding to the report ID corresponding to the target folder ID. permission.
  • the personal request obtaining module 16 is configured to obtain a personal rights configuration request input by the user, where the personal rights configuration request includes a user ID and a target user class ID.
  • the personal rights configuration module 17 is configured to perform personal rights configuration based on the personal rights configuration request in the Portal platform, so that the user corresponding to the user ID has the user class rights corresponding to the target user class ID.
  • the report metadata obtaining module 11 is further configured to store the report metadata in the PostgreSQL database, and form a report relation table, where the report relationship table includes at least one report metadata information, and the report metadata information includes a report ID and a report name.
  • the folder data creating module 12 is further configured to store the folder data in the Oracle database, and form a folder relationship table.
  • the folder relationship table includes at least one folder information, and the folder information includes a folder ID and a folder name.
  • the association relationship creation module 13 is further configured to create an association relationship information table in the portal platform, where the association relationship information table includes at least one association information, where the association information includes a report ID and a folder ID.
  • the folder data includes a plurality of nested folder groups, each layer folder group including at least one folder.
  • the computer readable instructions 53 may be divided into the data access request acquisition module 21, the target user class ID acquisition module 22, the user authority determination module 23, and the report data display module 24 shown in FIG. 4, and the specific functions of each module are as follows:
  • the data access request obtaining module 21 is configured to obtain a data access request input by the user, where the data access request includes a user ID and a target folder ID.
  • the target user class ID obtaining module 22 is configured to acquire a corresponding target user class ID based on the user ID.
  • the user authority judging module 23 is configured to determine whether the user class corresponding to the target user class ID has the right to access the report metadata corresponding to the report ID corresponding to the target folder ID.
  • the report data display module 24 is configured to: if the user class permission corresponding to the target user class ID is the permission to access the report metadata corresponding to the report ID corresponding to the target folder ID, display the report ID corresponding to the target folder ID. Report metadata.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Health & Medical Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • Library & Information Science (AREA)
  • Computational Linguistics (AREA)
  • Automation & Control Theory (AREA)
  • Storage Device Security (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本申请公开一种数据访问权限管理方法、装置、终端设备及存储介质。该数据访问权限管理方法包括：在Tableau中获取报表元数据，报表元数据包括报表ID；在Portal平台中创建文件夹数据，文件夹数据包括至少一个文件夹，文件夹包括文件夹ID；在Portal平台中创建报表ID与文件夹ID的关联关系；获取用户输入的用户类权限配置请求，用户类权限配置请求包括用户类ID和目标文件夹ID；在Portal平台中基于用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。该数据访问权限管理方法可使Tableau Server中每一报表元数据的权限为用户类而不是单一用户，以实现对Tableau Server中报表访问权限的灵活管理，提高Tableau的应用范围。

Description

数据访问权限管理方法、装置、终端设备及存储介质
本专利申请以2017年9月19日提交的申请号为201710845614.3，名称为“数据访问权限管理方法、装置、设备及存储介质”的中国发明专利申请为基础，并要求其优先权。
技术领域
本申请涉及权限管理技术领域，尤其涉及一种数据访问权限管理方法、装置、终端设备及存储介质。
背景技术
Tableau是一种致力于帮助人们查看并理解数据的桌面系统简单的智能商业(Business Intelligence，即BI)工具。其中，Tableau包括Tableau Desktop和Tableau Server，基于Tableau Desktop为应用Tableau的客户端，而Tableau Server为Tableau的服务器。Tableau Desktop是一种用于分析实际存在的任何结构化数据，以在几分钟内生成美观的图表、坐标图和、仪表盘与报告的软件应用程序。Tableau Server是企业智能化软件，提供任何人可以学习与使用的基于浏览器的分析。Tableau Server是软件应用程序，将Tableau Desktop中最新的交互式数据可视化内容、仪表盘、报告与工作簿的共享变得迅速简便。Tableau是一款非常流行的BI工具，可实现对预先存储的报表进行可视化显示，但当前Tableau Server在对报表进行权限管理，任一报表只能为一个用户所有，使得Tableau的权限管理时不灵活。在企业使用Tableau时，由于Tableau Server的权限管理不灵活，无法对同一报表分别给企业内部不同机构、部门或岗位的用户配置不同的权限，使得每一报表需保存多份并分别配置不同权限，影响Tableau的应用。
发明内容
本申请提供一种数据访问权限管理方法、装置、终端设备及存储介质，以解决当前Tableau欠缺强大的权限管理机制的问题。
第一方面，本申请提供一种数据访问权限管理方法，包括：
在Tableau中获取报表元数据，所述报表元数据包括报表ID；
在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件 夹包括文件夹ID；
在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
第二方面，本申请提供一种数据访问权限管理装置，包括：
报表元数据获取模块，用于在Tableau中获取报表元数据，所述报表元数据包括报表ID；
文件夹数据创建模块，用于在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
关联关系创建模块，用于在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
用户类请求获取模块，用于获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
用户类权限配置模块，用于在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
第三方面，本申请提供一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
在Tableau中获取报表元数据，所述报表元数据包括报表ID；
在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
第四方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质存储有计 算机可读指令，所述计算机可读指令被处理器执行时实现如下步骤：
在Tableau中获取报表元数据，所述报表元数据包括报表ID；
在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
本申请提供的数据访问权限管理方法、装置、终端设备及存储介质中，通过在Portal平台中配置用户类ID对应的用户类具有访问目标文件夹ID对应的文件夹的权限，以使该用户类ID对应的用户类具有访问相应的文件夹中与报表ID相关联并存储在Tableau的报表元数据的权限，使Tableau Server中每一报表元数据的权限对应的用户类而不是单一用户，以实现对Tableau Server中报表访问权限的灵活管理，提高Tableau的应用范围。
附图说明
为了更清楚地说明本申请的技术方案，下面将对本申请的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是实施例1中数据访问权限管理方法的一流程图。
图2是实施例1中数据访问权限管理方法的另一流程图。
图3是实施例2中数据访问权限管理装置的一原理框图。
图4是实施例2中数据访问权限管理装置的另一原理框图。
图5是实施例4中终端设备的一示意图。
具体实施方式
下面将结合本申请中的附图，对本申请中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
实施例1
图1示出本实施例中数据访问权限管理方法的流程图。该数据访问权限管理方法用于改进Tableau Server的权限管理不灵活的问题，以便于对企业的报表访问权限进行灵活管理。如图1所示，该数据访问权限管理方法包括如下步骤：
S11：在Tableau中获取报表元数据，报表元数据包括报表ID。
其中，Tableau是一种用于分析实际存在的任何结构化数据，以在几分钟内生成美观的图表、坐标图、仪表盘与报告的软件应用程序。报表元数据是需采用Tableau进行处理的原始数据，该原始数据以报表形式存在。报表ID是用于唯一识别报表元数据的标识，每一报表元数据对应一报表ID。
本实施例中，用户可在客户端显示的Tableau Desktop上采用新建报表元数据方式获取报表元数据，并将报表元数据上传到Tableau Server，以使Tableau Server可获取报表元数据。或者，用户可在客户端显示的Tableau Desktop上采用导入方式导入已创建的报表元数据，并将报表元数据发送给Tableau Server，以使Tableau Server可获取报表元数据，再依据用户选定的图表、坐标图、仪表盘与报告进行可视化显示，以提高报表元数据显示的显示效果。
在一具体实施方式中，步骤S11具体包括：在Tableau中获取报表元数据，将报表元数据存储在PostgreSQL数据库，并形成报表关系表，报表关系表包括至少一个报表元数据信息，报表元数据信息包括报表ID和报表名称。
其中，PostgreSQL是一个自由的对象-关系数据库服务器(数据库管理系统)，PostgreSQL支持大部分SQL标准并且提供了许多其他现代特性，如复杂查询、外键、触发器、视图、事务完整性检查和多版本并行控制系统(MVCC)等特性。报表关系表是用于对存储在PostgreSQL数据库中的报表元数据进行信息管理的关系表。报表关系表包括至少一个报表元数据信息，以便基于该报表元数据信息对存储在PostgreSQL数据库中的报表元数据进行管理。其中，报表元数据信息包括但不限于本实施例中的报表ID和报表名称，还可以包括报表元数据的制作人姓名、制作人ID和上传时间。
S12：在Portal平台中创建文件夹数据，文件夹数据包括至少一个文件夹，文件夹包括文件夹ID。
其中，Portal平台是指门户平台，是集成各种应用程序、数据资源和互联网资源集的信息管理平台。该Portal平台给用户提供统一的用户界面，以使用户可快速建立企业对客户、企业对内部员工和企业对企业之间的信息通道，用以存储与企业相关的各种信息。 文件夹ID是用于唯一识别文件夹的标识，每一文件夹对应一文件夹ID，可根据该文件夹ID查找获取对应的文件夹。可以理解地，文件夹不仅包括文件夹ID，还包括文件夹名称，以便基于文件夹ID和文件夹名称进行文件夹管理。
本实施例中，在Portal平台中创建的文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个文件夹。可以理解地，在多层嵌套式文件夹组中，每一上层文件夹组嵌套有至少一个下层文件夹组。如在Portal平台中创建一集团公司的文件夹数据时，可先依据集团公司下属的子公司划分第一层文件夹组；如平安集团下属有银行和保险两个子公司，则第一层文件夹组的文件夹名称为“银行”和“保险”，对应的文件夹ID分别为W01和W02。对于“保险”这个第一层文件夹组下还可依据业务机构的不同划分为“产险”和“寿险”对应的第二层文件夹组，对应的文件夹ID为W0201和W0202。对于“产险”这个第三层文件夹组还可依据区域划分为“广东省”和“上海市”对应的第四层文件夹组，其对应的文件夹ID分别为W020101和W020102……依此类推，直至依据划分到企业内最小团队对应的文件夹，以存储该最小团队对应的报表元数据。
在一具体实施方式中，步骤S12具体包括：在Portal平台中创建文件夹数据，将文件夹数据存储在Oracle数据库中，并形成文件夹关系表，文件夹关系表包括至少一个文件夹信息，文件夹信息包括文件夹ID和文件夹名称。
Oracle数据库(即Oracle Database，又名Oracle RDBMS，或简称Oracle)是一款关系数据库管理系统，该关系数据库管理系统可移植性好、使用方便、功能强，适用于各类大、中、小、微机环境。Oracle数据库是一种高效率、可靠性好、数据安全性高且稳定性强的数据库。文件夹关系表是用于对存储在Oracle数据库中的文件夹数据进行管理的关系表。文件夹关系表包括至少一个文件夹信息。其中，文件夹信息包括但不限于本实施例中的文件夹ID和文件夹名称，还可以包括制作该文件夹的制作人姓名、制作人ID和上传时间。
S13：在Portal平台中创建报表ID与文件夹ID的关联关系。
本实施例中，在Portal平台中创建报表ID与文件夹ID的关联关系，以便每一文件夹ID对应的文件夹可存储报表ID对应的报表元数据，以便基于该关联关系和确定的文件夹ID查找到对应的报表ID对应的报表元数据，或者基于该关联关系和确定的报表ID查找对应的文件夹ID对应的文件夹。
在一具体实施方式中，步骤S13具体包括：在Portal平台中创建关联关系信息表，关联关系信息表包括至少一个关联信息，关联信息包括报表ID与文件夹ID，以实现在 Portal平台中创建报表ID与文件夹ID的关联关系。
其中，关联关系信息表是用于存储报表ID与文件夹ID的关联关系的信息表。关联关系信息表中包括至少一个关联信息，每一关联信息包括但不限于报表ID和文件夹ID，以使Tableau中创建的与报表ID相对应的报表元数据和Portal平台中创建的与文件夹ID对应的文件夹建立关联关系。该关联信息还可以包括制作关联关系信息表的制作人姓名、制作人ID和制作时间。可以理解地，通过在Portal平台中创建关联关系信息表，以便基于关联关系信息表中每一关联信息和确定的文件夹ID查找对应的报表ID，获取与报表ID对应的报表元数据；或者，可基于关联关系信息表中每一关联信息和确定的报表ID查找对应的文件夹ID，获取与文件夹ID对应的文件夹。
S14：获取用户输入的用户类权限配置请求，用户类权限配置请求包括用户类ID和目标文件夹ID。
其中，用户类权限配置请求是用于请求给目标文件夹ID对应的文件夹配置与用户类ID对应的用户类的访问权限请求。其中，用户类ID是用于唯一识别用户类的标识。用户类是在权限配置过程中可根据用户角色设置的类，可采用User Class来表示。目标文件夹ID是本次用户类权限配置请求中确定的文件夹ID。本实施例中，企业的管理人员可在Portal平台中输入用户类权限配置请求，以根据该用户类权限配置请求给用户类ID对应的用户类分配访问目标文件夹ID对应的文件夹的权限，以使具有该用户类ID对应的用户类的用户可访问该目标文件夹ID对应的文件夹对应的报表元数据。
S15：在Portal平台中基于用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
具体地，可在Portal平台中创建用户类信息表，该用户类信息表包括至少一个用户类信息，每一用户类信息不仅包括用户类ID和目标文件夹ID，还可包括权限配置时间或其他信息。可以理解地，Portal平台每接收一个用户类权限配置请求，即在用户类信息表中创建一个用户类信息，以限定用户类ID对应的用户类具有访问与目标文件夹ID对应的文件夹(即目标文件夹)的权限，即访问该目标文件夹中报表ID对应的报表元数据的权限。本实施例中，在基于用户类权限配置请求进行用户类权限配置时，设置目标文件夹ID对应的文件夹(即目标文件夹)的用户类为该目标文件夹的持有人，如用户类一般可描述为XX公司XX部门XX机构XX团队等。
可以理解地，由于在Portal平台中创建的文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个文件夹；在用户类权限配置时，可对用户类进行多级嵌套式配 置，以匹配多层嵌套式文件夹组，以提高权限管理的灵活性和效率。如对用户类进行多级配置时，可依次配置为一级用户类、二级用户类、三级用户类……N级用户类等，以便后续进行权限管理控制。可以理解地，在一级用户类包括至少一个二级用户类，每一二级用户类包括至少一个三级用户类……，使得每一上级用户类可以包括至少一个下级用户类。在用户类权限配置时，具有上级用户类的用户可查看下级用户类对应的目标文件夹ID对应的文件夹(即目标文件夹)中的报表元数据，而具有下级用户类的用户不可查看上级用户类对应的目标文件夹ID对应的文件夹(即目标文件夹)中的报表元数据。
本实施例所提供的数据访问权限管理方法中，通过在Tableau中获取与报表ID对应的报表元数据，以存储报表元数据；再通过在Portal平台中创建与文件夹ID相对应的文件夹数据，并建立报表ID与文件夹ID的关联关系，以使该文件夹ID对应的文件夹可存储报表ID对应的报表元数据；然后在Portal平台中基于用户输入的用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问目标文件夹ID对应的文件夹(即目标文件夹)的权限，即具有访问该目标文件夹中存储的报表ID相对应的报表元数据的权限。可以理解地，该数据访问权限管理方法中，通过在Portal平台中配置用户类ID对应的用户类具有访问目标文件夹ID对应的文件夹(即目标文件夹)的权限，以使该用户类ID对应的用户类具有访问目标文件夹中与报表ID相关联并由Tableau创建的报表元数据的权限，使Tableau Server中每一报表元数据的权限对应的用户类而不是单一用户，以实现对Tableau Server中报表访问权限的灵活管理，提高Tableau的应用范围。
在一具体实施方式中，该数据访问权限管理方法还包括如下步骤：
S16：获取用户输入的个人权限配置请求，个人权限配置请求包括用户ID和目标用户类ID。
其中，用户ID是用于唯一识别用户的标识，该用户ID可以用于唯一识别公司员工的工号。目标用户类ID是用于唯一识别用户ID对应的用户所属的用户类的标识。本实施例中，基于用户类权限配置请求进行用户类权限配置时，设置目标文件夹ID对应的文件夹(即目标文件夹)的用户类为该目标文件夹的持有人，如用户类一般可描述为XX公司XX部门XX机构XX团队等。在对公司员工进行管理时，可依据其所属用户类，给该用户员工分配其可访问的文件夹中的报表元数据的权限。具体地，用户(即管理人员)可登录Portal平台的权限配置界面，用户(即管理人员)可输入用户ID，并在已创建的用户类ID列表中选取对应的目标用户类ID，然后点击“提交”按钮，即可
输入个人权限配置请求，以使Portal平台获取到相应的个人权限配置请求，以便基于该 个人权限配置请求完成对任一公司员工(即用户ID对应的用户)的权限配置。
S17：在Portal平台中基于个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与目标用户类ID对应的用户类权限。
具体地，可在Portal平台中创建个人信息表，该个人信息表包括至少一个个人信息，每一个人信息包括但不限于用户ID和用户姓名等个人信息，还包括与用户ID关联的目标用户类ID。Portal平台每接收到一个个人权限配置请求时，即可在个人信息表中新增一个个人信息，将用户ID和目标用户类ID添加到相应的个人信息中，以完成个人权限配置，使得用户ID对应的用户具有与目标用户类ID对应的用户类的权限。
本实施例中，由于Portal平台预先配置文件夹数据，该文件夹数据包括至少一个文件夹，并使Tableau中创建的每一报表元数据对应的报表ID与文件夹ID具有关联关系；通过用户类权限配置，使得每一用户类ID对应的用户类可对应一目标文件夹ID对应的文件夹(即目标文件夹)，以使该用户类ID对应的用户类为目标文件夹ID对应的文件夹(即目标文件夹)的持有人；最后通过个人权限配置，给用户ID对应的用户配置目标用户类ID对应的用户类，即可使用户ID对应的用户具有目标用户类ID对应的用户类的权限，可访问目标文件夹中与报表ID对应的报表元数据。
在一具体实施方式中，如图2所示，数据访问权限管理方法还包括：
S21：获取用户输入的数据访问请求，数据访问请求包括用户ID和目标文件夹ID。
其中，数据访问请求是指请求访问目标文件夹中的对应的报表元数据的请求。目标文件夹ID是指用户想要访问的目标文件夹对应的文件夹ID。本实施例中，任一用户ID对应的用户可登录Portal平台，以使该用户在Portal平台输入的所有请求均携带用户ID。用户登录Portal平台后，可直接输入目标文件夹ID，也可以拖拉形式输入目标文件夹ID，再点击“提交”按钮即可输入数据访问请求。
S22：基于用户ID，获取对应的目标用户类ID。
其中，目标用户类ID是指用户ID对应的用户所属的用户类对应的用户类ID。可以理解地，Portal平台每接收到一个数据访问请求时，获取数据访问请求中的用户ID，基于该用户ID查询预先创建的个人信息表，获取与该用户ID相关联的目标用户类ID。可以理解地，由于企业内员工岗位交叉设置，使得一个公司员工可对应一个目标用户类ID，也可能对应多个目标用户类ID。
S23：判断目标用户类ID对应的用户类是否具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
具体地，Portal平台在接收到数据访问请求时，获取数据访问请求中的目标文件夹ID，并通过步骤S22获取对应的目标用户类ID，可通过查询Portal平台中预先创建的用户类信息表，判断该目标用户类ID和目标文件夹ID是否在同一用户类信息中。若目标用户类ID和目标文件夹ID在同一用户类信息中，则认定目标用户类ID对应的用户类具有访问目标文件夹ID对应的文件夹(即目标文件夹)的权限，即具有访问与目标文件夹ID具有关联关系的报表ID对应的报表元数据的权限。若目标用户类ID和目标文件夹ID不在同一用户类信息中，则认定目标用户类ID对应的用户类权限不具有访问目标文件夹ID对应的文件夹(即目标文件夹)的权限。
S24：若目标用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与目标文件夹ID对应的报表ID对应的报表元数据。
可以理解地，若Portal平台确定目标用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限，则Portal平台可显示与目标文件夹ID对应的报表ID对应的报表元数据。具体地，在Portal平台上显示的报表元数据可以是采用Tableau中创建报表元数据，以实现多个用户通过Portal平台访问Tableau上同一报表元数据的目的。
可以理解地，由于用户输入的数据访问请求包括用户ID和目标文件夹ID，可基于用户ID确定对应的目标用户类ID，再判断目标用户类ID对应的用户类是否具有访问目标文件夹ID对应的文件夹(即目标文件夹)的权限；并在目标用户类ID对应的用户类具有访问目标文件夹的权限时，可在Portal平台上显示与目标文件夹ID对应的报表ID对应的报表元数据。该数据访问权限管理方法中，可使Tableau Server中每一报表元数据的权限对应的用户类而不是单一用户，以实现对Tableau Server中报表访问权限的灵活管理，提高Tableau的应用范围。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施过程构成任何限定。
实施例2
图3示出与实施例1中数据访问权限管理方法一一对应的数据访问权限管理装置的原理框图。如图3所示，该数据访问权限管理装置包括报表元数据获取模块11、文件夹数据创建模块12、关联关系创建模块13、用户类请求获取模块14、用户类权限配置模块15、个人请求获取模块16和个人权限配置模块17。其中，报表元数据获取模块11、文件夹数据创建模块12、关联关系创建模块13、用户类请求获取模块14、用户类权限配置模块15、 个人请求获取模块16和个人权限配置模块17的实现功能与实施例1中数据访问权限管理方法对应的步骤S11-S17一一对应，为避免赘述，本实施例不一一详述。
报表元数据获取模块11，用于在Tableau中获取报表元数据，报表元数据包括报表ID。
文件夹数据创建模块12，用于在Portal平台中创建文件夹数据，文件夹数据包括至少一个文件夹，文件夹包括文件夹ID。
关联关系创建模块13，用于在Portal平台中创建报表ID与文件夹ID的关联关系。
用户类请求获取模块14，用于获取用户输入的用户类权限配置请求，用户类权限配置请求包括用户类ID和目标文件夹ID。
用户类权限配置模块15，用于在Portal平台中基于用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
进一步地，该数据访问权限管理装置还包括个人请求获取模块16和个人权限配置模块17。
个人请求获取模块16，用于获取用户输入的个人权限配置请求，个人权限配置请求包括用户ID和目标用户类ID。
个人权限配置模块17，用于在Portal平台中基于个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与目标用户类ID对应的用户类权限。
进一步地，报表元数据获取模块11，还用于将报表元数据存储在PostgreSQL数据库，并形成报表关系表，报表关系表包括至少一个报表元数据信息，报表元数据信息包括报表ID和报表名称。
文件夹数据创建模块12，还用于将文件夹数据存储在Oracle数据库中，并形成文件夹关系表，文件夹关系表包括至少一个文件夹信息，文件夹信息包括文件夹ID和文件夹名称。
关联关系创建模块13，还用于在Portal平台中创建关联关系信息表，关联关系信息表包括至少一个关联信息，关联信息包括报表ID与文件夹ID。
进一步地，文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个文件夹。
进一步地，如图4所示，数据访问权限管理装置还包括数据访问请求获取模块21、目标用户类ID获取模块22、用户权限判断模块23和报表数据显示模块24。其中，数据 访问请求获取模块21、目标用户类ID获取模块22、用户权限判断模块23和报表数据显示模块24的实现功能与实施例2中数据访问权限管理方法对应的步骤S21-S24一一对应，为避免赘述，本实施例不一一详述。
数据访问请求获取模块21，用于获取用户输入的数据访问请求，数据访问请求包括用户ID和目标文件夹ID。
目标用户类ID获取模块22，用于基于用户ID，获取对应的目标用户类ID。
用户权限判断模块23，用于判断目标用户类ID对应的用户类是否具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
报表数据显示模块24，用于若目标用户类ID对应的用户类权限为访问与目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与目标文件夹ID对应的报表ID对应的报表元数据。
实施例3
本实施例提供一计算机可读存储介质，该计算机可读存储介质上存储有计算机可读指令，该计算机可读指令被处理器执行时实现实施例1中数据访问权限管理方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中数据访问权限管理装置中各模块/单元的功能，为避免重复，这里不再赘述。
所述计算机可读存储介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。
实施例4
图5是本申请一实施例提供的终端设备50的示意图。如图5所示，该实施例的终端设备50包括：处理器51、存储器52以及存储在存储器52中并可在处理器51上运行的计算机可读指令53。处理器51执行计算机可读指令53时实现上述实施例1提供的数据访问权限管理方法的各个步骤，例如图1所示的步骤S11-S17，或者图2所示的步骤S21-S24。或者，处理器51执行计算机可读指令53时实现上述实施例2提供的数据访问权限管理装置中各模块/单元的功能。如图3所示的报表元数据获取模块11、文件夹数据创建模块12、关联关系创建模块13、用户类请求获取模块14、用户类权限配置模块15、个人请求获取模块16和个人权限配置模块17的功能；或者如图4中的数据访问请求获取模块21、目标用户类ID获取模块22、用户权限判断模块23和报表数据显示模块24的功能。
示例性的，计算机可读指令53可以被分割成一个或多个模块/单元，一个或者多个模块/单元被存储在存储器52中，并由处理器51执行，以完成本申请。一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令53的指令段，该指令段用于描述计算机可读指令53在终端设备50中的执行过程。
例如，计算机可读指令53可以被分割成图3所示的报表元数据获取模块11、文件夹数据创建模块12、关联关系创建模块13、用户类请求获取模块14、用户类权限配置模块15、个人请求获取模块16和个人权限配置模块17，各模块具体功能如下：
报表元数据获取模块11，用于在Tableau中获取报表元数据，报表元数据包括报表ID。
文件夹数据创建模块12，用于在Portal平台中创建文件夹数据，文件夹数据包括至少一个文件夹，文件夹包括文件夹ID。
关联关系创建模块13，用于在Portal平台中创建报表ID与文件夹ID的关联关系。
用户类请求获取模块14，用于获取用户输入的用户类权限配置请求，用户类权限配置请求包括用户类ID和目标文件夹ID。
用户类权限配置模块15，用于在Portal平台中基于用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
个人请求获取模块16，用于获取用户输入的个人权限配置请求，个人权限配置请求包括用户ID和目标用户类ID。
个人权限配置模块17，用于在Portal平台中基于个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与目标用户类ID对应的用户类权限。
进一步地，报表元数据获取模块11，还用于将报表元数据存储在PostgreSQL数据库，并形成报表关系表，报表关系表包括至少一个报表元数据信息，报表元数据信息包括报表ID和报表名称。
文件夹数据创建模块12，还用于将文件夹数据存储在Oracle数据库中，并形成文件夹关系表，文件夹关系表包括至少一个文件夹信息，文件夹信息包括文件夹ID和文件夹名称。
关联关系创建模块13，还用于在Portal平台中创建关联关系信息表，关联关系信息表包括至少一个关联信息，关联信息包括报表ID与文件夹ID。
进一步地，文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个文件 夹。
或者，计算机可读指令53可以被分割成图4所示的数据访问请求获取模块21、目标用户类ID获取模块22、用户权限判断模块23和报表数据显示模块24，各模块的具体功能如下：
数据访问请求获取模块21，用于获取用户输入的数据访问请求，数据访问请求包括用户ID和目标文件夹ID。
目标用户类ID获取模块22，用于基于用户ID，获取对应的目标用户类ID。
用户权限判断模块23，用于判断目标用户类ID对应的用户类是否具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
报表数据显示模块24，用于若目标用户类ID对应的用户类权限为访问与目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与目标文件夹ID对应的报表ID对应的报表元数据。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围内。

Claims (20)

  1. 一种数据访问权限管理方法，其特征在于，包括：
    在Tableau中获取报表元数据，所述报表元数据包括报表ID；
    在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
    在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
    获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
    在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
  2. 如权利要求1所述的数据访问权限管理方法，其特征在于，所述数据访问权限管理方法还包括：
    获取用户输入的个人权限配置请求，所述个人权限配置请求包括用户ID和目标用户类ID；
    在Portal平台中基于所述个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与所述目标用户类ID对应的用户类权限。
  3. 如权利要求2所述的数据访问权限管理方法，其特征在于，所述数据访问权限管理方法还包括：
    获取用户输入的数据访问请求，所述数据访问请求包括用户ID和目标文件夹ID；
    基于所述用户ID，获取对应的目标用户类ID；
    判断目标用户类ID对应的用户类是否具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限；
    若目标用户类ID对应的用户类具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与所述目标文件夹ID对应的报表ID对应的报表元数据。
  4. 如权利要求1所述的数据访问权限管理方法，其特征在于，所述在Tableau中获取报表元数据，还包括：将所述报表元数据存储在PostgreSQL数据库，并形成报表关系表，所述报表关系表包括至少一个报表元数据信息，所述报表元数据信息包括所述报表ID和报表名称；
    所述在Portal平台中创建文件夹数据，还包括：将所述文件夹数据存储在Oracle数 据库中，并形成文件夹关系表，所述文件夹关系表包括至少一个文件夹信息，所述文件夹信息包括文件夹ID和文件夹名称；
    所述在Portal平台中创建所述报表ID与所述文件夹ID的关联关系，包括：在所述Portal平台中创建关联关系信息表，所述关联关系信息表包括至少一个关联信息，所述关联信息包括所述报表ID与所述文件夹ID。
  5. 如权利要求1-4任一项所述的数据访问权限管理方法，其特征在于，所述文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个所述文件夹。
  6. 一种数据访问权限管理装置，其特征在于，包括：
    报表元数据获取模块，用于在Tableau中获取报表元数据，所述报表元数据包括报表ID；
    文件夹数据创建模块，用于在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
    关联关系创建模块，用于在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
    用户类请求获取模块，用于获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
    用户类权限配置模块，用于在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
  7. 如权利要求6所述的数据访问权限管理装置，其特征在于，所述数据访问权限管理装置还包括：
    个人请求获取模块，用于获取用户输入的个人权限配置请求，所述个人权限配置请求包括用户ID和目标用户类ID；
    个人权限配置模块，用于在Portal平台中基于所述个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与所述目标用户类ID对应的用户类权限。
  8. 如权利要求7所述的数据访问权限管理装置，其特征在于，所述数据访问权限管理装置还包括：
    数据访问请求获取模块，用于获取用户输入的数据访问请求，所述数据访问请求包括用户ID和目标文件夹ID；
    目标用户类ID获取模块，用于基于所述用户ID，获取对应的目标用户类ID；
    用户权限判断模块，用于判断目标用户类ID对应的用户类是否具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限；
    报表数据显示模块，用于若目标用户类ID对应的用户类具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与所述目标文件夹ID对应的报表ID对应的报表元数据。
  9. 如权利要求6所述的数据访问权限管理装置，其特征在于，
    所述报表元数据获取模块，还用于将所述报表元数据存储在PostgreSQL数据库，并形成报表关系表，所述报表关系表包括至少一个报表元数据信息，所述报表元数据信息包括所述报表ID和报表名称；
    所述文件夹数据创建模块，还用于将所述文件夹数据存储在Oracle数据库中，并形成文件夹关系表，所述文件夹关系表包括至少一个文件夹信息，所述文件夹信息包括文件夹ID和文件夹名称；
    所述关联关系创建模块，还用于在所述Portal平台中创建关联关系信息表，所述关联关系信息表包括至少一个关联信息，所述关联信息包括所述报表ID与所述文件夹ID。
  10. 如权利要求6-9任一项所述的数据访问权限管理装置，其特征在于，所述文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个所述文件夹。
  11. 一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    在Tableau中获取报表元数据，所述报表元数据包括报表ID；
    在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
    在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
    获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
    在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
  12. 如权利要求11所述的终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    获取用户输入的个人权限配置请求，所述个人权限配置请求包括用户ID和目标用户 类ID；
    在Portal平台中基于所述个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与所述目标用户类ID对应的用户类权限。
  13. 如权利要求12所述的终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：
    获取用户输入的数据访问请求，所述数据访问请求包括用户ID和目标文件夹ID；
    基于所述用户ID，获取对应的目标用户类ID；
    判断目标用户类ID对应的用户类是否具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限；
    若目标用户类ID对应的用户类具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与所述目标文件夹ID对应的报表ID对应的报表元数据。
  14. 如权利要求11所述的终端设备，其特征在于，所述在Tableau中获取报表元数据，还包括：将所述报表元数据存储在PostgreSQL数据库，并形成报表关系表，所述报表关系表包括至少一个报表元数据信息，所述报表元数据信息包括所述报表ID和报表名称；
    所述在Portal平台中创建文件夹数据，还包括：将所述文件夹数据存储在Oracle数据库中，并形成文件夹关系表，所述文件夹关系表包括至少一个文件夹信息，所述文件夹信息包括文件夹ID和文件夹名称；
    所述在Portal平台中创建所述报表ID与所述文件夹ID的关联关系，还包括：在所述Portal平台中创建关联关系信息表，所述关联关系信息表包括至少一个关联信息，所述关联信息包括所述报表ID与所述文件夹ID。
  15. 如权利要求11-14任一项所述的终端设备，其特征在于，所述文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个所述文件夹。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现如下步骤：
    在Tableau中获取报表元数据，所述报表元数据包括报表ID；
    在Portal平台中创建文件夹数据，所述文件夹数据包括至少一个文件夹，所述文件夹包括文件夹ID；
    在Portal平台中创建所述报表ID与所述文件夹ID的关联关系；
    获取用户输入的用户类权限配置请求，所述用户类权限配置请求包括用户类ID和目标文件夹ID；
    在Portal平台中基于所述用户类权限配置请求进行用户类权限配置，以使用户类ID对应的用户类具有访问与目标文件夹ID对应的报表ID对应的报表元数据的权限。
  17. 如权利要求16所述的计算机可读存储介质，其特征在于，所述计算机可读指令被处理器执行时还实现如下步骤：
    获取用户输入的个人权限配置请求，所述个人权限配置请求包括用户ID和目标用户类ID；
    在Portal平台中基于所述个人权限配置请求进行个人权限配置，以使用户ID对应的用户具有与所述目标用户类ID对应的用户类权限。
  18. 如权利要求17所述的计算机可读存储介质，其特征在于，所述计算机可读指令被处理器执行时还实现如下步骤：
    获取用户输入的数据访问请求，所述数据访问请求包括用户ID和目标文件夹ID；
    基于所述用户ID，获取对应的目标用户类ID；
    判断目标用户类ID对应的用户类是否具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限；
    若目标用户类ID对应的用户类具有访问与所述目标文件夹ID对应的报表ID对应的报表元数据的权限，则显示与所述目标文件夹ID对应的报表ID对应的报表元数据。
  19. 如权利要求16所述的计算机可读存储介质，其特征在于，所述在Tableau中获取报表元数据，还包括：将所述报表元数据存储在PostgreSQL数据库，并形成报表关系表，所述报表关系表包括至少一个报表元数据信息，所述报表元数据信息包括所述报表ID和报表名称；
    所述在Portal平台中创建文件夹数据，还包括：将所述文件夹数据存储在Oracle数据库中，并形成文件夹关系表，所述文件夹关系表包括至少一个文件夹信息，所述文件夹信息包括文件夹ID和文件夹名称；
    所述在Portal平台中创建所述报表ID与所述文件夹ID的关联关系，还包括：在所述Portal平台中创建关联关系信息表，所述关联关系信息表包括至少一个关联信息，所述关联信息包括所述报表ID与所述文件夹ID。
  20. 如权利要求16-19任一项所述的计算机可读存储介质，其特征在于，所述文件夹数据包括多层嵌套式文件夹组，每一层文件夹组包括至少一个所述文件夹。
PCT/CN2018/077473 2017-09-19 2018-02-28 数据访问权限管理方法、装置、终端设备及存储介质 WO2019056705A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
SG11201809880RA SG11201809880RA (en) 2017-09-19 2018-02-28 Data access authority management method, apparatus, terminal device and storage medium
US16/098,129 US11093631B2 (en) 2017-09-19 2018-02-28 Data access authority management method, apparatus, terminal device and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710845614.3A CN108280365B (zh) 2017-09-19 2017-09-19 数据访问权限管理方法、装置、终端设备及存储介质
CN201710845614.3 2017-09-19

Publications (1)

Publication Number Publication Date
WO2019056705A1 true WO2019056705A1 (zh) 2019-03-28

Family

ID=62801239

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077473 WO2019056705A1 (zh) 2017-09-19 2018-02-28 数据访问权限管理方法、装置、终端设备及存储介质

Country Status (4)

Country Link
US (1) US11093631B2 (zh)
CN (1) CN108280365B (zh)
SG (1) SG11201809880RA (zh)
WO (1) WO2019056705A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111159164A (zh) * 2020-01-16 2020-05-15 四川天翼网络服务有限公司 基于参数化传递的报表数据访问权限控制方法
CN111383087A (zh) * 2020-02-25 2020-07-07 远光软件股份有限公司 报表的访问方法、装置、存储介质及电子设备
CN111581156A (zh) * 2020-04-27 2020-08-25 上海鸿翼软件技术股份有限公司 一种文件权限控制方法、装置、设备及介质
CN112131837A (zh) * 2020-09-22 2020-12-25 平安证券股份有限公司 业务报告配置方法、装置、计算机设备和存储介质
CN112163236A (zh) * 2020-10-14 2021-01-01 上海妙一生物科技有限公司 文件访问方法、装置、系统和计算机可读存储介质
CN117313073A (zh) * 2023-11-28 2023-12-29 武汉海昌信息技术有限公司 涉及权限分配的数据处理方法、装置、介质及电子设备

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109254965A (zh) * 2018-08-22 2019-01-22 中国平安人寿保险股份有限公司 模型处理方法及系统、存储介质和电子设备
CN109299147B (zh) * 2018-09-26 2024-04-05 中国平安人寿保险股份有限公司 数据库访问处理方法、装置、计算机设备和存储介质
CN110020525B (zh) * 2019-03-05 2023-09-26 平安科技（深圳）有限公司 Kubernetes平台的权限配置方法、装置、计算机设备及存储介质
CN110618990B (zh) * 2019-08-15 2024-04-30 中国平安财产保险股份有限公司 清单报表设置方法、系统及清单报表获取方法
CN110555200A (zh) * 2019-09-05 2019-12-10 北京思维造物信息科技股份有限公司 一种报表发布方法、装置及设备
CN110929280B (zh) * 2019-11-25 2023-03-28 普元信息技术股份有限公司 大数据环境下基于元数据实现数据权限控制的系统及其方法
CN110968851A (zh) * 2019-12-19 2020-04-07 北京思特奇信息技术股份有限公司 一种业务权限的管控方法、管控系统及计算机可读介质
CN111447275B (zh) * 2020-03-26 2021-01-01 深圳市中盛瑞达科技有限公司 存储系统和存储装置
CN113779517A (zh) * 2020-06-09 2021-12-10 武汉斗鱼鱼乐网络科技有限公司 一种权限获取方法、装置、设备及存储介质
CN112115134A (zh) * 2020-08-04 2020-12-22 北京金山云网络技术有限公司 数据存储方法、装置、电子设备及存储介质
CN112019424A (zh) * 2020-09-08 2020-12-01 协鑫集成科技股份有限公司 一种基于Tableau的报表推送方法、终端设备及存储介质
CN113765876B (zh) * 2020-11-30 2023-09-26 北京沃东天骏信息技术有限公司 报表处理软件的访问方法和装置
CN113204790B (zh) * 2021-05-25 2024-03-01 北京字跳网络技术有限公司 一种视图权限处理方法、装置、设备及介质
CN115757526B (zh) * 2022-12-02 2023-08-15 广州市玄武无线科技股份有限公司 一种元数据的管理方法、装置、设备和计算机存储介质
CN116521488B (zh) * 2023-07-03 2024-03-26 杭州新中大科技股份有限公司 基于元数据的自定义单据溯源方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101178730A (zh) * 2007-12-14 2008-05-14 清华大学 面向集成化企业模型的文档管理方法
CN102346835A (zh) * 2010-07-22 2012-02-08 日本电气株式会社 内容管理设备和内容管理方法
CN102693318A (zh) * 2012-05-30 2012-09-26 华为技术有限公司 一种报表查询方法及设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7016919B2 (en) * 2002-03-29 2006-03-21 Agilent Technologies, Inc. Enterprise framework and applications supporting meta-data and data traceability requirements
CN101470862A (zh) * 2007-12-27 2009-07-01 新奥特（北京）视频技术有限公司 一种通过对文件夹的权限设置完成节目流程设置的方法
CN102004868A (zh) * 2009-09-01 2011-04-06 上海杉达学院 一种基于角色访问控制的信息系统数据存储层及组建方法
CN102902767A (zh) * 2012-09-25 2013-01-30 北京科东电力控制系统有限责任公司 一种表格快速搭建的方法及系统
CN104063636A (zh) * 2013-03-22 2014-09-24 鸿富锦精密工业（深圳）有限公司 角色权限控制方法及系统
CN105740656A (zh) * 2014-12-09 2016-07-06 航天信息股份有限公司 数据权限管理方法及装置
US9948655B1 (en) * 2016-04-15 2018-04-17 AtScale, Inc. Data access authorization for dynamically generated database structures
US11709833B2 (en) * 2016-06-24 2023-07-25 Dremio Corporation Self-service data platform
US10521442B1 (en) * 2016-09-16 2019-12-31 EMC IP Holding Company LLC Hierarchical value-based governance architecture for enterprise data assets
US20180081953A1 (en) * 2016-09-21 2018-03-22 idea5, LLC System, computer-implemented method, and computer program for improving access to and usefulness of data for business intelligence
US20180082227A1 (en) * 2016-09-21 2018-03-22 idea5, LLC System, computer-implemented method, and computer program for improving business intelligence and peer analysis
CN111699696B (zh) * 2017-12-06 2023-11-28 V-诺瓦国际有限公司 用于对字节流进行编码和解码的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101178730A (zh) * 2007-12-14 2008-05-14 清华大学 面向集成化企业模型的文档管理方法
CN102346835A (zh) * 2010-07-22 2012-02-08 日本电气株式会社 内容管理设备和内容管理方法
CN102693318A (zh) * 2012-05-30 2012-09-26 华为技术有限公司 一种报表查询方法及设备

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111159164A (zh) * 2020-01-16 2020-05-15 四川天翼网络服务有限公司 基于参数化传递的报表数据访问权限控制方法
CN111159164B (zh) * 2020-01-16 2024-01-30 四川天翼网络股份有限公司 基于参数化传递的报表数据访问权限控制方法
CN111383087A (zh) * 2020-02-25 2020-07-07 远光软件股份有限公司 报表的访问方法、装置、存储介质及电子设备
CN111581156A (zh) * 2020-04-27 2020-08-25 上海鸿翼软件技术股份有限公司 一种文件权限控制方法、装置、设备及介质
CN111581156B (zh) * 2020-04-27 2024-03-29 上海鸿翼软件技术股份有限公司 一种文件权限控制方法、装置、设备及介质
CN112131837A (zh) * 2020-09-22 2020-12-25 平安证券股份有限公司 业务报告配置方法、装置、计算机设备和存储介质
CN112131837B (zh) * 2020-09-22 2023-11-03 平安证券股份有限公司 业务报告配置方法、装置、计算机设备和存储介质
CN112163236A (zh) * 2020-10-14 2021-01-01 上海妙一生物科技有限公司 文件访问方法、装置、系统和计算机可读存储介质
CN117313073A (zh) * 2023-11-28 2023-12-29 武汉海昌信息技术有限公司 涉及权限分配的数据处理方法、装置、介质及电子设备
CN117313073B (zh) * 2023-11-28 2024-02-02 武汉海昌信息技术有限公司 涉及权限分配的数据处理方法、装置、介质及电子设备

Also Published As

Publication number Publication date
US11093631B2 (en) 2021-08-17
SG11201809880RA (en) 2019-04-29
US20200356688A1 (en) 2020-11-12
CN108280365B (zh) 2019-04-12
CN108280365A (zh) 2018-07-13

Similar Documents

Publication Publication Date Title
WO2019056705A1 (zh) 数据访问权限管理方法、装置、终端设备及存储介质
US20210385087A1 (en) Zero-knowledge identity verification in a distributed computing system
US11082226B2 (en) Zero-knowledge identity verification in a distributed computing system
US10135609B2 (en) Managing a database management system using a blockchain database
Aboutorabiª et al. Performance evaluation of SQL and MongoDB databases for big e-commerce data
US9298829B2 (en) Performing a function on rows of data determined from transitive relationships between columns
US11489839B2 (en) Automatic user permission refinement through cluster-based learning
EP2577507B1 (en) Data mart automation
US11709878B2 (en) Enterprise knowledge graph
US20120054146A1 (en) Systems and methods for tracking and reporting provenance of data used in a massively distributed analytics cloud
US20140067810A1 (en) Methods and apparatus for partitioning data
US11886431B2 (en) Real-time analytical queries of a document store
US11755768B2 (en) Methods, apparatuses, and systems for data rights tracking
US9418077B2 (en) System and method for geo-location data type searching in an on demand environment
US9483510B2 (en) Correlating database and storage performance views
US9069817B2 (en) Database row access control
CN110928963A (zh) 针对运维业务数据表的列级权限知识图谱构建方法
WO2021034329A1 (en) Data set signatures for data impact driven storage management
US11416583B2 (en) Determining software application license usage
US20240171586A1 (en) Secure roles for data sharing
US20200021599A1 (en) Profile-based dashboard system
Singh et al. E-Government database: A Retrospective study
de Carvalho Victorino et al. A Proposed Architecture to Support the Processing and Analysis of Structured and Unstructured Massive Data Sets in the Brazilian Army

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18858789

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18858789

Country of ref document: EP

Kind code of ref document: A1