CN113722341B

CN113722341B - Operation data processing method and related device

Info

Publication number: CN113722341B
Application number: CN202111016333.XA
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-03-01
Anticipated expiration: 2041-08-31
Also published as: CN113722341A

Abstract

After obtaining a reference field and an associated field to be associated issued by a user, the embodiment of the application establishes a mapping relationship between each associated field and the reference field, and when updating field content of the reference field, updates the updating content of the reference field to the associated field synchronously based on the mapping relationship. Because the reference field and the associated field are different from each other on the product platform, the operation data of the multi-product platform can be updated and managed through the flow, and therefore the problem that the update and management efficiency of the processing platform on the operation data in the related technology is low is solved.

Description

Operation data processing method and related device

Technical Field

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

Background

With the rapid development of internet technology, many product operators have established their corresponding product platforms via the internet. Such as an online shopping platform, an electronic book viewing platform, a short video platform, etc. The internet service of the product platform is complex and changeable, and the product operators generally manage the operation data of a plurality of product platforms by constructing a processing platform of the operation data. In the related art, the update management efficiency of the processing platform on the operation data is low.

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 update management efficiency of a processing platform on operation data in the related technology is low.

In a first aspect, an embodiment of the present application provides an operation data processing method, where the method includes:

acquiring a reference field and an associated field in response to an associated instruction of a user; wherein the reference field is defined by a first platform, and the associated field belongs to a first material metadata model of a second platform;

establishing a mapping relation between the association field and the reference field; wherein, the field content of the reference field represents a material instance in one type of operation data;

and if the reference field is monitored to be updated, inquiring the associated field corresponding to the reference field according to the mapping relation, and updating the associated field in the first metadata model of the second platform based on the updating result of the reference field.

In some possible embodiments, the reference field is a field of a second material metadata model in the first platform, and the establishing a mapping relationship between the associated field and the reference field includes:

Identifying a unique identifier of the second material metadata model in which the reference field is located;

and associating the field name of the reference field with the field name of the association field, and associating the unique identifier with the association field to obtain the mapping relation.

In some possible embodiments, the reference field includes a reference subfield, the association field includes an association subfield, and after associating the field name of the reference field with the field name of the association field, the method further includes:

displaying the field name of the reference field and the field name of the reference subfield in a field association interface;

responding to the input operation for the reference subfields triggered by the field association interface, and acquiring the input fields as the associated subfields corresponding to the reference subfields;

and adding the association relation between the association subfield and the reference subfield into the mapping relation.

In some possible embodiments, the associating field is associated with a synchronous update condition, and if it is monitored that the reference field is updated, querying the associating field corresponding to the reference field according to the mapping relationship, and updating the associating field in the first metadata model of the second platform based on an update result of the reference field includes:

If the reference field is monitored to be updated, determining an updating mode of the reference field;

inquiring the associated field corresponding to the reference field according to the mapping relation;

acquiring a synchronous updating condition corresponding to the associated field;

and if the updating mode of the reference field meets the synchronous updating condition, updating the associated field in the first metadata model of the second platform.

In some possible embodiments, before the updating the association field in the first metadata model of the second platform, the method further comprises:

responding to the selection operation of the associated field, and displaying synchronous update condition options of the associated field;

and establishing an association relationship between the association field and the synchronous update condition of the association field in response to the selection operation of the synchronous update condition option.

In some possible embodiments, determining that the update manner of the reference field satisfies the synchronous update condition includes at least one of:

if the synchronous updating condition comprises a newly added field, if the updating mode of the reference field is detected to be the content of the added field, determining that the updating mode meets the synchronous updating condition;

If the synchronous updating condition comprises a deleting operation, if the updating mode of the reference field is detected to be deleting field content, determining that the updating mode meets the synchronous updating condition;

if the synchronous update condition comprises a modification field, if the update mode of the reference field is detected to be modification field content, determining that the update mode meets the synchronous update condition.

