Extensible electronic archive business element retrieval method and system, terminal and medium

Abstract

The invention relates to the field of data retrieval, and particularly discloses an extensible electronic archive business element retrieval method and system, a terminal and a medium, the method comprises the following steps: constructing a plurality of business retrieval components, and configuring attribute information of each business retrieval component; associating the file type with a corresponding business retrieval component; based on the selected archive type, obtaining attribute information of a business retrieval component associated with the selected archive type, and rendering a front-end page for the user to configure business retrieval elements according to the attribute information; obtaining service retrieval elements configured by a user, and based on the attribute information of the service retrieval component, retrieving a corresponding service document identifier from the service data through the back-end interface according to the service retrieval elements; and combining the business document identifier and the general file retrieval condition into a target retrieval condition, retrieving the corresponding file content according to the target retrieval condition, and returning the retrieved corresponding file content to the front end. Retrieval requirements of different businesses are met, configuration is flexible, and the use range is wide.

Description

Technical Field

[0001] The present invention relates to the field of data retrieval, and in particular to an expandable electronic archive business element retrieval method, system, terminal and medium. Background Art

[0002] Currently, searching public electronic archives only retrieves publicly available bibliographic information, with no ability to add specific search criteria for different archive types. Alternatively, secondary development can be used to hard-code certain business search criteria. However, both approaches have significant drawbacks. Because not all data on business documents is contained within the archive content, the former cannot effectively integrate business and archival data, creating information silos and preventing the effective retrieval and utilization of business data not included in the archive content. The latter suffers from insufficient flexibility, low efficiency, and a lack of scalability. Furthermore, it can only be customized for specific archive types and cannot be subsequently upgraded. Summary of the Invention

[0003] To solve the above problems, the present invention provides an expandable electronic archive business element retrieval method, system, terminal and medium, which retrieves business data based on business retrieval requirements based on components, and then combines it with archive retrieval to break down the barriers between business data and archive data, meet the retrieval needs of different businesses, and has flexible configuration, wide range of use, strong scalability and low cost.

[0004] In a first aspect, the technical solution of the present invention provides a scalable electronic archive business element retrieval method, comprising the following steps: Constructing several business search components and configuring the attribute information of each business search component to be stored in a database; wherein the business search component is used to provide a front-end page for users to configure business search elements and a back-end interface for performing search operations based on the business search elements; Associate the file type with the corresponding business search component; In response to the archive search, based on the selected archive type, the attribute information of the business search component associated with it is obtained, and the front-end page for the user to configure the business search elements is rendered based on the attribute information; Obtain the business search elements configured by the user, and based on the attribute information of the business search component, retrieve the corresponding business document identifier from the business data through the back-end interface according to the business search elements; Combine the business document ID and the general file retrieval condition into the target retrieval condition, retrieve the corresponding file content according to the target retrieval condition, and return the retrieved corresponding file content to the front end.

[0005] In an optional implementation, the attribute information of the service search component includes a service search component name and a unique index identifier; Associate the file type with the corresponding business retrieval component, specifically including: Add the option "Business Element Retrieval" to the file type dictionary; In response to the selection of the "Business Element Retrieval" option, detect the name of the business retrieval component added by the user; Associate the current file type with the unique index identifier of the corresponding business retrieval component according to the name of the business retrieval component added by the user; One file type is associated with at least one business retrieval component; Build an association mapping relationship and store it.

[0006] In an optional implementation, in response to file retrieval, based on the selected file type, obtain the attribute information of the associated business retrieval component, and render a front-end page for the user to configure business retrieval elements, specifically including: In response to file retrieval, detect whether the selected file type is associated with a business retrieval component. If so, filter out at least one business retrieval component associated with it based on the selected file type; According to the filtering result, obtain the attribute information of each business retrieval component based on the unique index identifier of the business retrieval component; Dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface; In response to the selection of a business retrieval component, render a front-end page for the user to configure business retrieval elements.

[0007] In an optional implementation, the attribute information of the business retrieval component also includes whether it is enabled information; Dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface, specifically including: Extract the whether it is enabled information in the attribute information of each business retrieval component; Filter out the business retrieval components in the enabled state; Dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface for the business retrieval components in the enabled state.

[0008] In an optional implementation, the attribute information of the business retrieval component also includes the front-end business retrieval condition page URL; In response to the selection of a business retrieval component, render a front-end page for the user to configure business retrieval elements, specifically including: In response to the selection of a business retrieval component, display the pre-set front-end page for the user to configure business retrieval elements according to the front-end business retrieval condition page URL of the business retrieval component.

