Form management method, form system, storage medium and computer program product

Abstract

The invention relates to a form management method, a form system, a storage medium and a computer program product. The form management method comprises the steps that form configuration is carried out based on a graph structure, so that components in a form are associated with the graph structure, form configuration data are generated, and the graph structure comprises entities, relations and attributes; converting the form filling data into an expression form of a graph structure through form configuration data; and associating the form filling data corresponding to the same entity among different forms. According to the method, the semantics of the collected data can be distinguished by establishing the mapping relation between the components and the human and terrestrial entities and the standard attributes of the components, and information association of the same entity between different applications is achieved.

Description

Technical Field

[0001] The present disclosure relates to the field of machine learning, and in particular to a form management method, a form system, a storage medium, and a computer program product. Background Art

[0002] The form system has a very wide range of application scenarios. With the development of information technology, more and more paper materials have been digitized in the form of forms. Electronic forms have improved the operating efficiency of social production and life activities by accelerating the rapid flow of information. At the same time, the data of various application forms have also been gathered in the cyberspace to form a rich data resource. Comprehensive management and analysis of these data can improve the efficiency of social life and optimize the life experience of residents. For example, in the government affairs scenario, residents fill in their names, ID numbers, home addresses, and event information in the form to submit applications to the government. Government staff can quickly complete the application after reviewing the form; at the same time, the accumulated resident information, address and other data can help the government understand the dynamic situation of the population in the city and help the government to do a good job in urban management. In the enterprise scenario, the rapid advancement of the event process can be achieved through the filling, viewing and approval of forms; at the same time, analysis of the accumulated event data can also help enterprises optimize processes and improve efficiency.

[0003] The related technologies for implementing form configuration, reporting and data management face the following three difficulties. First, it is necessary to implement componentization of form configuration, allowing users to build forms based on widgets to form form configurations; and to complete the parsing of form configurations on the reporting end to generate an interface for users to fill in. Secondly, it is necessary to implement standardization of storage fields. Different forms store the same content (such as a person's name, phone number, location, organization's social credit code, etc.) in the same way, so that unified data management can be achieved. Finally, the data collected through the form needs to be associated with the real entity, and the form system needs to be able to build an entity identifier from the entity data of the form, so that information association of the same entity in different application processes can be achieved. Summary of the invention

[0004] Through research, the inventors found that related technical form systems usually only focus on the question type design of the form at the interactive level and the data analysis and statistics work after the data collection is completed. The forms configured by different applications or users are independent of each other in terms of data semantics and storage. The comprehensive analysis and utilization of data between forms often requires heavy data understanding and processing work.

[0005] In view of at least one of the above technical problems, the present disclosure provides a form management method, a form system, a storage medium and a computer program product. By establishing a mapping relationship between components and people, place entities and their standard attributes, the semantics of these collected data can be distinguished to achieve information association of the same entity between different applications.

[0006] According to one aspect of the present disclosure, a form management method is provided, which is applied to a form system, wherein the form management method includes:

[0007] Configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships, and attributes;

[0008] Through form configuration data, the form filling data is converted into the expression form of graph structure;

[0009] Associate the form filling data corresponding to the same entity between different forms.

[0010] In some embodiments of the present disclosure, configuring the form based on the graph structure to associate components in the form with the graph structure includes:

[0011] In the form configuration interface, according to the user input, for each component or subcomponent in the form, select a first type component or a second type component for configuration, wherein the first type component includes at least one of a text box, a selection box, and a value, and the second type component is a component obtained by associating the first type component with an entity, an entity attribute, or a relationship attribute, and the component includes at least one subcomponent;

[0012] According to the user input, the first type component or the second type component is added to the form content.

[0013] In some embodiments of the present disclosure, configuring the form based on the graph structure to associate components in the form with the graph structure includes:

[0014] In the form configuration interface, all components available to users are displayed to users through the component area;

[0015] In the form configuration area, an interactive interface for configuring the form is provided for the user, wherein each entity is displayed as an information box with a title in the interactive interface for configuring the form;

[0016] In the form configuration area, the component selected by the user and its corresponding entity or attribute are displayed in the information box to complete the configuration of the form;

[0017] In the configuration information editing area, the configuration information of each component is modified according to the user's input, wherein the configuration information includes at least one of a verification mode, a default value and a hidden state.

[0018] In some embodiments of the present disclosure, generating form configuration data includes:

[0019] Generate standardized form configuration data according to the configured form content, wherein the form configuration data includes at least one data table field, and one component corresponds to one data table field;

[0020] Use component identifiers and attribute identifiers to construct the names of data table fields.

[0021] In some embodiments of the present disclosure, the form management method further includes:

[0022] Perform at least one of filling verification, data backfilling and data update based on the data filled in the form.

[0023] In some embodiments of the present disclosure, performing filling verification according to the form filling data includes:

[0024] When the user fills in data and submits the form, check whether the data filled in by the user conforms to the configuration information of the component.

[0025] In some embodiments of the present disclosure, the data backfilling according to the form filled data includes:

[0026] Through the entity identification algorithm, it is determined whether the current entity matches the existing entity in the database according to the information of the current entity in the form filling data;

[0027] In the case where the current entity matches an existing entity in the database, the information of the same entity in the database is associated with each other;

[0028] Backfill the form's data based on the information associated with the current entity in the database.

[0029] In some embodiments of the present disclosure, updating data according to form filled data includes:

[0030] After the user submits the form, parse the form data;

[0031] Update the parsed form submission data to the database for system query and analysis;

[0032] Update the entities, relationships and attributes corresponding to the parsed form submission data into the system database.

[0033] In some embodiments of the present disclosure, the form filling data is converted into an expression form of a graph structure by using form configuration data, including:

[0034] Receive the form content after form configuration is completed or form data is filled in;

[0035] Perform component parsing, graph parsing, and metadata parsing on the form content.

[0036] In some embodiments of the present disclosure, the component parsing of the form content includes at least one of the following steps, wherein:

[0037] Parse each component in the form content respectively, and identify at least one of the component category, configuration information, and display control logic;

[0038] Verify the legitimacy of component configuration information;

[0039] Verify whether the component reported data meets the requirements of component configuration information.

