CN107766396B - Resource data management method and device - Google Patents
Resource data management method and device Download PDFInfo
- Publication number
- CN107766396B CN107766396B CN201710125134.XA CN201710125134A CN107766396B CN 107766396 B CN107766396 B CN 107766396B CN 201710125134 A CN201710125134 A CN 201710125134A CN 107766396 B CN107766396 B CN 107766396B
- Authority
- CN
- China
- Prior art keywords
- data
- model
- node
- data model
- new
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
Abstract
The invention relates to a resource data management method and device. The method comprises the steps of obtaining newly added resource data, extracting field attributes of the newly added resource data, generating a newly created data model according to the field attributes, creating a newly created node associated with the newly created data model, adding the newly created node to a data management page, reading the newly added resource data according to a node path of the newly created node and searching for the newly created data model when a selection instruction of the newly created node is obtained on the data management page, and generating a form of the newly created resource data according to the newly created data model and displaying the form on the data management page. The resource data management method and the device simplify the workload and the repetitive labor of data management development, and are convenient for users to operate and manage.
Description
Technical Field
The present invention relates to the field of information technologies, and in particular, to a method and an apparatus for managing resource data.
Background
At present, various products of various large, medium and small enterprises have a large amount of resource data, and the enterprises generally adopt a data management device to store and manage the resource data, but because the content and the data type of the resource data of each product are different, the traditional data management device is customized developed according to the specific type of the resource data, and the unified development and management of the resource data of different types cannot be carried out. And each new resource data is subjected to development work of a foreground and a background, so that a small amount of development work is required from database design, background coding, foreground coding, management page design and the like, different types of resource data are required to be designed into different management pages, and a large amount of repeated work is required in the development design of the management pages and the development design of the corresponding background, so that time and labor are consumed. In addition, the management pages of the resource data are too many to be beneficial to the query and management of the data.
Disclosure of Invention
Therefore, it is necessary to provide a resource data management method and device for solving the problems of large workload of design and development and inconvenient data query of the data management device.
A method of resource data management, the method comprising:
acquiring newly added resource data;
extracting field attributes of the newly added resource data;
generating a new data model according to the field attribute;
creating a new node associated with the new data model;
and adding the new node to the data management page, reading the new resource data according to the node path of the new node and searching for a new data model when a selection instruction of the new node is acquired on the data management page, and generating a form of the new resource data according to the new data model and displaying the form on the data management page.
In one embodiment, the method further comprises:
storing the newly-built data model;
matching the field attribute with the field attribute of the established data model;
and when a matched data model which is completely matched with the field attribute exists in the established data model, creating a new node associated with the matched data model.
In one embodiment, the method further comprises:
extracting the data name of the newly added resource data;
and matching the data name with the node name of the established node associated with the matched data model, and storing the newly added resource data according to the node path of the matched node when the matched node matched with the data name exists in the established node.
In one embodiment, the method further comprises:
storing the newly-built data model;
matching the field attribute with the field attribute of the established data model;
when the field attribute is matched with part of field attributes of the established data model, generating a new data model according to the field attribute, and generating a model recommendation interface according to the new data model and the established data model partially matched with the field attributes of the new data model;
marking the unmatched field attributes on a model recommendation interface and displaying model operation options;
and receiving a selected instruction of the model operation option, and executing corresponding model operation according to the operation instruction.
In one embodiment, the model operation options at least comprise a model deactivation option, and the newly-created data model is stored in a model matching library; receiving a selection instruction of a model operation option, and executing corresponding model operation according to the operation instruction, wherein the step comprises the following steps:
when a selected instruction for a model deactivation option is received, the created data model is deleted from the model matching library.
An apparatus for resource data management, the apparatus comprising:
the data acquisition module is used for acquiring newly added resource data;
the attribute extraction module is used for extracting the field attribute of the newly added resource data;
the model new building module is used for generating a new data model according to the field attribute;
the node creating module is used for creating a new node associated with the new data model;
and the data management module is used for adding the new node to the data management page, reading the new resource data according to the node path of the new node and searching for a new data model when a selection instruction of the new node is acquired on the data management page, and generating a form of the new resource data according to the new data model and displaying the form on the data management page.
In one embodiment, the apparatus further comprises:
the model storage module is used for storing the newly-built data model;
the attribute matching module is used for matching the field attribute with the field attribute of the established data model;
and the matching creation module is used for creating a new node associated with the matching data model when the matching data model completely matched with the field attribute exists in the created data model.
In one embodiment, the apparatus further comprises:
the name extraction module is used for extracting the data name of the newly added resource data;
and the name matching module is used for matching the data name with the node name of the established node associated with the matched data model, and storing the newly added resource data according to the node path of the matched node when the matched node matched with the data name exists in the established node.
In one embodiment, the apparatus further comprises:
the model storage module is used for storing the newly-built data model;
the attribute matching module is used for matching the field attribute with the field attribute of the established data model;
the recommendation interface module is used for generating a new data model according to the field attributes when the field attributes are matched with part of the field attributes of the established data model, and generating a model recommendation interface according to the new data model and the established data model partially matched with the field attributes of the new data model;
the option display module is used for marking the unmatched field attributes on a model recommendation interface and displaying model operation options;
and the operation execution module is used for receiving the selected instruction of the model operation option and executing the corresponding model operation according to the operation instruction.
In one embodiment, the model operation options at least comprise a model deactivation option, and the newly-created data model is stored in a model matching library; and the operation execution module is used for deleting the established data model from the model matching library when a selected instruction of the model deactivation option is received.
The resource data management method and the device extract the field attribute of the resource data, automatically generating a corresponding new data model according to the field attribute, creating a new node associated with the new data model, the nodes are managed uniformly on the data management page, the node paths of the nodes correspond to the storage positions of the resource data in the database, when a user selects the nodes on the data management page, reading resource data corresponding to the node path in a database, acquiring data model information associated with the node, generating a form in a corresponding form by the resource data according to the data model and displaying the form on a data management page, the data management page can realize unified query and management of various types of data, greatly simplifies the workload and the repetitive labor of data management development, and is convenient for a user to operate and manage.
Drawings
FIG. 1 is a diagram of an application environment of a method for resource data management in one embodiment;
FIG. 2 is a flow diagram of a method for resource data management in one embodiment;
FIG. 3 is a flowchart of the model matching step of the resource data management method in one embodiment;
FIG. 4 is a flowchart of the node matching step of the resource data management method in one embodiment;
FIG. 5 is a flowchart of a recommended page generation step of the resource data management method in one embodiment;
FIG. 6 is a diagram illustrating an exemplary architecture of an apparatus for resource data management;
FIG. 7 is a diagram showing the structure of a resource data management apparatus in another embodiment;
FIG. 8 is a diagram showing the structure of a resource data management apparatus in another embodiment;
FIG. 9 is a diagram showing the structure of a resource data management apparatus according to still another embodiment;
fig. 10 is a schematic structural diagram of a terminal in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The resource data management method provided in the embodiment of the present invention may be applied to an application environment as shown in fig. 1. The server 102 is connected to a plurality of terminals 104 via a network. The server 102 has a database deployed thereon. The terminal 104 sends the resource data and the resource data storage instruction to the server 102, and the server 102 receives the resource data and the resource data storage instruction and writes the resource data into the database according to the resource data storage instruction. The terminal 104 sends a resource data acquisition request and a terminal identifier to the server 102, the server 102 receives the resource data and the terminal identifier sent by the terminal 104, and the server 102 reads corresponding resource data from a database according to the resource data acquisition request and sends the resource data to the corresponding terminal 104 according to the terminal identifier. This enables a plurality of terminals 104 to share data information of the database on the server 102.
Referring to fig. 2, fig. 2 is a flowchart of a resource data management method in an embodiment, which is described by taking the method as an example for being applied to the terminal in fig. 1, and the method specifically includes the following steps:
The newly added resource data is a newly added data file imported by a user from the resource data management page, the newly added data can be various types of resource data, and the terminal acquires the imported newly added resource data.
The field attribute comprises a field name and a field type of a corresponding field under the field name, and the terminal analyzes the data field in the imported newly added data file and extracts the field name and the field type of the data field.
In one embodiment, before performing step 220, the following steps are further included:
the terminal judges whether the file type of the newly added resource data is a standard file type, if so, step 120 is executed; if not, the terminal converts the file type of the newly added resource data into a standard file type.
Generally, the file type of a newly added data file imported from a resource data management page is a form file in an excel format or a document file in a txt text format, the first data in each line of data in the file is the field name of the line of data, when a terminal extracts the field attribute, the first line of data in the file is extracted to be used as the field name, and the data type of the corresponding data under each field name is identified to be used as the field type.
In this implementation, the standard file type is set to be in an excel format and a txt format, and if the imported new resource data is a file of another type, such as a word-type file or a pdf-type file, the word-type file or the pdf-type file is first converted into the excel format or the txt format, and specifically, the terminal may convert the file type by calling a file conversion tool or a conversion program. In other embodiments, the standard file type may be other file types.
The terminal generates a new data model according to the extracted field name and field type, which can be understood as that the data model stores data structures of different types of resource data, and one data model corresponds to one resource data type. For example, the physical examination information data model is shown in table one:
table one:
| name of field | Type of field |
| Name (I) | Text |
| Sex | Text |
| Date | Date |
| Height of a person | Number |
| Body weight | Number |
| Blood pressure | Number |
The physical examination information data model stores a data structure of resource data of which the resource data type is physical examination information, each field name of the model corresponds to each line of data of the resource data, each field type is a data type of each line of data, and the resource data of the physical examination result type has 6 lines of data in total, namely, a name (Text, Text type), a gender (Text, Text type), a Date (Date type), a height (Number, numerical type), a weight (Number, numerical type) and a blood pressure (Number, numerical type).
After the new data model is generated, the terminal creates a new node, the new node is associated with the new data model, and the terminal can search the data model associated with the new node through the node. The attributes of the node include the node name, the node path, and the association model. The node name may be the same as the name of the imported resource data, or may be automatically numbered according to the associated data model, and preferably, the node name is the name of the imported resource data, so that the resource data is conveniently queried by the node.
When a new node is created, a terminal sends a node path allocation request to a server, the server acquires an allocated storage position from a database according to a data model associated with the new node in the node path allocation request, the path of the storage position is used as a new node path and sent to the terminal, namely the node path corresponds to the storage position in a storage area of the database, after the new node is created, the terminal sends new resource data and the node path to the server, and the server writes the new resource data into the corresponding storage position in the database according to the node path. In this embodiment, the database is deployed on a server. In another embodiment, the database is deployed on the terminal for storing and querying the data resources by the local terminal.
In one embodiment, the database is a Mongodb database (distributed document storage database), the data structure supported by the Mongodb database is very loose, files with different structures can be stored in the same database, and the Mongodb database is high in performance, easy to deploy and easy to use. In one embodiment, nodes associated with the same data model are stored in the same data set in the database, and nodes associated with different data models are stored in different data sets in the database.
And step 250, adding the new node to the data management page, reading the new resource data according to the node path of the new node and searching for a new data model when a selection instruction of the new node is acquired on the data management page, and generating a form of the new resource data according to the new data model and displaying the form on the data management page.
And the terminal adds the newly-built node to a data management page, and the data management page performs unified management and operation on the node. When a user selects a new node on a data management page, a terminal obtains a selection instruction of the new node and obtains a node path of the new node, searches a storage position of corresponding new resource data from a database according to the node path and reads the new resource data, searches a new data model associated with the new node, generates a data form of the new resource data according to a data structure stored by the new data model, and displays the data form on the data management page.
In one embodiment, after the step of obtaining the selection instruction of the new node at the data management page, the method further includes: and searching for the field name of the new model associated with the new node, generating a field selection option and displaying the field selection option on a data management page.
The user can select the field name on the data management page, and after the terminal acquires the selection instruction of the field name, the read new resource data is generated into a form according to the data structure corresponding to the selected field name and displayed on the data management page, namely, the data corresponding to the field name selected by the user is only displayed on the data management page, so that the user can conveniently search the data information to be acquired.
In one embodiment, deletion and combination operation options of nodes are provided on a data management page, when a user selects node deletion operation type selection, a terminal acquires a node deletion instruction, then acquires a node path of the node, searches a storage position of resource data corresponding to the node from a database according to the node path, and deletes the corresponding resource data from the database. When a user carries out the combination operation of a plurality of nodes, the user selects a main node and a home node, a terminal obtains node paths of the main node and the home node, searches storage positions of resource data corresponding to the main node and the home node in a database, moves the resource data corresponding to the home node to the storage position corresponding to the main node, and sets the node name of the combined node as the node name of the main node.
In the resource data management method in the foregoing embodiment, the terminal extracts field attributes of the resource data, automatically generates a corresponding new data model according to the field attributes, creates a new node associated with the new data model, and uniformly manages the nodes on the data management page, where a node path of a node corresponds to a storage location of the resource data in the database, and when a user selects a node on the data management page, reads the resource data corresponding to the node path in the database, and obtains a data model associated with the node, that is, obtains data structure information stored in the data model, and generates the resource data in a corresponding form according to the data structure information stored in the data model and displays the form on the data management page. Therefore, the user can carry out unified query and management on various types of resource data through the data management page, and the data query and management operation of the user is simplified. And the design development of managing pages and background storage of different types of resource data is not needed, so that the workload and the repetitive labor of data management development are greatly simplified.
In one embodiment, the method further comprises the step of storing the newly created data model.
After the terminal executes step 230, the terminal stores the generated new data model into the database, and updates the established data model stored in the database.
In one embodiment, the method further comprises: and adding the new data model to the model management module of the data management page, wherein the step can be executed before the step of storing the new data model or after the step of storing the new data model.
In one embodiment, the step of adding the new data model to the model management module of the data management page further includes prompting the user to input a name of the new data model, where the name of the data model is capable of reflecting a type of the resource data corresponding to the name of the new data model.
The terminal adds the generated new data model to a management module of the page, and when the user selects the model name of the new data model, the field attribute information of the new data model is displayed, so that the user can conveniently check the established data model, and the user can conveniently know the type of the resource data in the data management page.
In this embodiment, as shown in fig. 3, the method further includes the following model matching step:
step 222: and matching the field attribute with the field attribute of the established data model.
In this embodiment, before performing step 230, the terminal matches the field attribute of the newly added data resource with the established data model stored in the database, specifically, the terminal matches the extracted field name of the newly added data resource with the field name of the established data model, if the established data model with completely consistent field names is matched, then determines whether the field types corresponding to the field names are consistent, if so, a matching data model completely matching the field attribute exists in the established data model, and performs step 224; if the field name of the newly added data resource is completely mismatched or partially matched with the field name of the established data model, or the field names are completely matched but the field types corresponding to the field names are not consistent, step 230 is executed.
Step 224: a new node associated with the matching data model is created.
And the terminal establishes the associated model attribute as a new node of the matched data model, and the model information of the matched data model can be found through the new node.
In one embodiment, the storage position in the database corresponding to the node path of the newly-built node is a data set where all nodes of the associated and matched data model are located, the terminal sends the newly-added resource data and the node path to the server, and the server stores the newly-added resource data into the data set.
In the embodiment, the terminal stores the newly-built data model into the database, continuously updates and perfects the data model in the database, matches the field attribute of the newly-added resource data with the built data model after acquiring the newly-added resource data imported by the user, and directly creates the node associated with the matched data model when matching the matched data model with the completely consistent field attribute, so as to avoid generating the newly-built data model repeated with the data model stored in the database, thereby optimizing the storage and page management processes of the newly-added resource data.
In one embodiment, as shown in fig. 4, the method further comprises the following node matching step:
step 215: and extracting the data name of the newly added resource data.
The data name is a file name of the newly added resource data imported by the user, and after the step 210 is executed, the terminal extracts the data name of the newly added resource data. In this embodiment, the data name is used as the node name of the node corresponding to the resource data.
Step 223: and matching the data name with the node name of the established node associated with the matched data model.
After the terminal executes step 222, if a matching data model completely matching the field attribute exists in the established data model, the terminal obtains node names of all established nodes associated with the matching data model, and determines whether a matching node exists in the established nodes, where the node name is consistent with the extracted data name, and if so, obtains a node path of the matching node and executes step 225; if not, go to step 224: a new node associated with the matching data model is created.
The data name of the newly added resource data is consistent with the node name of the established node, which indicates that the newly added resource data is the supplementary update data of the stored resource data in the database.
Step 225: and storing the newly added resource data according to the node path of the matched node.
And the terminal sends the node path and the newly added resource data to the server, and the server stores the newly added resource data to a storage position corresponding to the matching node, namely, the newly added resource data is additionally stored behind the existing resource data.
In the embodiment, when the matched data model completely matched with the field attribute exists in the data model, the data name of the newly added resource data is matched with the established node associated with the matched data model, and when the matched node exists, the newly added resource data is directly stored according to the node path of the matched node without newly establishing the node, so that two identical resource data files are prevented from being established into two nodes which are associated with a unified data model and have the same node name, the trouble of looking up data by a user is avoided, the user can conveniently look up the resource data, the storage form of the resource data is more compact, and the storage space can be effectively utilized.
In one embodiment, the method further comprises the step of storing the newly created data model. After the terminal executes step 230, the terminal stores the generated new data model into the database, and updates the established data model stored in the database.
In this embodiment, as shown in fig. 5, the method further includes the following recommendation page generation step:
step 222: and matching the field attribute with the field attribute of the established data model.
In this embodiment, before performing step 230, the terminal matches the extracted field name of the newly added data resource with the field name of the created data model, and determines whether the field types corresponding to the field names are consistent. When the field name and the field type of the newly added data resource do not completely match the created data model, but a part of the field name matches the created data model, step 230 is executed.
Step 226: and generating a model recommendation interface according to the new data model and the established data model partially matched with the field attribute of the new data model.
The terminal obtains model information of the established data model and model information of the newly-added data model which are partially matched with the field name of the newly-added resource data, generates a model recommendation interface according to the model information, and displays the partially-matched established data model and the newly-added data model together on the model recommendation interface.
In one embodiment, the terminal only obtains the model information of the established data model matching the most field names and displays the model information on the model recommendation interface.
Step 227: and marking the unmatched field attributes at a model recommendation interface and displaying model operation options.
And the terminal compares the newly-built data model with the partially-matched built data model to obtain the name and the type of the difference field, and marks the name and the type of the difference field on a model recommendation interface to prompt a user. And meanwhile, the operation selection of the newly-built data model and the built data model is displayed on the model recommendation interface, so that a user can operate the data model.
In one embodiment, the model operation options include at least a model deactivation option. In another embodiment, the model operation options further comprise a new model confirmation generation option, a model delay option and the like.
Step 228: and receiving a selected instruction of the model operation option, and executing corresponding model operation according to the operation instruction.
And the user selects the model operation selection displayed on the model recommendation interface, and the terminal receives a selection instruction of the user on the model operation selection and operates the data model according to the selection instruction.
In one embodiment, the newly created data model is stored in a model matching library, and when the terminal receives a selected instruction for a model deactivation option, the created data model is deleted from the model matching library.
And the terminal stores the generated new data model in the model matching library, updates the existing data model in the model matching library, and when new resource data is input, the new resource data is only matched with the data model in the model matching library, and the data models stored in other storage areas in the database do not participate in matching. When the data structure of the resource data of the same type is adjusted, the originally established data model is not suitable any more, a newly established data model generated according to the adjusted resource data needs to be replaced, but the resource data corresponding to the associated node of the established model still needs to be reserved, and the user can delete the established data model from the model matching library and store the data model in other areas by selecting a model deactivation option, so that the resource data with the same data structure as the established data model can still be searched, meanwhile, the interference of the newly increased resource data in model matching can be reduced, and the matching efficiency is improved.
In one embodiment, when the terminal receives a selected instruction of the model delay option, the newly built data model is deleted, and the partially matched built data model displayed on the model recommendation page continues to be delayed. When some field names of the displayed newly-built data model and the displayed established data model are only slightly different, the user judges whether the field name of the newly-added resource data is wrongly input or has the same semantics, and when the resource type corresponding to the newly-added resource data and the established data model is determined to belong to the same type, the user can associate the newly-added resource data with the established data model through model delay operation, so that a repeated data model which occupies resources and is not beneficial to data viewing is avoided being generated.
In the above embodiment, the terminal continuously updates and perfects the data model in the database by storing the newly-created data model in the database, and after acquiring newly-added resource data imported by the user, matches the field attribute of the newly-added resource data with the created data model, and when the created data model is partially matched with the field attribute of the newly-added resource data, generates the model recommendation interface, the user can visually check the comparison result between the newly-created data model and the created data model through the model recommendation interface, compare the type of the resource data with the type of the existing resource data, determine whether the type of the existing resource data is still applicable, or check the input newly-added resource data, and perform corresponding operation on the data model according to the determination result by selecting the model operation option, so that the data model stored in the data can be updated along with the update of the resource data structure, and optimizes the steps of model matching.
The following description will be made specifically by taking a patient hospitalization information resource data management system of a hospital as an example. The medical information resource data comprises various types of resource data such as personal basic information resource data, medication information resource data, medical record resource data, physical examination information resource data and the like. After a user imports resource data with a file name of 'research and development department physical examination result' from a resource data page, a terminal extracts field attributes of the resource data as name (Text), gender (Text), Date (Date), height (Number), weight (Number) and blood pressure (Number) after acquiring the resource data, matches the field attributes with established data models in a database, successfully matches the established data models with physical examination information data models (model information of the physical examination information data models is shown in the table I), acquires node names associated with the physical examination information data models, matches the node names with the 'research and development department physical examination result', and creates new nodes with the node names of 'research and development department physical examination result' and the physical examination information data models when judging that no nodes with name matching exist in the associated nodes. And storing the resource data into a corresponding area in the database according to the node path of the newly-built node.
In one embodiment, as shown in fig. 6, there is provided a resource data management apparatus including: a data acquisition module 602, an attribute extraction module 604, a model creation module 606, a node creation module 608, and a data management module 610, wherein:
a data obtaining module 602, configured to obtain new resource data;
an attribute extraction module 604, configured to extract a field attribute of the newly added resource data;
a model creation module 606, configured to generate a new data model according to the field attribute;
a node creating module 608, configured to create a new node associated with the new data model;
and the data management module 610 is configured to add the new node to the data management page, and when a selection instruction of the new node is acquired on the data management page, read the new resource data according to a node path of the new node and search for a new data model, and generate a form from the new resource data according to the new data model and display the form on the data management page.
In one embodiment, as shown in fig. 7, the apparatus further comprises: a model storage module 607, an attribute matching module 609 and a match creation module 611, wherein:
the model storage module 607 is used for storing the newly-built data model;
the attribute matching module 609 is used for matching the field attribute with the field attribute of the established data model;
a matching creating module 611, configured to create a new node associated with the matching data model when there is a matching data model that completely matches the field attribute in the created data model.
In one embodiment, as shown in fig. 8, the apparatus further comprises: a name extraction module 612 and a name matching module 614, wherein:
a name extraction module 612, configured to extract a data name of the newly added resource data;
and a name matching module 614, configured to match the data name with a node name of an established node associated with the matching data model, and store the newly added resource data according to a node path of the matching node when there is a matching node matching the data name in the established node.
In one embodiment, as shown in fig. 9, the apparatus further comprises: a model storage module 607, an attribute matching module 609, a recommendation interface module 613, an option presentation module 615 and an operation execution module 617, wherein:
the model storage module 607 is used for storing the newly-built data model;
the attribute matching module 609 is used for matching the field attribute with the field attribute of the established data model;
a recommendation interface module 613, configured to generate a new data model according to the field attribute when the field attribute matches with a partial field attribute of the already-established data model, and generate a model recommendation interface according to the new data model and the already-established data model partially matching with the field attribute of the new data model;
the option display module 615 is used for marking the unmatched field attributes on a model recommendation interface and displaying model operation options;
the operation executing module 617 is configured to receive a selected instruction for the model operation option, and execute a corresponding model operation according to the selected instruction.
In one embodiment, the model operation options include at least a model deactivation option, the newly created data model is stored in a model matching library; the operation execution module 617 is further configured to delete the created data model from the model matching library when a selected instruction for the model deactivation option is received.
In one embodiment, as shown in FIG. 10, a terminal 100 is provided that includes a processor 110, an internal memory 120, a non-volatile storage medium 140, and a network interface 130 connected by a system bus. The non-volatile storage medium 140 of the terminal 100 stores therein an operating system 142 and a resource data management device 144, and the resource data management device 144 is configured to implement processing of different types of resource data. The processor 110 of the terminal 100 is for providing computing and control capabilities and is configured to perform a resource data management method. The internal memory 120 provides an environment for the operation of the resource data management device 144 in the non-volatile storage medium 140, and the internal memory 120 may store computer readable instructions, which when executed by the processor, may cause the processor to perform a resource data management method. The network interface 130 is used for communicating with an external server via a network connection. Those skilled in the art will appreciate that the configuration shown in fig. 10 is a block diagram of only a portion of the configuration relevant to the present application, and does not constitute a limitation on the terminal to which the present application is applied, and that a particular terminal may include more or less components than those shown in the drawings, or may combine certain components, or have a different arrangement of components.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for resource data management, the method comprising:
acquiring newly added resource data;
extracting field attributes of the newly added resource data;
generating a new data model according to the field attribute;
creating a new node associated with the new data model;
adding the new node to a data management page, reading the newly added resource data according to the node path of the new node and searching the new data model when a selection instruction of the new node is obtained on the data management page, and generating a form of the newly added resource data according to the new data model and displaying the form on the data management page;
the method further comprises the following steps:
storing the newly-built data model;
matching the field attribute with the field attribute of the established data model before generating a new data model according to the field attribute;
and when a matched data model which is completely matched with the field attribute exists in the established data model, creating a new node associated with the matched data model.
2. The method for resource data management according to claim 1, wherein said method further comprises:
extracting the data name of the newly added resource data;
and matching the data name with the node name of the established node associated with the matched data model, and storing the newly added resource data according to the node path of the matched node when the matched node matched with the data name exists in the established node.
3. The method for resource data management according to claim 1, wherein said method further comprises:
storing the newly-built data model;
matching the field attribute with the field attribute of the established data model;
when the field attribute is matched with part of field attributes of the established data model, generating a new data model according to the field attribute, and generating a model recommendation interface according to the new data model and the established data model partially matched with the field attributes of the new data model;
marking the unmatched field attributes on the model recommendation interface and displaying model operation options;
and receiving a selected instruction of the model operation option, and executing corresponding model operation according to the operation instruction.
4. The resource data management method of claim 3, wherein the model operation options include at least a model deactivation option, the newly created data model being stored in a model matching library; the step of receiving a selected instruction of the model operation option and executing corresponding model operation according to the operation instruction comprises the following steps:
and when a selected instruction of the model deactivation option is received, deleting the established data model from a model matching library.
5. An apparatus for resource data management, the apparatus comprising:
the data acquisition module is used for acquiring newly added resource data;
the attribute extraction module is used for extracting the field attribute of the newly added resource data;
the model new building module is used for generating a new data model according to the field attribute;
the node creating module is used for creating a new node associated with the new data model;
the data management module is used for adding the newly-built node to a data management page, reading the newly-added resource data according to the node path of the newly-built node and searching the newly-built data model when a selection instruction of the newly-built node is obtained on the data management page, and generating a form of the newly-added resource data according to the newly-built data model and displaying the form on the data management page;
the device further comprises:
the model storage module is used for storing the newly-built data model;
the attribute matching module is used for matching the field attribute with the field attribute of the established data model before the new data model is generated according to the field attribute;
and the matching creation module is used for creating a new node associated with the matched data model when the matched data model completely matched with the field attribute exists in the created data model.
6. The apparatus for resource data management according to claim 5, wherein said apparatus further comprises:
the name extraction module is used for extracting the data name of the newly added resource data;
and the name matching module is used for matching the data name with the node name of the established node associated with the matched data model, and storing the newly added resource data according to the node path of the matched node when the matched node matched with the data name exists in the established node.
7. The apparatus for resource data management according to claim 5, wherein said apparatus further comprises:
the model storage module is used for storing the newly-built data model;
the attribute matching module is used for matching the field attribute with the field attribute of the established data model;
the recommendation interface module is used for generating a new data model according to the field attributes when the field attributes are matched with part of the field attributes of the established data model, and generating a model recommendation interface according to the new data model and the established data model partially matched with the field attributes of the new data model;
the option display module is used for marking the unmatched field attributes on the model recommendation interface and displaying model operation options;
and the operation execution module is used for receiving the selected instruction of the model operation option and executing the corresponding model operation according to the operation instruction.
8. The apparatus according to claim 7, wherein the model operation options include at least a model deactivation option, the newly created data model being stored in a model matching library; the operation execution module is further used for deleting the established data model from a model matching library when a selected instruction of the model deactivation option is received.
9. A computer arrangement comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1-4 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710125134.XA CN107766396B (en) | 2017-03-03 | 2017-03-03 | Resource data management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710125134.XA CN107766396B (en) | 2017-03-03 | 2017-03-03 | Resource data management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107766396A CN107766396A (en) | 2018-03-06 |
| CN107766396B true CN107766396B (en) | 2020-03-27 |
Family
ID=61264942
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710125134.XA Active CN107766396B (en) | 2017-03-03 | 2017-03-03 | Resource data management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107766396B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108446935A (en) * | 2018-04-02 | 2018-08-24 | 北京小度信息科技有限公司 | Method for managing resource, device, electronic equipment and computer readable storage medium |
| CN110543946B (en) * | 2018-05-29 | 2022-07-05 | 百度在线网络技术（北京）有限公司 | Method and apparatus for training a model |
| CN109471840B (en) * | 2018-10-15 | 2021-10-26 | 北京海数宝科技有限公司 | File viewing method and device, computer equipment and storage medium |
| CN111475513B (en) * | 2020-06-28 | 2020-10-02 | 平安国际智慧城市科技股份有限公司 | Form generation method and device, electronic equipment and medium |
| CN112328633A (en) * | 2020-10-16 | 2021-02-05 | 安徽精益测绘有限公司 | Measurement data attribute intelligent matching and identifying module for database construction |
| CN115774707B (en) * | 2023-02-15 | 2023-05-12 | 广州汇通国信科技有限公司 | Object attribute-based data processing method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101241434A (en) * | 2008-03-04 | 2008-08-13 | 浪潮集团山东通用软件有限公司 | Form self-defining method |
| CN105069092A (en) * | 2015-08-05 | 2015-11-18 | 深圳联友科技有限公司 | Report display method, system and mobile terminal |
| CN105373523A (en) * | 2015-10-14 | 2016-03-02 | 浪潮软件集团有限公司 | Workflow solution method based on user-defined form and Activiti |
| CN105843788A (en) * | 2016-03-31 | 2016-08-10 | 浪潮通信信息系统有限公司 | Report generation method and device |
| CN106294389A (en) * | 2015-05-20 | 2017-01-04 | 上海纳鑫信息科技有限公司 | A kind of method and system realizing customizing form |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8234242B2 (en) * | 2009-01-22 | 2012-07-31 | International Business Machines Corporation | Maintaining a data structure with data set names and pointers to a plurality of catalogs |
-
2017
- 2017-03-03 CN CN201710125134.XA patent/CN107766396B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101241434A (en) * | 2008-03-04 | 2008-08-13 | 浪潮集团山东通用软件有限公司 | Form self-defining method |
| CN106294389A (en) * | 2015-05-20 | 2017-01-04 | 上海纳鑫信息科技有限公司 | A kind of method and system realizing customizing form |
| CN105069092A (en) * | 2015-08-05 | 2015-11-18 | 深圳联友科技有限公司 | Report display method, system and mobile terminal |
| CN105373523A (en) * | 2015-10-14 | 2016-03-02 | 浪潮软件集团有限公司 | Workflow solution method based on user-defined form and Activiti |
| CN105843788A (en) * | 2016-03-31 | 2016-08-10 | 浪潮通信信息系统有限公司 | Report generation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107766396A (en) | 2018-03-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107766396B (en) | Resource data management method and device | |
| CN108874926B (en) | Mass data query method, device, computer equipment and storage medium | |
| CN111339171B (en) | Data query method, device and equipment | |
| CN108664582B (en) | Enterprise relation query method and device, computer equipment and storage medium | |
| US10268655B2 (en) | Method, device, server and storage medium of searching a group based on social network | |
| CN103400579A (en) | Voice recognition system and construction method | |
| CN108228770A (en) | A kind of method and device of application file source inquiry | |
| CN111818175B (en) | Enterprise service bus configuration file generation method, device, equipment and storage medium | |
| CN113094370A (en) | Data index construction method and device, storage medium and electronic equipment | |
| CN111083054B (en) | Route configuration processing method and device, computer equipment and storage medium | |
| CN109213775B (en) | Search method, search device, computer equipment and storage medium | |
| CN113407560B (en) | Update message processing method, data synchronization method and configuration information configuration method | |
| CN105843809B (en) | Data processing method and device | |
| CN112231317B (en) | Data query method, device, electronic device and storage medium | |
| US11755631B2 (en) | Workflow-based dynamic data model and application generation | |
| CN112905600A (en) | Data query method and device, storage medium and electronic equipment | |
| CN111552527A (en) | Method, device and system for translating characters in user interface and storage medium | |
| CN115858463A (en) | Data management method, device, equipment and storage medium | |
| CN106547843B (en) | Multi-stage classification query method and device | |
| JPH10143539A (en) | Information retrieving method, its system, recording medium recording information resource dictionary data and recording medium recording information retrieving program | |
| CN110532457B (en) | Method and system for acquiring network segment ID | |
| CN107644103A (en) | It is a kind of can tracing information source information storage method and system | |
| CN112052234A (en) | Service data processing method and device, storage medium and electronic device | |
| JP2015095092A (en) | Information processing system, information processing device, information processing method, and program | |
| JP2020161089A (en) | Information processing device, information processing method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220519 Address after: 518048 China Aviation Center 2901, No. 1018, Huafu Road, Huahang community, Huaqiang North Street, Futian District, Shenzhen, Guangdong Province Patentee after: Shenzhen Ping An medical and Health Technology Service Co.,Ltd. Address before: Room 12G, Area H, 666 Beijing East Road, Huangpu District, Shanghai 200001 Patentee before: PING AN MEDICAL AND HEALTHCARE MANAGEMENT Co.,Ltd. |
|
| TR01 | Transfer of patent right |