| At line 0 added 6 lines. |
| + !! Monday Afternoon |
| + * Jessie Kennedy presented SEEK Taxon update and plans (PowerPoint) will be put in CVS as part of plenary session |
| + |
| + !! Tuesday Morning |
| + * Plenary Session |
| + |
| Line 3 was replaced by line 9 |
| - * Laura Downey, Going Forward Presentation |
| + * Laura Downey, Going Forward Presentation (see attachment) |
| Line 14 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 |
| Lines 107-109 were replaced by lines 113-114 |
| - Nico will analyze the design needs for modifying Morpho to add a TOS lookup during meta record creation. |
| - |
| - Xianhua will nominally consider working on the implementation of that using existing GetBestConcept service. |
| + * Morpho |
| + ** Nico will analyze the functional design requirement for modifying Morpho to add a TOS lookup during meta record creation. Description of placement, function, insertion, behavior of such a function (End of November) |
| Line 111 was replaced by line 116 |
| - Xianhua will make the relationship mapper compliant with TCS. TCS record import and export. |
| + ** Xianhua will nominally consider working on the implementation of that using existing GetBestConcept service. (dependency on knowing requirements from Nico, and after other tasks) |
| At line 112 added 1 line. |
| + ** Xinhua will upgrade Ranunculus data to latest TCS, (1-2 weeks) Bob will make his data available: |
| Line 114 was replaced by line 120 |
| - Bob will make his data available: Ranunculus data, it needs to be upgraded to latest TCS, Xianhua will do that in 1 week. Jan or Feb 2006: All USDA Plants in version 4, mapped against all plants in FNA, and also all of the Alan Weekly collaboration, his version mapped against 8 different classifications of plants. |
| + ** (Bob) In Jan or Feb 2006, all USDA Plants in version 4, mapped against all plants in FNA, and also all of the Alan Weekly collaboration, his version mapped against 8 different classifications of plants. |
| At line 118 added 1 line. |
| + ** Tasks and Subprojects: |
| Removed lines 120-121 |
| - ** Tasks: |
| - |
| Line 124 was replaced by lines 129-181 |
| - *** MSW Bat data need to be mapped between 1993 and 2005 versions. Kate Jones demonstrated how they did the mapping in interview with Nico and Laura, the actual mappings can be identified from explicit annotations in the 2005 publication. But publication notes will likely not be explicit as to the exact mapping operator. We need someone to read the treatment and try to extract the mappings. We do not currently have a copy of the treatment. Diane Reeder and Don Wilson are the authors of this information and created the source documents. |
| + *** MSW Bat data need to be mapped between 1993 and 2005 versions. Kate Jones demonstrated how they did the mapping in interview with Nico and Laura, the actual mappings can be identified from explicit annotations in the 2005 publication. But publication notes will likely not be explicit as to the exact mapping operator. We need someone to read the treatment and try to extract the mappings. We do not currently have a copy of the treatment. Diane Reeder and Don Wilson are the editors of MSW and created the source documents. |
| + |
| + **** Beach will meet with Don Wilson November 2nd, explain our need and interest. Will ask him for a copy of the 2005 MSW bat treatment. |
| + |
| + **** Nico will then use Xianhua's mapping tool to author the relationships. Reserves the right to pass on the task if overly complex. Nico will use the TCS-included subset of Nico's symbolic annotation codes. (dependent on receipt of MSW Bats 2005 text from Beach) |
| + |
| + |
| + *** Susan's project will look at the 100 treatments she has since 1993 and will try to see if the concepts in those were adopted and/or mapped in the 2005 treatment. Then we can compare the actual 2005 tree with pieces that would have ben predicted from the treatments, then we can evaluate how close we get to truth. (January 2006) |
| + |
| + * PLANTS (Stinger) |
| + ** Stinger will send PLANTS database with county records.(October 31) |
| + ** Vieglais will put the county records into a DiGIR server. (Dependent on receipt of data from Stinger. |
| + ** Updated PLANTS nomenclature for 4.0 to be given to Bob.(October 31) |
| + ** Stinger will get archived version of PLANTS.(October 31) |
| + |
| + * Kepler-TOS Objectives (Gales) |
| + |
| + ** Tasks |
| + *** Rob will produce a GET-TAXA description of actors he is developing (November). |
| + *** Version upgrade of TOS 1.01 (Gales and Stewart) |
| + *** Rob will work with Matt to identify parameters for the ecological niche workflow. |
| + *** Write one large "GET TAXA" TOS actor, to handle three actors now has (without a lot of parameters, just the basic workflow needs (January). |
| + *** The GET TAXA actor will have added parameters to handle matching scenarios discussed on Wednesday. Concept overlaps, transitive links, etc. |
| + *** Additional actors need to be specified based on requirements of the other workflows. |
| + |
| + *** Setup SEEK-ITTC server for TOS. |
| + *** Hibernate upgrade, TOS deployment, also see Aimee and Rob list from week before meeting. |
| + ** Web application to take a GUID and output a subtree of all related concepts and descendants, for ConceptMapper queries on TOS. |
| + |
| + |
| + * Concept MapperTool Objectives (Xianhua) |
| + |
| + ** Translate Alan Weakley's Excel data into TCS (Timing UNKNOWN), sends to KU, import it into TOS |
| + ** Incorporating Laura's heuristic evaluation comments, and results of the task analysis not currently in the tool (Nico and Laura have information (2 weeks) |
| + ** ConceptMapper modified to import TCS documents |
| + ** ConceptMapper modified to export TCS documents |
| + ** ConceptMapper modified to creating concepts |
| + |
| + ** 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. |
| + |
| + ** 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.) |
| + |
| + ** 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. |
| + |
| + * GUID Issues |
| + ** TDWG Workshop in February, Attending: Peet, Gales or Perry, Spears, Kennedy(?) |
| + ** Need to discuss how to configure GUID services for SEEK, which data get returned? |
| + |
| + |
| + * Future Meetings |
| + |
| + ** __Next SEEK-Taxon Conference Call__ November 22, 2005, 4PM GMT, 11AM EST, 10 CST, 9 MST, 8 PST |
| + |
| Line 126 was replaced by lines 183-184 |
| - *** Susan's project will look at the 100 treatments she has since 1993 and will try to see if the concepts in those were adopted and/or mapped in the 2005 treatment. Then we can compare the actual 2005 tree with pieces that would have ben predicted from the treatments, then we can evaluate how close we get to truth. |
| + ** __SEEK Early Faculty Ecoinformatics Training for Ecologists__, January 2006. |
| + *** Nico presenting SEEK taxon concept talk |
| At line 127 added 1 line. |
| + ** __SEEK Developers Meeting__, April 30--May 5, 2006 |
| At line 128 added 2 lines. |
| + ** __SPNHC Meeting__, May 23-27, Albuquerque |
| + *** good opportunity for outreach to collections managers and museum directors |
| At line 129 added 3 lines. |
| + ** __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 |
| At line 130 added 3 lines. |
| + ** __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 |
| At line 131 added 1 line. |
| + ** __TDWG__ October 2006, Somewhere in the U.S., St. Louis, or Durham. |
| At line 135 added 2 lines. |
| + Review of objectives and timetables (above). |
| + Stinger discussed availability of concepts with character data for TOS, grasses from various projects, family lists, |
| At line 136 added 2 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. |
| At line 137 added 18 lines. |
| + * 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. |
