Abstract: The use of multiple logical data models to expose a data storage system. Each logical data model may expose the data storage system using a semantic mapping set that maps sets of entities or attributes of the respective logical data model to corresponding sets of entities or attributes of the physical data model or perhaps directly to the data storage system itself. Each logical data model might serve a different vertical, and have a particular modelling notation selected by the logical data model provider. The mapping may also translate different logical modelling notations into a common logical modelling notation for use in communicating with the physical data model. The system may account for the lifecycle of the logical data model including birth or retirement of logical data model entities, and merging or splitting of logical data models.

Abstract: The present invention extends to methods, systems, and computer program products for managing data-driven services. Aspects of the invention include a platform for data services. The platform manages data and associated data models holistically together. The platform enables and integrates data-driven services through a service model. The platform transforms data into information and information into intelligence and exposes insights to services. The platform allows for data and service sharing across domains.

Abstract: A version manager that manages multiple versions of a logical data model. Each version of the logical data model exposes a data storage system using a corresponding semantic mapping set that for multiple logical data model entities, maps at least the logical data model entity to at least a corresponding physical data model entity of the data storage system. The logical data model itself may consistent of multiple constituent logical data models, each used for a different vertical to expose the same underlying storage system. The version manager corresponds each of one or more data consumers of the data storage system with a version of the logical data model. Accordingly, when requests come in from a particular data consumer, the corresponding version of the logical data model is used.

Abstract: Model queries that identify and direct to retrieve from one or more logical data models. A model query engine interprets the model queries, and interacts accordingly with the identified logical data model(s) specified in the respective model query. The interaction may be in the form of respective logical data model queries to the respective logical data models, and results are returned in the modeling notation of that respective logical data model. The model query engine may then use the results to interact with a physical data model, after potentially translating the modeling notation into a common notation used by a physical data model. The interaction with the physical data model may be in the form of a physical data model query, with the results therefrom being assembled into a result set. Accordingly, queriers may formulate queries by referencing models, without having to understand the schema of the data source.

Abstract: The use of a data model index for assisting in efficient response to a data model query. The data model query identifies the data model itself and references the schema of the data model, rather than referencing the schema of the underlying data source. The index assists by correlating previous model queries on the data model and associated response to those previous model queries. Accordingly, if a similar model query is encountered, the response from the previous model query may still be considered fresh, the index may be used to more efficiently retrieve the results for the similar model query. A data management system may include multiple data models, each having a corresponding data model index.

Abstract: The present invention extends to methods, systems, and computer program products for managing data ingestion. Aspects of the invention include a pluggable architecture channel service (e.g., a push/pull channel service) to ingest raw data. Aspects of the invention also include a pluggable architecture formatter to convert ingested raw data into a common format, such as, for example, key value pairs. Aspects of the invention also include an EAV storage with functionality allowing consumers to define multiple entities on (and spanning) ingested data sets. Accordingly, data can be ingested without data loss, without having to define extraction logic, and without having to define a storage schema.

Abstract: A version manager that manages multiple versions of a logical data model. Each version of the logical data model exposes a data storage system using a corresponding semantic mapping set that for multiple logical data model entities, maps at least the logical data model entity to at least a corresponding physical data model entity of the data storage system. The logical data model itself may consistent of multiple constituent logical data models, each used for a different vertical to expose the same underlying storage system. The version manager corresponds each of one or more data consumers of the data storage system with a version of the logical data model. Accordingly, when requests come in from a particular data consumer, the corresponding version of the logical data model is used.

Abstract: The present invention extends to methods, systems, and computer program products for managing data ingestion. Aspects of the invention include a pluggable architecture channel service (e.g., a push/pull channel service) to ingest raw data. Aspects of the invention also include a pluggable architecture formatter to convert ingested raw data into a common format, such as, for example, key value pairs. Aspects of the invention also include an EAV storage with functionality allowing consumers to define multiple entities on (and spanning) ingested data sets. Accordingly, data can be ingested without data loss, without having to define extraction logic, and without having to define a storage schema.

Abstract: Model queries that identify and direct to retrieve from one or more logical data models. A model query engine interprets the model queries, and interacts accordingly with the identified logical data model(s) specified in the respective model query. The interaction may be in the form of respective logical data model queries to the respective logical data models, and results are returned in the modeling notation of that respective logical data model. The model query engine may then use the results to interact with a physical data model, after potentially translating the modeling notation into a common notation used by a physical data model. The interaction with the physical data model may be in the form of a physical data model query, with the results therefrom being assembled into a result set. Accordingly, queriers may formulate queries by referencing models, without having to understand the schema of the data source.

Abstract: The present invention extends to methods, systems, and computer program products for managing data-driven services. Aspects of the invention include a platform for data services. The platform manages data and associated data models holistically together. The platform enables and integrates data-driven services through a service model. The platform transforms data into information and information into intelligence and exposes insights to services. The platform allows for data and service sharing across domains.

Abstract: The use of multiple logical data models to expose a data storage system. Each logical data model may expose the data storage system using a semantic mapping set that maps sets of entities or attributes of the respective logical data model to corresponding sets of entities or attributes of the physical data model or perhaps directly to the data storage system itself. Each logical data model might serve a different vertical, and have a particular modelling notation selected by the logical data model provider. The mapping may also translate different logical modelling notations into a common logical modelling notation for use in communicating with the physical data model. The system may account for the lifecycle of the logical data model including birth or retirement of logical data model entities, and merging or splitting of logical data models.

Abstract: The use of a data model index for assisting in efficient response to a data model query. The data model query identifies the data model itself and references the schema of the data model, rather than referencing the schema of the underlying data source. The index assists by correlating previous model queries on the data model and associated response to those previous model queries. Accordingly, if a similar model query is encountered, the response from the previous model query may still be considered fresh, the index may be used to more efficiently retrieve the results for the similar model query. A data management system may include multiple data models, each having a corresponding data model index.

Abstract: An automated workflow services system can provide guidance to a user via constraints. A wide variety of constraint types are supported, including constraints based on identity, action type, and the like. Relative and negative constraints can be supported. Constraints for transitive actions can also be supported. Constraints can be based on any of a variety of facts, which can be drawn from sources outside the workflow services system.