In some possible embodiments, after determining the synchronization update condition of the association field, the method further comprises:

responding to search operation for the associated field triggered by the field association interface, and acquiring a field name of the associated field to be searched;

acquiring an associated field corresponding to the field name and a synchronous updating condition of the associated field;

and updating the synchronous updating condition of the associated field in response to the modification operation of the synchronous updating condition.

In a second aspect, an embodiment of the present application provides an operation data processing apparatus, including:

a field acquisition module configured to perform acquisition of a reference field and an associated field in response to an associated instruction of a user; wherein the reference field is defined by a first platform, and the associated field belongs to a first material metadata model of a second platform;

A relationship establishing module configured to perform establishing a mapping relationship between the association field and the reference field; wherein, the field content of the reference field represents a material instance in one type of operation data;

and the synchronous updating module is configured to execute the steps of inquiring the associated field corresponding to the reference field according to the mapping relation if the reference field is monitored to be updated, and updating the associated field in the first metadata model of the second platform based on the updating result of the reference field.

In some possible embodiments, the reference field is a field of a second material metadata model within the first platform, the performing establishing a mapping relationship between the associated field and the reference field, the relationship establishing module being configured to:

In some possible embodiments, the reference field includes a reference subfield, the association field includes an association subfield, and after performing the associating the field name of the reference field with the field name of the association field, the relationship establishment module is further configured to:

In some possible embodiments, the association field is associated with a synchronous update condition, the step of querying the association field corresponding to the reference field according to the mapping relation if the reference field is updated is performed, and based on an update result of the reference field, updating the association field in the first metadata model of the second platform, the synchronous update module is configured to:

In some possible embodiments, before performing the updating of the associated field in the first metadata model of the second platform, the synchronization update module is further configured to:

In some possible embodiments, after performing the determining of the synchronization update condition of the association field, the synchronization update module is further configured to:

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

In the embodiment of the application, a reference field and at least one associated field corresponding to the reference field are acquired in response to an associated instruction of a user. Each associated field is respectively from a different first material metadata model, and the material metadata models are used for representing one type of operation data. And establishing a mapping relation between the reference field and each associated field, wherein when the field content of the reference field is updated, the updated content of the reference field is synchronously updated to each associated field based on the mapping relation. Therefore, the problem that the update management efficiency of the processing platform to the operation data in the related art is low is 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 practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof 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 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 diagram of an operation data processing method provided in an embodiment of the present application;

fig. 2a is a flowchart of an overall operation data processing method provided in an embodiment of the present application;

FIG. 2b is a diagram illustrating field name correspondence, according to an example embodiment;

FIG. 2c is a schematic diagram of an editing interface shown in accordance with an exemplary embodiment;

FIG. 2d is a schematic diagram of a field association interface shown in accordance with an exemplary embodiment;

FIG. 2e is another field association interface schematic diagram shown in accordance with an exemplary embodiment;

FIG. 2f is a schematic diagram of a reference field A shown according to an exemplary embodiment;

FIG. 2g is a schematic diagram of an association field B, shown according to an exemplary embodiment;

FIG. 2h is a diagram illustrating database synchronization update results according to an exemplary embodiment;

FIG. 2i is a diagram illustrating synchronization update condition modification according to an example embodiment;

FIG. 3 is a block diagram of an operational data processing apparatus shown in accordance with an exemplary embodiment;

fig. 4 is a schematic diagram of an electronic device illustrating an operational data processing 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 for 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) The reference field and the associated field are fields in the material metadata model, and the material metadata model to which the reference field belongs and the material metadata model to which the associated field belongs respectively belong to different servers.

(8) The material instance is used for representing instance data formed by the custom field and the corresponding material in the material metadata model. For example, after adding a cover picture (the number of materials) to the advertisement cover field, the advertisement cover field and the cover picture form a material instance.

