Abstract: Techniques and solutions are provided for organizing and controlling access/operations with respect to computing objects, such as a definition of a computing object or data associated with an instance of a defined computing object. A collection of computing objects is associated with a namespace, the namespace having a namespace identifier. At least a first set of access rights is associated with the namespace, such as access rights of a first tenant, representing a computing environment to which the computing objects of the namespace may be deployed. The access rights specify permitted/prohibited operations with respect to the computing objects, such as whether the computing objects are available on a read-only basis or whether create, update, or delete operations are also allowed. A namespace can have multiple tenant accessors, where different tenants can have different access rights for a given namespace.

Abstract: Techniques and solutions for defining clusters of data objects are provided. An anchor data object for the cluster is determined. The anchor data object is associated with a semantic concept. Other data objects included in the cluster are also associated with the semantic concept. One or more data objects that are related to the anchor data object are added to the cluster. Additional data objects, related to the one or more other data objects, or to other data objects of the additional data objects, are added to the cluster. The cluster is associated with a name, which can be used to identify data objects that are part of the cluster. The cluster can be used for a variety of purposes, including defining a replication task, for the creation of an application program interface, or for defining a deployment task that deploys at least a portion of cluster data objects.

Abstract: Techniques and solutions are described for defining and deploying application content. Content, such as objects, can be created in a repository defined for a first application. A package can be defined based at least in part on the objects for use in a computing environment only requiring the first application. A second package can be defined based at least in part on the objects for use in a computing environment in which both the first application and a second application are available. Content can be moved between repositories defined for a single application and repositories defined for multiple applications. Content can be added to, or removed from, a client computing system as applications available on a client computing system change.

Abstract: Techniques and solutions are described for providing flexible access to data during execution of a data access request. Multiple instances of a data artifact are created, where different instances of the data artifact provide access to different data sources having data associated with the data access request. When a data access request is executed, a particular data artifact instance can be used during execution of the data access request. In some cases, switching logic can be used to determine which data artifact instance is to be used in executing the data access request. Also described are technologies for facilitating creation of data artifact instances corresponding to a modelling artifact.

Abstract: Techniques and solutions are described for storing and processing metadata. A target system sends a request to a source system to identify extensions to one or more specified database artefacts. The source system identifies one or more software objects that include metadata extensions to the one or more specified database artefacts and sends at least a portion of such metadata elements to the target system in response to the request. The source system can expose APIs, such as APIs in a standard format, to the target system to assist in requesting and retrieving metadata from the source system.

Abstract: Techniques and solutions are provided for maintaining data separation, such as when consolidating data for two instances of a data artifact. If data separation is not maintained, it may not be possible, or as easy, to determine from which instance particular data came, which can also limit filtering/selectively searching data for a particular instance. The present disclosure addresses this issue by providing a consolidation data artifact. For particular sets of data in the consolidation data artifact, the consolidation artifact maintains the data in association with an identifier of the instance that serves as the source of the data.

Abstract: The present disclosure provides techniques and solutions for integrating data from different instances of a data source, such as a data artifact. That is, in some cases data may be disjoint, or it may overlap in whole or part. How data should be integrated can depend on whether data overlaps, or a type or extent of overlap. An artifact that consumes data can be integrated to indicate how data from underlying instances of a data source should be integrated, including when this consuming artifact requests data indirectly from a consolidation artifact. A search against the consuming artifact can be modified based on configuration information in the consuming artifact indicating how or if data from multiple instances of the data source should be integrated.

Abstract: Techniques and solutions are provided for grouping of landscape elements, such as instances of software applications or application content. Landscape elements of the same or different types can be included in groups, where the groups can also be used to exclude other landscape elements from a group. In one implementation, a consolidation landscape element can be generated to consolidate content of two or more landscape elements in a group, and having a same type. In another implementation, grouping of landscape elements can be used to control the installation of cross-type content. In a given landscape, grouping can be used to control either of both of the generation of consolidation landscape elements or the installation of cross-type content.

Abstract: Techniques and solutions are provided for grouping of applications, including application content, or other content useable by a computer-implemented process. In particular, a consolidation space is provided as a lightweight mechanism for this purpose. Identifiers are received for multiple landscape elements, where a landscape element can be an application, application content, or other content. A given landscape element has a type and has one or more artifacts. A consolidation space is generated for at least first and second landscape elements having a first type. A consolidation artifact is generated in the consolidation space, where the consolidation artifact references respective first and second instances of a first artifact in the first and second landscape elements.

Abstract: Techniques and solutions are described for facilitating the reuse of text translations. For a first instance of text in a human language, a first logical pointer value is assigned to the first instance of the text, pointing to a target having at least a first translation for the text. A second instance of the text is received. If only the first instance is present, the first logical pointer value is assigned to the second instance. If a third instance of the text is present, associated with a second translation and a second logical pointer value, user or process input is received determining whether the first logical pointer value or the second logical pointer value is assigned to the second instance. Context information can be provided to a user to help determine whether the second instance should be associated with the first translation or the second translation.

