An Archiving Method and System for an Archival Business System

Abstract

The present invention belongs to the technical field of big data processing, and discloses an archiving method and system for an archive business system. The method designs an archiving scope template and an archiving scope survey template; distributes the archiving scope collection work to each user through a shared link method and authority control, and summarizes it to a business expert terminal, obtains the enterprise archiving scope data with a complete business directory, and outputs it; the archive developer publishes it to the business system developer through an archiving interface, and converts it into data that can be received by the archive system. After the archive system receives the archive data, it performs a test. After the test passes, the archive expert compiles and completes the archiving of the enterprise archive scope data. The present invention proposes the concept of an archiving business line, uses the archiving business line to collect the archiving scope and data, realizes the integration of management, use, and display of the archiving scope, and greatly ensures the improvement of archiving efficiency.

Description

Technical Field

[0001] The present invention belongs to the technical field of big data processing, and particularly relates to an archiving method system for an archive business system. Background Art

[0002] With the rapid development of the Internet, information technology, big data, 5G technology, etc., the enterprise archive management has gradually changed from paper-based to electronic, and more and more document materials show digital and data characteristics. And with the enterprise's full-scale digital transformation, the business system has become a key element in enterprise operation and production, such as ERP systems, OA systems, asset management systems, etc. The business data generated by them, as the records of business processes and business activities, is the core information carrier of enterprise operation and has definite archive data attributes.

[0003] Therefore, the main sources of enterprise archiving data are, firstly, work transaction documents such as financial, business, and construction types generated around the daily work of the enterprise, and secondly, business data generated by the business system. However, at present, the enterprise archiving work faces the following obstacles.

[0004] (1) The archiving scope is extensive and the archiving data is diverse.

[0005] The electronic files generated in the enterprise business system adopt various formats, and the boundary of the archiving scope is blurred. Important files may be omitted, while unnecessary file scopes are instead included in the archiving scope, increasing the management burden.

[0006] (2) The awareness of archiving is weak, the archiving management is weak, the archiving process is cumbersome, the archiving system is imperfect, and the archiving efficiency is low.

[0007] Some enterprise employees believe that they have no obligation to archive to the archive department, and the files to be archived are not as convenient to keep as by themselves. These concepts hinder the smooth progress of the archiving work.

[0008] The archiving methods adopted by enterprises are not scientific enough, resulting in the archiving management work not keeping up with the enterprise's development. Or enterprises lack perfect electronic document management systems and specifications, resulting in the lack of unified standards and processes for archiving work. And with the changes in the organization and business, the archiving scope fails to be adjusted in time, resulting in disconnection from the actual needs, reducing the archiving quality, and causing problems such as important files being omitted or double-archived.

[0009] (3) Archiving is not timely and the archiving frequency is unreasonable.

[0010] Some business systems fail to archive the generated data in time, resulting in the loss or damage of data / files, affecting the integrity and continuity of the archives. And either too high or too low archiving frequency may bring problems. Too high may increase the management cost, and too low may lead to data loss.

[0011] The unscientific classification and organization of archived electronic files leads to inconvenience in file storage, inspection and utilization, and increases management and time costs. Summary of the invention

[0012] In order to overcome the problems existing in the related art, the disclosed embodiments of the present invention provide an archiving method and system for an archive business system.

[0013] The technical solution is as follows: A filing method for an archive business system, comprising:

[0014] S1, design the archiving scope template and the archiving scope investigation template; the archiving scope template is used to determine the files to be archived and record the retention period, carrier type, and file type data of the files; the archiving scope investigation template is used to classify the files to be archived according to different standards and requirements, form a business line template, and record the relationship between the business line and the archiving scope, and the interaction information of the authority;

[0015] S2, based on the results of the archive scope template design and the archive scope survey template design, the archive scope collection work is assigned to each user through the shared link method and permission control, and summarized to the business expert terminal to obtain the enterprise archive scope data with a complete business directory and output it;

[0016] S3, receiving the enterprise archive scope data information with a complete business directory, the archive developer publishes the enterprise archive scope data format and data constraint information to the business system developer through the archive interface, and the business system developer develops data conversion logic according to the above conditions and converts it into data received by the archive system; after receiving the archive data, the archive system performs detection, and reorganizes it after passing the detection to complete the archiving of the enterprise archive scope data.

[0017] In step S1, the archive range template is designed using HTML and JS technology to bind the data structure to the archive range template. A cell is selected in the interface, and the path of the field is obtained through the data structure field node and added to the cell as a cell HTML attribute;

[0018] The archiving scope template includes the archiving person in charge information and the metadata of the archiving scope. The archiving person in charge information includes: name, job title, department and contact information;