[0009] In an alternative embodiment, obtaining the service retrieval elements configured by the user specifically includes: In response to the user's configuration completion, extracting the service retrieval elements configured by the user; Detecting whether the service retrieval elements configured by the user meet the requirements; If not, feedback a configuration error prompt; If so, adding all the service retrieval elements configured by the user to an array structure.

[0010] In an alternative embodiment, the attribute information of the service retrieval component further includes service unit information and RPC retrieval interface information; Based on the attribute information of the service retrieval component, retrieving the corresponding service document identifier from the service data through the backend interface according to the service retrieval elements, specifically including: Transmitting all the service retrieval elements configured by the user and the unique index identifier of the corresponding service retrieval component to the backend retrieval program; The backend retrieval program matches the attribute information of the corresponding service retrieval component in the database according to the unique index identifier of the corresponding service retrieval component, and extracts the service unit information and RPC retrieval interface information therefrom; According to the service unit information and RPC retrieval interface information, retrieving the corresponding service document identifier from the service data based on all the service retrieval elements configured by the user.

[0011] In a second aspect, the technical solution of the present invention provides an extensible electronic file service element retrieval system, including: A service retrieval component configuration module, configured to construct a plurality of service retrieval components, and configure the attribute information of each service retrieval component to be stored in a database; wherein the service retrieval component is used to provide a front-end page for the user to configure service retrieval elements and a backend interface for performing retrieval operations based on the service retrieval elements; An association relationship creation module, configured to associate the file type with the corresponding service retrieval component; A service retrieval element configuration module, configured to, in response to a file retrieval, based on the selected file type, obtain the attribute information of the associated service retrieval component, and render a front-end page for the user to configure service retrieval elements according to the attribute information; A service document identifier acquisition module, configured to obtain the service retrieval elements configured by the user, and based on the attribute information of the service retrieval component, retrieve the corresponding service document identifier from the service data through the backend interface according to the service retrieval elements; A file content retrieval module, configured to combine the service document identifier and the general file retrieval condition into a target retrieval condition, retrieve the corresponding file content according to the target retrieval condition, and return the retrieved corresponding file content to the front end.

[0012] In a third aspect, the technical solution of the present invention provides a terminal, including: A memory for storing an extensible electronic file business element retrieval program; A processor for implementing the steps of the extensible electronic file business element retrieval method as described in any one of the above when executing the extensible electronic file business element retrieval program.

[0013] In a fourth aspect, the technical solution of the present invention provides a computer-readable storage medium, on which an extensible electronic file business element retrieval program is stored. When the extensible electronic file business element retrieval program is executed by a processor, the steps of the extensible electronic file business element retrieval method as described in any one of the above are implemented.

[0014] As can be seen from the above technical solutions, the present application has the following advantages: The service retrieval component provides a front-end page for users to configure service retrieval elements and a back-end interface for performing retrieval operations based on the service retrieval elements. Different file types are associated with different service retrieval components. When performing a retrieval, first, based on the file type, the user is provided to configure the corresponding service retrieval elements, and based on the service retrieval elements, the service document identifier is retrieved from the service data. Then, according to the service document identifier and the general file retrieval conditions, the corresponding file content is retrieved and the retrieved corresponding file content is returned to the front end. The present invention retrieves service data based on service retrieval requirements through components, and then combines with file retrieval to break through the barrier between service data and file data, meet the retrieval needs of different services, and has flexible configuration, wide application range, strong scalability and low cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solution of the present application, the drawings required to be used in the description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0016] Figure 1 It is a schematic flowchart of an extensible electronic file business element retrieval method provided by an embodiment of the present invention.

[0017] Figure 2 It is a schematic diagram of the architecture of the extensible electronic file business element retrieval method.

[0018] Figure 3 It is a schematic block diagram of the structure of an extensible electronic file business element retrieval system provided by an embodiment of the present invention.

[0019] Figure 4 It is a schematic diagram of the structure of a terminal provided by an embodiment of the present invention. Detailed implementation manners

[0020] To make the application purpose, features, and advantages of the present application more obvious and understandable, the following will use specific embodiments and accompanying drawings to clearly and completely describe the technical solutions protected by the present application. Obviously, the embodiments described below are only a part of the embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the technical field to which this invention belongs. The terms used in the specification of this invention herein are only for the purpose of describing specific embodiments, and are not intended to limit the present invention.

