A safe and environment-friendly data management system and method

Abstract

A safe and environmentally friendly data management system and method are disclosed, relating to the field of big data governance. The system includes: a server node; a front-end interactive interface, including access points and business directories for multiple ledger modules; a back-end storage architecture, including ledger documents and storage directories; a dynamic indexing engine for establishing a mapping relationship between the front-end interactive interface and the back-end storage architecture; and a heterogeneous integration unit for embedding internal hyperlinks and external URLs pointing to the regulatory platform within the ledger modules. By adopting this solution, multi-format independent ledger units are integrated flatly on the main interface, allowing direct navigation with a click, conforming to the habits of paper-based browsing. It is adaptable to multiple terminals, supports low-threshold deployment and smooth upgrades, and combines compliance management, intelligent retrieval, and cross-departmental collaboration functions. It overcomes the shortcomings of traditional compliance systems, such as cumbersome processes and inefficiency, enabling low-cost implementation, improving data management efficiency and compliance risk control levels, and adapting to the needs of enterprises of different sizes.

Description

Technical Field

[0001] This application relates to the field of big data governance, specifically to a safe and environmentally friendly data management system and method. Background Technology

[0002] Currently, enterprises are required to deploy various compliance management systems, which are implemented in three main ways: First, they manually record, organize, and archive data using traditional paper ledgers or scattered electronic documents, with separate logins to the corresponding platforms required for reporting government-regulated business; second, they rely on specialized regulatory platforms built under the leadership of government departments, where enterprises only need to fill in and upload the specified data as required, and the platform's functions and architecture are uniformly set by the regulatory department; and third, some larger enterprises use specialized management systems built on database technology, which require professional programming development and database configuration and server debugging during deployment.

[0003] However, these implementation methods all have significant drawbacks: Traditional models suffer from scattered data storage, lack of unified standards, low information transparency, and difficulty in traceability. The inability of multiple users to operate synchronously can lead to data inconsistencies and untimely updates. Furthermore, ledger maintenance relies on repetitive manual labor, resulting in low work efficiency. Government regulatory platforms have weak personalization and adaptability, poor flexibility and scalability, and each platform operates independently with data disconnected. Enterprises need to switch between multiple systems, making it impossible to achieve one-stop collaboration between internal management and supervision, and it is difficult to cover the entire process of refined internal management. Professional management systems have high technical barriers, and deployment and maintenance require skills such as database configuration and professional programming. Non-technical managers find it difficult to operate them independently, and the systems lack integration, failing to seamlessly integrate Office software, local multimedia resources, and links to multiple government regulatory platforms. Dispersed resource management further increases operational complexity and management costs, and it is difficult to quickly adjust functional modules and directory structures according to changes in enterprise business, resulting in poor adaptability.

[0004] This invention aims to provide a low-cost, easy-to-implement, intuitive, and efficient ledger management solution that complements existing complex compliance systems, addressing their shortcomings in operational flexibility, ease of use, and intuitive retrieval. It also balances compliance and scalability, enabling a smooth upgrade from basic electronic to intelligent digitalization, significantly improving enterprise data management efficiency, cross-departmental collaboration capabilities, and compliance risk control, adapting to the needs of enterprises of different sizes. Summary of the Invention

[0005] This application provides a safe and environmentally friendly data management system and method to solve the problems of traditional safe and environmentally friendly data management systems.

[0006] Firstly, this application provides a safe and environmentally friendly data management system, the system comprising: Server nodes are used to provide web page access services; The front-end interactive interface includes access points and business directories for multiple ledger modules, including the fire safety ledger module. The backend storage architecture includes ledger documents and a storage directory for querying ledger documents; A dynamic indexing engine is used to establish a mapping relationship between the front-end interactive interface and the back-end storage architecture; The heterogeneous integration unit is used to embed internal hyperlinks and external URL links pointing to the regulatory platform in the ledger module.

[0007] By adopting the above technical solutions, centralized and digital management of multiple independent ledger files is achieved, providing users with direct hyperlinks and integrating them into a single main interface for an intuitive browsing experience. A precise mapping between front-end interaction and back-end storage is established to ensure rapid retrieval and access to ledger documents. Simultaneously, internal resources and external regulatory platforms are integrated to achieve one-stop coverage for enterprise internal management and government supervision, supporting multi-user online synchronous operation and improving the efficiency, coverage, and collaboration of security and environmental protection data management.

[0008] In one specific feasible implementation, the dynamic indexing engine includes: The multidimensional feature encoding module is used to extract and encode structured features from ledger documents in the backend storage architecture, generating a unified feature representation that includes at least time, space and semantic dimensions. The dynamic mapping relationship construction unit is used to establish a mapping relationship network that dynamically adjusts with the feature dimension weight between the business directory nodes of the front-end interactive interface and the physical storage location of the back-end storage architecture, based on a unified feature representation.

[0009] By adopting the above technical solutions, the comprehensive extraction and unified encoding of multi-dimensional structured features of safety and environmental protection ledger documents are achieved, breaking through the limitations of traditional indexes that rely solely on single keywords for retrieval, and ensuring the completeness and standardization of feature descriptions. The construction of a dynamic mapping relationship network enables flexible association between business directory nodes and the physical storage location of ledger documents, and the dynamic adjustment mechanism of feature dimension weights adapts to the needs of different retrieval scenarios, greatly improving the accuracy and flexibility of ledger document positioning. In particular, it is suitable for the business characteristics of frequent multi-dimensional retrieval needs in the field of safety and environmental protection, reducing invalid retrieval paths, shortening ledger document retrieval time, and improving data management efficiency.

[0010] In one specific implementation scheme, the dynamic mapping relationship building unit is configured as follows: In response to user access operations, a dynamic weight configuration vector is generated based on the contextual preferences implied by the current operation. The dynamic weight configuration vector is used to adjust the weight ratio of different dimensions in the unified feature representation. Based on the adjusted unified feature representation, the association strength between business directory nodes and ledger documents is recalculated, and the connection paths and priorities in the mapping relationship network are updated in real time according to the association strength and the preset association strength threshold.