[0019] The metadata within the described filing scope is the information presented in each cell, including: serial number, business line, filing scope name, reference document, data source, carrier type, file format, affiliated department, affiliated category, filing timing, retention period, confidentiality level, and scope of knowledge information; the data structure of the filing scope template includes information on the filing responsible person and specific attribute descriptions of the metadata of the filing scope.

[0020] In step S1, the design of the filing scope research template includes:

[0021] Step (a), organizational structure design: The organizational structure includes departments and personnel, and is used to divide the permissions of business lines; personnel are based on the login accounts to verify the permissions of the current user on the business line, and the data type of the organizational structure is an array;

[0022] Step (b), business line design: Conduct business line planning, bind the business line to the filing scope template, and set user permissions for the business line.

[0023] In step (a), the data type of the organizational structure is an array, including:

[0024] isDept is used to identify whether the current node is a department or a person, true for department, false for person; name is the name of the department or person; children is the list of child nodes;

[0025] Verifying the permissions of the current user on the business line includes: After the user logs in, obtain the user's account from the login interface, loop through each business line. If no permissions are set in the business line data, it is displayed normally; if permissions are set in the business line data, loop through the permission data to determine whether the current user's account is equal to any of the accounts in the permissions. If equal, the user has the right to view the business line; if no permission account is equal to the current user's account, the user has no right to view the business line.

[0026] In step (b), business line planning includes: performing operations such as adding, deleting, moving, and copying business lines, and setting operations;

[0027] Setting user permissions for the business line includes: Only users with set permissions can view and edit the current business line and the filing scope template on the line.

[0028] In step (b), binding the business line to the filing scope template includes:

[0029] Each business line is bound to a filing scope template for collecting the files that should be filed and received under the business. The binding methods of the template include:

[0030] The first type, all business lines are bound to one filing scope template;

[0031] The second type is that each business line is bound to an archiving scope template;

[0032] The third type is based on the above two cases of the first and second types. When binding the template, the most recent historical data is synchronously updated;

[0033] Through the above three cases, the archiving scope template is generated into a link and bound to the business line; when the archiving scope template changes and the template version changes, the new template is re-bound to the business line, and the existing data that is the same as the old template is re-populated into the new template.

[0034] Furthermore, re-populating the existing data that is the same as the old template into the new template includes:

[0035] Step1: Extract the old template data, query the cells through the field path on the cell, and fill the data in the cell into the corresponding position of the field;

[0036] Step2: Fill the data into the new template. Query the cells according to the extracted data and the field path of each field in the data, and fill the field data into the cells; when filling, assign the current field value obj'[key_item] to the cell, and make the html of the cell = obj'[key_item].

[0037] In step S2, through the shared link method and permission control, the archiving scope collection work is assigned to each user, including: setting permissions for each business line. After the user logs in, the login account is matched with the business line permissions. If it is matched or the business line has no permissions set, the business line is displayed. If it is not matched, the line is hidden from the user.

[0038] In step S3, the archive developer provides the interface specification, defines the structure and logic of the interface, the input parameters and formats, the interface return, and the data conversion rule description. The business system developer performs data conversion, interface docking, and joint debugging and development work according to the provided information, and sends the archiving scope and its archiving data into the archive system through the interface; among them, the archiving data includes the business line directory, the structured data of the business system, unstructured files, and file metadata. After the archive system receives the archiving data, it performs authenticity, integrity, availability, and security detection of the archives. After passing the detection, the data archiving is completed by the archive expert.

[0039] Another object of the present invention is to provide an archiving system for an archive business system, which implements the archiving method for the archive business system. The system includes:

[0040] The template design module is used to design the archiving scope template and the archiving scope research template. The archiving scope template design is used to determine the files to be archived and record the retention period, carrier type, and file type data of the files. The archiving scope research template design is used to classify the files to be archived according to different standards and requirements, form a business line template, and record the relationship between the business line and the archiving scope, and the interaction information of the permissions.

[0041] The enterprise archive scope data acquisition module is used to distribute the archive scope collection work to each user through the shared link method and permission control based on the results of the archive scope template design and the archive scope survey template design, and summarize it to the business expert terminal to obtain the enterprise archive scope data with a complete business directory and output it;

[0042] The archiving interface identification and data archiving module are used to receive enterprise archiving scope data information with a complete business directory. The archive developer publishes the enterprise archiving scope data format and data constraint information to the business system developer through the archiving interface. The business system developer develops data conversion logic according to the above conditions and converts it into data received by the archive system. After receiving the archived data, the archive system performs detection, and reorganizes it after passing the detection to complete the archiving of the enterprise archiving scope data.

