阅读说明：本技术 一种运营数据处理方法及相关装置 (Operation data processing method and related device ) 是由 赵岳宁 于 2021-08-31 设计创作，主要内容包括：本申请实施例提供一种运营数据处理方法及相关装置,本申请实施例预先构建允许用户添加自定义字段的素材元数据模型。前端界面可基于该模型对应的数据库表生成用于对该模型编辑的表单。用户可通过在前端界面中对该模型进行自定义字段的添加或删改。由于一个素材元数据模型即可定义为一类运营数据,运营人员仅通过前端界面即可对运营数据进行自由的扩展、删改。通过上述流程对运营数据进行添加删改时无需对前后端执行编码操作,降低了运营成本。(The embodiment of the application provides an operation data processing method and a related device. The front-end interface may generate a form for editing the model based on the database table to which the model corresponds. The user can add or delete the custom field to the model in the front-end interface. Because one material metadata model can be defined as a type of operation data, the operation personnel can freely expand and delete the operation data only through a front-end interface. When the operation data is added and deleted through the process, the front end and the back end do not need to be coded, and the operation cost is reduced.)

1. An operational data processing method, characterized in that the method comprises:

when the material metadata model is instantiated, the field attribute in the material metadata model is obtained; wherein, the field attribute comprises the corresponding relation between the display name and the data type;

displaying the display name in an example editing interface;

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

and determining and storing a material instance based on the corresponding relation between the material data and the field attribute.

2. The method of claim 1, wherein generating the field attributes of the material metadata model comprises:

displaying a model generation interface, wherein the model generation interface comprises operation items for defining the field attribute;

and responding to the user operation of the operation item for defining the field attribute to obtain the field attribute of the material metadata model.

3. The method according to claim 2, wherein before the field attribute of the material metadata model is obtained in response to the user operation on the operation item for defining the field attribute, the method further comprises:

displaying a naming control of the material metadata model in the model generation interface;

and taking the input characters as the model names of the material metadata models based on the input operation of the naming control.

4. The method of claim 1, wherein the material metadata model further comprises a change indication field that characterizes whether the material metadata model can be changed, the method further comprising:

if the change indication field indicates that the material metadata model can be changed, an operation item for changing the material metadata model is also displayed in the example editing interface;

modifying the material metadata model in response to the action item for modifying the material metadata model;

the operation item for changing the material metadata model comprises at least one of the following items: the operation item of newly adding field attribute, the operation item of changing field attribute and the operation item of deleting field attribute.

5. The method according to claim 1, wherein the field attribute further includes presentation indication information for indicating whether presentation is possible, and the presenting the presentation name in the instance editing interface includes:

reading the display indication information of the field attribute;

if it is determined that the display indication information indicates that the field attribute can be displayed in the instance editing interface, displaying the display name of the field attribute in the instance editing interface.

6. The method of claim 1, wherein after determining and storing an instance of material based on the correspondence between the material data and the field attributes, the method further comprises:

responding to a obtaining request for the material instance;

and analyzing the material example, acquiring the field attribute in the material example and the material data corresponding to the field attribute, and displaying the material data in an example display interface.

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

the field attribute acquisition module is configured to acquire field attributes in the material metadata model when the material metadata model is instantiated; wherein, the field attribute comprises the corresponding relation between the display name and the data type;

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

the material data acquisition module is configured to execute addition operation responding to the material data added to the display name and acquire material data matched with the data type corresponding to the display name;

and the material instance acquisition module is configured to determine and store a material instance based on the corresponding relation between the material data and the field attribute.

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 processing method of any of claims 1 to 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 processing method of any of claims 1-6.

10. A computer program product comprising a computer program, characterized in that the computer program realizes the operational data processing method of any of claims 1 to 3 when executed by a processor.

Technical Field

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

Background

With the rapid development of internet technology, internet products have become an indispensable part of people's daily life. Many internet-based product platforms can provide certain business operations to users through user interfaces. Such as an online shopping platform, an e-book viewing platform, a short video platform, etc.

With the continuous improvement of user requirements, the internet data volume in a product platform is greatly increased, and the internet service becomes complicated and changeable. In the related art, management of operation data required by a service needs to be realized by means of front-end and back-end codes, and the implementation mode has the problem of high operation cost.

Disclosure of Invention

