Abstract: A document may be received as part of a request to identify similar documents in a collection of documents. However, the received document and the documents in the collection may have different schemas or formats. To provide semantic context to the search and allow similarity scores to be generated between different document types, a configuration may be accessed that defines how to generate queries from one schema into another schema. The configuration may map queries between different fields in both schemas. Results of the multiple queries can be combined to generate a weighted combination for each document that can be used as a similarity score between different document types.

Abstract: One or more embodiments interpret a configuration graph to efficiently and optimally construct requests and fetch data from a datastore. The values of objects of a requested data type are used to generate additional queries for pre-fetching data from the datastore. Specifically, the values are used to query for and retrieve a corresponding subset of objects of another, related data type. Recursively querying for and retrieving objects of related data types based on already retrieved objects builds a data cache of relevant objects. The cached, relevant objects may be useful in subsequent queries that are likely to follow the initial query.

Abstract: One or more embodiments interpret a configuration graph to efficiently and optimally construct requests and fetch data from a datastore. The values of objects of a requested data type are used to generate additional queries for pre-fetching data from the datastore. Specifically, the values are used to query for and retrieve a corresponding subset of objects of another, related data type. Recursively querying for and retrieving objects of related data types based on already retrieved objects builds a data cache of relevant objects. The cached, relevant objects may be useful in subsequent queries that are likely to follow the initial query.

Abstract: In one embodiment, change handling in mobile client applications may be facilitated by intermediate storage of changes using a data-provider-agnostic change object schema. An input on a mobile device that indicates a create, update, or delete action on a data object stored in a remote datastore is received. In response to receiving the input, a description of the action on the data object in a syntax that is agnostic as to type of remote service provider used for interacting with the remote datastore is created. The description of the action to a syntax of the first remote service provider is converted to compose a command configured to cause a first remote service provider to execute the action. The command is transmitted over a network to the first remote service provider to cause the action to be performed on the data object in the remote datastore.

Abstract: One or more embodiments interpret a configuration graph to efficiently and optimally construct requests and fetch data from a datastore. The values of objects of a requested data type are used to generate additional queries for pre-fetching data from the datastore. Specifically, the values are used to query for and retrieve a corresponding subset of objects of another, related data type. Recursively querying for and retrieving objects of related data types based on already retrieved objects builds a data cache of relevant objects. The cached, relevant objects may be useful in subsequent queries that are likely to follow the initial query.