[0043] In combination with all the above-mentioned technical solutions, the beneficial effects of the present invention are as follows: in order to address the problems of wide archiving scope, diversified archiving data, weak archiving management, etc., which lead to low archiving efficiency and difficulty in retrieving and utilizing archived data, the present invention proposes the concept of archiving business lines, and uses archiving business lines to collect archiving scopes and data, thereby realizing the integration of management, use, and display of archiving scopes, and greatly ensuring the improvement of archiving efficiency. The present invention classifies the archiving scope based on the archiving business line, forming a clear and systematic business line directory, so that the archiving scope can be integrated in management, use, and display in the directory. Specifically, through this tool, enterprises can clearly see the data files generated under each business line, and as the enterprise's business develops and changes, it can easily adjust the business line and archiving scope to adapt to new business needs.

[0044] The present invention enables integrated management, use and display of archiving scope in the directory, decoupling knowledge with low cost and universality, enabling business experts, archive experts and software technicians to effectively communicate and cooperate without in-depth study of their respective professional knowledge, flexibly collecting the archiving scope of the business system, significantly improving archiving efficiency, and helping enterprises to better manage archived data. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings herein are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description, serve to explain the principles of the present disclosure;

[0046] Figure 1 It is a flowchart of the archiving method for the archival business system provided by the embodiments of the present invention;

[0047] Figure 2 It is a flowchart for extracting the data of the old archiving scope template provided by the embodiments of the present invention;

[0048] Figure 3 It is an output flowchart of the enterprise archiving scope with a complete business directory provided by the embodiments of the present invention;

[0049] Figure 4 It is a schematic diagram of the archiving system for the archival business system provided by the embodiments of the present invention;

[0050] In the figure: 1. Template design module; 2. Enterprise archiving scope data acquisition module; 3. Archiving interface identification and data archiving module. Specific implementation manners

[0051] To make the above objects, features, and advantages of the present invention more obvious and understandable, the following will describe the specific implementation manners of the present invention in detail with reference to the accompanying drawings. Many specific details are set forth in the following description to fully understand the present invention. However, the present invention can be implemented in many other ways different from those described herein, and those skilled in the art can make similar improvements without departing from the connotation of the present invention. Therefore, the present invention is not limited by the specific implementations disclosed below.

[0052] The innovation of the present invention lies in: aiming at the problems of wide archiving scope, diverse archiving data, and weak archiving management, which lead to low archiving efficiency and difficult retrieval and utilization of archiving data, the present invention proposes the concept of the archiving business line, uses the archiving business line to collect the archiving scope and data, constructs a tool for improving the archiving efficiency for the archival industry system, realizes the integration of management, use, and display of the archiving scope, and greatly ensures the improvement of archiving efficiency.

[0053] Example 1, as Figure 1 shown, the archiving method for the archival business system provided by the embodiments of the present invention includes the design of the archiving scope research tool, the collection of the archiving scope, the docking of the archiving interface, and data archiving; the specific steps are as follows:

[0054] S1, conduct the design of the archiving scope template and the design of the archiving scope research template; the design of the archiving scope template is used to determine the files to be archived and saved, and record the retention period, carrier type, and file type data of the files; the design of the archiving scope research template is used to classify the files stored in the archives according to different standards and requirements to form a business line template, and record the relationship between the business line and the archiving scope and the interaction information of permissions;

[0055] S2, based on the results of the archive scope template design and the archive scope survey template design, the archive scope collection work is assigned to each user through the shared link method and permission control, and summarized to the business expert terminal to obtain the enterprise archive scope data with a complete business directory and output it;

[0056] S3, receiving the enterprise archive scope data information with a complete business directory, the archive developer publishes the enterprise archive scope data format and data constraint information to the business system developer through the archive interface, and the business system developer develops data conversion logic according to the above conditions and converts it into data received by the archive system; after receiving the archive data, the archive system performs detection, and reorganizes it after passing the detection to complete the archiving of the enterprise archive scope data.

[0057] Exemplarily, step S1 specifically includes: designing an archiving scope survey tool, performing step S101, designing an archiving scope template; step S102, designing an archiving scope survey template; wherein, the archiving scope template is designed to clarify which files or materials in the enterprise need to be archived, and record the retention period, carrier type, and file type data of these files; the archiving scope survey template is designed for business experts to use national standards, industry standards, enterprise standards, enterprise system requirements, enterprise archiving requirements, and industry experience to classify the files that need to be archived by the enterprise, form a business line template, and record the relationship between the business line and the archiving scope, permissions and other interactive information.