The embodiment of the application provides an operation data processing method and a related device, which are used for solving the problem that the operation cost is higher in an operation data management mode in the related technology.

In a first aspect, an embodiment of the present application provides an operation data processing method, where a configuration interface of operation data supports a custom field attribute, and the method includes:

when the material metadata model is instantiated, the field attribute in the material metadata model is obtained; wherein, the field attribute comprises the corresponding relation between the display name and the data type;

displaying the display name in an example editing interface;

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

and determining and storing a material instance based on the corresponding relation between the material data and the field attribute.

In some possible embodiments, generating the field attributes of the material metadata model includes:

displaying a model generation interface, wherein the model generation interface comprises operation items for defining the field attribute;

and responding to the user operation of the operation item for defining the field attribute to obtain the field attribute of the material metadata model.

In some possible embodiments, before the obtaining of the field attribute of the material metadata model in response to the user operation on the operation item for defining the field attribute, the method further includes:

displaying a naming control of the material metadata model in the model generation interface;

and taking the input characters as the model names of the material metadata models based on the input operation of the naming control.

In some possible embodiments, the material metadata model further includes a change indication field for indicating whether the material metadata model can be changed, and the method further includes:

if the change indication field indicates that the material metadata model can be changed, an operation item for changing the material metadata model is also displayed in the example editing interface;

modifying the material metadata model in response to the action item for modifying the material metadata model;

the operation item for changing the material metadata model comprises at least one of the following items: the operation item of newly adding field attribute, the operation item of changing field attribute and the operation item of deleting field attribute.

In some possible embodiments, the field attribute further includes presentation indication information that characterizes whether to present, and the presenting the presentation name in the instance editing interface includes:

reading the display indication information of the field attribute;

if it is determined that the display indication information indicates that the field attribute can be displayed in the instance editing interface, displaying the display name of the field attribute in the instance editing interface.

In some possible embodiments, after determining and storing the material instance based on the correspondence between the material data and the field attribute, the method further comprises:

responding to a obtaining request for the material instance;

and analyzing the material example, acquiring the field attribute in the material example and the material data corresponding to the field attribute, and displaying the material data in an example display interface.

In some possible embodiments, the example display interface includes an operation item for updating material data, the field attribute in the material example and the material data corresponding to the field attribute are obtained, and after the material data is displayed in the example display interface, the method further includes:

and responding to the operation item for updating the material data, and updating the material data corresponding to the field attribute.

In some possible embodiments, after determining and storing the material instance based on the correspondence between the material data and the field attribute, the method further comprises:

responding to the search operation of the material instance, and acquiring the material instance; alternatively, the first and second electrodes may be,

responding to the search operation of the field attribute in the material instance, and acquiring the field attribute in the material instance and the material data corresponding to the field attribute.

In a second aspect, an embodiment of the present application provides an operation data processing apparatus, where a configuration interface of operation data supports a custom field attribute, the apparatus includes:

the field attribute acquisition module is configured to acquire field attributes in the material metadata model when the material metadata model is instantiated; wherein, the field attribute comprises the corresponding relation between the display name and the data type;

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

the material data acquisition module is configured to execute addition operation responding to the material data added to the display name and acquire material data matched with the data type corresponding to the display name;

and the material instance acquisition module is configured to determine and store a material instance based on the corresponding relation between the material data and the field attribute.

In some possible embodiments, generating the field attribute of the material metadata model is performed, and the field attribute acquisition module is configured to:

displaying a model generation interface, wherein the model generation interface comprises operation items for defining the field attribute;

and responding to the user operation of the operation item for defining the field attribute to obtain the field attribute of the material metadata model.

In some possible embodiments, before the field attribute of the material metadata model is obtained in response to the user operation on the operation item for defining the field attribute, the field attribute obtaining module is further configured to:

displaying a naming control of the material metadata model in the model generation interface;

and taking the input characters as the model names of the material metadata models based on the input operation of the naming control.

In some possible embodiments, the material metadata model further includes a change indication field for indicating whether the material metadata model can be changed, and the apparatus further includes:

an operation item processing module configured to perform, if the change indication field indicates that the material metadata model is changeable, further showing an operation item for changing the material metadata model in the instance editing interface;

modifying the material metadata model in response to the action item for modifying the material metadata model;