[0040] In some embodiments of the present disclosure, the graph parsing of the form content includes at least one of the following steps, wherein:

[0041] Identify the attribute information to which the component is linked in the form content;

[0042] Map the configuration information of the component to the corresponding attribute in the graph, and automatically connect the entity or relationship corresponding to the attribute;

[0043] Through the context of the form configuration data, the entities, relationships and attributes involved in the form configuration data are associated.

[0044] In some embodiments of the present disclosure, performing metadata parsing on the form content includes at least one of the following steps, wherein:

[0045] Bind each component to a component type, wherein the component types include text boxes, selection boxes, and values;

[0046] Determine the data storage type corresponding to the component by identifying the component type corresponding to the component;

[0047] At least one of the storage field name, default value and index of the data is determined through the configuration information of the component and the context of the form configuration data.

[0048] In some embodiments of the present disclosure, associating form filling data corresponding to the same entity between different forms includes:

[0049] For each form, a metadata record file is generated, wherein each metadata record file is used to record entities in the form and relationships between entities, as well as attribute fields belonging to the entities or relationships;

[0050] Different unique entity identifier generation algorithms are designed for different types of entities, and the parsed data of the same entity in different forms are mapped to the same real entity.

[0051] In some embodiments of the present disclosure, the form management method further includes:

[0052] Build data management tables of components and graph structures to configure entities, relationships, and attributes in the form system;

[0053] In the case where a specific attribute does not meet the application requirements, the specific attribute is taken offline to close the user's access to the component related to the specific attribute.

[0054] In some embodiments of the present disclosure, the form management method further includes: using multiple components of different types to express the same attribute.

[0055] In some embodiments of the present disclosure, the form management method further includes:

[0056] In some embodiments of the present disclosure, the form management method further includes: constructing a data layer, wherein the data layer is used to store underlying configuration information of the form system, wherein the underlying configuration information includes a component library, an entity library, a relationship library, an attribute library, and an attribute component mapping library.

[0057] According to another aspect of the present disclosure, a form system is provided, comprising:

[0058] A form configuration module is configured to configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships and attributes;

[0059] The parsing module is configured to convert the form filling data into an expression form of graph structure through form configuration data; and associate the form filling data corresponding to the same entity between different forms.

[0060] According to another aspect of the present disclosure, a form system is provided, comprising:

[0061] a memory configured to store instructions;

[0062] The processor is configured to execute the instructions so that the form system implements the form management method as described in any of the above embodiments.

[0063] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the form management method as described in any of the above embodiments is implemented.

[0064] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the form management method as described in any of the above embodiments is implemented.

[0065] The present disclosure establishes a mapping relationship between components and human and land entities and their standard attributes, thereby distinguishing the semantics of these collected data and realizing information association of the same entity between different applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0067] Figure 1 Schematic diagrams of some embodiments of the form system disclosed herein.

[0068] Figure 2 Schematic diagrams of other embodiments of the form system disclosed herein.

[0069] Figure 3 Schematic diagram of some embodiments of the form management method disclosed in the present invention.

[0070] Figure 4 Schematic diagram of the first type of components in some embodiments of the present disclosure.

[0071] Figure 5 A schematic diagram of configuring student names in some embodiments of the present disclosure.

[0072] Figure 6 A schematic diagram of a form configuration interface in some embodiments of the present disclosure.

[0073] Figure 7 This is a schematic diagram of interaction design based on spatial perception experience in some embodiments of the present disclosure.

[0074] Figure 8 This is a schematic diagram of adding components to the configuration area in some embodiments of the present disclosure.

[0075] Figure 9a A schematic diagram of entity type selection in some embodiments of the present disclosure.

[0076] Figure 9b This is a schematic diagram of configuring an information editing area in some embodiments of the present disclosure.

[0077] Fig.10 The figure is a schematic diagram of the entity, relationship and attribute library in some embodiments of the present disclosure.

[0078] Fig.11 A schematic diagram of optional components of detailed address attributes in some embodiments of the present disclosure.

[0079] Fig.12 This is a schematic diagram of the public student off-campus accommodation status form.

[0080] Fig.13 It is a schematic diagram of the association between two entities in some embodiments of the present disclosure.

[0081] Fig.14 Schematic diagrams of the structures of some further embodiments of the form system disclosed herein. DETAILED DESCRIPTION

[0082] The technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0083] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0084] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0085] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0086] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0087] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0088] The inventor also found through research that: the mainstream form system of the related art implements multiple question types for form configuration, but does not have data storage management functions, while another type of form system creates a physical table in the database synchronously when configuring the form, and adds corresponding fields to the physical table according to the data items in the form, but the management of form metadata is relatively loose, and the data collected by this type of form system is difficult to realize mutual conversion between different applications. The related art form system also has the following technical problems.

[0089] First, the information that needs to be collected is diverse, but the relevant technical form system lacks a highly condensed and generalized expression of information. On the one hand, the system cannot distinguish different information generated by the same component; on the other hand, even the same description and the same type of information generated by the same component may produce completely different semantics, and the relevant technical system cannot identify their differences, making it impossible to standardize the management of the collected information. For example, the relevant technical form system uses text components to collect information such as a person's name, occupation, and specialty, but due to the lack of standardized definitions of attribute fields such as name, occupation, and specialty, the relevant technical system cannot distinguish the semantics of the collected text data. Another example is that the ID numbers of two people are collected in a form. Even if the two ID number components have the same configuration, they describe the information of different people. The relevant technical system cannot accurately identify the correspondence between the two certificates and the two people.

[0090] Secondly, in questionnaires constructed by traditional form systems, since the relevant technical systems are not clear about the semantic information of each component, the content reported by the components has not been truly digitized, resulting in the inability to automatically associate the data filled in by users. Complex and arduous data governance is required before it can be used in other systems or scenarios. For example, in the form configuration, components such as a person's name and address are collected and filled in by the user. When other systems want to use this collected information to display these people on a map, since there is no mapping relationship between the components and the human and land entities and their standard attributes, the semantics of these collected data cannot be directly distinguished (for external systems, they are all text, not data that can be directly recognized by digital systems). Therefore, the semantic information of each field needs to be manually annotated before it can be used by external systems.

