CN113806596B

CN113806596B - Operation data management method and related device

Info

Publication number: CN113806596B
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: 2024-04-16
Anticipated expiration: 2041-08-31
Also published as: CN113806596A

Abstract

The application provides an operation data management method and a related device, which are used for solving the problems of multiple operation data and complex and changeable management. The operation data management method provided by the application can be applied to the operation data management platform provided by the embodiment of the application, and the platform can realize definition of the material examples without code development. In order to facilitate improvement of management efficiency of operation data, in the embodiment of the present application, operation data is managed by supporting not only one-dimensional data but also multidimensional data.

Description

Operation data management method and related device

Technical Field

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

Background

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

As internet data increases, internet services become complex and variable, so too does the operational data required to manage these services and often requires changes in the manner of management. And how to conveniently manage the operation data has been an aspect of continuous 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 complex operation data and complex and changeable management in related technologies.

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

responding to a request for generating a material instance for a sub-model of a target material metadata model, and analyzing 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;

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

responding to an 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, and storing the material instance.

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 user operation of adding the sub-model triggered at the first interface, and associating the sub-model as a sub-model of the target material metadata model.

Optionally, the responding to the user operation of adding the sub-model triggered at the first interface associates the sub-model as the sub-model of the target material metadata model includes:

responding to user operation for adding fields triggered on the first interface, and displaying a second 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 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.

Optionally, 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 includes:

responding to the selection operation of model classes in a drop-down list of a 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 based on the input operation of the editing control of the model name, acquiring the input characters as the model name of the sub model.

Optionally, the method further comprises:

responding to a request for editing the composite model triggered in the first interface, and displaying a model editing interface; the model editing interface comprises an operation item 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 parsing the target material metadata model to obtain the first field attribute in the sub-model, the method further includes:

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

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

the generating the material instance of the first field attribute of the sub model based on the correspondence 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 comprises:

if the sub model is a list type after analyzing the target material metadata model, an operation item for adding 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 adding the field attribute of the sub-model, and obtaining a second field attribute of the sub-model; 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 on an instance editing interface;

responding to an adding operation of adding second material data to the second display name, and obtaining 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, and storing the material instance.

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

a parsing module configured to perform parsing of a target material metadata model to obtain a first field attribute in a sub-model of the target material metadata model in response to a request to generate a material instance for the sub-model; the first field attribute comprises a first display name and a corresponding first data type;

A presentation module configured to execute presentation of the first presentation name in the first field attribute at an instance editing interface;

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

and the generation module is configured to execute the generation of the 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, the apparatus further includes:

a sub-model addition module configured to add to the target material metadata model based on the following method:

displaying a first interface of the target material metadata model;

Optionally, executing the user operation of adding a sub-model triggered in response to the first interface, associating the sub-model as a sub-model of the target material metadata model, and the sub-model adding module is specifically configured to execute:

Optionally, executing the user operation based on the first operation item and the second operation item, setting the data type of the field to be edited as a model class and determining a model name of the sub-model, and 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 includes:

a sub-model field property 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 an operation item for customizing field attributes;

Optionally, after the parsing 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 exposed name at the instance editing interface;

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

Optionally, the apparatus further comprises 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 present application.

In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform any 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 which, 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 brings the following beneficial effects:

the operation data management method provided by the application can be applied to the operation data management platform provided by the embodiment of the application, and the platform can realize definition of the material examples without code development. In order to facilitate improvement of management efficiency of operation data, in the embodiment of the present application, operation data is managed by supporting not only one-dimensional data but also multidimensional 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 that are needed in the embodiments of the present application will be briefly described below, and it is obvious that the drawings that are described below are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is an application scenario schematic diagram of an operation data processing method provided in an embodiment of the present application;

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

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

FIG. 4 is a flow chart of an exemplary multidimensional metadata model in accordance with one embodiment of the present application;

FIGS. 5 a-5 e are schematic diagrams of a page for generating a multi-dimensional metadata model according to an embodiment of the present application;

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

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

FIG. 8 is a block diagram of an operational data management device, according to an example embodiment;

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

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present application, 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 the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be implemented in other sequences than those illustrated or otherwise described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

In the following, some terms in the embodiments of the present application are explained for easy understanding by those skilled in the art.

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

(2) "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

(3) The server is used for serving the terminal, and the content of the service provides resources for the terminal and stores the terminal data; the server corresponds to the application program installed on the terminal and operates in cooperation with the application program on the terminal.