the operation item for changing the material metadata model comprises at least one of the following items: the operation item of newly adding field attribute, the operation item of changing field attribute and the operation item of deleting field attribute.

In some possible embodiments, the field attribute further includes presentation indication information indicating whether presentation is possible, the presentation of the presentation name in the instance editing interface is performed, and the presentation module is configured to:

reading the display indication information of the field attribute;

if it is determined that the display indication information indicates that the field attribute can be displayed in the instance editing interface, displaying the display name of the field attribute in the instance editing interface.

In some possible embodiments, after performing the determining and storing of the material instance based on the correspondence between the material data and the field attribute, the material instance obtaining module is further configured to:

responding to a obtaining request for the material instance;

and analyzing the material example, acquiring the field attribute in the material example and the material data corresponding to the field attribute, and displaying the material data in an example display interface.

In some possible embodiments, the instance display interface includes an operation item for updating material data, the obtaining of the field attribute in the material instance and the material data corresponding to the field attribute is executed, and after the material instance is displayed in the instance display interface, the material instance obtaining module is further configured to:

and responding to the operation item for updating the material data, and updating the material data corresponding to the field attribute.

In some possible embodiments, after performing the determining and storing of the material instance based on the correspondence between the material data and the field attribute, the material instance obtaining module is further configured to:

responding to the search operation of the material instance, and acquiring the material instance; alternatively, the first and second electrodes may be,

responding to the search operation of the field attribute in the material instance, and acquiring the field attribute in the material instance and the material data corresponding to the field attribute.

In a third aspect, an embodiment of 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.

According to the embodiment of the application, the material metadata model is generated in response to the configuration operation of the material metadata model in advance. The material metadata model includes at least one custom field attribute. In the present application, a material metadata model is used to define a class of operational data. After the material metadata model is built, analyzing operation is carried out on the material metadata model, and the field names corresponding to the field attributes in the material metadata model are displayed in an example editing interface. And responding to the adding operation of adding the material data aiming at the displayed field names, acquiring the material data corresponding to the field names, and analyzing the field attributes and the material data corresponding to the field attributes in the material metadata model into a material instance. And sending the material instance to a server side for storage. Through the process, the problems that the labor resource consumption is high and the operation cost is high in the management mode of the operation data in the related technology are solved.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

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 an application scenario diagram of an operation data processing method according to an embodiment of the present application;

FIG. 2a is a diagram of a material metadata model provided in an embodiment of the present application;

FIG. 2b is a schematic diagram of a material example model provided in the embodiments of the present application;

fig. 3a is an overall flowchart of an operation data processing method according to an embodiment of the present application;

FIG. 3b is a tabular diagram illustrating the building of a material metadata model in accordance with an exemplary embodiment;

FIG. 3c is a schematic diagram illustrating a model generation interface, according to an exemplary embodiment;

FIG. 3d is a diagram illustrating field re-editing functionality, according to an exemplary embodiment;

FIG. 3e is a diagram illustrating an example editing interface, according to an illustrative embodiment;

FIG. 3f is a diagram illustrating status indication information, according to an example embodiment;

FIG. 3g is an illustration of an example presentation interface shown in accordance with an illustrative embodiment;

FIG. 3h is a diagram illustrating the results of an edit and delete operation performed in accordance with an illustrative embodiment;

fig. 4 is a block diagram illustrating an operational data processing apparatus 400 according to an example embodiment;

fig. 5 is a schematic diagram of an electronic device illustrating an operation data processing 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) And the material instance is used for representing instance data formed by the custom fields and the materials corresponding to the custom fields in the material metadata model. For example, when a cover picture (the cover picture is the number of materials) is added to the advertisement cover field, the advertisement cover field and the cover picture form a material example.

In consideration of the related art, different database tables need to be established for different types of operation data. Because the field corresponding to the operation data is fixed in the database table, the codes of the front end and the back end need to be modified when the original operation data needs to be deleted or a new type of operation data needs to be added. In order to solve the above problems, the inventive concept of the present application is: a material metadata model is pre-constructed that allows a user to add custom fields. The front-end interface may generate a form for editing the model based on the database table to which the model corresponds. The user can add or delete the custom field to the model in the front-end interface. Because one material metadata model can be defined as a type of operation data, the operation personnel can freely expand and delete the operation data only through a front-end interface. When the operation data is added and deleted through the process, the front end and the back end do not need to be coded, and the operation cost is reduced.

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.

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 method steps as shown in the following embodiments or figures, more or fewer steps may be included in the method based on conventional or non-inventive efforts. 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. The method can be executed in the order of the embodiments or the method shown in the drawings or in parallel in the actual process or the control device.