[0022] The following explains the key terms that appear in the present invention.

[0023] RPC: Remote Procedure Call, abbreviated as RPC, remote procedure call, is a method of requesting services from a remote computer over a network without the need to understand the details of the underlying network technology.

[0024] Figure 1 It is a schematic flow chart of an extensible electronic file business element retrieval method provided by an embodiment of the present invention. Among them, Figure 1 The execution subject can be an extensible electronic file business element retrieval system. The extensible electronic file business element retrieval method provided by the embodiment of the present invention is executed by a computer device. Correspondingly, the extensible electronic file business element retrieval system runs in the computer device. According to different requirements, the order of the steps in this flow chart can be changed, and some can be omitted.

[0025] As Figure 1 shown, the method includes the following steps.

[0026] S1. Construct a number of business retrieval components, and configure the attribute information of each business retrieval component and store it in the database; where the business retrieval component is used to provide a front-end page for the user to configure business retrieval elements and a back-end interface for performing retrieval operations based on the business retrieval elements.

[0027] In this step, independent retrieval modules (i.e., business retrieval components) are developed for different business scenarios (such as contracts, finance, and human resources). Each component includes a front-end page and a back-end interface. The front-end page provides retrieval forms strongly related to the business, such as "contract number", "project stage", etc. The back-end interface is used to process the retrieval conditions input by the user and call the business system interface to obtain the matching business data ID.

[0028] Meanwhile, store the metadata of the component into a prefabricated table in the database to achieve configuration management. The metadata includes the front-end page URL, back-end interface, etc.

[0029] In this step, the retrieval function is managed in a configuration way. Adding or modifying business retrieval conditions does not require modifying the core code, which improves flexibility and supports quickly adapting to new business types. In addition, the business logic is separated from the archive system, reducing the risk of dependencies between modules.

[0030] S2, associate the archive type with the corresponding business retrieval component.

[0031] In the archive classification management, associate each archive type with the required business retrieval components. Multiple business retrieval components can be associated. For example, "contract archive" is associated with "contract number retrieval" and "signing unit retrieval" components, and "financial archive" is associated with "voucher number retrieval" and "accounting period retrieval" components.

[0032] This step realizes customizing exclusive retrieval conditions for different archive types, which can meet the diverse business needs. Moreover, the association is achieved through configuration rather than hard coding, supporting adjusting the business logic according to requirements.

[0033] S3, in response to the archive retrieval, based on the selected archive type, obtain the attribute information of the associated business retrieval component, and render the front-end page for the user to configure business retrieval elements according to the attribute information.

[0034] After the user selects a certain archive type, the system obtains its attribute information, such as FILTERURL, from the prefabricated table according to the associated component configuration. Load the corresponding front-end page through FILTERURL, and dynamically generate a business retrieval element selection page, such as showing input boxes for "contract number" and "project phase". Realize loading and adapting the retrieval element configuration page for the current archive type as needed.

[0035] S4, obtain the business retrieval elements configured by the user, and based on the attribute information of the business retrieval component, retrieve the corresponding business document identifiers from the business data according to the business retrieval elements through the back-end interface.

[0036] The user enters business retrieval conditions on the front-end page, such as "project phase = in execution", and then, according to the attribute information of the business retrieval component, such as the service unit identifier and the RPC retrieval interface ID, call the RPC interface of the corresponding business system. The business system returns the matching business document IDs, such as the contract ID list ["C-001", "C-005"]). This step directly calls the business system interface to ensure that the retrieval conditions are consistent with the business data logic.

[0037] S5. Merge the business document identifier and the general file retrieval conditions into the target retrieval conditions, retrieve the corresponding file content according to the target retrieval conditions, and return the retrieved corresponding file content to the front end.

[0038] Merge the business document ID with the general retrieval conditions, such as merging ["C-001", "C-005"] and "Creation Time = 2023" to generate a combined query condition. Perform a combined retrieval in the file system (such as WHERE Contract ID IN ("C-001","C-005") AND Creation Time > '2023-01-01'). Return the file details that meet the conditions.

[0039] Since not all the data on the business document is in the file, the method of this embodiment first uses the comprehensive data distribution on the business document to retrieve the corresponding business document identifier through a component, and then retrieves the corresponding file content through the business document identifier and the general retrieval conditions. It should be noted that the business document identifier is included in the file.