[0011] By adopting the above technical solutions, the dynamic weight configuration vector is used to make targeted adjustments to the unified feature representation, enabling the mapping relationship network to accurately adapt to the user's current access intent and improve the accuracy of the association between business directory nodes and target ledger documents. The real-time calculation of association strength and the dynamic updating of connection paths ensure that the mapping relationship network always maintains an efficient connection structure, reducing the impact of invalid connections on retrieval efficiency. Users can quickly locate ledger documents that are highly relevant to the current operation, further improving the retrieval efficiency and ease of use of security and environmental protection data.

[0012] In one specific feasible implementation, the dynamic indexing engine includes: The self-organizing optimization module is used to continuously collect the actual access frequency and user operation feedback of each connection path in the mapping relationship network. The mapping strategy iteration unit adjusts the generation strategy of the dynamic weight configuration vector and the calculation parameters of the association strength based on the collected data, so that the structure of the mapping relationship network evolves in the direction of optimal access efficiency.

[0013] By adopting the above technical solutions, the self-organizing optimization of the mapping relationship network is realized, enabling the generation strategy of the dynamic weight configuration vector and the calculation parameters of the association strength to be continuously adjusted according to the actual user data, gradually adapting to the user's access habits and business needs; the structure of the mapping relationship network is continuously optimized during use, and the access efficiency is continuously improved after long-term use, reducing the user's manual filtering operations and further reducing the operational costs of secure and environmentally friendly data management.

[0014] In one specific implementation scheme, the heterogeneous integration unit includes: The heterogeneous link network construction module is used to build a unified link graph for the ledger module, including internal nodes and external nodes. The internal nodes are associated with ledger documents and business directories within the system, while the external nodes are associated with regulatory platform resources pointed to by external URL links. The intelligent link filtering unit is used to identify a subset of links that are semantically and functionally strongly related to the current context from the unified link graph, based on the context information of the current access.

[0015] By adopting the above technical solutions, unified link management of system ledger documents, business catalogs and external regulatory platform resources is achieved, breaking down the barriers of scattered storage of heterogeneous resources; based on the filtering of link subsets according to context information, it is ensured that the output links are highly relevant to the user's current business needs, reducing the user's switching operations between multiple systems and multiple documents, improving the collaborative efficiency of security and environmental protection data management and external regulatory docking, and reducing the operational complexity of compliance management.

[0016] In one specific implementation, the smart link filtering unit is configured as follows: The current context information is parsed to extract the core task intent and key entity identifiers; In the unified link graph, direct links between nodes are obtained through the link discovery process, and potential link paths indirectly associated through intermediate nodes are evaluated. By combining the weight of direct links with the inference confidence of potential link paths, the context relevance score of each candidate link is calculated, and the candidate links are then filtered and ranked based on the context relevance score.

[0017] By adopting the above technical solutions, a comprehensive evaluation of direct and potential link paths in the unified link graph can be achieved. The calculation of context relevance scores ensures the accuracy of the screening results. The subset of links filtered and sorted by score enables users to quickly obtain the internal and external links most relevant to their current business needs, reduce the interference of invalid links, further improve the collaborative efficiency of security and environmental protection data management and external regulatory docking, and reduce the time cost of cross-platform operations.

[0018] In one specific implementation scheme, the heterogeneous integration unit includes: The link network self-evolution module is used to monitor the operation data of the user adopting the subset of links output by the intelligent link filtering unit; The graph structure adaptive adjustment unit dynamically adjusts the weights of links between nodes in the unified link graph based on the operational data.

[0019] By adopting the above technical solutions, the unified link graph can be made adaptively evolved. The dynamic adjustment of the link weights between nodes gives higher priority to highly relevant links. The identification and link optimization of high-frequency co-occurring node pairs further improve the practicality of the link network. The unified link graph can continuously adapt to changes in user habits and business needs. After long-term use, the accuracy and effectiveness of link screening will continue to improve, the efficiency of users in obtaining relevant internal and external resources will be further improved, and the collaboration and convenience of security and environmental protection data management will be strengthened.

[0020] A second aspect of this application provides a method for managing safe and environmentally friendly data, the method comprising: The server node responds to access requests and loads the front-end interactive interface. In response to user access to the ledger module, a dynamic mapping relationship between the business directory in the front-end interactive interface and the corresponding storage directory in the back-end storage architecture is established through a dynamic index engine. Through the heterogeneous integration unit, the internal hyperlinks pointing to the ledger documents in the back-end storage architecture and the external URL links pointing to the external regulatory platform are rendered and output in parallel in the front-end interactive interface. Based on the user's interactive operations on the front-end interface, and using dynamic mapping relationships, the system locates and retrieves the corresponding ledger document or redirects to the corresponding external regulatory platform.

[0021] A third aspect of this application provides an electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the above-described method steps.

[0022] A fourth aspect of this application provides a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the method steps described above. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of a safe and environmentally friendly data management system provided in an embodiment of this application; Figure 2 This is a schematic diagram of a front-end interactive interface provided in an embodiment of this application; Figure 3 This is a flowchart illustrating a safe and environmentally friendly data management method provided in an embodiment of this application. Detailed Implementation

[0024] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0025] In the description of the embodiments of this application, the words "for example" or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design that is described as "for example" or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the words "for example" or "for instance" is intended to present the relevant concepts in a specific manner.

[0026] In the description of the embodiments of this application, the term "multiple" means two or more. For example, multiple systems means two or more systems, and multiple screen terminals means two or more screen terminals. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0027] Please refer to Figure 1 A schematic diagram of a safe and environmentally friendly data management system is presented. This system can be implemented using a computer program or a microcontroller. The computer program can be integrated into a computer device or run as a standalone application. Specifically, the system includes: The server node provides web page access services; the front-end interactive interface includes access points and business directories for multiple ledger modules, including a fire safety ledger module; the back-end storage architecture includes ledger documents and a storage directory for querying ledger documents; the dynamic index engine is used to establish a mapping relationship between the front-end interactive interface and the back-end storage architecture; and the heterogeneous integration unit is used to embed internal hyperlinks and external URL links pointing to the regulatory platform in the ledger modules.

[0028] In this embodiment, the server node is configured as a server device that deploys Windows Internet Information Services (IIS) to provide web page access services to users. Users send Hypertext Transfer Protocol (HTTP) requests to the server node through their browsers. After receiving the requests, the server node responds and returns the corresponding web page resources, thus supporting the network access foundation of the entire system.