Fig. 1 is a schematic view of an application scenario of the operation data processing method according to the embodiment of the present application. The application scenario is used for describing the operation data processing platform. The operation data processing platform can comprise a plurality of terminal devices 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 that may support a downstream content server (not shown) to provide internet services to users of the internet services.

In this embodiment, the terminal device 101 may display an operation interface for defining the material, and the operator may flexibly define the material based on the operation interface, and then submit the material to the server 102 for storage. Based on the material, 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.

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.

Considering that in the related art, different database tables need to be established for different types of operation data, this directly results in the need to rebuild the database when a new type of operation data is added. In the present application, a material metadata model is first established, which may be specifically shown in fig. 2a, where the material metadata model is used to represent a type of operation data. The model Key (i.e., the unique identifier in the model), the model Name (i.e., the Name of the material metadata model), and custom field attributes are included in the material metadata model. The custom field attribute comprises a field type used for expressing the data type of the field and a display name used for calling of a product platform and displaying of a 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.

After the user defines the field attribute to obtain the material metadata model, the material metadata model can be endowed with material data, and a material instance is obtained for storage.

Further, as shown in fig. 2b, in the embodiment of the present application, in order to conveniently instantiate the material metadata model, the material instance is saved. A unified material instance model is provided for hosting material data of various types, in particular 7 data types as shown in fig. 2 b. The material metadata model instantiated in the embodiments of the present application may be referred to as a material instance model. And defining a material key in the material instance model to correspond to the model key in the material metadata model so as to represent that material data in the material instance model under the same key correspond to the respective defined field attributes in the material metadata model. Therefore, by configuring and defining the material metadata model and displaying the material metadata model on the front-end interface, when a new type of operation data exists, the material data can be added to the custom field only after the custom field is added to the type of operation data on the front-end interface. The front end and the rear end do not need to be coded, and a large amount of labor consumption is saved.

The operation data processing method provided by the embodiment of the present application is described in detail below with reference to fig. 3a, and includes the following steps:

the method is based on a Nocode open source framework, a database used for configuring the material metadata model is constructed in advance, and all elements contained in the material metadata model are defined in the database. For example, each column Name in the database includes a model key, a model Name, a custom field attribute, and the like of the material metadata model, and the operator can configure the material metadata model through the front-end interface to generate the material metadata model.

In implementation, the database interface of the material metadata model defined by the above process is pulled through the front-end interface to generate a form for constructing the material metadata model in the front-end interface, where the form may be as shown in fig. 3 b. After the operator names and inputs the material metadata model in the form, the input data is fed back to the database through the interface. The database generates a unique identification (material key) and creation time for the material metadata model. The operator can name the display name and the english name of the material metadata model by clicking the edit button in the form. The display name is the name displayed by the material metadata model in the front-end interface. The display names of the material element models can be customized at will by customizing the display names. The English name is a name which is automatically generated in the front-end code and the back-end code and is used for representing the material metadata model code, and the name cannot be displayed on a front-end interface. After the editing operation is finished, the material metadata model can be generated by clicking and saving. This corresponds to building a basic framework of the material metadata model. The operator can complete the construction of the material metadata model by adding a custom field to the material metadata model.

Specifically, after the operator finishes editing the form shown in fig. 3b, the operator clicks the storage interface to jump to the model generation interface. Specifically, as shown in fig. 3c, the model name of the material metadata model, the unique identifier of the material metadata model, and the creation time are displayed 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. In the model generation interface, custom field attributes can be added to the material metadata model by selecting a control of 'adding blank columns'. As shown in FIG. 3c, after selecting "Add blank column", N columns of customizable field properties are revealed, N being used to represent the next field. The field attributes may include at least:

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. 3b, 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 field attributes, e.g., 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. 3c, 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.

In order to adapt to more application scenarios, the field attribute also includes change indication information indicating whether the field attribute can be changed, and the change indication information is used for indicating whether the field attribute can be edited and modified by the 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.