[0040] The method of this embodiment directly uses the complete data on the business document for retrieval through a business retrieval component, rather than relying only on the common descriptive information in the file, which solves the problem of "retrieval omission caused by incomplete archiving of business data", can break information silos, and realize the integration of business and file data. Specifically, the business data is associated with the file content through the business document identifier, so that the unarchived business fields can still be retrieved through the business system, improving data utilization rate, and realizing targeted retrieval of different types of files. By configuring the business retrieval component, the retrieval for business types can be realized without secondary development or hard coding, and new business types can be adapted. One file type can be associated with multiple components to meet the refined retrieval requirements of complex business scenarios. In addition, the business retrieval conditions can be customized by the business group, and the field definitions are highly matched with the business logic. For example, "Project Phase = Acceptance" only contains valid enumerated values, reducing invalid results.

[0041] Further, as a refinement and extension of the specific implementation manner of the above embodiment, in order to fully illustrate the specific implementation process in this embodiment, another extensible method for retrieving business elements of electronic files is provided. This method aims to solve the problem that the comprehensive utilization query function of traditional file retrieval methods is weak and cannot meet the business management requirements. By dynamically loading the business retrieval conditions in the form of external components, the purpose of retrieving business elements of files is realized. And different business retrieval components can be configured for various types of files to specifically realize the retrieval of business elements of different business files. Figure 2It is a schematic diagram of the architecture of an extensible retrieval method for electronic file business elements, including that the business group develops business retrieval to construct the front-end interface and back-end methods, and pre-sets data. The electronic file end provides a pre-set table for business retrieval construction, adds configuration items for file types, dynamically loads retrieval conditions in the filtering area, executes retrieval to call the back-end retrieval construction, and queries based on the retrieval conditions and business element retrieval conditions. The project end configures business retrieval components for each type of file, puts forward retrieval requirements, and obtains and views retrieval results.

[0042] The method includes the following steps.

[0043] SS1, construct several business retrieval components.

[0044] In some alternative embodiments, add a prefabricated table for business retrieval components in the database, which is used to record component-related information and serves as the data source for the business component attributes in file classification. Table 1 is the prefabricated table for business retrieval components.

[0045] Table 1: Prefabricated Table for Business Retrieval Components

[0046] In some alternative embodiments, the business retrieval component provides a front-end page for users to configure business retrieval elements. It should be noted that there are no requirements for the page content of the front-end page, which is subject to the actual business requirements. The page url is the FILTERURL in the pre-set table. The page is required to implement two global js methods for obtaining and setting retrieval conditions. The specific methods are as follows: / / Obtain the filtering conditions of the retrieval page function getBizFilters() { / ** * The return value is an array. * If the retrieval conditions on the retrieval page do not meet the requirements, return null. At this time, the business filtering condition pop-up window will not close and the filters will not take effect. [[ID=D29]]* If no filtering conditions are set on the retrieval page, return an empty array. * If filtering conditions are set on the retrieval page, return all the set filtering conditions in the array. The content of the array is not restricted and needs to be parsed by oneself in the setBizFilters and the back-end rpc retrieval methods. * return [{custom structure}, {},...]; * / } / / Restore the existing filtering conditions on the page (the method name can be arbitrary. Call parent.ermRecoverBizFilters() at an appropriate time to obtain the filter set and restore it to the page) func(){ var filters = parent.ermGetBizFilters(); / / Restore the page } In some alternative embodiments, the business retrieval component provides a backend interface for performing retrieval operations based on business retrieval elements. Specifically, the backend method needs to retrieve the IDs of all archived data in this business system according to the filtering conditions obtained by the frontend method getBizFilters() (the returned field is the business document ID) and return them. The su and serviceid of the method are the SU and QUERYSERVICEID in the preset table. The method input parameter is of the HashMap type, and the filtering condition list data named bizFilters can be obtained through the input parameter. Its content is provided by the frontend method getBizFilters(). The interface needs to retrieve the archived data of this module according to the content of bizFilters and return the data IDs that meet all the conditions; the return value type is Map, and the structure is: {"type":"itemIds / bizIds","dataList":["","",...]} , where the type type defaults to bizIds (business data ID set), and dataList is the result set of the retrieval. If the archive ID is stored in the business, itemIds (archive data ID set) can also be used as the returned result set. Specifically, at a certain time after the rendering of the retrieval component page selection is completed, use the method ermRecoverBizFilters() provided by the parent page (archive retrieval) to obtain the saved business retrieval conditions for display.

[0047] SS2. Associate the archive type with the corresponding business retrieval component.