[0029] refer to Figure 2 The front-end interactive interface is configured as a web page that users can access through a browser. This interface intuitively displays the access points of multiple ledger modules and the corresponding business catalogs of each module. The ledger modules cover multiple key areas such as the safety standard system, special equipment system, and fire ledger module. Among them, the fire ledger module is specifically used to centrally manage various ledger information related to fire protection. Users can enter the business catalog page of the fire ledger module by clicking the access point of the fire ledger module on the front-end interactive interface.

[0030] The backend storage architecture is configured as a structured file directory system on the server nodes. This storage directory has a pre-defined hierarchical folder structure according to the classification of the ledger module and business type. It is specifically used to store fire ledger documents and ledger documents of other modules. Fire ledger documents include basic information documents of fire protection facilities, maintenance record documents, training and exercise documents, inspection activity documents, etc. The document formats cover portable document formats, Microsoft Word documents, and image files such as PNG and JPG formats.

[0031] The dynamic indexing engine is configured as a functional module in the system to associate the front-end interactive interface with the back-end storage architecture. By parsing data such as the path information, file name, and file type of the back-end storage directory, it establishes a one-to-one mapping relationship between the access entry points and business directories of each ledger module on the front-end interactive interface and the back-end storage directory and the ledger documents therein. When a user clicks on the access entry point or business directory of the fire ledger module on the front-end interactive interface, the dynamic indexing engine can accurately locate the corresponding storage directory in the back-end storage architecture according to the preset mapping relationship and retrieve the ledger documents under that directory for the user to access.

[0032] The heterogeneous integration unit is configured as a functional module within the system to integrate internal and external resources. Within the fire safety ledger module, both internal hyperlinks and external Uniform Resource Locators (URLs) pointing to the regulatory platform are embedded. The internal hyperlinks point to other ledger modules related to fire safety ledgers within the system or to different business directories within the fire safety ledger module. The external URLs directly link to the official webpages of fire safety regulatory platforms at various levels of government. Users can directly access the government regulatory platform to handle relevant business through these external URLs within the fire safety ledger module without having to enter a separate website address, achieving one-stop coverage for the integration of internal fire safety ledger management with government regulation.

[0033] In some embodiments, the number of server nodes can be 1, deployed in the enterprise's internal LAN, supporting up to 100 users within the enterprise to access online simultaneously; the number of access points for the ledger module in the front-end interactive interface can be 9, and the access point for the fire ledger module can be the 7th entry in the display order of the front-end interactive interface; the storage directory name corresponding to the fire ledger module in the back-end storage architecture can be 07-Fire Protection and Lightning Protection System, and the number of subfolders under this directory can be 9; the mapping relationship data established by the dynamic index engine can be stored in an Extensible Markup Language (XML) file; the number of external URL links embedded in the heterogeneous integration unit can be 3, pointing to the municipal, provincial, and national fire supervision platforms respectively.

[0034] Based on the above embodiments, as another optional embodiment, the service catalog includes: The system consists of three levels: first-level directory, second-level directory, and third-level directory. For the fire safety ledger module, the first-level directory is configured as the entry point for the fire safety ledger. The second-level directory includes basic fire safety information, general layout of fire safety facilities, fire safety maintenance records, fire safety training and drills, and fire safety inspection activities. The third-level directory is used to classify and archive the second-level directory. The dynamic indexing engine dynamically updates the business directory based on the storage directory.

[0035] The business directory is configured as a hierarchical directory structure within the fire safety ledger module in the front-end interactive interface, used for classifying, displaying, and managing ledger documents, including a first-level directory, a second-level directory, and a third-level directory.

[0036] In some embodiments, the first-level directory is configured as the top-level directory corresponding to the access entry of the fire alarm ledger module on the front-end interactive interface. This directory is the first level for users to enter the fire alarm ledger module. Users can enter the first-level directory page by clicking the access entry icon or text label of the fire alarm ledger module on the front-end interactive interface. The first-level directory page intuitively displays the category list of the second-level directory, providing users with clear operation guidance.

[0037] The second-level directory is a core business category directory divided under the first-level directory, which can include basic fire protection information, general layout of fire protection facilities, fire protection maintenance records, fire training and drills, and fire inspection activities. Specifically, the basic fire protection information directory is used to collect basic parameter documents such as the model, specifications, installation date, manufacturer, and responsible person of fire protection facilities; the general layout of fire protection facilities directory is used to store general layout documents and zoning drawings that mark the distribution and installation points of all fire protection facilities within the factory area; the fire protection maintenance records directory is used to store records related to the daily maintenance, troubleshooting, and component replacement of fire protection facilities; the fire training and drills directory is used to manage documents such as fire training plans, training materials, drill schemes, participant attendance sheets, and drill summary reports; and the fire inspection activities directory is used to collect documents such as fire inspection notices, inspection record forms, problem rectification notices, and rectification completion reports.

[0038] The third-level directory is a further subdivision of the archive directory under each second-level directory. It is used to classify and archive the ledger documents under the second-level directory in a more detailed manner, so that users can quickly locate the target document. For example, under the second-level directory of fire protection maintenance records, the third-level directory can be divided into fire hydrant maintenance record directory, fire extinguisher maintenance record directory, fire pump maintenance record directory, etc., according to the type of fire protection facility, or into routine maintenance record directory, fault repair record directory, emergency repair record directory, etc., according to the type of problem. Different third-level directories store the ledger documents of the corresponding categories.

[0039] In some embodiments, the dynamic indexing engine monitors in real time the changes in the storage directory corresponding to the fire safety ledger module in the backend storage architecture. Changes in the backend storage directory include adding subfolders, deleting existing folders, modifying folder names, adding ledger documents, deleting ledger documents, moving document storage paths, etc. When the dynamic indexing engine detects these changes, it automatically updates the business directory structure of the fire safety ledger module in the front-end interactive interface to ensure that the business directory displayed on the front end is consistent with the actual structure of the backend storage directory.

