EP-4735995-A1 - MAPPING DATA-SERIALIZATION ELEMENTS BETWEEN A SOURCE AND A DESTINATION

EP4735995A1EP 4735995 A1EP4735995 A1EP 4735995A1EP-4735995-A1

Abstract

A system may display a Graphical User Interface including a source region presenting a plurality of source data-serialization elements and a destination region presenting a plurality of destination data-serialization elements. The system may receive a user input associating a first destination data-serialization element, of the plurality of destination data-serialization elements, and a first source data-serialization element of the plurality of source data-serialization elements. Responsive to receiving the user input, the system may generate and store a mapping expression that defines a mapping association between the first source data-serialization element and the first destination data-serialization element. The system may present in a mapping region of the GUI displayed concurrently with the source region and the destination region, a mapping element representing the mapping association between the first source data-serialization element and the first destination data-serialization element.

Inventors

ALLI, SUNITHA
HORA, THOMAS

Assignees

Oracle International Corporation

Dates

Publication Date: 20260506
Application Date: 20240605

Claims (19)

1. One or more non-transitory computer readable media comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising: concurrently displaying in a Graphical User Interface (GUI): a source region presenting a plurality of source data-serialization elements, a destination region presenting a plurality of destination data-serialization elements, and a mapping region; receiving a user input associating a first destination data-serialization element, of the plurality of destination data-serialization elements, and a first source data-serialization element of the plurality of source data-serialization elements; responsive to receiving the user input: generating and storing a mapping expression that defines a first mapping association between the first source data-serialization element and the first destination data- serialization element; presenting, in the mapping region of the GUI, a first mapping element representing the first mapping association between the first source data-serialization element and the first destination data-serialization element.
2. The media of Claim 1, wherein the operations further comprise: determining a source hierarchy among a first set of elements of the plurality of source data- serialization elements, and presenting the first set of elements in the source region according to the source hierarchy; or determining a destination hierarchy among a second set of elements of the plurality of destination data-serialization elements, and presenting the second set of elements in the destination region according to the destination hierarchy.
3. The media of Claim 2, wherein the operations comprise determining the source hierarchy, wherein determining the source hierarchy comprises: identifying, from among the plurality of source data-serialization elements, at least one of: a parent source data-serialization element corresponding to the first source data-serialization element, or a child source data-serialization element corresponding to the first source data-serialization element; and wherein generating the mapping expression comprises defining an association between the first destination data-serialization element and the at least one of the parent source data- serialization element or the child source data-serialization element corresponding to the first source data-serialization element.
4. The media of Claim 2, wherein the operations comprise determining the destination hierarchy, wherein determining the destination hierarchy comprises: identifying, from among the plurality of destination data-serialization elements, at least one of: a parent destination data-serialization element corresponding to the first destination data-serialization element, or a child destination data-serialization element corresponding to the first destination data-serialization element; and wherein generating the mapping expression comprises defining an association between the first source data-serialization element and the at least one of the parent destination data-serialization element or the child destination data-serialization element corresponding to the first destination data-serialization element.
5. The media of any of the preceding Claims, wherein the operations further comprise: responsive to receiving the user input, generating an independently executable code that encodes the mapping expression.
6. The media of Claim 5, wherein the first source data-serialization element comprises a source container element having a source value field and a source value occupying the source value field; wherein the first destination data-serialization element comprises a destination container element having a destination value field; and wherein generating the independently executable code comprises: generating an executable instruction configured to generate a copy of the source value and populate the destination value field with the copy of the source value, wherein upon executing the executable instruction, the destination container element comprises the copy of the source value occupying the destination value field.
7. The media of Claim 5, wherein the plurality of source data-serialization elements comprises at least one source container element having a source value field and a source value occupying the source value field, and wherein the first source data-serialization element is associated with a source schema element defining a source structure for the source value field; wherein the plurality of destination data-serialization elements comprises a destination container element having a destination value field, and wherein the first destination data- serialization element is associated with a destination schema element defining a destination structure for the destination value field, wherein the destination schema element differs from the source schema element; wherein generating the independently executable code comprises: generating an executable instruction that is configured to (a) generate a copy of the source value, (b) transform the copy of the source value based on the destination schema element, and (c) populate the destination value field with the copy of the source value, wherein upon executing the executable instruction, the destination container element comprises the copy of the source value occupying the destination value field and conforming to the destination schema element.
8. The media of Claim 5, wherein the plurality of source data-serialization elements comprises at least one source container element having a source value field and a source value occupying the source value field, and wherein the first source data-serialization element is associated with a source schema element defining a source structure for the source value field; wherein the plurality of destination data-serialization elements comprises a destination container element having a destination value field, and wherein the first destination data- serialization element is associated with a destination schema element defining a destination structure for the destination value field, wherein the destination schema element differs from the source schema element; wherein generating the independently executable code comprises: generating an executable instruction that is configured to (a) generate an additional destination schema element corresponding to the source schema element, (b) assign the additional destination schema element to the destination container element, (c) generate a copy of the source value, and (d) populate the destination value field with the copy of the source value, wherein upon executing the executable instruction, the destination container element is associated with the additional destination schema element defining the destination structure for the destination value field, and the copy of the source value conforming to the additional destination schema element occupies the destination value field.
9. The media of any of the preceding Claims, wherein the operations further comprise: receiving a second user input indicating a second proposed mapping of a second destination data- serialization element, of the plurality of destination data-serialization elements, with a second source data-serialization element of the plurality of source data-serialization elements; responsive to receiving the second user input: determining that the second proposed mapping satisfies one or more mapping rules; and responsive to determining that the second proposed mapping satisfies the one or more mapping rules: generating and storing a second mapping expression that defines a second mapping association between the second destination data-serialization element and the second source data-serialization element; and presenting, in the mapping region of the GUI, a second mapping element representing the second mapping association between the second destination data-serialization element and the second source data- serialization element.
10. The media of Claim 9, wherein the one or more mapping rules comprise at least one of: a first mapping rule that prohibits mapping of a source container element with a destination container element when the destination container element is incongruent with the source container element; a second mapping rule that prohibits mapping of a source schema element with a destination schema element when the destination schema element is incongruent with the source schema element; or a third mapping rule that prohibits mapping of a source container element with a destination container element when the destination container element has a destination data structure defined by a destination schema element that is incongruent with a source schema element that defines a source data structure of the source container element.
11. The media of any of the preceding Claims, wherein the operations further comprise: receiving a second user input indicating a second proposed mapping of a second destination data- serialization element, of the plurality of destination data-serialization elements, with a second source data-serialization element of the plurality of source data-serialization elements; responsive to receiving the second user input: determining that the second proposed mapping fails at least one of one or more mapping rules; and responsive to determining that the second proposed mapping fails at least one of the one or more mapping rules: presenting in the GUI, a mapping error object indicating that the second proposed mapping fails at least one of the one or more mapping rules.
12. The media of any of the preceding Claims, wherein the operations further comprise: presenting in the GUI, at least one of: a source mapping line between the first source data-serialization element and the first mapping element, and a destination mapping line between the first mapping element and the first destination data-serialization element; or a mapping line between the first source data-serialization element and the first destination data-serialization element.
13. The media of any of the preceding Claims, wherein the plurality of source data-serialization elements comprises at least one of: a source schema element or a source object element; or wherein the plurality of destination data-serialization elements comprise at least one of: a destination schema element or a destination object element.
14. The media of any of the preceding Claims, wherein the first source data-serialization element is a first source schema element and wherein the first destination data-serialization element is a first destination schema element, wherein the first mapping association is between the first source schema element and the first destination schema element; and wherein the operations further comprise, responsive to receiving the user input: determining a first source container element, of the plurality of source data-serialization elements, having a first data structure defined by the first source schema element; determining a first destination container element, of the plurality of destination data- serialization elements, having a second data structure defined by the first destination schema element; generating a second mapping expression that defines a second mapping association between the first source container element and the first destination container element; and presenting in the mapping region of the GUI, a second mapping element representing the second mapping association between the first source container element and the first destination container element.
15. The media of any of the preceding Claims, wherein the first source data-serialization element is a first source container element and wherein the first destination data-serialization element is a first destination container element, wherein the first mapping association is between the first source container element and the first destination container element; and wherein the operations further comprise, responsive to receiving the user input: determining a first source schema element, of the plurality of source data-serialization elements, defining a first data structure of the first source container element; determining a first destination schema element, of the plurality of destination data- serialization elements, defining a second data structure of the first destination container element; generating a second mapping expression that defines a second mapping association between the first source schema element and the first destination schema element; and presenting in the mapping region of the GUI, a second mapping element representing the second mapping association between the first source schema element and the first destination schema element.
16. A method comprising operations as recited in any of Claims 1-15.
17. A system comprising at least one device including a hardware processor, the system being configured to perform operations as recited in any of Claims 1-15.
18. A system comprising means for performing operations as recited in any of Claims 1-15.
19. A computer program product, comprising computer program/instructions which, when executed by a processor, cause the processor to perform operations as recited in any of Claims 1-15.