(4) The terminal device may refer to APP (Application) of a software class or a client. The system has a visual display interface, and can interact with a user; corresponding to the server, providing local service for clients. Applications for software classes, except some applications that only run locally, are typically installed on a common client terminal, and need to run in conjunction with a server. After the development of the internet, more commonly used application programs include, for example, short video applications, email clients when receiving email, and clients for instant messaging. For this type of application program, there is a need to have a corresponding server and service program in the network to provide a corresponding service, such as a database service, a configuration parameter service, etc., 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 in the application refers to operation type data, for example, a popup advertisement is a material, and the popup advertisement can include popup attribute, advertisement picture, advertisement connection and the like.

(6) And the material metadata model is used for defining operation data so as to facilitate management of 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) Multidimensional data, in contrast to one-dimensional data, may not only contain data of a basic data type, but also support other complex data types, for example, multidimensional data is formed by referencing other material metadata models in the material metadata model.

In view of the fact that the internet services are complex and variable with the increase of internet data in the related art, management of operation data required for these services becomes complex and variable. In order to improve management efficiency of operation data, an embodiment of the application provides an operation data management method and a related device.

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

Referring to fig. 1, an application scenario diagram of an operation data management method provided in an embodiment of the present application is shown. The application scenario is used to describe an operational data management platform. The operation data management platform may include a plurality of terminal devices 101 and a server 102. The terminal device 101 and the server 102 are connected through a wireless or wired network, and the terminal device 101 includes, but is not limited to, electronic devices such as a desktop computer, a mobile phone, a mobile computer, a tablet computer, a media player, an intelligent wearable device, and an intelligent television. Server 102 may be a server, a server cluster formed by a plurality of 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 cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligence platforms, 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 storage. The server 102 stores material instances and may support a downstream content server (not shown) to provide internet services, such as an online shopping service, a short video traffic service, an advertisement service, etc., to users of the internet services.

In this embodiment of the present application, the terminal device 101 may display an operation interface (hereinafter also referred to as a first interface) for defining a material metadata model, and the operator may flexibly customize the material metadata model based on the interface and submit the customized material metadata model to the server 102 for saving. 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 popup advertisement as an example, an operator may define a material metadata model of the popup advertisement based on the terminal device 101 and submit the material metadata model to the server 102 for storage. The content server and the terminal devices of the content consumers can implement corresponding interaction logic and presentation logic based on the material metadata model.

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

In order to further explain the technical solutions provided in the embodiments of the present application, the following details are described with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operational steps as shown in the following embodiments or figures, more or fewer operational steps may be included in the method, either on a routine or non-inventive basis. In steps where there is logically no necessary causal relationship, the execution order of the steps is not limited to the execution order provided by the embodiments of the present application.

For easy understanding, the content of the material metadata model of the one-dimensional data in the operation platform provided by the embodiment of the application is described first, and then the operation data processing method based on the operation platform for realizing the multi-dimensional data provided by the embodiment of the application is described.

1. Operation data management platform for realizing 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 identification 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 operations of the operator. So that the material metadata model can be searched according to the update time and the creation time at a later stage.

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

1) The field key in the field attribute can be customized by operators or can be automatically generated. The field key is the unique identification of the field in the material metadata model. 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 names are presented for instantiating the names presented when the material metadata model so that the operator task knows which field to instantiate.

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

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

If the field attribute needs to be added, a customizable field attribute can be added to the material metadata model by selecting the control of adding blank columns. After selecting "add blank column", the editable content as shown in "nth column" is presented, and will not be described here.

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 attributes, in a model generation interface such as that shown in FIG. 2a, the field data in the field data item template may be added using the "Add column from List configuration template" control, which may reduce the operations of manually editing field attributes.

For convenience of management, the field attribute also comprises change indication information for indicating whether the field attribute can be edited and modified by operators. For example, field attributes of respective defined fields in the settable material metadata model can be edited and modified, while unique identification of the model automatically generated by the database, creation time, update time, and the like of the model cannot be edited and modified to avoid confusion of the background data.

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

Based on the above flow, an operator can generate a material metadata model for representing various operation data through simple interface operation, and edit the field properties of the material metadata model in the front-end interface.

After the construction of the material metadata model is completed, if the material metadata model needs to be instantiated. The corresponding edited material metadata model may be selected. The background can analyze the field attributes of each field in the material metadata model and display the display names of the field attributes. And adding a corresponding material instance to a custom field in the material metadata model to finish giving material data to the material metadata model. In practice, as shown in fig. 3, step 301 is first performed: when the material metadata model is instantiated, field attributes in the material metadata model are obtained. As described above, the field attribute includes a correspondence between the presentation name and the data type.

