Document provenance of results by Mimi Tzeng - Revision history

Mimi: Set PropertyValue: Progress = 100

2015-06-03T18:21:25Z

Set PropertyValue: Progress = 100

2015-06-03T18:20:12Z

2015-04-11T16:07:53Z

2015-04-03T21:45:27Z

2015-03-21T01:33:46Z

Set PropertyValue: Progress = 95

2015-03-21T01:33:08Z

2015-03-21T01:27:51Z

2015-03-20T20:58:36Z

2015-03-20T19:24:45Z

Set PropertyValue: Progress = 100

2015-03-17T15:01:12Z

@@ Line 22: / Line 22: @@
 	Expertise=Geosciences|
 	Owner=Mimi_Tzeng|
-	Progress=95|
+	Progress=100|
 	StartDate=2015-03-07|
 	TargetDate=2015-03-20|
 	Type=Low}}

← Older revision		Revision as of 18:20, 3 June 2015
Line 14:		Line 14:
	11 Apr 2015: updated version of workflow diagram. Coming soon: a separate page keyed to the blue letters.		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 6: / Line 6: @@
 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-MWTb.png]]
+[[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.
 <!-- Add any wiki Text above this Line -->

@@ Line 8: / Line 8: @@
 [[File:20150320 DocumentProvenance-MWTb.png]]
-Note from Telecon: 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 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?
 <!-- Add any wiki Text above this Line -->

@@ Line 17: / Line 17: @@
 	Expertise=Geosciences|
 	Owner=Mimi_Tzeng|
-	Progress=100|
+	Progress=95|
 	StartDate=2015-03-07|
 	TargetDate=2015-03-20|
 	Type=Low}}

@@ 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.
-Mar 2015: Diagram is available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243
+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: 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?

← Older revision		Revision as of 01:27, 21 March 2015
Line 5:		Line 5:

	20 Mar 2015: Diagram is available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243		20 Mar 2015: Diagram is available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243
		+
		+	Note from Telecon: 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?

← Older revision		Revision as of 20:58, 20 March 2015
Line 3:		Line 3:

	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 available at Zenodo: http://dx.doi.org/10.5281/zenodo.16243

← Older revision		Revision as of 15:01, 17 March 2015
Line 2:		Line 2:
	<br/><b>Details on how to do this task:</b> [[Document the provenance of the results]]<br/><br/>		<br/><b>Details on how to do this task:</b> [[Document the provenance of the results]]<br/><br/>

−	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.