The provenance of workflow upgrades

David Koop, Carlos E. Scheidegger, Juliana Freire, Cláudio T. Silva

Research output: Chapter in Book/Report/Conference proceedingConference contribution

9 Scopus citations


Provenance has become an increasingly important part of documenting, verifying, and reproducing scientific research, but as users seek to extend or share results, it may be impractical to start from the exact original steps due to system configuration differences, library updates, or new algorithms. Although there have been several approaches for capturing workflow provenance, the problem of managing upgrades of the underlying tools and libraries orchestrated by workflows has been largely overlooked. In this paper we consider the problem of maintaining and re-using the provenance of workflow upgrades. We propose different kinds of upgrades that can be applied, including automatic mechanisms, developer-specified, and user-defined. We show how to capture provenance from such upgrades and suggest how this provenance might be used to influence future upgrades. We also describe our implementation of these upgrade techniques.

Original languageEnglish (US)
Title of host publicationProvenance and Annotation of Data and Processes - Third International Provenance and Annotation Workshop, IPAW 2010, Revised Selected Papers
Number of pages15
StatePublished - 2010
Event3rd International Provenance and Annotation Workshop, IPAW 2010 - Troy, NY, United States
Duration: Jun 15 2010Jun 16 2010

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume6378 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349


Other3rd International Provenance and Annotation Workshop, IPAW 2010
Country/TerritoryUnited States
CityTroy, NY

ASJC Scopus subject areas

  • Theoretical Computer Science
  • General Computer Science


Dive into the research topics of 'The provenance of workflow upgrades'. Together they form a unique fingerprint.

Cite this