[0040] In some embodiments, the number of second-level directories in the fire protection ledger module can be 5, corresponding one-to-one with the basic fire protection information, general layout of fire protection facilities, fire protection maintenance records, fire protection training and drills, and fire protection inspection activities defined in claim 2; the number of third-level directories under each second-level directory can be 3-8, depending on the actual business management needs; the time interval for the dynamic index engine to monitor changes in the backend storage directory can be 30 seconds, that is, the backend storage directory is scanned once every 30 seconds to detect whether there are any changes and to update the business directory synchronously.

[0041] Based on the above embodiments, as another optional embodiment, the storage directory includes: The system includes time and location subdirectories; the front-end interactive interface includes a selector control used to filter the corresponding subdirectories.

[0042] In some embodiments, the storage directory includes a time subdirectory and a location subdirectory, both of which are subfolders under the storage directory corresponding to the fire log module in the backend storage architecture, and together with other subdirectories, they constitute a complete storage system.

[0043] In this embodiment of the application, the time subdirectory is a folder that classifies and stores fire safety ledger documents according to the time dimension. It is used to distinguish ledger documents generated in different time periods, making it convenient to query and manage them by time dimension. The division of the time subdirectory can be done by year, and each year subdirectory can be further divided into more detailed time subdirectories by month. Fire safety ledger documents from different time periods are stored in the corresponding time subdirectory according to the time of generation.

[0044] The Location subdirectory is a folder that categorizes and stores fire safety records documents according to the location of fire safety facilities. It is used to distinguish fire safety records documents related to different areas. The division of the Location subdirectory can be set according to the layout of the enterprise's factory area, such as dividing by workshop or by factory area. Fire safety records documents related to a specific location are stored in the corresponding Location subdirectory.

[0045] In some embodiments, the front-end interactive interface is provided with a selector control. The selector control is an interactive element in the business directory page of the fire safety ledger module, and may include drop-down menus, date selection boxes, check boxes, etc. The selector control is used to provide users with input entry points for filtering conditions, so that users can filter the corresponding subdirectories and ledger documents in them by time or location.

[0046] When users need to filter by time, they can select a specific year and month using the time selector control. After selection, the dynamic indexing engine receives the filtering instruction, locates the corresponding time subdirectory based on the user's selected time conditions, and displays all ledger documents under that time subdirectory on the front-end interactive interface. When users need to filter by location, they can select a specific location name using the location selector control. The dynamic indexing engine locates the corresponding location subdirectory based on the selected location conditions and displays the ledger documents under that location subdirectory, achieving accurate filtering and fast searching of ledger documents.

[0047] Based on the above embodiments, as another optional embodiment, the dynamic indexing engine includes: The multidimensional feature encoding module is used to extract and encode structured features from ledger documents in the backend storage architecture, generating a unified feature representation that includes at least time, spatial, and semantic dimensions. The dynamic mapping relationship construction unit is used to establish a mapping relationship network that dynamically adjusts with the feature dimension weights between the business directory nodes in the front-end interactive interface and the physical storage locations in the backend storage architecture based on the unified feature representation.

[0048] In some embodiments, the multidimensional feature encoding module supports user-defined addition of feature dimensions, such as business priority dimensions. Users only need to add the extraction rules and encoding standards for the new dimension in the encoding configuration file to complete the expansion. The mapping relationship network supports regular automatic backups, and the backup cycle can be set by the administrator to avoid network data loss. For batch additions of safety and environmental protection ledger documents, the multidimensional feature encoding module can start batch encoding mode to automatically complete feature extraction and encoding, and automatically connect the encoded documents to the mapping relationship network without manual intervention.

[0049] Based on the above embodiments, as another optional embodiment, the dynamic mapping relationship construction unit is configured as follows: In response to user access operations, a dynamic weight configuration vector is generated based on the contextual preferences implied by the current operation. The dynamic weight configuration vector is used to adjust the weight ratio of different dimensions in the unified feature representation. Based on the adjusted unified feature representation, the association strength between business directory nodes and ledger documents is recalculated, and the connection paths and priorities in the mapping relationship network are updated in real time according to the association strength and the preset association strength threshold.

[0050] In some embodiments, the dynamic weight configuration vector is generated based on the identified task intent, and the sum of the weight values ​​of each dimension in the vector is 1. For example, for a compliance verification task intent, the generated dynamic weight configuration vector has a time dimension of 0.4, a spatial dimension of 0.1, and a semantic dimension of 0.5; for a rectification tracking task intent, the generated dynamic weight configuration vector has a time dimension of 0.2, a spatial dimension of 0.4, and a semantic dimension of 0.4; and for a general query task intent, the generated dynamic weight configuration vector has a time dimension of 0.3, a spatial dimension of 0.1, and a semantic dimension of 0.6.

[0051] The dynamic mapping relationship construction unit, based on the adjusted unified feature representation, recalculates the association strength between business directory nodes and ledger documents. The association strength is calculated using a weighted summation formula, which includes: D=(s1*w1)+(s2*w2)+(s3*w3); Where D is the association strength, s1 is the temporal similarity, w1 is the temporal weight, s2 is the spatial similarity, w2 is the spatial weight, s3 is the semantic similarity, and w3 is the semantic weight.

[0052] In some embodiments, temporal similarity, spatial similarity, and semantic similarity are numerical values ​​representing the matching degree of the corresponding dimensions in a unified feature representation, with values ​​ranging from 0 to 1, and the association strength value range is also from 0 to 1.

[0053] The dynamic mapping relationship construction unit presets a correlation strength threshold, which is a critical value for judging the validity of connection paths. The system default correlation strength threshold is 0.6, and administrators can adjust the threshold size according to business needs through the front-end interactive interface. Based on the recalculated correlation strength and the preset correlation strength threshold, the dynamic mapping relationship construction unit updates the connection paths and priorities in the mapping relationship network in real time. Connection paths with a correlation strength greater than or equal to the threshold are retained, while invalid connection paths with a correlation strength less than the threshold are deleted. Simultaneously, valid connection paths are sorted according to their correlation strength values, and the top five connection paths with the highest correlation strength are marked as priority recommended paths. The updated mapping relationship network is synchronized to the storage medium in real time to ensure that subsequent user accesses use the latest mapping relationships.

[0054] In some embodiments, the association strength threshold can be customized according to the business module. For example, the association strength threshold of the fire protection ledger module is set to 0.65, and the association strength threshold of the environmental protection ledger module is set to 0.6.

