Demo Data from SIGIR 2026 / reviewers in the wild / expert
Thorsten Seyschab
dblp:181/9138
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 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 |
Transaction processing and concurrency control · 100% | |
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Transaction processing and concurrency control › versioning
schema versioning |
0.2 | 1 | 2016 | InVerDa - co-existing schema versions made foolproof · ICDE 2016 |
Software maintenance and evolution › software evolution
schema evolution |
0.1 | 1 | 2016 | InVerDa - co-existing schema versions made foolproof · ICDE 2016 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | InVerDa - co-existing schema versions made foolproofabstractIn modern software landscapes multiple applications usually share one database as their single point of truth. All these applications will evolve over time by their very nature. Often former versions need to stay available, so database developers find themselves maintaining co-existing schema version of multiple applications in multiple versions. This is highly error-prone and accounts for significant costs in software projects, as developers realize the translation of data accesses between schema versions with hand-written delta code. In this demo, we showcase INVERDA, a tool for integrated, robust, and easy to use database versioning. We rethink the way of specifying the evolution to new schema versions. Using the richer semantics of a descriptive database evolution language, we generate all required artifacts automatically and make database versioning foolproof. Kai Herrmann 0002, Hannes Voigt, Thorsten Seyschab, Wolfgang Lehner |
ICDE | 3 |