Cited by 300Scientific Computing and Data ManagementAdvanced Database Systems and QueriesDistributed systems and fault tolerance

A survey on provenance: What for? What form? What from?

Herschel, Melanie, Diestelkämper, Ralf, Ben Lahmar, Houssem·2017·The VLDB Journal

Integrity signals

Registry

Crossref · 10.1007/s00778-017-0486-1

Cites

200 of 200 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

We couldn’t retrieve this paper’s full text, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • In interconnected systems, data flow drives everything, integrating systems and bringing their functionality.

    “Importantly, in these interconnected systems data flow drives everything, in that the flow of data between, through, and across systems works to integrate them and brings their functionality [22].”
  • The general opacity of interconnections between systems, coupled with the general lack of technical means for tracking data flow at such a scale, poses accountability issues.

    “The general opacity of the interconnections between systems, coupled with the general lack of technical means for tracking data flow at such a scale, therefore poses accountability issues, as it becomes difficult to discern the technical components involved, and then who is responsible for these [22], [23].”
  • Although provenance has been considered for some specific compliance aspects, the broader accountability considerations have yet to be explored in depth.

    “Though, as mentioned, provenance has been considered for some specific compliance aspects (see for e.g.[22], [23], [27]- [29]), the broader accountability considerations have yet to be explored in depth.”
  • Proactive measures could allow users to set policy that constrains particular information flows or keep users informed of changes in circumstance.

    “That said, proactive measures could also be employed to allow users to set policy that constrain particular information flows [22], or keep users informed of any change in circumstance.”
  • More information regarding the nature of systems could allow those building and deploying systems to improve their quality and identify points of failure, while empowering others by offering more insight into systems and data beyond their direct control.

    “Generally speaking, more information regarding the nature of systems could allow those building and deploying systems to improve their quality and to identify points of failure, while empowering others by offering more insight into the nature of the systems and data that is beyond their direct control [4], [22], [23].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Herschel, M., Diestelkämper, R., & Ben Lahmar, H.
Affiliations
University of Stuttgart (DE)
Corresponding author
Herschel, Melanie
Venue
The VLDB Journal
Published
2017-10-16
Volume
26
Issue
6
Pages
881-906
ISSN
  • 0949-877X (ISSN-L)
  • 1066-8888
OpenAlex
W2766945679
Cited by
300
References
200
Citations by year
2026: 40 · 2025: 34 · 2024: 28 · 2023: 28 · 2022: 37 · 2021: 43 · 2020: 34 · 2019: 34 · 2018: 22
FWCI
39.63
Type
journal article
Language
en
Open access
closed
Locations
The VLDB Journal (publishedVersion)
Funders
Deutsche Forschungsgemeinschaft (SFB-TRR 161)
Topics
  • Social Sciences › Decision Sciences › Information Systems and Management › Scientific Computing and Data Management
  • Physical Sciences › Computer Science › Computer Networks and Communications › Advanced Database Systems and Queries
  • Physical Sciences › Computer Science › Computer Networks and Communications › Distributed systems and fault tolerance
Keywords
provenance, data provenance, provenance capture, accountability, reproducibility, privacy, scalability

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review