[0091] Finally, in the forms constructed by the relevant technical form system, even if some components have basic semantic information, they cannot be materialized, that is, the system has no ability to build and identify the relationship between data and real entities, resulting in the inability to query, analyze and apply the data filled in by users in the dimension of entities, which greatly reduces the application value of data in the field of people's livelihood. For example, users fill in their (mobile phone number, ID number, occupation), (mobile phone number, work unit), (ID number, education level) information in different forms, but because the relevant technical system does not have the ability to materialize, the user's information cannot be associated with the person, so the user needs to repeatedly fill in information such as mobile phone number and ID number in multiple forms, which is a poor experience and greatly reduces the user's willingness to use.

[0092] In view of at least one of the above technical problems, the present disclosure provides a form management method, a form system, a storage medium and a computer program product, which are described below through specific embodiments.

[0093] Figure 1 Schematic diagram of some embodiments of the form system disclosed in the present invention. Figure 1 As shown, the form system of the present disclosure may include a form configuration module 101 and a parsing module 102 .

[0094] The form configuration module 101 is configured to configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships and attributes.

[0095] In some embodiments of the present disclosure, a knowledge graph is a structured semantic knowledge base used to describe concepts and their relationships in the physical world in a symbolic form. Its basic components are "entity-relationship-entity" triples, as well as entities and their related attribute-value pairs. Entities are connected to each other through relationships to form a network of knowledge structures.

[0096] In some embodiments of the present disclosure, the content of the graph (including entities / relationships / attributes) is replaceable.

[0097] The parsing module 102 is configured to convert the form filling data into an expression form of a graph structure through form configuration data; and associate the form filling data corresponding to the same entity between different forms.

[0098] Figure 2 Schematic diagrams of other embodiments of the form system disclosed in the present invention. Figure 2 As shown, the disclosed form system may include an application layer 3, a parsing layer 2 and a data layer 1, wherein the parsing layer may be implemented as Figure 1 The parsing module 102 of an embodiment.

[0099] Data layer 1 is configured as a form system that needs to separate components, entities, relationships, attributes, and the mapping relationship data between attributes and components from the system logic into database tables to achieve flexible configuration and access of these basic elements in the system.

[0100] In some embodiments of the present disclosure, Figure 2 As shown, the data layer 1 stores the underlying configuration information of the form system, and the data layer 1 may include a component library 11 , an entity library 12 , a relationship library 13 , an attribute library 14 , and an attribute component mapping library 15 .

[0101] Parsing layer 2, the core functions of the parsing layer in the form system include three parts, namely component parsing module 21, graph parsing module 22 and metadata parsing module 23.

[0102] The component parsing module 21 is configured to parse the configuration description of the component in the application form configuration file (usually a markup language file such as JSON or HTML, XML, etc.) into the corresponding data structure of the system, and verify the validity of the configuration information, wherein the data structure refers to the abstract object in the program, such as various data classes in JAVA projects.

[0103] In some embodiments of the present disclosure, Figure 2 As shown, the component parsing module 21 can be configured to perform configuration loading and verification, and data loading and verification.

[0104] The graph parsing module 22 is configured to map the components in the form configuration to their corresponding entity attributes or relationship attributes, and to interconnect the relationships and entities to which these attributes belong, to form a graph structure with abstract business semantics. Since the present disclosure associates components with graphs, the information that the graph can express must be abstract, otherwise the semantics of the graph cannot be applied to rich business scenarios. For example, the present disclosure abstracts more than a dozen attributes of the "person" entity, and the "name" attribute of "person" can represent "Chinese name", "English name", "former name", "net name", etc. in different scenarios. This is why the semantics of the graph structure extracted from the form are abstract rather than specific.

[0105] In some embodiments of the present disclosure, Figure 2 As shown, the graph parsing module 22 can be configured to perform entity parsing, relationship parsing and attribute parsing.

[0106] The metadata parsing module 23 is configured to parse out key information such as the database table field type, name, description, etc. corresponding to the component based on the form component name, description and other information configured by the user and the graph information corresponding to the component. The system can create a data table based on the metadata to record the data uploaded by the user on the reporting end.

[0107] In some embodiments of the present disclosure, metadata, also known as intermediate data or relay data, is data about data, mainly information describing data properties, and is used to support functions such as indicating storage location, historical data, resource search, and file records.

[0108] In some embodiments of the present disclosure, Figure 2 As shown, the metadata parsing module 23 can be configured to parse out information such as the type, name, entity or relationship of the library table field.

[0109] Application layer 3, application layer 3 can include two parts: configuration end 31 and reporting end 32.

[0110] In some embodiments of the present disclosure, Figure 2 As shown, the configuration terminal 31 can be configured to allow the user to configure the entities, relationships and attributes of the graph, and can also configure the components in the form. The system can also recommend relationships and components to the user through algorithms.

[0111] In some embodiments of the present disclosure, Figure 2 As shown, the configuration terminal 31 can be configured to automatically fill in the content in the form for the user based on the information already filled in and other available information when the user fills in the form, and to verify the validity of the form content submitted by the user, and to assist the business system to record the data in the database, that is, to perform data backfilling, filling verification and data update.

[0112] The public form system includes a form configuration end and a reporting end. Among them, the configuration end provides users with a collection information configuration page, through dragging and dropping and other methods to create text boxes, multiple-choice questions, values, time, tables and other types of questions, and set the title, description, visibility, data source and other attributes of the question type, so as to complete the configuration and release of the collected content; after that, other users can see the content to be collected in the reporting end, complete the filling of information, and the form system will automatically verify the reported content. After the information is confirmed to be correct and submitted, the form configuration personnel can see all the reported information and complete the data collection. At the same time, the public form system can further display, analyze and count the collected data to provide users with more decision-making basis.

[0113] The disclosed form system is a form system based on a knowledge graph. The disclosed form system can implement the form management method described in any of the above embodiments.

[0114] In view of the componentization of form configuration and the standardization of form storage, the above-mentioned embodiments of the present disclosure propose a form system based on graph technology.

[0115] The form management method and form system disclosed in the present invention are introduced below through specific embodiments.

[0116] Figure 3 The following is a schematic diagram of some embodiments of the form management method disclosed in the present invention. Preferably, the present embodiment can be executed by the form system disclosed in the present invention. Figure 3 The form management method of the embodiment includes at least one of steps 1 to 3.