In the related art, the linkage relation exists in part of operation data of the related product platform, however, the processing platform of the operation data in the related art does not support synchronous update of the operation data among different platforms. For example, a product operator needs to update a batch of operation data to two associated product platforms under a flag, but the operation data processing platform cannot update the operation data of the two product platforms synchronously, so that the operation data can only be distributed to the two product platforms in batches, which causes additional time consumption and human resource waste.

To solve the above problems, the inventive concept of the present application is: after the reference field and the associated field to be associated, which are issued by the user, are acquired, the updating content of the reference field can be synchronously updated to the associated field based on the mapping relation when the field content of the reference field is updated by establishing the mapping relation between each associated field and the reference field. Because the reference field and the associated field are different from each other on the product platform, the operation data of the multi-product platform can be updated and managed through the flow, and therefore the problem that the update and management efficiency of the processing platform on the operation data in the related technology is low is solved.

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, in order to further illustrate the technical solution provided in the embodiments of the present application, the following detailed description is provided with reference to the accompanying drawings and the specific embodiments. 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 based on routine or non-inventive labor. 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. The methods may be performed sequentially or in parallel as shown in the embodiments or the drawings when the actual processing or the control device is executing.

Referring to fig. 1, an application scenario diagram of an operation data processing method provided in an embodiment of the present application is shown.

The application scenario is used to describe an operational data processing platform. The operation data processing platform may comprise a plurality of terminal devices 101, servers 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 and may support a downstream content server (not shown) to provide internet services to users of the internet services.

In this embodiment of the present application, 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 saving. 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 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.

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.

The following describes in detail the operation data processing method provided in the embodiment of the present application through fig. 2a, specifically as shown in fig. 2a, including:

the method and the device establish a database corresponding to the operation data of each product platform in the operation data processing platform in advance, wherein the database of each product platform is used for storing the operation data of the product platform. And the databases are configured to be connected with the corresponding product platform service ends, so that the operation data of each product platform are stored in the operation data platform. Therefore, the unified management of the operation data processing platform for the management work such as maintenance, update and the like of the operation data of each product platform can be realized.

In the embodiment of the application, a material metadata model is built in advance based on a database, and the material metadata model is used for representing one type of operation data. The material metadata model includes a model Key (i.e., a unique identifier in the model), a model Name (i.e., the Name of the material metadata model), and custom field attributes. The custom field attribute comprises a presentation name for product platform calling and front-end page presentation, a field type for representing the field data type and a unique identification of the field. The operator can assign material data to the material metadata model to obtain material examples and store the material examples. For example, a product platform updates a batch of mid-autumn style commodity display templates during mid-autumn, and the "templates" are one type of operation data. The "templates" may include, for example, class a mid-autumn templates, class B mid-autumn templates, and the like. The name of each template is one field name (for example, a class a mid-autumn template and a class B mid-autumn template are two field names) in the material metadata model, and the field content corresponding to the field is material data. Taking a field with a field name of the class A mid-autumn template as an example, the field content of the field is a template diagram of the class A mid-autumn template. Therefore, an operator stores the material instance by adding the material data into the material metadata model. Unless otherwise specified, the following material metadata models in the embodiments of the present application are models to which material data is instantiated.

Considering that there may be different situations for the material metadata models corresponding to each product platform for the same kind of operation data, for example, for the operation data of the "template" type, unique identifiers of the material metadata models representing the "template" type in the corresponding databases of different product platforms are different. Also, there may be differences in field name settings in the "template" class material metadata model for different product platforms. The model key is set by related personnel when constructing the material metadata model, and is used for representing the unique identifier of the material metadata model, specifically, as shown in fig. 2B, the model key of the material metadata model corresponding to the product platform a is 111, and the model key of the material metadata model corresponding to the product platform B is 211. In the material metadata model with the model Key 111, the field name of the specified template, which is "summer template", is "xiari". In the material metadata model with the model Key 211, the field name of the specified template, which is "summer template", is "summer.