[0048] In some alternative embodiments, in the archive type dictionary, add the option "Business Element Retrieval". If this option is selected, add the option of the business retrieval component, allowing multiple selections of the data in the "Business Retrieval Component Preset Table" in step SS1. The specific steps are as follows.

[0049] SS2.1. Add the option "Business Element Retrieval" in the archive type dictionary.

[0050] Specifically, in the file type management module of the system, find the dictionary table that defines the attributes of the file type, add a new field or option value, or add a checkbox through the interface configuration tool, with the label "Business Element Retrieval". On the file type editing page, add a checkbox or dropdown option to allow users to enable the "Business Element Retrieval" function for specific file types.

[0051] SS2.2, in response to the "Business Element Retrieval" option being selected, detect the name of the business retrieval component added by the user.

[0052] Specifically, when the user checks "Business Element Retrieval" on the file type configuration page, a text input box or dropdown list is dynamically displayed for the user to select or enter the name of an existing business retrieval component. The name entered by the user needs to match the NAME field in the prefabricated table (such as biz_filter_component). If an invalid name is entered, the front end prompts "No matching business retrieval component found".

[0053] SS2.3, based on the name of the business retrieval component added by the user, associate the current file type with the unique index identifier of the corresponding business retrieval component; one file type is associated with at least one business retrieval component.

[0054] Specifically, according to the component name entered by the user, obtain its unique index identifier, such as ID or CODE, from the prefabricated table, and insert a record in the association table to save the corresponding relationship between the file type ID and the component ID.

[0055] SS2.4, construct and store the association mapping relationship.

[0056] Specifically, create an association table including fields such as field name, type, and description. Each time the user completes the component association operation, insert a new record into the association table.

[0057] SS3, in response to file retrieval, based on the selected file type, obtain the attribute information of the associated business retrieval component, and render the front-end page for the user to configure business retrieval elements according to the attribute information.

[0058] In some alternative embodiments, in the file retrieval function, when the corresponding file classification is selected, obtain the business retrieval component configuration information on this classification. If the business element retrieval is also enabled and the business retrieval component is correctly preconfigured, then in the file retrieval area, dynamically render the corresponding number of business retrieval components. At this time, only the names of the corresponding business retrieval components are displayed. When clicking to open the component, display the preconfigured url page of the corresponding component. Specifically, it includes the following steps.

[0059] SS3.1, In response to file retrieval, detect whether the selected file type is associated with business retrieval construction. If so, filter out at least one business retrieval component associated with the selected file type.

[0060] It should be noted that any number of business retrieval components are allowed to be configured for the file type, or no business retrieval components can be configured. Specifically, when a user selects a certain file type in the file system and clicks the "Retrieve" button, the backend queries the association table based on the selected file type ID and obtains all associated business retrieval component IDs. If no components are associated, a prompt "The current file type is not configured with business retrieval function" will be given. Subsequently, the corresponding file content retrieved according to the general file retrieval conditions is returned to the front end.

[0061] SS3.2, According to the screening results, obtain the attribute information of each business retrieval component based on the unique index identifier of the business retrieval construction.

[0062] Specifically, use the component ID list to query the prefabricated table of business retrieval components to obtain the attribute information, and the backend encapsulates the query results in JSON format and returns them to the front end.

[0063] SS3.3, Dynamically render the corresponding number of business retrieval components on the human-computer interaction interface in the form of business retrieval component names.

[0064] In some alternative embodiments, extract the enabled information in the attribute information of each business retrieval component; filter out the business retrieval components in the enabled state; and dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface.

[0065] Specifically, the front end filters out the components with ENABLED = 1 according to the returned component attribute data, and uses a front-end framework (such as Vue, React) to dynamically render buttons or labels. Each button corresponds to the name of an enabled component. The user can click on the component name to trigger subsequent operations.

[0066] SS3.4, In response to a business retrieval component being selected, render a front-end page for the user to configure business retrieval elements.

[0067] Specifically, in response to a business retrieval component being selected, display the pre-set front-end page for the user to configure business retrieval elements according to the front-end business retrieval condition page URL of the business retrieval component.