[0117] Step 1: Configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships, and attributes.

[0118] In some embodiments of the present disclosure, the entity may be at least one of a person, a place, a thing, an object, and an organization.

[0119] In some embodiments of the present disclosure, the relationship may be a relationship between two entities.

[0120] In some embodiments of the present disclosure, the attribute may be an entity attribute or a relationship attribute.

[0121] In some embodiments of the present disclosure, the graph storage structure of form data is replaceable.

[0122] In some embodiments of the present disclosure, the graph storage structure of the form data may be a graph database, a relational database, a columnar database, etc.

[0123] In some embodiments of the present disclosure, in step 1, the step of configuring the form based on the graph structure to associate components in the form with the graph structure may include at least one step from step 10 to step 12.

[0124] Step 10: Use a graph structure to define the collection objects and content of the form and establish unified standards for data collection.

[0125] In some embodiments of the present disclosure, step 10 may include: using a graph structure to define the collection objects and contents of the form, and formulating unified specifications for data collection, wherein the graph structure includes entities (such as people, places, things, objects, organizations, etc.), relationships (such as person-person service relationships, person-place permanent relationships, etc.), and attributes of entities or relationships (such as person's name attributes, place's coordinate attributes, start and end time attributes of person-place permanent relationships, etc.).

[0126] In some embodiments of the present disclosure, the definitions of entities, relationships, and attributes are standardized and globally consistent, thereby achieving a semantically unified abstraction of collected data.

[0127] In some embodiments of the present disclosure, the form management method may further include: constructing a data layer, wherein the data layer is used to store underlying configuration information of the form system, wherein the underlying configuration information includes a component library, an entity library, a relationship library, an attribute library, and an attribute component mapping library.

[0128] Step 11, form system initialization.

[0129] In some embodiments of the present disclosure, step 11 may include: when the form system is initialized, it loads basic information of the component from the component library, such as name, configuration format, data storage format, data export format, etc. Common basic components (first type components) include text boxes, values, options, etc. Figure 4 Schematic diagram of the first type of components in some embodiments of the present disclosure. Figure 4 As shown in FIG, these first-type components serve as the most basic interaction units and become the data entry and data exit of the entire form system. Figure 4 As shown, the first type of components disclosed in the present invention may include an address filling component, an attachment upload component, a self-increment text box, multiple-choice questions, an address level selection component, a unified social credit code component, a cascading multiple-choice question, an identity document component, a single-line text box, a numerical value, a drop-down single choice, a multi-line text box, a date and time component, an image upload component, a map point selection, a mobile phone number component, a single-choice question and an object code, etc.

[0130] Step 12. In the form configuration interface, based on the user input, for each component or subcomponent in the form, select a first type component or a second type component for configuration, wherein the first type component includes at least one of a text box, a selection box, and a numeric value, and the second type component is a component after the first type component is associated with an entity, an entity attribute, or a relationship attribute.

[0131] In some embodiments of the present disclosure, a component may include at least one subcomponent.

[0132] Figure 5 Schematic diagram of configuring student names in some embodiments of the present disclosure. Figure 5As shown, the personnel information component may include a student name subcomponent, an age subcomponent, and a home address subcomponent.

[0133] In some embodiments of the present disclosure, in the configuration end, user-configurable components include not only basic components such as text boxes, selection boxes, and numerical values ​​(first type components), but also other components generalized from the basic components (second type components). These components are associated with specific entities, entity attributes, or relationship attributes and have easy-to-understand literal meanings. By adding these components to the form content in the configuration end, the user can associate the form content with the graph content.

[0134] In some embodiments of the present disclosure, the entity information box is a component associated with the entity, and there are also components associated with attributes and relationships in the system. For example, "name", "gender", "nationality", etc. are all controls that can be used by users in the system, and these controls are associated with the attributes of the "person" entity. "Start time", "end time", "production method", etc. are also controls that can be used by users in the system, and they are all associated with the attributes of the "manufacturing" relationship.

[0135] In some embodiments of the present disclosure, the display form of the physical information box is replaceable.

[0136] In some embodiments of the present disclosure, the entity information box may be displayed in the form of a semi-closed wireframe, an independent plane, etc. It only needs to express the semantic relevance and irrelevance of the space inside and outside the space respectively.

[0137] In some embodiments of the present disclosure, users can change the title, description, options, display data and other information of a component by themselves, but the corresponding graph elements behind it will not be changed, that is, the component always has a stable semantic interpretation.

[0138] Step 13: Add the first type component or the second type component to the form content according to the user input.

[0139] In some embodiments of the present disclosure, in step 1, the step of configuring the form based on the graph structure to associate components in the form with the graph structure may include at least one step from step 14 to step 17.

[0140] Step 14: In the form configuration interface, all user-available components are displayed to the user through the component area.

[0141] Figure 6 Schematic diagram of the form configuration interface in some embodiments of the present disclosure. Figure 6As shown in the figure, the form configuration page is divided into the component area, form configuration area, and configuration information editing area. The component area displays all components available to users, such as name, ID number, contact information, address, social credit code, etc.

[0142] Step 15: In the form configuration area, an interactive interface for configuring the form is provided to the user, wherein each entity is displayed as an information box with a title in the interactive interface for the user to configure the form.

[0143] Step 16, in the form configuration area, the component selected by the user and its corresponding entity or attribute are displayed in the information box to complete the configuration of the form.

[0144] In some embodiments of the present disclosure, step 15 and step 16 may include: in the form configuration area, in order to optimize the user's configuration experience, the system designs an interaction method based on the user's spatial perception experience. In the interactive interface of the user configuration form, each entity is displayed as an information box with a title. Figure 7 Schematic diagram of interaction design based on spatial perception experience in some embodiments of the present disclosure. Figure 7 As shown in the figure, users can drag or select related entities, attributes or components into the information box according to their understanding of business knowledge and the closeness of the relationship between information, and complete the form configuration in an intuitive way to create a form with graph standard elements, bringing a smooth interactive experience. Specifically, Figure 7 In the embodiment, a place entity information box (home address sub-component) and a personnel information sub-component are provided in the personnel entity information box (personnel component).