[0058] In step S101, designing an archiving scope template includes: the template style may vary according to the standards and requirements of the enterprise, and the archiving scope research tool is compatible with template designs for various business scenarios. Examples of archiving scope templates are shown in Table 1.

[0059] Table 1 Archive scope template:

[0060]

[0061] The archiving scope template is mainly divided into two parts: one is the archiving person in charge information, and the other is the archiving scope metadata, which is used to describe the key information of the archived files and plays a vital role in the subsequent identification and retrieval of archival data.

[0062] The information of the archiving person in charge includes: name, job title, department and contact information; the metadata of the archiving scope includes the information displayed in each cell: serial number, business line, archiving scope name, reference file, data source, carrier type, file format, department, category, archiving time, storage period, confidentiality level and scope of knowledge;

[0063] The data structure of the filing scope template includes information about the person in charge of filing and specific attribute descriptions of the metadata of the filing scope.

[0064] Specifically, the data structure of the filing scope template is as follows:

[0065] {

[0066] "Responsible person information": {

[0067] "Name": "",

[0068] "Position name": "",

[0069] "Department": "",

[0070] "Contact information": "",

[0071] },

[0072] "Filing scope": [ {

[0073] "Serial number": "",

[0074] "Business line": "",

[0075] "Filing scope name": "",

[0076] "Reference document": "",

[0077] "Data source": "",

[0078] "Carrier type": "",

[0079] "File format": "",

[0080] "Department": "",

[0081] "Category": "",

[0082] "Filing time": "",

[0083] "Retention period": "",

[0084] "Confidential level": "",

[0085] "Scope of knowledge": ""

[0086] } ]

[0087] }

[0088] Among them, in the "Archiving Scope" list, the "Archiving Scope Name" refers to the documentary materials with preservation and archiving value, and the "Data Source" refers to the source of the archiving scope, which may be data from business systems (such as OA, ERP, asset management systems, etc.) or offline documents. The business line is the name of the business line to which the archiving scope belongs. The carrier type indicates the form in which the archived files are archived, such as electronic data, paper documents, audio-visual materials, etc. The file format is the format of the files in the archiving scope, such as.pdf,.doc,.png,.xlsx, etc. The department to which it belongs is the department from which the archiving scope originates. The archiving time refers to the time node when the collection, collation, and archiving of the archival files are finally completed. The category to which it belongs refers to the archival classification to which the archived files should be assigned. The retention period is the period for which the archived files are stored in the system (10 years, 30 years, permanent, etc.). It is recommended that the archives of the enterprise's core business be permanent, and other archives can be evaluated according to the size of their asset value, evidentiary value, and value of recording history. The confidentiality level is the confidentiality level to which the archived files belong (no confidentiality, secret, top secret, etc.). The scope of access indicates which people, roles, or departments are allowed to query the archived files, and the non-accessible scope cannot query the directory of the archives.

[0089] Using HTML and JS technologies, the above data structure is bound to the archiving scope template in the form of "pair matching", that is, a cell is selected in the interface, and then a data structure field node is double-clicked. When double-clicking, the path of the field is obtained and added to the cell as the HTML attribute of the cell.

[0090] It can be understood that the definition of the template here only includes the table style and data structure, without actual data. The essence of the HTML and JS technologies is to set attributes on the dom element, and the attribute value is the field path. The setting syntax is: dom.setAttribute('bind', 'field path');

[0091] The role of setting this attribute here is to prepare for the update of historical data in step (b02).

[0092] Another exemplary step S102 is to design an archiving scope research template, including:

[0093] The archiving scope research template includes: step (a), organizational structure design, and step (b), business line design, which are specifically described as follows:

[0094] Step (a) The organizational structure design includes:

[0095] The organizational structure includes departments and personnel, which are used to divide the permissions of business lines. Among them, the personnel are based on the login accounts to verify the permissions of the current user on the business line. The data type of the organizational structure is an array, and its data structure is as follows:

[0096] [{

[0097] "isDept": true,

[0098] "name": "",

[0099] "children": []

[0100] }]

[0101] Among them, isDept is used to identify whether the current node is a department or a person. true indicates a department, and false indicates a person. name is the name of the department or person; children is a list of child nodes, and the data structure of the child node list is the same as the above structure.

[0102] The verification process is as follows: After the user logs in, obtain the user's account from the login interface, loop through each business line. If no permissions are set in the business line data, it is displayed normally. If permissions are set in the business line data, loop through the permission data to determine whether the current user's account is equal to any of the accounts in the permissions. If so, it means the user has the right to view the business line. If none of the permission accounts are equal to the current user's account, it means the user has no right to view the business line, that is, the business line is hidden from the current user. Among them, the permission descriptions involved above can be found in the following business line design.

