Overview
Version
| FineBI Version | Functional Change |
|---|---|
6.0.4 | - |
6.0.5 | Added Data Used Space and Affected Users to Public Data Management. Optimized Public Data Management to allow sub-admins to use. |
6.0.10 | 1. Optimized the content of public data detection.
2. Added Detect Views in Last: N Days, which allows customizing the detection date. 3. Optimized Export Excel to allow exporting public data detection results as an Excel file. |
6.0.12 | Added Lineage Level to the content of public data detection and the search panel. |
6.1.5 | 1. Added User Data Management to help you manage the data in My Analysis. 2. Merged the former Public Data Management and User Data Management to the Data Management tab. 3. Optimized Public Data Management. |
Application Scenarios
As system usage time increases, there are loads of datasets in Public Data.
However, many of these data tables have been abandoned or never used, which leads to messy public space and inconvenient management for the admin.
Function Description
Data Management provided in FineBI allows you and admins to manage the data efficiently.
Public Data Management: You can perform management operations on public data including Unpublish, Stop Update and Delete.
User Data Management: You can perform management operations on the data in My Analysis including Delete.
Public Data Management
The super admin can detect, unpublish, stop updating, and delete the tables in the public data.
The subordinate admin can unpublish, stop updating and delete tables in the public data detected and within the administrative rights.
Detect Public Data
1. Detect the public data.
Only the super admin can perform the operation.
Log in FineBI system as a super admin, and choose System Management > Data Management > Public Data Management to enter the public data management page.
Click Detect Public Data Now to detect all the tables in the public data.
By default, you can check the public data accessed in the past 30 days.
You can modify the setting Detect Access in Last X Day(s) to change dynamic detection range. Setting range: From 1 to 90. Unit: Day.
After you have modified the range, the system will immediately perform a public data detection.
2. Present the detection results.
After the detection is completed, the latest detection results will be automatically displayed on the page. FineBI admins can view a breakdown of public data for which they have management rights.
After the detection is completed, the results will be presented in the form of an itemized table. The detection results include basic information, business using information, system pressure information, and degree of influence.
The detection process is executed in the backend. You can continue the works on other pages.
During the detection process, a detection progress bar is provided for you to know the process.
Last Data Detection Time is displayed, which is helpful for you to plan detection tasks.
3. Re-filter the detection results.
As the amount of public data detected can be very large, you are recommended to re-filter the detection results.
Click Expand Search Panel, select the needed search contents, and click Search to view the corresponding information.
You can click the table field of the tables to sort the detection results.
You can click Export Excel to export the detection results under the current search criteria to an .xlsx format file for business users to confirm.
Public Data Management
FineBI admins can select the public data tables displayed in the list to perform the operations.
Operations include Unpublish, Stop Update, and Delete.
The impact and scope of these operations are shown in the following table:
| Operation | Description |
|---|---|
| Unpublish | 1. It only takes effect on tables whose type is self-service datasets, or tables published from My Analysis to Public Data. 2. Unpublishing on other types of tables do not take effect. |
| Stop Update | 1. It only takes effects on updated tables, not on direct connect tables and the simplest tables. 2. After you set Stop Update for basic tables, the tables here will also stop to update. Also, the setting of Update Single Table > Update Folder changes to Full first time, no update thereafter, which means that the table will be updated fully when the folder where the table is located is updated, and the table will not be updated thereafter. 3. After you set Stop Update for self-service dataset tables, the table here will also stop to update. Update Single Table changes to No Update With Parent Table, which means that the table will not update with its parent table. |
| Delete | 1. It only takes effect on basic tables, not on self-service dataset tables. 2. After you delete the basic table, the deleted table will be moved to the recycle bin. 3. The influence of deleting a table here is the same as deleting a table in other options. |
The detection results and management suggestions are shown in the following table:
| Type | Field | Description | Management Suggestions |
|---|---|---|---|
| Basic information | Table type Note:1. It only exists in the table name field as an identifier, not as an independent field. 2. It does not exist in the exported detection results.
| Data table includes: DB table SQL table EXCEL table Self-service dataset: The table published in public data by a user after analysis. Other tables: Data tables other than the above four types, such as user access logs embedded in FineBI. | - |
| Table Name | The name of a data table | - | |
| Creator | The creator of a data table, including the creator's username and name. Format: Name (Username) | - | |
| Location | The location of a data table in Public Data. Format: Public Data/Folder/Folder/Folder | - | |
| Creation/Publication Time | The creation time of a data table shown in the basic table. A table of the self-service dataset type shows the publishing time when the data table was published from My Analysis to Public Data. Format: yyyy-MM-dd HH:mm:ss | The tables recently created/published may not have been used yet, so it focuses mainly on the historical tables. | |
| Information on the extent of business usage | Recent Visits | The view times the table, table-associated topics, dashboards, components, self-service datasets have been accessed in the last N days. The data is taken from the table fine_record_execute table in Logdb. The view times for the following type are calculated: Subject: type = 501 and 502 Dashboard: type = 101, 102, 105, 106, 107, and 108 Component: type = 301 and 302 Dataset: type = 202 | Tables with no views or low views are the main targets for removal. |
| Last Use Time of Other Users | The latest view time that other users (not the creator) visit a table, its associated subjects, dashboards, components, and self-service datasets in the past N days. If no other users have accessed the data table, the field value is displayed as --. | - | |
| Update Mode | The update modes for self-service dataset settings include:
Update with a parent table.
Not update with a parent table.
The field value in a direct table, the simplest table, and a basic table is displayed as --. | - | |
| Last Update Success Time | The latest time that a table is updated successfully. Format: YYYY-MM-DD HH:MM:SS The field value of direct connect tables, tables that have not been updated, tables that have failed to update for a long time, and the simplest tables are displayed as empty by default. | Tables that have not been updated for a long time are the main targets for removal. | |
| System pressure information | Data Used Space | Calculate the amount of data in the current table | Tables with a lot of updates to be removed/ or sunk into the database. |
| Degree of influence | Number of Affected Users | The number of creators of all direct or indirect sub-tables/components/dashboards of the table, including the creators themselves. Note: | For data tables that are still in use but are ready to be removed/replaced, you can check which users are using them, which is helpful for you to communicate and notify. |
| Number of affected sub-tables | The number of all direct and indirect sub-tables of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected components | The number of all direct and indirect components of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected dashboards | The number of all direct and indirect dashboards of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected analysis documents | The number of all direct and indirect analysis documents | The small number shows the little public significance of the table which can be removed. | |
| Lineage Level | The level of the table in the lineage | Avoid creating and relying on data tables with deep lineage levels. | |
| Permission Inheritance | Whether to enable permission inheritance : Yes or No | If the data is published without Permission Inheritance enabled, there may be differences in permissions after the publication is cancelled. |
User Data Management
User Data Management is only available for FineBI super admins and not available for subordinate admins.
Detecting User Data
1. Detect the user data.
Log in FineBI system as a super admin, and choose System Management > Data Management > User Data Management to enter the user data management page.
Click Detect User Data Now to detect all tables under My Analysis.
By default, you can check the user data accessed in the past 30 days.
You can modify the setting Detect Access in Last X Day(s) to change dynamic detection range. Setting range: from 1 to 90. Unit: Day.
After you have modified the range, the system will immediately perform a user data detection.
2. Present the detection results.
After the detection is completed, the latest detection results will be automatically displayed on the page. The super admin can view all tables in the user data.
After the detection is completed, the results will be presented in the form of an itemized table. The detection results include basic information, business using information, system pressure information, and degree of influence.
The detection process is executed in the backend. The super admin can continue the work in other pages.
During the detection process, a detection progress bar is provided for you to know the process.
Last Data Detection Time is displayed, which is helpful for the super admin to plan detection tasks.
3. Re-filter the detection results.
As the amount of table detected under My Analysis can be very large, you are recommended to re-filter the detection results.
Click Expand Search Panel, select the needed search contents, and click Search to view the corresponding information.
You can click the table field of the tables to sort the detection results.
You can click Export Excel to export the detection results under the current search criteria to an .xlsx format file for business users to confirm.
User Data Management
The super admin can select the table under My Analysis displayed in the list to perform the operation Delete.
After you delete the table, the deleted table will be moved to the recycle bin. The influence of deleting a table here is the same as deleting a table in other options.
The detection results and management suggestions are shown in the following table.
| Classification | Field | Description | Management Suggestions |
|---|---|---|---|
| Basic Information | Source Table Type Note:1. It only exists in the Table Name field as an identifier, not as an independent field. 2. It does not exist in the exported detection results. | Data table includes: Local Excel files in My Analysis and Others | - |
| Table name | The name of a data table | - | |
| Creator | The creator of a data table, including the creator's username and name. Format: Name (Username) | - | |
| Location | The location of a data table in My Analysis. Format: xx's Analysis/Folder/Folder/Topic | - | |
| Creation Time | The creation time of the data table Format: YYYY-MM-DD HH:MM:SS | The tables recently created may not have been used yet, so it focuses mainly on the historical tables. | |
| Information on the extent of business usage | Recent Visits | The number of accesses to the table and its sub-resources on the lineage in the last N days, including: Dataset Edit/Preview Editing/previewing of all sub-datasets Editing/previewing of all subcomponents/dashboards/analysis documents of the dataset Editing/previewing of subcomponents, dashboards, analysis documents of all sub-datasets | Tables with no views or low views are the main targets for removal. |
| Last Use Time of Other Users | The latest view time that other users (not the creator) visit a table, its associated subjects, dashboards, components, and self-service datasets in the past N days. If no other users have accessed the data table, the field value is displayed as --. | - | |
| Update Mode | The update modes for self-service dataset settings include: Update With Parent Table Not Update With Parent Table | - | |
| Last Update Success Time | The latest time that a table is updated successfully. Format: YYYY-MM-dd HH:mm:ss The field value of direct connect tables, tables that have not been updated, and tables that have failed to update for a long time are displayed as empty by default. | Tables that have not been updated for a long time are the main targets for removal. | |
| Published or Not | Published to the public data: Yes/No | Unpublished tables are not public data and have less impact. | |
| Active or Not | Extraction table: Yes/No Direct tables: field values are -- | Inactive tables indicate that the tables are less used and can be removed. | |
| System pressure information | Data Used Space | Calculate the amount of the data in the current table. | Tables with a lot of updates should be removed/sunk to the database. |
| Degree of influence | Number of Affected Users | The number of creators of all direct or indirect sub-tables/components/dashboards of the table, including the creators themselves. Note: | For data tables that are still in use but are ready to be removed/replaced, you can check which users are using them, which is helpful for you to communicate, confirm, and notify. |
| Number of affected sub-tables | The number of all direct and indirect sub-tables of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected components | The number of all direct and indirect components of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected dashboards | The number of all direct and indirect dashboards of the table | The small number shows the little public significance of the table which can be removed. | |
| Number of affected analysis documents | The number of all direct and indirect analysis documents | The small number shows the little public significance of the table which can be removed. | |
| Lineage Level | The level of the table in the lineage | Avoid creating and relying on data tables with deep lineage levels. | |
| Permission Inheritance | Whether to enable permission inheritance includes: Yes/No. | If the data is published without Permission Inheritance enabled, there may be differences in permissions after the publication is cancelled. |