In order to enable the operation data processing platform to synchronously update the operation data of each product platform, the field content sharing can be realized by setting mapping association among fields. A library of reference fields may be pre-established in the operational data processing platform, each reference field representing a material in a certain type of operational data. Taking "summer templates" as an example, the field name of "summer templates" may be defined in the reference field database as "xrmb". And taking a field representing a summer template in the database corresponding to each product platform as an associated field, and establishing a mapping relation between the reference field and the corresponding associated field.

In implementation, as shown in fig. 2c, after the reference field library is established, the database data is pulled through the front-end interface to form a form, and an editing interface for configuring the mapping relation between the reference field and the associated field is provided for operators. The operator may indicate the associated field corresponding to the reference field at the editing interface. The operational data processing platform performs step 201 in response to the association indication of the user: the reference field and the associated field are obtained in response to an association indication of the user.

Wherein the reference field is defined by the first platform and the associated field belongs to the first material metadata model of the second platform. That is, the reference field and the associated field are each from different product platforms. Specifically, for each product platform managed by the operation data processing platform, one product platform is selected as a reference product platform, and other product platforms are target product platforms. And establishing a mapping relation by taking each field in the database corresponding to the reference product platform as a reference field and each field in the database corresponding to the target product platform as an associated field.

After the reference field and the associated field are acquired, step 202 is performed: and establishing a mapping relation between the association field and the reference field. Wherein, the field content of the reference field represents a material instance in one type of operation data. Taking the foregoing "summer template" as an example, the field name of the reference field is called "summer template", and the field content of the reference field indicates the specific template style of the summer template, that is, the material instance of the summer template.

Because the reference field is different from the product platform to which the association field belongs, the reference field is used as the mapping original image of the association field, so that the mapping relation between the reference field and the association field is established, and the operation data processing platform can synchronously update the association field based on the mapping relation when updating the field content of the reference field.

In the foregoing description, in the embodiment of the present application, the database of each product platform is stored in the operation data processing platform, and the database is used to store the material metadata model of the corresponding product platform. Because the other material metadata models except the material metadata model to which the reference field belongs may have the same field as the name of the reference field, in order to avoid the selection error of the mapping target, considering that the field name in each material metadata model is different, that is, the field name of each reference field is unique in the second material metadata model, when the mapping relationship is established, the unique identifier (that is, the model Key) of the second material metadata model to which the reference field belongs can be obtained in advance, and the unique identifier is associated with the associated field to ensure that the correct mapping original image is selected. Further, the establishment of the mapping relation between the reference field and the associated field is realized by associating the field name of the reference field with the field name of the associated field.

Because the associated fields of the different second platforms may have the same field names, for example, an associated field "xiatian" exists in the "template" type material metadata model in the second platform a, and an associated field of the same field name also exists in the "sticker" type material metadata model in the second platform B, although the two associated fields represent the template material instance and the sticker material instance, respectively, the field names may still be the same. Therefore, in order to avoid the situation that the mapping is wrong due to the reasons of the same names, the unique identifier corresponding to the reference field needs to be associated with the associated field.

In practical application, the fields have nesting relation. By nested relation, i.e. a field is nested with at least one sub-field, a sub-field is understood as an additional attribute of a field. Taking the reference field as an example, the field name is "summer template", the field can be nested with reference word subfields such as "size", "icon", and the like, and each reference subfield is an attribute of the reference field of the "summer template". For the reference field with the reference sub-field, the associated field with the nested relation can be adopted to establish the mapping relation with the reference field. Thus, when the reference subfields of the reference fields are updated, the reference subfields of the reference fields can be synchronously updated into the associated subfields of the associated fields based on the mapping relation, and the synchronous update can be thinned into the subfields.

