2013
DOI: 10.1007/978-3-642-37450-0_5
|View full text |Cite
|
Sign up to set email alerts
|

Semantic Data Warehouse Design: From ETL to Deployment à la Carte

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
23
0
1

Year Published

2014
2014
2021
2021

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 31 publications
(24 citation statements)
references
References 19 publications
0
23
0
1
Order By: Relevance
“…Even though we notice the lower requirement for the cleanness and constraintness of output data in the next generation BI setting (see Table 2), which would typically result with lower complexity of a data flow, today's BI applications do require rather complex data analytics, which are typically not supported in the schema mapping approaches. Some approaches try to extend this by automating the flow design (e.g., [79,5]), but still with very limited and predefined operation sets (i.e., ETL & ETO). Therefore, automating the creation of more complex data-intensive flows (e.g., machine learning algorithms), by means of exploiting different input data characteristics or using metadata mechanisms is still lacking.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Even though we notice the lower requirement for the cleanness and constraintness of output data in the next generation BI setting (see Table 2), which would typically result with lower complexity of a data flow, today's BI applications do require rather complex data analytics, which are typically not supported in the schema mapping approaches. Some approaches try to extend this by automating the flow design (e.g., [79,5]), but still with very limited and predefined operation sets (i.e., ETL & ETO). Therefore, automating the creation of more complex data-intensive flows (e.g., machine learning algorithms), by means of exploiting different input data characteristics or using metadata mechanisms is still lacking.…”
Section: Discussionmentioning
confidence: 99%
“…On the one hand, it should raise the usability of the BI system, for a broader set of business users. This module should provide a business-oriented view over the included data sources (e.g., by means of domain ontologies like in [79,50,5]). On the other hand, the Query Assistance module should also facilitate the low coupledness of data sources and be able to efficiently connect to a plethora of external data source repositories.…”
Section: Overall Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…For example, in [10] the authors use an ontology of the data sources and their functional dependencies, together with business queries, to semiautomatically generate the ETL steps and the data warehouse multi-dimentional model at a conceptual level. Similarly, [2] proposes an approach where the domain model along with user-requirements are modelled on the ontological level and subsequently, an ETL process is produced, also modelled as an implementation-independent ontology.…”
Section: Functionality-based Designmentioning
confidence: 99%
“…As a final remark, CoAl works at the logical level and is therefore applicable to a variety of approaches that generate logical data flows from information requirements expressed either as high level business objects (e.g., [9], [10], [11]) or in engine specific languages (e.g., [12]). …”
Section: Introductionmentioning
confidence: 99%