Description

PATENT COOPERATION TREATY PATENT APPLICATION FOR MAPPING DATA-SERIALIZ ATION ELEMENTS BETWEEN A SOURCE AND A DESTINATION INVENTORS: SUNITHA ALLI THOMAS HORA APPLICANT: ORACLE INTERNATIONAL CORPORATION 500 ORACLE PARKWAY REDWOOD SHORES, CA 94065 TECHNICAL FIELD [0001] The present disclosure relates to mapping data-serialization elements between a source and a destination. BACKGROUND [0002] Serialization formats or data interchange formats may be used to represent structured data in a standardized way, allowing for transmission, storage, and consumption by different systems and programming languages. The structured data in connection with a serialization format or data interchange format may be represented by data-serialization elements. The structured data may be transferred from a source to a destination by mapping data serialization elements associated with the destination to data serialization elements associated with the source. [0003] The content of this background section should not be construed as prior art merely by virtue of its presence in this section. BRIEF DESCRIPTION OF THE DRAWINGS [0004] The embodiments are shown by way of example and not by way of limitation in the figures of the accompanying drawings. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and they mean at least one. In the drawings: [0005] FIG. 1A illustrates an example system that includes a data repository and a data- serialization element management system in accordance with one or more embodiments; [0006] FIGS. 1B-1D illustrate an example user device interface of the system of FIG. 1A, including a data-serialization mapping interface, in accordance with one or more embodiments; [0007] FIG. IE illustrates further aspects of the example system of FIG. 1A, including an integration server for transforming source payloads associated with a source computing system to destination payloads associated with a destination computing system; [0008] FIG. 2A illustrates example operations that may be performed by the system, including operations associated with generating mapping expressions that define mapping associations between data-serialization elements and presenting mapping elements representing the mapping expressions in a user device interface, in accordance with one or more embodiments; [0009] FIG. 2B illustrates example operations that may be performed by the system, including operations associated with generating data-serialization elements for inclusion in mapping expressions, in accordance with one or more embodiments; [0010] FIG. 2C illustrates example operations that may be performed by the system, including operations associated with updating values for data-serialization elements and displaying updated values computed from mapping expressions that define mapping associations between the data-serialization elements with updated values, in accordance with one or more embodiments; [0011] FIGS. 3A-3C illustrate example features of a data-serialization element mapping interface, including features associated with generating mapping expressions and presenting mapping elements, in accordance with one or more embodiments; [0012] FIG. 3D illustrates example features of a data-serialization element mapping interface, including features associated with generating data-serialization elements for inclusion in mapping expressions, in accordance with one or more embodiments; [0013] FIGS. 3E-3H illustrate further example features of a data-serialization element mapping interface, including further features associated with generating data-serialization elements for inclusion in mapping expressions, in accordance with one or more embodiments; and [0014] FIG. 31 illustrates example features of a data-serialization element mapping interface, including features associated with updating values for data-serialization elements, in accordance with one or more embodiments; [0015] FIG. 4 shows a block diagram that illustrates a computer system in accordance with one or more embodiments. DETAILED DESCRIPTION [0016] In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding. Detailed examples are described below for purposes of clarity. One or more embodiments may be practiced without these specific details. Components and/or operations described below should be understood as one specific example which may not be applicable to certain embodiments. Features described in one embodiment may be combined with features described in a different embodiment. In some examples, well-known structures and devices are described with reference to a block diagram form in order to avoid unnecessarily obscuring the present invention. Components and/or operations described below should not be construed as limiting the scope of any of the claims. 1. GENERAL OVERVIEW 2. SERIALIZED DATA MANAGEMENT SYSTEM