Database language extended to accommodate entity-relationship models
US-9442977-B2 · Sep 13, 2016 · US
US12086152B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12086152-B2 |
| Application number | US-202117487608-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 28, 2021 |
| Priority date | Jun 17, 2021 |
| Publication date | Sep 10, 2024 |
| Grant date | Sep 10, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method for importing data objects, the method comprising: executing a query for metadata from a metadata source, wherein the query identifies an entity from a list of entities of a service metadata model defined at a metadata service and associated with one or more applications; in response to executing the query, obtaining, at a data warehouse application, query-relevant metadata including metadata for the entity and metadata for relevant entities that are identified as relevant for the query based on a scope function implemented and executed at a source application of the one or more applications, wherein the scope function determines which types of entities are related to the identified entity from the list based on the service metadata model; in response to obtaining the query-relevant metadata, querying a service at the source application to identify a set of programming interfaces associated with the identified entity and the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application; and generating instructions to be used to configure a database associated with the data warehouse application to acquire a data object from the data objects based on executing a call to a corresponding programming interface from the identified set of programming interfaces; and providing the generated instructions to the database to configure the database to automatically execute the call to acquire the data object from the source application. 2. The method of claim 1 , wherein the service at the source application determines the set of programming interfaces based on predefined mapping relationships between metadata entities and programming interfaces defined at the source application. 3. The method of claim 1 , wherein querying the service at the source application includes querying a mapping storage at the source application that defines mappings between metadata entities and sections of programming interfaces. 4. The method of claim 1 , further comprising: providing a mapping storage including mappings between a programming interface and one or more metadata entities defined at a metadata model of a metadata exposure service; and in response to receiving the query for metadata at the metadata exposure service, providing the metadata for the relevant entities in response to the query to the data warehouse application, wherein the service that is queried at the source application in response to the obtained metadata is executing the query based on evaluating the mappings stored at the mapping storage. 5. The method of claim 4 , wherein the data warehouse application accumulates metadata for entities from a set of source applications based on a common metadata exposure service that defines a structure of metadata entities, and wherein the data warehouse application generates a set of configurations synchronized for acquiring data from the set of source applications to configure automatic execution of data gathering at the data warehouse application. 6. A non-transitory, computer-readable medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations, the operations comprising: executing a query for metadata from a metadata source, wherein the query identifies an entity from a list of entities of a service metadata model defined at a metadata service and associated with one or more applications; in response to executing the query, obtaining, at a data warehouse application, query-relevant metadata including metadata for the entity and metadata for relevant entities that are identified as relevant for the query based on a scope function implemented and executed at a source application of the one or more applications, wherein the scope function determines which types of entities are related to the identified entity from the list based on the service metadata model; in response to obtaining the query-relevant metadata, querying a service at the source application to identify a set of programming interfaces associated with the identified entity and the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application; and generating instructions to be used to configure a database associated with the data warehouse application to acquire a data object from the data objects based on executing a call to a corresponding programming interface from the identified set of programming interfaces; and providing the generated instructions to the database to configure the database to automatically execute the call to acquire the data object from the source application. 7. The computer-readable medium of claim 6 , wherein the service at the source application determines the set of programming interfaces based on predefined mapping relationships between metadata entities and programming interfaces defined at the source application. 8. The computer-readable medium of claim 6 , wherein querying the service at the source application includes querying a mapping storage at the source application that defines mappings between metadata entities and sections of programming interfaces. 9. The computer-readable medium of claim 6 , further storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations, comprising: providing a mapping storage including mappings between a programming interface and one or more metadata entities defined at a metadata model of a metadata exposure service; and in response to receiving the query for metadata at the metadata exposure service, providing the metadata for the relevant entities in response to the query to the data warehouse application, wherein the service that is queried at the source application in response to the obtained metadata is executing the query based on evaluating the mappings stored at the mapping storage. 10. The computer-readable medium of claim 9 , wherein the data warehouse application accumulates metadata for entities from a set of source applications based on a common metadata exposure service that defines a structure of metadata entities, and wherein the data warehouse application generates a set of configurations synchronized for acquiring data from the set of source applications to configure automatic execution of data gathering at the data warehouse application. 11. A system comprising a computing device; and a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations, the operations comprising: executing a query for metadata from a metadata source, wherein the query identifies an entity from a list of entities of a service metadata model defined at a metadata service and associated with one or more applications; in response to executing the query, obtaining, at a data warehouse application, query-relevant metadata including metadata for the entity and metadata for relevant entities that are identified as relevant for the query based on a scope function implemented and executed at a source application of the one or more applications, wherein the scope function determines which types of entities are related to the identified entity from the list based on the service metadata model; in response to obtaining the query-relevant metadata, querying a service at the source application to identify a set of programming interfaces associated with the identified entity and the relevant entities for acquiring data
Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title
Object oriented databases · CPC title
between a Database Management System and a front-end application · CPC title
Adding application-functional data or data for application control, e.g. adding metadata · CPC title
Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.