Specifically, the material metadata model can be displayed on a model generation interface according to the change indication information corresponding to each field attribute in the material metadata model. The model generation interface comprises operation items for defining field attributes. The operation item is used for an operator to edit the field attribute of the custom field so as to realize the editing operation of the field attribute. A naming control for the material metadata model is displayed in the model generation interface, and a user can use input characters as the model name of the material metadata model through input operation of the naming control.

In some possible embodiments, a change indication field for indicating whether the material metadata model can be changed is set in the material metadata model, specifically as shown in fig. 3d, if the change indication field of the material metadata model indicates that the material metadata model can be changed, the operator may change the field attribute 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. 3d to perform an operation to add a new field property, clicking on the "re-edit" button shown in FIG. 3d 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 re-edit the field attribute of the custom field in the material metadata model, namely, update the generated material metadata model.

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 respective defined fields of the material metadata model in the front-end interface.

And after the construction of the material metadata model is completed, adding a corresponding material instance to the custom field in the material metadata model, namely, completing the endowing of the material metadata model with the material data. In practice, step 301 is executed first: and when the material metadata model is instantiated, acquiring the field attribute in the material metadata model. Wherein, the field attribute comprises the corresponding relation between the display 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.

In the embodiment of the present application, in order to facilitate an operator to add material data to each defined field of a material metadata model, after clicking the save button in fig. 3b, the operator may set a jump to the model generation interface and display an instance editing interface beside the model generation interface, specifically as shown in fig. 3e, by adding a corresponding material instance to the defined field in the instance editing interface. In practice, by performing 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.

It is considered that there are some field attributes in the material metadata model, such as the above-mentioned "creation time", "update time", etc., which do not have practical meaning in the process of adding material data to the operator. 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 whether the instance editing interface presentation is supported. 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. 3f, 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. 3e, the name "pop-up advertisement" of the material metadata model is displayed in the interface, and the display names of the two custom fields in the material metadata model (i.e., "advertisement name" and "advertisement cover" shown in fig. 3 e) are displayed. And also adding a control according to an instance corresponding to the data type of the custom field. For example, if the data type defined in the "advertisement title" custom field is a string type, the instance addition control presented in the instance editing interface is an input field for inputting string type data. For example, if the data type defined in the "advertisement cover" custom field is a picture file type, the example addition control displayed in the example editing interface is an upload button (i.e., "picture file upload button" shown in fig. 3 d) for uploading a picture file, a locally stored picture storage address appears in a pop-up window form after clicking the button, and the picture can be pulled from the picture storage address and uploaded to the "advertisement cover" field by clicking the picture storage address corresponding to the picture to be added.

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 rear end codes, and only 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 code-free editing of the operation data.

In addition, after the corresponding relation between each field attribute and the material data in the material metadata model is analyzed into a material example and stored, the material example which is stored in a warehouse can be displayed for the convenience of the operator to check the material example. In implementation, the material instance stored in the database is acquired by sending an acquisition request of the material instance to the server. And analyzing the material example, acquiring the field attribute of the material example and the material data corresponding to the field attribute, and displaying the material data in the example display interface. The displayable information is information that can be displayed by the material instance display interface in each field attribute, and may be, for example, a field name of a field attribute, material data corresponding to a field attribute, and the like.

In implementation, the example presentation interface may perform some functional optimization, for example, an operation item for updating the material data may be included in the example presentation interface, and the operation item is used to edit the material data of each field attribute presented by the example presentation interface. Specifically, as shown in fig. 3g, material data corresponding to each defined field in each material metadata is displayed in the example display interface. The operator can edit, modify and delete the material data on the interface.

Specifically, as shown in fig. 3h, the material data corresponding to the originally defined field "advertisement cover" is a panda picture, and the operator can delete the picture by clicking the delete button, and at this time, the advertisement cover of the material metadata "pop-up window advertisement" no longer has the picture. In addition, the operator can also change the panda picture by clicking the edit button, for example, changing an apple picture, and in the example display interface, the advertisement cover of the material metadata of the "pop-up window advertisement" is changed into an apple by the panda.

Meanwhile, the creation time of each material data is recorded in the interface. The creation time is the time when the material data is added to the custom field in the instance editing interface. The time when each material data is updated is also recorded in the interface, and the updating time is the time when the material data of the field attribute is edited, modified and/or deleted. The creation time and the update time are automatically generated based on the actual operation of an operator and cannot be manually modified.

