Schema alignment and structural data mapping of database objects
US-2020349129-A1 · Nov 5, 2020 · US
US11853271B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11853271-B2 |
| Application number | US-202016804185-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 28, 2020 |
| Priority date | Nov 18, 2019 |
| Publication date | Dec 26, 2023 |
| Grant date | Dec 26, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, systems, and devices are described that support extensible data mapping. A data mapping server may receive an indication of a source schema for a data source and may receive a user input indicating creation of a custom data object to handle the source schema. The server may create the custom data object based on the user input. The data mapping server may automatically map one or more data fields for a source data object (e.g., based on the source schema) to one or more custom data fields for the custom data object (e.g., based on a custom schema). The server may import a set of data records stored at the data source and may store the data records in a database system according to the custom schema based on the data mapping. The stored custom data objects may be used for segmentation, activation, analysis, or some combination thereof.
Opening claim text (preview).
What is claimed is: 1. A method for data mapping, comprising: importing a plurality of data records from a first data source and a second data source to a database system in accordance with a first source data schema and a second source data schema based on performing an authentication procedure which includes receiving authentication information for the first data source and the second data source from a user device; storing the plurality of data records in a data lake of the database system in accordance with a custom data schema different from the first source data schema and the second source data schema; creating a custom data object that includes data from the plurality of data records stored in accordance with the custom data schema, wherein creating the custom data object comprises using a natural language processing (NLP) model to map fields of two or more data records associated with at least one standard data object and at least one hybrid data object from different data sources to fields of the custom data object based on determining that the two or more data records correspond to a same user; receiving, from a cloud client, a query that includes a search criterion associated with the custom data object; and querying the data lake of the database system to retrieve data from the at least one standard data object and the at least one hybrid data object that are mapped to the custom data object based at least in part on the search criterion associated with the custom data object. 2. The method of claim 1 , further comprising: receiving, at the database system, a second user input indicating a mapping between a data field from the first data source and a custom data field of the custom data object; and updating, in the database system, the plurality of data records stored according to the custom data schema based at least in part on the second user input, wherein updating the plurality of data records comprises mapping a plurality of values from the plurality of data records to the custom data field in accordance with the mapping. 3. The method of claim 1 , further comprising: receiving, at the database system, an indication of the second source data schema for the second data source; receiving, at the database system, a second user input indicating the custom data object; and mapping, by the database system, data fields from the second data source to one or more custom data fields of the custom data object based at least in part on the second source data schema. 4. The method of claim 1 , further comprising: receiving, at the database system, an indication of a third source data schema that is different from the first source data schema and the second source data schema; receiving, at the database system, a second user input indicating a standard data object; and receiving, at the database system, a third user input indicating a mapping between one or more data fields of the third source data schema and one or more standard data fields of the standard data object. 5. The method of claim 1 , wherein creating the custom data object comprises: receiving, at the database system, a second user input; and modifying, by the database system, a custom data field of the custom data object based at least in part on the second user input. 6. The method of claim 1 , further comprising: fetching the first source data schema from the first data source. 7. The method of claim 1 , further comprising: receiving, at the database system, a second user input indicating the second source data schema for the second data source. 8. The method of claim 1 , further comprising: performing data segmentation, activation, analysis, or a combination thereof on the plurality of data records based at least in part on storing the plurality of data records according to the custom data schema. 9. The method of claim 1 , further comprising: querying the plurality of data records using the search criterion; identifying a connection between the custom data object and a standard data object based at least in part on querying the plurality of data records; retrieving, based at least in part on the connection, a data field for the standard data object; and transmitting, in accordance with the query, an indication of the data field. 10. The method of claim 1 , further comprising: transmitting, for display at a user interface, an indication of a mapping for the custom data object. 11. The method of claim 1 , further comprising: storing, in the database system, a data stream from the first data source; importing, from the first data source, a second plurality of data records associated with the data stream; and storing, in the database system, the second plurality of data records according to the custom data schema. 12. The method of claim 1 , further comprising: receiving, at the database system and from a user device, a second user input indicating the second data source; identifying the authentication procedure for the second data source; transmitting, to the user device, a request for the authentication information associated with the authentication procedure for the second data source; and receiving, at the database system and from the user device, the authentication information, wherein an indication of the second source data schema for the second data source is received after performing the authentication procedure for the second data source using the authentication information. 13. The method of claim 1 , further comprising: compressing and encrypting the plurality of data records to reduce system load and increase system security, wherein the plurality of compressed, encrypted data records are stored in the data lake associated with the database system. 14. The method of claim 2 , wherein: the data field is initially unmapped to the custom data field; and the plurality of values are preserved in the database system after storing the plurality of data records at the database system. 15. The method of claim 2 , wherein updating the plurality of data records is based at least in part on storing the plurality of data records according to the custom data schema. 16. The method of claim 4 , further comprising: receiving, at the database system, a fourth user input indicating a creation of a custom data field for the standard data object and a mapping from a data field of the third source data schema to the custom data field for the standard data object; creating the custom data field for the standard data object based at least in part on the fourth user input; and mapping, by the database system, values from the third source data schema to the custom data field for the standard data object based at least in part on the fourth user input. 17. The method of claim 5 , wherein modifying the custom data field of the custom data object comprises: changing, by the database system, a label of the custom data field, a data type of the custom data field, a property of the custom data field, or a combination thereof. 18. The method of claim 11 , further comprising: receiving, at the database system, a second user input indicating a refresh schedule for the first data source, wherein the second plurality of data records are imported in accordance with the refresh schedule. 19. An apparatus for data mapping, comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: import a plurality of data records from a first da
with details for schema evolution support · CPC title
Updates performed during online database operations; commit processing · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
the source of the received data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.