[0068] Exemplarily, when the user selects the contract management category containing the contract retrieval component in the file classification navigation, the business retrieval component of this category will be loaded and rendered to the filtering area of the file. When the user clicks on this component, a business retrieval component window will pop up on the right side of the interface according to the configuration of the business retrieval component, load the specified page, and after the page rendering is completed, call parent.ermGetBizFilters() to obtain the stored retrieval conditions of the file retrieval, and render the stored retrieval conditions to the component page; after clicking "OK", the file retrieval page calls the ermGetBizFilters() method of the component page to obtain the retrieval conditions input by the current component, and passes this part of the conditions to the backend method on the business retrieval component when retrieving files to obtain the corresponding business document scope.

[0069] SS4. Obtain the business retrieval elements configured by the user, and based on the attribute information of the business retrieval component, retrieve the corresponding business document identifiers from the business data through the backend interface according to the business retrieval elements.

[0070] In some alternative embodiments, obtaining the business retrieval elements configured by the user specifically includes: in response to the user's configuration being completed, extracting the business retrieval elements configured by the user; detecting whether the business retrieval elements configured by the user meet the requirements; if not, feedback a configuration error prompt; if so, add all the business retrieval elements configured by the user to an array structure.

[0071] Specifically, the user fills in the retrieval conditions on the front-end page of the business retrieval component, clicks the "OK" button, binds the click event of the button through the front-end framework (such as Vue, React), and triggers the data extraction logic. Traverse the form elements on the page to obtain the values input by the user. Based on the predefined verification rules, traverse all the retrieval conditions and verify them item by item. For example, some fields must be filled in, the contract number needs to conform to a regular expression, the date field needs to be in a valid format, etc. Then convert the retrieval conditions input by the user into a standardized object or key-value pair, and convert the front-end data into the format required by the backend interface.

[0072] In some alternative embodiments, based on the attribute information of the business retrieval component, retrieving the corresponding business document identifiers from the business data through the backend interface according to the business retrieval elements specifically includes the following steps.

[0073] SS4.1, Pass all the business retrieval elements configured by the user and the unique index identifier of the corresponding business retrieval component to the backend retrieval program.

[0074] In SS4.2, the backend retrieval program matches the unique index identifier of the corresponding business retrieval component to the attribute information of the corresponding business retrieval component in the database, and extracts the service unit information and RPC retrieval interface information therefrom.

[0075] Specifically, after receiving the data, the backend queries the corresponding records from the prefabricated table of business retrieval components. The returned fields include SU (service unit identifier) and QUERYSERVICEID (RPC interface ID). SU identifies the microservice unit where the business service is located, and QUERYSERVICEID is the retrieval interface provided by the business system.

[0076] In SS4.3, based on the service unit information and RPC retrieval interface information, the corresponding business document identifier is retrieved from the business data according to all business retrieval elements configured by the user.

[0077] Specifically, according to SU and QUERYSERVICEID, the RPC interface of the business system is called. The request parameters contain the structured data of bizFilters. The business system analyzes the filtering logic according to bizFilters and returns a list of matching business document IDs.

[0078] In SS5, the business document identifier and the general file retrieval condition are combined into a target retrieval condition. According to the target retrieval condition, the corresponding file content is retrieved and the retrieved corresponding file content is returned to the front end.

[0079] Specifically, the ID list returned by the business system in the previous stage (SS4.3) and the general conditions set by the user at the front end are used. The business document identifier and the general conditions are combined into a logical "AND" relationship to generate the final retrieval condition. A combined query is executed in the database of the file system, and the original database results are converted into the JSON format required by the front end. After receiving the data, the front end displays the file content in the form of a table, card, or list.

[0080] In the above text, the embodiments of an extensible electronic file business element retrieval method are described in detail. Based on the extensible electronic file business element retrieval method described in the above embodiments, the embodiments of the present invention also provide an extensible electronic file business element retrieval system corresponding to this method.

[0081] Figure 3 It is a schematic block diagram of the structure of an extensible electronic file business element retrieval system provided by the embodiments of the present invention. In this embodiment, the extensible electronic file business element retrieval system 300 can be divided into multiple functional modules according to the functions it executes. The module referred to in the present invention refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, and are stored in the memory.

[0082] A service retrieval component configuration module 310 is used to construct a number of service retrieval components, and configure the attribute information of each service retrieval component and store it in a database; wherein the service retrieval component is used to provide a front-end page for users to configure service retrieval elements and a back-end interface for performing retrieval operations based on the service retrieval elements.

[0083] An association relationship creation module 320 is used to associate the file type with the corresponding service retrieval component.

[0084] A service retrieval element configuration module 330 is used to respond to file retrieval, based on the selected file type, obtain the attribute information of the associated service retrieval component, and render a front-end page for users to configure service retrieval elements according to the attribute information.