[0145] In some embodiments of the present disclosure, business knowledge refers to the knowledge of the business scenario served by the configuration form, and the user configures the form according to the "closeness of the association between information". For example, if a user needs to configure a form to collect "students' off-campus accommodation information", the user will first drag the "name" into the form and then drag the "location" control into the information box where the "name" control is located. This operation process is determined by the user's business knowledge. In business, the information of "students" is closely related to the information of "accommodation location", and the user will naturally place controls with closely related information together.

[0146] Figure 8 Schematic diagram of adding components to the configuration area in some embodiments of the present disclosure. Figure 8 As shown, in the component area, the user can drag and drop a certain type of entity information box component (such as personnel information, location information, etc.) into the form configuration area and other attribute components of this type of entity (such as name, gender, etc.) to set the object to be collected.

[0147] Figure 9aSchematic diagram of entity type selection in some embodiments of the present disclosure. Figure 9a As shown in the figure, when a new information box or attribute components of other types of entities are dragged into an entity information box, the system can automatically pop up entity type options presented in business terms (such as home address, work location, route address, etc.). After the user selects, the information box can be created, and the system will synchronously record the relationship between the two entities in the background. The user can also add attribute components of the relationship under the newly added information box.

[0148] In some embodiments of the present disclosure, the concepts of attributes, entities, and relationships in the knowledge graph are abstract and difficult for users to understand. Directly presenting such abstract concepts to users will cause confusion to users and increase the user's usage threshold. Therefore, the present disclosure displays the specialized description of attributes in classic scenarios (that is, the data mentioned here) on the interactive front desk. Users can understand the meaning of these terms and select corresponding business-compliant terms based on their understanding. The system can also link to the attributes or relationships corresponding to the business information based on the terms. For example, "home address" is a term for the "person-place-permanent" relationship. When the user selects this term, the system will know that the user is adding a "person-place-permanent" relationship to the form.

[0149] Step 17, in the configuration information editing area, modify the configuration information of each component according to the user's input, wherein the configuration information includes at least one of the following information: verification mode, default value, and hidden state, such as Figure 9b shown. Figure 9b This is a schematic diagram of configuring an information editing area in some embodiments of the present disclosure.

[0150] In the configuration information editing area of ​​the present disclosure, users can modify the configuration of each component, including verification mode, default value, hidden status, etc.

[0151] In some embodiments of the present disclosure, specifically, if the user needs to collect the student's home address, the following configuration can be used: Figure 5 The operation process of the form shown is as follows: drag the "Person Name" component from the component area, and modify its component configuration in the configuration information editing area on the right, the system automatically creates the corresponding "Person Entity Box"; drag the "Age" component from the component area to the "Person Entity Box", and modify its component configuration in the configuration information editing area; drag the "Place Name" component from the component area to the "Person Entity Box", the system automatically creates the "Place Entity Box", and the user needs to select the "Home Address" relationship from the recommended relationship list, such as Figure 7 As shown, modify its component configuration in the configuration information editing area; according to the above steps, you can complete the form configuration for collecting student home address information, and the collected content includes the student's name, age and home address.

[0152] In some embodiments of the present disclosure, in step 1, the step of generating form configuration data may include at least one of steps 18 to 19.

[0153] Step 18, generating standardized form configuration data according to the configured form content, wherein the form configuration data includes at least one data table field, and one component corresponds to one data table field; using component identifiers and attribute identifiers to construct the names of the data table fields.

[0154] In some embodiments of the present disclosure, step 18 may include: after the configuration is completed, the system will automatically generate a standardized database table creation statement based on the form content configured by the user, and the graph attribute information corresponding to the field is explicitly recorded in the data table field name, so that the data in the database table can be easily associated with the metadata of its corresponding form, and then converted into application knowledge expressed in the form of a graph.

[0155] In some embodiments of the present disclosure, the user configures a "certificate component" in a form and successfully publishes the form for data collection. Then the system will create a corresponding database table for the form to store the data filled in through the form. When establishing a data table, the system will generate data table fields according to the rules. For example, if the id of the "certificate component" in the form is "IdCard_d5G3E", and the component corresponds to two attributes, namely "IdCard.type" and "IdCard.number", then the data table fields corresponding to this component are "IdCard_d5G3E.type" and "IdCard_d5G3E.number". In short, the system uses the component Id and the attribute Id in the form to jointly construct the field name of the data table, which enables the system to correspond the data with the specific attributes of the specific controls in the form through the field name of the data table when reading the data in the data table.

[0156] In some embodiments of the present disclosure, indexes are designed for graph nodes to enable fast entity and entity association queries.

[0157] Step 19, construct a data management table of components and graph structures to configure entities, relationships and attributes in the form system; when a specific attribute does not meet application requirements, the specific attribute is taken offline to close the user's access to the component related to the specific attribute.

[0158] In some embodiments of the present disclosure, since the entities, relationships and attributes in the graph will change with the iteration of business applications, it is necessary to construct a corresponding data management table to achieve flexible configuration of valid entity, relationship and attribute information in the form system. Fig.10 Schematic diagram of entity, relationship and attribute library in some embodiments of the present disclosure. Fig.10 As shown, the entities include "personnel", "place", "object", "organization" and "event", among which the relationship between "personnel" and "personnel" entity time can be "managed", "management", "bloodline", "service", etc., and the attributes contained in "personnel" include "number", "name", "gender", etc.

[0159] In some embodiments of the present disclosure, if a certain attribute no longer meets the application requirements, it can be taken offline to close the user's access to the component related to the attribute.

[0160] In some embodiments of the present disclosure, the knowledge graph used in the system is constantly updated, which causes the correspondence between components and the knowledge graph to constantly change. For example, the deletion of an attribute in the graph will cause the component corresponding to the attribute to be offline.

[0161] In some embodiments of the present disclosure, there were two relationships between people in the graph, namely the "person-person-bloodline" relationship and the "person-person-relative" relationship. Later, we found that the difference between the two was not significant, so we merged the two into the "person-person-relative" relationship. This resulted in all attributes of the original "person-person-bloodline" relationship being deleted, and the corresponding components also needed to be taken offline, such as "bloodline relationship category", "bloodline relationship start time", etc.

