Introduction to Algorithms
Provenance trails in the Wings-Pegasus system
Concurrency and Computation: Practice & Experience - The First Provenance Challenge
Extracting causal graphs from an open provenance data model
Concurrency and Computation: Practice & Experience - The First Provenance Challenge
Efficient lineage tracking for scientific workflows
Proceedings of the 2008 ACM SIGMOD international conference on Management of data
A Model for Sharing of Confidential Provenance Information in a Query Based System
Provenance and Annotation of Data and Processes
Towards a model of provenance and user views in scientific workflows
DILS'06 Proceedings of the Third international conference on Data Integration in the Life Sciences
Managing rapidly-evolving scientific workflows
IPAW'06 Proceedings of the 2006 international conference on Provenance and Annotation of Data
Provenance collection support in the kepler scientific workflow system
IPAW'06 Proceedings of the 2006 international conference on Provenance and Annotation of Data
A model for user-oriented data provenance in pipelined scientific workflows
IPAW'06 Proceedings of the 2006 international conference on Provenance and Annotation of Data
Bridging workflow and data provenance using strong links
SSDBM'10 Proceedings of the 22nd international conference on Scientific and statistical database management
The Foundations for Provenance on the Web
Foundations and Trends in Web Science
Hi-index | 0.00 |
Workflow Management Systems (WFMS), such as Kepler, are proving to be an important tool in scientific problem solving. They can automate and manage complex processes and huge amounts of data produced by petascale simulations. Typically, the produced data need to be properly visualized and analyzed by scientists in order to achieve the desired scientific goals. Both run-time and post analysis may benefit from, even require, additional meta-data --- provenance information. One of the challenges in this context is the tracking of the data files that can be produced in very large numbers during stages of the workflow, such as visualizations. The Kepler provenance framework collects all or part of the raw information flowing through the workflow graph. This information then needs to be further parsed to extract meta-data of interest. This can be done through add-on tools and algorithms. We show how to automate tracking specific information such as data files locations.