[0103] Step (b), the business line design includes:

[0104] The core of the design of the archiving scope research template lies in designing the business line. The business line is the general term for a series of business activities divided within an enterprise to achieve specific business goals, and it is a specific and single business process or business procedure. For the software industry, the business line usually refers to a series of software products or services developed by a company to meet the needs of different customer groups, such as project lines, product lines, service lines, etc.

[0105] Combining the business line with the archiving scope, its core idea is to be oriented by business needs, comprehensively and importantly determine the archiving scope, and flexibly carry out dynamic adjustment and optimization as the business develops, that is, perform operations such as adding, deleting, modifying, editing, and setting on the business line; therefore, this template provides a function for online designing the business line to assist business consultants in quickly sorting out and establishing business lines.

[0106] Exemplarily, in the design of this archiving scope research template, the data structure of the business line is as follows:

[0107] [{

[0108] "id": "Unique identifier of the business line",

[0109] "name": "Name of the business line",

[0110] "formUrl": {

[0111] url:"Archive scope template link",

[0112] groupId: "Archive scope template data ID"

[0113] },

[0114] "responsiblePerson": [],

[0115] "children": [],

[0116] "fileList": {

[0117] name:"File name",

[0118] fileId: "file ID"

[0119] }],

[0120] "remark": "Remark",

[0121] }]

[0122] Among them, id uses GUID as the unique identifier of the business line, which is automatically generated by the tool. ResponsiblePerson is a user permission list, and its data structure corresponds to the organizational structure. The process of setting permissions is the process of selecting people from the organizational structure, indicating which people are allowed to view and edit this business line; children is a list of child lines. formUrl is used to store the information of the archive scope template link. The url is the archive scope template link, which contains the archive scope template ID, the template historical version ID, and the name of the collection to which it belongs. It is used to request the interface to obtain the template content and display it in the interface. groupId is the archive scope template data ID. Its main function is to synchronize historical data to the new template. The synchronization process is shown in step (b02).

[0123] fileList is a list of attachments, allowing users to upload additional files on each business line.

[0124] The above data structure corresponds to the following functions:

[0125] Step (b01), business line planning.

[0126] The filing scope research template allows users to flexibly construct a tree-level business line, that is, to add, delete, move, and copy business lines, set operations, clearly classify the filing scope, and place each type of filing scope in a specific directory with a unique path, effectively reducing the chaos of the filing scope and improving the management efficiency of the filing scope and the retrieval efficiency of data after filing.

[0127] Adding a business line: Users can, according to actual needs, add a sub-business line or a parallel business line in the tree structure through the add button, and support users to input the name and remarks of the business line.

[0128] Deleting a business line: Users can select the business line to be deleted and remove it through the delete button. If the deleted business line contains sub-business lines, the sub-business lines will be deleted together.

[0129] Moving a business line: Move the business line to a new position in the tree structure through a drag-and-drop operation.

[0130] Copying a business line: Users can select the business line to be copied and create a copy of the business line through the copy button. The copied business line will retain all the data of the original business line but has an independent identifier, and users can further edit and modify the copied business line.

[0131] Setting operations: Set permissions for the business line and bind the filing scope template. For specific instructions, see step (b02).

[0132] Step (b02): Bind the business line to the filing scope template.

[0133] The filing scope template is derived from the design in step S101. Each business line allows binding of one filing scope template, which is used to collect the files that should be filed and received under this business. The ways of binding the template are divided into the following three types.

[0134] The first type: All business lines bind to one filing scope template;

[0135] The second type: Each business line binds to one filing scope template;

[0136] The third type: Based on the above first and second cases, synchronously update the most recent historical data while binding the template.

[0137] In the above three cases, the filing scope template generates a link and is bound to the business line. After the filing scope template is designed, it is saved in the database through an interface. When saving, each template will generate a template ID, a template historical version ID, and the name of the belonging set. The link consists of a protocol, an IP address, a port, and a route. The generation of the filing scope template link is to splice the template ID and the template historical version ID as parameters in the above link.

[0138] Exemplarily, the third case applies to the scenario where the research has started and actual data has been generated in the archiving scope template, but due to changes in business requirements, the style of the original archiving scope template has changed. After the template changes, the template version changes, and it is necessary to rebind the new template to the business line and refill the data existing in the old template into the new template.

[0139] However, the filling is restricted by the template data structure, that is, the new template can only fill the parts that are consistent with the data structure of the old template, and the inconsistent parts need to be completed manually.

[0140] The filling process is as follows:

[0141] Step1: Extract the old template data. Since the archiving scope data structure has been bound to the archiving scope template, the data is extracted from the template through the binding relationship. Substantially, the data in the cell is queried through the field path on the cell, and the data in the cell is filled into the corresponding position of the field. The process of extracting the old archiving scope template data is as follows:

[0142] Input: Old archiving scope template (HTML + data structure), Output: Old archiving scope template data;

[0143] Let obj, path = "", parentKey = "", where obj is the archiving scope data structure, and its value may be an object or an array. path is the path of the current field, and parentKey is the parent path of the current field.

[0144] Judge whether obj is an array or an object. If it is an array, jump to 3; if it is an object, jump to 4. If it is neither, end.

[0145] If obj is an array, loop through the array and let the index array_index = 0;

[0146] 3.1 Let the temporary variable obj' = obj[array_index], parentKey += "[" + array_index + "]", and judge whether obj' is an object or an array. If it is an object, jump to 4; if not, the index array_index += 1;

[0147] 3.2 Judge whether array_index is greater than the length of the array. If it is greater, end; otherwise, jump to 3.1;

[0148] If obj is an object, let obj' = obj;

[0149] 4.1 Obtain all the key lists keyList of obj' and loop through them;

[0150] 4.2 Let the key index keyList_index = 0;

[0151] 4.3 Let the key key_item = keyList[keyList_index];

[0152] 4.4 Determine whether path is an empty string. If it is an empty string, let the current field's path in the current object currentPath = key_item; otherwise, let currentPath = path + "." + key_item;

[0153] 4.5 Determine whether parentKey is an empty string. If it is empty, let the full path fullPath of the current field in the entire object = currentPath; otherwise, let fullPath = parentKey + "." + currentPath;

[0154] 4.6 Obtain the cell according to fullPath. If obtained, obtain the html of the cell and let the current field value obj'[key_item] = html. Let keyList_index += 1; if not, let keyList_index += 1;

[0155] 4.7 Determine whether keyList_index is greater than the length of keyList. If it is greater, end the loop of this object; if not, path = fullPath, parentKey = fullPath, and then jump to 4.3;

[0156] 5. Until the recursion loops through each layer of objects or arrays, end and output the old template data.

[0157] It can be understood that steps 2 to 4 are to obtain the field path of the field in the data structure, find the cell according to the field path, and assign the cell content to the field (Step1) or fill the field value into the cell (Step2).

[0158] The above process is for synchronizing historical data in the new template. When the research has started and actual data has been generated in the archived scope template; at this time, some columns or content of the template have changed. It is obviously unrealistic to let the user re-enter the unchanged part, so the existing data in the old template needs to be filled into the new template again.

[0159] Step 2: Fill the data into the new template. Similarly, the essence of filling is to query cells based on the extracted data and the field paths of each field in the data, and fill the field data into the cells. The filling process is basically the same as the extraction process in Step 1, and the difference lies in the gray nodes in the flowchart of Step 1. When filling, this step is changed to assign the current field value obj'[key_item] to the cell, and set the html of the cell to obj'[key_item].

[0160] Step (b03) Business line user permission setting

[0161] The data source of the business line permissions is the organizational structure in step (a). The permissions of the business line are specific to individuals. Each business line can set data permissions and access controls, indicating that only users with permissions can view and edit the current business line and the on-line archive scope template, ensuring the security and consistency of the archive scope.

[0162] Step S2 specifically includes: Archive scope collection. Based on Step S1, the business expert shares the business line to other users in the form of a shared link. When other users log in to the tool, the tool verifies the permissions of the business line according to the logged-in account. The current user can only view, edit the business line and archive scope template related to himself, enabling users to focus more on their own work. The archive scope collection work is assigned to each responsible person (user) through the shared link method and permission control, and finally summarized to the business expert terminal, and finally an enterprise archive scope with a complete business directory is obtained. The so-called shared link refers to generating a shared link from the business line template, and the generation method is the same as that in step (b02); where groupId is the data ID of the archive scope template, and the explanation can be found in step S102.

[0163] Exemplarily, assigning the archive scope collection work to each responsible person through the shared link method and permission control includes: setting permissions for each business line during design. After the responsible person logs in, use his login account to match the business line permissions. If the match is successful or the business line has no permissions set, the business line is displayed; if the match fails, the line is hidden from the user. There may be many business lines, so after the responsible person logs in, he only sees the information related to him, and the information unrelated to him is hidden.

[0164] The output flowchart of the enterprise archive scope with a complete business directory is shown in Figure 3.