Specifically, a field attribute of a custom field of the material instance to be added is obtained. The field attribute may include a presentation name of the field at the model generation interface and a data type corresponding to the field attribute. The data type is the data type of the material instance added by the field, such as a picture. After the field attributes are obtained, by executing step 302: the display name is displayed in an instance editing interface. To provide an instance editing interface for operators to add material instances.

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 operators add the corresponding material data for each field attribute in the material metadata model through an example editing interface.

In the embodiment of the present application, a material for managing pop-up advertisements is described as an example. As shown in fig. 2c, after the user edits the material metadata model with the display name "popup advertisement" and the english name click save, the user may edit the field attribute for the "popup advertisement" model in the "model generation interface" shown in fig. 2 c. Two field attributes are provided in fig. 2 c. The display name of one field attribute is an advertisement name, and the data type is a character string type. Another field attribute is shown with a name of "advertisement cover" and a data type of "picture file". An "instance editing interface" as shown in FIG. 2c can be obtained by parsing the two field properties of this model of "popup advertisement". As shown in fig. 2c, in the "instance editing interface", the displayed names include the displayed names of the first field attribute and the second field attribute, that is, "advertisement name" and "advertisement cover". The user can define "pandas" whose field name is a character string based on the "advertisement name", and the user can know that his advertisement cover is to be selected for the field name "pandas" based on the "advertisement cover", so that the material data of the picture file type is selected. 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's selection of the picture as a cover.

Considering that there may be some content in the field attribute of the material metadata model that does not have a practical meaning for the procedure of adding material data to an operator. Such as "creation time", "update time", etc., as described above. To optimize the instance editing interface, presentation indication information characterizing whether presentation is possible or not can be added to 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 instance editing interface presentation. When the state value is 0, the field attribute is indicated not to be displayed by the instance editing interface, and when the state value is 1, the field attribute is indicated to be displayed by the instance editing interface. In implementation, a function of assigning state indication information can be provided in the model generation interface, specifically, as shown in fig. 2d, a control for assigning state indication information is added beside each field attribute, and setting whether the field attribute is displayed in the instance editing interface can be completed by inputting 0 or 1 into the control. In addition, the fact that the custom field attributes are required to be added with material examples is considered, namely, the process of adding material data has practical meaning. What does not have a true meaning is the fixed field attributes in the database. Therefore, the field attributes such as "creation time", "material name" and the like can be set in advance in the library establishment stage and are not shown in the instance editing interface.

After acquiring the material data corresponding to each field in the material metadata model, 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 an example editing interface shown in fig. 2c, after a field name of "panda" is input, the "panda" is associated with a display name of a first field attribute in the model, and a picture selected by a user may be associated with an "advertisement cover" in the field attribute, and the "panda" is associated with a picture selected by the user. At the time of instantiation, only the association relationship between the presentation name in the field attribute and the data type selected by the user, namely, "pandas" and the picture selected by the user, may be recorded as a material instance.

After the addition of the material data to the field attributes of the respective definition fields in the material metadata model is completed through the flow, 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 for storage. Specifically, the material data corresponding to each field data in the material metadata can be stored in the database, so that an operator does not need to modify front-end and back-end codes to add the material data, 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.

2. Implementation of multidimensional data

If the operation data management platform only supports one-dimensional data, the functions of the operation data management platform are solidified, and the management of complex operation data is difficult to support. Accordingly, the embodiment of the application provides an operation data management method. The method provides the function of flexibly defining the multidimensional data. The dimension of the data can be customized according to the actual demand, so that the operation data management platform can correlate the operation data according to the actual service demand. For example, as shown in fig. 4, a flow chart of the method includes the following steps:

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

In step 402, in response to a user operation triggered at the first interface to add a sub-model, the sub-model is associated as a sub-model of the target material metadata model.

The first interface is shown in fig. 5a, where the ID in the first interface represents a unique identification of the target material metadata model, i.e. a 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 selecting "add blank column", the field attribute customizable by "column 4" is displayed, and the field attribute may at least include:

1) The field key in the field attribute can be customized by operators or can be automatically generated. The field key is the unique identification of the field, and is unique in the target material metadata model.

2) And the display name of the field is customized by operators, so that when the material data is added to the field, the operators can conveniently identify which field the material data is added to. Note that the presentation name here is not a field name, and the operator can customize the field name according to the presentation name when material data is added later. As in fig. 5e, "name" and "cover" are both presentation names, and the user can customize the field names.