[0162] In some embodiments of the present disclosure, the form management method may further include: using multiple components of different types to express the same attribute.

[0163] In some embodiments of the present disclosure, the same attribute can be expressed in completely different ways. To meet the form configuration requirements of the application to the greatest extent possible, the system supports configuring different components for the attributes. For example, the detailed address attribute can be input through the address selection component, the text box, or even the standard geographic level component. Fig.11 shown. Fig.11 A schematic diagram of optional components of detailed address attributes in some embodiments of the present disclosure.

[0164] Step 2: Configure the data in the form and convert the form-filled data into a graph structure expression.

[0165] In some embodiments of the present disclosure, step 2 may include at least one of steps 20 to 22 .

[0166] Step 20: perform at least one of filling verification, data backfilling and data updating according to the data filled in the form.

[0167] In some embodiments of the present disclosure, Figure 2As shown, the main functions of the application at the reporting end include reporting verification, data backfilling and data updating.

[0168] In some embodiments of the present disclosure, step 20, the step of performing filling verification based on the form filling data may include: when the user fills in the data and submits the form, verifying whether the data filled in by the user complies with the configuration information of the component.

[0169] In some embodiments of the present disclosure, step 20, the step of performing filling verification based on the form filling data may include: when the user fills in the data and after submitting the form, verifying whether the data filled in by the user complies with the configuration of the form.

[0170] In some embodiments of the present disclosure, step 20, the step of backfilling data according to the form filled-in data may include: using an entity identification recognition algorithm, identifying whether the current entity matches an existing entity in the database based on the information of the current entity in the form filled-in data; in the case that the current entity matches an existing entity in the database, associating the information of the same entity in the database; and backfilling the form data based on the information associated with the current entity in the database.

[0171] In some embodiments of the present disclosure, the identification generation / recognition algorithm for entities in the graph is replaceable.

[0172] In some embodiments of the present disclosure, data backfilling refers to the system filling end automatically filling in information for the user based on the user's known information when the user fills in the information, reducing the user's operation burden. This function includes two main steps, namely unique entity identification and entity information association. The former uses the entity identification recognition algorithm to identify whether the entity matches the existing entity in the application database based on the information of the current entity, and the latter associates the information of the same entity in the database. Figure 5 When filling out the form shown, if the form system can obtain the user's address information, it can automatically fill in the information for the user in the component when the user enters the filling page or during the filling process.

[0173] In some embodiments of the present disclosure, step 20, the step of updating data according to the form filling data may include: parsing the form filling data after the user submits the form; updating the parsed form filling data into the database for query analysis by the application system; and updating the entities, relationships and attributes corresponding to the parsed form filling data into the basic database of the system.

[0174] In some embodiments of the present disclosure, the automatic information backfill and the recommended update strategy are replaceable.

[0175] Step 21, receiving the form content after the form configuration is completed or the form data is filled in.

[0176] Step 22, perform component parsing, graph parsing and metadata parsing on the form content.

[0177] In some embodiments of the present disclosure, in step 22, the step of performing component parsing on the form content may include at least one step from step 221 to step 223.

[0178] Step 221, parse each component in the form content respectively, and identify at least one of the component category, configuration information and display control logic.

[0179] Step 222, verify the legitimacy of the component configuration information.

[0180] Step 223, verify whether the component reported data meets the requirements of the component configuration information.

[0181] In some embodiments of the present disclosure, in step 22, the step of parsing the form content into components may include: after the user completes the form configuration or fills in the form data, the form content is submitted to the form system, and the system parses each component in the form configuration and identifies the component category, configuration information, display control logic, etc., verifies the legitimacy of the component configuration description and whether the component filling data meets the component configuration requirements. Figure 5 As shown, the user adds a text input box component to the form on the configuration side, sets the title of the component to "Student Name", the description to "Name registered in the Civil Affairs System", the input limit to 50 characters, the content is required and the component is not hidden; after the user submits the form configuration on the configuration side, the system will check whether the title and description of the component exceed the system limit and perform other checks; and after the user fills in the component and uploads the data on the reporting side, the system will check whether the user has filled in the content in the component and whether the length of the content exceeds 50 characters.

[0182] In some embodiments of the present disclosure, a common limitation for titles and descriptions is the word length limitation, for example, the word count cannot exceed 100.

[0183] In some embodiments of the present disclosure, such as for selection controls, users can configure many options for the user to choose from, but the system needs to limit the maximum number of options that the user can configure (such as a maximum of 100 options, which can meet the needs of most configuration selection controls). Otherwise, some unpredictable situations may occur.

[0184] In some embodiments of the present disclosure, in step 22, the step of performing graph parsing on the form content may include at least one step from step 224 to step 226.

[0185] Step 224, identifying the attribute information linked to the component in the form content.

[0186] Step 225, map the configuration information of the component to the corresponding attribute in the graph, and automatically connect the entity or relationship corresponding to the attribute.

[0187] Step 226, through the context of the form configuration data, the entities, relationships and attributes involved in the form configuration data are associated.

[0188] In some embodiments of the present disclosure, in step 22, the step of performing graph analysis on the form content may include: by identifying the attribute information linked to the components in the user-configured form, mapping the component configuration information to the corresponding attributes in the graph, automatically connecting the entities or relationships corresponding to the attributes, and associating the entities, relationships and attributes involved in the form configuration through the context of the form configuration. Figure 5 As shown, the attribute connected by this component is the "Name" attribute under the "Person" entity, the "Student Address" is connected to the "Description" attribute of the "Place" entity, and the two entities "Person" and "Place" are connected through the "Permanent" relationship.

[0189] In some embodiments of the present disclosure, the step of performing metadata parsing on the form content may include at least one step from step 227 to step 229 .

[0190] Step 227, bind each component to a component type, wherein the component types include text boxes, selection boxes, and numerical values.

[0191] Step 228, determine the data storage type corresponding to the component by identifying the component type corresponding to the component.

[0192] Step 229, determining at least one of the storage field name, default value and index of the data through the configuration information of the component and the context of the form configuration data.