[0055] Based on the above embodiments, as another optional embodiment, the dynamic indexing engine includes: The self-organizing optimization module continuously collects the actual access frequency and user operation feedback of each connection path in the mapping relationship network; the mapping strategy iteration unit corrects the generation strategy of the dynamic weight configuration vector and the calculation parameters of the association strength based on the collected data, so that the structure of the mapping relationship network evolves in the direction of optimal access efficiency.

[0056] In some embodiments, the mapping strategy iteration unit corrects the generation strategy of the dynamic weight configuration vector and the calculation parameters of the association strength based on the data collected by the self-organizing optimization module. The correction process follows the evolution goal of optimal access efficiency.

[0057] To correct the generation strategy of dynamic weight configuration vectors, the mapping strategy iteration unit statistically analyzes the weight vectors corresponding to the connection paths adopted by users under different task intentions. If the user dwell time increases significantly after the spatial dimension weight is increased in a certain type of task intention, the weight vector generation rule corresponding to that task intention is adjusted to increase the basic weight ratio of the spatial dimension. To correct the calculation parameters of association strength, the mapping strategy iteration unit analyzes the three-dimensional similarity distribution of high-frequency access connection paths. If the semantic dimension similarity accounts for a generally high proportion in high-frequency paths, the semantic dimension weight coefficient in the association strength calculation is adjusted to strengthen the influence of the semantic dimension on the association strength.

[0058] The correction operation of the mapping strategy iteration unit is triggered by the cumulative amount of collected data. When the amount of collected data reaches a preset threshold, the correction is initiated to ensure the reliability of the correction strategy. The corrected generation strategy and calculation parameters are applied to the dynamic mapping relationship construction unit in real time, so that the structure of the mapping relationship network evolves towards the direction of optimal access efficiency.

[0059] In some embodiments, the self-organizing optimization module supports users to manually submit operation feedback. Users can mark the relevance level of the current connection path through the front-end interactive interface. The relevance level is divided into four levels: highly relevant, relevant, average, and irrelevant. This feedback data, together with the data automatically collected by the system, serves as the basis for correction.

[0060] Based on the above embodiments, as another optional embodiment, the heterogeneous integration unit includes: The heterogeneous link network construction module is used to build a unified link graph for the ledger module, including internal and external nodes. The internal nodes are associated with ledger documents and business directories within the system, while the external nodes are associated with regulatory platform resources pointed to by external URL links. The intelligent link filtering unit is used to identify a subset of links that are semantically and functionally strongly related to the current context from the unified link graph based on the current access context information.

[0061] In some embodiments, the heterogeneous link network construction module establishes connection relationships between nodes according to preset rules. Internal nodes establish connections based on business relevance, for example, the fire protection facility ledger document node establishes a connection with the fire protection maintenance record node; internal nodes establish connections with external nodes based on functional relevance, for example, the environmental monitoring report node establishes a connection with the environmental monitoring platform data reporting page node, ultimately forming a unified link graph covering internal and external resources of the system.

[0062] The context information of the current access includes the business directory node currently accessed by the user, the content of the ledger document being viewed, and the recently entered search keywords. The intelligent link filtering unit analyzes this context information, identifies the current business needs of the user, and then filters out the link nodes that can meet the needs from the unified link graph to form a link subset. The link subset contains several internal node links and external node links that are highly relevant to the current context.

[0063] Based on the above embodiments, as another optional embodiment, the intelligent link filtering unit is configured as follows: The current context information is parsed to extract the core task intent and key entity identifiers; in the unified link graph, direct links between nodes are obtained through the link discovery process, and potential link paths indirectly associated through intermediate nodes are evaluated; by combining the weight of direct links and the inference confidence of potential link paths, the context relevance score of each candidate link is calculated, and each candidate link is screened and ranked according to the context relevance score.

[0064] In this embodiment of the application, the key entity identifier is the core object involved in the context information, such as a specific fire protection facility ID, an environmental protection testing project name, a regulatory platform name, etc. The parsing process uses natural language processing technology to identify keywords and semantic associations in the context information, thereby determining the core task intent and key entity identifier.

[0065] The intelligent link filtering unit obtains direct links between nodes in the unified link graph through a link discovery process. This process involves traversing the unified link graph to find nodes directly connected to the currently accessed node; the links corresponding to these directly connected nodes are considered direct links. Simultaneously, the intelligent link filtering unit evaluates potential link paths indirectly associated through intermediate nodes. A potential link path is a connection path established between the current accessed node and the target node through one or more intermediate nodes. The evaluation process calculates the inference confidence of the potential link path based on the correlation strength between the intermediate nodes and the current accessed node and the target node. The inference confidence is used to characterize the relevance of the link corresponding to the path to the current context.

[0066] The intelligent link filtering unit combines the weight of direct links with the inference confidence of potential link paths to calculate the context relevance score of each candidate link. The calculation formula includes: S = a1*k1 + a2*k2; Where S is the context relevance score, a1 is the direct link weight, k1 is the first coefficient, a2 is the inference confidence, and k2 is the second coefficient.

[0067] In some embodiments, the first coefficient and the second coefficient are weighting coefficients, and their sum is 1. The intelligent link filtering unit filters and sorts each candidate link based on the context relevance score, selects candidate links with scores greater than or equal to a preset score threshold, arranges them in descending order of score, forms the final subset of links, and outputs it to the front-end interactive interface.

[0068] In some embodiments, the first coefficient is set to 0.7 by default, and the second coefficient is set to 0.3 by default. Administrators can adjust the values ​​of the two coefficients according to the link relevance priority. The preset scoring threshold is set to 0.5, and candidate links below this threshold will be filtered.

[0069] Based on the above embodiments, as another optional embodiment, the heterogeneous integration unit includes: The link network self-evolution module is used to monitor the operation data of the user adopting the link subset output by the intelligent link filtering unit; the graph structure adaptive adjustment unit dynamically adjusts the weight of the links between nodes in the unified link graph according to the operation data.

[0070] In some embodiments, the operation data adopted by the user includes the links clicked and accessed by the user, the access duration, whether the link is saved, whether the link is added to the list of frequently used links, etc. The link network self-evolution module monitors these operation data in real time and stores them in the data cache area.