3) The definition of data type may be implemented as a drop down list based definition. For example, as shown in the right-hand diagram of fig. 5a, there are a number of data types available for selection in the expanded drop-down list. Including basic data types such as character strings, and model classes such as "compound models" and "model lists". The model list may be used for operators to expand the corresponding field attribute according to the requirement, for example, the field attribute of the sub-model may be infinitely increased in the example editing interface as shown in fig. 5 e. The composite model is used to define a model, and field attributes cannot be added in the 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 is described above, and will not be described here again.

The configuration of the sub-model in the first interface, namely, the configuration of the field attribute of the custom sub-model is realized. The sub-model field attribute configuration can also configure the sub-model, so that more deep multidimensional data is realized. I.e. sub-models can also be nested in the sub-model.

In the first interface of the target material metadata model, if the defined data type is a model class, a sub-model may be associated for 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 accomplished through the "increase blank column" control in FIG. 5 a.

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

Based on the above description, it may be summarized as adding a sub-model to a target material metadata model based on implementation such as first exposing a second interface in response to a user operation triggered at the first interface to add a field; 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 (type of model class such as a composite model and a model list in the embodiment of the application) of the field to be edited, and the second operation item is used for customizing the model name of the sub-model; thus, based on the user operations 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 class 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 for data dimension management is expanded.

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

Assuming that the specific class of model class selected is a model list (as shown in step (1) of fig. 5 b), the "add+" control (as shown in step (2) of fig. 5 b) may be continued to be selected, which may bring up a drop down list (as not shown in fig. 5 b) from which an item may be selected for defining the class name. Accordingly, as shown in FIG. 5b, an input box next to the attribute "model select" may be provided for customizing the name of the sub-model. Of course, in another embodiment, the input box may be implemented to customize the name of the sub-model, 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 the user needs to define a sub-model in the target material metadata model, this may be implemented to expose a model editing interface in response to a request to edit the composite model triggered in the first interface; the model editing interface comprises an operation item for customizing field attributes; then, in response to a user operation result of an operation item for customizing the field attribute of the model editing interface, determining the field attribute of each field in the sub model.

For example, as shown in fig. 5b, step (3) may be performed to enable selection of a "submodel configuration", trigger a request for editing a submodel, and then enter the 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 field attributes can be added as required. As shown in fig. 5c, wherein:

model name: the name of the sub-model can be customized through a text edit box next to the model name. The model name is presented with a presentation effect different from the font in the input box above the model name as the user inputs the model name. And with the synchronous display of the input, for example, the input Button, the Button is synchronously displayed above the input Button, and when the input Button is completed, the Button is synchronously displayed above the input Button. The name of the submodel is thus given to Button.

Configuration: the definition of field properties in the sub-model is increased by configuring the side "+ Add" control. For example, in the right-hand side of fig. 5c, it is assumed that two field attributes are added, one field having a presentation name of "button document" and the other field having a presentation name of "jump link". The "+Add" control in each field property editing area is identical to the "Add+control" in the field property editing area of FIG. 5a and will not be described again here.

Adding a model: through which sub-models can be added.

Thus, an operator may implement adding any number of sub-models to the target material metadata model.

After the target material metadata model of the embedded sub-model is customized, material data may be added to facilitate instantiation of the model. The steps shown in fig. 6 can be implemented:

in step 601: responding to a request for generating a material instance for a sub-model of a target material metadata model, and analyzing 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.

In step 602: and displaying the first display name in the first field attribute in an example 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, and storing the material instance.

A naming control for displaying the first display name on the instance editing interface; then, based on the field name input by the naming control, obtaining the field name of the first display name, completing the instantiation of the first display name, and then 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 based on the field name of the first display name. Thus, the field name is obtained from the field data through the display name, and the material data corresponding to the field name is obtained through the added material data, so that the instantiation of the field attribute is completed.

The description will be continued taking as an example the field properties of the sub-model defined in fig. 5 c. As shown in fig. 5c, the presentation names of the two fields are defined, respectively "button text" and "jump link". Further assume that the target material metadata model name is "popup advertisement", and an example editing interface for adding material data is shown in fig. 5 d. The name "popup advertisement" of the target material metadata model is shown in fig. 5d and the presentation names of the two basic fields of the target material metadata model are shown, including the name and the cover. Operators can customize the names, such as popup window A advertisements, and can select corresponding cover pictures for the covers.

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

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

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

in step 703, the second presentation name in the second field attribute is presented in an instance editing interface;

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

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

