VisTrails: visualization meets data management
Proceedings of the 2006 ACM SIGMOD international conference on Management of data
Story book: an efficient extensible provenance framework
TAPP'09 First workshop on on Theory and practice of provenance
Layering in provenance systems
USENIX'09 Proceedings of the 2009 conference on USENIX Annual technical conference
Provenance collection support in the kepler scientific workflow system
IPAW'06 Proceedings of the 2006 international conference on Provenance and Annotation of Data
SPADE: support for provenance auditing in distributed environments
Proceedings of the 13th International Middleware Conference
Provenance for seismological processing pipelines in a distributed streaming workflow
Proceedings of the Joint EDBT/ICDT 2013 Workshops
IPAPI: designing an improved provenance API
TaPP'13 Proceedings of the 5th USENIX conference on Theory and Practice of Provenance
IPAPI: designing an improved provenance API
Proceedings of the 5th USENIX Workshop on the Theory and Practice of Provenance
Provenance in sensor data management
Communications of the ACM
Provenance in Sensor Data Management
Queue - Large-Scale Implementations
| Hi-index | 0.02 |
Most provenance capture takes place inside particular tools - a workflow engine, a database, an operating system, or an application. However, most users have an existing toolset - a collection of different tools that work well for their needs and with which they are comfortable. Currently, such users have limited ability to collect provenance without disrupting their work and changing environments, which most users are hesitant to do. Even users who are willing to adopt new tools, may realize limited benefit from provenance in those tools if they do not integrate with their entire environment, which may include multiple languages and frameworks. We present the Core Provenance Library (CPL), a portable, multi-lingual library that application programmers can easily incorporate into a variety of tools to collect and integrate provenance. Although the manual instrumentation adds extra work for application programmers, we show that in most cases, the work is minimal, and the resulting system solves several problems that plague more constrained provenance collection systems.