In implementation, a field association interface may be established in the operational data processing platform, where the field association interface is configured to configure a mapping relationship between the reference field and the associated field. The field association interface displays the field name of the reference field and the field name of the reference subfield. And acquiring the input field as the associated sub-field corresponding to the reference sub-field by responding to the input operation for the reference sub-field triggered by the field association interface. Further, the association relation between the association sub-field and the reference sub-field is added into the mapping relation. As shown in fig. 2d specifically, for the reference field "summer template", the operator may input, in the interface area 1 shown in fig. 2d, a unique identifier corresponding to the reference field, a field name of the reference field, and a field name of a corresponding associated field. And after receiving the association instruction input by the user, the operation data processing platform establishes a mapping relation between the reference field and the association field. Further, the operator can configure the mapping relation of the reference field corresponding to the reference subfield through the interface. As shown in the interface area 2 in fig. 2d, the operator fills in the field names of the reference subfield "tubiao" of the reference field "xiari" and the associated subfield "logo" in the interface area 2 to establish the mapping relationship between the subfields.

In view of the fact that the above-mentioned manner of establishing a mapping relationship for the reference fields of the nested relationship by manually inputting field names takes a long time, the mapping relationship can also be established by configuring the Groovy code logic between the reference fields and the associated fields. The mapping between the reference sub-field corresponding to the reference field and the associated sub-field can be automatically established by establishing the mapping between the reference field and the associated field through the Groovy code logic, and the mapping relation is not required to be independently established for the sub-fields.

Further, a synchronization update opportunity may be set to determine under what circumstances the associated field is updated synchronously with the reference field. In practice, a synchronization update condition may be set for the associated field, which is used to determine whether to follow the reference field for synchronization update. Specifically, if it is monitored that the field content of the reference field is updated, the updating mode of the reference field is obtained, and the corresponding associated field is queried according to the mapping relation of the reference field. And if the updating mode of the reference field is determined to be in accordance with the synchronous updating condition set by the associated field, updating the associated field.

In some possible embodiments, an update component is provided in the field association interface for setting a synchronous update condition for the associated field. As shown in fig. 2e, the update component shown in fig. 2e includes three options of "add", "delete" and "modify". The "update" option indicates that when the update mode of the reference field is the content of the newly added field, the associated field corresponding to the reference field is synchronously updated. The "delete" option indicates that when the update mode of the reference field is to delete the field content, the associated field corresponding to the reference field is synchronously updated. The "modify" option indicates that when the update mode of the reference field is to modify the field content, the associated field corresponding to the reference field is synchronously updated.

In some possible embodiments, the synchronization update condition may be applied to a reference subfield of an associated field if the associated field is nested with at least one associated subfield. For example, reference field a is nested with reference subfield a, reference field a is associated with association field a and reference subfield a is associated with association subfield a nested with association field a. After setting the synchronous update condition for the associated field a as "newly added", when the field content of the reference field a is newly added, the newly added field content is updated into the associated field a. Correspondingly, if the field content of the reference subfield a is detected to be newly increased, the field content of the reference subfield a is updated to the associated subfield a. In addition, a synchronization update condition may be set for the subfields separately, and taking the above reference field a and the associated field a as examples, the synchronization update condition of the associated field a may be set to "delete" and "modify", and the synchronization update condition of the associated subfield a is "add", which is not limited in this application for a specific setting manner of the synchronization update condition.

In some possible embodiments, the storage form of the reference field in the database may be as shown in fig. 2f, where the whole form is a second metadata model of material where the reference field is located, each column name in the form is a field name of a respective definition field, the data in each row corresponding to the column is a prime number of material of the corresponding field of the column, as shown in fig. 2f, the reference field with a field name a is a custom field in the metadata model of the second material, and the reference field a stores the material data of the picture a. Accordingly, the association field is the same as the reference field in its stored form, as shown in fig. 2 g. The associated field with the field name B is a custom field in the first material metadata model, and the associated field B and the reference field A have a mapping relation. For example, if a picture B is newly added in the reference field a, as shown in fig. 2h, the picture B is synchronously added to the corresponding row of the column of the associated field B, so as to realize synchronous update.