[0165] Exemplarily, step S3 specifically includes: archiving interface docking and data archiving. In this module, the business system developer (business system developer) and the archive developer (archive developer) conduct archiving interface docking. The two communicate to clarify the specific requirements of the archiving interface. The archive developer provides interface specifications, defines the structure and logic of the interface, input parameters and format, interface return, data conversion rules and other instructions. The business system developer performs data conversion and interface docking, joint debugging and other development work based on the provided information, and sends the archiving scope and its archived data to the archive system through the interface. The archived data includes the business line directory, the structured data of the business system, unstructured files, and file metadata. After receiving the archived data, the archive system performs four-property detection on it to ensure the authenticity, integrity, availability, and security of the archive. After the detection is passed, the archive expert can complete the archiving by reorganization.

[0166] Exemplarily, the archiving interface connection between the business system developer and the archive developer includes: the archive developer publishes the archiving interface to the business system developer, informs the business system developer of the data format, data constraints and other information that the archive system can receive, and the business system developer develops data conversion logic according to the above conditions to convert the business system data into data that can be received by the archive system. The process includes debugging and testing until the data is successfully sent to the archive system.

[0167] Business system developers perform data conversion, interface docking, joint debugging and other development work based on the information provided. Data conversion includes: business system developers develop conversion logic based on the archive data format and constraints provided by the archive system developers, and convert business system data into a data format that can be received by the archive system.

[0168] In summary, in response to the problems of low archiving efficiency and difficulty in retrieving and utilizing archived data due to the wide archiving scope, diversified archived data, and weak archiving management, this article proposes a tool to improve the archiving efficiency of the archives industry system, and puts forward the concept of archiving business line. The archiving business line is used to collect the archiving scope and data, and the management, use, and display of the archiving scope are integrated, which greatly ensures the improvement of archiving efficiency.

[0169] Embodiment 2, as Figure 4 As shown, an embodiment of the present invention provides an archiving system for an archive business system, including:

[0170] Template design module 1 is used to design the archiving scope template and the archiving scope investigation template; the archiving scope template design is used to determine the files to be archived and recorded the retention period, carrier type, and file type data of the files; the archiving scope investigation template design is used to classify the archived files according to different standards and requirements to form a business line template, and record the relationship between the business line and the archiving scope, and the interaction information of the authority;

[0171] The enterprise archive scope data acquisition module 2 is used to distribute the archive scope collection work to each user through a shared link method and permission control based on the results of the archive scope template design and the archive scope survey template design, and summarize it to the business expert terminal to obtain the enterprise archive scope data with a complete business directory and output it;

[0172] The archiving interface identification and data archiving module 3 is used to receive enterprise archiving range data information with a complete business directory. The archive developer publishes the enterprise archiving range data format and data constraint information to the business system developer through the archiving interface. The business system developer develops data conversion logic according to the above conditions and converts it into data received by the archive system. After receiving the archived data, the archive system performs a test, and reorganizes it after passing the test to complete the archiving of the enterprise archive range data.

[0173] As shown in Table 2, the traditional survey method and the method-level system proposed in the present invention are compared as follows: A certain enterprise sorted out more than 5,000 archived items, including the description (carrier, confidentiality level, etc.), display format, data structure and other information of the archived items.

[0174] Table 2 Comparison between the traditional survey method and the method-level system proposed in this invention:

[0175]

[0176] The above description is only a preferred specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any modifications, equivalent substitutions and improvements made by any technician familiar with the technical field within the technical scope disclosed by the present invention and within the spirit and principles of the present invention should be covered within the protection scope of the present invention.

Claims

