| Line 12 was replaced by line 12 |
| - ** 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. |
| + 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. |
| Line 14 was replaced by line 14 |
| - ** Problem with names coming out TOS query being mapped to more than once of the concepts specified for DiGIR query for GARP input. |
| + Problem with names coming out TOS query being mapped to more than once of the concepts specified for DiGIR query for GARP input. |
| Line 16 was replaced by line 16 |
| - ** 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) |
| + 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) |
| Line 18 was replaced by line 18 |
| - ** 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. |
| + 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. |
| Line 20 was replaced by line 20 |
| - ** 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, |
| + 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, |
| Line 22 was replaced by line 22 |
| - *** 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. |
| + * 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. |
| Line 24 was replaced by line 24 |
| - *** 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. |
| + * 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. |
| Lines 26-28 were replaced by lines 26-28 |
| - **** 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) |
| + ** 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) |