In order to flexibly adapt to various application scenes, each option in the updating component can be selected according to actual requirements, and the number of the options selected at the same time is not limited. For example, a product platform to which the reference field belongs temporarily adds an exclusive label (such as a product logo) of the product platform for a type of template material, and adding the exclusive label is to newly add field content of the reference field. It is apparent that the content of the newly added field of the reference field does not need to be synchronously updated into the associated fields of other product platforms, and thus the "newly added" option should not be checked at this time. For example, a batch of template materials are temporarily put on a product platform to which the reference field belongs, and the lower frame of template materials is to delete the field content of the reference field. If other product platforms do not need to put down the batch of material templates, the deleting operation executed by the reference field in the process of putting down the template materials does not need to be synchronized into the other product platforms, and the deleting option does not need to be checked at this time. For another example, the product platform to which the reference field belongs needs to modify the product logo of a batch of template materials. The modification of the product logo of the template material can be understood as the modification of the field content of the reference field, and other product platforms obviously do not need to do the modification since the product logo is specific to the product platform. There is no need to hook the "modify" option at this point.

In some embodiments, if the aforementioned mapping relationship between the reference field and the associated field, and between the reference subfield and the associated subfield is established by means of field name association, the update component may be added in an interface area (such as interface area 2 shown in fig. 2 e) where the mapping relationship between the reference subfield is configured. Thereby realizing further refinement of the synchronization update judgment performed on the associated subfields.

By the method, the mapping relation between the reference field and the associated field and the synchronous updating condition of the associated field can be configured in the field editing interface. After the configuration is completed, the operation data processing platform monitors the reference field in real time. When the reference field is monitored to be updated, inquiring the associated field corresponding to the reference field based on the mapping relation of the reference field, and determining the updating mode of the reference field. And when the updating mode of the reference field meets the synchronous updating condition of the associated field, synchronously updating the field content of the associated field. Therefore, an operator sets the synchronous updating condition of the associated field according to the actual requirement, and can control whether the associated field is synchronously updated along with the reference field.

To accommodate more application scenarios, a synchronous update condition modification function for the associated fields may be set. Specifically, the field association interface is configured to allow related personnel to input a search box of the associated field to be modified. After the field names of the associated fields input by related personnel are obtained, the associated fields corresponding to the field names and the synchronous updating conditions of the associated fields are inquired and displayed. Specifically, as shown in fig. 2i, after the field name a is obtained, the associated field a corresponding to the field name a and the synchronization update condition of the associated field a are identified, and the synchronization update condition is modified by checking the synchronization update condition.

Based on the same inventive concept, the present application further provides an operation data processing apparatus 300, in particular as shown in fig. 3, which includes:

a field acquisition module 301 configured to perform acquisition of a reference field and an associated field in response to an associated instruction of a user; wherein the reference field is defined by a first platform, and the associated field belongs to a first material metadata model of a second platform;

a relationship establishing module 302 configured to perform establishing a mapping relationship between the association field and the reference field; wherein, the field content of the reference field represents a material instance in one type of operation data;

And the synchronous updating module 303 is configured to perform query, if the reference field is updated, the associated field corresponding to the reference field according to the mapping relation, and update the associated field in the first metadata model of the second platform based on the updating result of the reference field.

In some possible embodiments, the reference field is a field of a second material metadata model within the first platform, the performing establishing a mapping relationship between the associated field and the reference field, and the relationship establishing module 302 is configured to:

In some possible embodiments, the reference field includes a reference subfield, the association field includes an association subfield, and after performing the associating the field name of the reference field with the field name of the association field, the relationship establishment module 302 is further configured to:

In some possible embodiments, the association field is associated with a synchronous update condition, the step of querying the association field corresponding to the reference field according to the mapping relationship if the reference field is updated is performed, based on an update result of the reference field, updating the association field in the first metadata model of the second platform, and the synchronous update module 303 is configured to:

In some possible embodiments, before performing the updating of the associated fields in the first metadata model of the second platform, the synchronization update module 303 is further configured to:

In some possible embodiments, after performing the synchronization update condition that determines the association field, the synchronization update module 303 is further configured to:

An electronic device 130 according to this embodiment of the present application is described below with reference to fig. 4. The electronic device 130 shown in fig. 4 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present application in any way.

As shown in fig. 4, the electronic device 130 is 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 of the apparatus 400 to perform the above-described method. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

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

In an exemplary embodiment, aspects of an operation data processing method provided in the present application may also be implemented in the form of a program product comprising program code for causing a computer device to carry out the steps of an operation data processing method according to the various exemplary embodiments of the present application as described in the present specification, 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 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 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 operating data processing, the method comprising:

acquiring a reference field and an associated field in response to an associated instruction of a user; the reference field is a field of a second material metadata model in the first platform, and the associated field belongs to the first material metadata model of the second platform;

identifying a unique identifier of a second material metadata model in which the reference field is located; associating the field name of the reference field with the field name of the associated field, and associating the unique identifier with the associated field to obtain a mapping relationship between the associated field and the reference field;

if the reference field is monitored to be updated, inquiring the associated field corresponding to the reference field according to the mapping relation, and updating the associated field in the first metadata model of the second platform based on the updating result of the reference field;

Wherein the reference field comprises a reference subfield and the association field comprises an association subfield; after the associating the field name of the reference field with the field name of the associated field, the method further includes:

responding to the input operation for the reference subfields triggered by the field association interface, and acquiring the input fields as the associated subfields corresponding to the reference subfields; and adding the association relation between the association subfield and the reference subfield into the mapping relation.

2. The method according to claim 1, wherein the association field is associated with a synchronous update condition, and wherein if the reference field is monitored to be updated, the association field corresponding to the reference field is queried according to the mapping relationship, and updating the association field in the first metadata model of the second platform based on the update result of the reference field includes:

3. The method of claim 2, wherein prior to updating the association field in the first metadata model of the second platform, the method further comprises:

4. A method according to claim 2 or 3, characterized in that determining that the update manner of the reference field satisfies the synchronous update condition comprises at least one of:

5. The method of claim 4, wherein after determining the synchronization update condition of the association field, the method further comprises:

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

a field acquisition module configured to perform acquisition of a reference field and an associated field in response to an associated instruction of a user; the reference field is a field of a second material metadata model in the first platform, and the associated field belongs to the first material metadata model of the second platform;

The relation establishing module is configured to execute unique identification for identifying a second material metadata model where the reference field is located; associating the field name of the reference field with the field name of the associated field, and associating the unique identifier with the associated field to obtain a mapping relationship between the associated field and the reference field;

the synchronous updating module is configured to execute the steps of inquiring the associated field corresponding to the reference field according to the mapping relation if the reference field is monitored to be updated, and updating the associated field in the first metadata model of the second platform based on the updating result of the reference field;

wherein the reference field comprises a reference subfield and the association field comprises an association subfield; after performing the associating the field name of the reference field with the field name of the associated field, the relationship establishment module is further configured to:

7. The apparatus of claim 6, wherein the associated field is associated with a synchronization update condition, wherein the querying the associated field corresponding to the reference field according to the mapping relationship is performed if the reference field is updated, wherein the updating of the associated field in the first metadata model of the second platform is performed based on an update result of the reference field, and wherein the synchronization update module is configured to:

8. The apparatus of claim 7, wherein prior to performing the updating of the association field in the first metadata model of the second platform, the synchronization update module is further configured to:

9. The apparatus according to claim 7 or 8, wherein determining that the update manner of the reference field satisfies the synchronous update condition comprises at least one of:

10. The apparatus of claim 9, wherein after performing the determining the synchronization update condition of the association field, the synchronization update module is further configured to:

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