1. A filing method for an archive business system, characterized in that: The method includes: S1, design the archiving scope template and the archiving scope investigation template; the archiving scope template is used to determine the files to be archived and record the retention period, carrier type, and file type data of the files; the archiving scope investigation template is used to classify the archived files according to different standards and requirements, form a business line template, and record the relationship between the business line and the archiving scope, and the interaction information of the authority; S2, based on the results of the archive scope template design and the archive scope survey template design, the archive scope collection work is assigned to each user through the shared link method and permission control, and summarized to the business expert terminal to obtain the enterprise archive scope data with a complete business directory and output it; S3, receiving enterprise archive scope data information with a complete business directory, the archive developer publishes the enterprise archive scope data format and data constraint information to the business system developer through the archive interface, and the business system developer develops data conversion logic based on the above information and converts it into data received by the archive system; after receiving the archive data, the archive system performs a test, and reorganizes it after passing the test, completing the archiving of the enterprise archive scope data; In step S1, a scoping survey template is designed, including: Step (a), organizational structure design: The organizational structure includes departments and personnel, which are used to divide the permissions of business lines. The personnel are based on the login account to verify the permissions of the current user in the business line. The data type of the organizational structure is an array. Step (b), business line design: business line planning, business line and archive scope template binding, business line user authority setting; In step (a), the data type of the organization structure is an array, including: isDept is used to identify whether the current node is a department or a person. true is a department, false is a person. name is the name of the department or person. children is a list of child nodes. Verify the current user's authority on the business line, including: after the user logs in, obtain the user's account from the login interface, loop through each business line, and if no authority is set in the business line data, display it normally; if authority is set in the business line data, loop through the authority data to determine whether the current user's account is equal to any account in the authority. If so, the user has the right to view the business line. If no authority account is equal to the current user's account, the user has no right to view the business line. In step (b), business line planning includes: adding, deleting, moving, copying, and setting operations on business lines; Business line user permission settings, including: the current business line and the online archiving range templates can only be viewed and edited by users with set permissions; In step (b), the business line is bound to the archive scope template, including: Each business line is bound to a filing scope template, which is used to collect the files that should be filed and collected under the business. The ways to bind the template include: The first type is to bind all business lines to one archive scope template; The second type is to bind an archive scope template to each business line; The third method is based on the above two situations, and the most recent historical data is updated synchronously while binding the template; Through the above three situations, the archive scope template is linked and bound to the business line; when the archive scope template changes and the template version changes, the new template is re-bound to the business line, and the existing data consistent with the old template is re-filled into the new template; Furthermore, the existing data consistent with the old template is refilled into the new template, including: Step 1: Extract the old template data, query the cell through the field path on the cell, and fill the data in the cell into the corresponding position of the field; Step 2: Fill the data into the new template, query the cell according to the extracted data and the field path of each field in the data, and fill the field data into the cell; when filling, assign the current field value obj'[key_item] to the cell, and let the cell's html=obj'[key_item].

2. The archiving method for an archive business system according to claim 1, characterized in that: In step S1, the archive range template is designed using HTML and JS technology to bind the data structure to the archive range template. A cell is selected in the interface, and the path of the field is obtained through the data structure field node and added to the cell as a cell HTML attribute; The archiving scope template includes the archiving person in charge information and the metadata of the archiving scope. The archiving person in charge information includes: name, job title, department and contact information; The metadata of the archiving scope is the information displayed in each cell, including: serial number, business line, archiving scope name, reference file, data source, carrier type, file format, department, category, archiving time, retention period, confidentiality level and knowledge scope information; the data structure of the archiving scope template includes the archiving person in charge information and the specific attribute description of the metadata of the archiving scope.

3. The archiving method for an archive business system according to claim 1, characterized in that: In step S2, the archive scope collection work is assigned to each user through shared links and permission control, including: setting permissions for each business line, matching the business line permissions with the login account after the user logs in, and displaying the business line if a match is found or the business line has no permissions set, and hiding the line from the user if a match is not found.

4. The archiving method for an archive business system according to claim 1, characterized in that: In step S3, the archive developer provides interface specifications, defines the structure and logic of the interface, input parameters and formats, interface returns, and data conversion rules. The business system developer performs data conversion, interface docking, and joint development work based on the information provided, and sends the archive scope and its archive data to the archive system through the interface; the archive data includes the business line directory, structured data of the business system, unstructured files, and file metadata; after receiving the archive data, the archive system performs authenticity, integrity, availability, and security tests on the archives. After the test is passed, the archive experts will compile and complete the data archiving.

5. An archiving system for an archive business system, characterized in that: The system implements the archiving method for the archive business system as claimed in any one of claims 1 to 4, and the system comprises: The template design module (1) is used to design an archiving scope template and an archiving scope survey template; the archiving scope template design is used to determine the files to be archived and record the retention period, carrier type, and file type data of the files; the archiving scope survey template design is used to classify the archived files according to different standards and requirements to form a business line template, and record the relationship between the business line and the archiving scope, and the interaction information of the authority; The enterprise archive scope data acquisition module (2) is used to distribute the archive scope collection work to each user through a shared link method and permission control based on the results of the archive scope template design and the archive scope survey template design, and to aggregate the archive scope data to the business expert terminal, thereby obtaining the enterprise archive scope data with a complete business directory and outputting it; The archiving interface identification and data archiving module (3) is used to receive enterprise archiving range data information with a complete business directory. The archive developer publishes the enterprise archiving range data format and data constraint information to the business system developer through the archiving interface. The business system developer develops data conversion logic based on the above information and converts it into data received by the archive system. After receiving the archived data, the archive system performs a test, and after passing the test, it compiles it to complete the archiving of the enterprise archiving range data.

Images