[0193] In some embodiments of the present disclosure, the step of performing metadata analysis on the form content may include: each specific component is bound to a fixed question type, and when parsing the form configuration information, the question type (text box, numeric input, option, etc.) corresponding to the component is identified to determine the data storage type corresponding to the component, and then the storage field name, default value, index and other information of the data are determined through the component configuration information and the form context configuration information. This information will be used to guide the form system to assist the application system in creating a database table. Figure 5As shown in the figure, the data filled in by the user in the "Student Name" component will be stored in the field named "inputWidget_7hdbc7", the type is VARCHAR(50), the default value is empty, and the field value is not allowed to be empty. The VARCHAR type is used to store variable-length strings; input Widget (input control).

[0194] Step 3: Associate the form filling data corresponding to the same entity between different forms.

[0195] In some embodiments of the present disclosure, step 3 may include: the data generated by the form is stored in a structured, digital and physical form.

[0196] In some embodiments of the present disclosure, step 3 may include at least one of steps 31 to 32.

[0197] Step 31: Generate a metadata record file for each form, wherein each metadata record file is used to record entities in the form and relationships between entities, as well as attribute fields belonging to the entities or relationships.

[0198] Step 32, different unique entity identifier generation algorithms are designed for different types of entities, and the parsed data of the same entity in different forms are mapped to the same real entity.

[0199] In some embodiments of the present disclosure, for the entity "person", the structure of its entity identification is " / system version number / entity category code / whether to verify / personnel code", where the personnel code is generated based on the three elements of the person: name, mobile phone number, and ID number. In different authentication requirements, it can be judged whether the entities are the same according to different conditions. For example, in the most stringent conditions, only when the name, mobile phone number, and ID number of a person are the same, they are considered to be the same person; in general scenarios, as long as the mobile phone number is the same, they can be considered to be the same person.

[0200] In some embodiments of the present disclosure, information from different forms can be conveniently transferred by using entities, relationships, and attributes corresponding to the data as anchor points.

[0201] Based on this feature, the public form system can be linked with other business systems to implement customized data update and backfill strategies to improve user form filling efficiency; when the user modifies this information, the business system can also parse the form data into standard graph elements, compare it with the business library of other business systems and prompt for information update. After the user confirms, the business system can automatically update internal data, helping the business system to maintain data more efficiently and allowing users to quickly fill in accurate information the next time they fill out the form.

[0202] The above-mentioned embodiments of the present disclosure can configure the collection form based on the entities, relationships and attributes (including entity attributes and relationship attributes) of the graph, and the components in the form are associated with the attributes in the graph.

[0203] The above-mentioned embodiment of the present disclosure converts the reported data into a graph expression form through form configuration data, so that the reported data has graph-based semantics.

[0204] The reporting end of the above-mentioned embodiment of the present disclosure can obtain other data of the entity in this application or other applications by identifying the entity corresponding to the information filled in by the user, thereby realizing information association of the same entity between different applications.

[0205] The above-mentioned embodiments of the present disclosure may design a component interaction mode based on user space perception experience, and design a physical information box as a closed configuration area, wherein the information in the information box is associated with the semantics identified by the information box.

[0206] The component interaction method designed based on the user's spatial perception experience in the above-mentioned embodiment of the present disclosure refers to the aforementioned "users will naturally place controls with closely related information together". The above-mentioned embodiment of the present disclosure uses a closed configuration area to visually utilize the user's spatial perception experience to enhance the user's perception of the boundaries between different business information in the form. Based on the boundaries between such business information and their business knowledge, the user organizes the positions of different controls according to the degree of connection between the controls.

[0207] Fig.12 This is a schematic diagram of the student off-campus accommodation situation form disclosed in this disclosure. Fig.12 As shown, in some embodiments of the present disclosure, the present disclosure can briefly configure a [Student Off-campus Accommodation Situation] into the following form, and the information in the form can be divided into three parts, namely ① student information, ② off-campus accommodation address information, and ③ landlord information. The boundaries between these three parts of information are visually presented by closed information boxes, and the information in the boxes is closely connected in terms of business. If the student's college needs to be collected, then the user will intuitively drag the "school" or "single-line text box" control into the ① student information box. If the rental method of the accommodation address needs to be collected, the new control will be dragged into the ② off-campus accommodation address information, and so on.

[0208] Therefore, through the present disclosure, the reason why users place closely connected controls together in business, visually utilizing the user's control perception experience, and strengthening the interactive design of the boundaries between different information combinations through closed wireframes plays a great role.

[0209] The form system of related technologies does not associate the data in the form with real entities (such as specific people, places, things, objects, and organizations). More deeply, if the form system only realizes the correspondence between form components and entities, then although the data in the form has semantics that can be parsed, when there are multiple entities in the form, the relationship between the entities cannot be parsed from the form, which causes information loss and reduces the value of data.

[0210] The form system proposed in the present disclosure associates the components in the form with the attributes of entities or relationships during the form configuration stage, so that the components are associated with entities, and the entities can be associated with each other through relationships.

[0211] Fig.13 FIG. 1 is a schematic diagram of the association between two entities in some embodiments of the present disclosure. Fig.13 As shown, by scenarios of multiple entities, the advantages of the form system proposed in the present disclosure compared with the existing form system are explained: if two components are configured in a form, which are used to collect the certificate information of a father and his children respectively, then the form system proposed in the present disclosure can not only associate the two certificate components with the person entities, but also indicate that there is a parent-child relationship between the two person entities through the relationship, such as Fig.13 shown.

[0212] Fig.14 FIG. 1 is a schematic diagram of the structure of some other embodiments of the form system disclosed in the present invention. Fig.14 As shown, the form system includes a memory 91 and a processor 92 .

[0213] The memory 91 is used to store instructions. The processor 92 is coupled to the memory 91 . The processor 92 is configured to execute the form management method involved in the above embodiment based on the instructions stored in the memory.

[0214] like Fig.14 As shown, the form system also includes a communication interface 93 for information exchange with other devices. At the same time, the form system also includes a bus 94, through which the processor 92, the communication interface 93, and the memory 91 communicate with each other.

[0215] The memory 91 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. The memory 91 may also be a memory array. The memory 91 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0216] In addition, the processor 92 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.

[0217] According to another aspect of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the form management method as described in any of the above embodiments is implemented.

[0218] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the form management method as described in any of the above embodiments is implemented.

