RFC Name : DataProvenance |
Editor(s): ScooterMorris |
Date: 11/20/2008 |
Status: Draft |
<<TableOfContents: execution failed [Argument "maxdepth" must be an integer value, not "[2]"] (see also the log)>>
Proposal
Include support for Data Provenance in Cytoscape 3.0
Background
In early discussions of Cytoscape 3.0, we talked about the need to support the idea of Data Provenance. At the time, the focus was on something called a CyProject, which would gather all of the files and intermediate stages along with the experimenter's comments and annotation about what was done. In the recent discussions about Data Provenance, it was discussed that we might be able to use lower-level mechanisms.
Use Cases
The major use case is to be able to record what was done to create a result. In this case, the idea is that the user reads in several files, performs various analysis, applies various visualizations, interacts with web services, etc., etc., and in the end, they have a network that elucidates some scientific result they want to publish. Now, during the review cycle, or for future work, or as part of a collaboration, they want to be able to recapitulate what was done. Generally not as an automated process (although that could be useful also), but as a reminder of how they got this network.
Related RFCs
Link to other related RFCs
Issues
Comments
Add comment hereā¦
How to Comment
Edit the page and add your comments under the provided header. By adding your ideas to the Wiki directly, we can more easily organize everyone's ideas, and keep clear records. Be sure to include today's date and your name for each comment. Try to keep your comments as concrete and constructive as possible. For example, if you find a part of the RFC makes no sense, please say so, but don't stop there. Take the extra step and propose alternatives.