[0071] The graph structure adaptive adjustment unit dynamically adjusts the weights of links between nodes in the unified link graph based on the operational data monitored by the link network self-evolution module. For links frequently clicked by users, the graph structure adaptive adjustment unit increases the weight of the link by a preset ratio; for links repeatedly ignored by users or marked as irrelevant, the weight of the link is decreased by a preset ratio; for links that have not been accessed by users for a long time, they are marked as dormant and their weight is reduced to the minimum value.

[0072] Meanwhile, the graph structure adaptive adjustment unit identifies high-frequency co-occurrence node pairs by analyzing operational data. High-frequency co-occurrence node pairs refer to combinations of nodes that are clicked continuously or visited sequentially within a short period of time during user access. The graph structure adaptive adjustment unit establishes direct connections for high-frequency co-occurrence node pairs or increases their link weights, making the structure of the unified link graph more in line with the user's actual usage habits.

[0073] In some embodiments, the link weight adjustment ratio is set to increase or decrease by 0.1 each time, and the weight value range is kept between 0 and 1.

[0074] Based on the above embodiments, as another optional embodiment, the system includes: Multi-user collaboration unit; The multi-user collaboration unit is used to configure permissions for storage directories and ledger documents in the backend storage architecture, define the read and write operation scope of users with different roles, and record the operation logs of each user accessing and modifying ledger documents through the dynamic index engine. The operation logs are associated with metadata tags.

[0075] In this embodiment of the application, the multi-user collaboration unit is a functional module used to manage multi-user access permissions and record operation logs, in order to ensure data security and operation traceability when multiple users perform online synchronous operations.

[0076] In some embodiments, the multi-user collaboration unit first classifies system users into roles. Based on the enterprise's management needs and user responsibilities, system users are divided into different roles, such as system administrators, safety and environmental protection specialists, and general users. Different roles correspond to different permission ranges. Subsequently, the multi-user collaboration unit configures corresponding access permissions and operation permissions for each storage directory and its ledger documents in the backend storage architecture, clarifying the read and write operation scope for different user roles.

[0077] The system administrator role has the highest privileges, allowing read and write operations on all storage directories and ledger documents, including adding, modifying, deleting, downloading, and printing documents. The safety and environmental protection specialist role has read and write permissions for specific storage directories, which are usually related to the role's job responsibilities. For example, a safety and environmental protection specialist responsible for fire management has read and write permissions for all storage directories in the fire ledger module and can maintain fire-related ledger documents. The ordinary viewer role only has read-only permissions for some storage directories and can only view the corresponding ledger documents. They cannot perform write operations such as modification, deletion, or addition to ensure that data is not accidentally manipulated.

[0078] The multi-user collaboration unit is also responsible for recording the operation logs of each user accessing and modifying the ledger documents through the dynamic indexing engine. The operation logs include key information such as the user's account information, operation type, operation object, and operation time. The operation type is specifically divided into viewing, adding, modifying, deleting, downloading, and printing. The operation object is the specific fire ledger document name and its corresponding storage path. The operation time is accurate to the second.

[0079] Operation logs are linked to the metadata tags of the corresponding fire safety ledger documents. Each operation log entry records core information from the metadata tags of the corresponding fire safety ledger document, such as fire safety facility identification, modification timestamp, and the person responsible for the update, creating a complete chain of association between the operation logs and the ledger documents. When it is necessary to trace the operation history of a specific fire safety ledger document, administrators can query the operation logs corresponding to the document's metadata tags through the multi-user collaborative unit. This allows them to clearly understand which users, when, and what operations were performed on the document. In case of data anomalies or errors, the responsible party can be quickly identified, ensuring data security and integrity.

[0080] In some embodiments, the role division may also include a department administrator role, which has read and write permissions for the relevant storage directories of its own department and read-only permissions for the storage directories of other departments; the operation logs are stored in a dedicated log folder in the backend storage architecture in an encrypted manner, and only the system administrator role can view and export the operation logs.

[0081] Based on the above embodiments, as another optional embodiment, the system includes: The identity authentication gateway is used to encrypt user credentials. When a user accesses the front-end interactive interface, the identity authentication gateway performs local authentication. After successful authentication, it unlocks the access permission to call the dynamic indexing engine. The user account lifecycle management can be completed by editing the encrypted configuration file of the identity authentication gateway.

[0082] In this embodiment, the identity authentication gateway is a security verification module set between the front-end interactive interface and the dynamic index engine. It is used to verify the user's identity, ensure the security of system access, and prevent unauthorized users from entering the system.

[0083] In some embodiments, the identity authentication gateway is used to encrypt user credentials, which include a user account and a user password. The identity authentication gateway uses an encryption algorithm to encrypt the user account and password before storing them. The encryption algorithm can be a symmetric encryption algorithm, such as the Advanced Encryption Standard (AES) algorithm, or an asymmetric encryption algorithm. Encryption prevents user credentials from being transmitted or stored in plaintext, reducing the risk of user credential leakage.

[0084] When a user accesses the front-end interactive interface, they first need to enter their username and password on the login page. After receiving the user's entered credentials, the identity authentication gateway immediately encrypts the credentials and then executes the local identity verification process. Local identity verification refers to the identity authentication gateway retrieving preset valid user credentials from the encrypted configuration file on the server node and comparing the encrypted user input credentials with the preset valid user credentials.

[0085] If the two match, authentication is successful. The authentication gateway sends an authorization signal to the dynamic index engine, unlocking access to the dynamic index engine. The user can then access the system's front-end interface, access the fire safety ledger module and other functional modules, and query, view, and download ledger documents through the dynamic index engine. If the two do not match, authentication fails. The authentication gateway refuses to send an authorization signal to the dynamic index engine, maintaining access restrictions, and the user cannot access the system.

[0086] In some embodiments, user account lifecycle management includes operations such as account creation, modification, deactivation, and deletion. These operations are all completed by editing the encrypted configuration file of the identity authentication gateway. The encrypted configuration file is a web page configuration file stored on the server node, specifically the script part in the web page code. Administrators do not need professional programming knowledge and can open the encrypted configuration file using common Office software or simple web page editing tools.

