Abstract: The present invention extends to methods, systems, and computer program products for forming data responsive to a query. Responding to a query can include selecting data views on top of data sources. A data catalog stores data elements from different data sources and stores links between data elements from the different data sources. A view can be selected for a query based on one or more of: classification of data included in the data catalog or prior usage of data included in the data catalog. A selected data view is populated with data elements from the data catalog using the links to determine that data elements spanning multiple data sources satisfy the query. The data catalog can be used to identify relationships between data elements from different data sources that would not otherwise be identified.

Abstract: Embodiments described herein are directed to methods, and systems for generating event processing language code in a development environment using an event processing compiler. A query in event processing language is received in a development environment. The query can be associated with sample data from input files or an input data source. An event processing compiler compiles the query, where the compiler transforms the query from event processing language code to a development environment script language code. In particular, the event processing language code transforms the code based on event processing attributes that are intricately aligned in syntax and semantic between the event processing language and the development environment script language. The query as a development environment script is executed using sample data.

Abstract: The present invention extends to methods, systems, and computer program products for forming data responsive to a query. Responding to a query can include selecting data views on top of data sources. A data catalog stores data elements from different data sources and stores links between data elements from the different data sources. A view can be selected for a query based on one or more of: classification of data included in the data catalog or prior usage of data included in the data catalog. A selected data view is populated with data elements from the data catalog using the links to determine that data elements spanning multiple data sources satisfy the query. The data catalog can be used to identify relationships between data elements from different data sources that would not otherwise be identified.

Abstract: The present invention extends to methods, systems, and computer program products for creating data views. Embodiments of the invention allow automatic creation of data views/projections on top of data sources. A view can be created on one data source (by looking at one or multiple data elements within the data source) or by looking at multiple data sources (of the same or different data types) and combining elements into a view. Data sources can be any kind of data source, including but not limited to: databases, files, and Web services. Views can be picked from a set of predefined views, picked from views of another tenant (either statically or using fuzzy logic), selected based on data element classifications and/or data element relationship classifications, selected based on data usage (e.g., by looking at logs), etc.

Abstract: Embodiments are directed to providing access to supplemental query data that is relevant to a data query. In one scenario, a computer system receives an input indicating that a data query is to be processed, where the input provides various search criteria. The computer system then generates the data query according to the search criteria in the received input. The computer system further sends the data query to a second computer system which is configured to process the data query and receives the results of the data query. The results indicate that additional data elements relevant to the search criteria have been identified. The computer system then displays an indication of various steps that are to be taken in order to access the identified additional data elements.

Abstract: Embodiments are directed to establishing a metadata repository that aggregates metadata for a plurality of data sources, inferring data source metadata at a metadata repository and to providing recommendations to data managers based on aggregated inputs. In one scenario, a computer system establishes a reference to one or more data sources, where each data source includes data elements. The computer system receives a data request for specified data elements stored on the data sources and accesses the established references to determine which data source the specified data elements are stored on. The computer system then retrieves at least one of the specified data elements from its determined data source and sends the retrieved data elements to a specified computer system, along with an indication of additional data elements that are relevant to the received data request, and a further indication of how those additional data elements are to be accessed.

Abstract: Content providers define a set of scenarios that are addressed by their datasets. The scenarios include user-friendly, human-readable attributes such as a title, description, and visualization. The scenarios may also include a technical description that can be used to generate sample queries that can then be executed against the dataset. The technical description may be machine translated to arbitrary data querying protocols while maintaining the semantic meaning of the query. A user interface may be provided to allow users to intuitively generate the scenarios. In one embodiment, an extensible framework provides for the creation of protocol-specific translation plug-ins that are used to generate implementations of the scenario suitable for selected protocols. Known market-relevant translator plug-ins may also be implemented.

Abstract: Content providers define a set of scenarios that are addressed by their datasets. The scenarios include user-friendly, human-readable attributes such as a title, description, and visualization. The scenarios may also include a technical description that can be used to generate sample queries that can then be executed against the dataset. The technical description may be machine translated to arbitrary data querying protocols while maintaining the semantic meaning of the query. A user interface may be provided to allow users to intuitively generate the scenarios. In one embodiment, an extensible framework provides for the creation of protocol-specific translation plug-ins that are used to generate implementations of the scenario suitable for selected protocols. Known market-relevant translator plug-ins may also be implemented.

Abstract: Embodiments described herein are directed to methods, and systems for generating event processing language code in a development environment using an event processing compiler. A query in event processing language is received in a development environment. The query can be associated with sample data from input files or an input data source. An event processing compiler compiles the query, where the compiler transforms the query from event processing language code to a development environment script language code. In particular, the event processing language code transforms the code based on event processing attributes that are intricately aligned in syntax and semantic between the event processing language and the development environment script language. The query as a development environment script is executed using sample data.

Abstract: The present invention extends to methods, systems, and computer program products for creating data views. Embodiments of the invention allow automatic creation of data views/projections on top of data sources. A view can be created on one data source (by looking at one or multiple data elements within the data source) or by looking at multiple data sources (of the same or different data types) and combining elements into a view. Data sources can be any kind of data source, including but not limited to: databases, files, and Web services. Views can be picked from a set of predefined views, picked from views of another tenant (either statically or using fuzzy logic), selected based on data element classifications and/or data element relationship classifications, selected based on data usage (e.g., by looking at logs), etc.

Abstract: Embodiments are directed to providing access to supplemental query data that is relevant to a data query. In one scenario, a computer system receives an input indicating that a data query is to be processed, where the input provides various search criteria. The computer system then generates the data query according to the search criteria in the received input. The computer system further sends the data query to a second computer system which is configured to process the data query and receives the results of the data query. The results indicate that additional data elements relevant to the search criteria have been identified. The computer system then displays an indication of various steps that are to be taken in order to access the identified additional data elements.

Abstract: Embodiments are directed to establishing a metadata repository that aggregates metadata for a plurality of data sources, inferring data source metadata at a metadata repository and to providing recommendations to data managers based on aggregated inputs. In one scenario, a computer system establishes a reference to one or more data sources, where each data source includes data elements. The computer system receives a data request for specified data elements stored on the data sources and accesses the established references to determine which data source the specified data elements are stored on. The computer system then retrieves at least one of the specified data elements from its determined data source and sends the retrieved data elements to a specified computer system, along with an indication of additional data elements that are relevant to the received data request, and a further indication of how those additional data elements are to be accessed.

Abstract: Embodiments described herein are directed to generating and displaying a user interface that allows data managers to provide supplemental metadata for data sources. In one scenario, a computer system generates a UI that shows an indication of data elements to which a metadata catalog is linked. The metadata catalog includes references to different data sources that store data elements. The UI receives an input indicating that metadata for at least one of the data sources is to be modified. The modification includes providing additional metadata for a specified data source, providing documentation for a specified data source and/or providing an entry point for an access request workflow. The computer system performs the received data source metadata modification according to the received input and, upon determining that the metadata has been modified, displays the updated metadata for the data sources in the UI.

Abstract: Content providers define a set of scenarios that are addressed by their datasets. The scenarios include user-friendly, human-readable attributes such as a title, description, and visualization. The scenarios may also include a technical description that can be used to generate sample queries that can then be executed against the dataset. The technical description may be machine translated to arbitrary data querying protocols while maintaining the semantic meaning of the query. A user interface may be provided to allow users to intuitively generate the scenarios. In one embodiment, an extensible framework provides for the creation of protocol-specific translation plug-ins that are used to generate implementations of the scenario suitable for selected protocols. Known market-relevant translator plug-ins may also be implemented.