[0085] A service document identifier acquisition module 340 is used to acquire the service retrieval elements configured by the user, and based on the attribute information of the service retrieval component, retrieve the corresponding service document identifier from the service data through the back-end interface according to the service retrieval elements. [[ID=I2]]

[0086] A file content retrieval module 350 is used to combine the service document identifier and the general file retrieval condition into a target retrieval condition, retrieve the corresponding file content according to the target retrieval condition, and return the retrieved corresponding file content to the front end.

[0087] The extensible electronic file service element retrieval system of this embodiment is used to implement the foregoing extensible electronic file service element retrieval method. Therefore, the specific implementation manners in this system can be seen in the embodiment part of the extensible electronic file service element retrieval method in the foregoing text. Therefore, its specific implementation manners can refer to the descriptions of the corresponding various part embodiments, and will not be elaborated here.

[0088] In addition, since the extensible electronic file service element retrieval system of this embodiment is used to implement the foregoing extensible electronic file service element retrieval method, its functions correspond to those of the above method, and will not be elaborated here. [[ID=Z1]]

[0089] Figure 4 The structure diagram of a terminal 400 provided by an embodiment of the present invention includes: a processor 410, a memory 420, and a communication unit 430. The processor 410 is used to implement the flow steps of the foregoing extensible electronic file service element retrieval method embodiment when implementing the extensible electronic file service element retrieval program stored in the memory 420.

[0090] The terminal 400 includes a processor 410, a memory 420, and a communication unit 430. These components communicate via one or more buses. Those skilled in the art can understand that the structure of the server shown in the figure does not constitute a limitation on the present invention. It can be a bus structure, a star structure, and can also include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0091] Among them, the memory 420 can be used to store the execution instructions of the processor 410. The memory 420 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. When the execution instructions in the memory 420 are executed by the processor 410, the terminal 400 can execute some or all of the steps in the above method embodiments.

[0092] The processor 410 is the control center of the storage terminal, connecting various parts of the entire electronic terminal through various interfaces and lines. By running or executing the software programs and / or modules stored in the memory 420, and by calling the data stored in the memory, it executes various functions of the electronic terminal and / or processes data. The processor can be composed of an integrated circuit (IC). For example, it can be composed of a single packaged IC, or can be composed of multiple packaged ICs with the same or different functions connected together. For example, the processor 410 can include only a central processing unit (CPU). In the embodiment of the present invention, the CPU can be a single operation core or can include multiple operation cores.

[0093] The communication unit 430 is used to establish a communication channel so that the storage terminal can communicate with other terminals. It receives user data sent by other terminals or sends user data to other terminals.

[0094] The present invention also provides a computer storage medium. The storage medium here can be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), etc.

[0095] The present invention also provides a computer storage medium, which may be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), or the like.

[0096] The computer storage medium stores an extensible electronic file service element retrieval program. When the extensible electronic file service element retrieval program is executed by a processor, the flow steps of the above-described extensible electronic file service element retrieval method embodiment are implemented.

[0097] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution in the embodiments of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., which can store program codes, and includes several instructions to enable a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0098] In several embodiments provided by the present invention, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical, or other form.

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

[0100] In addition, in each embodiment of the present invention, the functional units can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0101] The foregoing description of the disclosed embodiments enables those skilled in the art to practice or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An extensible retrieval method for business elements of electronic files, characterized in that, It includes the following steps: Construct a number of business retrieval components and configure the attribute information of each business retrieval component to be stored in the database; Among them, the business retrieval component is used to provide a front-end page for users to configure business retrieval elements and a back-end interface for performing retrieval operations based on business retrieval elements; Associate the file type with the corresponding business retrieval component; In response to file retrieval, based on the selected file type, obtain the attribute information of the associated business retrieval component, and render a front-end page for users to configure business retrieval elements according to the attribute information; Obtain the business retrieval elements configured by the user, and based on the attribute information of the business retrieval component, retrieve the corresponding business document identifier from the business data through the back-end interface according to the business retrieval elements; Merge the business document identifier and the general file retrieval condition into a target retrieval condition, retrieve the corresponding file content according to the target retrieval condition, and return the retrieved corresponding file content to the front end.