[0087] When creating a user account, the administrator simply adds a user record in the encrypted configuration file, entering the user account and corresponding encrypted password. When modifying a user account, the administrator locates the corresponding user record in the configuration file and modifies its password or related permission information. When deactivating a user account, the administrator changes the status of the corresponding user record in the configuration file to invalid, preventing the account from being authenticated. When deleting a user account, the administrator simply deletes the corresponding user record in the configuration file. The entire account management process does not rely on a backend database, making it simple and convenient, and conforming to the design philosophy of zero technical barriers.

[0088] In some embodiments, the storage path of the encrypted configuration file can be the config subfolder under the web folder of the server node; the identity authentication gateway supports the same account to log in on up to 3 devices at the same time. When the number of devices logging in exceeds the limit, a prompt will be made that the account has already logged in on other devices; the encryption processing of user passwords adopts the AES-256 encryption algorithm to ensure the encryption strength of the password.

[0089] Based on the above embodiments, as another optional embodiment, the system includes: The visualization association module is used to establish a connection between visualized data and corresponding ledger documents. The visualized data includes 3D models and floor plans of fire protection facilities. When a user clicks on a fire protection facility icon on the fire protection facility master plan, the visualization association module is triggered and displays the visualized data and ledger documents associated with the target fire protection facility.

[0090] In this embodiment of the application, the visualization association module is used to establish the association between visualized data and fire protection ledger documents, and to realize interactive display. This module can improve users' intuitive understanding of fire protection facility-related information and enhance the ease of use of the system.

[0091] In some embodiments, the visualization data includes a 3D model and a floor plan of the fire protection facilities. The 3D model is a digital model constructed using professional 3D modeling software (such as AutoCAD or SketchUp). This model accurately reproduces the actual size, structure, and appearance of the fire protection facilities, clearly displaying their three-dimensional form and internal structure. The floor plan is a 2D drawing created using drafting software (such as CAD or Visio). The drawing indicates the specific location, distribution, and relationships between adjacent facilities of all fire protection facilities within the factory area, facilitating users' understanding of the overall layout of the fire protection facilities.

[0092] The visualized data is stored in a standardized file format in the corresponding storage directory of the backend storage architecture. The visualization association module binds the visualized data to the corresponding fire protection ledger document by establishing an identification association relationship. Specifically, a unique identification information is assigned to each fire protection facility's 3D model and floor plan. This identification information is consistent with the fire protection facility identifier in the metadata tag of the corresponding fire protection facility's ledger document. By establishing a one-to-one correspondence between the visualized data and the ledger document through the same identification information, it ensures that each visualized data can be accurately matched to the corresponding ledger document.

[0093] After a user clicks the access point for the fire protection facility master plan in the fire protection ledger module of the front-end interactive interface, the interface will display the fire protection facility master plan. This master plan features icons for various fire protection facilities, each corresponding to an actual fire protection facility and labeled with its name or simplified number. When a user clicks on a fire protection facility icon, the front-end interactive interface sends a trigger signal to the visualization association module. This signal contains the identification information of the fire protection facility corresponding to the clicked icon.

[0094] After receiving a trigger signal, the visualization association module searches for associated visualization data and ledger documents in the backend storage architecture based on the fire protection facility identification information. It finds the matching 3D model, floor plan, and corresponding basic information documents, maintenance records, and inspection records for the fire protection facility. Subsequently, the visualization association module feeds back the search results to the front-end interactive interface, displaying the visualization data and ledger documents associated with the target fire protection facility in a pop-up window or new page. Users can simultaneously view the 3D structure, actual location, and relevant ledger information of the fire protection facility on the same interface, gaining a clear and comprehensive understanding of the target fire protection facility's status and improving management efficiency.

[0095] In some embodiments, the visualized data may also include operation demonstration videos of fire protection facilities, which show in detail the usage methods and operation steps of the fire protection facilities; the visualization association module supports users to rotate, scale, and pan the displayed 3D model, making it convenient for users to view the fire protection facilities from different angles; the ledger documents displayed in the pop-up window support one-click download and printing, meeting the actual usage needs of users.

[0096] Based on the above embodiments, as another optional embodiment, the backend storage architecture includes: The compliant product digital catalog includes safety and environmental protection product types and store qualification review standards. The heterogeneous integration unit also embeds external e-commerce URL links corresponding to the compliant product catalog. These external e-commerce URL links only point to stores selling safety and environmental protection products that have passed the qualification review. The compliant product types include signage, labor protection products, fire protection facilities, environmental testing services, environmental assessment services, and products related to environmental protection construction projects.

[0097] In some embodiments, the compliant digital catalog of goods includes two main modules: safety and environmental protection product types and store qualification review standards. The safety and environmental protection product types are strictly limited to signage, personal protective equipment, fire-fighting equipment, environmental testing services, environmental assessment services, and products related to environmental protection construction projects. Each product type is further subdivided into specific product subcategories and specification ranges.

[0098] The store qualification review standards clearly stipulate the conditions that e-commerce stores must meet to be included in the directory, including having a valid business license and relevant production or sales qualification certificates for the products. The review standards are stored in the directory in the form of digital rules for easy automated verification.

[0099] Based on the above embodiments, as another optional embodiment, the system includes: The deployment unit is used to package the server node, front-end interactive interface, back-end storage architecture, dynamic index engine and heterogeneous integration unit into an executable installation package, which is used to complete the installation and configuration of the system on the target server in one step.

[0100] In some embodiments, the deployment unit is used to package all core components of the system, such as the server node runtime environment, front-end interactive interface web page files, the preset directory system of the back-end storage architecture, the core program of the dynamic indexing engine, the heterogeneous integration unit link library, and other functional module dependent components, into a single executable installation package. The packaging process can be optimized and extended based on the PyInstaller tool.

[0101] refer to Figure 3Based on the above embodiments, as another optional embodiment, this application also provides a safe and environmentally friendly data management method, including the following steps: The server node responds to access requests and loads the front-end interactive interface. In response to user access operations to the ledger module, the dynamic index engine parses and establishes a dynamic mapping relationship between the business directory in the front-end interactive interface and the corresponding storage directory in the back-end storage architecture. Through the heterogeneous integration unit, the front-end interactive interface renders and outputs internal hyperlinks pointing to ledger documents in the back-end storage architecture and external URL links pointing to external regulatory platforms in parallel. Based on the user's interactive operations in the front-end interactive interface and the dynamic mapping relationship, the corresponding ledger document is located and called or the user is redirected to the corresponding external regulatory platform.

