Provenance refers to any information describing the production process of an end product,
which can be anything from a piece of digital data to a physical object. While this survey …

In large-scale data management systems, failure is practically a certainty. Fault-tolerant
protocols and components are notoriously difficult to implement and debug. Worse still …

Provenance has been studied extensively to explain existing and missing results for many
applications while focusing on scalability and usability challenges. Recently, techniques that …

Why and why-not provenance have been studied extensively in recent years. However, why-
not provenance, and to a lesser degree why provenance, can be very large resulting in …

Large-scale distributed systems must be built to anticipate and mitigate a variety of hardware
and software failures. In order to build confidence that fault-tolerant systems are correctly …

Explaining why an answer is (or is not) returned by a query is important for many
applications including auditing, debugging data and queries, and answering hypothetical …

Explaining why an answer is in the result of a query or why it is missing from the result is
important for many applications including auditing, debugging data and queries, and …

Explaining why an answer is present (traditional provenance) or absent (missing answer
provenance) from a query result is important for many use cases. Most existing approaches …

How to use provenance to explain why a query returns a result or why a result is missing has
been studied extensively. Recently, we have demonstrated how to uniformly answer these …

One important issue in modern database applications is supporting the user with efficient
tools to debug and fix queries because such tasks are both time and skill demanding. One …