| Line 6 was replaced by line 6 |
| - ''__Attendance__'' (Katz): Shawn Bowers, Dan Higgins, Samantha Katz, Bill Michener, Deana Pennington, Mark Schildhauer\\ |
| + ''__Attendance__'' (Katz): Shawn Bowers, Dan Higgins, Samantha Katz, Bill Michener, Deana Pennington, Mark Schildhauer, Aimee Stewart, David Thau\\ |
| Line 8 was replaced by line 8 |
| - Goals for this training to have users return from training and be able to: \\ |
| + Goals for this training to have users return from training and be able to: |
| Lines 13-14 were replaced by lines 13-15 |
| - **Show how kepler utilizes the EcoGrid and how that functions into the importance of well structured data sets and databases -- which included QA/QC |
| - **KR--SMS should show the functionalities that allow kepler to work -- showing the semantic, semantic annotation and ontologies and how that works for them. |
| + **Show how kepler utilizes the EcoGrid and how that functions into the importance of well structured data sets and databases -- which includes QA/QC |
| + **Show how kepler utilizes the functionalities of KR SMS -- how the semantic, semantic mediation and annotation through ontologies works for them and how this is linked to well documented and well structured datasets. |
| + **Show how taxonomic resolution works and how this is linked to well documented and well structured datasets. |
| At line 23 added 1 line. |
| + **Will's presentation on Eml and morpho link link to Grid presentation and tie into Dan's presentation on Kepler. |
| Line 26 was replaced by line 28 |
| - ** |
| + **KR SMS presentation by Shawn will close up the week by revisitng topics covered previously during the week: the importance of well documented and well structured datasets and how this is exploited through semantic mediation and ontologies. Using an exercise that illustrates problems of and solutions to data integration. |
| At line 29 added 2 lines. |
| + ''__Attendance__'' (Katz): Laura Downey, Dan Higgins, Samantha Katz, Deana Pennington, Mark Schildhauer\\ |
| + |
| Lines 31-35 were replaced by lines 35-39 |
| - *First example -- Simple Addition changed to Simple Statistics -- needs reviewed for edits and completeness -- Need Dan to review and save as workflow for the Beta3 release |
| - *Need to finish updating section 5.3 Director and Actor Icons with most recent icon family categories for the Beta3 release |
| - **sam used the 3 "all-the-actors actor in workflows" directory that Matt made and went back to svg and made some adaptations) |
| - **Laura needs to be reviewed and make suggestion |
| - *Need to finish the screenshots in the GSG.Working with Monica from UCSB people on creating screenshots. Will work with Monica on making sure the GSG images are the same as the Kepler interface -- go over images with Laura |
| + **First example -- Simple Addition changed to Simple Statistics -- __needs reviewed for edits and completeness -- Need Dan to review and save as workflow for the Beta3 release.__ |
| + **Need to finish updating section 5.3 Director and Actor Icons with most recent icon family categories for the Beta3 release. Sam used the 3 "all-the-actors actor in workflows" directory that Matt made and went back to svg and made some adaptation to create an initial list. __Laura needs to be reviewed and make suggestion__ |
| + **Need to finish the screenshots in the GSG. __Need to go over the graphic designers images with Laura__ |
| + **Need to change the default parameter in Lotka-Volterra model for the GSG and the saved workflows |
| + **Need to identify channels in the images -- ___make sure this is reflected in the document and that we adequately describe channel and this idea___. |
| Lines 37-45 were replaced by lines 41-49 |
| - *Review actor classifications |
| - **List of list SEEK actors and workflows -- corresponds |
| - **Review and request developer level actor documentation -- need help Dan, Ilkay and Efrat cannot be the only people reviewing |
| - **Removed the following actors from the actor documentation: File to String Converter ; Invoke server; ServerExecute, TempActor; |
| - **Naming convention -- camel case conventions |
| - **Incorporating documentation into application -- working with Chad on the strategy mentioned below |
| - Strategy: Use the Actor right-click menu to update the individual documentation screens (i.e., update the actor's MOML files). Use HTML <p>, <i>, and <tt> tags to preserve formatting. Save the updated actor files as KAR file and then overwrite the existing files in the /Kepler/src/actors directory in CVS. |
| - In the current system, the application will display the Java doc, unless there is doc info in the corresponding MOML file, which will override the Java doc. The system also examines the class and displays that name. An example of an actor with a MOML doc is the Scatterplot actor. |
| - Documentation about ports and parameters should only be pasted into the actor if it differs from its base class. Will this work? Now that I'm writing this up, I'm a bit confused. We're updating the MOML file, right? Will the class MOML file overwrite a child's Java docs? |
| + |
| + |
| + Review actor classifications |
| + **List of list SEEK actors and workflows -- __make sure these lists correspond__ |
| + **Review and request developer level actor documentation -- need help Dan, Ilkay and Efrat cannot be the only people reviewing __It was decided that we would only create user level documentation for those actors that: related to the SEEK project; has adequate developer documentation; or the developer was willing to work with us.__ |
| + **Removed the following actors from the actor documentation: File to String Converter ; Invoke server; ServerExecute, TempActor. __The list of actors will be reviewed and extended based upon a review by Dan, Samantha and Kirsten__ |
| + **Naming convention -- __camel case conventions__ |
| + **Incorporating documentation into application. __work with David Sledge on an alternative strategy to the "cut and paste method."__ |
| + |
| Lines 48-49 were replaced by lines 52-60 |
| - *KR- SMS ontology -- what kind of documentation is needed? Why? -- example -- ask laura for appendices and one-page description. |
| - Eml dataset and link to morpho |
| + KR- SMS ontology |
| + **What kind of documentation is needed? Why? __ask laura for appendices and one-page description__ |
| + |
| + FAQ needs to be expanded to include the following |
| + **__Native windows “zip” doesn’t work for Kepler__ |
| + **__Link to GSG__ |
| + **__deletion of kepler cache and note about deleting cache removes any remote components__. |
| + **__Need to add a list in the GSG about the complete list of workflows that are shipped with the release__. |
| + **__Need to add a note/table about workflows and the difference between the nightly build and the release__. |