Abstract: Techniques for reducing CPU consumption in a federated search are disclosed. In some example embodiments, a computer-implemented method comprises determining an initial search scope by selecting a subset of searchable resources from a plurality of searchable resources based on interaction data of a user, with the initial search scope being defined by the selected subset of searchable resources, and the interaction data indicating online activity of the user directed towards past search results of past search queries submitted by the user. A federated search for a current search query is then performed using the initial search scope, with the federated search for the current search query being restricted to only the subset of searchable resources, and current search results for the current search query are generated based on the performing of the federated search.

Abstract: Techniques and solutions are described for providing flexible access to data during execution of a data access request. Multiple instances of a data artifact are created, where different instances of the data artifact provide access to different data sources having data associated with the data access request. When a data access request is executed, a particular data artifact instance can be used during execution of the data access request. In some cases, switching logic can be used to determine which data artifact instance is to be used in executing the data access request. Also described are technologies for facilitating creation of data artifact instances corresponding to a modelling artifact.

Abstract: Techniques and solutions are described for propagating extensions to data artifacts, such as data artifacts defining objects in a physical or virtual data model. One or more data artifacts are identified that are related to a first data artifact. One or more extension elements of the first data artifact are analyzed for propagation to at least one data artifact of the one or more data artifacts. Analyzing whether an extension element should be propagated can include analyzing a type of the extension element, a type of operation or context in which the extension element is used, or how the at least one data artifact refers to, uses, or incorporates the first data artifact, including particular elements thereof. The results of the analysis are compared with various rules. Extension elements are propagated automatically, manually upon user approval (e.g., propagation recommendations are provided), or in a semi-automated manner.

Abstract: Techniques and solutions are described for defining and deploying application content. Content, such as objects, can be created in a repository defined for a first application. A package can be defined based at least in part on the objects for use in a computing environment only requiring the first application. A second package can be defined based at least in part on the objects for use in a computing environment in which both the first application and a second application are available. Content can be moved between repositories defined for a single application and repositories defined for multiple applications. Content can be added to, or removed from, a client computing system as applications available on a client computing system change.

Abstract: Techniques and solutions are described for retaining names for metadata elements, such as when metadata is imported, converted to a different format, or used with a system that may have restrictions on naming different than a system on which the metadata is created. Metadata includes a plurality of metadata elements, including a first metadata element associated with a first name. A second name is received for the first metadata element. The second name is assigned to the first metadata element. An association is created between the renamed first metadata element and the first name.

Abstract: Techniques and solutions are described for storing and processing metadata. A target system sends a request to a source system to identify extensions to one or more specified database artefacts. The source system identifies one or more software objects that include metadata extensions to the one or more specified database artefacts and sends at least a portion of such metadata elements to the target system in response to the request. The source system can expose APIs, such as APIs in a standard format, to the target system to assist in requesting and retrieving metadata from the source system.

Abstract: Techniques and solutions are described for storing and retrieving metadata for database artefacts. A client request is received that includes a relevancy identifier. The relevancy identifier is useable to determine a subset of metadata that should be provided in response to the request. Metadata, including in metadata objects or database artefacts, can be reviewed to determine whether it is relevant to the request, such as if the metadata is associated with the relevancy identifier. Different requests from the same client can specify different relevancy identifiers, as, for example, a first set of metadata may be relevant to one client process and another set may be relevant to another client process. While some metadata can be specific to a particular client, at least some of the metadata can be accessed by multiple clients, and at least in some cases different clients can specify the same relevancy identifier.

Abstract: Techniques and solutions are described for storing and processing metadata, including to instantiate database artefacts at a target system based on metadata for database artefacts maintained at a source system. The target system can query the source system for metadata associated with database artefacts of the source system. The target system can instantiate database artefacts based on such metadata. The database artefacts of the target system are linked to corresponding database artefacts of the source system, such as by associating a database artefact of the target system with an API useable to obtain data or metadata from the source system for a corresponding database artefact of the source system. The target system obtains additional data or metadata for a database artefact of the target system using a corresponding API.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for automatic database configuration. One example method includes receiving, at a database associated with a data warehouse application, a request to generate a configuration to acquire data objects based on executing calls to corresponding programming interfaces provided by a source application, wherein the programming interfaces are identified in the received instructions and are associated with acquiring the data objects associated with metadata entities defined at the database; in response to the received instructions, configuring the database to automatically execute one or more calls to acquire relevant data for a metadata entity defined at the database, wherein the metadata entity is associated with a section of a first programming interface; and invoking the first programming interface at the source application, wherein invoking the first programming interface results in acquiring the relevant data.

Abstract: The present disclosure relates to computer-implemented methods, software, and systems for importing metadata between applications. One example method includes obtaining, at a data warehouse application, metadata for relevant entities in response to a query defined for querying metadata from a metadata source associated with a source application. A service at the source application is queried to identify a set of programming interfaces associated with the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application. Instructions are generated that can be used to configure the database associated with the data warehouse application to acquire a data object based on executing a call to a corresponding programming interface. The generated instructions are provided to the database to configure the database to automatically execute the call to acquire the data object from the source application.