2. The scalable electronic file service element retrieval method according to claim 1, wherein The attribute information of the business retrieval component includes the business retrieval component name and the unique index identifier; Associating the file type with the corresponding business retrieval component specifically includes: Add an option "Business Element Retrieval" to the file type dictionary; In response to the selection of the "Business Element Retrieval" option, detect the name of the business retrieval component added by the user; According to the name of the business retrieval component added by the user, associate the current file type with the unique index identifier of the corresponding business retrieval component; one file type is associated with at least one business retrieval component; Construct and store the association mapping relationship.

3. The scalable retrieval method for electronic file service elements according to claim 2, wherein In response to file retrieval, based on the selected file type, obtain the attribute information of the associated business retrieval component, and render a front-end page for users to configure business retrieval elements according to the attribute information, specifically including: In response to file retrieval, detect whether the selected file type is associated with a business retrieval component. If so, filter out at least one business retrieval component associated with it based on the selected file type; According to the filtering result, obtain the attribute information of each business retrieval component based on the unique index identifier of the business retrieval component; Dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface; In response to the selection of a business retrieval component, render a front-end page for users to configure business retrieval elements.

4. The scalable electronic file business element retrieval method according to claim 3, characterized in that, The attribute information of the business retrieval component also includes the enable information; Dynamically render the corresponding number of business retrieval components in the form of business retrieval component names on the human-computer interaction interface, specifically including: Extract the enable information in the attribute information of each business retrieval component; Filter out the business retrieval components in the enabled state; Dynamically render the business retrieval components in the enabled state in the form of business retrieval component names on the human-computer interaction interface.

5. The scalable electronic file service element retrieval method according to claim 3, wherein The attribute information of the business retrieval component also includes the URL of the front-end business retrieval condition page; In response to the selection of a business retrieval component, render a front-end page for users to configure business retrieval elements, specifically including: In response to the selection of a business retrieval component, display the pre-set front-end page for users to configure business retrieval elements according to the URL of the front-end business retrieval condition page of the business retrieval component.

6. The scalable electronic file service element retrieval method according to claim 4, characterized in that Obtain the business retrieval elements configured by the user, specifically including: Upon completion of user configuration, extract the business retrieval elements configured by the user; Detect whether the business retrieval elements configured by the user meet the requirements; If not, feedback a configuration error prompt; If so, add all the business retrieval elements configured by the user to the array structure.

7. The scalable electronic file service element retrieval method according to claim 6, wherein The attribute information of the business retrieval component also includes service unit information and RPC retrieval interface information; Based on the attribute information of the business retrieval component, retrieve the corresponding business document identifier from the business data through the backend interface according to the business retrieval elements, specifically including: Pass all the business retrieval elements configured by the user and the unique index identifier of the corresponding business retrieval component to the backend retrieval program; The backend retrieval program matches the attribute information of the corresponding business retrieval component in the database according to the unique index identifier of the corresponding business retrieval component, and extracts the service unit information and RPC retrieval interface information therefrom; According to the service unit information and RPC retrieval interface information, retrieve the corresponding business document identifier from the business data based on all the business retrieval elements configured by the user.

8. An extensible retrieval system for business elements of electronic files, characterized in that, Including: A business retrieval component configuration module, used to construct several business retrieval components and configure the attribute information of each business retrieval component to be stored in the database; Wherein the business retrieval component is used to provide a front-end page for the user to configure business retrieval elements and a backend interface for performing retrieval operations based on the business retrieval elements; An association relationship creation module, used to associate the file type with the corresponding business retrieval component; A business retrieval element configuration module, used to respond to file retrieval, based on the selected file type, obtain the attribute information of the associated business retrieval component, and render a front-end page for the user to configure business retrieval elements according to the attribute information; A business document identifier acquisition module, used to obtain the business retrieval elements configured by the user, and based on the attribute information of the business retrieval component, retrieve the corresponding business document identifier from the business data through the backend interface according to the business retrieval elements; A file content retrieval module, used to combine the business document identifier and the general file retrieval condition into a target retrieval condition, retrieve the corresponding file content according to the target retrieval condition, and return the retrieved corresponding file content to the front end.

9. A terminal, characterized in that, Including: A memory, used to store an extensible electronic file business element retrieval program; A processor, used to implement the steps of the extensible electronic file business element retrieval method as described in any one of claims 1 to 7 when executing the extensible electronic file business element retrieval program.

10. A computer-readable storage medium, characterized in that, The extensible electronic file business element retrieval program is stored on the readable storage medium, and when the extensible electronic file business element retrieval program is executed by the processor, the steps of the extensible electronic file business element retrieval method as described in any one of claims 1 to 7 are implemented.

Images