Difference between revisions of "Document provenance of results by Mimi Tzeng"
m |
(Set PropertyValue: Progress = 100) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
I am using [https://www.literatureandlatte.com/scapple.php Scapple] to make my workflow diagram. It was intended for diagramming story structure in fiction, but I've found this to be a useful tool for making entity relationship diagrams (ERDs) for relational databases and wanted to try it out for workflows. | I am using [https://www.literatureandlatte.com/scapple.php Scapple] to make my workflow diagram. It was intended for diagramming story structure in fiction, but I've found this to be a useful tool for making entity relationship diagrams (ERDs) for relational databases and wanted to try it out for workflows. | ||
| + | 20 Mar 2015: Diagram is also available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243 (but thanks to Suzanne, I now know I can just upload these directly to the wiki!) | ||
| + | |||
| + | [[File:20150320 DocumentProvenance-MWTc.png]] | ||
| + | |||
| + | Note from Telecon 3/20: I need to include more information about what specific processing each of the software components did to the data files. Perhaps by adding text to the actual diagram boxes? That would make those boxes very large. Or would it work to give them all numbers, and then make a separate page with notes in outline form? | ||
| + | |||
| + | Note from Telecon 4/3: use footnotes on a separate page, since the workflow diagram is already pretty complex. | ||
| + | |||
| + | 11 Apr 2015: updated version of workflow diagram. Coming soon: a separate page keyed to the blue letters. | ||
| + | |||
| + | 3 Jun 2015: I've decided that the blue letters are going to be explained in detail in the main text instead. The only other change that needs to be made to the diagram is to remove the little note at the upper left that says I need to make a mooring diagram for the paper; I have this done now. | ||
<!-- Add any wiki Text above this Line --> | <!-- Add any wiki Text above this Line --> | ||
| Line 11: | Line 22: | ||
Expertise=Geosciences| | Expertise=Geosciences| | ||
Owner=Mimi_Tzeng| | Owner=Mimi_Tzeng| | ||
| − | Progress= | + | Progress=100| |
StartDate=2015-03-07| | StartDate=2015-03-07| | ||
TargetDate=2015-03-20| | TargetDate=2015-03-20| | ||
Type=Low}} | Type=Low}} | ||
Latest revision as of 18:21, 3 June 2015
Details on how to do this task: Document the provenance of the results
I am using Scapple to make my workflow diagram. It was intended for diagramming story structure in fiction, but I've found this to be a useful tool for making entity relationship diagrams (ERDs) for relational databases and wanted to try it out for workflows.
20 Mar 2015: Diagram is also available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243 (but thanks to Suzanne, I now know I can just upload these directly to the wiki!)
Note from Telecon 3/20: I need to include more information about what specific processing each of the software components did to the data files. Perhaps by adding text to the actual diagram boxes? That would make those boxes very large. Or would it work to give them all numbers, and then make a separate page with notes in outline form?
Note from Telecon 4/3: use footnotes on a separate page, since the workflow diagram is already pretty complex.
11 Apr 2015: updated version of workflow diagram. Coming soon: a separate page keyed to the blue letters.
3 Jun 2015: I've decided that the blue letters are going to be explained in detail in the main text instead. The only other change that needs to be made to the diagram is to remove the little note at the upper left that says I need to make a mooring diagram for the paper; I have this done now.
