ProvTools Ecosystem

[MKLau]

An ecosystem structure would facilitate the modularization of software into feature driven packages that could then be related in terms of their functional and conceptual inter-dependencies.

This was suggested by @tfjmp last spring and would be good effect now as it would help to solve several development issues relating to the overlapping of features and the legibility to users. I've started work on this by initiating a github organization, similar to the end-to-end-provenance organization that would collect tools to do specific tasks, like the tidyverse.

The overarching theme would be "leveraging provenance for science" and we would therefore have:

• capture (e.g., RDataTracker, noworkflow, etc.)
• storage (CPL)
• analysis (codecleanR, encapsulator, summary, DDG-Explorer)

[erboose]

Matt, Thomas--could you outline some use cases that would illustrate how the various modules might be used from the user's prospective?

[MKLau]

Will do!