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

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

Abstract: An application may support ingestion of data to a data server. A user may identify the data source, and the server may determine a connector corresponding to the identified data source. The server may support a plurality of connectors for data ingestion. Based on the selected source, the user may select a data channel type, where the data channel type is associated with one or more packaged data sets that include different data set types. The server may then ingest the data set using the determined connector. The application may further support mapping of source and target attributes, custom mapping, and transformation functions.

Abstract: Embodiments of the invention are generally related to semantic search and service metadata repositories, particularly with regards to methods and systems for performing a semantic asset search in a service metadata repository. One embodiment includes identifying service metadata assets with similar metadata, relationships, and categorizations to the service metadata assets with the most relevant keywords and identifying service metadata assets have been used in conjunction with the one or more selected service metadata assets.

Abstract: Embodiments of the invention are generally related to Ontologies and service metadata repositories, and particularly related to systems and methods for transforming Ontologies into service metadata assets in a service metadata repository. One embodiment includes a plug-in from an ontology development tool communicating to an application programming interface for a service metadata repository. One embodiment includes transforming an ontology from an ontology web language file in an ontology development tool into a service metadata asset in the service metadata repository.

Abstract: Embodiments of the invention are generally related to semantic search and service metadata repositories, particularly with regards to methods and systems for performing a semantic asset search in a service metadata repository. One embodiment includes identifying service metadata assets with similar metadata, relationships, and categorizations to the service metadata assets with the most relevant keywords and identifying service metadata assets have been used in conjunction with the one or more selected service metadata assets.