In some possible embodiments, the interface is shown for example with the addition of filtering functionality. In practice, the material instance may be configured to be obtained in response to a search operation on the material instance. Or, in response to a search operation for a specified field attribute in the material instance, the specified field attribute in the material instance and the corresponding material data are acquired. Specifically, the material instance can be searched out by setting the unique identification material key in the material instance, and the material instance can also be searched out by setting the field name of the custom field in the material instance. By adding the filtering function to the example display interface, operators can quickly find required material examples without line-by-line searching.

Based on the same inventive concept, the present application further provides an operation data processing apparatus 400, specifically as shown in fig. 4, the apparatus includes:

a field attribute obtaining module 401, configured to obtain a field attribute in a material metadata model when the material metadata model is instantiated; wherein, the field attribute comprises the corresponding relation between the display name and the data type;

a presentation module 402 configured to perform presentation of the presentation name in an instance editing interface;

a material data acquisition module 403 configured to perform an addition operation of adding material data in response to the display name, and acquire material data matching the data type corresponding to the display name;

a material instance obtaining module 404 configured to determine and store a material instance based on a correspondence between the material data and the field attribute.

In some possible embodiments, the generating of the field attribute of the material metadata model is performed, and the field attribute obtaining module 401 is configured to:

displaying a model generation interface, wherein the model generation interface comprises operation items for defining the field attribute;

and responding to the user operation of the operation item for defining the field attribute to obtain the field attribute of the material metadata model.

In some possible embodiments, before the field attribute of the material metadata model is obtained in response to the user operation on the operation item for defining the field attribute, the field attribute obtaining module 401 is further configured to:

displaying a naming control of the material metadata model in the model generation interface;

and taking the input characters as the model names of the material metadata models based on the input operation of the naming control.

In some possible embodiments, the material metadata model further includes a change indication field for indicating whether the material metadata model can be changed, and the apparatus further includes:

an operation item processing module configured to perform, if the change indication field indicates that the material metadata model is changeable, further showing an operation item for changing the material metadata model in the instance editing interface;

modifying the material metadata model in response to the action item for modifying the material metadata model;

the operation item for changing the material metadata model comprises at least one of the following items: the operation item of newly adding field attribute, the operation item of changing field attribute and the operation item of deleting field attribute.

In some possible embodiments, the field attribute further includes presentation indication information indicating whether to present, the presenting the presentation name in the instance editing interface is performed, and the presentation module 402 is configured to:

reading the display indication information of the field attribute;

if it is determined that the display indication information indicates that the field attribute can be displayed in the instance editing interface, displaying the display name of the field attribute in the instance editing interface.

In some possible embodiments, after performing the determining and storing of the material instance based on the correspondence between the material data and the field attribute, the material instance obtaining module 404 is further configured to:

responding to a obtaining request for the material instance;

and analyzing the material example, acquiring the field attribute in the material example and the material data corresponding to the field attribute, and displaying the material data in an example display interface.

In some possible embodiments, the instance display interface includes an operation item for updating material data, the obtaining of the field attribute in the material instance and the material data corresponding to the field attribute is performed, and after the material instance is displayed in the instance display interface, the material instance obtaining module 404 is further configured to:

and responding to the operation item for updating the material data, and updating the material data corresponding to the field attribute.

In some possible embodiments, after performing the determining and storing of the material instance based on the correspondence between the material data and the field attribute, the material instance obtaining module 404 is further configured to:

responding to the search operation of the material instance, and acquiring the material instance; alternatively, the first and second electrodes may be,

responding to the search operation of the field attribute in the material instance, and acquiring the field attribute in the material instance and the material data corresponding to the field attribute.

The electronic device 130 according to this embodiment of the present application is described below with reference to fig. 5. The electronic device 130 shown in fig. 5 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. 5, 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 the memory 132 comprising instructions, executable by the processor 131 of the apparatus 400 to perform the above-described method is also provided. Alternatively, the computer readable storage medium may be 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, there is also provided a computer program product comprising computer programs/instructions which, when executed by the processor 131, implement any of the operational data processing methods as provided herein.

In an exemplary embodiment, various aspects of an operation data processing method provided by the present application can also be implemented in the form of a program product, which includes program code for causing a computer device to perform the steps in an operation data processing 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 image scaling of 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.

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.