[0102] It should be noted that the system provided in the above embodiments is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0103] Based on the above embodiments, as another optional embodiment, the present application embodiment may further include a computer storage medium, which may store multiple instructions adapted for loading by a processor and executing a method of the above embodiments. For the specific execution process, please refer to the detailed description of the above embodiments, which will not be repeated here.

[0104] Based on the above embodiments, as another optional embodiment, this application embodiment may further include an electronic device. The electronic device may include: at least one processor, at least one communication bus, a user interface, at least one network interface, and a memory.

[0105] The communication bus is used to enable communication between these components.

[0106] The user interface may include a display screen and a camera. Optional user interfaces may also include standard wired interfaces and wireless interfaces.

[0107] The network interface may include standard wired interfaces and wireless interfaces (such as Wi-Fi interfaces).

[0108] The processor may include one or more processing cores. It connects to various parts of the server via various interfaces and lines, executing instructions, programs, code sets, or instruction sets stored in memory, and accessing data stored in memory to perform various server functions and process data. Optionally, the processor may be implemented using at least one of the following hardware forms: Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also be implemented as a separate chip without being integrated into the processor.

[0109] The memory may include random access memory (RAM) or read-only memory. Optionally, the memory may include a non-transitory computer-readable storage medium. The memory can be used to store instructions, programs, code, code sets, or instruction sets. The memory may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor. As a computer storage medium, the memory may include an operating system, a network communication module, a user interface module, and an application program of one method.

[0110] In electronic devices, the user interface is primarily used to provide an input interface for users and to acquire user input data; while the processor can be used to call an application program stored in memory that represents a method. When executed by one or more processors, this causes the electronic device to perform one or more methods as described in the above embodiments. It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps can be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0111] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0112] In the various embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between apparatuses or units may be electrical or other forms.

[0113] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0114] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0115] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0116] The above are merely exemplary embodiments of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Other embodiments of this disclosure will readily conceive of those skilled in the art upon consideration of the specification and the disclosure of practical truths.

[0117] This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described in this disclosure. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. A secure and environmentally friendly data management system, characterized by, The system includes: Server nodes are used to provide web page access services; The front-end interactive interface includes access points and business directories for multiple ledger modules, including a fire safety ledger module. The backend storage architecture includes ledger documents and a storage directory for querying the ledger documents; A dynamic indexing engine is used to establish the mapping relationship between the front-end interactive interface and the back-end storage architecture; The heterogeneous integration unit is used to embed internal hyperlinks and external URL links pointing to the regulatory platform in the ledger module.

2. The secure environmental data management system of claim 1, wherein, The dynamic indexing engine includes: The multidimensional feature encoding module is used to extract and encode structured features from the ledger documents in the backend storage architecture, generating a unified feature representation that includes at least time, space and semantic dimensions. The dynamic mapping relationship construction unit is used to establish a mapping relationship network that dynamically adjusts with the feature dimension weights between the business directory nodes of the front-end interactive interface and the physical storage locations of the back-end storage architecture, based on the unified feature representation.

3. The safety and environmental protection data management system according to claim 2, characterized in that, The dynamic mapping relationship construction unit is configured as follows: In response to a user's access operation, a dynamic weight configuration vector is generated based on the contextual preferences implied by the current operation. The dynamic weight configuration vector is used to adjust the weight ratio of different dimensions in the unified feature representation. Based on the adjusted unified feature representation, the association strength between business directory nodes and ledger documents is recalculated, and the connection paths and priorities in the mapping relationship network are updated in real time according to the association strength and the preset association strength threshold.

4. The secure environmental data management system of claim 3, wherein, The dynamic indexing engine includes: The self-organizing optimization module is used to continuously collect the actual access frequency and user operation feedback of each connection path in the mapping relationship network; The mapping strategy iteration unit corrects the generation strategy of the dynamic weight configuration vector and the calculation parameters of the association strength based on the collected data, so that the structure of the mapping relationship network evolves in the direction of optimal access efficiency.

5. The safety and environmental protection data management system according to claim 1, characterized in that, The heterogeneous integration unit includes: The heterogeneous link network construction module is used to construct a unified link graph including internal nodes and external nodes for the ledger module. The internal nodes are associated with ledger documents and business directories within the system, and the external nodes are associated with the regulatory platform resources pointed to by the external URL links. The intelligent link filtering unit is used to identify a subset of links that are semantically and functionally strongly related to the current context from the unified link graph based on the context information of the current access.

6. The secure environmental data management system of claim 5, wherein, The intelligent link filtering unit is configured as follows: The current context information is parsed to extract the core task intent and key entity identifiers; In the unified link graph, direct links between nodes are obtained through a link discovery process, and potential link paths indirectly associated through intermediate nodes are evaluated. By combining the weights of the direct links with the inference confidence of the potential link paths, a context relevance score is calculated for each candidate link, and the candidate links are then filtered and ranked based on the context relevance score.

7. The safety and environmental protection data management system according to claim 6, characterized in that, The heterogeneous integration unit includes: The link network self-evolution module is used to monitor the operation data of the user adopting the link subset output by the intelligent link filtering unit; The graph structure adaptive adjustment unit dynamically adjusts the weights of links between nodes in the unified link graph based on the operation data.

8. A safe and environmentally friendly data management method, characterized in that, The method includes: The server node responds to access requests and loads the front-end interactive interface. In response to user access to the ledger module, a dynamic mapping relationship between the business directory in the front-end interactive interface and the corresponding storage directory in the back-end storage architecture is parsed and established through a dynamic index engine. Through the heterogeneous integration unit, the front-end interactive interface is rendered in parallel and outputs internal hyperlinks pointing to the ledger documents in the back-end storage architecture, as well as external URL links pointing to the external regulatory platform. Based on the user's interactive operations on the front-end interface, and based on the dynamic mapping relationship, the corresponding ledger document is located and invoked, or the user is redirected to the corresponding external supervision platform.

9. An electronic device, comprising: It includes a processor, a memory, a user interface, and a network interface. The memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory to cause the electronic device to perform the method as described in claim 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores multiple instructions that are adapted to be loaded by a processor and executed as described in claim 8.

Images