| 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 |
| - |
| Lines 170-171 were replaced by line 167 |
| - * Taxon Comparison tool (Martin) |
| - ** Scenario document for use with collections manager scenario investigation. Martin will send to Laura. Beach will set up LiveMeeting configuration to do a test session btwn UNM and KU. Target early December for outreach sessions. (During time that Beach is at UNM?) |
| + ** User testing planned for 1Qr 2006 (Laura, Xianhua, Bob?, Alan, Brett, Bat Person, Nico?) Nico will organize schedule. Laura will organize the entire testing script, Xianhua will organize software, Bob will need to make local arrangments. Jim will confirm with Michener and Griego. |
| Line 173 was replaced by line 169 |
| - ** Load up Ranunculus data and prepare a scenario and demonstration for taxonomists/ecologists to compare taxa to help in the resolving of concepts. (Dependent on receiving data in TCS.) |
| + ** Load up Ranunculus data and prepare a scenario and demonstration for taxonomists/ecologists to compare taxa to help in the resolving of concepts.(Dependent on receiving data in TCS.) |
| Line 175 was replaced by line 171 |
| - ** Explore the effect of the granularity of matching. If you match only on concepts what you discover? If you match on names, what knowledge do you discover? Etc. Pass that document to Laura and Bob, to plan an evaluation session with Bob in early 2006. |
| + ** Explore the effect of the granularity of matching. If you match only on concepts what you discover? If you match on names, what knowledge do you discover? Etc. Pass that document to Laura and Bob, to plan an evaluation session with Bob in early 2006. |
| Line 184 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. |
| Lines 187-189 were replaced by line 186 |
| - ** ESA |
| - *** 3500-4000 scientists, Memphis, Tennessee |
| - *** Things to possibly demonstrate: Taxon Comparison tool, Kepler ENM use case with two different classifications, ConceptMapper, |
| + ** __SEEK Developers Meeting__, April 30--May 5, 2006 |
| Line 191 was replaced by line 188 |
| - ** SPNHC Meeting, May 23-27, Albuquerque |
| + ** __SPNHC Meeting__, May 23-27, Albuquerque |
| Lines 194-195 were replaced by lines 191-193 |
| - * Workshop Concept |
| - ** Tentatively planned for May 2006, to overlap with SPNHC? Specify, Usability interviews and testing, not a 5 day general informatics meeting |
| + ** __Workshop/Feedback Event__ |
| + *** Tentatively planned for May 2006, to overlap with SPNHC? Specify, Usability interviews and testing, not a 5 day general informatics meeting |
| + ** DEADLINE to decide Two Weeks |
| Line 197 was replaced by lines 195-197 |
| - * SEEK Developers Meeting, April 30--May 5, 2006 |
| + ** __Ecological Society of America Annual Meeting__, 6-11 August 2006. |
| + *** 3500-4000 scientists, Memphis, Tennessee |
| + *** Things to potentially demonstrate: Taxon Comparison tool, Kepler ENM use case with two different classifications, Peterson, two bird classification, biological reserve planning, demonstration, ConceptMapper. Need a very large graphic display! Try Bat data 93-05 comparison with distribution data |
| 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. |