For example, continuing with the example of FIG. 5d, the "button list" in the left-hand diagram of FIG. 5d is the class name of the child 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 names of various fields in the sub-model, such as "button text" and "jump link" shown in the right diagram in fig. 5 d. The method is used for customizing a field name of the button text, namely 'go to rob red packets', and adding corresponding links for rob red packets to displayed jump links. The sub-model is a model list, so that an operator can increase field attributes of the sub-model through an 'add +' control shown in a right diagram in fig. 5 d. For example, as shown in fig. 5e, a set of "button text" and "jump links" may be added, and the operator may define the newly added "button text" as "invite friends", and the newly added jump links as links for inviting friends. Thus, although field attributes are defined only once for the sub-model in fig. 5c, these field attributes may be repeatedly added as needed to improve the management function of the multi-dimensional data.

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

a parsing module 801 configured to perform parsing of a target material metadata model to obtain a first field attribute in a sub-model of the sub-model in response to a request to generate a material instance for the sub-model; the first field attribute comprises a first display name and a corresponding first data type;

a presentation module 802 configured to execute presenting the first presentation name in the first field attribute at 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 is configured to perform generating a material instance of the first field attribute of the sub model based on the correspondence between the first field attribute and the first material data for storage.

Optionally, the apparatus further includes:

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 includes:

Having described the method and apparatus for managing border operation data according to exemplary embodiments of the present application, next, an electronic device according to another exemplary embodiment of the present application is described.

Those skilled in the art will appreciate that the various aspects of the present application may be implemented as a system, method, or program product. Accordingly, aspects of the present application may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may 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. The memory stores therein program code that, when executed by the processor, causes the processor to perform the operational data management methods described above in this specification according to various exemplary embodiments of the present application. For example, the processor may perform steps as in an operational data management method.

An 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 merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present application.

As shown in fig. 9, the electronic device 130 is embodied in the form of a general-purpose electronic device. Components of 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 connecting the various system components, including the memory 132 and the processor 131.

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

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 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include 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.), one or more devices that enable a user to interact with the electronic device 130, and/or any device (e.g., router, modem, etc.) that enables the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur through an input/output (I/O) interface 135. Also, electronic device 130 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 130, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

In an exemplary embodiment, a computer readable storage medium is also provided, such as a memory 132, comprising instructions executable by the processor 131 to perform the above-described operational data management method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, 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 methods of operational data management as provided herein.

In an exemplary embodiment, aspects of an operation data management method provided in the present application may also be implemented in the form of a program product including a 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 as described above when the program product is run 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. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk 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 code 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.

The readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. 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 of the foregoing. 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, partly on the remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic device 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., connected 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 a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the elements described above may be embodied in one element in accordance with embodiments of the present application. Conversely, the features and functions of one unit described above may be further divided into a plurality of units to be embodied.

Furthermore, although the operations of the methods of the present application are depicted in the drawings in a particular order, this is not required to or suggested that these operations must be performed in this particular order or that all of the illustrated operations must be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform.

It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling device, 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 device 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 apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While 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. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A method of operation data management, the method comprising:

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, and storing the material instance;

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

Displaying a first interface of the target material metadata model;

responding to user operation triggered at the first interface and added with a sub-model, and associating the sub-model as a sub-model of the target material metadata model;

the responding to the user operation of adding the sub-model triggered at the first interface, the sub-model is associated as the sub-model of the target material metadata model, and the method comprises the following steps:

2. The method of claim 1, 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;

3. The method according to any one of claims 1-2, wherein the method further comprises:

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

5. A method according to claim 3, characterized in that the method further comprises:

6. An operation data management apparatus, characterized in that the apparatus comprises:

a generation module configured to perform generation of a material instance of the first field attribute of the sub model based on a correspondence between the first field attribute and the first material data for storage;

the apparatus further comprises:

Displaying a first interface of the target material metadata model;

executing the user operation of adding a sub-model in response to the trigger at the first interface, associating the sub-model as a sub-model of the target material metadata model, the sub-model adding module being specifically configured to execute:

7. The apparatus of claim 6, wherein performing the user operation based on the first operation item and the second operation item sets a data type of the field to be edited as a model class and determines a model name of the sub-model, the sub-model addition module being specifically configured to perform:

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

8. The apparatus according to any one of claims 6-7, wherein the apparatus further comprises:

9. The apparatus of claim 6, wherein after parsing the target material metadata model to obtain the first field attribute in the sub-model, the apparatus further comprises:

10. The apparatus of claim 8, further comprising an augmentation module configured to perform:

11. 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-5.

12. A computer readable storage medium, characterized in that 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 according to any one of claims 1-5.