CN115617797A - Dynamic expansion method of service metadata field, electronic equipment and storage medium - Google Patents
Dynamic expansion method of service metadata field, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115617797A CN115617797A CN202211257737.2A CN202211257737A CN115617797A CN 115617797 A CN115617797 A CN 115617797A CN 202211257737 A CN202211257737 A CN 202211257737A CN 115617797 A CN115617797 A CN 115617797A
- Authority
- CN
- China
- Prior art keywords
- meta
- metadata
- model
- service metadata
- attribute
- 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.)
- Pending
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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Abstract
The invention provides a dynamic expansion method of a service metadata field, electronic equipment and a storage medium, wherein the method comprises the following steps: constructing a meta-model class table and a meta-model class attribute table according to the object type and the attribute contained in the initial service metadata; constructing a meta-model attribute value storage table; defining each field information of the initial service metadata; constructing a meta-model management module, and creating a meta-model class and a meta-model class attribute of the initial service metadata; acquiring target metadata, initializing a meta-model type and meta-model type attributes in a meta-model management module, adding target service metadata attribute information, expanding values of fields and fields of the target service metadata, and updating the meta-model type attribute information of the target service metadata; and obtaining information of the target metadata field and the field value and dynamically rendering the information at the front end. The invention realizes dynamic expansion of the service metadata field through the design of the metadata storage structure, the service metadata byte storage and the constructed metadata management module.
Description
Technical Field
The invention relates to the technical field of metadata management, in particular to a dynamic expansion method of a service metadata field, electronic equipment and a storage medium.
Background
In the process of data governance, metadata is needed to be used to perform basic definition of data content and format on a data use data structure of a business system, perform some basic standardized management on subsequent use of data, and add business attribute description, classification and the like on data aiming at different business systems.
Data governance is widely applied in different industries at present, business metadata needs to be modified when requirements in different projects are different, and therefore the development amount on programs is greatly increased. Not only the database table structure of the metadata needs to be modified, but also the system code related to the metadata needs to be modified, the development workload is large, different system versions need to be maintained subsequently, and the implementation and deployment cost is increased. Even if the system is modified for different service scenes before online use, the requirement of the user in the use process cannot be met. When the system is in use, if the service is changed, the service metadata is also changed correspondingly.
In summary, when the prior art faces different service scenarios, it is impossible to dynamically extend the service metadata field online without modifying the database table structure and the system code or closing the system.
Disclosure of Invention
In view of this, it is necessary to provide a method, an electronic device, and a storage medium for dynamically expanding a service metadata field, which can dynamically expand the service metadata field on line without modifying a database table structure and a system code and without closing a system, so as to meet requirements in different service scenarios.
In order to solve the above technical problem, in one aspect, the present invention provides a method for dynamically expanding a service metadata field, including:
constructing a meta-model class table and a meta-model class attribute table according to the object type and the attribute contained in the initial service metadata;
constructing a meta-model class attribute value storage table which is not influenced by the change of the meta-model class attributes;
defining information of each field of initial service metadata in the meta-model class table, the meta-model class attribute table and the meta-model class attribute value storage table;
constructing a meta-model management module, and creating a meta-model class and a meta-model class attribute of the initial service metadata in the meta-model management module;
acquiring target metadata, initializing a meta-model class and meta-model class attributes in the meta-model management module, adding attribute information of the target service metadata, expanding values of fields and fields of the target service metadata according to the attribute information of the target service metadata, and updating the meta-model class attribute information of the target service metadata;
and obtaining the information of the target metadata field and the field value and dynamically rendering the information at the front end.
Further, the meta-model class table includes at least four fields of class ID, class name, class code, and class description.
Further, the meta-model class attribute table at least comprises five fields of an attribute ID, a class ID, an attribute name, an attribute code and an attribute type.
Further, the meta-model class attribute value storage table at least comprises four fields of class ID, entity ID, attribute ID and attribute value.
Further, the defining information of each field of the initial service metadata in the meta model class table, the meta model class attribute table, and the meta model class attribute value storage table includes:
defining the meaning of each field of the initial service metadata;
defining different initial metadata field names according to different fields of the initial service metadata;
defining the data type and length of each field of the initial service metadata;
determining a storage mode of data of each field according to the data type of each field of the initial service metadata;
the display mode of each field of the initial service metadata on a page is ensured;
and defining dictionary values of fields of the initial service metadata and null value information.
And further, modifying and deleting the created meta-model class and the meta-model class attribute according to the meta-model management module.
Further, the expanding target service metadata field according to the target service metadata attribute information includes:
and defining the data type, the length and the dictionary value of the class attribute table field of the target service metadata.
Further, the obtaining information of the fields and the field values of the target metadata is dynamically rendered at a front end, and includes:
acquiring fields and field values of non-business metadata of the target metadata according to the entity table of the target metadata;
acquiring fields and field values of the service metadata according to the meta-model attribute value table of the target service metadata;
and associating the field value of the non-business metadata with the field value of the business metadata, assembling the data into uniform format, returning the data to the page, and dynamically rendering the data at the front end.
In another aspect, the present invention further provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where when the processor executes the computer program, the method for dynamically expanding the service metadata field as described above is implemented.
Finally, the present invention also provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the dynamic service metadata field expansion method as described above.
The beneficial effects of adopting the above embodiment are: the invention provides a dynamic expansion method of service metadata fields, which designs a metadata model data storage structure of service metadata, designs a metadata model attribute value storage table which is not influenced by the attribute change of the metadata model, creates metadata model types and class attributes according to a constructed metadata model management module, only needs to acquire target metadata when facing new service requirements, initializes the metadata model types and the metadata model attributes in the metadata model management module, expands the values of the fields and the fields according to the attribute information of the target service metadata, updates the metadata model attribute information of the target service metadata, and acquires the information of the fields and the field values of the target metadata to dynamically render at the front end. The invention solves the problems of database table structure modification and system code modification caused by different business metadata fields in different projects, and reduces the workload of software developers and the workload of project deployment implementation. And various requirements of the user on data management can be realized through simple configuration under the condition of upgrading the system without stopping.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of an embodiment of a dynamic expansion method for a service metadata field according to the present invention;
FIG. 2 is a schematic structural diagram of an embodiment of a meta-model type table and a meta-model type attribute table according to the present invention;
FIG. 3 is a schematic structural diagram of an embodiment of a meta-model class attribute value storage table according to the present invention;
FIG. 4 is a flowchart of a method for dynamically rendering an embodiment of the invention;
fig. 5 is a schematic structural diagram of an embodiment of an electronic device provided in the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. It should be apparent that the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be understood that the schematic drawings are not necessarily to scale. The flowcharts used in this disclosure illustrate operations implemented according to some embodiments of the present invention. It should be understood that the operations of the flow diagrams may be performed out of order, and that steps without logical context may be performed in reverse order or concurrently. One skilled in the art, under the direction of this summary, may add one or more other operations to, or remove one or more operations from, the flowchart.
Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor systems and/or microcontroller systems.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein may be combined with other embodiments.
Before the description of the embodiments, the related words are paraphrased:
metadata: metadata is data that describes the structure and method of building data within a data warehouse and can be divided into two categories depending on the purpose: technical metadata and business metadata.
Technical metadata: technical metadata is data that stores technical details about the data warehouse system and is data used to develop and manage data warehouse usage.
Service metadata: business metadata describes data in a data warehouse from a business perspective, and provides a semantic layer between users and actual systems, so that business personnel who do not know computer technology can read the data in the data warehouse
Meta-model management: meta-model management is the definition of meta-data, and the design of meta-models can be completed quickly through meta-model configuration capability.
Based on the above description of technical terms, in the prior art, since the business metadata needs to be modified due to different requirements of different projects, the development amount of the program is greatly increased. Not only the database table structure of the metadata needs to be modified, but also the system code related to the metadata needs to be modified, the development workload is large, different system versions need to be maintained subsequently, and the implementation and deployment cost is increased. Even if the system is modified for different service scenes before online use, the requirement of the user in the use process cannot be met. When the system is in use, if the service changes, the service metadata is changed correspondingly. The invention aims to provide a method for dynamically expanding service metadata fields on line under the conditions of not modifying database table structures and system codes and not closing a system.
Specific examples are described in detail below, respectively:
the embodiment of the invention provides a dynamic expansion method of a service metadata field, electronic equipment and a storage medium, which are respectively explained below.
As shown in fig. 1, fig. 1 is a schematic flow chart of an embodiment of a dynamic expansion method for a service metadata field provided by the present invention, where the dynamic expansion method for the service metadata field includes:
s101, constructing a meta-model class table and a meta-model class attribute table according to object types and attributes contained in initial service metadata;
s102, constructing a meta-model attribute value storage table which is not influenced by the change of the meta-model attribute;
s103, defining each field information of the initial service metadata in the meta model class table, the meta model class attribute table and the meta model class attribute value storage table;
s104, constructing a meta-model management module, and creating a meta-model class and a meta-model class attribute of the initial service metadata in the meta-model management module;
s105, acquiring target metadata, initializing a meta-model class and meta-model class attributes in the meta-model management module, adding attribute information of target service metadata in the target metadata, expanding values of fields and fields of the target service metadata according to the attribute information of the target service metadata, and updating the meta-model class attribute information of the target service metadata;
and S106, obtaining the information of the target metadata field and the field value and dynamically rendering the information at the front end.
Compared with the prior art, the method for dynamically expanding the service metadata field provided by the embodiment of the invention is characterized in that a meta-model data storage structure of the service metadata is designed, a meta-model attribute value storage table which is not influenced by the change of the meta-model attribute is designed, the meta-model class and the class attribute are created according to the constructed meta-model management module, when a new service requirement is met, only target metadata needs to be obtained, the meta-model class and the meta-model attribute are initialized in the meta-model management module, the field value and the field value are expanded according to the attribute information of the target service metadata, the meta-model attribute information of the target service metadata is updated, and the information of the target metadata field and the field value is dynamically rendered at the front end. The method can dynamically expand the service metadata field on line under the conditions of not modifying the database table structure and system codes and not closing the system.
In some embodiments of the present invention, as shown in fig. 2, fig. 2 is a schematic structural diagram of an embodiment of a meta-model class table and a meta-model class attribute table provided in the present invention.
The meta-model class table at least comprises four fields of class ID, class name, class code and class description, and the primary key in the original model class table is set as the field of the class ID.
The meta-model attribute table at least comprises five fields of attribute ID, class ID, attribute name, attribute code and attribute type, and the primary key in the original model attribute table is set as the field of the attribute ID.
It should be noted that, in the above embodiment and fig. 2, only the meta model type table and the association relationship between the main fields in the meta model type attribute table and the two tables are listed, and the fields in the tables do not contain all fields.
In some embodiments of the present invention, as shown in fig. 3, fig. 3 is a schematic structural diagram of an embodiment of a meta model attribute value storage table provided in the present invention, where the meta model attribute value storage table at least includes four fields of a primary key ID, an entity ID, an attribute ID, and an attribute value, and the primary key in the meta model attribute value storage table is set as a field where the class ID is located.
It should be noted that the meta-model class table, the original-model class attribute table, and the meta-model class attribute value storage table all include a class ID field, that is, the meta-model class table, the original-model class attribute table, and the meta-model class attribute value storage table can be associated with each other by the class ID field.
In the specific embodiment of the invention, because the fields of the service metadata are dynamic, the fields can be expanded in the meta-model management at any time, the description information of the fields is stored in the meta-model class attribute table, and the fields are not created in the table of the database. Based on this characteristic, the embodiment of the present invention is directed to designing a class attribute value storage table that is not affected by the change in the meta-model class attribute.
The entity object described by the service metadata field is changed, and when the value of the service metadata field is stored, which entity described by the attribute value is to be distinguished, so the ID of the entity is to be stored. Considering that the service metadata field is dynamic, can be added and deleted, and can also modify the field name, the attribute ID, which is a value that does not change once created, should be used to identify the attribute corresponding to the current attribute value.
Further, in some embodiments of the present invention, after the meta-model class table, the original-model class attribute table, and the meta-model class attribute value storage table are created, field information included in the meta-model class table needs to be defined, where the field information includes:
defining the meaning of each field of the initial service metadata;
defining different initial metadata field names according to different fields of the initial service metadata;
defining the data type and length of each field of the initial service metadata;
determining a storage mode of data of each field according to the data type of each field of the initial service metadata;
the display mode of each field of the initial service metadata on a page is ensured;
and defining dictionary values of fields of the initial service metadata and null value information.
It should be noted that the display mode of the field on the page may be a text format, a drop-down box, a radio box, or the like, which is convenient for dynamic rendering of the page.
Further, in some embodiments of the present invention, a meta-model management module needs to be constructed, the meta-model management module completes definition of the meta-data, and the meta-model class and the class attribute are created in the meta-data management module, and the created meta-model class and the meta-model class attribute may be modified and deleted.
It should be noted that, part of meta-model classes are essential for normal operation of the system, and may be initialized in meta-model management, such as table types, column types, and the like.
Further, in some embodiments of the present invention, for target metadata in an actual project, first, target metadata is obtained, where the target metadata includes business metadata and non-business metadata, a meta-model class and a meta-model class attribute that do not need to be changed in a system are initialized in a meta-model management module, at this time, metadata defined by a meta-model may already satisfy normal operation of a basic function of the system, then, attribute information of the target business metadata in the target metadata is added, values of fields and fields of the target business metadata are expanded according to the attribute information of the target business metadata, meta-model class attribute information of the target business metadata is updated, and information of the fields and fields of the target metadata is obtained and dynamically rendered at a front end.
It should be noted that, the target service metadata field is expanded according to the attribute information of the target service metadata, and mainly includes data type, length and dictionary value of the class attribute table field defining the target service metadata.
The embodiment of the invention designs the meta-model data storage structure of the service metadata, designs the meta-model attribute value storage table which is not influenced by the change of the meta-model attribute, creates the meta-model class and the class attribute according to the constructed meta-model management module, only needs to acquire the target metadata when facing new service requirements, initializes the meta-model class and the meta-model attribute in the meta-model management module, expands the values of the fields and the fields according to the attribute information of the target service metadata, updates the meta-model attribute information of the target service metadata, and realizes the dynamic expansion of the service metadata fields.
Further, in some embodiments of the present invention, after implementing dynamic extension of a service metadata field, it is necessary to dynamically render updated information at a front end, as shown in fig. 4, where fig. 4 is a flowchart of a method of an embodiment of dynamic rendering provided by an embodiment of the present invention, and a step of the method includes:
s401, acquiring fields and field values of non-business metadata of the target metadata according to the entity table of the target metadata;
s402, acquiring fields and field values of the service metadata according to the meta-model class attribute value table of the target service metadata;
and S403, associating the field values of the non-service metadata with the field values of the service metadata, assembling the data into data with a uniform format, returning the data to a page, and dynamically rendering the data at the front end.
In the specific embodiment of the invention, different metadata types are distinguished according to class codes in the meta-model class, and then the class attribute information, namely the value of the metadata field, is inquired by the primary key of the meta-model class. The field value needs to be obtained in two cases, the first is the value of the non-service metadata field, which is directly obtained from the metadata object entity table, and the second is the value of the service metadata field, which is obtained from the meta-model class attribute value table. And then, associating the field values acquired in the two ways with the fields, and assembling the fields into data in a uniform format to be returned to the page, wherein specific examples of the data in the uniform format are as follows:
it should be noted that, when a metadata field and a field value are dynamically rendered on a page, the type of the metadata should not be distinguished, and only meta model attribute information for page rendering carried in a field concerning the metadata is used, and the information mainly includes: attribute names, page element types (e.g., text entry box, radio box, drop-down box, etc.), attribute codes (for presenting and storing values for fields), whether null is allowed (if null is not allowed, the page is checked for non-null while saving data), default value presentation for fields, and the like.
The embodiment of the invention designs a meta-model data storage structure of the service metadata, designs a meta-model class attribute value storage table which is not influenced by the change of the meta-model class attribute, creates the meta-model class and the class attribute according to the constructed meta-model management module, only needs to acquire the target metadata when facing new service requirements, initializes the meta-model class and the meta-model class attribute in the meta-model management module, expands the values of fields and fields according to the attribute information of the target service metadata, updates the meta-model class attribute information of the target service metadata, and then acquires the information of the fields and the field values of the target metadata to be dynamically rendered at the front end. The problem of database table structure modification and system code modification caused by different business metadata fields in different projects is solved, and the workload of software developers and the workload of project deployment and implementation are reduced. And various requirements of the user on data management can be realized through simple configuration under the condition of upgrading the system without stopping.
As shown in fig. 5, the present invention also provides an electronic device 500. The electronic device 500 includes a processor 501, a memory 502, and a display 503. Fig. 5 shows only some of the components of the electronic device 500, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead.
In some embodiments, processor 501 may be a single server or a group of servers. The server groups may be centralized or distributed. In some embodiments, the processor 501 may be local or remote. In some embodiments, processor 501 may be implemented in a cloud platform. In an embodiment, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an intra-house, a multi-cloud, and the like, or any combination thereof.
The storage 502 may be an internal storage unit of the electronic device 500, such as a hard disk or a memory of the electronic device 500, in some embodiments. The memory 502 may also be an external storage device of the electronic device 500 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc., provided on the electronic device 500.
Further, the memory 502 may also include both internal storage units and external storage devices of the electronic device 500. The memory 502 is used for storing application software and various data for installing the electronic device 500.
The display 503 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch panel, or the like in some embodiments. The display 503 is used to display information at the electronic device 500 and to display a visual user interface. The components 501-503 of the electronic device 500 communicate with each other via a system bus.
In one embodiment, when the processor 501 executes the dynamic extension method of the service metadata field in the memory 502, the following steps can be implemented:
constructing a meta-model class table and a meta-model class attribute table according to the object type and the attribute contained in the initial service metadata;
constructing a meta-model attribute value storage table which is not influenced by the change of the meta-model attribute;
defining each field information of the initial service metadata in the meta model class table, the meta model class attribute table and the meta model class attribute value storage table;
constructing a meta-model management module, and creating a meta-model class and a meta-model class attribute of the initial service metadata in the meta-model management module;
acquiring target metadata, initializing a meta model type and a meta model type attribute in the meta model management module, adding attribute information of target service metadata in the target metadata, expanding values of fields and fields of the target service metadata according to the attribute information of the target service metadata, and updating the meta model type attribute information of the target service metadata;
and dynamically rendering the information of the target metadata field and the field value at the front end.
It should be understood that: when the processor 501 executes the dynamic extension program of the service metadata field in the memory 502, it may also implement other functions in addition to the above functions, which may be specifically referred to the description of the corresponding method embodiment above.
Further, the type of the mentioned electronic device 500 is not specifically limited in the embodiment of the present invention, and the electronic device 500 may be a portable electronic device such as a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a wearable device, and a laptop computer (laptop). Exemplary embodiments of portable electronic devices include, but are not limited to, portable electronic devices that carry an IOS, android, microsoft, or other operating system. The portable electronic device may also be other portable electronic devices such as laptop computers (laptop) with touch sensitive surfaces (e.g., touch panels), etc. It should also be understood that in other embodiments of the present invention, the electronic device 500 may not be a portable electronic device, but may be a desktop computer having a touch-sensitive surface (e.g., a touch panel).
Correspondingly, the embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium is used to store a computer-readable program or instruction, and when the program or instruction is executed by a processor, the step or the function in the dynamic service metadata field expansion method provided in the foregoing method embodiments can be implemented.
Those skilled in the art will appreciate that all or part of the processes of the methods of the above embodiments may be implemented by instructing relevant hardware (such as a processor, a controller, etc.) by a computer program, and the computer program may be stored in a computer readable storage medium. The computer readable storage medium is a magnetic disk, an optical disk, a read-only memory or a random access memory.
The service metadata field dynamic expansion method, the electronic device and the storage medium provided by the present invention are introduced in detail, and a specific example is applied in the present document to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for those skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A dynamic expansion method for service metadata fields is characterized by comprising the following steps:
constructing a meta-model class table and a meta-model class attribute table according to the object type and the attribute contained in the initial service metadata;
constructing a meta-model class attribute value storage table which is not influenced by the change of the meta-model class attributes;
defining each field information of the initial service metadata in the meta model class table, the meta model class attribute table and the meta model class attribute value storage table;
constructing a meta-model management module, and creating a meta-model class and a meta-model class attribute of the initial service metadata in the meta-model management module;
acquiring target metadata, initializing a meta model type and a meta model type attribute in the meta model management module, adding attribute information of the target service metadata, expanding values of fields and fields of the target service metadata according to the attribute information of the target service metadata, and updating the meta model type attribute information of the target service metadata;
and dynamically rendering the information of the target metadata field and the field value at the front end.
2. A dynamic expansion method for service metadata fields according to claim 1, characterized in that the meta-model class table at least comprises four fields of class ID, class name, class code and class description.
3. A method for dynamically expanding service metadata fields according to claim 1, wherein the meta model class attribute table at least comprises five fields of attribute ID, class ID, attribute name, attribute code and attribute type.
4. The dynamic expansion method for the service metadata field according to claim 1, wherein the meta-model class attribute value storage table at least includes four fields of class ID, entity ID, attribute ID and attribute value.
5. The method according to claim 1, wherein the defining information of each field of the initial service metadata in the meta-model class table, the meta-model class attribute table, and the meta-model class attribute value storage table includes:
defining the meaning of each field of the initial service metadata;
defining different initial metadata field names according to different fields of the initial service metadata;
defining the data type and length of each field of the initial service metadata;
determining a storage mode of data of each field according to the data type of each field of the initial service metadata;
the display mode of each field of the initial service metadata on a page is ensured;
and defining dictionary values of fields of the initial service metadata and null value information.
6. The dynamic expansion method of service metadata field according to claim 1, characterized in that the created meta-model class and meta-model class attributes are modified and deleted according to the meta-model management module.
7. The dynamic extending method for service metadata fields according to claim 1, wherein the extending target service metadata fields according to the target service metadata attribute information includes:
and defining the data type, the length and the dictionary value of the class attribute table field of the target service metadata.
8. The dynamic expansion method for the service metadata field according to claim 1, wherein the step of obtaining the information of the field and the field value of the target metadata is dynamically rendered at a front end, and includes:
acquiring fields and field values of non-business metadata of the target metadata according to the entity table of the target metadata;
acquiring fields and field values of the service metadata according to the meta-model attribute value table of the target service metadata;
and associating the field value of the non-business metadata with the field value of the business metadata, assembling the data into uniform format, returning the data to the page, and dynamically rendering the data at the front end.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for dynamically expanding service metadata fields according to any one of claims 1 to 8 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored, which program, when executed by a processor, implements a method for dynamic extension of service metadata fields according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211257737.2A CN115617797A (en) | 2022-10-12 | 2022-10-12 | Dynamic expansion method of service metadata field, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211257737.2A CN115617797A (en) | 2022-10-12 | 2022-10-12 | Dynamic expansion method of service metadata field, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115617797A true CN115617797A (en) | 2023-01-17 |
Family
ID=84862111
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211257737.2A Pending CN115617797A (en) | 2022-10-12 | 2022-10-12 | Dynamic expansion method of service metadata field, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115617797A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116737113A (en) * | 2023-04-23 | 2023-09-12 | 中国科学院高能物理研究所 | Metadata catalog management system and method for mass scientific data |
-
2022
- 2022-10-12 CN CN202211257737.2A patent/CN115617797A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116737113A (en) * | 2023-04-23 | 2023-09-12 | 中国科学院高能物理研究所 | Metadata catalog management system and method for mass scientific data |
| CN116737113B (en) * | 2023-04-23 | 2024-01-02 | 中国科学院高能物理研究所 | Metadata catalog management system and method for mass scientific data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10846071B2 (en) | Data model API for live applications in a cloud collaboration platform | |
| US9037614B1 (en) | Secondary mappings to enable code changes without schema updates | |
| JP2018010642A (en) | Annotations of resources | |
| US20120102453A1 (en) | Multi-dimensional objects | |
| US8782631B2 (en) | Copy management of process versions over lifecycle | |
| US8312445B2 (en) | User-specified install locations | |
| CN111078205A (en) | Modular programming method and device, storage medium and electronic equipment | |
| CN102541963B (en) | Method and device for inquiring character identification | |
| CN115617797A (en) | Dynamic expansion method of service metadata field, electronic equipment and storage medium | |
| KR101150121B1 (en) | Method and apparatus for constructing representations of objects and entities | |
| US20130124611A1 (en) | Unified repository & tool infrastructure | |
| US8166080B2 (en) | Optimized computer diagramming method | |
| CN111158777B (en) | Component calling method, device and computer readable storage medium | |
| CN117170655A (en) | Metadata processing method and device, data processing equipment and storage medium | |
| US7664776B1 (en) | Methods and apparatus for dynamic form definition | |
| CN111610908B (en) | Method for generating frame diagram, computer equipment and readable storage medium | |
| CN102193907A (en) | Method and system for comparing manuscripts based on B/S (Browser/Server) structure | |
| CN111221560B (en) | Resource management method and device and electronic equipment | |
| CN114816470A (en) | Metadata database management method and device, electronic equipment and medium | |
| CN113110846A (en) | Method and device for acquiring environment variable | |
| CN112685078A (en) | Interface document generation and query method, device and computer readable storage medium | |
| CN102567431B (en) | Document processing method and device | |
| CN112632294B (en) | Method and system for synchronizing Neo4j data to search server | |
| CN108319750B (en) | Subway engineering collaborative design system based on DWG file splitting and recombining method | |
| CN114238839A (en) | Page generation method and device, electronic equipment and storage medium |
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 |