EDBT 2026 Demo / reviewers in the wild / expert
Aaron R. Jeyaraj
dblp:318/6528
· DBLP profile ↗
2ranked-venue papers
0as first author
2since 2021 · last 2023
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 since 2021Databases, data management, data science and information retrieval · 1 · 1 since 2021
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
2 papers |
Database system architecture and tuning · 62% Data integration and cleaning · 38% | |
| Network and information security
2 papers |
Privacy and data protection · 100% |
Topics — the 2 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data integration and cleaning
data provenance |
0.5 | 1 | 2021 | Retrofitting GDPR Compliance onto Legacy Databases · Proc. VLDB Endow. 2021 |
Privacy and data protection
regulatory compliance |
0.5 | 1 | 2021 | Retrofitting GDPR Compliance onto Legacy Databases · Proc. VLDB Endow. 2021 |
Methods — techniques the papers use, named apart from their topics
query log analysis · 1.0foreign key analysis · 1.0data-driven relationship inference · 1.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | K9db: Privacy-Compliant Storage For Web Applications By Construction
Kinan Dak Albab, Ishan Sharma, Justus Adam, Benjamin Kilimnik, Aaron R. Jeyaraj, Raj Paul, Artem Agvanian, Leonhard F. Spiegelberg, Malte Schwarzkopf |
OSDI | 5 |
| 2021 | Retrofitting GDPR Compliance onto Legacy DatabasesabstractNew privacy laws like the European Union's General Data Protection Regulation (GDPR) require database administrators (DBAs) to identify all information related to an individual on request, e.g. , to return or delete it. This requires time-consuming manual labor today, particularly for legacy schemas and applications. In this paper, we investigate what it takes to provide mostly-automated tools that assist DBAs in GDPR-compliant data extraction for legacy databases. We find that a combination of techniques is needed to realize a tool that works for the databases of real-world applications, such as web applications, which may violate strict normal forms or encode data relationships in bespoke ways. Our tool, GDPRizer, relies on foreign keys, query logs that identify implied relationships, data-driven methods, and coarse-grained annotations provided by the DBA to extract an individual's data. In a case study with three popular web applications, GDPRizer achieves 100% precision and 96--100% recall. GDPRizer saves work compared to hand-written queries, and while manual verification of its outputs is required, GDPRizer simplifies privacy compliance. Archita Agarwal, Marilyn George, Aaron R. Jeyaraj, Malte Schwarzkopf |
Proc. VLDB Endow. | 3 |