Demo Data from EDBT 2026 / reviewers in the wild / expert
Daniel Müller 0004
dblp:13/204-4
· DBLP profile ↗
2ranked-venue papers
0as first author
0since 2021 · last 2018
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 2Artificial intelligence and machine learning · 1Applied, interdisciplinary, general and emerging computing · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Data integration and cleaning · 77% Database system architecture and tuning · 23% | |
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data integration and cleaning
schema mapping |
0.3 | 1 | 2018 | Curating Variational Data in Application Development · ICDE 2018 |
Software maintenance and evolution › software evolution
schema evolution |
0.3 | 1 | 2018 | Curating Variational Data in Application Development · ICDE 2018 |
Methods — techniques the papers use, named apart from their topics
query rewriting · 0.7data migration · 0.7
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2018 | Curating Variational Data in Application DevelopmentabstractBuilding applications for processing data lakes is a software engineering challenge. We present Darwin, a middleware for applications that operate on variational data. This concerns data with heterogeneous structure, usually stored within a schema-flexible NoSQL database. Darwin assists application developers in essential data and schema curation tasks: Upon request, Darwin extracts a schema description, discovers the history of schema versions, and proposes mappings between these versions. Users of Darwin may interactively choose which mappings are most realistic. Darwin is further capable of rewriting queries at runtime, to ensure that queries also comply with legacy data. Alternatively, Darwin can migrate legacy data to reduce the structural heterogeneity. Using Darwin, developers may thus evolve their data in sync with their code. In our hands-on demo, we curate synthetic as well as real-life datasets. Uta Störl, Daniel Müller 0004, Alexander Tekleab, Stephane Tolale, Julian Stenzel, Meike Klettke, Stefanie Scherzinger |
ICDE | 2 |
| 2017 | Uncovering the evolution history of data lakesabstractData accumulating in data lakes can become inaccessible in the long run when its semantics are not available. The heterogeneity of data formats and the sheer volumes of data collections prohibit cleaning and unifying the data manually. Thus, tools for automated data lake analysis are of great interest. In this paper, we target the particular problem of reconstructing the schema evolution history from data lakes. Knowing how the data is structured, and how this structure has evolved over time, enables programmatic access to the lake. By deriving a sequence of schema versions, rather than a single schema, we take into account structural changes over time. Moreover, we address the challenge of detecting inclusion dependencies. This is a prerequisite for mapping between succeeding schema versions, and in particular, detecting nontrivial changes such as a property having been moved or copied. We evaluate our approach for detecting inclusion dependencies using the MovieLens dataset, as well an adaption of a dataset containing botanical descriptions, to cover specific edge cases. Meike Klettke, Hannes Awolin, Uta Störl, Daniel Müller 0004, Stefanie Scherzinger |
IEEE BigData | 4 |