Line 2 was replaced by line 2 |
- * Jessie presented SEEK Taxon update and plans (PowerPoint) will be put in CVS |
+ * Jessie Kennedy presented SEEK Taxon update and plans (PowerPoint) will be put in CVS as part of plenary session |
At line 3 added 3 lines. |
+ !! Tuesday Morning |
+ * Plenary Session |
+ |
Line 6 was replaced by line 9 |
- * Laura Downey, Going Forward Presentation (will be put in CVS and Wiki attachment) |
+ * Laura Downey, Going Forward Presentation (see attachment) |
Line 17 was replaced by line 20 |
- ! Taxon-Kepler Interaction Design and Engineering Discussion with Dan Higgins |
+ Taxon-Kepler Interaction Design and Engineering Discussion with Dan Higgins |
Removed line 145 |
- |
Removed line 147 |
- |
Removed line 149 |
- |
Removed line 151 |
- |
Removed line 153 |
- |
Removed line 158 |
- |
Line 183 was replaced by lines 180-183 |
- ** _SEEK Early Faculty Ecoinformatics Training for Ecologists_, January 2006. |
+ ** __Next SEEK-Taxon Conference Call__ November 22, 2005, 4PM GMT, 11AM EST, 10 CST, 9 MST, 8 PST |
+ |
+ |
+ ** __SEEK Early Faculty Ecoinformatics Training for Ecologists__, January 2006. |
Line 186 was replaced by line 186 |
- ** _SEEK Developers Meeting_, April 30--May 5, 2006 |
+ ** __SEEK Developers Meeting__, April 30--May 5, 2006 |
Line 188 was replaced by line 188 |
- ** SPNHC Meeting, May 23-27, Albuquerque |
+ ** __SPNHC Meeting__, May 23-27, Albuquerque |
Line 191 was replaced by line 191 |
- ** _Workshop/Feedback Event_ |
+ ** __Workshop/Feedback Event__ |
Line 195 was replaced by line 195 |
- ** _Ecological Society of America Annual Meeting_, 6-11 August 2006. |
+ ** __Ecological Society of America Annual Meeting__, 6-11 August 2006. |
Line 199 was replaced by line 199 |
- ** _TDWG_ October 2006, Somewhere in the U.S., St. Louis, or Durham. |
+ ** __TDWG__ October 2006, Somewhere in the U.S., St. Louis, or Durham. |
At line 206 added 21 lines. |
+ !! Taxon-related Plenary Notes |
+ * Need a set of scenarios for the different tasks we are trying to improve and/or enable for our various user groups. They are in peoples' heads and discussed but not really written down anywhere. |
+ |
+ * TOS user interaction: |
+ ** could be embedded within data search so user can make decision about what data set to get. |
+ ** or use to extract the rows from a data set? |
+ ** What do the user interfaces look like for user to interact with? |
+ *** What about asking user to pick the best match? |
+ *** What about asking user to rank the authoritative sources then having the system do the concept resolution based on that? |
+ *** Have user specify some level of precision for matching/concept resolution etc.? |
+ |
+ * Establish plan for showing Martin's visualization to collection managers. This is a near term activity. We will structure the feedback and conduct the feedback most likely remotely using technology. General plan is demo the product, demonstrate the current tasks it can support, then get user feedback on tasks they would like to do that it doesn't support. |
+ |
+ * Concept mapper - change connect to DB to read and write TCS documents |
+ |
+ * Kepler actors: |
+ ** There is an actor that does the querying of data and returns concepts (for several species) so this would replace the user using the data tab and getting results and then dragging that data set on to the canvas. (Laura's question). This would then feed into the ENM workflow. |
+ ** Should we have a tool outside or within Kepler for users to configure the data (based on TOS). Users could configure the actor to fire automatically or manually. |
+ ** Jessie feels strongly that the searching should be part of the workflow why is there a data tab separately? |
+ *** One reason is because a search returns multiple objects and then a decision needs to be made of which data sets to use. This was seen as a separate step since the workflow objects/actors are seen as configurable but not necessarily interactive. |
+ *** There are some technical issues within Kepler that have prevented more interactive actors. |