| Removed line 1 |
| - |
| Line 6 was replaced by lines 5-7 |
| - !! Kepler-Taxon work flow discussion integration of DiGIR and Kepler in two SEEK use case work flows |
| + ! Taxon-Kepler Interaction Design and Engineering Discussion with Dan Higgins |
| + |
| + * Integration of DiGIR and Kepler in two SEEK use case work flows |
| Lines 11-51 were replaced by line 12 |
| - ** High-level Taxon-Kepler Interaction Design and Engineering Issues with Dan Higgins |
| - |
| - *** The 'selection problem' How do users *find* and then *select* the focal concept for searching, parameterizing an actor, with the concept one wants to work with. 1st generation, little interactivity, fill in a Kepler parameter file. |
| - |
| - Wrap Robs current work flow into a custom actor, interactivity would come later, and maybe then passing parameter files to the actor from an application outside of GARP. |
| - |
| - |
| - ***** Problem with names being mapped to more than once concept for GARP work flow |
| - |
| - ***** Merging data sets with concepts that overlap, how do we integrate them once they come back |
| - |
| - ***** Looping issue in GARP usecase workflow: going through list of concepts to find synonyms to identify overlaps (names with 2 or more concepts), Gales & Jones, Action: make a custom TOS actor instead of modifying web services actor (which came from GEON) |
| - |
| - ***** SEEK-Taxon would like to see more possibility for an interactive UI within Kepler for TOS query and selection tasks. Alternative is to stop, restart and repeat short workflows as the 'interactivity' |
| - |
| - |
| - |
| - |
| - *** SEEK Use Case #2 need a taxon concept merging tool. SMS is working on merging other types of parameters across site data sets. (Get a list of species from LTER data sets, assume they are in EML, input to TOS [GetBestConcept], output unique list of merged names, |
| - |
| - **** Must mark up taxon names as concepts with GUIDs in the EML data sets first, GUIDs would be the concept IDs. Need a tool to do that, Morpho is the likely app. If no GUID in the data set, a call to TOS could match on data set taxon name and a taxon reference. |
| - |
| - **** Kepler work flow scenario: Kepler has Actors that can actually merge the data, need some user interaction with TOS to decide which level of lumping the user wants, include synonyms, concept overlaps, go up a level, etc. |
| - |
| - |
| - |
| - ***** if the GUIDs match between data sets, we merge |
| - ***** if the names from two data sets match (derived from GUIDs in the date set) in TOS, we combine them |
| - ***** if concepts match in TOS (other TOS operations) |
| - |
| - |
| - |
| - |
| - |
| - |
| - |
| - |
| - and how to identify concepts that match user's query concept 'expectation', (e.g. query TOS, return concepts to Kepler, do a EcoGrid query). How to build a UI that is meaningful to users for such tasks. |
| - |
| - **** |
| - |
| + ** The 'selection problem' How do users *find* and then *select* the focal concept for searching and parameterizing an actor, with the concept one wants to work with? 1st generation, no interactivity, beyond filling in an Actor parameter file. Rob has wrapped current work flow into a custom actor, interactivity would come later, and maybe then passing parameter files to the actor from an application outside of Kepler would be possible. |
| At line 52 added 1 line. |
| + ** Problem with names coming out TOS query being mapped to more than once of the concepts specified for DiGIR query for GARP input. |
| At line 53 added 1 line. |
| + ** Looping issue in GARP usecase workflow: going through list of concepts to find synonyms to identify overlaps (names with 2 or more concepts), Gales & Jones, Action: make a custom TOS actor instead of modifying web services actor (which came from GEON) |
| At line 54 added 1 line. |
| + ** SEEK-Taxon would like to see more possibility for an interactive UI within Kepler for TOS query and selection tasks. Alternative is to stop, restart and repeat short workflows as the way to introduce 'interactivity' for the user to test steps before running the complete workflow. |
| At line 55 added 1 line. |
| + ** SEEK Use Case #2 need a taxon concept merging tool. SMS is working on merging other types of parameters across site data sets. (Get a list of species from LTER data sets, assume they are in EML, input to TOS, output unique list of merged names, |
| At line 56 added 1 line. |
| + *** Must mark up taxon names as concepts with GUIDs in the EML data sets first, GUIDs would be the concept IDs. Need a tool to do that, Morpho is the likely app. If no GUID in the data set, a call to TOS could match on data set taxon name and a taxon reference. |
| At line 57 added 1 line. |
| + *** Kepler work flow scenario: Kepler has Actors that can actually merge the data, need some user interaction with TOS to decide which level of lumping the user wants, include synonyms, concept overlaps, go up a level, etc. |
| At line 58 added 3 lines. |
| + **** if the GUIDs match between data sets, we merge |
| + **** if the names from two data sets match (derived from GUIDs in the date set) in TOS, we combine them |
| + **** if concepts match in TOS (other TOS operations) |