[0219] In some embodiments of the present disclosure, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

[0220] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, devices, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0221] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0222] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0223] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0224] The form system, form configuration module, parsing module, application layer, parsing layer and data layer described above can be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components or any appropriate combination thereof for performing the functions described in this application.

[0225] So far, the present disclosure has been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.

[0226] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or may be accomplished by instructing the relevant hardware through a program, and the program may be stored in a non-transitory computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0227] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A form management method, applied to a form system, wherein: The form management method comprises: Configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships, and attributes; Through form configuration data, the form filling data is converted into the expression form of graph structure; Associate the form filling data corresponding to the same entity between different forms.

2. The form management method according to claim 1, wherein: The configuring of the form based on the graph structure to associate the components in the form with the graph structure includes: In the form configuration interface, according to the user input, for each component or subcomponent in the form, select a first type component or a second type component for configuration, wherein the first type component includes at least one of a text box, a selection box, and a value, and the second type component is a component obtained by associating the first type component with an entity, an entity attribute, or a relationship attribute, and the component includes at least one subcomponent; According to the user input, the first type component or the second type component is added to the form content.

3. The form management method according to claim 1 or 2, wherein: The configuring of the form based on the graph structure to associate the components in the form with the graph structure includes: In the form configuration interface, all components available to users are displayed to users through the component area; In the form configuration area, an interactive interface for configuring the form is provided for the user, wherein each entity is displayed as an information box with a title in the interactive interface for configuring the form; In the form configuration area, the component selected by the user and its corresponding entity or attribute are displayed in the information box to complete the configuration of the form; In the configuration information editing area, the configuration information of each component is modified according to the user's input, wherein the configuration information includes at least one of a verification mode, a default value and a hidden state.

4. The form management method according to claim 1 or 2, wherein: The generating form configuration data comprises: Generate standardized form configuration data according to the configured form content, wherein the form configuration data includes at least one data table field, and one component corresponds to one data table field; Use component identifiers and attribute identifiers to construct the names of data table fields.

5. The form management method according to claim 1 or 2, further comprising: Perform at least one of filling verification, data backfilling and data update based on the data filled in the form.

6. The form management method according to claim 5, wherein: The verification of filling in the form according to the data filled in the form includes: When the user fills in data and submits the form, check whether the data filled in by the user conforms to the configuration information of the component.

7. The form management method according to claim 5, wherein: The data backfilling according to the form filled data includes: Through the entity identification algorithm, it is determined whether the current entity matches the existing entity in the database according to the information of the current entity in the form filling data; In the case where the current entity matches an existing entity in the database, the information of the same entity in the database is associated with each other; Backfill the form's data based on the information associated with the current entity in the database.

8. The form management method according to claim 5, wherein: The data updating according to the form filling data includes: After the user submits the form, parse the form data; Update the parsed form submission data to the database for system query and analysis; Update the entities, relationships and attributes corresponding to the parsed form submission data into the system database.

9. The form management method according to claim 1 or 2, wherein: The expression form of converting the form filling data into a graph structure through form configuration data includes: Receive the form content after form configuration is completed or form data is filled in; Perform component parsing, graph parsing, and metadata parsing on the form content.

10. The form management method according to claim 9, wherein: The component parsing of the form content includes at least one of the following steps, wherein: Parse each component in the form content respectively, and identify at least one of the component category, configuration information, and display control logic; Verify the legitimacy of component configuration information; Verify whether the component reported data meets the requirements of component configuration information.

11. The form management method according to claim 9, wherein: The graph analysis of the form content includes at least one of the following steps, wherein: Identify the attribute information to which the component is linked in the form content; Map the configuration information of the component to the corresponding attribute in the graph, and automatically connect the entity or relationship corresponding to the attribute; Through the context of the form configuration data, the entities, relationships and attributes involved in the form configuration data are associated.

12. The form management method according to claim 9, wherein: The step of performing metadata analysis on the form content includes at least one of the following steps, wherein: Bind each component to a component type, wherein the component types include text boxes, selection boxes, and values; Determine the data storage type corresponding to the component by identifying the component type corresponding to the component; At least one of the storage field name, default value and index of the data is determined through the configuration information of the component and the context of the form configuration data.

13. The form management method according to claim 1 or 2, wherein: The associating form filling data corresponding to the same entity between different forms includes: For each form, a metadata record file is generated, wherein each metadata record file is used to record entities in the form and relationships between entities, as well as attribute fields belonging to the entities or relationships; Different unique entity identifier generation algorithms are designed for different types of entities, and the parsed data of the same entity in different forms are mapped to the same real entity.

14. The form management method according to claim 1 or 2, further comprising: Build data management tables of components and graph structures to configure entities, relationships, and attributes in the form system; In the case where a specific attribute does not meet the application requirements, the specific attribute is taken offline to close the user's access to the component related to the specific attribute.

15. The form management method according to claim 1 or 2, further comprising: Use multiple components of different types to express the same property.

16. The form management method according to claim 1 or 2, wherein: The entity is at least one of a person, a place, a thing, an object, and an organization; The relationship is a relationship between two entities; The attribute is an entity attribute or a relationship attribute.

17. The form management method according to claim 1 or 2, further comprising: Use a graph structure to define the collection objects and content of the form, and establish unified standards for data collection.

18. The form management method according to claim 1 or 2, further comprising: Construct a data layer, wherein the data layer is used to store the underlying configuration information of the form system, wherein the underlying configuration information includes a component library, an entity library, a relationship library, an attribute library, and an attribute component mapping library.

19. A form system comprising: A form configuration module is configured to configure the form based on the graph structure to associate components in the form with the graph structure and generate form configuration data, wherein the graph structure includes entities, relationships and attributes; The parsing module is configured to convert the form filling data into an expression form of graph structure through form configuration data; and associate the form filling data corresponding to the same entity between different forms.

20. A form system, comprising: a memory configured to store instructions; The processor is configured to execute the instructions so that the form system implements the form management method as described in any one of claims 1-18.

21. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the form management method according to any one of claims 1 to 18 is implemented.

22. A computer program product comprising a computer program, wherein: When the computer program is executed by a processor, the form management method according to any one of claims 1 to 18 is implemented.

Images