CN111142989B - Object management method, device and storage medium - Google Patents
Object management method, device and storage medium Download PDFInfo
- Publication number
- CN111142989B CN111142989B CN201911232577.4A CN201911232577A CN111142989B CN 111142989 B CN111142989 B CN 111142989B CN 201911232577 A CN201911232577 A CN 201911232577A CN 111142989 B CN111142989 B CN 111142989B
- Authority
- CN
- China
- Prior art keywords
- data
- management
- page
- target metadata
- target
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The application relates to an object management method, a device and a storage medium, belonging to the technical field of computers, wherein the method comprises the following steps: acquiring target metadata of a target object when the object management page is displayed, wherein the target metadata is obtained through dynamic configuration; rendering the page elements in the object management page according to the target metadata; inputting management information in the rendered object management page; sending the management information to a server for data persistence; the problem that the object management efficiency is low because the content of the page field of the existing object management system is fixed and the change requirement of the object type or the object attribute cannot be met without modifying codes can be solved; because the dynamic configuration of the target metadata is supported, the content rendered according to the target metadata on the object management page is uncertain, and at this time, a configurator can dynamically configure the target metadata to change the fields of the object management page according to the needs, without modifying the system code, and the object management efficiency can be improved.
Description
Technical Field
The application relates to an object management method, an object management device and a storage medium, and belongs to the technical field of computers.
Background
The resource information of the monitoring cameras in the public security information network and the video private network is generally managed through a one-machine one-file management system. The one-machine one-file management system is used for collecting, maintaining and managing the resource information of the monitoring camera in the network.
The existing implementation mode of the one-machine one-file system generally defines the equipment type (category) of the video monitoring equipment to be managed in advance, extracts the equipment attributes of the video monitoring equipment, and encapsulates the equipment attributes into corresponding objects in codes for processing. In this design mode, both the device type and the device attribute of the system-managed surveillance video device are fixed.
However, if the type or attribute of the device managed by the system needs to be changed, the developer needs to modify the code according to the change requirement, and the operation and maintenance personnel needs to redeploy the modified system to meet the customer requirement. Because the system can only manage preset devices of several types, the attribute of the preset devices cannot be changed once deployed, and the requirements of device types and device attribute change can be met only by continuous deployment and upgrading, the management mode has low efficiency.
Disclosure of Invention
The application provides an object management method, an object management device and a storage medium, which can solve the problem that the object management efficiency is lower because the content of a page field of the existing object management system is fixed and the change requirement of an object type or an object attribute cannot be met without modifying codes. The application provides the following technical scheme:
in a first aspect, there is provided an object management method, the method comprising:
receiving a display operation of an object management page;
when the object management page is displayed based on the display operation, acquiring target metadata of a target object, wherein the target metadata is obtained through dynamic configuration;
rendering page elements in the object management page according to the target metadata;
inputting management information in the rendered object management page;
and sending the management information to a server for data persistence.
Optionally, before the obtaining the target metadata of the target object, the method further includes:
displaying a data configuration page;
and configuring target metadata of the target object in the data configuration page, and sending the target metadata to a server.
Optionally, after the sending the management information to the server, the method further includes:
receiving a view operation of the management information;
acquiring the management information from the server based on the viewing operation;
and displaying the management information in the rendered object management page.
Optionally, the target metadata includes: object type data, object attribute data, a data dictionary corresponding to the object attribute data, and relationship data between object types.
Optionally, the management information includes a value of data described by the target metadata.
In a second aspect, there is provided an object management method, the method comprising:
displaying a data configuration page;
configuring target metadata of the target object in the data configuration page;
and sending the target metadata to a server for data persistence, wherein the target metadata is used for rendering page elements in the object management page so as to input management information in the rendered object management page.
In a third aspect, there is provided an object management method, the method comprising:
receiving a metadata acquisition request;
sending target metadata of a target object to a management end based on the metadata acquisition request, so that the management end renders page elements in an object management page according to the target metadata; the management information is input into the rendered object management page, and the target metadata is obtained by configuring the configuration end in the data configuration page;
and receiving and storing the management information sent by the management end.
Optionally, before receiving the metadata acquisition request, the method further includes:
and receiving and storing the target metadata of the target object sent by the configuration end.
Optionally, after receiving the management information sent by the management end, the method includes:
receiving a viewing request sent by the management end, wherein the viewing request is used for requesting to view the management information;
and sending the management information indicated by the viewing request to the management end so that the management end can display the rendered object management page.
In a fourth aspect, there is provided an object management apparatus, the apparatus comprising:
the operation receiving module is used for receiving the display operation of the object management page;
the data acquisition module is used for acquiring target metadata of a target object when the object management page is displayed based on the display operation, wherein the target metadata is obtained through dynamic configuration;
the page rendering module is used for rendering page elements in the object management page according to the target metadata;
the information acquisition module is used for inputting management information into the rendered object management page;
and the information sending module is used for sending the management information to the server side for data persistence.
In a fifth aspect, there is provided an object management apparatus, the apparatus comprising:
the page display module is used for displaying the data configuration page;
the data configuration module is used for configuring target metadata of the target object in the data configuration page;
the data sending module is used for sending the target metadata to the server for data persistence, and the target metadata is used for rendering page elements in the object management page so as to input management information in the rendered object management page.
In a sixth aspect, there is provided an object management apparatus, the apparatus comprising:
the request receiving module is used for receiving the metadata acquisition request;
the data sending module is used for sending target metadata of a target object to a management end based on the metadata acquisition request so that the management end renders page elements in an object management page according to the target metadata; recording management information in the rendered object management page, wherein the target metadata is configured by the configuration terminal on a data configuration page;
and the information receiving module is used for receiving and storing the management information sent by the management end.
In a seventh aspect, there is provided an object management apparatus, the apparatus comprising a processor and a memory; the memory stores a program, and the program is loaded and executed by the processor to implement the object management method according to the first aspect; or, to implement the object management method described in the second aspect; or, to implement the object management method described in the third aspect.
In a fourth aspect, there is provided a computer-readable storage medium having stored therein a program that is loaded and executed by the processor to implement the object management method of the first aspect; or, to implement the object management method described in the second aspect; or, to implement the object management method described in the third aspect.
The application has the beneficial effects that: receiving a display operation of an object management page; acquiring target metadata of a target object when an object management page is displayed based on a display operation; rendering the page elements in the object management page according to the target metadata; inputting management information in the rendered object management page; sending the management information to a server for data persistence; the problem that the object management efficiency is low because the content of the page field of the existing object management system is fixed and the change requirement of the object type or the object attribute cannot be met without modifying codes can be solved; because the content displayed according to the target metadata on the object management page supports dynamic configuration, a configurator can configure the target metadata according to actual requirements, and the configuration can take effect immediately after the completion of the configuration, so that the goal of flexibly managing the target metadata and the object management information without modifying codes is achieved, and the object management efficiency is improved.
The foregoing description is only an overview of the present application, and is intended to provide a better understanding of the present application, as it is embodied in the following description, with reference to the preferred embodiments of the present application and the accompanying drawings.
Drawings
FIG. 1 is a schematic diagram of an object management system according to an embodiment of the present application;
FIG. 2 is a flow chart of an object management method provided by one embodiment of the present application;
FIG. 3 is a flow chart of an object management method according to another embodiment of the present application;
FIG. 4 is a block diagram of an object management apparatus provided by one embodiment of the present application;
FIG. 5 is a block diagram of an object management apparatus provided by one embodiment of the present application;
FIG. 6 is a block diagram of an object management apparatus provided by one embodiment of the present application;
fig. 7 is a block diagram of an object management apparatus according to an embodiment of the present application.
Detailed Description
The following describes in further detail the embodiments of the present application with reference to the drawings and examples. The following examples are illustrative of the application and are not intended to limit the scope of the application.
Metadata (Metadata): also called intermediate data and relay data, is information about the organization of data, data fields and their relationships. In other words, metadata is data (data about data) describing data, mainly information describing data attributes (properties), and is used to support functions such as indicating storage locations, history data, resource searching, file recording, and the like. In the present application, metadata refers to data for describing management information, such as: the metadata includes the type of objects, object attributes, and associations between objects that are involved in the object management system.
Fig. 1 is a schematic structural diagram of an object management system according to an embodiment of the present application, as shown in fig. 1, the system at least includes: configuration side 110, management side 120, and service side 130.
The configuration end 110 and the management end 120 are in communication connection with the service end 130 through wired or wireless modes.
Alternatively, the configuration terminal 110 and the management terminal 120 may be electronic devices with man-machine interaction function and processing function, such as a computer, a mobile phone, a tablet computer, and the like.
The configuration terminal 110 is used for displaying a data configuration page; configuring target metadata of a target object in a data configuration page; the target metadata is sent to the server 130 for data persistence.
Alternatively, the server 130 may be a device such as a server having data storage and processing capabilities.
The server 130 is configured to receive and store target metadata of the target object sent by the configuration end 110.
Optionally, the server 130 stores the target metadata through a relational database.
The management end 120 is configured to receive a display operation of an object management page; acquiring target metadata of a target object when an object management page is displayed based on a display operation; rendering the page elements in the object management page according to the target metadata; inputting management information in the rendered object management page; the management information is sent to the server 130 for data persistence.
The server 130 receives and stores management information transmitted from the management 120.
Optionally, the server 130 stores the management information through a non-relational database.
Alternatively, the configuration end 110 and the management end 120 may be implemented in the same device; or in a different device.
The number of configuration terminals 110 may be one or more, and the number of management terminals 120 may be one or more, and the number of configuration terminals 110 and management terminals 120 is not limited in this embodiment.
Fig. 2 is a flowchart of an object management method according to an embodiment of the present application, and this embodiment is described by taking the application of the method to the object management system shown in fig. 1 as an example. The method at least comprises the following steps:
in step 201, the configuration terminal displays a data configuration page.
The data configuration page is used for a user to dynamically configure target metadata of the target object. The target metadata refers to data for describing management information of the target object.
Optionally, the target object includes, but is not limited to: personnel, equipment, books, etc., the present embodiment does not limit the type of target object.
Step 202, the configuration end configures target metadata of the target object in the data configuration page.
Optionally, the target metadata includes: object type data, object attribute data, a data dictionary corresponding to the object attribute data, and relationship data between object types.
The object type data is used to represent the type of the object. Optionally, the object type data includes, but is not limited to: object type name, object type identification, object type description, and/or object type ordering order. Taking a target object as an example of equipment, the object type data comprises equipment names, equipment type identifiers, equipment type descriptions and equipment type ordering sequences; the device type identifier may be a device code, a device number, etc., and the embodiment does not limit the type of the device identifier. Similarly, the object type identifier is used to uniquely identify the target object, and the implementation of the object type identifier is not limited in this embodiment.
Alternatively, the object type ordering order may be obtained by the user dragging the ordering order of the respective target objects; alternatively, the sequence number may be obtained by inputting a sequence number (e.g., 1, 2, 3, 4, etc.), and the embodiment does not limit the manner of obtaining the ordering sequence.
The object attribute data is used to describe attributes of the corresponding type of object. Optionally, the object attribute data includes, but is not limited to: attribute name, attribute identification, attribute type, attribute constraint rule, whether it is a mandatory attribute, whether it is list-exposed, and whether it is a query condition. Wherein the attribute constraint rule refers to a constraint condition of data having a corresponding attribute type.
Such as: the attribute types are as follows: text boxes, tree text boxes, numeric values, phone numbers, mailboxes, web addresses, IP addresses, mac addresses, dates, drop-down boxes, tables, pictures, files, and the like. The limiting type of the text length is divided into an unlimited, fixed length and a range length; the tree text box is divided into a single selection type and a multiple selection type; the numerical value is divided into an integer, a positive number, a negative number and a decimal number, and if the numerical value is the decimal number, the decimal number is required to be configured; the form is divided into a single choice and a multiple choice.
The corresponding relation between the attribute type and the attribute constraint rule is shown in the following table one:
table one:
the above-mentioned attribute types and attribute constraint rules are merely illustrative, and the correspondence between the attribute types and attribute constraint rules may be other types in actual implementation, which is not listed here.
The data dictionary corresponding to the object attribute is used for defining and describing data items, data structures, data streams, data storage and/or processing logic and the like of the data. The purpose of the data dictionary is to describe each element in the data flow chart in detail. Optionally, the data dictionary includes, but is not limited to: dictionary entries such as configuration item names, configuration item keys, configuration item values, types, remote url addresses, field contents, default presentation fields, and/or extension data.
Relationship data between object types is used to represent data of type relationships between different target objects. Such as: for a certain target object, the relationship data between object types includes: child object type identification, child object attribute identification, parent object type identification, and parent object attribute identification.
Optionally, the data configuration page includes: an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control, and a relationship data configuration control. When a first configuration operation acting on an object type data configuration control is received, the configuration end receives object type data in a data configuration page; then, for a certain configured object type data, when receiving a second configuration operation acting on the object attribute data configuration control, the configuration terminal receives the object attribute data of the object type data in a data configuration page; for a certain configured object attribute data, when a third configuration operation acting on a data dictionary configuration control is received, a configuration end receives a data dictionary corresponding to the object attribute data in a data configuration page; for certain configured object type data and/or object attribute data, when a fourth configuration operation acting on the relationship data configuration control is received, the configuration end receives relationship data among the object types in the data configuration page.
Alternatively, each object type data may correspond to one or more sets of object attribute data.
In step 203, the configuration end sends the target metadata to the server end for data persistence.
The target metadata is used for rendering page elements in the object management page so as to input management information in the rendered object management page.
In step 204, the server receives and stores the target metadata of the target object sent by the configuration end.
The target metadata is obtained through dynamic configuration.
The target metadata is obtained by the configuration end in the configuration page. Optionally, the server manages the target metadata through a relational database. In other words, the server stores the target metadata through the table structure.
The target metadata is assumed to include: object type data, object attribute data, a data dictionary corresponding to the object attribute data, and relationship data between object types, target metadata stored by the server are shown in the following table two to table five respectively, wherein the table two is stored object type data, the table three is stored object attribute data, the table four is relationship data between stored object types, and the table five is stored data dictionary.
And (II) table:
table three:
table four:
table five:
in step 205, the management end receives a display operation of the object management page.
The object management page is used for acquiring management information of each target object.
Optionally, the management end receives the display operation of the object management page, generates a metadata acquisition request, and sends the metadata acquisition request to the server end. The metadata acquisition request is used for requesting target metadata of each target object stored by the server.
In one implementation, after receiving the display operation, the management end invokes a communication interface of the server end to send a metadata acquisition request to the server end.
In step 206, the server receives a metadata acquisition request when the object management page is displayed based on the display operation.
In step 207, the server sends the target metadata of the target object to the management end based on the metadata acquisition request.
The target metadata are used for the management end to render the page elements in the object management page according to the target metadata; and inputting management information in the rendered object management page.
In step 208, the management end obtains the target metadata of the target object.
Optionally, before this step, the management end may display a data configuration page; and configuring target metadata of the target object in the data configuration page, and sending the target metadata to the server. In other words, the management end may also be implemented as a configuration end, and the related description of this part is the same as that of steps 201-203, except that the execution body is different, which is not repeated here in this embodiment.
In step 209, the management end renders the page elements in the object management page according to the target metadata.
Such as: the target metadata comprises object type data of a network camera and object attribute data of a device state, and the management end renders a drop-down frame of the network camera on an object management page.
Step 210, the management end inputs management information in the rendered object management page.
Alternatively, the object management page may pop up or be provided with a data entry page for entering management information.
The management information includes values of data described by the target metadata. In other words, the management information is information described by the target metadata.
Such as: for object attribute data "object state", the management information acquired by the management end is: on-line. The management information is content that the manager inputs to be managed.
Step 211, the management end sends the management information to the server end for data persistence.
Step 212, the server receives and stores the management information sent by the management end.
Optionally, in this implementation, the server stores the management information through a non-relational database. Since the target metadata is dynamically configured, the data amount and storage format of the target metadata are uncertain. In other words, there are several types of device data, which attributes there are, what types of storage formats for the attributes are, and nothing can be determined. Based on the characteristics of the target metadata, it is necessary to store management information using non-relational data with flexible storage methods and high expansibility. In addition, because the amount of management information required to be managed by the server may be large, and the read-write performance of the non-relational database is better than that of the relational database, the read-write performance of the data can be improved by storing the management information by adopting the non-relational database.
When the server side stores the management information, the target metadata and the corresponding management information are stored in the form of key value pairs.
Optionally, referring to fig. 3, after step 212, the method further comprises steps 31-35:
step 31, the management end receives the viewing operation of the management information.
Since the management end may need to check the management information after receiving the management information, at this time, detailed information of the management information needs to be checked. Optionally, an information viewing control is set in the object management page, and when the user needs to view details of the management information, the management end receives a viewing operation serving as an information viewing space.
And generating a viewing request when the management end receives the viewing operation, and sending the viewing request to the server end.
Step 32, the server receives a viewing request sent by the management end, where the viewing request is used for requesting to view management information.
And step 33, the server side sends the management information indicated by the viewing request to the management side so that the management side can display the rendered object management page.
Optionally, the viewing request carries an information identifier of management information, the information identifier may be a key in a key value pair, and the server determines corresponding management information according to the information identifier, and sends the management information to the management end.
In step 34, the management terminal obtains management information from the server terminal based on the viewing operation.
And 35, the management end displays management information in the rendered object management page.
In summary, in the object management method provided in this embodiment, the display operation of the object management page is received; acquiring target metadata of a target object when an object management page is displayed based on a display operation; rendering the page elements in the object management page according to the target metadata; inputting management information in the rendered object management page; sending the management information to a server; the problem that the object management efficiency is low because the content of the page field of the existing object management system is fixed and the change requirement of the object type or the object attribute cannot be met without modifying codes can be solved; because the content displayed according to the target metadata on the object management page supports dynamic configuration, a configurator can configure the target metadata according to actual requirements, and the configuration can take effect immediately after the completion of the configuration, so that the goal of flexibly managing the target metadata and the object management information without modifying codes is achieved, and the object management efficiency is improved.
In addition, the target metadata includes object type data, object attribute data, a data dictionary corresponding to the object attribute data, and relationship data between the object types; the object type and the object attribute can be dynamically modified or expanded, and the relation between the objects can be dynamically configured; thus, the page elements on the object management page can be dynamically displayed; the method solves the problem that the page elements displayed on the object management page and the display modes of the page elements are fixed; the flexibility of object management is improved.
In addition, by setting the query conditions in the target metadata, the query conditions on the object management page can be dynamically configured, and according to the requirements of users, the attribute of any one device can be set as the query conditions, so that the flexibility of setting the query conditions is improved.
In addition, by dynamically configuring the attribute types and the corresponding attribute constraint rules, the system can verify the validity of the value of the attribute according to the requirements, and the data verification mode does not need to be added and modified in the code, so that the efficiency of verifying whether the value of the attribute is valid or not is improved.
Alternatively, the steps performed by the configuration end side described above may be implemented separately as embodiments of the configuration end side; the steps performed by the management side may be implemented solely as embodiments of the management side; the steps performed by the server side may be implemented separately as embodiments of the server side.
Fig. 4 is a block diagram of an object management apparatus according to an embodiment of the present application, and this embodiment is described by taking an example that the apparatus is applied to a management end 120 in the object management system shown in fig. 1. The device at least comprises the following modules: the operations receiving module 410, the data obtaining module 420, the page rendering module 430, the information obtaining module 440, and the information transmitting module 450.
An operation receiving module 410, configured to receive a display operation of the object management page;
the data obtaining module 420 is configured to obtain target metadata of a target object when the object management page is displayed based on the display operation, where the target metadata is obtained through dynamic configuration;
a page rendering module 430, configured to render the page elements in the object management page according to the target metadata;
an information acquisition module 440, configured to enter management information in the rendered object management page;
and the information sending module 450 is configured to send the management information to a server for data persistence.
For details, reference is made to the steps executed by the management end.
Fig. 5 is a block diagram of an object management apparatus according to an embodiment of the present application, and this embodiment is described by taking a configuration terminal 110 of the apparatus applied to the object management system shown in fig. 1 as an example. The device at least comprises the following modules: a page display module 510, a data configuration module 520, and a data transmission module 530.
A page display module 510 for displaying a data configuration page;
a data configuration module 520, configured to configure target metadata of the target object in the data configuration page;
the data sending module 530 is configured to send the target metadata to a server for data persistence, where the target metadata is used to render page elements in the object management page, so as to input management information in the rendered object management page.
For details, reference is made to the steps executed by the configuration end.
Fig. 6 is a block diagram of an object management apparatus according to an embodiment of the present application, and this embodiment is described by taking a server 130 of the object management system shown in fig. 1 as an example. The device at least comprises the following modules: a request receiving module 610, a data transmitting module 620, and an information receiving module 630.
A request receiving module 610, configured to receive a metadata acquisition request;
the data sending module 620 is configured to send, based on the metadata acquisition request, target metadata of a target object to a management end, so that the management end renders a page element in an object management page according to the target metadata; recording management information in the rendered object management page;
and the information receiving module 630 is configured to receive and store the management information sent by the management end.
For details, reference is made to the steps executed by the server.
It should be noted that: in the object management device provided in the above embodiment, only the division of the above functional modules is used for illustration, and in practical application, the above functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the object management device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the object management device and the object management method provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the object management device and the object management method are detailed in the method embodiments, which are not described herein again.
Fig. 7 is a block diagram of an object management apparatus according to an embodiment of the present application, where the object management apparatus may be the configuration side 110, the management side 120, or the service side 130. The apparatus comprises at least a processor 701 and a memory 702.
The processor 701 may include one or more processing cores, such as: 4 core processors, 8 core processors, etc. The processor 701 may employ a DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA
(Programmable Logic Array) the programmable logic array is implemented in at least one hardware form. The processor 701 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 701 may integrate a GPU (Graphics Processing Unit, image processor) for rendering and drawing of content required to be displayed by the display screen. In some embodiments, the processor 701 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 702 may include one or more computer-readable storage media, which may be non-transitory. The memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 702 is used to store at least one instruction for execution by processor 701 to implement the object management method provided by the method embodiments of the present application.
In some embodiments, the object management device may further include: a peripheral interface and at least one peripheral. The processor 701, the memory 702, and the peripheral interfaces may be connected by buses or signal lines. The individual peripheral devices may be connected to the peripheral device interface via buses, signal lines or circuit boards. Illustratively, peripheral devices include, but are not limited to: radio frequency circuitry, touch display screens, audio circuitry, and power supplies, among others.
Of course, the object management device may also include fewer or more components, which the present embodiment is not limited to.
Optionally, the present application further provides a computer readable storage medium having a program stored therein, the program being loaded and executed by a processor to implement the object management method of the above-described method embodiment.
Optionally, the present application further provides a computer product, which includes a computer readable storage medium having a program stored therein, the program being loaded and executed by a processor to implement the object management method of the above-mentioned method embodiment.
The technical features of the above-described embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above-described embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (10)
1. An object management method, the method comprising:
receiving display operation of an object management page, displaying a data configuration page, and configuring target metadata of a target object in the data configuration page; the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
when the object management page is displayed based on the display operation, acquiring target metadata of a target object, wherein the target metadata is obtained through dynamic configuration; the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
rendering page elements in the object management page according to the target metadata;
recording management information in the rendered object management page, wherein the management information is information described by the target metadata;
and sending the management information to a server for data persistence.
2. The method of claim 1, wherein after the sending the management information to the server, further comprises:
receiving a view operation of the management information;
acquiring the management information from the server based on the viewing operation;
and displaying the management information in the rendered object management page.
3. An object management method, the method comprising:
displaying a data configuration page, and configuring target metadata of a target object in the data configuration page; the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
configuring target metadata of a target object in the data configuration page, wherein the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control, and the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types; the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
and sending the target metadata to a server for data persistence, wherein the target metadata is used for rendering page elements in an object management page so as to input management information in the rendered object management page, and the management information is information described by the target metadata.
4. An object management method, the method comprising:
receiving a metadata acquisition request; displaying a data configuration page, and configuring target metadata of a target object in the data configuration page; the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
sending target metadata of a target object to a management end based on the metadata acquisition request, so that the management end renders page elements in an object management page according to the target metadata; the management information is input into the rendered object management page, and the target metadata is obtained by configuring the configuration end in the data configuration page; the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
and receiving and storing the management information sent by the management end, wherein the management information is information described by the target metadata.
5. The method of claim 4, wherein after receiving the management information sent by the management end, the method comprises:
receiving a viewing request sent by the management end, wherein the viewing request is used for requesting to view the management information;
and sending the management information indicated by the viewing request to the management end so that the management end can display the rendered object management page.
6. An object management apparatus, the apparatus comprising:
the operation receiving module is used for receiving the display operation of the object management page, displaying a data configuration page, and configuring target metadata of a target object in the data configuration page; the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
the data acquisition module is used for acquiring target metadata of a target object when the object management page is displayed based on the display operation, wherein the target metadata is obtained through dynamic configuration; the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
the page rendering module is used for rendering page elements in the object management page according to the target metadata;
the information acquisition module is used for inputting management information in the rendered object management page, wherein the management information is information described by the target metadata;
and the information sending module is used for sending the management information to the server side for data persistence.
7. An object management apparatus, the apparatus comprising:
the page display module is used for receiving the display operation of the object management page and displaying a data configuration page, wherein the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
the data configuration module is used for configuring target metadata of a target object in the data configuration page, wherein the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
the data sending module is used for sending the target metadata to a server for data persistence, wherein the target metadata are used for rendering page elements in an object management page so as to input management information in the rendered object management page, and the management information is information described by the target metadata.
8. An object management apparatus, the apparatus comprising:
the request receiving module is used for receiving the metadata acquisition request; displaying a data configuration page, and configuring target metadata of a target object in the data configuration page; the data configuration page comprises an object type data configuration control, an object attribute data configuration control, a data dictionary configuration control and a relation data configuration control;
the data sending module is used for sending target metadata of a target object to a management end based on the metadata acquisition request so that the management end renders page elements in an object management page according to the target metadata; the management information is input into the rendered object management page, and the target metadata is obtained by configuring the configuration end in the data configuration page; the target metadata comprises object type data, object attribute data, a data dictionary corresponding to the object attribute data and relation data between the object types;
and the information receiving module is used for receiving and storing the management information sent by the management end, wherein the management information is information described by the target metadata.
9. An object management apparatus, the apparatus comprising a processor and a memory; the memory has stored therein a program that is loaded and executed by the processor to implement the object management method according to any one of claims 1 to 2; alternatively, the object management method according to claim 3 is implemented; alternatively, the object management method according to claim 4 or 5 is implemented.
10. A computer-readable storage medium, wherein a program is stored in the storage medium, which when executed by a processor is for realizing the object management method according to any one of claims 1 to 2; alternatively, the object management method according to claim 3 is implemented; alternatively, the object management method according to claim 4 or 5 is implemented.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911232577.4A CN111142989B (en) | 2019-12-05 | 2019-12-05 | Object management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911232577.4A CN111142989B (en) | 2019-12-05 | 2019-12-05 | Object management method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111142989A CN111142989A (en) | 2020-05-12 |
| CN111142989B true CN111142989B (en) | 2023-09-08 |
Family
ID=70517683
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911232577.4A Active CN111142989B (en) | 2019-12-05 | 2019-12-05 | Object management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142989B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113938750A (en) * | 2020-06-29 | 2022-01-14 | 阿里巴巴集团控股有限公司 | Video processing method and device, electronic equipment and storage medium |
| CN113220746B (en) * | 2021-05-20 | 2023-07-14 | 支付宝(杭州)信息技术有限公司 | Information verification processing method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108664296A (en) * | 2017-03-31 | 2018-10-16 | 阿里巴巴集团控股有限公司 | A kind of page rendering method and apparatus, a kind of page processing method and device |
| CN108846087A (en) * | 2018-06-12 | 2018-11-20 | 恒生电子股份有限公司 | A kind of page rendering method, apparatus, terminal and server |
-
2019
- 2019-12-05 CN CN201911232577.4A patent/CN111142989B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108664296A (en) * | 2017-03-31 | 2018-10-16 | 阿里巴巴集团控股有限公司 | A kind of page rendering method and apparatus, a kind of page processing method and device |
| CN108846087A (en) * | 2018-06-12 | 2018-11-20 | 恒生电子股份有限公司 | A kind of page rendering method, apparatus, terminal and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111142989A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107798038B (en) | Data response method and data response equipment | |
| CN109308284B (en) | Report menu generation method and device, computer equipment and storage medium | |
| CN107133309B (en) | Method and device for storing and querying process example, storage medium and electronic equipment | |
| CN110569657B (en) | Data access method, device, equipment and storage medium | |
| CN111142989B (en) | Object management method, device and storage medium | |
| CN102135880A (en) | Widget Framework | |
| CN113268260A (en) | Routing method and device for web front end | |
| CN106776638A (en) | Database operation method and device | |
| CN112035555B (en) | Information display method, device and equipment | |
| CN112650804B (en) | Big data access method, device, system and storage medium | |
| CN110989891B (en) | Component deployment method in chart editor, chart editor and related equipment | |
| CN108920642A (en) | Campus information delivery system | |
| CN108600780A (en) | Method for pushed information | |
| JP6946404B2 (en) | Recommended methods, devices, devices and readable storage media based on cloud search | |
| US20100250631A1 (en) | Information processor, electronic file managing device, electronic file managing system, and computer readable medium | |
| CN111858617A (en) | User searching method and device, computer readable storage medium and electronic equipment | |
| CN111045928A (en) | Interface data testing method, device, terminal and storage medium | |
| CN116594834A (en) | Operation and maintenance data processing method and device for multi-protocol server | |
| CN112162731B (en) | Data expansion method, device, storage medium and electronic device | |
| CN114968235A (en) | Page form generation method and device, computer equipment and storage medium | |
| US20210064673A1 (en) | Information processing apparatus and information processing system | |
| CN107729579A (en) | Database separate design method and device | |
| CN113656718A (en) | Theme switching method and device | |
| CN103902148B (en) | Information processing method and electronic devices | |
| CN113900755A (en) | Alarm page processing method and device, computer equipment and readable 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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201117 Address after: Room 708, Ruiqi building, building 11, no.668, Fengting Avenue, Suzhou Industrial Park, Suzhou, Jiangsu Province, 215000 Applicant after: Ruishi (Suzhou) video technology Co.,Ltd. Applicant after: SUZHOU KEDA TECHNOLOGY Co.,Ltd. Address before: 215000 unit 04, floor 13, building a, No. 388, Xinping street, Suzhou Industrial Park, Suzhou City, Jiangsu Province Applicant before: Suzhou Ruiweibo Technology Co.,Ltd. Applicant before: SUZHOU KEDA TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |