CN113806596A

CN113806596A - Operation data management method and related device

Info

Publication number: CN113806596A
Application number: CN202111016106.7A
Authority: CN
Inventors: 赵岳宁
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-08-31
Filing date: 2021-08-31
Publication date: 2021-12-17
Anticipated expiration: 2041-08-31
Also published as: CN113806596B

Abstract

The application provides an operation data management method and a related device, which are used for solving the problems of various operation data and complex and variable management. The operation data management method provided by the application can be suitable for the operation data management platform provided by the embodiment of the application, and the platform can define the material examples without code development. In order to improve the management efficiency of the operation data, in the embodiment of the application, not only one-dimensional data but also multidimensional data are supported to manage the operation data.

Description

Operation data management method and related device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to an operation data management method and a related apparatus.

Background

With the development of communication technology, the internet, a "virtual world", brings great convenience to people's life and work. Many internet products are capable of meeting the user's application needs through a user interface. Such as an online shopping platform, an e-book viewing platform, a short video platform.

As internet data increases, internet services become complex and variable, and the operational data required to manage these services also becomes complex and often requires changes in management. How to conveniently manage operational data is a continuing area of improvement in the industry.

Disclosure of Invention

The embodiment of the application provides an operation data management method and a related device, which are used for solving the problems of various operation data and complex and changeable management in the related technology.

In a first aspect, the present application provides an operation data management method, including:

responding to a request for generating a material instance for a submodel of a target material metadata model, and analyzing the target material metadata model to obtain a first field attribute in the submodel; the first field attribute comprises a first display name and a corresponding first data type;

displaying the first display name in the first field attribute in an instance editing interface;

responding to the adding operation of adding first material data to the first display name, and acquiring material data corresponding to the first data type;

and generating a material instance of the first field attribute of the sub-model based on the corresponding relation between the first field attribute and the first material data for storage.

Optionally, adding the sub-model to the target material metadata model includes:

displaying a first interface of the target material metadata model;

and responding to the user operation of adding the sub-model triggered on the first interface, and associating the sub-model as the sub-model of the target material metadata model.

Optionally, the associating the sub-model as the sub-model of the target material metadata model in response to the user operation of adding the sub-model triggered on the first interface includes:

displaying a second interface in response to the user operation for adding the field triggered on the first interface; the second interface comprises a first operation item and a second operation item, wherein the first operation item is used for customizing the data type of a field to be edited, and the second operation item is used for customizing the model name of the sub-model;

and setting the data type of the field to be edited as a model type and determining the model name of the sub model based on the user operation of the first operation item and the second operation item.

Optionally, the setting the data type of the field to be edited as a model type and determining a model name of the sub model based on the user operation of the first operation item and the second operation item includes:

responding to the selection operation of the model class in the drop-down list of the field to be edited, and determining the data type of the field to be edited as the model class;

displaying an editing control of the model name based on the model class;

and acquiring input characters as the model name of the sub-model based on the input operation of the editing control of the model name.

Optionally, the method further includes:

displaying a model editing interface in response to a request for editing a composite model triggered in the first interface; the model editing interface comprises operation items for customizing field attributes;

determining the field attribute of the sub-model based on the user operation result of the operation item for customizing the field attribute.

Optionally, after the target material metadata model is analyzed to obtain the first field attribute in the sub-model, the method further includes:

displaying a naming control of the first display name on the example editing interface;

obtaining the field name of the first display name based on the field name input by the naming control;

the generating of the material instance of the first field attribute of the sub-model based on the corresponding relationship between the first field attribute and the first material data includes:

and generating a material instance of the first field attribute of the sub-model based on the field name of the first display name and the corresponding relation between the first field attribute and the first material data.

Optionally, the method further includes:

if the sub-model is a list type obtained by analyzing the target material metadata model, an operation item for increasing the field attribute of the sub-model is also displayed in the instance editing interface;

responding to the user operation of the operation item for increasing the field attribute of the submodel to obtain a second field attribute of the submodel; the second field attribute comprises a second display name and a corresponding second data type;

displaying the second display name in the second field attribute in an instance editing interface;

responding to an adding operation of adding second material data to the second display name, and acquiring material data corresponding to the second data type;

and generating a material instance of the second field attribute of the sub-model based on the corresponding relation between the second field attribute and the second material data for storage.

In a second aspect, the present application further provides an operation data management apparatus, including:

the analysis module is configured to execute a request for generating a material instance for a submodel of a target material metadata model, and analyze the target material metadata model to obtain a first field attribute in the submodel; the first field attribute comprises a first display name and a corresponding first data type;

a presentation module configured to perform presentation of the first presentation name in the first field attribute in an instance editing interface;

the acquisition module is configured to execute an adding operation of adding first material data to the first display name, and acquire material data corresponding to the first data type;

a generating module configured to execute generating a material instance of the first field attribute of the sub-model for storage based on a corresponding relationship between the first field attribute and the first material data.

Optionally, the apparatus further comprises:

a sub-model adding module configured to add for the target material metadata model based on:

displaying a first interface of the target material metadata model;

Optionally, the sub-model is associated with the sub-model as a sub-model of the target material metadata model in response to the user operation of adding the sub-model triggered on the first interface, and the sub-model adding module is specifically configured to perform:

Optionally, the user operation based on the first operation item and the second operation item is executed, the data type of the field to be edited is set as a model type, and a model name of the sub model is determined, where the sub model adding module is specifically configured to execute:

displaying an editing control of the model name based on the model class;

Optionally, the apparatus further comprises:

a sub-model field attribute editing module configured to execute a model editing interface in response to a request for editing a composite model triggered in the first interface; the model editing interface comprises operation items for customizing field attributes;

Optionally, after the analyzing the target material metadata model to obtain the first field attribute in the sub-model, the apparatus further includes:

a naming module configured to execute a naming control that exposes the first exposure name at the instance editing interface;

executing the material instance for generating the first field attribute of the sub-model based on the correspondence of the first field attribute and the first material data, the generation module being specifically configured to execute:

Optionally, the apparatus further includes an adding module configured to perform:

In a third aspect, the present application further provides an electronic device, including:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement any of the methods as provided in the first aspect of the application.

In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where instructions, when executed by a processor of an electronic device, enable the electronic device to perform any one of the methods as provided in the first aspect of the present application.

In a fifth aspect, an embodiment of the present application provides a computer program product comprising a computer program that, when executed by a processor, implements any of the methods as provided in the first aspect of the present application.

The technical scheme provided by the embodiment of the application at least has the following beneficial effects:

the operation data management method provided by the application can be suitable for the operation data management platform provided by the embodiment of the application, and the platform can define the material instance without code development. In order to improve the management efficiency of the operation data, in the embodiment of the application, not only one-dimensional data but also multidimensional data are supported to manage the operation data.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, 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 view of an application scenario of an operation data processing method according to an embodiment of the present application;

FIGS. 2 a-2 d are schematic diagrams of a pattern generation interface provided in accordance with an embodiment of the present application;

FIG. 3 is a schematic flowchart illustrating an exemplary one-dimensional material metadata model according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart illustrating an exemplary multidimensional material metadata model according to an embodiment of the present application;

5 a-5 e are schematic page views of a multi-dimensional material metadata model generated according to an embodiment of the present application;

fig. 6 is a flowchart illustrating an operation data management method according to an embodiment of the present application;

fig. 7 is another schematic flow chart of an operation data management method according to an embodiment of the present application;

fig. 8 is a block diagram illustrating an operational data management apparatus according to an example embodiment;

fig. 9 is a schematic structural diagram of an electronic device of an operation data management method according to an exemplary embodiment.

Detailed Description

In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

(1) In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

(2) "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

(3) A server serving the terminal, the contents of the service such as providing resources to the terminal, storing terminal data; the server is corresponding to the application program installed on the terminal and is matched with the application program on the terminal to run.

(4) The terminal device may refer to an APP (Application) of a software class, or may refer to a client. The system is provided with a visual display interface and can interact with a user; is corresponding to the server, and provides local service for the client. For software applications, except some applications that are only run locally, the software applications are generally installed on a common client terminal and need to be run in cooperation with a server terminal. After the development of the internet, more common application programs include short video applications, email clients for receiving and sending emails, and clients for instant messaging, for example. For such applications, a corresponding server and a corresponding service program are required in the network to provide corresponding services, such as database services, configuration parameter services, and the like, so that a specific communication connection needs to be established between the client terminal and the server terminal to ensure the normal operation of the application program.

(5) The material, the material in this application refers to operation type data, for example, a pop-up window advertisement is a material, and this material of the pop-up window advertisement may include a pop-up window attribute, an advertisement picture, an advertisement connection, and the like.

(6) And the material metadata model is used for defining the operation data so as to conveniently manage the operation data.

(7) In the embodiment of the present application, the one-dimensional data refers to material metadata that only includes basic data types such as character strings and numerical values, and is one-dimensional data.

(8) The multidimensional data can not only contain data of basic data types, but also support other complex data types, for example, the multidimensional data is formed by referring to other material metadata models in the material metadata model, as compared with the one-dimensional data.

In view of the complexity and variability of internet services with the increase of internet data in the related art, the management of operation data required for these services becomes complex and variable. In order to improve management efficiency of operation data, embodiments of the present application provide an operation data management method and a related apparatus.

After introducing the design concept of the embodiment of the present application, some simple descriptions are provided below for application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.

Fig. 1 is a schematic view of an application scenario of the operation data management method according to the embodiment of the present application. The application scenario is used for describing an operation data management platform. The operation data management platform may include a plurality of terminal apparatuses 101 and servers 102. The terminal device 101 and the server 102 are connected via a wireless or wired network, and the terminal device 101 includes but is not limited to a desktop computer, a mobile phone, a mobile computer, a tablet computer, a media player, a smart wearable device, a smart television, and other electronic devices. The server 102 may be a server, a server cluster composed of several servers, or a cloud computing center. The server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like.

The operator can customize different materials based on the terminal device 101 and then send the materials to the server 102 for saving. The server 102 stores material instances, and may support a downstream content server (not shown in the figure) to provide internet services, such as an online shopping service, a short video traffic service, an advertisement service, and the like, for a user of the internet services.

In this embodiment, the terminal device 101 may display an operation interface (hereinafter also referred to as a first interface) for defining the material metadata model, and the operator flexibly defines the material metadata model based on the interface and then submits the defined material metadata model to the server 102 for storage. Based on the material metadata model, corresponding business logic can be developed for content servers such as short video platform servers and short video user terminals.

Taking the pop-up advertisement as an example, the operator may define a material metadata model of the pop-up advertisement based on the terminal device 101, and submit the material metadata model to the server 102 for storage. The content server and the content consumer's terminal device may implement corresponding interaction logic and presentation logic based on the material metadata model.

The material metadata model can define field data, and can be nested with another material metadata model to realize the management of multidimensional data by one material metadata model.

To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or figures, more or less operation steps may be included in the method based on the conventional or non-inventive labor. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application.

For convenience of understanding, the content of the material metadata model of the one-dimensional data in the operation platform provided in the embodiment of the present application is introduced first, and then the operation data processing method for implementing the multidimensional data based on the operation platform provided in the embodiment of the present application is described.

First, an operation data management platform realizes a material metadata model as one-dimensional data

As shown in fig. 2a, after the user defines the presentation name and english name of the material metadata model, the unique identification of the material metadata model and the creation time are presented in the model generation interface. The ID in the model generation interface represents a unique identifier of the material metadata model, i.e., a key of the material metadata model. The creation time and the update time in the model generation interface may be automatically generated according to the operation of the operator. So that the material metadata model can be searched for later according to the updating time and the creating time.

In the model generation interface shown in FIG. 2a, definable field attributes are shown in the "Nth column". The field data may include a field key, a presentation name, and a data type. Wherein:

1) and the field key in the field attribute can be customized by an operator or can be automatically generated. The field key is the unique identification of the field in the material metadata model. And ensuring that the field key is unique in the material metadata model.

2) And displaying the name, namely displaying the name of the custom field in the front-end page. The presentation name is used to present the name when instantiating the material metadata model so that the job task knows which field to instantiate.

3) Data type, the definition of data type may be implemented based on a drop down list definition. For example, as shown in the right diagram of fig. 2a, a plurality of data types are available for selection in the expanded drop-down list. The basic data types such as character strings are included, and the types of model types such as "compound models" and "model lists" may also be included.

4) Add +, this control may add some optional attributes, for example, add some common verification means, such as form verification, to the field attribute.

If the field attribute needs to be added, a customizable field attribute can be added to the material metadata model by selecting a control of 'adding blank columns'. After the "add blank column" is selected, the editable content shown in the "nth column" is displayed, which is not described in detail herein.

In an embodiment of the present application, a field data item template is provided, where the template includes a plurality of configured field attributes. To facilitate adding existing field properties, in the model generation interface shown in FIG. 2a, the control "add columns from List configuration template" may be used to add field data in the field data item template, which may reduce the manual editing of field properties.

For management, the field attribute also includes change indication information indicating whether the field attribute can be changed by editing by an operator. For example, the field attributes of the respective defined fields in the settable material metadata model can be edited and modified, and the unique identification of the model automatically generated by the database, the creation time and the update time of the model and the like cannot be edited and modified, so that the confusion of background data is avoided.

In some possible embodiments, a change indication field is provided in the material metadata model to characterize whether the material metadata model can be changed. If the modification indication field of the material metadata model indicates that the attributes of each field in the material metadata model can be modified, as shown in fig. 2b, an operator can modify the attributes of the field of the custom field in the material metadata model in the model generation interface. Changes to field properties may include clicking on the "add +" control shown in FIG. 2b to perform an operation to add a new field property, clicking on the "re-edit" button shown in FIG. 2b to perform an operation to change a field property, and clicking on the "delete" button to delete a field property. Through the operation, the operator can edit the field attribute of the custom field in the material metadata model again, namely, the generated material metadata model is updated.

Based on the above process, the operator can generate the material metadata model for representing various types of operation data through simple interface operation, and can edit the attributes of each field of the material metadata model in the front-end interface.

And after the construction of the material metadata model is completed, instantiating the material metadata model if necessary. The corresponding edited material metadata model may be selected. The background can parse the field attributes of each field in the material metadata model and expose the display names of each field attribute. And adding a corresponding material instance to the custom field in the material metadata model to finish giving material data to the material metadata model. In practice, as shown in fig. 3, first, step 301 is executed: and when the material metadata model is instantiated, acquiring the field attribute in the material metadata model. As described above, the field attribute includes the corresponding relationship between the presentation name and the data type.

Specifically, the field attribute of the custom field of the material instance to be added is obtained. The field attribute may include a display name of the field on the model generation interface and a data type corresponding to the field attribute. The data type is the data type of the material instance to which the field can be added, such as a picture. After the field attribute is obtained, by performing step 302: and displaying the display name in an example editing interface. And providing an instance editing interface for adding the material instance by the operator.

Step 303: and responding to the adding operation of adding the material data to the display name, and acquiring the material data matched with the data type corresponding to the display name so as to realize that an operator adds the corresponding material data to each field attribute in the material metadata model through an example editing interface.

In the embodiment of the present application, a description is given by taking a material for managing pop-up advertisements as an example. As shown in fig. 2c, after the user clicks and saves the display name of the editing material metadata model, i.e., "pop-up advertisement", and the english name, the user can edit the field attribute for the "pop-up advertisement" model in the "model generation interface" shown in fig. 2 c. Two field attributes are provided in fig. 2 c. Wherein, the display name of a field attribute is 'advertisement name', and the data type is character string type. The other field attribute is a display name of 'advertisement cover' and the data type is 'picture file'. An "example editing interface" as shown in FIG. 2c can be obtained by parsing the two field attributes of the "popup advertisement" model. As shown in fig. 2c, the name displayed in the "example editing interface" includes the display name of the first field attribute and the second field attribute, i.e., "ad name" and "ad cover". The user can define a "panda" whose field name is a character string type based on the "advertisement name", and the user can know to select its advertisement cover for the field name "panda" based on the "advertisement cover", and thus select the material data of the picture file type. As shown in fig. 2c, the user clicks the "picture file upload" control, and the interface jumps to the storage address of the picture to facilitate the user to select the picture as a cover page.

It is considered that some contents which do not have practical meaning to the process of adding the material data to the operator may exist in the field attribute of the material metadata model. Such as the "creation time", "update time", etc., described above. To optimize the instance editing interface, presentation indication information that characterizes whether to present or not can be added to the field attributes in the material metadata model.

In some possible embodiments, the presentation information may include a status indication information state for prompting whether to support the presentation of the instance editing interface. When the value of the state is 0, it indicates that the field attribute is not to be displayed by the instance editing interface, and correspondingly, when the value of the state is 1, it indicates that the field attribute can be displayed by the instance editing interface. During implementation, a function of assigning the state indicating information can be provided on the model generation interface, specifically, as shown in fig. 2d, a control for assigning the state indicating information is added beside each field attribute, and setting whether the field attribute is displayed on the instance editing interface can be completed by inputting 0 or 1 into the control. In addition, the custom field attribute is considered to need to add material instances, namely, the custom field attribute has actual meaning to the flow of adding material data. But most of them have no practical meaning are fixed field attributes in the database. Therefore, the specific field attributes such as "creation time", "material name" and the like can be set in advance in the library building stage and cannot be displayed in the instance editing interface.

After the material data corresponding to each field in the material metadata model is obtained, step 304 is executed: and determining and storing a material instance based on the corresponding relation between the material data and the field attribute. Specifically, as shown in the example editing interface shown in fig. 2c, after the field name of "panda" is input, "panda" is associated with the display name of the first field attribute in the model, "advertisement cover" in the field attribute of the picture selected by the user, and "panda" is associated with the picture selected by the user. When the picture is instantiated, only the display name in the field attribute and the data type selected by the user, namely the incidence relation between the panda and the picture selected by the user can be recorded as the material example.

After the material data are added to the field attributes of the respective defined fields in the material metadata model through the process, the corresponding relation between the field attributes in the material metadata model and the material data is analyzed into a material instance, and the material instance is sent to a server side for storage. Specifically, the material data corresponding to each field data in the material metadata can be stored in the database, so that the operator can add the material data without modifying front and back end codes, and only needs to add the corresponding material data to each field attribute of the material metadata model in a front end interface (the example editing interface), thereby realizing the operation and maintenance management of the operation data.

Implementation of two-dimensional and multi-dimensional data

If the operation data management platform only supports one-dimensional data, the function of the operation data management platform is solidified, and the management of complex operation data is difficult to support. Therefore, the embodiment of the application provides an operation data management method. The method provides the function of flexibly defining the multidimensional data. The dimensionality of the data can be customized according to actual requirements, so that the operation data management platform can associate operation data according to actual business requirements. For example, as shown in fig. 4, is a schematic flow chart of the method, which includes the following steps:

in step 401, a first interface of the target material metadata model is presented.

In step 402, in response to a user operation of adding a sub-model triggered on the first interface, associating the sub-model as a sub-model of the target material metadata model.

This first interface is shown in fig. 5a, where the ID in the first interface represents a unique identifier of the target material metadata model, i.e., the key of the material metadata model. The creation time and the update time in the first interface may be automatically generated according to a user operation. In the first interface, by selecting the control of 'adding blank columns', customizable field attributes can be added to the target material metadata model. As shown in the right diagram of fig. 5a, after "add blank column" is selected, a field attribute that "column 4" can be customized is shown, and the field attribute at least may include:

1) and the field key in the field attribute can be customized by an operator or can be automatically generated. The field key is the unique identifier of the field and is only required to be in the target material metadata model.

2) The display name is the display name of the user-defined field of the operator, so that when material data are added to the field, the operator can conveniently identify which field the material data are added to. Note that the display name here is not a field name, and when material data is added subsequently, an operator can customize the field name according to the display name. As shown in fig. 5e, the "name" and the "cover" are both display names, and the user can customize the field name.

3) Data type, the definition of data type may be implemented based on a drop down list definition. For example, as shown in the right diagram of fig. 5a, a plurality of data types are available for selection in the expanded drop-down list. The basic data types such as character strings are included, and the types of model types such as "compound models" and "model lists" may also be included. The model list may be used for the operator to expand the corresponding field attribute as required, for example, the field attribute of the sub-model may be added in the instance editing interface shown in fig. 5e for an unlimited number of times. The compound model is used for defining a model, and field properties cannot be added in an instance editing interface.

4) Add +, this control may add some optional field attributes, such as whether the data validation mode is form validation or other validation modes, etc.

In addition, the role of the control "add column from list configuration template" in the first interface has been explained above, and is not described here.

And configuring the sub-model in the first interface, namely configuring the field attribute of the custom sub-model. The configuration of the field attribute of the submodel can also configure the submodel, thereby realizing the more deep multidimensional data. I.e. submodels in which submodels can also be nested.

In a first interface of the target material metadata model, if the data type is defined as a model class, a sub-model can be associated with the target material metadata model. The number of sub-models that can be associated is not limited, and the association of any number of sub-models into the target material metadata model can be achieved through the "add blank column" control in fig. 5 a.

It should be noted that, when implemented, the specific implementation manner of the first interface may be set according to actual requirements, and fig. 5a is only an example.

Based on the above description, it can be summarized as adding a sub-model to the target material metadata model based on the following manner, such as first displaying a second interface in response to a user operation for adding a field triggered on the first interface; the second interface comprises a first operation item and a second operation item, wherein the first operation item is used for customizing the data type (the type of a model class in the embodiment of the application is a composite model and a model list) of a field to be edited, and the second operation item is used for customizing the model name of the sub-model; therefore, based on the user operation of the first operation item and the second operation item, the data type of the field to be edited can be set as a model type, and the model name of the sub model can be determined.

Therefore, multidimensional data can be realized through simple interface operation, and the flexibility of the data operation platform on data dimension management is expanded.

In some embodiments, to facilitate associating sub-models for the target material metadata model, an edit control for the class name may also be presented after the operator selects a data type for a model class (e.g., a model list). And the editing control of the class name can support the operator to define the name of the sub-model.

Assuming that the specific class of the selected model is a model list (shown in the first step in fig. 5 b), the "add +" control (shown in the second step in fig. 5 b) may be continuously selected, the control may call up a drop-down list (not shown in fig. 5 b), and an item for defining the class name may be selected from the drop-down list. Accordingly, as shown in FIG. 5b, the input box next to the attribute "model selection" can be used to customize the name of the sub-model. Of course, in another embodiment, the input box may be implemented as a custom sub-model name, and may also provide a drop-down list of the constructed material metadata model for the operator to select the constructed model as the sub-model of the target material metadata model.

In one embodiment, assuming that a user needs to define a sub-model in the target material metadata model, it may be implemented to present a model editing interface in response to a request for editing the composite model triggered in the first interface; the model editing interface comprises operation items for customizing the field attribute; then, the field attribute of each field in the submodel is determined in response to the user operation result of the operation item of the model editing interface for customizing the field attribute.

For example, it may be implemented as shown in fig. 5b, to perform a third step to enable selection of "sub-model configuration", trigger a request for editing a sub-model, and then enter a model editing interface as shown in fig. 5 c.

The model editing interface is similar to the first interface of the target material metadata model, and the field attribute can be added according to the requirement. As shown in fig. 5c, wherein:

the model name: the name of the sub-model can be customized by a text edit box beside the model name. As the user enters the model name, the model name is presented with a different presentation above it than the font in the input box. And with the synchronous display of the input, for example, the Button is synchronously displayed above the input, and when the Button is input, the Button is synchronously displayed above the input. The name of the submodel thus obtained is Button.

Configuration: the definition of field properties in the submodel is increased by configuring the side "+ add" control. For example, in the right diagram of fig. 5c, it is assumed that two field attributes are added, the presentation name of one field is "button copy" and the presentation name of the other field is "jump link". The "+ add" control in each field property editing region is identical to the "add + control" in the field property editing region in fig. 5a, and is not described here again.

Adding a model: the sub-model can be added through the control.

Therefore, the operator can add any number of sub models in the target material metadata model.

After customizing the target material metadata model of the embedded sub-model, material data can be added to facilitate instantiation of the model. May be implemented as the steps shown in fig. 6:

in step 601: responding to a request for generating a material instance for a submodel of a target material metadata model, and analyzing the target material metadata model to obtain a first field attribute in the submodel; the first field attribute comprises a first display name and a corresponding first data type.

In step 602: and displaying the first display name in the first field attribute in an instance editing interface.

In step 603: and responding to the adding operation of adding the first material data to the first display name, and acquiring the material data corresponding to the first data type.

In step 604: and generating a material instance of the first field attribute of the sub-model based on the corresponding relation between the first field attribute and the first material data for storage.

If the naming control of the first display name is displayed on the example editing interface; then, based on the field name input by the naming control, the field name of the first display name is obtained, instantiation of the first display name is completed, and then based on the field name of the first display name, the corresponding relation between the first field attribute and the first material data, a material example of the first field attribute of the sub-model is generated. Therefore, the field name is obtained through the display name in one field data, the material data corresponding to the field name is obtained through the added material data, and the instantiation of the field attribute is completed.

The description is continued by taking the field attributes of the submodel defined in fig. 5c as an example. As shown in FIG. 5c, two fields of the presentation name are defined, namely "button copy" and "jump link", respectively. Assuming further that the target material metadata model name is "pop-up" then an example editing interface for adding material data is shown in fig. 5 d. In fig. 5d, the name "pop-up" of the target material metadata model is shown and the presentation name of the two basic fields of the target material metadata model is shown, including the name and the cover page. The operator can customize the name, for example, the name is customized as a pop-up window a advertisement, and can also select a corresponding cover picture for the cover.

In another embodiment, the list-type submodel may extend the field input of the submodel when instantiating the submodel according to actual needs, and may be implemented as shown in fig. 7:

in step 701, for a list-type submodel, an operation item for adding a field attribute of the submodel is also displayed in the instance editing interface;

in step 702, in response to the user operation on the operation item for adding the field attribute of the submodel, obtaining a second field attribute of the submodel; the second field attribute comprises a second display name and a corresponding second data type;

in step 703, displaying the second display name in the second field attribute in an instance editing interface;

in step 704, in response to an adding operation of adding second material data to the second display name, material data corresponding to the second data type is obtained;

in step 705, a material instance of the second field attribute of the sub-model is generated and stored based on the corresponding relationship between the second field attribute and the second material data.

For example, continuing with the example of FIG. 5d, the "button list" in the left diagram of FIG. 5d is the class name of the sub-model. Since the data type of the sub-model is a model list, an "add +" control is displayed, and an operator clicks the control to display the display names of the fields in the sub-model, such as a "button pattern" and a "jump link" shown in the right diagram in fig. 5 d. The method is used for customizing the field name in the button file as 'robbing red envelope', and adds a corresponding link for robbing the red envelope to the displayed jump link. Since the submodel is a model list, the operator can add the field attribute of the submodel by using the "add +" control shown in the right diagram in fig. 5 d. For example, as shown in fig. 5e, a set of "button documents" and "jump links" is added, and the operator may define the newly added "button documents" as "inviting friends", and the newly added jump links as links for inviting friends. Thus, although field attributes are defined only once for the submodel in fig. 5c, these field attributes may be repeatedly added as needed to improve the management function of the multidimensional data.

Based on the same inventive concept, the present application further provides an operation data management apparatus, as shown in fig. 8, where the apparatus 800 includes:

an analysis module 801 configured to execute a request for generating a material instance for a sub-model of a target material metadata model, and analyze the target material metadata model to obtain a first field attribute in the sub-model; the first field attribute comprises a first display name and a corresponding first data type;

a presentation module 802 configured to perform presenting the first presentation name in the first field attribute in an instance editing interface;

an obtaining module 803, configured to perform an adding operation of adding first material data to the first display name, and obtain material data corresponding to the first data type;

a generating module 804 configured to execute generating, based on the correspondence between the first field attribute and the first material data, a material instance of the first field attribute of the sub-model for storage.

Optionally, the apparatus further comprises:

displaying a first interface of the target material metadata model;

displaying an editing control of the model name based on the model class;

Optionally, the apparatus further comprises:

Having described the world operations data management method and apparatus of the exemplary embodiments of the present application, an electronic device according to another exemplary embodiment of the present application is next described.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

In some possible implementations, an electronic device according to the present application may include at least one processor, and at least one memory. Wherein the memory stores program code which, when executed by the processor, causes the processor to perform the operational data management method according to various exemplary embodiments of the present application described above in this specification. For example, the processor may perform steps as in an operational data management method.

The electronic device 130 according to this embodiment of the present application is described below with reference to fig. 9. The electronic device 130 shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 9, the electronic device 130 is represented in the form of a general electronic device. The components of the electronic device 130 may include, but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 that connects the various system components (including the memory 132 and the processor 131).

Bus 133 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.

The memory 132 may include readable media in the form of volatile memory, such as Random Access Memory (RAM)1321 and/or cache memory 1322, and may further include Read Only Memory (ROM) 1323.

Memory 132 may also include a program/utility 1325 having a set (at least one) of program modules 1324, such program modules 1324 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), with one or more devices that enable a user to interact with the electronic device 130, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur via input/output (I/O) interfaces 135. Also, the electronic device 130 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as memory 132 comprising instructions, executable by processor 131 to perform the above-described operational data management method is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, comprising a computer program which, when executed by the processor 131, implements any of the operational data management methods as provided herein.

In an exemplary embodiment, various aspects of an operation data management method provided by the present application may also be implemented in the form of a program product, which includes program code for causing a computer device to perform the steps in the operation data management method according to various exemplary embodiments of the present application described above in this specification when the program product runs on the computer device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for operating the data management method of the embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on an electronic device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device and partly on a remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic devices may be connected to the consumer electronic device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external electronic device (e.g., through the internet using an internet service provider).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.

Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable image scaling apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable image scaling apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable image scaling device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer implemented process such that the instructions which execute on the computer or other programmable device provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An operational data management method, the method comprising:

2. The method of claim 1, wherein adding the sub-model to the target material metadata model comprises:

displaying a first interface of the target material metadata model;

3. The method of claim 2, wherein associating the sub-model as a sub-model of the target material metadata model in response to a user action to add the sub-model triggered at the first interface comprises:

4. The method of claim 3, wherein the setting the data type of the field to be edited as a model class and determining the model name of the sub-model based on the user operation of the first operation item and the second operation item comprises:

displaying an editing control of the model name based on the model class;

5. The method according to any one of claims 2-4, further comprising:

6. The method of claim 1, wherein after parsing the target material metadata model for the first field attribute in the sub-model, the method further comprises:

7. An operational data management apparatus, the apparatus comprising:

8. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the operational data management method of any of claims 1-6.

9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the operational data management method of any of claims 1-6.

10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the operational data management method of any one of claims 1-6.